Skip to content

[Tracking] Enforce a source style in Markdown files with Prettier #10402

@ddbeck

Description

@ddbeck

This is a meta issue for the work that needs to happen to adopt to an automated, formalized code style for MDN content. This overall approach was proposed in https://github.com/mdn/content/discussions/9901#discussioncomment-1576438 and wasn't objected to, so this is how we're doing it.

MDN has several guidelines for code style. See Code example guidelines. Instead of asking people to know and carry out a style, we ought to do the modern thing: directly format what we want.

Distinct slices of work are broken down in the following issues:

Metadata

Metadata

Assignees

No one assigned

    Labels

    infraInfrastructure issues (npm, GitHub Actions, linting) for this repomarkdownIssues related to Markdown conversion

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions