Latest version of #HTML standard includes a warning that advises against using the #XML syntax (formerly known as #XHTML), stating that it's "essentially unmaintained"🧐 :
I'm only just finding my way in the land of #htmx, but it feels like "trigger a request from any #HTML element" is a trap. I want progressive enhancement, which still requires a functional non-Javascript page before adding the nice things htmx offers. I didn't realise how rusty I am with regard to designing a presentation layer for all this in the backend.
I just published my first #Wix site today. I have limited experience with similar site builder services like Square Space and Weebly.
Is Wix typical of these kind of tools? I found it to be extremely difficult to use. On the plus side it almost gave me every ability I could produce as an actual developer... almost.
Less would have been more in the case of Wix. Just because you can stuff every possible feature into a Web based WYSIWYG builder doesn't mean you should.
It made it really hard to produce a simple and elegant site that is really what's needed by most people using such a service. If you truly have a need for the advanced features, trying to do those through multiple layers of nested menus is the worst way to do it. You might as well as hire a developer and do it the right way.
This site coulda been an email. Instead it was an insane toothpick tower that kept exploding on me b/c nothing played nicely with anything.
@sysop408 a few years back when I launched my first page on Wix, I felt that the overall experience was fairly straightforward and to the point...plus some of the analytics and plug-ins available were nice, too.
That being said, after a years subscription of the Pro version ended, I chose to leave the platform and self-host my own page.
My advice, find a nice #React template and build your own...or #HTML if it's just static.
Much more flexibility of component design! 😎💯 :html5: :react:
I found https://buildexcellentwebsit.es extremely insightful and inspiring! It pushed me to finally completely restructure my personal website’s #CSS, after many years of mess.
Unfortunately, though, I find the massive use of all those calc() and clamp() functions to be quite heavy in terms of performance… #Lighthouse gave the website a very bad performance score (see screenshot). It even seems that while scrolling the page it lags (😳) even if it’s super simple and built with pure #HTML and CSS!
Do you have any ideas or suggestions? 🤔
Thank you so much for all the interesting things you share! ❤️🚀
(The current unstable development version of my website is at https://dev.tommi.space/, I am using the homepage as reference)
In 45 minutes I made a #kotlin#javalin application from scratch, which uses #webjars to include #htmx from a #maven pom file. It uses static #HTML files for the first load, and then renders HTML from #jte templates for #SSR of the parts of the pages that need that kind of interaction. There's no #springboot (or any #spring at all) and no #SPA like #angular or #react.
Now because simply setting up a project says close to nothing about its real world viability, next step is an actual usecase ( :
So Kitten’s build process (i.e., the time it takes to build Kitten itself) takes ~0.7 seconds on my ~1 year old desktop (Ryzen 7 5700G 3.8Ghz) vs ~1.4 seconds on my ~3-year-old Starlabs LabTop (renamed to the Starbook thanks to a suggestion by yours truly but sadly, not quickly enough).
So, in summary, it’s bloody fast for something that results in a ~9MB bundle.
Note that when you’re working with Kitten, your apps do not have a build process.
You write HTML, CSS, JavaScript and, optionally, extend using first-class support for htmx and alpine.js as well as Kitten’s own Streaming HTML workflow¹. There’s also no scaffolding or generating a project with hundreds of files or anything. You just write the code for your app.