Less interface, so the content leads.

3lastic.com teresastudio.art sebastianunda.com
  • Astro
  • Tailwind CSS
  • Firebase Hosting
  • MDX
  • Umami

Redmirror serves two purposes

Sketch of the same interface in a browser and on a phone, with the NavPill component marked on both

Showing how we build a design system. The ones we have built for clients are under NDA; this one can be explored end to end.

Keeping our own sites on a solid foundation, fitted to the way we understand work done well.

What we believe

Sketch of a human figure with open arms

The reader matters more than the designer

Contrast, accessibility and speed are not a compliance layer. They are what makes the page work for the person using it, not an extra bolted on at the end.

Sketch of a document with a crown on top

Content leads

Whatever serves the content stays; whatever doesn't, goes. Typography gets the care because it carries the message. No animated text, no motion that doesn't support what is being said: every layer earns its place or stays out.

Sketch of two stacks of shapes: an unstable one next to an ordered, stable one

Subtraction over accumulation

Faced with an improvement, the first question is what can be removed. The system gets better by shrinking, not by growing.

How we sustain it

Sketch of three arrows that cross and leave aligned in the same direction

How we understand the system

A system is not a folder of components. It is the dialogue between what we want, how we build it and how it evolves, aligned so that message and brand never contradict each other.

Sketch of arrows under a line, with a check mark inside and a question mark outside

How something gets into the system

Nothing gets in for being fashionable. A need is solved first on a real site; if a second site asks for it, it is abstracted and promoted. If only one site needs it, it stays on that site. One case is not a pattern.

Sketch of an open hand holding a small robot

Assisted development protocol

We work with AI on the sensitive part —the interface— with a workflow that decides who touches what, and what is never touched. These are the documents that govern it.

Accessibility is not a promise, it is a fact

Accessibility lives in the system, not in each site: whatever the system guarantees, it guarantees on all of them. This is what is already done.

Sketch of two letters A joined by a plus sign, with the note a11y above
  • Semantic structure. Real headings, landmarks, lists. Assistive technology navigates the page instead of guessing it.
  • Keyboard. Everything you can press is reachable without a mouse, with visible focus.
  • Contrast. Text meets AA against its background, in light and in dark.
  • Reduced motion. If your system asks for less motion, transitions and reveals switch off.
  • Text that adapts. The layout holds up under text zoom without breaking.

No site is perfectly accessible. If you run into a barrier we missed, we want to know: hello@3lastic.com. We will fix it in an upcoming release.