Strikeforce:Content Strategy - Revision history

AlexWebr: /* Content Strategy */

2014-06-01T22:35:52Z

‎Content Strategy

2014-05-29T22:19:07Z

‎Curated pages and category pages

2014-05-29T22:18:20Z

2014-05-29T22:08:10Z

2014-05-29T22:05:11Z

2014-05-29T19:44:44Z

2014-03-28T14:08:20Z

2014-03-27T12:49:01Z

2014-03-12T21:49:52Z

‎Cleaning up

2014-03-12T00:27:07Z

@@ Line 41: / Line 41: @@
 ** Calendar
 * Meetup
 * Twitter
 * Facebook

@@ Line 109: / Line 109: @@
 In some cases, a full description is not necessary. The events, for example, only need a curated selection of event descriptions in the main body, with a link to the full category. 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.
-. We have the standalone [[Events]] page, which looks nice, and links to Category:Events, which is fairly bare.
+# We have the standalone [[Events]] page, which looks nice, and links to Category:Events, which is fairly bare.
-. We create the Events page, but redirect it to Category:Events, which will contain both the curated content and the list of all events. It's harder to link to categories (the page becomes part of that category), so this way lets us easily link to categories, too.
+# We create the Events page, but redirect it to Category:Events, which will contain both the curated content and the list of all events. It's harder to link to categories (the page becomes part of that category), so this way lets us easily link to categories, too.
 So far, the second one sounds best.

@@ Line 60: / Line 60: @@
 <code>{{<nowiki />Archived}}</code>
 ===Handling subcategories of categorized items===
@@ Line 71: / Line 74: @@
 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 each category. Following this example with your date in place:
+For a single event, either the title should include the ISO 8601 date at the beginning, or the page should include a tag at its bottom which rewrites how it's categorized in each category. Following this example with your date in place:
 <code>{{<nowiki />Date|1999-12-31}}</code>
@@ Line 89: / Line 92: @@
 Archived articles become our history. For improved context, archived files should have pertinent future-tense or present-tense words changed to past-tense. (This isn't a requirement.)
 ===List Items===

@@ Line 102: / Line 102: @@
 In some cases, a full description is not necessary. The events, for example, only need a curated selection of event descriptions in the main body, with a link to the full category. 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.
-. We have the standalone [[Events]] page, which looks nice, and links to [[Category:Events]], which is fairly bare.
+. We have the standalone [[Events]] page, which looks nice, and links to Category:Events, which is fairly bare.
-. We create the Events page, but redirect it to Category:Events, which will contain both the curated content and the list of all events.
+. We create the Events page, but redirect it to Category:Events, which will contain both the curated content and the list of all events. It's harder to link to categories (the page becomes part of that category), so this way lets us easily link to categories, too.
 So far, the second one sounds best.

@@ Line 2: / Line 2: @@
 * To redesign the information architecture of the SkullSpace wiki (this wiki) and design a proper content management strategy that others can use to update the wiki.
 * Leader: A. Michael
-* Members: A. Michael, Nate, Jeremy[1]
+* Members: A. Michael, Nate, Phoul
 * Status: Initial Planning

← Older revision		Revision as of 21:49, 12 March 2014
Line 106:		Line 106:
	* Updates, which perhaps don't belong on the Wiki (or should be immediately archived)		* Updates, which perhaps don't belong on the Wiki (or should be immediately archived)

		+
		+	What is our content? The entire hierarchy of content should be mapped and some of it transformed into different formats for other channels.

	==Information Architecture==		==Information Architecture==

@@ Line 90: / Line 90: @@
-==Cleaning up==
+===Cleaning up===
 Fill out the Help page with a short page detailing simple formatting and the use of things like templates and sections.
@@ Line 107: / Line 107: @@
 ==Content Strategy==
 ===Archives===