This needs to be considered from all angles but as far as I'm concerned the headings in a markdown document should be valid within that document but also be influenced by how they are rendered. For example, articles get rendered with an external <h1> title. All headings in the markdown document should be at least <h2> but the writer should not need to keep track of that manually. Currently all article subheadings have to start with ##, I think that's probably wrong, since locally they are the highest heading in the document. The rendering should make sure they fit in the heading hierarchy.
This needs to be considered from all angles but as far as I'm concerned the headings in a markdown document should be valid within that document but also be influenced by how they are rendered. For example, articles get rendered with an external `<h1>` title. All headings in the markdown document should be at least `<h2>` but the writer should not need to keep track of that manually. Currently all article subheadings have to start with ##, I think that's probably wrong, since locally they are the highest heading in the document. The rendering should make sure they fit in the heading hierarchy.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This needs to be considered from all angles but as far as I'm concerned the headings in a markdown document should be valid within that document but also be influenced by how they are rendered. For example, articles get rendered with an external
<h1>title. All headings in the markdown document should be at least<h2>but the writer should not need to keep track of that manually. Currently all article subheadings have to start with ##, I think that's probably wrong, since locally they are the highest heading in the document. The rendering should make sure they fit in the heading hierarchy.