Martin,
What's a good way to tag blueprints for common understanding regarding status?
e.g. Approved Pending Approval Review Drafting Discussion New Superseded Obsolete
--Jared ________________________________________ From: Martin Owens [doctormo@...400...] Sent: Monday, August 05, 2013 4:41 PM To: Jared Meidal Cc: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Staging website blueprints up
On Mon, 2013-08-05 at 23:19 +0000, Jared Meidal wrote:
I would love to contribute more in filling content, if suggestions can be made within these blueprints or through the mailing list! Thanks.
The parent menu pages are a technical snag, if you can figure out how to make DjangoCMS optionally not have pages for menu items they can be changed freely between pages and non-pages as needed. Although for consistency we should choose one.
I'd like to have pages rather than not. Parent pages should present a more general and inclusive description and invitation while child pages are more detailed and focused on the reader who knew what they wanted.
Example: Develop -> Getting Started/Coding Style/Bug Management
Develop parent doesn't have to be just a link to the three sub pages. It could explain things like 'why help inkscape', 'who developers inkscape' and 'what sort of things does one need to know to develop'. These are all useful things to inform readers but are far more general than specific which the child pages take care of.
My feeling is that we should aim for both and use the menu to deliver both.
Martin,