The contrary of HTMLHell, a page full of tips: HTML Heaven.

Documents will be available in HTML!

Lessons from maintaining an open source tool:

1. Simplicity is a feature
2. Real users reveal problems
3. open source is a marathon

Yet through all these changes, the need for efficient HTML delivery remains constant. That's perhaps the most interesting lesson: fundamental problems persist even as technologies evolve.

An example of semantic class names and a teaser on server of Kelp to have dynamic HTML through WebComponents.

Not read yet.

It was one of those moments where something you once knew suddenly clicks again with fresh significance. Here was a URL doing far more than just pointing to a page. It was storing state, encoding intent, and making my entire setup shareable and recoverable. No database. No cookies. No localStorage. Just a URL.

Good candidates for URL state:

• Search queries and filters
• Pagination and sorting
• View modes (list/grid, dark/light)
• Date ranges and time periods
• Selected items or active tabs
• UI configuration that affects content
• Feature flags and A/B test variants --> I never though about this one

Anti-Patterns to avoid:

• state only in memory SPAs
• sensitive Data in URLs
• inconsistent or opaque naming
• overloading URLs with complex state
• breaking the back button

Another post about semantic HTML, or the UX of HTML with <button>

The content is similar to The HTML Output Element from Matthias Ott or HTML’s Best Kept Secret: The

Tag — Den Odell

.

They advocate for better usage of <output> instead of aria attributes. Let's use native instead of ARIA!

edit: I am deceived by all the quirks

Under accessibility, but this tag should be the norm

<output> is currently underused in so many SPAs and apps, because it announces

1. Convert the PDF in a browser or automate it using a browser automation tool
2. https://weasyprint.org/ / https://stirlingpdf.io/

and more

Raw HTML and CSS?

1. It's fast
2. It's easy
3. Pure HTML is evergreen
4. I can host it anywhere, often for free
5. Accessibility and SEO benefits are automatic
6. It won’t need security patches
7. There are no build steps

I totally agree: using HTML as much as possible, then CSS, then JS to enhance it in this order.

The API can respond with HTML fragments anyway for an HTML table.

Seach content in collapsible sections.

That's great!

Some different ways to write HTML

Put an id inside the <details> body