Blog
All articles tagged 'architecture'
-
Reference architecture for SPA front-ends
external A reference architecture for SPA front-ends with React and Angular, focused on principles instead of rules. -
The case for state machines in client-side applications
Features that seem simple can become unmaintainable due to unforeseen state management issues. State machines help avoid this. -
Scalable CSS architecture
In the last two years, I found that my CSS architecture was becoming too complex. But, utility-first frameworks were not doing it for me either. I needed a mix, I needed utility-enabled. Then came CUBE CSS and it all clicked. -
SWR-like data fetching in Svelte
I am a big fan of the [SWR](https://swr.vercel.app/) package of Vercel. Let's see how to implement something similar in Svelte. -
State machines and state management
updated! State management is one of the most complicated, and opinionated topics in modern and JavaScript-focused front-end development. Let's make it easier. -
Authentication token management
Complex client-side applications require sophisticated solutions around authentication management and background refreshing. -
Interdependencies and code stability
updated! As engineers, we have the tendency to over-engineer our solutions, make our code as reusable as possible. We make our code DRY. But in this quest, we often create unstable code. -
Binding CSS and JavaScript with HTML data-attributes
HTML data-attributes allow you to bind CSS and JavaScript more closely to each other. By utilizing this type of attribute, you can reduce the amount of JavaScript required for styling, and move this responsibility back to CSS. -
Demystifying the component architecture
Our little UI components do more for us than we give them credits for. Their internals are more complex than we know. -
How to create a scalable and maintainable front-end architecture
A modern architecture for digital enterprises build on existing ideas, but let you scale quickly -
Interfacing your UI components
Interfaces are everywhere, for users and developers, so why not use them?