Editor
A site user responsible for performing editorial process to create, edit, or otherwise manage content. An editor creates, manages, edits, approves, and publishes content. This is considered the core user of a site, typically a content management system (CMS). Most CMS functionality is based around editors.
There are several subtypes of editor:
- A power editor might also have some administrative responsibilities.
- An approver might only be responsible for moving content through the approval process.
- An UGC editor or community manager might only manage and review user-generated content (comments, ratings, reviews, etc.)
- A marketer might not create and edit content directly, but is responsible for delivery, optimization, and performance of that content.
Related Chapter Sections:
-
Inputs and Outputs
Chapter 7: Know Your Content
Inputs and outputs for Chapter 7: Know Your Content
-
Application of Information Architecture
Chapter 10: Organize Your Content
The labeling, the navigation, the organization — this is all information architecture, the practice dedicated to finding organization through context and structure.
-
Inputs and Outputs
Chapter 11: Model Your Content
Inputs and outputs for Chapter 11: Model Your Content.
-
Inputs and Outputs
Chapter 12: Write for People and Machines
Inputs and outputs for Chapter 12: Write for People and Machines.
-
Model Implementation
Chapter 20: Implement the Back-End Functionality
Remember that content model you created? It's time to convert that model into something your CMS can manage.
-
Defining the Content Model
Chapter 11: Model Your Content
So, what exactly IS a content model? Before we begin planning a content model, let's take some time to define it.
-
Implementing the Content Model
Chapter 11: Model Your Content
And now, let's make the content model REAL. Let's build it within the structure of the content management system.
-
The Content: Maintaining and Creating Content That Works
Chapter 24: Maintain and Improve
The steps to maintaining content focus on carving out attention and setting up useful systems of review.
-
The Site Itself: Adjustments to Your Big Investment
Chapter 24: Maintain and Improve
Beyond maintaining content, you'll also find yourself maintaining the site itself — the integrations, the next-phase updates, and the content management system in general.
-
Other Development Tasks
Chapter 20: Implement the Back-End Functionality
Beyond the main back-end development tasks there's quite a few other details to be handled.
-
The Short List and Request for Proposal (RFP)
Chapter 16: Select a Content Management System
Once you’ve notified a handful of vendors that you’ve decided not to move forward with them, you need to prepare an RFP for the remaining vendors.
-
Writing for Machines
Chapter 12: Write for People and Machines
Finally, there's one audience you can never please — because they care only for data: search engines and screen readers.
-
Testing the Site
Chapter 22: Test and Launch the Site
There are three axes that a QA issue can turn on when testing the site: public vs. private, absolute vs. partial, and uncontained vs. contained.
-
Transitioning from Project to Product
Chapter 24: Maintain and Improve
Your site has launched, and it's yours now! We've officially moved from the project phase into the PRODUCT phase.