Docs
Changelog
Latest updates and announcements around the Astro registry, docs shell, and component release work.
June 15, 2026
Branding, audio navigation, and docs catalog polish
A reusable logo mark, navigation sound feedback, working code copy, and a grouped components catalog.
This pass brought the brand identity into the product and tightened a few rough edges across the docs experience.
What changed
- Added a reusable Logo component and brand assets, surfaced on the home page and docs browser shell, with the SDF helper updated to the new mark.
- Played navigation sounds from the click gesture and persisted the audio-unlocked state across pages, so transitions stay audible after the first interaction.
- Made the code-tabs copy button actually work, with a clipboard fallback and a transient “Copied!” label.
- Grouped and alphabetized the components catalog page into a multi-column layout instead of a flat grid.
- Lightened code block surfaces and tidied the global scrollbar and changelog card styling.
Why it matters
The docs now look and sound like a finished product: the brand is present, navigation gives feedback, and copying a snippet just works. Grouping the catalog also makes it easier to find a component as the registry grows.
June 10, 2026
CLI file-update prompts and preview flags
The motion-blocks CLI now asks before overwriting existing files, supports read-only diff and view previews, and never hangs in CI.
This release focused on making the CLI safe to run inside existing projects. Rather than silently clobbering files, it pauses and asks — or skips automatically in non-interactive environments.
What changed
- Per-file write decisions — before any existing file is changed, the CLI shows a diff and asks whether to overwrite, skip, or keep. New files are always created without a prompt.
motion-blocks initconfirmation — re-running init on a project that already hasmotion-blocks.jsonasks before overwriting; declining skips the config write but lets the rest of init continue.- Patch prompts — tsconfig and vite.config patches now show the planned change and ask for confirmation before applying. Declining prints the equivalent manual step.
--yesflag — auto-confirms the dependency install prompt without affecting per-file overwrite safety.--diff [path]and--view [path]— read-only preview flags formotion-blocks add; nothing is written, no prompts are shown.- CI safety — non-interactive environments (piped stdin, no TTY) default to skipping conflicting files instead of hanging. Pass
--overwriteto override. - Outcome summary — after
motion-blocks addfinishes, a count shows how many files were created, updated, skipped, or identical. - React support —
initvite patcher now handles React projects;addpatches JSX custom-element types on React targets. - CLI 0.0.2 — package version bumped with full npm metadata (homepage, repository, bugs, keywords).
Why it matters
Running the CLI a second time used to risk losing local edits. The per-file prompt model removes that risk: you stay in control of every change, and the outcome summary tells you exactly what happened. CI pipelines get the same safety without needing extra flags.