Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Website Backlog"

Line 5: Line 5:
 
* More bugfixes for 179537 - making wiki nav look like website nav (continued meta data editing bugs)
 
* More bugfixes for 179537 - making wiki nav look like website nav (continued meta data editing bugs)
 
* Create an Eclipse wiki bugizilla item for supporting project specific look and feel's
 
* Create an Eclipse wiki bugizilla item for supporting project specific look and feel's
* Create new Higgins specific look and feel "template
+
* Create new Higgins specific look and feel "template once we know the format and have new look and feel for website.
once we know the format and have new look and feel for website.
+
  
 
Website
 
Website
 
* Post revised navigation organization to Higgins-dev list
 
* Post revised navigation organization to Higgins-dev list
 
* 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.
 
* 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:
+
** 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 slick pages.  
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 slick pages. Still something on the top or top left...
+
** 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.
 +
** Still has Eclipse legal stuff at bottom. See www.eclipse.org/higgins/ver2 bottom line.  
 
** etc.
 
** etc.
 
* Iterate on new design with Designer.
 
* Iterate on new design with Designer.
* Vet new design with Higgins dev list
+
* Vet new design with Higgins dev list.
 +
* Implement new design on in PHP
  
  
 
etc...
 
etc...

Revision as of 20:01, 19 March 2008

{{#eclipseproject:technology.higgins}} Under construction, NOT yet complete..

Wiki

  • More bugfixes for 179537 - making wiki nav look like website nav (continued meta data editing bugs)
  • Create an Eclipse 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

  • Post revised navigation organization to Higgins-dev list
  • 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 slick 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.
    • Still has Eclipse legal stuff at bottom. See www.eclipse.org/higgins/ver2 bottom line.
    • etc.
  • Iterate on new design with Designer.
  • Vet new design with Higgins dev list.
  • Implement new design on in PHP


etc...

Back to the top