Difference between revisions of "Help:Contents"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
# ''Outcome or result'' is a category that describes a desired outcome for which a transit agency would employ strategies. Content at this level has at least one parent and two children. While content at this level will usually take the form of a category, it can take the form of a page if the content for none of the children strategies is (or is anticipated to be) long enough to warrant its own strategy page. | # ''Outcome or result'' is a category that describes a desired outcome for which a transit agency would employ strategies. Content at this level has at least one parent and two children. While content at this level will usually take the form of a category, it can take the form of a page if the content for none of the children strategies is (or is anticipated to be) long enough to warrant its own strategy page. | ||
# ''Strategy'' - a strategy usually takes the form of a page. This page includes: | # ''Strategy'' - a strategy usually takes the form of a page. This page includes: | ||
| − | + | ##an introduction to the concept covered in the page that gives the intelligent but unfamiliar reader context | |
| − | + | ##an overview of the benefits and drawbacks involved with pursuing the strategy, including how the strategy can help an agency in pursuit of any desired ##parent ''outcome or result'' , but also any adverse effects the strategy may have on other strategies, aspects of transit service delivery, or stakeholders | |
| − | + | ##examples of the strategy in action | |
| − | + | ##further reading for those interested in learning more, including academic literature and case studies, with link to content or DOI/library page. Each item linked in further reading should include at a minimum of two sentences that inform the reader's decision to follow or not follow the link. | |
# ''Sub-page'' - When some content provided on a ''strategy'' page would be too narrowly-focused or detailed for the typical reader, this additional information should be linked in a sub-page. A ''sub-page'' differs from a ''strategy'' page in that it is not a strategy in-and-of itself (and therefore does not have a <nowiki>[[category:whatever]]</nowiki> tag, and it usually only linked by a parent page. | # ''Sub-page'' - When some content provided on a ''strategy'' page would be too narrowly-focused or detailed for the typical reader, this additional information should be linked in a sub-page. A ''sub-page'' differs from a ''strategy'' page in that it is not a strategy in-and-of itself (and therefore does not have a <nowiki>[[category:whatever]]</nowiki> tag, and it usually only linked by a parent page. | ||
Revision as of 19:00, 14 February 2012
About categories & pages
Relationships
The relationships between categories and pages provide some structure for content in the Wiki, which will be useful as the Wiki matures with more content, or becomes a repository for additional research projects. The typical relationship between categories or categories and pages is a parent-child relationship, although in some instances a page or category will have multiple parents. A parent is a page or category with at least one child. A child is a page or category that includes the [[Category:something]] tag. Below is an explanation of the relationship between different levels of content.
- Group of categories (eg: Internal strategies, External strategies). These are top-level groupings, and for this project these categories have no parents. This level can be thought of as Parts of a report.
- Category - items at this second level have a parent (a level 1 group of categories) and at least two "children" outcome (eg: Operations planning)
- Outcome or result is a category that describes a desired outcome for which a transit agency would employ strategies. Content at this level has at least one parent and two children. While content at this level will usually take the form of a category, it can take the form of a page if the content for none of the children strategies is (or is anticipated to be) long enough to warrant its own strategy page.
- Strategy - a strategy usually takes the form of a page. This page includes:
- an introduction to the concept covered in the page that gives the intelligent but unfamiliar reader context
- an overview of the benefits and drawbacks involved with pursuing the strategy, including how the strategy can help an agency in pursuit of any desired ##parent outcome or result , but also any adverse effects the strategy may have on other strategies, aspects of transit service delivery, or stakeholders
- examples of the strategy in action
- further reading for those interested in learning more, including academic literature and case studies, with link to content or DOI/library page. Each item linked in further reading should include at a minimum of two sentences that inform the reader's decision to follow or not follow the link.
- Sub-page - When some content provided on a strategy page would be too narrowly-focused or detailed for the typical reader, this additional information should be linked in a sub-page. A sub-page differs from a strategy page in that it is not a strategy in-and-of itself (and therefore does not have a [[category:whatever]] tag, and it usually only linked by a parent page.
Page titles
Please
- use active voice
- use simple language
- avoid prepositions
- avoid redundancy when possible (eg: transit, bus, rail)