Timeline for Is using 'heading' Markdown okay in answers?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 31, 2022 at 14:10 | history | bounty awarded | ColleenV | ||
| Mar 29, 2022 at 17:57 | comment | added | ColleenV | @NotTheDr01ds I agree that it's unreasonable to expect users to be intimately familiar with the structure of the surrounding page. Making people aware that they're using elements that have semantic meaning has value though. Some markup doesn't have a strong semantic element, but a lot of it does, and encouraging people to use it more consistently when writing an answer can improve the overall usefulness of a site. | |
| Oct 9, 2021 at 5:41 | history | edited | Mateen Ulhaq | CC BY-SA 4.0 | fix: spelling |
| Oct 7, 2021 at 19:16 | comment | added | NotTheDr01ds | So while I understand accessibility concerns, I think that "markdown" for database content (answers) forces a different perspective. We can't expect users to know the structure of the surrounding page. Today, questions are formatted by Stack as H1's. So does that mean that every answer (that uses headings) should start with H2? No, because (a) it would be not be logical to assume that users are going to look at the HTML markup for the page before doing markdown formatting on their answer, and (b) the page structure could change in the future. | |
| Oct 7, 2021 at 16:59 | history | edited | Super Jade | CC BY-SA 4.0 | Updated headers for accessibility. |
| Oct 7, 2021 at 16:45 | comment | added | Thomas Weller | Nobody prevents SO to render the # markdown as a H2 HTML, since H1 has already been used for the question title. | |
| Oct 7, 2021 at 16:06 | history | answered | Super Jade | CC BY-SA 4.0 |