Views
Web infrastructure/Meego.com
(→Information Architecture) |
|||
| (One intermediate revision not shown) | |||
| Line 36: | Line 36: | ||
== Information Architecture == | == Information Architecture == | ||
<gallery> | <gallery> | ||
| - | |||
File:Web_Infrastructure_Site_Map_v01.png|Web Infrastructure Overview Diagram | File:Web_Infrastructure_Site_Map_v01.png|Web Infrastructure Overview Diagram | ||
| + | File:Meego.com_Site_Map_v1.1.png|Existing site map for meego.com | ||
| + | File:Meego.com_Home_Page_v1.0.png|meego.com home page overview | ||
| + | File:Meego.com_developers_section_v1.0.png|meego.com/developers sample page | ||
</gallery> | </gallery> | ||
| + | |||
| + | [[media:Meego_sitemaps_v01.1.graffle|MeeGo Site Maps OmniGraffle file]] | ||
== Tasks == | == Tasks == | ||
Latest revision as of 23:22, 10 December 2010
PROPOSAL - discussion
The team in charge of the maintenance, update and expansion of meego.com. Any significant change in the website content or structure is coordinated here.
Contents |
Team
- Webmaster: Mike Shaver
- Content coordination: Quim Gil
- Technical writing support: Noel Arnold
- Content owners:
- Homepage: Quim Gil
- Downloads: Mike Shaver
- Developers: Ronan Mac Laverty Bob Spencer
- Projects: Mike Shaver Working on new proposal.
- "Garage": Bob Spencer
- Community: Dawn Foster
- Forum: Reggie Suplido
- About: FIXME
- Netbook: Netbook Working Group
- Handsets: Handset Working Group
- IVI: IVI Working Group
- Connected TV: Connected TV Working Group
- Media Phone: Media Phone Working Group
Process
PROPOSAL
- Develop working architecture diagram (ie, site map) to better handle growth in a consistent and user focused way.
- Documentation/tutorials for creating and editing content, see Community WG list of tasks.
- Use the wiki for rapid growth. Then the consolidated pages can be agreed to move to the main site.
- Significant changes in the homepage and the main pages of each section need to be agreed first. Use the wiki to document major changes and the Community Matters forum to discuss the proposals. Bugzilla should be used to track the tasks.
- Following the point above, content owners have flexibility to improve and expand their own areas.
- Volunteers can help improving certain area at any time. Use the Community Matters forum or contact the related maintainer in order to get involved.
- Regular contributors in a specific area can request editing permissions and content ownership. Make sure the maintainers of a specific area agree with your candidacy before requesting it to the meego.com team coordinators.
Information Architecture
 Web Infrastructure Overview Diagram |
 Existing site map for meego.com |
 meego.com home page overview |
 meego.com/developers sample page |
MeeGo Site Maps OmniGraffle file
Tasks
We are using the main Community WG list of tasks to organize the meego.com specific work.
meego.com tasks are assigned and prioritized at the Community Working Group Meeting.
If you want to suggest a new task or get a task assigned to you just follow the usual Community WG process.
Bugs
Bugs and enhancement requests about meego.com content or functionality must be filed at http://bugs.meego.com/enter_bug.cgi?product=meego.com
Get involved
We welcome volunteers testing the site and providing feedback. Get started proposing specific improvements at bugs.meego.com, propose new content (text, graphics) and get involved in regular tasks.
- I can do some technical writing and graphics work as well --Texrat 04:47, 2 September 2010 (UTC)