Skip to content

Include Available Version markers when documenting new features #500

@Cheddam

Description

@Cheddam

Pages affected

Description

Often documentation for new features lands in this repo (and is published) before the version it becomes available in is shipped. Even after it ships, some projects may not be updated immediately. This can create some confusion when a developer discovers and attempts to reference documentation for a feature that isn't yet available in their project.

To combat this, I propose introducing a guideline to encourage the inclusion of an 'Available from x.y' flag above any newly created documentation. In addition, I'd suggest we prune these flags when branching a new major version of the docs, since all flagged documentation can be assumed to be current at that point.

Validations

  • Check that there isn't already an issue that reports the same problem

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions