OccupyWallStreet.net Content

OccupyWallStreet.net Wiki The public website for news and information about OWS in NYC.

CRM Resources Style Content Development Planning

Content Management

OccupyWallStreet.net is built using a Drupal CMS system and the Workbench plug which allows authors to submit content to the site and editors to modify and publish it to the website.

To begin using the system, go to occupywallstreet.net/admin/workbench and log-in if you already have an account or register to apply for one. Once you've logged into the site, make sure you're at the url occupywallstreet.net/admin/workbench. You'll now have access to the following areas.

My Content

"My Content" is your dashboard for all content you've editted and all "recent content" uploaded to the system.

Create Content

"Create Content" allows you to create different types of content items. The three main content items are Stories, Events and Announcements.

• Stories are content item that are published through the normal workflow. They can appear in the featured area on the home page, stories area on the home page and the entire "read" page. Most content is a "story."
• Events are items with time and location information unique to events. "Events" pages can appear in all the same places as "Stories".
• Announcements are content items that live in the top navigation bar of the website. These items only appear on the bar and do not create their own unique pages.

Stories

To add a story, go from your dashboard at admin/workbench to "Create Content", then click "Story". Fill out all required fields. Explanations for each field are below.

• Title: Headline, there is only one (should be title case)
• Author: whomever wrote the story
• Source: if the article is being republished, it would be the name of the publication or URL of the site from which is came
• Summary: Teaser that will be displayed through features
• Body: This is where the story goes.

Events

Events operate just like stories but also contain information about date and address, which will be placed at the top of the page. To add an event, go from your dashboard at admin/workbench to "Create Content", then click "Event". Events appear as content on the home page and the read page, as well as event listings on the contribute page.

Note: Even though there is a map in the "Create an Event" editor, it will not appear on the website.

• Title: Headline, there is only one (should be title case)
• Source: if the event is being republished, it would be the name of the publication or URL of the site from which is came
• Date: Enter start and finish date and time of the event
• Location: Enter name and address of event
• Summary: Teaser that will be displayed through features
• Body: This is where the event information goes

Announcements

There are two announcement content items that live on the top navigation bar, titled "announcement 1" and "announcement 2". To change the content, find the announcement items as published content in the "All Recent Content" section of your admin/workbench.

Make sure:

• your content is under 100 characters or there will be formatting problems.
• you click "preview" to see how the announcement will look before it goes live.

Featured Content

To access the "Featured Area" section, go to a story and click on the "Featured Items" tab.

Screen shot showing how to reorder items, remove them, find and add new items. Credit: Misfist

On the featured items page, there are two sections:

• Featured Stories is the section on the front page of the site. It can contain up to 5 story items and you can reorder them from the screen. These stories will also appear on the home page as "Stories".
• Single Featured Story is the large thumbnail on the Read page. These stories will only appear on the read page as the large thumbnail. Only one story can be featured here at a time.
• Note: there is current a bug, which cause an article to appear in duplicate if it's featured on the home page and on the stories page.

Moderation Workflow

Publishing options: "Promote to the front" and "Sticky at the top" don't do anything so don't worry about them. Moderate state determines who can access your content.

• "Draft" means only you, the author, can view and edit the content. Keep stories in draft mode until you want them to be seen by an editor.
• "Needs Review" means your content is still unpublished, but the editors can see it, edit it and publish it.
• "Published" content is live on the site. It can be edited by creating revisions.

The moderation screen shows the elements of the workflow. Credit: Misfist

My Drafts

This section of the site logs all the articles you've created and edited.

Needs Review

The workflow system we're using allows authors to add a content item and editors to review, edit and publish it.

When authors first create a content item it remains in the "draft" state where they can edit it until they change the state from "draft" to "needs review". Once an item is in "needs review", it becomes public to the editors who can edit and publish it.

All content items in the "needs review" state can be found under your "Needs Review" tab. When you click a story, you can edit the draft and view edits under the "moderate" tab. When a story is ready to be published, simply change the state on the top of the page from "Needs Review" to "Published." Once published, you can change it's placement on the site through the "Featured Items" tab.

Published

This means the content is publicly viewable on the site.

Content Submission

Contributing Content

Our capacity to publish content from a wide variety of sources will expand over time as the site is developed, but in the beginning we are limited to the following processes:

• Subscribe to the owscontent@lists.occupy.net listserve and introduce yourself.
• Submit content to OccupyWallStreet.net by emailing us at submissions@occupywallstreet.net.
• Get published by a partner publication and we might publish it.

Evaluating Submissions

The curator’s position is twofold:

1. evaluating the submissions that are sent to submissions@occupywallstreet.net
2. searching the nycga subdomains and affiliated websites for appropriate content

When evaluating the submissions sent to submissions@occupywallstreet.net, the curator should input the date, author, and title of the piece into the submissions@occupywallstreet.net spreadsheet. The curator should indicate the category into which the submission falls, if applicable.

• Editorial
• News
• Analysis
• Event
• GA Statement

The curator should then classify the submission according to a 4-point scale:

1. The piece looks great and is ready for publication with no edits. This will apply to content that is being republished from another vetted publication.
2. The piece looks good and will be submitted through the workflow for editing and publication.
3. The piece is being tabled for now but might enter the workflow at another time.
4. The piece is being rejected for poor quality, violation of the principles of solidarity, or the fact that it falls out of the scope of occupywallstreet.net

The curator should indicate any relevant impressions in the comments column of the spreadsheet.

Protocols that PR uses for deciding whether or not to send a press release about an action:

Guidelines for support:

1. Initiative by a WG/WGs as defined by the post Jan 20th guidelines or Other Group so long as they are coordinated with the appropriate WG/genuine connection with a WG.
2. Independent Group or an Affinity Group, ultimately needs approval by DA or GA
3. Does not conflict with principles of solidarity
4. Non-violent action
5. Does not support a particular political candidate or party, including politicians speaking at your event (OWS is about every day people, not about promoting celebrities, politicians...they can do their own PR anyway)
6. Orientation has to be towards economic/social/racial/envt’l justice

Factors to consider:


1. Number of people attending meetings/a part of the WG or AG
2. How many people do they expect?
3. Level of general/media interest in the issue
4. local action vs national
5. connection to core OWS concerns
6. Focus
7. Partners and outside groups involved--this should be considered not in an effort to be exclusionary, but to be transparent (level of involvement/nature of relationship)
8. List of speakers (if there are any)--diversity of speakers

@owsnet

• No personal attacks
• Relevant to the OWS community

Content Structure

All content items will display attribution in the byline:

• If it comes from a working group, it will have the working group name and the author if specified
• If it comes from an occupy, it will have the author's name and occupation name as source
• If it's editorial it will have the author's name and OccupyWallStreet.net as source

Required Elements

Articles must contain the following elements, at a minimum

• Title: What is the name of the article?
• Summary/Excerpt: 140 characters or less!
• Category: Editorial | News | Analysis | Event | GA Statement
• Date: Publication Date
• Author: Author on the byline
• Source: If originally published elsewhere, name and link to source
• Pull-quotes (optional): Author on the byline
• Image(s) (optional): Engaging images to display in the article listing and in the body of the article; if no image is provided, a default image will be displayed.

Optional Elements

• Editor: Responsible for quality control
• Documentation (optional)
  • Interviews
  • Drafts
  • General notes
  • Citations
  • Research

Tags

• Content items may be tagged with harmonized groupings and their occupation source from the Occupy.net Registry.
• Content items may be tagged with information describing the nature of their source:
  • General Assembly Statements
  • Working Group Chartered by a GA
  • Content affiliates in solidarity with OWS