Guide for Content Authors

(1)

As a content author,

I want to know how to write articles for ecobytes.net

So that they are cohesive and a joy to read.

(2)

As a designer working for ecobytes,

I want to codify design decisions and best practices concerning the public content of ecobytes.net

So that Content Authors will access and enjoy them

(3)

As a content author with some experience in authoring,

I want to share my tacit and codified knowledge with fellow authors and the designer(s)

So that they can do journeys (1) and (2)

-

  • An editor can access a single "Content Authors' Guide" that contains pointers to all relevant resources
  • A designer and any experienced author can edit it

This Content Authors' Guide

  • is always kept up to date, and the responsibility for that is codified in some way
  • adheres to the ethos and norms that we are setting for the association
  • links to analogous guides for different roles

The resources it points to

  • are accessible and actionable for any author who reads the guide
  • might be authored guides, comments in code, wiki pages, external pages, or even people's contacts
  • themselves keep in-sync with the ethos and norms that we are setting for the association
  • contain back-links to the Content Authors' Guide

All concerns of content editing are covered, including, but not limited to

  • normative standards that can be part of a manual review process, parsing, or validation step
  • actionable instructions

-

Context: We are implementing guides for different roles (author, developer, member, etc.). See the discussions in #2 and #3 for how we got here.

Blocked by: #4 (closed) Editorial Workflow

Edited by Flupsi