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"

(New Site Look and Feel)
 
(56 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{#eclipseproject:technology.higgins}}
+
{{#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'd like to do for 1.1 is here: [[Higgins 1.1 Wishlist]]
  
== Wiki ==
 
To Do:
 
* Finish applying web nav to all wiki pages 223927
 
  
Done:
+
== Misc ==
* [[Higgins Wiki Done]]
+
 
+
== New Site Look and Feel ==
+
Original Design Goals:
+
* Give the site have a sense of "integrity". Its a standalone destination project with navigation that stays within the project while tying this in to the Eclipse mother ship
+
* Make it seem like Higgins is a "cool" project
+
* Follow this messaging hierarchy:
+
** Tagline: Open Source Information Cards
+
*** Something short and sweet
+
** Provide a graphic and introductory text that draws the visitor in
+
** Longer description: Higgins an extensible, open source identity framework. For end-users Higgins provides an Identity Selector (think "wallet") application that allows a use get, manage and use "Information Cards". For developers Higgins provides a platform- and protocol-agnostic identity management framework. The Higgins framework is an abstraction layer that provides a set of APIs for developers. Developers can use Higgins to build identity "provider" web services (e.g. a Token Service) as well as to enable relying websites and applications to rely on identity assertions from identity providers.
+
 
+
To Do:
+
* Gather feedback on http://eclipse.org/higgins
+
 
+
Done:
+
* [[Higgins Site Look and Feel Done]]
+
 
+
== New Downloads Organization ==
+
* Create new download approach
+
** Design new download approach to meet the needs of different "users"
+
*** Use the [http://wiki.eclipse.org/Components 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 [http://www.eclipse.org/higgins/ver2/downloadsnew.php?loc=downloads/hbx Example 1] with the page that you get when you click a build, that lists the available parts [http://download.eclipse.org/technology/higgins/downloads/hbx/builds/R-R20080222-200802220506/index.html 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: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218923 218923]
+
 
+
== General Website Organization - can be done now, anytime==
+
* Update project plan and breakout milestone pages - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=223368 223368] Done
+
* Combine [http://www.eclipse.org/higgins/status.php status] page with updated [http://www.eclipse.org/higgins/projectplan.php Project Plan] page, and [http://www.eclipse.org/higgins/past%20milestones.php Past Milestones] page into a single page. - Done - All but archive material combined
+
 
* Combine volunteer and getting started material
 
* 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. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=224379 224379] Done
 
 
* Clean up website directories when are done experimenting.  
 
* 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.
 
* 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.
 
* Break Higgins based Solutions at the bottom of Solutions page into open source and commercial offerings.
*Revise Charter and update old long description
+
* Revise Charter and update old long description
 +
* Twitter?
  
== Eclipse i-cards ==
+
=== Eclipse i-cards ===
 
* Creation and use of "Eclipse" i-cards to build community and drive usage experience
 
* 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
 
** Follow-up with webmaster on specifics of relationship between bugzilla and mediawiki
Line 52: Line 19:
 
** Also create bugzilla RP and distribute widely
 
** Also create bugzilla RP and distribute widely
 
**  Draft phased proposal for Eclipse  (types of cards, systems)
 
**  Draft phased proposal for Eclipse  (types of cards, systems)
 
== Incorporation of CloudTripper Website==
 
* Start with a link.  Make CloudTripper is a visible example of one type of thing that can be done with Higgins
 
* Evaluate cost/benefits of consolidation
 
  
 
== Flash ==
 
== Flash ==
Line 70: Line 33:
 
== Bounties ==
 
== Bounties ==
 
* Jazz up the request for volunteers with requests for specific bounties (when funding permits)
 
* Jazz up the request for volunteers with requests for specific bounties (when funding permits)
 
== Other ==
 
* Twitter
 
 
etc...
 
 
[[Category:Higgins Marketing]]
 

Latest revision as of 21:27, 23 June 2010

{{#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'd like to do for 1.1 is here: Higgins 1.1 Wishlist


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)

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)

Back to the top