Difference between revisions of "Website Backlog"

Revision as of 16:02, 25 March 2008

{{#eclipseproject:technology.higgins}} Under construction, getting there, but a still a work in progress.

Wiki

• Bugfixes for 179537 - Done
• Re-update wiki pages to refresh nav cash where necessary (Top pages only) - OK now
• Finish applying web nav to all wiki pages bugzilla 223927
• Propose wiki page release versioning to dev list with sample page. (For now there is a released version and an underdevelopment version. At some point we may need to support more versions. Navigation link is to the released version with a link near the top of the page to previous versions. Need to play with layout/text to make this clear and easy. Consider converting wiki doc to php when doc is released.)
• Create an Eclipse Community wiki bugizilla item for supporting project specific look and feel's
• Create new Higgins specific look and feel "template" once we know the format and have new look and feel for website.

Website Look and Feel

• Jack draft new text picture concept for new home page for 3/25
• Mary Update plan with additional tasks and sequencing -done for 3/25 - will continue to evolve
• Can MediaWiki support expanding tabs?
• Respond to Bjorn about fade and button so rebels have some commonality - initial request 3/24
• Review status of effort with respect to engaging a Designer
• Prepare package for Designer for objectives for Higgins website - goal is new design and images that we can use to implement new look and feel and organization for www.eclipse.org/higgins website.
  • Bjorn is requiring a link to the standard project information somewhere in the upper left area of the page. Something to be the equivalent of this: http://www.eclipse.org/projects/dev_process/project-status-infrastructure/left-menu.php At the moment he is requiring the "About This Project" wording, etc., but is open to other ideas for our new cool pages.
  • Link to sample fade from Eclipse logo to Higgins logo. (Website still needs to have Eclipse logo at the top, like Apache projects have the feather. This is just an initial pass)
  • Still has Eclipse legal stuff at bottom.
  • Implementation: New design is in PHP and technically compatible with Eclipse.org site where it will run.
  • Here is a proposed home page concept: very top-level description of the three-layer cake, with some cool illustrations (not these, these are just placeholders) highlighting each.
    

    Proposed Home Page Concept
  • --Paul.socialphysics.org 16:35, 21 March 2008 (EDT) comment on the above image. I think that the Higgins logo should not be on equal standing with the Eclipse logo across the top. I think Eclipse should be much smaller, less prominent.
  • Should pass the 5 second "is cool" test
  • May include new cool graphics for end user download button(s) something better than
  • etc.
• Iterate on new design with Designer.
• Vet new design with Higgins dev list.
• Implement new design.
• Update Eclipse project "about" page that works with the new design.
• Create new version of intro/benefits text

Navigation - somewhat related to redesign

• Website navigation
  • Make one more clean-up pass on proposed navigation.
  • Post re-revised navigation organization to Higgins-dev listPropose to Dev list for feedback
  • Implement new nav (implies re packaging of some web and wiki pages)
  • Redirect higgins-project-org to www.eclipse.org/higgins when ready
  • Website navigation
    • Implement new nav in meta data for wiki
    • Update all wiki pages to get new nav (add higgins project control code where still needed)if necessary

Note: This will likely drive some additional content rewrites besides what is listed below

The following are independent improvement activities

New Downloads Organization

• Create new download approach
  • Design new download approach to meet the needs of different "users"
  • Vet download design with the dev list.
  • Develop new content required by download approach
  • Implemement new download approach - bugzilla: 218923

General Website Organization - can be done now, anytime

• Update projectplan and breakout milestone pages - 223368
• Combine status page with updated project plan page
• Combine volunteer and getting started material
• Create a nursery directory for the Website so we can continue to do ongoing updates to the existing site while we are creating a major new nursery in the directory. (currently only have "production" and "development" (ver2) directories) call it nursery.
• 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

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)

Incorporation of CloudTripper Website

• Start with a link. Make it so that CloudTripper is a visible example of one type of thing that can be done with Higgins
• Evaluate cost/benefits of consolidation

Flash

• Create flash video(s) and make available from a link on the home page.
• Could be several short 60-90 second ones.
• 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 priorty)

• Create hands on developers tutorials (i.e. how to add Higgins to my blog, How to hook a silo site up to CloutTripper or whatever...etc.)

Bounties

• Jazz up the request for volunteers with requests for specific bounties (when funding permits)

Other

• Twitter

etc...