I know we thoroughly documented the categories structure and guidelines, but I can't find them where they are supposed to be. So I fixed it on the following pages:<br><br><a href="http://codex.wordpress.org/Codex:Guidelines#Codex_Categories">http://codex.wordpress.org/Codex:Guidelines#Codex_Categories</a><br>
<br><a href="http://codex.wordpress.org/Help:Editing#Categories">http://codex.wordpress.org/Help:Editing#Categories</a><br><br><a href="http://codex.wordpress.org/Codex:Maintenance">http://codex.wordpress.org/Codex:Maintenance</a><br>
<br>I also spent some time going over the <a href="http://codex.wordpress.org/Special:Categories">http://codex.wordpress.org/Special:Categories</a> list and wanted to cry - the same emotion I feel every time I go to that page and find that all our beautiful work has been mangled again.<br>
<br>Here are the conventions and we need folks to start digging in and fixing these.<br><br>1. All categories must have Capital Letters not lower case as MediaWiki treats "WordPress Lessons" and "wordpress lessons" and "WordPress lessons" as three different pages. All pages with the lower case versions must have their categories changed to the appropriate cap version.<br>
<br>2. All foreign language pages must be categorized with their proper foreign category name, with the two letter language code in front of the category name, per the example in the Guidelines. The only exception is the country or language specific main category. <br>
<br>This two prong system does two important things. First, it groups all content into a specific "Codex section" for that language and second, it puts all language specific content in that language code. So if you click the French Codex category, you will find all the documents in French. If you click the fr:Panneaux_Administration, you will find all the articles about the Administration Panels in French. If you don't speak the language, at least try to recognize the language enough to get it in the right Codex language section to help out those volunteers.<br>
<br>3. Keep Categories SPECIFIC and matched to the Table of Contents and WordPress features. As outlined in the guidelines, the categories need to be in keeping with the current table of contents as much as possible. I'm working on a total restructing of the table of contents, but keep finding myself distracted with the never ending clean up of content, so your help in grouping things by category and cleaning as you go will help the TOC efforts dramatically. I'd love to find a way to do all our TOC by categories automatically. Still hunting for a MediaWiki solution - hint hint!<br>
<br>4. Fear NOT Overcategorization: For right now, I'd rather see the content in many related categories rather than only a few. Use your best judgment, and be specific, but let's make sure we help users find the information without being overwhelmed. Check a category to see if it is appropriate, as well as overloaded or not, if it helps you to decide where a document should be placed.<br>
<br>5. Categorize the Uncategorized: Check <a href="http://codex.wordpress.org/Category:Uncategorized">http://codex.wordpress.org/Category:Uncategorized</a> for uncategorized content and start categorizing. <br><br>6. Check each category in the <a href="http://codex.wordpress.org/Special:Categories">http://codex.wordpress.org/Special:Categories</a> to ensure the articles within it are categorized appropriately. <br>
<br>7. Why not add category links when appropriate within the content? To make a link in the content to a category, use a colon in front of the word "Category" such as [[:Category:WordPress_Lessons|WordPress Lessons category]] to guide people to related content. <br>
<br>And please tell me who to shoot that came up with UI Link as a category name. Do not make me tell you why it sucks as a category name. There are 56 pages that have to be changed to something more appropriate like Administration Panels. SIGH.<br>
<br>Once we've moved all the inappropriate categories to proper categories (you should be able to tell the diff, such as wrongly capped categories and bad category names), and they read zero members, let me know and I'll delete them. We don't need to do redirects on any of those as I don't think many are linking to categories. I'll check for backlinks before deleting them. <br>
<br>This can be part of the boring work of volunteering on the Codex, but it is the most important work, too. The better we can categorize the content, the better we can help users find the information they need. <br><br>
Once we get these cleaned up, I'll also make a category "cloud" unless we can find an add-on or extension that will do that automatically. There must be auto things like this by now, isn't there? <br><br>
RED LINKS<br>I've just noticed that the red links indicative of a page with no content aren't working. HOW did I miss THAT? I've asked that the red link style be added back to help us find the links to pages without content so we can fix that. <br>
<br>SNARK ALERT<br>While going through some of the documents to write the guidelines and check out the categories, I found some snarky comments in the docs. They are subtle but there. Pay close attention to any snarky comments and help clean those out, please, if you find them.<br>
<br>They are usually things phrased like, "If you want a better way to do this, see this..." leading to an external link, or "..but it doesn't always work" which isn't helpful nor informative since there isn't an explanation as to why or alternatives. These are just subtle "editorial comments" but also look out for snark comments that are more accusatory. The WordPress Codex is pretty strict on the editorial guidelines keeping the "I" out of the documentation and being neutral but enthusiastic in tone, so help us keep any little snarky commentaries out. Thanks.<br>
<br>Thanks to all! And thanks for cacthing this issue about the lack of category guidelines. I am sure that MichaelH and the rest of the team came up with those a few years ago. We worked so hard on setting up the categories in the first place. Odd. So thanks for noticing. <br>
<br>Lorelle VanFossen<br><br><br>On Wed, Jul 8, 2009 at 11:34 AM, Charles E. Frees-Melvin <<a href="mailto:charles@cefm.ca">charles@cefm.ca</a>> wrote:<br>><br>> The search is not great, or should I say the search in the theme. If you know mediawiki and can get to it's search page it's 6000% better.<br>
><br>> ---<br>><br>> Sent from my iPhone<br>><br>> On 2009-07-08, at 15:10, Will Kemp <Will@Swaggie.net> wrote:<br>><br>>> On 07/08/2009 06:25 PM, Lorelle VanFossen wrote:<br>>>><br>
>>> As everyone has said, welcome to the Codex and WordPress Documentation Team.<br>>><br>>> Thanks.<br>>><br>>>> Be sure and check out the guidelines for editing and working with the<br>
>>> Codex under the Community Portal. These will help you figure out how it<br>>>> all works.<br>>><br>>> That was the first thing i did!<br>>><br>>>> * Ensure EVERY page on the Codex has the proper Category at the bottom<br>
>>> of each page. A page can be in more than one category, but we have to be<br>>>> REALLY specific about categorizing the documents.<br>>><br>>> Are there any category guidelines anywhere? I've looked, but i haven't found it.<br>
>><br>>> I'm happy to spend as much time as i can going through the codex and categorizing articles. It will be a good way to get to know what's in there, anyway.<br>>><br>>>> A document on Plugins<br>
>>> should go in the Plugins category, but if it is really basic, it should<br>>>> also go in WordPress Lessons, but if complicated and very "developer"<br>>>> then it also needs a cross reference in the Developer category, right?<br>
>>> It's a tough call sometimes but think about how the user will hunt for<br>>>> the information and sort accordingly.<br>>><br>>> For development type subjects, at least, i think the categories may need to be more fine grained than that if they're going to be really useful.<br>
>><br>>>> * Foreign Language articles - We need to put the articles in different<br>>>> languages into their own language specific categories. That will help<br>>>> get those articles into their own grouping, and help us get that<br>
>>> information to the people who need it.<br>>><br>>> If non-English languages are going to be in their own categories, surely English language articles need to be categorized "English"? Maybe i've missed something, but that doesn't appear to be happening.<br>
>><br>>>> Check the categorization and<br>>>> language guidelines for how to categorized those.<br>>><br>>> Where are they? (Is it just me that can't find anything in this wiki?)<br>
>><br>>> Will<br>>> _______________________________________________<br>>> wp-docs mailing list<br>>> wp-docs@lists.automattic.comI know we thoroughly documented the categories structure and
guidelines, but I can't find them where they are supposed to be. So I
fixed it on the following pages:<br>
<br>
<a href="http://codex.wordpress.org/Codex:Guidelines#Codex_Categories">http://codex.wordpress.org/Codex:Guidelines#Codex_Categories</a><br>
<br>
<a href="http://codex.wordpress.org/Help:Editing#Categories">http://codex.wordpress.org/Help:Editing#Categories</a><br>
<br>
<a href="http://codex.wordpress.org/Codex:Maintenance">http://codex.wordpress.org/Codex:Maintenance</a><br>
<br>
I also spent some time going over the
<a href="http://codex.wordpress.org/Special:Categories">http://codex.wordpress.org/Special:Categories</a> list and wanted to cry -
the same emotion I feel every time I go to that page and find that all
our beautiful work has been mangled again.<br>
<br>
Here are the conventions and we need folks to start digging in and fixing these.<br>
<br>
1. All categories must have Capital Letters not lower case as MediaWiki
treats "WordPress Lessons" and "wordpress lessons" and "WordPress
lessons" as three different pages. All pages with the lower case
versions must have their categories changed to the cap version.<br>
<br>
2. All foreign language pages must be categorized with their proper
foreign category name, with the two letter language code in front of
the category name, per the example in the Guidelines. The only
exception is the country or language specific main category. That does
two important things. First, it groups all content into a specific
"Codex section" for that language and second, it puts all language
specific content in that language code. So if you click the French
Codex category, you will find all the documents in French. If you click
the fr:Panneaux_Administration, you will find all the articles about
the Administration Panels in French. If you don't speak the language,
at least try to recognize the language enough to get it in the right
Codex language section to help out those volunteers.<br>
<br>
3. Keep Categories SPECIFIC and matched to the Table of Contents and
WordPress features. As outlined in the guidelines, the categories need
to be in keeping with the current table of contents as much as
possible. I'm working on a total restructing of the table of contents,
but keep finding myself distracted with the never ending clean up of
content, so your help in grouping things by category and cleaning as
you go will help the TOC efforts dramatically. <br>
<br>
4. Fear NOT Overcategorization: For right now, I'd rather see the
content in many related categories rather than only a few. Use your
best judgment, and be specific, but let's make sure we help users find
the information without being overwhelmed. Check a category to see if
it is appropriate, as well as overloaded or not, if it helps you to
decide where a document should be placed. <br>
<br>
5. Categorize the Uncategorized: Check <a href="http://codex.wordpress.org/Category">http://codex.wordpress.org/Category</a>:<em>Uncategorized for </em><br>
<br clear="all">Lorelle VanFossen<br>
<br><br><div class="gmail_quote">On Wed, Jul 8, 2009 at 11:34 AM, Charles E. Frees-Melvin <span dir="ltr"><<a href="mailto:charles@cefm.ca">charles@cefm.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The
search is not great, or should I say the search in the theme. If you
know mediawiki and can get to it's search page it's 6000% better.<br>
<br>
---<br>
<br>
Sent from my iPhone<div><div class="h5"><br>
<br>
On 2009-07-08, at 15:10, Will Kemp <Will@Swaggie.net> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 07/08/2009 06:25 PM, Lorelle VanFossen wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As everyone has said, welcome to the Codex and WordPress Documentation Team.<br>
</blockquote>
<br>
Thanks.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Be sure and check out the guidelines for editing and working with the<br>
Codex under the Community Portal. These will help you figure out how it<br>
all works.<br>
</blockquote>
<br>
That was the first thing i did!<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Ensure EVERY page on the Codex has the proper Category at the bottom<br>
of each page. A page can be in more than one category, but we have to be<br>
REALLY specific about categorizing the documents.<br>
</blockquote>
<br>
Are there any category guidelines anywhere? I've looked, but i haven't found it.<br>
<br>
I'm happy to spend as much time as i can going through the codex and
categorizing articles. It will be a good way to get to know what's in
there, anyway.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A document on Plugins<br>
should go in the Plugins category, but if it is really basic, it should<br>
also go in WordPress Lessons, but if complicated and very "developer"<br>
then it also needs a cross reference in the Developer category, right?<br>
It's a tough call sometimes but think about how the user will hunt for<br>
the information and sort accordingly.<br>
</blockquote>
<br>
For development type subjects, at least, i think the categories may
need to be more fine grained than that if they're going to be really
useful.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Foreign Language articles - We need to put the articles in different<br>
languages into their own language specific categories. That will help<br>
get those articles into their own grouping, and help us get that<br>
information to the people who need it.<br>
</blockquote>
<br>
If non-English languages are going to be in their own categories,
surely English language articles need to be categorized "English"?
Maybe i've missed something, but that doesn't appear to be happening.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Check the categorization and<br>
language guidelines for how to categorized those.<br>
</blockquote>
<br>
Where are they? (Is it just me that can't find anything in this wiki?)<br>
<br>
Will<br>
_______________________________________________<br>
wp-docs mailing list<br>
<a href="mailto:wp-docs@lists.automattic.com" target="_blank">wp-docs@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
</blockquote>
_______________________________________________<br>
wp-docs mailing list<br>
<a href="mailto:wp-docs@lists.automattic.com" target="_blank">wp-docs@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
</div></div></blockquote></div><br><br>>> <a href="http://lists.automattic.com/mailman/listinfo/wp-docs">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>><br>> _______________________________________________<br>
> wp-docs mailing list<br>> <a href="mailto:wp-docs@lists.automattic.com">wp-docs@lists.automattic.com</a><br>> <a href="http://lists.automattic.com/mailman/listinfo/wp-docs">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
<br>