astro-webfinger 2.0
Introducing support for multiple accounts and server-side rendering
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
Routing in an SSR framework is complicated - here's my must-have list for a request routing API.
🎯 2024 prediction
Google announces that JavaScript execution will be disabled again for search crawlers
URLs are a fundamental part of the web, and a surprisingly complicated problem. Routing in JavaScript frameworks keeps getting more complex — it's about time we standardize on a simple, universal spec.
Great read that’s been making the rounds recently, especially the history of how we ended up with so much client-side rendering
https://dev.to/oxharris/rethinking-the-modern-web-5cn1
Also highlights what brought me to https://astro.build in the first, [HTML, CSS, JS]
> Build_Step
> [HTML, CSS, ...JS?]
Easily add and debug Fathom Analytics on your Astro sites.
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.
Explore beautiful community websites built with Astro.
Introducing: a growing catalog of themes, components, and integrations to jumpstart your next Astro project.
Building custom elements in plain old JavaScript + trying out the new Astro.resolve() API!
easy to get swept up in the latest libraries and platforms, but don't underestimate the time savings of "boring" tech.
Static sites powered by Forestry's git-based CMS, made even easier.
Spoiler - you probably don't need a kitchen sink framework.
Static doesn't mean boring! Easily add client routing and page transition animations with swup.js
Scalable e-commerce made easy with the Jamstack.
Static sites powered by Forestry's git-based CMS, made easy.
A handy trick to make your Svelte components feel even more like plain old HTML.
Static sites powered by a git-based CMS, made easy.
Do you really need all that JavaScript?
When you should `use:` actions in Svelte.
A (work-in-progress) minimalist CSS framework.
Easily add json+ld structured data to pages build in Svelte, with TypeScript type checking!
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?