Mattermost Handbook
Need help?How to spend company moneyHow to update the HandbookRelease overview
0.2.1
0.2.1
  • Mattermost Handbook
  • Company
    • About Mattermost
      • List of terms
      • Business model
      • Mindsets
    • "How to" guides for staff
      • How to set up a 1-1 channel
      • How to update the handbook
      • How to manage Handbook notifications
      • How to change mobile device
        • How to handle a lost mobile device
      • How to do a mini-retrospective
      • How to autolink keywords in Mattermost
  • Operations
    • Company operations
      • Areas of Responsibility
      • Mattermost Leadership Team (MLT)
        • MLT cadence
      • Company measures
        • Metrics definitions
        • FY23 goals board
        • MLT metrics
      • Company cadence
      • Company policies
        • Community response policy
        • Security policy
      • Company processes
        • Issue/solution process
        • Company agreements
        • Publishing
          • Public web properties
          • Publishing guidelines
            • Brand and visual design guidelines
            • Voice, tone, and writing style guidelines
              • Contribute to documentation
            • Confidentiality guidelines
          • Post-publication quality control process
      • Handbook processes and policies
        • Handbook onboarding
      • Fiscal year planning
    • Research and Development
      • Organization
        • Tech Writing
        • Data engineering
        • Delivery
        • Cloud Platform
        • Site Reliability Engineering
        • GRC
        • Product Security
        • Security Operations
      • Processes
        • Feature Labels
      • Product
        • Product planning
          • Product philosophy and principles
          • Prioritization process
          • Release planning process
          • Roadmap views
          • Release plan
          • Launch plan
          • Feature requests
        • Development process
          • Mobile feature guidelines
          • Deprecation policy
          • Mattermost software requirements process
          • Jira ticket lifecycle
          • Creating new Jira bug tickets
            • Priority levels for tickets
            • Jira fix versions
        • Release process
          • Release overview
          • Feature release process
          • Dot release process
          • Security release process
          • Mobile app release process
          • Desktop app release process
          • Release tips
          • Release scorecard definitions
        • How-to guides for Product
          • How to use productboard
          • How to record a roadmap video
          • How to update integrations directory
          • How to write a feature release announcement
        • Product Management team handbook
          • Product Management Areas of Ownership
          • Product Manager onboarding
          • Product Manager levels
          • Professional development
        • Product Design team handbook
          • Product Design levels
        • Technical Writing team handbook
          • Work with us
          • User interface text guidelines
          • Documentation style guide
          • Our terminology
          • Guidelines for PMs and developers
          • Guidelines for community contributions
          • Technical Writer levels
          • Docathon 2021
            • Getting started with contributing
        • Growth
          • A/B testing methodology
          • PQL definition
        • Analytics
          • Product Analyst Engineer levels
          • Looker
            • Dashboards
            • Explores
          • Telemetry
        • Developer relations
        • Product team hangouts
      • Engineering
        • Infrastructure engineering
          • Cloud infrastructure cost KPIs
          • Cloud data export process
          • Cloud churn process
          • Reliability Manifesto
          • Production Readiness Review
          • Infrastructure Library
        • Integrations team processes
        • Plugin release process
        • Data Engineering
        • Sustained Engineering
          • On call
        • How to go to a conference
        • Public speaking
        • Core contributor expanded access policy
      • Quality Assurance
        • QA workflow
        • QA testing tips and tools
        • Rainforest process
    • Messaging and Math
      • How-to guides for M&M
        • How to create release announcements
        • How to create screenshots and GIFs
        • How to write Mattermost case studies
        • How to write guest blog posts for Mattermost apps and services
        • How to write Mattermost recipes
        • How to compose tweets
        • How to create a split test for web page
        • How to run meetups
        • How to run executive dinners
      • Checklists for M&M
        • Blog post checklist
        • Bio checklist
      • Mattermost websites
      • Demand generation reporting
      • M&M Asana guidelines
      • Content marketing
        • How to use the editorial calendar
        • Content development and distribution
        • Video content guidelines
        • How to contribute content
    • Sales
      • Deal Desk
      • Partner programs
      • Lead management
    • Deployment Engineering
      • Overview
      • Workflows
      • Frequently Asked Questions
      • Playbook for MME Sev 1 Outages
      • Status Update Template
    • Program Management
    • Customer Success
      • Customer Support
    • Legal
      • Contracts
      • Ironclad Basics
        • Company-Wide Workflows
        • Sales Contracts and Workflows
        • Signing a Contract and Contract Repository
    • Finance
      • Budget
      • How to use Airbase
        • Access Airbase
        • Navigate Airbase
        • How to submit a purchase request
        • How to submit a reimbursement request
        • How to review a reimbursement request
        • Vendor portal guide
        • Frequently asked questions
      • Onboarding
        • Vendor onboarding
        • ROW staff onboarding
      • Staff member expenses
        • How to spend company money
        • How to spend company money: Internships
        • Corporate credit card policy
        • How to access Airbase
        • Gifting policy
        • How to book airfare and travel
        • How to reimburse the company
        • How to convert currencies
        • How to get paid
      • Arrange a Bounty Program
      • Naming files and agreements
      • Risk management
        • Mattermost U.S. consulting agreements
      • Operations playbook
    • Security
      • Policies
      • Privacy
        • Data deletion requests
        • Data subject access requests
      • Product Security
        • Product Vulnerability Process
        • Working on security-sensitive pull requests
        • Secure Software Development guide
      • Security Operations
        • User guides
    • Workplace
      • PeopleOps
        • HR cadences
        • HR systems
        • HR Processes
        • Working at Mattermost
          • Onboarding
            • Things everyone must know
            • Staff onboarding
            • Engineer onboarding timeline and expectations
            • Manager onboarding
            • Frequently asked questions
          • Learning and development
          • Mattermost communication best practices
          • Paid time off
            • Out of office email example
          • Travel
            • Business travel insurance
          • Leaves of absence
            • Pregnancy leave
            • Baby bonding parental leave
            • Jury duty
          • Workplace program
          • Relocation
          • Total rewards
        • Performance reviews
          • Formal review process
          • New staff performance review
          • Informal review process
        • Transfers and promotions
        • Offboarding instructions for managers
        • People compliance
      • People policies
      • Groups
        • Staff Resource Groups
      • Approvals and iteration
      • IT
        • IT helpdesk
        • Hardware and software purchases
        • Hardware buy back policy
        • Software systems
  • Contributors
    • Contributors
      • Equity, diversity, and inclusion
      • How to contribute to Mattermost
        • Community Content program
        • Documentation contributions
        • Help Wanted tickets
        • Localization
        • Contribution events
      • Mattermost community
      • Contributor kindness
      • Community systems
      • Guidelines and playbooks
        • Social engagement guidelines
        • Contribution guidelines and code of conduct
        • Mattermost Community playbook
        • How to run a Hackathon
        • Hacktoberfest event organizer guide for Mattermost
    • MatterCon
      • Staff information privacy management
      • Mattermost events code of conduct
      • MatterCon2021
    • Join us
      • Ice-breakers
      • Help Wanted tickets
      • Localization
      • Mattermost GitHub sponsorship
      • Things candidates should know
      • Staff recruiting
      • Recruiting cadences
        • Product Manager hiring process
      • Exec recruiting
        • EA logistics
  • Help and support
    • Contact us
Powered by GitBook
On this page
  • Templates
  • Task Workflow
  • Inbound topics
  • Planned and In Progress
  • Pending Review
  • Publication Prep
  • Scheduled
  • Done
  • Editorial calendar fields

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Messaging and Math
  3. Content marketing

How to use the editorial calendar

PreviousContent marketingNextContent development and distribution

Last updated 3 years ago

Was this helpful?

Our editorial calendar can be found in , and is used to track upcoming content to be published on the Mattermost website, blog, developer blog, and third-party channels.

Templates

The editorial calendar includes a Templates section, with workflow templates for common content types. To create a new task using a template, right-click the Template you want to use and select Duplicate Task. The task will automatically be added to Inbound Topics.

Task Workflow

Every piece of content moves through the same general workflow for creation, review, scheduling, and distribution. This is reflected in the Board View of the Asana project.

Inbound topics

When new content ideas and topics are shared with other members of the team, they should be added to Inbound Topics with the status [REVIEW] Inbound Idea. This helps us capture and triage new post ideas and ensure that our backlog stays healthy.

Tasks in this category may need to be approved by external or internal collaborators before moving forward. For example, technical content must be reviewed by R&D team leads before it's confirmed. For more on this process, please refer to our .

Planned and In Progress

Once we’re sure that we’ll move forward with developing a piece of content, the Asana ticket is moved to Planned if it hasn't yet been started. When it's underway, it's moved to In Progress.

In order to move into In Progress a post must have an assigned author/contributor.

Pending Review

All content requires an SEO/grammar review by the Editorial Team, and many pieces also require a technical review or external approval before they're ready for publication. Please add any internal reviewers to the Asana ticket during this stage, and make a comment for any additional/external reviewers.

Publication Prep

Posts are moved to Publication Prep when they're fully reviewed. This status indicates to the Editorial Team that the post is completely approved to go live.

Scheduled

Scheduled posts that are fully loaded into WordPress and have social media content scheduled are moved into Scheduled. This gives the Editorial Team an at-a-glance overview of content that's ready to be published.

Our goal is to have the Editorial Calendar scheduled about two weeks out, allowing us to avoid last-minute scrambles to complete content!

Note that Scheduled posts still need to be distributed manually (syndicated to third-parties, posted to Reddit, etc.).

Done

Editorial calendar fields

Every content task has a number of fields that help us track campaigns more easily. They allow anyone who is editing or preparing a post for publication to have all the information they need to get the job done.

  • Assignee: The name of the person responsible for moving the post to whatever its next state is; for many stages, this person will be on the Marketing team.

  • Due date: The date that the post is set to go live.

  • Tags: The high-level Content Themes that the post is associated with. A task may have multiple tags associated with it. There are currently five tags in use for content:

    • Open Source for Enterprise

    • DevOps Workflow

    • Remote Collab

    • Product: Use this for product releases, product-specific how-to’s, and other content.

    • Developer: Use this for any content that should be cross-posted to the Developer blog.

  • Status: Statuses are set to change automatically as a task is moved through different sections of the Asana board. Additional automation may be integrated in the future.

  • Content Type: Content types help the Editorial Team plan for the specific development and distribution activities for different content formats of content, e.g. building sales collateral for case studies. Please try to use existing content types where possible.

  • Byline: The name of the person (or people) who will be credited as the author of the content, where applicable.

  • Draft/Link: A link to the Google Doc, WordPress entry, or other source of content.

  • Description: Any notes on the content that are not captured in other fields.

When all publication activities are completed, the post is moved to Done and no further action is needed. Completed posts should be reviewed in the next Content Strategy review cycle, .

Asana
Content Development and Distribution Processes
during the first meeting of the month