Started writing a decision log for our #DesignSystem. Documenting why we chose to build plain ol' #HTML and #CSS where we can and #WebComponents where client-side #JS is needed is turning into a bit of a manifesto. Essentially we're using (and encouraging others to use) #ProgressiveEnhancement 😉
Here’s my latest case study for a server-rendered HTML of a Mastodon feed with only one progressive enhancement web component (github’s relative-time) — it turned out (surprisingly) pretty good if I may say so myself 🥹
Dites, développeuses z'et développeurs, régulièrement, dans mon cercle professionnel direct, j'entends dire que vous n'aimez pas #CSS (voire #HTML).
Question sérieuse et qui n'appelle pas à réveiller quelconque troll ou débat sans fin : pourquoi n'aimez-vous pas ce langage ?
Qu'est-ce qui vous chiffonne, vous rebute ?
D'où vient votre éventuel manque d'intérêt ?
J'ai déjà des éléments de réponse proches de moi, mais je suis curieux d'élargir la question ici.
I am sincerely wondering how hard it is to style a #HTML checkbox using #CSS. I'd be happy with just aligning them with a label, but this already seems to be asking for a lot. And most answers I find online are already outdated...
It is okay to nest #html <article /> elements so long as they contain a unit of self-contained content that could stand on its own and make sense, but also related to its parent article.
@baldur as someone with such a homepage (probably not that nice, but adaptive layout and translation) I can tell you the main benefit: lowest maintenance costs possible. I only change something when the content has to change.
No language and dependency updates.
No tooling dependencies.
And browser take care to be backward compatible.
Additionally loading super fast.
Team #HTML#CSS only 🤓
We Need to Talk More About Conformance, If We Want to Stop Fantasy HTML:
Conformant and valid HTML is the exception on websites and in apps, even though valid output is a sign of professional web development. Given how rarely the topic is being discussed these days, we benefit from raising more awareness for HTML conformance and validation.
If you have an opportunity to attend this #FrontEnd study hall hosted by @artlung , do it!
The first session was amazing and super informative. As a result, ended up refactoring and simplifying the chaotic mess that was my stylesheets😊 Was unable to attend the second, unfortunately, but looking forward to the third this Thursday.
Kitten now has a lovely new multi-page Settings screen and… drumroll… a new 🐢 interactive shell (REPL) for you to play with the running state of your Small Web site/app/place and debug your app, inspect/manipulate its database, etc.
I plan on recording demos of each of them tomorrow but you can play with them now.
And here’s a little tutorial to get you started with the shell:
I wish the other browser vendors didn't rely so heavily on Google to get the word out. They all do so much work to make these features possible, as do the standards committees, the #OpenUI group, and @igalia, and they all deserve to get more credit.
👉🏼 A SIMPLE CUSTOM
Had reason to re-read this recently.
“For whatever reason some people don’t like the standard HTML checkbox and radio button, they seek to jazz ’em up and in the process the often jizz up the usability/accessibility of these controls.”
I have been reading through the State of HTML 2023 results site (https://2023.stateofhtml.com/) and I am so disappointed in the overall #accessibility efforts — both in the questions and in the code.