Explore Base64, Base85, Ascii85, and Z85 encoding with Python
#python #flask #htmx @htmlallthethings
@linux
@python_discussions
@brianb
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)
- https://wagtail.org/blog/htmx-accessibility-gaps-data-and-recommendations/ (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.
-->--
Ever wonder about the accessibility of htmx UIs? We have too ️ https://wagtail.org/blog/htmx-accessibility-gaps-data-and-recommendations/ Includes a review of the available data, common gotchas, and recommendations to navigate those challenges, with a particular focus on the #django ecosystem
Colophon for https://beesocial.dev for anyone interested: https://beesocial.dev/colophon.
No vibe coding, just good vibes.
> 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”.
Ils sont sympas chez htmx, ils vous expliquent même comment vous passer d'htmx tout en réalisant des applications qui correspondent à ce qu'htmx permet. Et il y a quelques pépites là-dedans ! https://htmx.org/essays/alternatives/ #htmx #alternatives #web #html
Introducing the Django-Spellbook Editor:
https://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; https://github.com/wagtail/wagtail
#HTMX is growing on me.
It felt weird at first to generate frontend from the backend. But I gave in because writing more code at the backend was way too tempting. I just can't hold #javascript right.
Using templates and SQL, creating frontend using #php and htmx is pretty nice. Kind of feel like doing #graphql and #Rest together.
But at the end of the day, I am writing less javascript and it is great.
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!
Why not only htmx for a web site...because..
https://www.synthetic-depo.com/
Discussions: https://discu.eu/q/https://www.synthetic-depo.com/
If you are a Python web developer and would like some frontend superpowers without the Javascript fatigue, consider joining my upcoming modern frontends learning sprint.
See you @JavaForumNord this year! #htmx #hypermedia
Okay, No pressure but my Session at #SpringIO25 ist now officially one with high number of people interestet in the topic. Even it isone of the final sessions on the first day. #htmx #hypermedia #java
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 :-)