v0.0.3

A consistency pass over the component API, from the sweep /lumos-audit-props now performs. No behaviour changes — every difference here is felt in autocomplete rather than at runtime.

Changed

• Eyebrow declared variant before tag, where Heading and Paragraph declare tag first. It now matches them, and its destructuring follows its declaration.
• Sixteen props had no tooltip: every Section spacing prop, Heading and Paragraph's tag and maxWidth, RichText's maxWidth, Button's element, disabled and href, and Select's variant.
• Fifteen numeric props stated no range. They now carry @min / @max / @int, as Grid and Overlay already did.
• Paragraph and RichText stated a default in a sentence while every other option list marked the option itself. Both mark the option now.
• Input and Video documented a variant without saying what the options were.

Notes

The audit skips components whose props span a discriminated union — Button, Card, Grid, ContentWrapper and four others. A union writes its branches in the order the variants demand, so there is no single declaration order to compare, and those are listed for a hand read instead of reported as drift.

v0.0.2

Fixed

CI has failed on every commit since the example components page was written. Slider, Modal, Accordion and AccordionItem — plus uid.ts, which they all import — existed locally but were never added to git, so the runner checked out a tree where that page imported four missing modules. They are tracked now, and CI is green.

Added

Five skills, in .claude/skills, shipped with the framework and with any site scaffolded from it:

• lumos-import-figma — build a page or fill in variables from a Figma file, converting px to rem, line heights to unitless, and Figma's faked opacity back to color-mix
• lumos-import-webflow — move a site off Webflow, reading what the code export can prove and asking the Webflow API for the CMS and component bindings it strips
• lumos-upgrade-version — move a site onto a newer Lumos without losing its customizations, three-way merged against the commit it was scaffolded from
• lumos-audit-props — sweep the component library for prop order and tooltip consistency
• lumos-scaling-graphic — build an illustration that scales as one piece while staying real elements

Changed

create-lumos resolves main to a commit before downloading, and records it in the new site's package.json. Scaffolding is reproducible, and an upgrade can tell which Lumos a site started from instead of guessing. Ships with the next create-lumos publish.

Components are grouped into Form, Global, Interactive, Item, Media, Typography, Utility and Wrapper, and the form components have dropped their Form prefix — FormInput is now Form/Input.

v0.0.1 — Beta

The first tagged release of Lumos For Astro, a component and styling framework for building Astro sites.

This is a beta. The component API is still settling — expect prop names to move before v0.1.0.

What's in it

Styling — four cascade layers (base, patterns, components, utilities), fluid type and space scales, and four theme classes (theme-light, theme-dark, theme-brand, theme-invert) that anything can be dropped inside.

Layout — Section, ContentWrapper, Grid, ButtonWrapper.

Content — Heading, Paragraph, RichText, Eyebrow, Card, Button.

Media — Img, Video, Icon, Overlay.

Chrome — Nav, Footer, SkipLink, BaseHead, FormattedDate.

Every component takes a render prop to skip itself and its children, and components that would render nothing skip themselves.

Getting started

npm install
npm run dev

Node 22.12 or newer. See the README for how the cascade and theming fit together.