A collection of thoughts about HTML, CSS, JavaScript, UX, a11y, web standards, and related things. Posts by Cory LaViska.


Quiet UI is Now Open Source

Written on

About a month ago, I released Quiet UI under a source-available license. The idea was to make it free for personal, educational, and non-profit use while requiring payment for commercial licenses.

Quiet UI: My Creative Outlet

Written on

I recently released a side project called Quiet UI. It's, perhaps unexpectedly, a component library. This begs the question:

How I Use GitHub Issues

Written on

I like using GitHub issues for actionable things such as bugs and backlog items I've committed to doing. Non-maintainers are encouraged to open issues only for bugs, whereas everything else is a discussion.

Revisiting FOUCE

Written on

It's been awhile since I wrote about FOUCE and I've since come up with an improved solution that I think is worth a post.

Web Components Are Not the Future — They’re the Present

Written on

It’s disappointing that some of the most outspoken individuals against Web Components are framework maintainers. These individuals are, after all, in some of the best positions to provide valuable feedback. They have a lot of great ideas!

Component Machines

Written on

Components are like little machines. You build them once. Use them whenever you need them.

Styling Custom Elements Without Reflecting Attributes

Written on

I've been struggling with the idea of reflecting attributes in custom elements and when it's appropriate. I think I've identified a gap in the platform, but I'm not sure exactly how we should fill it.

Reflection and Custom States in Web Components

Written on

In the Web Component world, attribute reflection is commonly used to style custom elements both internally and as public APIs for consumers. If you're not familiar, attribute reflection occurs when an attribute in the DOM is updated due to changes in a corresponding property.

Anchoring Software to Major Versions

Written on

In a SemVer world, major releases are those which contain incompatible API changes. We often see software projects anchor themselves to major versions for long periods of time, usually with the promise of stability.

Building Custom Elements With a Library

Written on

I often get asked why I use Lit to build web components. Hands down, it's become my preference after years of working with various libraries and tools. Here's why I use it.

Feeds available in Atom & JSON


Explore the archive for additional posts or press / to search.