#[schmarty]i try to keep things to the ol' standard of one h1 per page and try not to nest more deeply than an h3.
#jackyI use a lot of the HTML5 tags and IIRC they suggest adjusting levels as things like <section>, <article> etc get deeprr
lagash joined the channel
#[schmarty]jacky: implied / reset heading levels in nested sections/articles has (finally) been removed from the HTML spec because browsers never implemented it đ
#[tantek]!tell snarfed is there a corollary or "future" to "manual until it hurts" where what do you do when the automation breaks and becomes unmaintained / unmaintainable? I feel there's more to the story of "manual until it hurts" (perhaps not enough for a flow chart, yet). example, what happened to: w3.org/Terms
#[tantek]even <section> and <article> have likely caused more authoring headache than benefit for users
#[tantek]jacky, [schmarty] yeah, depth 4 is about the most for me in practice too. Good, I didn't bother designing beyond depth level 4 for an actual human readable (without wondering, what's this gibberish) plain text expression of headings
jacky, abetusk, AramZS, jonnybarnes and [snarfed] joined the channel
#[snarfed]capjamesg: I'd want someone else to _drive_ a new Indie Map crawl, not just help...so it's up to them, not me, if it happens!
#Loqi[snarfed]: [tantek] left you a message 13 hours, 59 minutes ago: is there a corollary or "future" to "manual until it hurts" where what do you do when the automation breaks and becomes unmaintained / unmaintainable? I feel there's more to the story of "manual until it hurts" (perhaps not enough for a flow chart, yet). example, what happened to: w3.org/Terms
#[snarfed]and thanks re hackermention! my initial idea would have been really small and simple, but Firebase doesn't support it đĸ https://stackoverflow.com/a/73355286/186123 , so I'm doing it the more traditional way, ah well