Client-side input validation is now a cornerstone of user-friendly design. Of course, business-critical validation should happen on the backend. But by catching errors on the front end, developers avoid the “round trip” to the server, which saves time and prevents the existential dread of a 500-error page.

But here’s the irony: we’ve somehow managed to complicate things again. Many popular validation libraries today duplicate functionality already built into modern web browsers. Developers frequently find themselves reimplementing or working around native browser form validation features, rather than using them directly.

Throwback from this summer, I wrote an article explaining how to validate user input in Koval UI.

I added three new chapters to the documentation: Locale-aware formatting, Floating components, Media and Embeds.

Also, I split and extended with new info the previous Apply theme page into the Theme and style chapter.

New documentation is available online. Deployment is done using Vercel and GitHub Workflows. Some pages are still in progress, but the current state is already better than a previous version.

From now on, Koval UI documentation is provided using Docusaurus.