I'm going to go out on a limb from our previous design and say I've picked two of my favorites from the contest. Here's a mockup of the main site ( http://duckgoesoink.deviantart.com/art/Inkscape-Website-entry-front-81779014 ) here's a demo of another page on the site ( http://duckgoesoink.deviantart.com/art/Inkscape-Website-entry-main-81779682 ) also I halfway like the side navigation and the top of this theme... http://gri3fon.deviantart.com/art/Inkscape-redesign-entry-80320927 care to sound off or modify existing mock ups?
Thanks,
Ian

On Wed, Nov 24, 2010 at 12:33 AM, Bryan Hoyt | Brush Technology <bryan@brush.co.nz> wrote:
I agree with Ian re mockups vs. requirements. Mockups are usually a very good way to collect requirements, because people can *see* what's in the offering.

In the non-OSS world, I do a lot of specifications documents, and people *just don't get* verbal/written specs, no matter how literate they are. But a wireframe "screenshot" showing a set of features always gets people talking. "Can we have a button to ask for donations?", "Where's the menu for the forum?", "What about a sign-up-to-our-newsletter box?" etc.

That said, shouldn't we keep mockups very basic initially -- not much more than wireframes -- and then worry about graphic design? We don't want 10 people to waste their time designing awesome features that nobody wants.

 - Bryan

On Wed, Nov 24, 2010 at 20:49, Ian Caldwell <inchosting@gmail.com> wrote:
I do also agree on having one person in charge of that portion of the project which I'm trying to draft a team of talented developers and designers in order to delegate certain features off to the various people to best suit their skills and our needs... Mockups of how they think the site should look In my opinion is a part of setting up requirements....
Ian

On Nov 23, 2010, at 11:43 PM, n3storm <nestor@doodo.org> wrote:

You read my mind :


We could even tie in OSQA - http://www.osqa.net/ - and get a Stack Overflow-like system.  (That would really be a very suitable medium for Inkscape questions, I think.  Better than the traditional forum model.)  And the beauty of Django is that you can connect that to the rest - it doesn't need to be separate applications that you try to integrate, you dump the apps it uses into the project and it all Works.  (Disclaimer: I haven't actually tried deploying OSQA yet.)


Like Alex said
> collecting requirements first and doing designs later.
Wiki page for the analysis?

Then, we can discuss if django-cms, our mashup of django apps or http://mezzanine.jupo.org/ (the new guy in the pack) as starting point.

Another thing, I don't know how the actual site was made, but in my opinion the new one should be "directed" by one and only one person or else everybody will ask for every functionality and opinions about shades of green will start to slow down the project. Sorry if it sounds harsh, english is not my first language.

A couple of phase can get us to our objective, not everything in one go. IMHO

cheers,
Néstor

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel




--
PS. Check out the Brush newsletter: Subscribe or read our previous newsletters

Bryan Hoyt, Web Development Manager  --  Brush Technology
Ph: +64 3 741 1204     Mobile: +64 21 238 7955
Web: brush.co.nz