About: PathfinderWiki talk:Manual of style

Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: PathfinderWiki talk:Manual of style Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

Hrm. Sooooo. This is a huge undertaking. I think we can do it but we should go over a few priorities first. Do we really need everything outlining all the grammar rules? Same applies for things like currencies, mathematical symbols, etc. Only those items which directly apply to Pathfinder canon are really relevant, and stylistic rules about extremely general stuff might also not be needed.

Attributes	Values
rdfs:label	PathfinderWiki talk:Manual of style
rdfs:comment	Hrm. Sooooo. This is a huge undertaking. I think we can do it but we should go over a few priorities first. Do we really need everything outlining all the grammar rules? Same applies for things like currencies, mathematical symbols, etc. Only those items which directly apply to Pathfinder canon are really relevant, and stylistic rules about extremely general stuff might also not be needed.
dbkwik:pathfinder/...iPageUsesTemplate	dbkwik:resource/ZDObki9pDJcOMtEe2oCxyQ==
abstract	Hrm. Sooooo. This is a huge undertaking. I think we can do it but we should go over a few priorities first. Do we really need everything outlining all the grammar rules? Same applies for things like currencies, mathematical symbols, etc. Only those items which directly apply to Pathfinder canon are really relevant, and stylistic rules about extremely general stuff might also not be needed. My suggestion is to take it one section at a time, denoting with tags or in the comments which subsection(s) were edited. Once we have them all covered, we can do overall passes to ensure consistency within the sections and to determine if they're all necessary in the first place. Another way to make it a bit more manageable is to hide sections that we aren't sure of, which will keep the page mostly clean and allow us to fine tune more troublesome sections without holding up the MoS on the whole. That said, I'm now realizing that we have said a lot of this stuff in the help section, namely in the style guides for individual types of pages. It's a much larger project, but combining and/or streamlining this MoS with those pages should be on the agenda, at least for some point in the future. -- yoda8myhead 02:28, 22 May 2009 (UTC) Our initial run-through of the MoS is complete and specific headers and subheaders have been marked in invisible notes by the chronicler who handled it. I am going to compile in-text discussion into an additional section here for discussion in an easy-to-find location. We should have it all wrapped up in the next day or so. I am also removing the WIP template from the top of the article, as visible signs of the work in progress should no longer exist. -- yoda8myhead 15:17, 26 May 2009 (UTC)

OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software