Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Website Backlog"

(Prototyped in: ver2 */)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 
{{#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]]
+
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]]
  
== Flatten Solutions into the 3 solutions areas (nav structure change) ==
 
 
===Prototyped in */ver2===
 
SEE: http://higgins-project.org/ver2
 
* Change left-hand navigation menu
 
** Explode "Solutions" into the three "solutions areas": Higgins Selector, Identity Services, Attribute Services
 
*** Replace the single "Solutions" word in the left-hand-nav with the three solutions areas words (Higgins Selector,...etc.)
 
* Eliminate [[Solutions 1.0]] and [[Solutions 1.1]] pages moving their current (duplicative/conflicting) content into the appropriate sections of these pages (thereby eliminating overlap/conflict with these pages):
 
** http://www.eclipse.org/higgins/Client-Overview-1.1.php
 
** http://www.eclipse.org/higgins/WebSvc-Overview.php
 
** http://wiki.eclipse.org/IdAS_Solution <-- bad page anyway
 
* NOTE: the above 3 pages should all be wiki pages so that they are kept better up to date. The php pages are usually out of date at any given moment.
 
* Tuck the XDI4J solution underneath the "Attribute Services" 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 duplication/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.
 
* Here's another set of changes:
 
 
  TODAY        -->        PROPOSED
 
  =====                  ========
 
 
  Clients                Higgins Selector
 
  -------                ----------------
 
  AIR Client & Server    AIR Selector (including ICS)
 
                          Web Selector (including ICS)
 
  ICM[missing!]          merged into the above
 
  RCP                    no change
 
  GTK/Cocoa              no change
 
  FF-embedded            no change
 
 
 
  Identity Services      Identity Services
 
  -----------------      -----------------
 
  WS-Trust IdP            no change
 
  SAML IdP                no change
 
  RP                      no change
 
  Web Selector            moved up above
 
  XDI4J                  moved down below
 
                 
 
  Identity Att. Svcs      Attribute Services
 
  ------------------      ------------------
 
                          IDS - multiprotocol web service
 
                          XDI4J - now moved here
 
                          IdAS - today's Java framework
 
 
  Where IDS is short for "Identity Attribute Service," a multiprotocol
 
  attribute data service (web service) based on IdAS framework.
 
 
== Eliminate "Higgins Data Model" (nav structure change) ==
 
* 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 [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]
 
  
 
== Misc ==
 
== Misc ==
Line 83: 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)
 
== 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
 
* Identity Web Services
 
** IdP
 
** RP
 
** Web Selector
 
* IdAS
 
* Misc
 
** XDI4J
 
  
 
== Flash ==
 
== Flash ==
Line 125: 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)
 
 
 
== Done ==
 
 
* [[Higgins Wiki Done]]
 
 
[[Category:Higgins Marketing]]
 
 
* [[Higgins Site Look and Feel Done]]
 

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