Difference between revisions of "Higgins home page project plan"

Revision as of 13:58, 14 April 2008

This page focuses only on the http://eclipse.org/higgins page. For a complete list of what we'd like to get done someday on the wiki/site see: Website and Wiki Backlog.

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:

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".
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

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

New diagram showing 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:
After the above image has been reviewed a bit, we'll hire an illustrator to make it engaging and fun. Preferably Tim Nihoff (the same illustrator who created the Higgins mouse)
I think we should add hot spots to the image to allow you to drill in on each Higgins solution. And maybe each could also have a popup?
We need to decide what other things belong on the home page, and where. Today's home page is too boring and not well organized:
- News
- Events
- ??

See existing Solutions page
The solutions page will continue to mix together on one page both 1.0 and 1.1 solutions.
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)
XDJ4J solution

Existing Data Model page
Proposal:
- Change "Higgins Global Graph" to "Core IdAS model"
- Change the rest of the data model to "Peripheral model" or something like that

The following problems have already been addressed:

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

@@ Line 16: / Line 16: @@
 * New diagram showing 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:
-* [[Image:Higgins-vision-illustration-v2.PNG]]
+* [[Image:Higgins-vision-illustration-v3.PNG]]
 * After the above image has been reviewed a bit, we'll hire an illustrator to make it engaging and fun. Preferably Tim Nihoff (the same illustrator who created the Higgins mouse)
 * I think we should add hot spots to the image to allow you to drill in on each Higgins solution. And maybe each could also have a  popup?