All the current webpages are now reflected in blueprints for the staging website: https://blueprints.launchpad.net/inkscape-web I've used the nomenclature of "+" to indicate child pages, and to include the parent page in the title.
There are a number of blank pages still existing: *about+overview *about+screenshots (at least not much) *community *community+gallery (limited) *learn *contribute *contribute+contributor-stats *develop (not much more than descriptions and links to the child content) What stands out to be in this review is that _many of the parent pages are blank_. I also understand that this is the staging site which has not been completed. I would prefer we not simply fill a void by adding content, or simply add links to the content on the child pages. Rather, is there a strong reason for these parent pages to exist at all, beside simply adding a category for the necessary child pages? If there is a vision for these pages I would like to see that reflected in our blueprints. Otherwise I think we may see need to consider a revision of the menu structure to keep a simple site and not loose users in the multiplicity of pages.
I would love to contribute more in filling content, if suggestions can be made within these blueprints or through the mailing list! Thanks.
--Jared
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,
We essentially need to populate only the Community, Learn and Contribute parent pages. This really isn't too many pages for me to think we have an build-in argument to bypass these parent pages. I vote to keep them in too.
Within Joomla I've at times made pages that are mashups of child pages, through tabs within the content, or snippets from the children. But again, I'm not sure that will keep it clear for this website's purpose; and I really would prefer to not be redundant.
I'll just consider what content can land there, and await and include any suggestions that come along! The Develop -> Getting Started/Coding Style/Bug Management is a good example, thanks Martin. If that's the basic vision I'll try to continue in that.
--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,
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,
On Mon, 2013-08-05 at 23:55 +0000, Jared Meidal wrote:
What's a good way to tag blueprints for common understanding regarding status?
Approved - More than 2 people think it's a good idea Pending Approval - Less than 3 people think so Review - N/A Drafting - Planned outline under construction (inline, wiki orgoogle doc) Discussion - N/A New - New Superseded - Superseeded Obsolete - Obsolete
These blueprints would only plan out the construction of page content and not be about drafting actual content though. Staging should be used for that and we can do a round of editing as needed. I expect many pages to go through quick drafting to approval and move onto content creation in the cms.
Martin,
participants (2)
-
Jared Meidal -
Martin Owens