Skip to content

Guide: how to write docs. #14070

@steveklabnik

Description

@steveklabnik

We should have guidelines for how docs are written. Tense, /// vs /**, all that stuff.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions