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.
Difference between revisions of "Website Backlog"
(→Site Nav Improvement (flatter, more consistent structure)) |
(→Site Nav Improvement #1 (flatter, more consistent structure)) |
||
| Line 2: | Line 2: | ||
This page is a catch-all area of ideas of what we COULD or MIGHT to do improve http://project-higgins.org. What we ACTUALLY plan to do is listed here [[Higgins 1.1 Plan]] | This page is a catch-all area of ideas of what we COULD or MIGHT to do improve http://project-higgins.org. What we ACTUALLY plan to do is listed here [[Higgins 1.1 Plan]] | ||
| − | == | + | == Flatten Solutions into the 3 solutions areas (nav structure change) == |
* Change left-hand navigation (i.e. the main site structure) | * Change left-hand navigation (i.e. the main site structure) | ||
Revision as of 10:53, 5 March 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}} This page is a catch-all area of ideas of what we COULD or MIGHT to do improve http://project-higgins.org. What we ACTUALLY plan to do is listed here Higgins 1.1 Plan
Contents
- Change left-hand navigation (i.e. the main site structure)
- Explode "Solutions" into the three "solutions areas": Higgins Client, Identity Web Services, IdAS
- Replace the single "Solutions" word in the left-hand-nav with the three solutions areas words (Higgins client,...etc.)
- Eliminate Solutions 1.0 and Solutions 1.1 pages moving their content into the appropriate sections of these pages (thereby eliminating overlap/conflict with these pages):
- NOTE: the above 3 pages should be changed back to wiki pages so that they are kept better up to date. The php pages are usually out of date at any given moment.
- Explode "Solutions" into the three "solutions areas": Higgins Client, Identity Web Services, IdAS
- Tuck the XDI4J solution underneath the "IdAS" solution-area instead of treating it as an orphaned fourth solution area
- Benefits:
- Consistency: left hand nav would now be CONSISTENT with the home page (three + misc) vertical "doors"
- Eliminate conflict mentioned above
- Flatter structure: we've now organized our solutions into these four buckets, clicking on each brings you straight there
- More digestible: the reason we created the "four doors" approach was to chuck Higgins up. Solutions mashes all these disparate solutions back together again.
- Tuck the Context Data Model as a solution under the "IdAS" solution area
- Eliminate the overarching Higgins Data Model it has been a placeholder for years. The only substance is in the CDM which is ONLY used by IdAS solutions
Downloads
- Need some new ideas here. The current page that clicking "Downloads" at left brings you to is terrible: http://www.eclipse.org/higgins/downloads.php
- HBX links bring you to some old milestone builds of some random "HBX" component nothing useful
- The "real" download content is gotten to from the Components page
- Design new download approach to meet the needs of different "users"
- Use the Components page as a "download index"?
- Call out "Selected Downloads" (a few easy-to-consume solutions) vs. All downloads?
- Take out a layer. For example, combine the page that lists all the available builds Example 1 with the page that you get when you click a build, that lists the available parts Example 2. This could be done by adding 3 additional links to each row on the first page, and eliminating the 2nd.
- Vet download design with the dev list.
- Develop new content required by download approach
- Implemement new download approach - bugzilla: 218923
Misc
- Combine volunteer and getting started material
- Clean up website directories when are done experimenting.
- Make the POI and other Higgins papers more visible in own section under news. Don't just bury in press releases.
- Break Higgins based Solutions at the bottom of Solutions page into open source and commercial offerings.
- Revise Charter and update old long description
- Twitter?
Eclipse i-cards
- Creation and use of "Eclipse" i-cards to build community and drive usage experience
- Follow-up with webmaster on specifics of relationship between bugzilla and mediawiki
- Work with ICF and community on error handling for existing MediaWiki ((*Heads up to Charles)
- Work with ICF and community on workflow for RP's
- Propose details of Selectors offered initially and subsequently (Hosted (FireFox or AIR), Digital Me or Higgins hosted??)
- Also create bugzilla RP and distribute widely
- Draft phased proposal for Eclipse (types of cards, systems)
Solutions organization
- Higgins Client
- Selector
- for Andorid
- for iPhone (experimental)
- for Mac
- AIR
- Cocoa
- for Windows
- AIR
- GTK
- for Linux
- RPM
- Debian
- Higgins Selector Selector (HSS)
- Higgins Browser Extension (new multi-protocol integrated version)
- For FF
- For IE
- For Safari
- For Chrome
- Selector
- Identity Web Services
- IdP
- RP
- Web Selector
- IdAS
- Misc
- XDI4J
Flash
- Create flash video(s) and make available from a link on the home page.
- Could be several short 60-90 second ones. See two Data Portability videos, one in flash and the other in Blair Witch project style http://www.youtube.com/watch?v=TupCZY09Kwc
- Also show at workshops, etc.
- When the site looks good and navigates well and we have a more polished end user experience post to YouTube and blog about it.
- Can we get Derick Ashong to star in a brief video?
Tutorials
(This is much lower priority, requires more maturity)
- Create hands on developer tutorials (i.e. how to add Higgins to my blog, How to hook a silo site up to CloudTripper or whatever...etc.)
Bounties
- Jazz up the request for volunteers with requests for specific bounties (when funding permits)