Wiki » Website documentation

Site(s) vision

mageia.org is to welcome the whole Mageia community at large and host official contents about the association, the projects/products and derivative activities. It has to show the project's persona.

The Mageia community is: international, welcoming, open, teaching, technical, cross-disciplinary; made of people of very distinct types.

Roadmap to put this into work

1. discuss this document - not too many details, but clear directions (see #419
2. discuss this with: mar/comm', web, i18n team, propose for review to everyone else
3. implement global nav items + theming
4. implement global theme
5. implement main (www) mashup platform and aggregate existing contents and sites into hubs
6. organize edition/translation process
7. organize platform lifecycle
8. organize concept/integration/dev/test/deployment cycle

Use Cases

To think about (why do they come here and how? what do they see? what do they do? why do they leave? => what's the goal?)

We may need to specialize into separate sites/hubs for some of these people. But for a start, we will aggregate basic contents for each of these, within the same framework, focusing on the most important ones and prioritizing (to be done).

• Mageia User
• Non Linux User
• New visitor
• Student in Computer Science/Technical-digital-based discipline
• Student in other fields
• Experienced Community Member
• Potential New Community Member / Contributor
• Person New to Mageia
• Developer
• Potential Donor
• Software Editor
• School/University
• Experienced Duck

Hubs / Spaces

• Main Home
  • Mashup of most relevant pieces from next hubs (news, social, join, calls to action)
  • Direct presentation/get link to major product

• News/Communication
  • blogs & planets
  • timeline & calendar & events/meetings
  • social media / join
  • media/marketing tools
  • press releases/relations/reviews/tools
  • bonjourmageia, hugs
  • contact
  • irc, forums & mailing-lists
  • spread
  • stories/tales
  • metrics

• Product(s)/Project(s) (name?) OS, app-db, other?
  • Features
  • Getting it / Download
  • Extensions/Derivatives
  • Support (documentation, forums, irc, ml, online resources, partners, etc.)
  • Contributions (how to => Community => Contribute)
    • roadmap
    • variants

• Community
  • Self reflection / presentation (pervasive social network through mageia.org tools/sites?) / news / dating
  • Activities/Teams
    • Developers (each has its own hub), Packagers, Translators, Documentation, QA, Triage, Sysadmin, Release, Marketing, Comm, Artwork, Web, Metrics
    • Governance / Council / Board
    • Tools per activities?
      • Bugzilla
      • Wiki
      • transifex
      • svn, git,
      • pkgsubmit
      •  ?
  • People (see their faces, roles, activities - see above social net idea)
  • Join / Contribute

• About Us / the project
  • http://mageia.org/en/about/
  • vision
  • mission
  • governance
    • code of conduct
    • values
    • policies
    • statutes
  • free software / collaboration
  • contact
  • donations
  • financial/moral/sustainability reports
  • people / contributors
  • history
  • legal
  • thank you

Global navigation bar

(aka, global theme, global layout)

It's crucial that, at least at the top first level, all mageia.org shares the same design & navigation marks (same links, same layout, same colours, same identity, etc.).

Now, it's not exactly how we do it at this time. We have several ways to do that:

• have a google-like top nav (bookmark-like links + a user account link on the right) + local app/website design below
• have a apple-like top nav (few main universes on first level with embodied identity)
•  ?

Direction elements

Generic:

• As for representing the project and the people behind it, the site has to communicate the human, social touch of the project;
• show real people, really involved in the project;
• show people confidence;
• have a photographic/concrete quality;
• show things as they are, no fake, no bullshit, no static.
• Stay focused on each topic.
• Be welcoming.
• Be fun.
• Be creative.
• Be inclusive, minimalist or be prepared/ok to try a design and throw it completely away after some work on it.
• Showcase what the persons in the project can do, what users/developers can do with the product, wherever possible, but keep it simple.

Technical:

• aim for/use HTML 5 now
• forget IE 6
• validate
• aim for the edge, must work on Firefox & webkit-based browsers, should degrade gracefully on IE & Konqueror (if needed to degrade)
• be accessible
• don't try to be all at once
• continuous integration/deployment / small steps
• validation pre- and post-production (live)
• have a consistent, global navigation system (same theme, same behaviour, localized) for mageia.org as much as feasible
• have a consistent theme across spaces/hubs, at least at the top levels?