The hidden costs of JS metaframeworks
There are some really important implications of building your web product with a metaframework. These don't get talked about enough.
JSON APIs are a code smell 🌶️
HTMX is so compelling because it actually writes sane frontends for once.
The backend is the final say in state, authorization, and error handling. Expecting the frontend to optimistically duplicate all this logic is an impossible task.
Just use the platform.
The whole MPA vs. SPA debate in web development really was poorly named, obscuring the main point. Here's why.
Introducing support for multiple accounts and server-side rendering
The idea of a JS framework based on Finite State Machines got me thinking
Its really interesting to see JS frameworks shift back towards server rendering.
What if we leaning into web components and treating the DOM as our state?
Interactivity is managed by custom element attributes.
Site logic might boil down to really thin event handlers that querySelect()s a node and toggles an attribute.
This would leave a lot of state logic we’re used to today without a home…
Have state that doesn’t make sense in the DOM? It belongs on the server.
HTML partials would be really interesting here. Leave complex business logic on the server, only asking the browser for enough resources to handle basic user interactivity
What I look for in an SSR router
Routing in an SSR framework is complicated - here's my must-have list for a request routing API.
🎯 2024 prediction
Routing on the web is complicated - our routers should be simple
Great read that’s been making the rounds recently, especially the history of how we ended up with so much client-side rendering
Also highlights what brought me to Astro in the first,
[HTML, CSS, JS]>
[HTML, CSS, ...JS?]
Easily add and debug Fathom Analytics on your Astro sites.
The Surprising Things That CSS Can Animate
When you think of animating CSS properties, which ones come to mind? I recently started wondering about the ones that don’t come to mind — properties that aren’…
Integrating Mastodon profiles with Astro.
Introducing The Astro Showcase
Explore beautiful community websites built with Astro.
Astro Themes & Integrations
Introducing: a growing catalog of themes, components, and integrations to jumpstart your next Astro project.
How to use Web Components in Astro
The power of simplicity
easy to get swept up in the latest libraries and platforms, but don't underestimate the time savings of "boring" tech.
Astro + Foresty CMS Revisited
Static sites powered by Forestry's git-based CMS, made even easier.
Converting our site to Astro
Spoiler - you probably don't need a kitchen sink framework.
Animated page transitions in Astro with Swup
Static doesn't mean boring! Easily add client routing and page transition animations with swup.js
Astro + Snipcart
Scalable e-commerce made easy with the Jamstack.
Astro + Foresty CMS
Static sites powered by Forestry's git-based CMS, made easy.
Class properties in Svelte
A handy trick to make your Svelte components feel even more like plain old HTML.
Astro + Netlify CMS
Static sites powered by a git-based CMS, made easy.
Keeping it simple with Astro
The power of Svelte actions
When you should `use:` actions in Svelte.
A (work-in-progress) minimalist CSS framework.
Including json+ld structured data in Svelte
Easily add json+ld structured data to pages build in Svelte, with TypeScript type checking!
Web Accessibility: Hidden links make all the difference
For visitors that use a keyboard or screen reader to navigate websites, hidden quick links can make a site much more enjoyable.
That's right! Your site built with a JS framework with client-side code can still support users with JS disabled.
The Jamstack is evolving. Where did it start, and what does it look like in 2021?