5 posts
#frontend
Frontend posts about picking tools by team and task. HTMX in production, Astro 5 for marketing sites, Next.js or Nuxt depending on whether the team writes React or Vue, and the point where Tailwind starts to crack on large codebases. One post covers internationalization of a web app: dates, plurals, currencies, RTL and SEO.
If you are starting a marketing site, read the Astro post first. For an app, the Next.js vs Nuxt piece and the i18n stack matter more. The studio builds web applications and can help pick a stack that fits the project.
Related service: Web application development
(01)
HTMX in production: where it works and where it falls apart
HTMX promises SPA without SPA: attributes on HTML, server returns HTML fragments. Three production projects later — here is where it really is simpler and where it hit the wall.
→
(02)
Astro 5 in 2026 — what to use for a marketing site
Astro 5 has settled in as the default for landings and blogs. What is actually useful from the new features — Server Islands, Content Layer, View Transitions.
→
(03)
Web app i18n stack 2026
Localizing a web app is more than translating strings. Dates, numbers, currencies, plurals, RTL, SEO — all different.
→
(04)
Next.js vs Nuxt 3 — pick by your team
Next.js for React teams, Nuxt for Vue. Technically equivalent. Pick by what your team already knows.
→
(05)
Tailwind CSS at scale — when it breaks
Tailwind ships fast for small projects. On a codebase with 50+ developers and 5 years of history, the cracks show.
→