Skip to content

Freshness monitoring #14

@alexeagle

Description

@alexeagle

It's currently hard to know whether content is current.

My proposal:

  • Each page should have a public-visible "last updated by [github handle]"
  • We should have some script and automation so the tech writer has easy access to a report of which content ought to be reviewed soon, based on things like:
    • not fresh
    • commonly accessed (no point prioritizing dead content)
  • tech writer should be able to update the verification with some expiration when they want to re-review
  • tech writer needs a way to identify the Subject Matter Expert (SME) for any given page, so they know who to ask

https://www.notion.com/help/guides/verify-knowledge-your-teammates-can-trust-with-page-verification is an example of a system that does some of this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions