Skip to content

Create content strategy for OO blog #21

@theecrit

Description

@theecrit

Description

Without a content strategy, the blog risks becoming over- or under-managed. Potential consequences include excluding underrepresented voices, lack of quality control, and lack of relevance.

Recommended priorities:

  • Define an editorial purpose (eg "Create a shared and public space for learning out loud as OpenOakland explores how to bring tech and community together in service of a more equitable Oakland").
  • Define the editorial content mix (see "Content Mix").
  • Create a basic publishing workflow with clear roles and permissions that support quality control without gatekeeping.

Content mix

Since introducing the blog to the website, we've kept it pretty tightly focused on:

  • Steering Committee recaps
  • Project case studies and learnings
  • Member interviews/profiles

Potential good additions:

  • Project news, milestones, and requests for help
  • Special OO event announcements
  • Network roundup (recommend outweighing 3:1 by OO content)

Note

This issue has filed in the Culture, Process and Ritual project because it involves how the group works together and brigade strategy in significant ways. Once this issue is complete,a new one could be opened to reflect getting it codified in the OO Ops Handbook.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Input wantedIssue needs more discussion, clarity or specificity to be completed.suggestionHave an idea for how OpenOakland could work better?

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions