Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Higgins home page project plan

Revision as of 11:52, 13 April 2008 by Paul.socialphysics.org (Talk | contribs) (New Home Page Content)

Problems to Address

Even after the work that went into improving the Higgins website/wiki prior to the feb release of 1.0, we continue to get feedback that the site is:

  1. Lack of "integrity". It is confusingly mixed in with the rest of the Eclipse site. Most folks think Eclipse site is about IDE enhancements/plugins. We get comments like "that purple stuff isn't helping the Higgins cause". In reality that "purple stuff" helps Higgins enormously in various ways. But the Higgins website isn't one of them. Folks think that a project of the size and importance of Higgins should have its own site. Should be perceived of as standing on its own. They hear about Higgins, come to the site and then think "oh I must be mistaken, this looks like an IDE plugin. I wasn't looking for an IDE plugin".
  2. The http://eclipse.org/higgins home page is not professionally designed. It is critical that AT LEAST the home page be well designed and communicate well
    1. Part of the problem is the highly constraining Eclipse "phoenix" look and feel
    2. Part of the problem is our lack of concise, clear text and imagery

The Plan

  1. Develop new homepage text & imagery. Implement immediately while we wait for #2 below.
  2. Develop a new Higgins look & feel (hire outside design firm) and apply to the new content from #1

New Home Page Content

This section describes the key message hierarchy/organization.

TOP LEVEL MESSAGES

  • New diagram showing the "identity & user data layer". Shows the big picture, vision. Shows how apps, sites, web services plug into the "identity & user data layer" using a variety of protocols (WS-Trust, OpenID, SAML, LDAP, XDI). Shows that Higgins is a set of building blocks. You integrate different ones into what you're doing depending what kind of app you're building. The diagram includes blocks for:
    • RP solution 1.0+
    • IdP solutions 1.0+
    • Selector solutions 1.0+ <-- user-centric "controller"/"browser" component
    • Selector Selector <-- can we wedge this in?
    • IdAS client solution (1.1)
    • IdAS server solution (1.1)

Click on any of the above to drill in

  • Other things that should be on the home page:
    • news
    • events
    • movies on user-centric identity, dataportability?

MID LEVEL

  • RP solution
  • IdP solutions
    • STS IdP solution (1.0)
    • SAML2 IdP solution (1.0)
  • Selector solutions 1.0+ <-- user-centric "controller"/"browser" component
    • FF-embedded Selector (1.0)
    • Adobe AIR Selector (1.1)
    • GTK & Cocoa Selector (1.0)
    • RCP Selector (1.0)
    • Selector Selector (1.1)
  • IdAS client solution (1.1)
  • IdAS server solution (1.1)
  • Data Model
    • Although not a piece of code nor a solution, the Higgins Data Model makes the interoperability possible.
    • Core IdAS model (was "Higgins Global Graph")
    • Peripheral model

Done

The following problems have already been addressed:

  1. Develop a consistent approach to managing the wiki pages for different Higgins version (e.g. 1.0 vs. 1.1 content)

Back to the top