mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#htmx

0 Beiträge0 Beteiligte0 Beiträge heute

Put together a pretty cool live @ListenBrainz widget on my website! Auto-updates every 10 seconds, and shows as much metadata as I can cram into the widget space. All that metadata is the bonus of ListenBrainz being so closely tied to MusicBrainz

(and don't worry, I have some pretty aggressive caching so I won't hammer the ListenBrainz or MusicBrainz APIs)

piperswe.me/#playing-now

www.piperswe.meComputers? Computers. - Piper McCorkle's Personal Web Site

- wagtail.org/blog/htmx-accessib (htmx accessibility gaps: data and recommendations. A look at available data, known gotchas, and how to address the gaps)

--<--

Recommendations

Accessibility gets a mention in the htmx docs as part of Progressive Enhancement. This is a bit light on details for my liking, and I think oversimplifies what it means to build accessible UIs. Those oversimplifications are common in online htmx resources. I’d phrase them as:

- ❌ Simple HTML is all you need. That’s true – except when your UI becomes complex enough that it’s not.

- ❌ The least JavaScript the better. Also somewhat true – except when it leads to leaving out essential accessibility considerations.

-->--

Wagtail CMShtmx accessibility gaps: data and recommendations | Wagtail CMS
Mehr von Wagtail
Antwortete im Thread

@slightlyoff

> There is a better way. And it doesn’t require a complete rewrite of the internet or a return to 2005.

The way’s #HTMX – server-side rendering, clean accessible html, but with interactive controls unavailable in 2005 (or even today in pure html). But no complex “frontend-side logic”.

Introducing the Django-Spellbook Editor:

django-spellbook.org/editor/

I've been working on this project for the last week, I want to integrate it into a /sb-admin url similar to how #wagtail does it, but as a much simpler lightweight markdown parser.

Right now it's only available on the docs website for testing purposes :) please try it out, I hope you like it!

It's made through #HTMX and vanilla JS , so would it be too much of a hassle to require people use HTMX to use this library's admin editor? I guess I have to explore Wagtail's code and see how they did it; github.com/wagtail/wagtail

#Django#Python#markdown

Just added #HTMX to a #Django project. Performing a lazy loading of one part of a dashboard and allowing to change the period of it (month/year) without reloading the entire screen. It was simpler than I expected. Still need to add some error handling (I saw few examples of it!) and probably I'm organizing the template in a way that won't scale in a bigger project, but it is a good start!

I've been playing with #RustLang again.
Using #Axum #Handlebars #Htmx #Sqlx and #Sqlite
It's a really joyful environment to work with. I'm finding it far easier than last time, a combination of much improved compiler errors, clippy guidance, #VSCode also seems to have improved understanding of the code (I'm not using #AI just Rust-Analyser and Even Better TOML
Plus I'm building depth rather than width, fits much better for exploration and learning.
The amount of syntax feels much reduced :-)