Pathfinder Online Wiki
Log in

Difference between revisions of "User talk:NytCrawlr"

From Pathfinder Online Wiki
← $1
Line 8: Line 8:
  
 
-- Nope, your template was perfect IMO, in fact I was going to copy the basics of it and modify for other areas. [[User:Nihimon|Nihimon]] just wanted a normal page, with no templates, done to each type of feat, minus expendables, to get an idea purely of structure, for temporary purposes. Once he is done incorporating all the data into the wiki, we are going to go back and start using templates to present it. I know this is a different way of doing things, but I have faith that what he is doing will make things a lot easier, once he's done, on updating any changes, etc. —[[User:NytCrawlr|NytCrawlr]] ([[User talk:NytCrawlr|talk]]) 21:31, 7 September 2014 (UTC)
 
-- Nope, your template was perfect IMO, in fact I was going to copy the basics of it and modify for other areas. [[User:Nihimon|Nihimon]] just wanted a normal page, with no templates, done to each type of feat, minus expendables, to get an idea purely of structure, for temporary purposes. Once he is done incorporating all the data into the wiki, we are going to go back and start using templates to present it. I know this is a different way of doing things, but I have faith that what he is doing will make things a lot easier, once he's done, on updating any changes, etc. —[[User:NytCrawlr|NytCrawlr]] ([[User talk:NytCrawlr|talk]]) 21:31, 7 September 2014 (UTC)
 +
 +
== Categories ==
 +
I see you're starting the framework for a category tree, and wanted to point out a few best practices we learned on the main wiki.
 +
 +
First, try not to place categories within their own subcategories. It just gets confusing. Ever category an article or category belongs to should be a group to which it belongs (I know that's circular logic). For example:
 +
 +
: The Major Armor Keyword, "[[Masterwork]]", belongs to the following sets:
 +
* Major Armor Keywords
 +
* Major Keywords
 +
* Armor Keywords
 +
* Keywords
 +
 +
Each of those sets in turn belongs to other sets.
 +
 +
: Major Armor Keywords belongs to the following sets:
 +
* Major Keywords
 +
* Armor Keywords
 +
::Note that it doesn't belong to Keywords, because someone in the Keywords category page can navigate to this set via either of the two paths above.
 +
 +
: Major Keywords belongs to the following set:
 +
* Keywords
 +
:: It doesn't belong to the other two because not all Major Keywords are Armor Keywords, nor are they all Major Armor Keywords
 +
 +
: Armor Keywords belongs to the following set:
 +
* Keywords
 +
:: Again, because not all Armor Keywords Are Major Armor Keywords, nor are they all Major Keywords.
 +
 +
: Finally, Keywords belongs in a larger root category, which I've named Mechanics.
 +
 +
When placing articles in categories, think whether or not it should be alphabetized in the category list. The article, [[Keywords]], shouldn't really appear buried in the Ks when someone is looking at [[:Category:Keywords]]—it should stand alone and come before A. But within [[:Category:Mechanics]], it can totally be alphabetized under K, because there will also be articles in that category for Feats, Weapons, Armors, Recipes, Escalation Cycles, etc.
 +
 +
To set a different term by which to organize a page or subcategory within a parent category, simply add a pipe and the name you want it sorted under. If you want it sorted before the "A" header, leave a space immediately after the pipe, before the name you want it alphabetized by there.
 +
 +
I also suggest that, instead of category names like [[:Category:Major Keywords - Armor]], you place the words in an order that will them stand out from one another in alphabetized lists. "Major Armor Keywords" is easier to read to someone actually perusing the category tree, while "Armor Keywords (Major)" is going to default to better alphabetization. Something to consider.
 +
 +
Let me know if you have any questions, as setting up clear and clean category trees at the beginning of a project is MUCH easier than trying to recategorize hundreds or thousands of articles and categories later on. —[[File:Paizo_Publishing, LLC.png|16px]] [[User:Yoda8myhead|Yoda8myhead]] ([[User talk:Yoda8myhead|talk]]) 22:29, 13 September 2014 (UTC)

Revision as of 22:29, 13 September 2014

Welcome to Pathfinder Online Wiki! We hope you will contribute much and well. You will probably want to read the help pages. Again, welcome and have fun! Paizo Publishing, LLC.png Yoda8myhead (talk) 02:55, 20 August 2014 (UTC)

Crusader

I think you're going to find that you want to use a template to automatically fill that page. Formatting it with <br /> instead of hard line breaks will also keep the individual bulleted lines much closer together. Was there a particular reason you didn't want to continue using the template I put together? The formatting could easily be incorporated with the nested data templates Nihimon has been perfecting. —Paizo Publishing, LLC.png Yoda8myhead (talk) 23:37, 29 August 2014 (UTC)

-- Nope, your template was perfect IMO, in fact I was going to copy the basics of it and modify for other areas. Nihimon just wanted a normal page, with no templates, done to each type of feat, minus expendables, to get an idea purely of structure, for temporary purposes. Once he is done incorporating all the data into the wiki, we are going to go back and start using templates to present it. I know this is a different way of doing things, but I have faith that what he is doing will make things a lot easier, once he's done, on updating any changes, etc. —NytCrawlr (talk) 21:31, 7 September 2014 (UTC)

Categories

I see you're starting the framework for a category tree, and wanted to point out a few best practices we learned on the main wiki.

First, try not to place categories within their own subcategories. It just gets confusing. Ever category an article or category belongs to should be a group to which it belongs (I know that's circular logic). For example:

The Major Armor Keyword, "Masterwork", belongs to the following sets:
  • Major Armor Keywords
  • Major Keywords
  • Armor Keywords
  • Keywords

Each of those sets in turn belongs to other sets.

Major Armor Keywords belongs to the following sets:
  • Major Keywords
  • Armor Keywords
Note that it doesn't belong to Keywords, because someone in the Keywords category page can navigate to this set via either of the two paths above.
Major Keywords belongs to the following set:
  • Keywords
It doesn't belong to the other two because not all Major Keywords are Armor Keywords, nor are they all Major Armor Keywords
Armor Keywords belongs to the following set:
  • Keywords
Again, because not all Armor Keywords Are Major Armor Keywords, nor are they all Major Keywords.
Finally, Keywords belongs in a larger root category, which I've named Mechanics.

When placing articles in categories, think whether or not it should be alphabetized in the category list. The article, Keywords, shouldn't really appear buried in the Ks when someone is looking at Category:Keywords—it should stand alone and come before A. But within Category:Mechanics, it can totally be alphabetized under K, because there will also be articles in that category for Feats, Weapons, Armors, Recipes, Escalation Cycles, etc.

To set a different term by which to organize a page or subcategory within a parent category, simply add a pipe and the name you want it sorted under. If you want it sorted before the "A" header, leave a space immediately after the pipe, before the name you want it alphabetized by there.

I also suggest that, instead of category names like Category:Major Keywords - Armor, you place the words in an order that will them stand out from one another in alphabetized lists. "Major Armor Keywords" is easier to read to someone actually perusing the category tree, while "Armor Keywords (Major)" is going to default to better alphabetization. Something to consider.

Let me know if you have any questions, as setting up clear and clean category trees at the beginning of a project is MUCH easier than trying to recategorize hundreds or thousands of articles and categories later on. —Paizo Publishing, LLC.png Yoda8myhead (talk) 22:29, 13 September 2014 (UTC)