Talk:Organic Design Conventions
How is this article different to best practices? Should we not merge this content with the Best Practices article?--Milan 18:17, 9 January 2009 (NZDT)
Naming conventions
It would be nice to begin getting some naming conventions documented here.
- Preserving namespaces
When creating an article for something quite specific, like the kitchen of a particular Sanctuary, we wouldn't want to use a name like Kitchen because the Kitchen article should remain generic. This is the issue of needing to preserve namespaces. We could use a name like Swanson Sanctuary/Kitchen instead to denote the fact that we actually mean a specific kitchen. However, this can be quite unwieldy and leads to lots of repeated text. At the Mozilla Developer Centre they use a format which uses the abbreviation of the organisation's name, followed by a semicolon and the article name e.g. "MDC:Frequently Asked Questions". On Organic Design we have been using a slash to show that something is "under" a namespace as is the case with Identity/Summary. It still seems a good idea to abbreviate the organisation name, which would give us the format of SS/Kitchen.
- Categories
The SS/Kitchen article should be placed in the Category:Swanson Sanctuary, since it describes the kitchen "department" of the Swanson Sanctuary organisation as well as the Category:Kitchens, since it would presumably based on the template of Kitchen and and is an "instance" of "kitchen".
