Difference between revisions of "BestPractices"
From Exalted - Unofficial Wiki
(Tempted to alter the subpages part) |
(Changing advice on subpages, some formatting) |
||
| Line 16: | Line 16: | ||
* back to UserPages. | * back to UserPages. | ||
* back to WikiContent. | * back to WikiContent. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[#WikiSpeak] | [#WikiSpeak] | ||
=== Basic Wikispeak === | === Basic Wikispeak === | ||
| − | * A | + | * A '''wikizen''' is a user of the wiki. |
| − | |||
| − | |||
| − | * When you | + | * When you change the contents of a page, it is called an '''edit'''; you can track the changes to a page by clicking on the "View other revisions" link at the bottom. (The records of changes are cleared out by the system after a certain amount of time has passed, although it tries to keep at least one old version on file; so, on older pages, you won't see the full record of changes.) |
| − | * | + | * When you click the "This change is a minor edit" box (located right above the "Save" button), it is called a '''minor edit'''. RecentChanges (linked at the bottom and top of every page), which tracks edits (and is therefore used by most wikizens to observe the status of the wiki), can be set by each wikizen to either log both minor edits and non-minor edits, or to only log non-minor edits. (This setting is located under the Preferences link, which is also at the bottom and top of every page.) Most wikizens set their preferences so that only non-minor edits are shown on their RecentChanges page. |
| − | * A | + | * A '''WikiWord''' is a word consisting of multiple capitalized words. WikiWords link themselves; you do not need to put double brackets (<code><nowiki>[[ ]]</nowiki></code>) around them in order to make them into links. We like them and encourage them here on ExaltedWiki. |
| − | * A | + | * A '''top-level page''' is a page whose name (the word that appears at the end of the URL that leads to it) has no slashes ("/"). Examples of top-level pages include BestPractices, [[Charms]], and [[Ikselam]]. |
| − | + | * A '''subpage''' is a page that is attached to a top-level page by means of a slash. When you put a word on a top-level page and begin it with a slash, then it becomes a subpage of that top-level page. For example, /PastComments is a subpage of BestPractices; its full name (the way it appears at the end of the URL that leads to it) is BestPractices/PastComments. Subpages are useful because they are indelibly attached to their parent page (for one thing, the parent page is linked at the bottom and top of every one of its subpages), so when you want to have a page that is permanently associated with a given top-level page, it helps to make it a subpage of that top-level page. (Note, however, that the previous comments give the incorrect impression that subpages work like file paths and are there to solve organizational problems. They are not. For one thing, there can only be one "level" of subpages. See below for more about how to use them.)<br><br>You refer to subpages for pages different from the one you are currently on by giving the full name in double brackets; e.g., if you are not on [[Ikselam]] or any of its subpages, then to refer to [[Ikselam/FanFiction]], you type <code><nowiki>[[Ikselam/FanFiction]]</nowiki></code>. (Note that you cannot have a subpage of a subpage. If you make a subpage on a subpage, then the new subpage will branch off from the parent subpage's parent page. So, for example, if Ikselam writes <code><nowiki>/PerfectCircle</nowiki></code> on his subpage [[Ikselam/OtherCircles]], then he will end up with [[Ikselam/PerfectCircle]], not <code><nowiki>Ikselam/OtherCircles/PerfectCircle</nowiki></code>.) | |
[#FormatRefs] | [#FormatRefs] | ||
| Line 47: | Line 37: | ||
You should also read TextFormattingRules, but here's a shortlist of the rules referred to on this page. | You should also read TextFormattingRules, but here's a shortlist of the rules referred to on this page. | ||
| − | * You | + | * You '''redirect''' to a page by placing <code><nowiki>#REDIRECT NewPageName</nowiki></code> on the redirecting page. A redirected page goes straight from the redirecting page to the target page. For example, [[Lexicon]] is not a page in itself; it redirects to LexiconOfElderDays because the only text on [[Lexicon]] is <code><nowiki>#REDIRECT LexiconOfElderDays</nowiki></code>. |
| − | * You | + | * You '''prettify''', or relabel, an interwiki link by putting it in square brackets with the label name after the page's name and a vertical divider in between, like so: <code><nowiki>[[LexiconOfElderDays | Lexicon Of Elder Days]]</nowiki></code> will display as [[LexiconOfElderDays | Lexicon Of Elder Days]]. |
[#Wikiquette] | [#Wikiquette] | ||
=== How to Be a Good Wikizen === | === How to Be a Good Wikizen === | ||
| − | * | + | * '''Put your name on your pages.''' This may seem self-evident, but you'd be surprised how often people forget. This is especially important if the page you are creating is not a subpage of your own UserPage. If you do not have some indication of authorship on your pages, people are less likely to comment. Furthermore, people might think that the page is a CommunalProject and that they can mess around with it at will. |
| − | * | + | * '''Log in before you edit anything.''' You can very easily do this by clicking on the Preferences link (located at the bottom and the top of every single Wiki page). You probably will only need to log in once. You can tell whether or not you are logged in when you are editing a page by looking to the right of the "Save" button. Logging in is a good thing to do, not only because it will save your username and preferences, but because it will label the edits you make using your username. If you haven't logged in, then, for example, if you edit someone else's page, they will not be able to tell who you are by looking at that page's history, and they will be sad and confused about who edited their page. Furthermore, if you don't log in and you make major edits, then the system will label your edits with your IP address instead; thus, your IP address will be splashed all over RecentChanges, which is not only annoying for those of us who use RecentChanges to track developments but will probably lead people to ignore your edits. If for some reason you can't log in, then at least note who you are in the "Summary" box. |
| − | * | + | * '''Don't make large content edits to other peoples' work without permission; also, sign your comments.''' In other words, it's fine to correct someone else's typos -- people might even like you for it -- but don't change, say, the mote cost of one of the Charms they've invented unless you know they're okay with you doing so. If you disagree with the way someone else created something, leave a comment at the bottom of the relevant page. And when you leave comments, don't forget to sign them. |
| − | * | + | * '''Save edits that are irrelevant to everyone else as "minor".''' Good examples of irrelevant edits include pages you are deleting (putting in a redirect will fit the bill so that you don't need everyone to know that you did it), extremely minor changes (fixing spelling errors or changing a couple of sentences on one of your own pages), adding pages to general indices (examples: adding an Artifact to the main [[Artifacts]] page, listing your name in a Contributor index), etc. It is nice to save these edits as minor, because, as previously noted, most wikizens use RecentChanges to track important content changes to ExaltedWiki, and most wikizens set their RecentChanges page to only register non-minor edits. So if you're making an edit that doesn't make the relevant page different enough to re-check or reread, then you don't need to inform people of it. In fact, it's kind of annoying if you do, because RecentChanges can get very crowded; also, it can be very irritating for wikizens to check a page that they think someone has made an important edit to, only to discover that no one made any important edits at all. |
| − | * | + | * '''Conversely, some edits really shouldn't be minor.''' Examples of edits that probably shouldn't be minor include especially large and complex edits to other peoples' pages (people want to know when you're making major changes to their stuff, even if it is just an enormous overhaul of their grammar and spelling) and comments on pages (people want to be able to track comments when they are made). |
| − | * | + | * '''Avoid spaces and underscores in page link names.''' For example, IkselamTheBrave is better than [[Ikselam The Brave]] (which was written as <code><nowiki>[[Ikselam The Brave]]</nowiki></code>) or [[Ikselam_The_Brave]] (which was written as <code><nowiki>[[Ikselam_The_Brave]]</nowiki></code>). WikiWord pages -- those whose links lack spaces or underscores -- are easier to type quickly and easier for others to find (because everyone assumes that a page name will be a WikiWord -- so if it isn't, they may not be able to find it without going on a giant hunt through WikiContent). |
| − | * | + | * '''Remember that you can prettify links that are WikiWords.''' If a WikiWord link bugs you, just relabel it so that the displayed link has spaces. For example, the markup <code><nowiki>[[FormatStandards][a page about formatting standards]]</nowiki></code> renders as: [[FormatStandards][a page about formatting standards]] |
| − | * | + | * '''When you are making a generic type of page, try to follow the FormatStandards for that type of page.''' The FormatStandards try to set out standards for each "type" of page. You don't have to follow the FormatStandards exactly -- for example, if you're making a page for a character, it isn't a big deal if you put the character's statistics at the end of the page rather than at the beginning, as suggested by FormatStandards. However, do be sure to include all the categories recommended by FormatStandards, and try to make it look enough like the FormatStandards that people can still recognize the page for what it is. |
| − | * | + | * '''Subpages are probably not what you think they are.''' A common misconception is that page names work like files in a directory and, therefore, subpages are a way to organize pages. This isn't really true. Instead, think of a page name as what it is: the ''unique identifier'' for that page. The use of subpages is really used more of a way to ''prevent collisions'' of names. For example, if both Bob and Dave want to create a page called <code>Artifacts</code>, how do they do this without colliding with the [[Artifacts]] page that already exists? Subpages are one solution to this problem of generating unique names. See the "What should I name a new page?" section of HowDoIDoThat for advice on naming pages. |
| − | + | * '''When you make a top-level page for one of your items, it is a good idea to include your name in the address of the page. It is also nice of you to avoid taking "generic" top-level page names.''' For example, if you are making new Solar Resistance Charms, don't make a page that you intend to be your own personal page and call it something generic like SolarResistance. IkselamSolarResistance, for example, is way better. This also applies to other pages. For example, if you have an artifact called FistOfDoom, and you think that it is appropriate for a top-level page, it'd be a good idea to put your name in the title, e.g., IkselamFistOfDoom. The reason that top-level pages are frequently best off having the author's name directly in the link is that if someone ever wants to do a communal or wide-ranging thing and they happen to want your top-level page, it sucks that you've banned them from using it by taking the top-level page for yourself. People also get confused about whether or not top-level pages are CommunalProjects, and that can lead to unfortunate editing behaviour. | |
| − | * | + | * '''Many wikizens prefer to place some or all of their content on subpages of their UserPage.''' For example, [[Ikselam]] keeps his FanFiction on [[Ikselam/FanFiction]]. This is not necessary, but it does have the advantage of immediately associating your name with the work on the page and making it obvious that the stuff on the page is not a CommunalProject. If you decide to keep your content on a subpage of your UserPage, then please keep in mind that if it is crunch (e.g. [[Artifacts]], [[Charms]]), then many people will seek it on subpages of the crunch pages. Thus, it is a good idea to also make a subpage of the relevant crunch page and use it to redirect to your content page. (For example, [[Shataina]] likes to keep her Artifacts on [[Shataina/Artifacts]], but she knows that some people will look for her Artifacts at [[Artifacts/Shataina]], so [[Artifacts/Shataina]] redirects to [[Shataina/Artifacts]].) |
| − | * | + | * '''If you are placing content on a subpage of your UserPage, you can give it a top-level alias.''' For example, [[Ikselam/MadTeaParty]] could have a top-level page, IkselamMadTeaParty or, if you insist, MadTeaParty, which redirects to it. If you insist on having top-level names for your pages without your name in them, then it's often nice to use the top-level alias to redirect to a page that better observes BestPractices so that if anyone eventually wants that top-level alias for something communal, you can easily give it to them without having to delete or reorganize all your stuff. |
| − | * | + | * '''The first time you try to create your own pages, ask for advice on naming.''' Almost every beginner on this wiki goes through a false start or two regarding what to name their pages. Before adding your first pages, you might want to post a comment to NamingAdvice for a "plan" on how to name them harmoniously with the rest of the wiki. |
[#Cautions] | [#Cautions] | ||
=== Cautions === | === Cautions === | ||
| − | * | + | * '''The login function under Preferences does not necessarily do what you think it does.''' You can log in under any name with any password, or even leave the password field blank. So, for example, [[Shataina]] could log in as [[Ikselam]] with any random password, and vice versa. The point of the password is to allow you to save your Preferences. When you set a password, your current Preference settings match up with the password, and that means that you can access them from anywhere without having to go through and reset them all again as long as you provide that password to the new location. |
| − | * | + | * '''Subpages are not "paths"; in other words, the wiki does not organize itself through paths the way your personal computer does.''' See SlashLinksAreNotPaths and the "What should I name a new page?" section of HowDoIDoThat for more on this. |
[#Comments] | [#Comments] | ||
| Line 95: | Line 85: | ||
I'm tempted to rewrite the section on subpages, for a couple of reasons. 1) The text doesn't really convey how the wiki now actually uses subpages these days. 2) All of its talk about "taxonomy" conveys the wrong message, making it seem like page names are intended to describe a category hierarchy "path". (These comments are also [[ReaderCentricDesign|provably wrong]], but that's sort of beside the point.) I think approach taken by the "What should I name a new page?" section of the HowDoIDoThat page is both more correct and less confusing. What do others think? - [[Wordman]] | I'm tempted to rewrite the section on subpages, for a couple of reasons. 1) The text doesn't really convey how the wiki now actually uses subpages these days. 2) All of its talk about "taxonomy" conveys the wrong message, making it seem like page names are intended to describe a category hierarchy "path". (These comments are also [[ReaderCentricDesign|provably wrong]], but that's sort of beside the point.) I think approach taken by the "What should I name a new page?" section of the HowDoIDoThat page is both more correct and less confusing. What do others think? - [[Wordman]] | ||
| + | |||
| + | Since no one commented on my previous comment over a year, I'm doing said changes. - [[Wordman]] | ||
Revision as of 16:05, 23 March 2009
Contents
General ExaltedWiki Guidelines
Ideally, wiki content should be structured in such a way that it is both intuitively organized, and easy to link to from other wiki pages. Also, people who use the wiki should be trying to keep the wiki easy for everyone else to use. Wiki etiquette is based around these two ideals, and this is a page about Wiki etiquette.
Following these guidelines may not elicit comment, but people do notice and appreciate it!
This is not a template page or a page about how to format text. TextFormattingRules should teach you the latter, and FormatStandards is an attempt to establish the former. This is basically an "advanced intro" page -- the purpose is to tell you how to behave like a good wikizen. If you still have questions after reading this, please feel free to leave a comment at the bottom or go over to WikiQuestions.
Obviously, on such an anarchist institution as a wiki, there's no way anyone can make you follow these guidelines; nor would we want to. These aren't "rules", in other words. But it's nice of you to follow these. Also, it's good for you, because people are an awful lot more likely to read your content and listen to your opinions if you do.
- back to QuickStartGuide.
- back to HowDoIDoThat.
- back to WhatIsAWiki.
- back to FormatStandards.
- back to TextFormattingRules.
- back to UserPages.
- back to WikiContent.
[#WikiSpeak]
Basic Wikispeak
- A wikizen is a user of the wiki.
- When you change the contents of a page, it is called an edit; you can track the changes to a page by clicking on the "View other revisions" link at the bottom. (The records of changes are cleared out by the system after a certain amount of time has passed, although it tries to keep at least one old version on file; so, on older pages, you won't see the full record of changes.)
- When you click the "This change is a minor edit" box (located right above the "Save" button), it is called a minor edit. RecentChanges (linked at the bottom and top of every page), which tracks edits (and is therefore used by most wikizens to observe the status of the wiki), can be set by each wikizen to either log both minor edits and non-minor edits, or to only log non-minor edits. (This setting is located under the Preferences link, which is also at the bottom and top of every page.) Most wikizens set their preferences so that only non-minor edits are shown on their RecentChanges page.
- A WikiWord is a word consisting of multiple capitalized words. WikiWords link themselves; you do not need to put double brackets (
[[ ]]) around them in order to make them into links. We like them and encourage them here on ExaltedWiki.
- A top-level page is a page whose name (the word that appears at the end of the URL that leads to it) has no slashes ("/"). Examples of top-level pages include BestPractices, Charms, and Ikselam.
- A subpage is a page that is attached to a top-level page by means of a slash. When you put a word on a top-level page and begin it with a slash, then it becomes a subpage of that top-level page. For example, /PastComments is a subpage of BestPractices; its full name (the way it appears at the end of the URL that leads to it) is BestPractices/PastComments. Subpages are useful because they are indelibly attached to their parent page (for one thing, the parent page is linked at the bottom and top of every one of its subpages), so when you want to have a page that is permanently associated with a given top-level page, it helps to make it a subpage of that top-level page. (Note, however, that the previous comments give the incorrect impression that subpages work like file paths and are there to solve organizational problems. They are not. For one thing, there can only be one "level" of subpages. See below for more about how to use them.)
You refer to subpages for pages different from the one you are currently on by giving the full name in double brackets; e.g., if you are not on Ikselam or any of its subpages, then to refer to Ikselam/FanFiction, you type[[Ikselam/FanFiction]]. (Note that you cannot have a subpage of a subpage. If you make a subpage on a subpage, then the new subpage will branch off from the parent subpage's parent page. So, for example, if Ikselam writes/PerfectCircleon his subpage Ikselam/OtherCircles, then he will end up with Ikselam/PerfectCircle, notIkselam/OtherCircles/PerfectCircle.)
[#FormatRefs]
Formatting Rules Referenced Here
You should also read TextFormattingRules, but here's a shortlist of the rules referred to on this page.
- You redirect to a page by placing
#REDIRECT NewPageNameon the redirecting page. A redirected page goes straight from the redirecting page to the target page. For example, Lexicon is not a page in itself; it redirects to LexiconOfElderDays because the only text on Lexicon is#REDIRECT LexiconOfElderDays.
- You prettify, or relabel, an interwiki link by putting it in square brackets with the label name after the page's name and a vertical divider in between, like so:
[[LexiconOfElderDays | Lexicon Of Elder Days]]will display as Lexicon Of Elder Days.
[#Wikiquette]
How to Be a Good Wikizen
- Put your name on your pages. This may seem self-evident, but you'd be surprised how often people forget. This is especially important if the page you are creating is not a subpage of your own UserPage. If you do not have some indication of authorship on your pages, people are less likely to comment. Furthermore, people might think that the page is a CommunalProject and that they can mess around with it at will.
- Log in before you edit anything. You can very easily do this by clicking on the Preferences link (located at the bottom and the top of every single Wiki page). You probably will only need to log in once. You can tell whether or not you are logged in when you are editing a page by looking to the right of the "Save" button. Logging in is a good thing to do, not only because it will save your username and preferences, but because it will label the edits you make using your username. If you haven't logged in, then, for example, if you edit someone else's page, they will not be able to tell who you are by looking at that page's history, and they will be sad and confused about who edited their page. Furthermore, if you don't log in and you make major edits, then the system will label your edits with your IP address instead; thus, your IP address will be splashed all over RecentChanges, which is not only annoying for those of us who use RecentChanges to track developments but will probably lead people to ignore your edits. If for some reason you can't log in, then at least note who you are in the "Summary" box.
- Don't make large content edits to other peoples' work without permission; also, sign your comments. In other words, it's fine to correct someone else's typos -- people might even like you for it -- but don't change, say, the mote cost of one of the Charms they've invented unless you know they're okay with you doing so. If you disagree with the way someone else created something, leave a comment at the bottom of the relevant page. And when you leave comments, don't forget to sign them.
- Save edits that are irrelevant to everyone else as "minor". Good examples of irrelevant edits include pages you are deleting (putting in a redirect will fit the bill so that you don't need everyone to know that you did it), extremely minor changes (fixing spelling errors or changing a couple of sentences on one of your own pages), adding pages to general indices (examples: adding an Artifact to the main Artifacts page, listing your name in a Contributor index), etc. It is nice to save these edits as minor, because, as previously noted, most wikizens use RecentChanges to track important content changes to ExaltedWiki, and most wikizens set their RecentChanges page to only register non-minor edits. So if you're making an edit that doesn't make the relevant page different enough to re-check or reread, then you don't need to inform people of it. In fact, it's kind of annoying if you do, because RecentChanges can get very crowded; also, it can be very irritating for wikizens to check a page that they think someone has made an important edit to, only to discover that no one made any important edits at all.
- Conversely, some edits really shouldn't be minor. Examples of edits that probably shouldn't be minor include especially large and complex edits to other peoples' pages (people want to know when you're making major changes to their stuff, even if it is just an enormous overhaul of their grammar and spelling) and comments on pages (people want to be able to track comments when they are made).
- Avoid spaces and underscores in page link names. For example, IkselamTheBrave is better than Ikselam The Brave (which was written as
[[Ikselam The Brave]]) or Ikselam_The_Brave (which was written as[[Ikselam_The_Brave]]). WikiWord pages -- those whose links lack spaces or underscores -- are easier to type quickly and easier for others to find (because everyone assumes that a page name will be a WikiWord -- so if it isn't, they may not be able to find it without going on a giant hunt through WikiContent).
- Remember that you can prettify links that are WikiWords. If a WikiWord link bugs you, just relabel it so that the displayed link has spaces. For example, the markup
[[FormatStandards][a page about formatting standards]]renders as: [[FormatStandards][a page about formatting standards]]
- When you are making a generic type of page, try to follow the FormatStandards for that type of page. The FormatStandards try to set out standards for each "type" of page. You don't have to follow the FormatStandards exactly -- for example, if you're making a page for a character, it isn't a big deal if you put the character's statistics at the end of the page rather than at the beginning, as suggested by FormatStandards. However, do be sure to include all the categories recommended by FormatStandards, and try to make it look enough like the FormatStandards that people can still recognize the page for what it is.
- Subpages are probably not what you think they are. A common misconception is that page names work like files in a directory and, therefore, subpages are a way to organize pages. This isn't really true. Instead, think of a page name as what it is: the unique identifier for that page. The use of subpages is really used more of a way to prevent collisions of names. For example, if both Bob and Dave want to create a page called
Artifacts, how do they do this without colliding with the Artifacts page that already exists? Subpages are one solution to this problem of generating unique names. See the "What should I name a new page?" section of HowDoIDoThat for advice on naming pages.
- When you make a top-level page for one of your items, it is a good idea to include your name in the address of the page. It is also nice of you to avoid taking "generic" top-level page names. For example, if you are making new Solar Resistance Charms, don't make a page that you intend to be your own personal page and call it something generic like SolarResistance. IkselamSolarResistance, for example, is way better. This also applies to other pages. For example, if you have an artifact called FistOfDoom, and you think that it is appropriate for a top-level page, it'd be a good idea to put your name in the title, e.g., IkselamFistOfDoom. The reason that top-level pages are frequently best off having the author's name directly in the link is that if someone ever wants to do a communal or wide-ranging thing and they happen to want your top-level page, it sucks that you've banned them from using it by taking the top-level page for yourself. People also get confused about whether or not top-level pages are CommunalProjects, and that can lead to unfortunate editing behaviour.
- Many wikizens prefer to place some or all of their content on subpages of their UserPage. For example, Ikselam keeps his FanFiction on Ikselam/FanFiction. This is not necessary, but it does have the advantage of immediately associating your name with the work on the page and making it obvious that the stuff on the page is not a CommunalProject. If you decide to keep your content on a subpage of your UserPage, then please keep in mind that if it is crunch (e.g. Artifacts, Charms), then many people will seek it on subpages of the crunch pages. Thus, it is a good idea to also make a subpage of the relevant crunch page and use it to redirect to your content page. (For example, Shataina likes to keep her Artifacts on Shataina/Artifacts, but she knows that some people will look for her Artifacts at Artifacts/Shataina, so Artifacts/Shataina redirects to Shataina/Artifacts.)
- If you are placing content on a subpage of your UserPage, you can give it a top-level alias. For example, Ikselam/MadTeaParty could have a top-level page, IkselamMadTeaParty or, if you insist, MadTeaParty, which redirects to it. If you insist on having top-level names for your pages without your name in them, then it's often nice to use the top-level alias to redirect to a page that better observes BestPractices so that if anyone eventually wants that top-level alias for something communal, you can easily give it to them without having to delete or reorganize all your stuff.
- The first time you try to create your own pages, ask for advice on naming. Almost every beginner on this wiki goes through a false start or two regarding what to name their pages. Before adding your first pages, you might want to post a comment to NamingAdvice for a "plan" on how to name them harmoniously with the rest of the wiki.
[#Cautions]
Cautions
- The login function under Preferences does not necessarily do what you think it does. You can log in under any name with any password, or even leave the password field blank. So, for example, Shataina could log in as Ikselam with any random password, and vice versa. The point of the password is to allow you to save your Preferences. When you set a password, your current Preference settings match up with the password, and that means that you can access them from anywhere without having to go through and reset them all again as long as you provide that password to the new location.
- Subpages are not "paths"; in other words, the wiki does not organize itself through paths the way your personal computer does. See SlashLinksAreNotPaths and the "What should I name a new page?" section of HowDoIDoThat for more on this.
[#Comments]
Comments
Past comments for this page are available at /PastComments. (Last archived: 11.15.04 by Shataina)
Well, here's the deal with this page. The excellent Ikselam originally wrote it because he was trying to get his ideas about subpages down, but I didn't realize that when I first found it; I thought it was intended to be a kind of guide for how to work with pages as a polite wikizen, and I thought it was incomplete, so I soon edited the hell out of it and then added a bunch of new stuff. (Delayed apologies, Ikselam.) (See, this is an example as to why you should put very obvious and clear indication of authorship on pages.) As such, this page is a work in progress that originally came from a page that was made for a totally different reason, so I apologize for places where it is unclear to the new wikizen. I've done my best, but I use this wiki way too much and even though I'm comparatively new (or at least I feel new compared to people like Ikselam), I'm still accustomed enough to using the site that I occasionally fail to make things clear (because I'm so used to them). If you're new, and are confused about any of the statements on this page, please leave a comment and I'll try to make it so obvious that you feel horribly patronized. <grin>
~ Shataina
I'm tempted to rewrite the section on subpages, for a couple of reasons. 1) The text doesn't really convey how the wiki now actually uses subpages these days. 2) All of its talk about "taxonomy" conveys the wrong message, making it seem like page names are intended to describe a category hierarchy "path". (These comments are also provably wrong, but that's sort of beside the point.) I think approach taken by the "What should I name a new page?" section of the HowDoIDoThat page is both more correct and less confusing. What do others think? - Wordman
Since no one commented on my previous comment over a year, I'm doing said changes. - Wordman
