Skip to content

Provide rationale for the rules enabled or disabled #21

Open

Description

@khiga8

I think it will be helpful to provide context on why we recommend these configurations.

In base.json

{
    "default": true,
    "no-inline-html": false,
    "no-bare-urls": false,
    "no-blanks-blockquote": false,
    "fenced-code-language": true
}

In accessibility.json

{
    "no-alt-text": true,
    "no-default-alt-text": true,
    "no-duplicate-header": true,
    "no-emphasis-as-header": true,
    "no-generic-link-text": true,
    "no-space-in-links": false,
    "ol-prefix": "ordered",
    "single-h1": true,
    "ul-style": true
}

Some of these are somewhat obvious, while others are less so.

Activity

  1. chris-c-thomas commented on Feb 6, 2023

    @chris-c-thomas

    I think a doc page of some sort would definitely be great. I love opinionated things but also want to know the reasoning behind other's choices before I adopt it.

  2. andrialexandrou commented on Oct 9, 2023

    @andrialexandrou
    Collaborator

    Adding a note here to emphasize how some of the accessibility rules here are indeed related to accessibility, for instance

    • ul style asterisk
    • no space in links being disabled
    • ol prefix ordered
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions