Article
What We Learned About Extending the Nuxt Spine
Our daily work revealed a simpler Nuxt architecture rule: keep the default spine and extend it under each Entity that owns real behaviour.
FireUX
@fireux · 7 min read
Blog
Product notes, field reports and useful ideas from FireUX and the people building with it.
Browse the journal
Stories, notes and releases
16 stories
More from the journal
ArticleAlign the Product Contract, Not Every Interface
Related apps need consistent states, accessibility and behaviour, but they do not need to look identical when their product jobs differ.FireUX
@fireux · 2 min read
- Article
Build a Second Example Before an Abstraction
A second real product example reveals which parts of an architecture are genuinely shared and which only looked reusable in the first version.FireUX
@fireux · 2 min read
- Article
A Clean TypeScript Model Is Not a Data Migration
Why changing an Entity type is only the first gate in a safe data migration, and what must align before legacy authority can be retired.FireUX
@fireux · 4 min read
- Article
From Console to Workspace: Naming a Product Surface
Why FireUX replaced Console with Workspace, and how naming a product surface correctly protects domain ownership as an application grows.FireUX
@fireux · 4 min read
- Article
Derive Product Copy from Real Capabilities
Build product copy from real fields, actions and observable results so landing pages remain useful, specific and technically truthful.FireUX
@fireux · 2 min read
- Article
Turn Your Filesystem into Context for AI Coding Agents
Predictable ownership and folder structure help AI coding agents find the right files and make safer changes with less prompt context.FireUX
@fireux · 2 min read
- Article
How to Turn a Daily Brief into a Valuable Blog Post
A practical method for turning routine daily work into focused blog posts that teach App designers and developers something they can reuse.FireUX
@fireux · 4 min read
- Article
Live and Demo Modes Should Share One Product Surface
Demo data and live data can come from different sources while sharing the same presenter, product states and accessible interface components.FireUX
@fireux · 2 min read
- Article
Not Every Create Flow Should Use the Same Architecture
Classify create flows by where irreversible work happens so simple records, drafts, uploads, onboarding and provider work stay safe.FireUX
@fireux · 5 min read
- Article
Not Every Product Feature Is an Operation
Identity, team, finance, content and operational tools have different product meanings even when they appear together in one Console.FireUX
@fireux · 2 min read
- Article
Build Product Previews From the Real Workspace
A product preview stays honest and maintainable when it composes the same domain-owned Workspace parts people use after they enter the product.FireUX
@fireux · 3 min read
- Article
Public Pages Should Not Read Raw Database Records
Deliberate public read models keep private and operational fields away from browser routes while preserving clear record identity.FireUX
@fireux · 2 min read
- Article
Safe Publishing Must Hash Content, Not Filenames
A reliable publishing plan verifies exact text and image bytes, then uses content-derived image URLs to prevent stale immutable caches.FireUX
@fireux · 3 min read
- Article
Thin Nuxt Pages, Domain-Owned Product Logic
Keep Nuxt pages and API handlers focused on framework boundaries while domain capabilities own validation, policy and product behaviour.FireUX
@fireux · 2 min read
- Article
Turning Daily Briefs into Blog Content Safely
Learn how to turn private daily work briefs into useful public articles while protecting client names, account details, and personal information.FireUX
@fireux · 4 min read