[pydotorg-www] www.python.org: types of changes

[Richard Leland]

Thanks for your insight Aahz - it's good to have a breakdown of exactly what
content and appearance mean. Adding to the plan...

- Rich

Richard Leland
rich at richleland.com
240-242-7424


On Fri, Apr 23, 2010 at 4:42 PM, Aahz <aahz at pythoncraft.com> wrote:

> Rich's project goals at
> http://richleland.bitbucket.org/pydotorg-pm/goals.html
> includes the following:
>
> Agility
>
>   Making modifications to the content of the site currently requires a
>   build of static files and a level of technical expertise. The site
>   content and appearance need to be easier to update.
>
> My suggestion is that we should be careful about specifying exactly which
> types of updates we're discussing.  I would classify changes this way:
>
> Organization
>
>    The way pages are connected to each other, and the way a visitor
>    perceives sections of the site
>
> Content
>
>    The actual text of the site and downloadable documents
>
> Layout
>
>    Location of content elements on a page (which should have consistency
>    across all pages)
>
> Appearance
>
>    Text formatting and images used to convey organizational cues
>
> Obviously, these are all interrelated, but often one is focusing on only
> one or two aspects of updating the site at any particular time.  Also, I
> generally prioritize these changes in the order that I've listed them
> (with the caveat that making organizational changes is sufficiently
> difficult and controversial that it rarely happens).
> --
> Aahz (aahz at pythoncraft.com)           <*>
> http://www.pythoncraft.com/
>
> "It is easier to optimize correct code than to correct optimized code."
> --Bill Harlan
> _______________________________________________
> pydotorg-www mailing list
> pydotorg-www at python.org
> http://mail.python.org/mailman/listinfo/pydotorg-www
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pydotorg-www/attachments/20100426/6f778af1/attachment.html>