Talk:Strikeforce:Content Strategy - Revision history

AMichael at 21:39, 29 May 2014

2014-05-29T21:39:27Z

AMichael at 21:37, 29 May 2014

2014-05-29T21:37:40Z

AMichael: /* Handling subcategories of categorized items */

2014-03-19T00:12:14Z

‎Handling subcategories of categorized items

AMichael: /* Events */

2014-03-12T22:02:24Z

‎Events

AMichael at 17:36, 12 March 2014

2014-03-12T17:36:47Z

AMichael at 17:10, 12 March 2014

2014-03-12T17:10:10Z

AMichael: Created page with "We should archive every old page, even if they're in an archived list and are not linked anywhere else, because someone could link them in a separate document later."

2014-03-12T00:22:42Z

Created page with "We should archive every old page, even if they're in an archived list and are not linked anywhere else, because someone could link them in a separate document later."

New page

We should archive every old page, even if they're in an archived list and are not linked anywhere else, because someone could link them in a separate document later.

@@ Line 8: / Line 8: @@
 For example, from the Main Page:
 * Visit the list of all Projects
-* * Browse the category Cook all the Things
+** Browse the category Cook all the Things
-* * * View a single recipe
+*** View a single recipe
-* * * * Possibly find a small informational page relevant to something within the recipe
+**** Possibly find a small informational page relevant to something within the recipe
 ==Current Structure and Content==

@@ Line 1: / Line 1: @@
-==Ideas==
+==Purpose==
-===Archiving sets of items under an archived page===
+Our content strategy is a set of rules to follow when creating new content. We need to describe how to categorize it, where to post it, what channels work for what types of content, and how the content should be formatted for each channel. Ideally, it should be in some kind of easy-to-navigate linked map, which is where hypertext comes in handy.
-===Separate pages and category pages===
+This strategy should be as simple as possible, while covering the greatest breadth possible. To that end, we should give the site a very simple structure: No more than 7 main categories, and not more than 3 links away from the main page. There should be only a few ways to do things: Add an expiring event, add a managed project, create informational content specific to a particular medium, and combine pages of similar content into categories.
-===Handling subcategories of categorized items===
+For example, from the Main Page:
-The easiest way to manage individual items is to put them in subsections of their category parent page. For example, "[[Cook All the Things]]" contains each recipe under different headings for the courses, rather than just listing the names of all the recipes.
+* Visit the list of all Projects
-This becomes harder when things need to be included in more and more subcategories. In that case, adding each of them as categories will automatically add it to those category pages, so they're all easy to find.
+==Current Structure and Content==
-What's the best default? Will members always include their new entry into the appropriate list on the parent category? Or can we expect them to know the differences between all subcategories and apply all the right ones?
+Links:
-===Events===
+* No link to the blog
-A wiki page might be for one event, or could be about a recurring event.
+* The store needs to be checked up on
-For a single event, either the title should include the ISO 8601 date at the beginning, or the page should include a tag which rewrites how it's categorized in each category. Following this example with your date in place:
+Immediate suggestions:
-<code>{{<nowiki />DEFAULTSORT:''*1999-12-31''}}</code>
+A good idea would be to load page content directly from wiki pages and into the bodies of skullspace.ca pages.
-This would sort it under the heading "*" with proper date sorting.

@@ Line 8: / Line 8: @@
 ===Handling subcategories of categorized items===
-The easiest way to manage individual items is to broadly subcategorize them in subsections of their category parent page. For example, "[[Cook All the Things]]" contains each recipe under different course headings.
+The easiest way to manage individual items is to put them in subsections of their category parent page. For example, "[[Cook All the Things]]" contains each recipe under different headings for the courses, rather than just listing the names of all the recipes.
-This doesn't work as well when things need to be included in two or more subcategories. In that case, adding each individual item to all of its subcategories will automatically add it to the subcategory page, so that they're all easy to find.
+This becomes harder when things need to be included in more and more subcategories. In that case, adding each of them as categories will automatically add it to those category pages, so they're all easy to find.
-What's the best default? Can we trust members to always include their new entry into the appropriate list on the parent category? On the other hand, can we expect them to know the differences between all subcategories and apply all the right ones?
+What's the best default? Will members always include their new entry into the appropriate list on the parent category? Or can we expect them to know the differences between all subcategories and apply all the right ones?
 ===Events===

@@ Line 17: / Line 17: @@
 A wiki page might be for one event, or could be about a recurring event.
-For a single event, either the title should include the ISO 8601 date at the beginning, or the page should include a tag which rewrites how it's categorized in [[:Category:Events]], as follows:
+For a single event, either the title should include the ISO 8601 date at the beginning, or the page should include a tag which rewrites how it's categorized in each category. Following this example with your date in place:
-<code>[[<nowiki />Category:Events|''ISO8601 date followed by usual title'']]</code>
+<code>{{<nowiki />DEFAULTSORT:''*1999-12-31''}}</code>
-This way isn't as easy, because that extra code must be recopied for each category it's placed in (for example, once it's archived).
+This would sort it under the heading "*" with proper date sorting.

← Older revision		Revision as of 17:36, 12 March 2014
Line 13:		Line 13:

	What's the best default? Can we trust members to always include their new entry into the appropriate list on the parent category? On the other hand, can we expect them to know the differences between all subcategories and apply all the right ones?		What's the best default? Can we trust members to always include their new entry into the appropriate list on the parent category? On the other hand, can we expect them to know the differences between all subcategories and apply all the right ones?
		+
		+	===Events===
		+	A wiki page might be for one event, or could be about a recurring event.
		+
		+	For a single event, either the title should include the ISO 8601 date at the beginning, or the page should include a tag which rewrites how it's categorized in [[:Category:Events]], as follows:
		+
		+	<code>[[<nowiki />Category:Events\|''ISO8601 date followed by usual title'']]</code>
		+
		+	This way isn't as easy, because that extra code must be recopied for each category it's placed in (for example, once it's archived).

← Older revision		Revision as of 17:10, 12 March 2014
Line 1:		Line 1:
		+	==Ideas==
		+
		+	===Archiving sets of items under an archived page===
	We should archive every old page, even if they're in an archived list and are not linked anywhere else, because someone could link them in a separate document later.		We should archive every old page, even if they're in an archived list and are not linked anywhere else, because someone could link them in a separate document later.
		+
		+	===Separate pages and category pages===
		+	Does it matter whether we redirect from a given page to its category, and include all content there? If we do, we can post what we want on that page and there'll automatically be a list of all category items at the bottom.
		+
		+	===Handling subcategories of categorized items===
		+	The easiest way to manage individual items is to broadly subcategorize them in subsections of their category parent page. For example, "[[Cook All the Things]]" contains each recipe under different course headings.
		+
		+	This doesn't work as well when things need to be included in two or more subcategories. In that case, adding each individual item to all of its subcategories will automatically add it to the subcategory page, so that they're all easy to find.
		+
		+	What's the best default? Can we trust members to always include their new entry into the appropriate list on the parent category? On the other hand, can we expect them to know the differences between all subcategories and apply all the right ones?