v0.0.4older

Documentation version

Currently searching v0.0.4

Search pages, component props, utilities and tokens.

↑↓ to move to openesc to close

Open files in your editor

On a Mac, right-click the folder in Finder, hold Option, and choose Copy as Pathname.On Windows, hold Shift, right-click the folder, and choose Copy as path, then delete the quote marks.

GuidesLumos 0.0.4New

Upgrading Lumos

Move a customized site to a newer Lumos release without losing project work.

A site created by v0.0.4 records its Lumos version, exact source commit and scaffold date under lumos in package.json. The lumos-upgrade-version skill uses that commit as the merge base, so it can tell framework changes apart from your changes.

How the merge protects your work

Your copyNew Lumos copyResult
UnchangedUnchangedLeave the file alone.
UnchangedChangedTake the new Lumos file.
ChangedUnchangedKeep your project version.
ChangedChangedMerge both changes and report the decision.

Pages, content and assets belong to the project and are never replaced. base.css is merged token by token so new framework defaults arrive without erasing brand colors, typography or spacing. Renamed components, paths and props are then migrated through project-owned code.

The verification

  1. Run astro check and astro build until both are clean.
  2. Capture every route again at desktop and mobile.
  3. Compare the images and investigate every difference above the workflow's tolerance.
  4. Update the package.json source stamp and commit the reviewed upgrade.