I'm following on this thread discussions that happened here and on another
thread ('critics').

A few additional ideas :

*       Two issues I see and a possible solution for these
o       The first problem I see is that it is not easy according to me to
keep the site as it is and make it relevant both for 1) people who want to
play and/or contribute (not too much information, straight to the point, etc
- see Josselin's feedback on that) and for 2) us who need everything to be
available. This is the discussion that Xav and Josselin had on essential vs
comprehensive information, I agree with the issue.
We could break each category (game/project/company/references) into two
pieces on their home page, first piece with the core information and second
piece with the rest but I've tried to think about it and I'm not satisfied,
it does not work very well (but you might have ideas about it that I did not
have).
o       second issue that has been bothering me is that the distinction
between game and project makes sense when it comes to addressing separately
gamers and contributors, but I don't find it very coherent, there are some
bits that could belong to both categories. For instance the game design part
that is currently in project, but it could also make sense to have it in
game (where I could see the description of the game as it is, the features
that are coming in the next patch, the features currently in discussion,
etc.)
o       solution :
*       create a specific view for gamers and a specific view for
contributors, distinct from the main structure of the rest of the wiki, but
that points towards existing elements of the wiki. For instance, on the home
of the wiki, we show one block 'contribute' and one block 'play', each block
leading to a specific page. These two pages extract from the rest of the
wiki only the core elements for a player and for a contributor. So it's not
the same organization as we have today, though we already have the blocks.
*       Actually we may need a third block to present the studio - which
would lead to a page that has links towards the pitch and the bp and the
values, and maybe also explaining the overall organization (social contract,
role of the studio within the community, etc).
*       Merge the project and game categories, so that we can organize it
better (game as it is, current developments, current brainstorm, guidelines,
etc). 
*       The wiki would then have the following structure : 3 categories
(game and company and reference) that contain all the content of the wiki.
And 2 (or 3) specific views, one page for players and one page for
contributors, that point towards elements of the wiki that we think are
relevant for these two pages.
This, according to me, gives us more flexibility and more clarity.
*       Does it make sense ? If it is unclear how to structure things, I can
draft on power point some sketches
*       I think we should have a link to the site map (present at the bottom
of pages ?)
*       It would be nice if each page could show the path (ex : home >
project > guidelines > social contract) so that the user knows where he is,
how much work would it be to add it on mediawiki ?
*       Project pages, I was wondering how to break up pages regarding
development of the game (and links towards tools), Xav please let me know
because you have a better view than me on the various tools :
o       Current status of the game (existing quick insight + we could add on
the wiki release notes of what has been added in the builds)
o       Currently in development (and future builds for which we already
know what will be developed) : link towards the list of features which is on
the task tool (mediawiki TBC) ? Each feature broken into tasks in this tool
*       Specifications of these features through a link towards blueprints
of Launchpad
o       Brainstorm for the next builds : link towards uservoice
*       Blog : why not but I'm not sure how people will know what they can
find on wiki vs blog, don't you think it can become confusing ?

The mail is already long so I won't go into the detail of the structure.
Once we have an agreement on the macro structure, I can start listing the
elements that should appear in the 'play' and 'contribute'  and 'learn about
the studio' pages, and Xav and I (and other ones if motivated !) can share
implementation.

D

<<attachment: winmail.dat>>

_______________________________________________
Hackit Bar mailing list - [email protected]

Wiki:  http://community.hackit.cx/
List:  http://community.hackit.cx/ml/
Forum: http://community.hackit.cx/forum/
Ideas: http://community.hackit.cx/ideas/
IRC:   irc://irc.freenode.net/#politis

Reply via email to