Bugzilla – Full Text Bug Listing
| Summary: | Update project home page | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Rüdiger Herrmann <ruediger.herrmann> |
| Component: | Website | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | caniszczyk, tbuschto |
| Version: | unspecified | ||
| Target Milestone: | 1.3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 307932 | ||
|
Description
Rüdiger Herrmann
Link to single-sourcing page Refer to "RAP Runtime" instead of "Target Platform" on downloads page * Project summary, "Articles" still links to buzz page ( http://www.eclipse.org/projects/project_summary.php?projectid=rt.rap ) * Cleanup "Getting started instructions" * Remove 3.3 or earlier steps, ppl should use at least 3.4 and if not they should still be able to install a "regular" plugin. In my eyes this would help to clean up the whole page. * Add screenshot for the intro action. It's pretty easy to ignore the paragraph at the bottom that tells you the essential step how to install RAP (the runtime). * New & Noteworthy * Sort by release date. Currently the first item after 1.3 is 1.1.2 - we should rather put 1.2 there * We could even nest the releases (one item per release with subitems to the SR) * Documentation (http://eclipse.org/rap/documentation.php) * We should concentrate more on single sourcing. Currently the page has one mention of the term "single sourcing" * We should use icons for the different article/resource types. This would improve readability a lot as the titles would be in line with each other. (see http://eclipse.org/articles/) * Add news item to the right bar * This could be filled with content from an EclipseSource blog rss feed. All articles tagged with RAP for example. * Get Help * We should try to minimize the texts. It's pretty much to read for some steps. This way I don't think ppl will read it at all. * "Ask on the Community Newsgroup" should have a direct reference to the newsgroup * Bugs - http://eclipse.org/rap/bugs.php * Currently the query icon is broken * Contributing * Link to all bugs in "contribute patch" section * Link to Coding conventions is empty * The "Project Plan" menu item should rather point to a page of its own, explains the overall themes and links to the generated project plan. * The layout needs to be cleaned up to leave some space on the right for boxes, as seen on the project home page. * Add a custom CSS like emf page (e.g. to get decent bullet points). *** Bug 283048 has been marked as a duplicate of this bug. *** * Add links to RAP-related documentation (ie BIRT integration, e4 effort, etc) * we should also add some pointers where to get the source code of our demos * Since the help version in the Eclipse helpcenter does not correspond with the latest milestone, we should also include the help html files of the latest milestone into our website directly. The RAP team can consider crowdsourcing their documentation via Eclipsepedia. http://eclipsesource.com/blogs/2009/07/13/crowdsourcing-documentation-at-eclipse/ This way it's easier to keep things in sync :) * add links to the new Eclipse forum - http://www.eclipse.org/forums/index.php?t=thread&frm_id=34 * we should definitly add a psf to every demo so user can checkout our demo source. got the second request in two days where to find the source for our examples. * update newsgroup description From Denis mail: Since there are over 150 newsgroups at Eclipse.org, I'd like to ask you to revise your current newsgroup description. Use the Portal > Eclipse Projects > [view] > [maintain] Project Info Metadata to do so. * we should move old N&N pages to an N&N archive and only show current stable release + SR and current development version the articles on the documention page should be marked with a skill level (eg. expert for the readAndDispatch whitepaper) Just fixed the following items in cvs: * Refer to "RAP Runtime" instead of "Target Platform" on downloads page * Project summary, "Articles" still links to buzz page * query icon is broken * Add links to RAP-related documentation (ie BIRT integration, e4 effort, etc) * Add a custom CSS like emf page (e.g. to get decent bullet points). * Contributing * Link to all bugs in "contribute patch" section * Link to Coding conventions is empty * Cleanup "Getting started instructions" * Remove 3.3 or earlier steps Added a new psf for RMS+Examples+Example Design to CVS page, added pointer on the demo page. Open items currently left: General * re-think content of left 'main menu' * The "Project Plan" menu item should rather point to a page of its own, explains the overall themes and links to the generated project plan. * The layout needs to be cleaned up to leave some space on the right for boxes, as seen on the project home page. * include help center html of current milestone Introduction * use windows screenshots on Introduction page * Add screenshot for the intro action. It's pretty easy to ignore the paragraph at the bottom that tells you the essential step how to install RAP (the runtime). New & Noteworthy * Sort by release date. Currently the first item after 1.3 is 1.1.2 - we should rather put 1.2 there * We could even nest the releases (one item per release with subitems to the SR) * we should move old N&N pages to an N&N archive and only show current stable release + SR and current development version Documentation (http://eclipse.org/rap/documentation.php) * We should concentrate more on single sourcing. Currently the page has one mention of the term "single sourcing" * Link to single-sourcing page * We should use icons for the different article/resource types (see http://eclipse.org/articles/) * Add news item to the right bar. This could be filled with content from an EclipseSource blog rss feed. All articles tagged with RAP for example. * the articles on the documention page should be marked with a skill level (eg. expert for the readAndDispatch whitepaper) Get Help * We should try to minimize the texts. It's pretty much to read for some steps. This way I don't think ppl will read it at all * "Ask on the Community Newsgroup" should have a direct reference to the newsgroup * add links to the new Eclipse forum - http://www.eclipse.org/forums/index.php?t=thread&frm_id=34 XText ( http://www.eclipse.org/Xtext/ ) has a great welcome page for their project. In my eyes we should try to come up with something like that too. (In reply to comment #18) +1, I like the header with those quick navigation buttons. We should also add the new eclipseRT logo somewhere: http://wiki.eclipse.org/EclipseRT_Logos Yes, the Xtext and AMP pages are pretty. There is even a default template for this frontpage, see http://eclipse.org/default/ (and thanks chris for the pointer) I can't find anything regarding browser compatibility on the project page (except in the plan). We should make clear that RAP runs on the popular browsers. My suggestions: - Create prominent "Demo"-button: Like the current "Download"-button. The frame around the "Download"-Button should be removed (it's still very eye-catching) and placed around the "Demo"-button. To make room for the new button, two of the other three buttons will have to be merged or resized. - Improve/rethink header: Since it's looking exactly like the one on www.eclipse.org and has the Eclipse-logo above it, it gives the impression that it's not RAP-specific. (Thats also one of the reasons a new "Demo"-button would be important. ) Also, if we had the "Demo" button, AND if it were possible to directly click on the subtopics in each of the bigger buttons, the header would be entirely useless and could go. - More narrated vids. (I love the current one, but after watching it, there is currently only more video offered, and its not narrated. Surely there are a couple of great RAP-features we could demo there.) - Some kind of "news" box. Currently we have this "RAP Arrivals"-box, which is great, but who cares about new versions if it's not clear what improvements they bring? We could display some selected or random content of the last releases N&N in a similar box below the "Arrivals". For Helios, the work on the website can be considered completed. For ongoing updates and improvements, we should open new bugs. |