Editing
Site Organization
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
= Site Organization = Content is organized as a shallow hierarchy, moving from broad generalized domains of organizational concern to operational areas within a domain (and potentially, an intervening sub-area) – all the way down to the level of individual tools (one per page). * ''Domain →'' ** ''Operational Area →'' *** ''Operational Sub-area →'' **** ''Task →'' ***** ''Candidate Tool'' <span id="relations-to-wiki-categories"></span> === Relations to Wiki Categories === In Wiki-speak each of these levels is simply a [https://en.wikipedia.org/wiki/Wikipedia:Contents/Categories ''page'' ''category'']. The left-hand navigation panel mirrors this category hierarchy. Top-level entries — such as ''Operations'' or ''Communications'' — link to domain-level Wiki category pages and are maintained by our site administrators. Below the ''domain'' level (i.e., below the ''top level''), categories can be added by any site user as needed (but note site admins might roll your proposed category into an existing one or rename it.) To assign a page to a category, place the following tag near the bottom of the page’s wikitext, replacing <code>CategoryName</code> with the exact category name (spaces allowed; case-sensitive): <nowiki>[[Category:CategoryName]]</nowiki> A page can belong to more than one category — add one tag per line. The New Submission form handles this automatically via the ''Category'' tree selector. <span id="guidelines-for-new-category-additions"></span> === Guidelines for New Category Additions === <span id="short-names"></span> ==== Short Names ==== Keep the name under three words (ideally two, as the side panel nav tree might start word wrapping or exhibiting other rendering issues.) <span id="check-for-dups"></span> ==== Check for Dups ==== Verify there is no similar category before you add a new one. <span id="task-level-category-rules"></span> ==== Task Level Category Rules ==== Each ''Task'' should be a short phrase indicating a concrete action undertaken by technicians in service of either special projects, or ongoing operations. Tasks can be associated with more than one recommended tool. On any tool page we might have optional discussion of why that tool was selected over rejected alternatives, together with a discussion of those alternatives. But as soon as we start accumulating more than one viable candidate for a task, each one should not only get its own page. But we should create a page ‘Rejected Alternatives’ at the level of the immediate parent Task of the page that is now joined by its new sibling pages. [[Category:Meta]]
Summary:
Please note that all contributions to Doikayt Field Guide are considered to be released under the Creative Commons Attribution (see
DoikaytFieldGuide:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
associated-pages
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
About this wiki
Evaluation criteria used across this wiki
New Submission
Tools
What links here
Related changes
Page information
Cargo data
Categories
Communications
Internal Comms
Outbound Comms
Operations
Finance&Accounting
Project Management
Self Hosting