Website Analysis and Design: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 24: | Line 24: | ||
=== | === Users coming from the world of free software === | ||
I see three uses cases for user who already are used to free software: | |||
* New users who already have Scribus installed in they computer through the package manager | |||
* Potential users want to know if Scribus fits their | |||
=== Alternative graphic artists === | === Alternative graphic artists === | ||
=== Companies and public agencies looking for a cheaper solution === | === Companies and public agencies looking for a cheaper solution === | ||
Revision as of 07:59, 8 April 2010
This is where the discussion of business vision, scope, and user stories will converge into an outline of the website redesign.
proposal by a.l.e
- multilingual (en, de, fr, nl, es, it, pt, ...); how to manage the workflow?
- as little content as possible (the real content should be in wiki.scribus.net and docs.scribus.net)
Targeted users
I have identified five typologies of users which should be targeted by the scribus website:
- End users coming from the world of free software
- Alternative graphic artists
- Companies and public agencies looking for a cheaper solution
- Potential and current contributors
- Potential developers
In section I define the path each type of user is expected to follow when navigating the scribus website.
Users coming from the world of free software
I see three uses cases for user who already are used to free software:
- New users who already have Scribus installed in they computer through the package manager
- Potential users want to know if Scribus fits their
Alternative graphic artists
Companies and public agencies looking for a cheaper solution
Potential and current contributors
Potential developers
Structure and content
Homepage
Draft screenshot
Media:Website_proposal_ale.svg
Content
- scribus logo
- a top navigation
- about
- download
- community
- development
- a short description of scribus (300 to 500 chars)
- a feature list (3 sections with few words and a link)
- bigger download button with link to the current stable version for the visitor's current system
- one or more screenshots presented in a fancy way (transparences, irregular form)
- One highlight (300 to 500 chars)
- list with max 3 news (not older than 3 months)
- title + short description + link (+ picture?)
- a "beginning with scribus" button
- a keywords cloud (manually defined)
- bottom link list (more on the administration side...)
- contact
- sitemap
- sponsors
- a "standard" way to show special promotions (like the lgm pledgie, the new book)
- if no special promotion show one sponsor randomly picked each time + link to all the sponsors
- a top navigation bar with some special links
Graphical page structure
about
- about scribus (2'000 chars description)
- team
- name, nickname, competences, picture
- how to contact the team
- scribus association
- complementary projects
- fontmatrix
- littlecms
- gimp
- inkscape
download
- download
- short introduction to download according to the visitor's current operating system + link to the documentation for more infos.
- bigger download button with link to the current stable version for the host system
- stable version
- for each platform
- unstable version
- for each platform
- development version
- link to the latest available snapshot for each platform
- svn link + link to how to compile from svn
comunity
- community
- link to documentation
- why and how report bugs + link to bugs
- link to ML and to our web irc client
- eventually user friendly subscribe / unsubscribe form for the mailing list
- web irc client
development
contact
sitemap
- sitemap
- entries are manually added (not generated)
- several columns
Ssponsors
- sponsor
- list with logo, name, website and a description of what the sponsor is doing for scribus