November 5, 2026
A straight account of what changed in Nida over the last few weeks.
The design library, rebuilt
The website builder starts from a library of art directions, and that library was uneven. Some directions were thin paragraphs. Some previews looked like wireframes.
- 2,000 of the 2,003 design directions were rewritten into a full specification: palette, type scale, grid, section rhythm, motion, imagery rules, calls to action, accessibility, and the things a design should avoid.
- 1,574 preview pages were rebuilt and re-photographed so the library shows what the builder actually produces.
- Text over photography, the thing that made the most pages look unfinished, is now handled twice: the generation contract requires a scrim or a solid panel, and a runtime pass measures where text and images actually overlap and shades only those areas.
You can walk the whole library at nida-os.com/designs.
The bug hunt
We went through the modules you use most and fixed what was broken rather than what was easy to test.
- Booking and calendar: confirmation emails that were silently skipped, a premium booking-link flow, attendee replies sent from your own mailbox, working manage links, and slot collisions answered properly under race conditions instead of with a generic error.
- CRM: lead notes and tasks that never loaded behind a permission check, a pipeline stage board, and a lead drawer that shows every answer a form captured rather than a hand-picked subset.
- Reviews and support: review links that no longer live forever, tenant markup sanitised, and support and review defects closed in the same sweep.
- Security: tighter public routes, scoped CORS, and asset paths audited.
- Speed: the design previews and the documentation no longer ride along in every deploy, which brought a three-minute deploy down to about two.
The business card module
A Nida business card is a shareable page at your own address, not a PDF. It carries your photo, logo, services, links and a direct line to you, and it works as a small website on its own.
- One link you can put in an email signature, a QR code, or a text message.
- View and save counts, so you can see whether it is being used.
- Services, social links and contact details you can change without reprinting anything.
- It can carry a booking action and a chat, so a card can turn into a conversation.
Here is a live one: nida-os.com/c/stephenclarke. Cards can also sit on your own domain, so a client sees your brand, not ours.
What the builder produces now
Three examples from the rebuilt library, generated end to end by Nida:
Each one is a single generation: plan, copy, layout, imagery and motion, from one brief.
What comes next
The next pass is depth rather than surface: fewer new templates, more work on the parts that decide whether a site earns its keep, which is speed, search visibility, and the handoff from a visitor to a real conversation.
If something still feels wrong, tell us the exact steps you took. We would rather hear it early than have you find it twice.
← Back to the blog