v0.11.0

v0.11.0 - 2026-10-27

Features

• (skill) turn the fidelity review into a checklist - (062eb1e)
• (skill) review the fidelity check in overviews and slices - (27c3dbd)
• give the split's link a button style - (a1244bb)
• pin a header button beside the menu button - (52498d4)

Miscellaneous Chores

• (version) v0.11.0 - (7e09302)

v0.10.0

v0.10.0 - 2026-10-25

Features

• give every titled library section an eyebrow - (9434c06)
• (skill) ship what the Webflow demo's first run found - (10fd2fb)
• add title and description patterns per collection - (33b98ae)
• let the site config turn the breadcrumb off - (faf182f)
• fill facts in a Markdown body's link addresses - (f37b6cb)

Miscellaneous Chores

• (version) v0.10.0 - (b7ed472)

v0.9.0

v0.9.0 - 2026-10-24

Features

• add the agent rules, a brief and a Webflow migration skill - (c6a7d0b)

Miscellaneous Chores

• (version) v0.9.0 - (feb7d97)

v0.8.0

v0.8.0 - 2026-10-24

Documentation

• link the hostsmith.net docs, fix the schema export steps - (fd16764)

Features

• add interactive parts, highlights, site icons, a webflow example - (23a422e)

What's new

• Interactive parts: the section types tabs, slider and embed; lightbox: true on a gallery; video, with an optional videoWebm, on a hero with the variant background and on a split; children on a nav item, one level deep; and reveal on any section. Each part works by keyboard, shows all of its content without scripts, and moves nothing under reduced motion. Its script renders only on the pages that use it. See Interactive parts.
• Embeds load on a click: an embed sends nothing to its provider until the visitor presses its button. YouTube then loads from youtube-nocookie.com, and Vimeo with dnt=1. A Markdown paragraph that holds only a YouTube or Vimeo link renders as the same placeholder.
• Interface strings: the parts' fixed text comes from new ui keys. They are optional, so a site that uses no part needs none of them. A page that renders a part fails its build without the part's keys, naming the key and the settings file.
• Highlights: ==word== in any title renders the word in span.sk-highlight for the theme to style. The marks are removed from the page's <title>, og:title, breadcrumb and alt text.
• Site icons: an SVG in src/icons/ is an icon that every icon prop and the CMS accept, by its file name. The build fails, naming the file and the reason, on an icon that sets its own colors, holds a script or styles, links outside itself, or has a kit icon's name.
• Footer logo: the footer's brand block takes its own logo and logoAlt, such as a reversed logo on a dark footer.
• Kit icons: chevron-down, chevron-left, chevron-right, pause and play.
• The webflow example: every section type, variant, tone and part, in a structural theme with Webflow's breakpoints and element defaults. It's the start for porting a Webflow design, with --template hostsmith/site-kit-astro/examples/webflow#v0.8.0, and it's live at kit-astro-webflow.us.hostsmith.link.
• Themes: a theme may set the sm and lg breakpoints, and change token values per breakpoint. Its README.md lists the section types and parts it styles. HOOKS.md lists the parts' hooks under "Parts".

Behavior change

• A title that already holds a pair of == now shows the text between them as a highlight, and loses the marks. == can't be escaped, so reword such a title before the update. To find them: grep -rnE "title: .*==.+==" src/content. A lone == still shows as written.

Updating

• Follow Kit updates. npm run decap-config and npx site-kit schema add the new fields to public/admin/config.yml and .hostsmith/schema.json: commit both. No content file changes. Until the theme styles a new part a page renders, npm run check:styles -- --built warns about each of its hooks.

Miscellaneous Chores

• (version) v0.8.0 - (2593b34)

v0.7.0

v0.7.0 - 2026-10-23

Features

• split the package into a core and a kit layer - (985b7bf)

Behavior change

• A kit site with a non-static output now fails its build: output: "server" in astro.config.mjs, or a page or endpoint with export const prerender = false. The error names the setting or the route. Hostsmith serves static files only, and no kit page works without prerendering, so such a build never made a working site. A site that leaves output unset, as the examples do, builds as before.

Miscellaneous Chores

• (version) v0.7.0 - (e2c5b1c)

v0.6.2

v0.6.2 - 2026-10-19

Bug Fixes

• never load sharp, check licenses, examples under MIT-0 - (5dbc296)

Documentation

• point the 0.6 update steps at the v0.6.1 release notes - (9664704)

Miscellaneous Chores

• (version) v0.6.2 - (9b81c0a)

v0.6.1

v0.6.1 - 2026-10-19

v0.6.1 is the first 0.6 release on npm. v0.6.0 was tagged but never published, since its tests failed after its tag was pushed. Its changes and a site's update steps are below.

Breaking changes: locales for every site, interface strings and CMS fixes

a site's pages and URLs don't change, but its content files are renamed once. To update a site (README, "From 0.5 to 0.6"):

1. Rename every content file with git mv, with the default locale's code before its extension: pages/about.md becomes pages/about.en.md, and settings/site.yml becomes settings/site.en.yml.
2. Add locales to src/site.config.ts, with the settings' language as the tag, such as [{ code: "en", tag: "en-US" }], and delete language from the settings.
3. In src/site.schema.ts, declare each collection by its schema alone, such as news: { schema: ... }, and remove the imports of defineCollection and glob.
4. Move each custom page's own props into sections, and remove the custom pages' files collection from public/admin/config.site.yml. Then drop its template: custom and its hand-written page, or move its markup to a page template in src/components/pages/, as basics' about page does. customPage takes no props, a hand-written page names its entry with its locale, such as customPage("about.en"), and pagePath is gone.
   Then run npm run decap-config, npm run check:styles, the build, npm run check:urls and npm run check:styles -- --built. Field attributes now name the locale, such as settings/site.en#name.

Bug Fixes

• test a release before pushing its tag, compare with v0.5.2 - (74bbc04)

Features

• BREAKING locales for every site, interface strings and CMS fixes - (63413bf)

Miscellaneous Chores

• (version) v0.6.0 - (50cdd32)
• (version) v0.6.1 - (3bbe149)

v0.5.2

v0.5.2 - 2026-10-17

Bug Fixes

• close the gaps a 0.4 site hits when taking 0.5 - (d360bea)

Miscellaneous Chores

• (version) v0.5.2 - (70ee41b)

v0.5.1

v0.5.1 - 2026-10-17

Bug Fixes

• wait for npm to serve a release before checking it - (8592b95)

Miscellaneous Chores

• (version) v0.5.1 - (31c8d41)

v0.5.0

v0.5.0 - 2026-10-17

Breaking changes: make the kit designless, with styling hooks and the Kestrel example

Update: the steps below leave out six that a 0.4 site needs. Take v0.5.2 or later and follow the README's From 0.4 to 0.5 checklist alongside them. It also corrects step 5: footer.links and social go in one untitled links block, since two fail the build.

the package's styles.css export and its Tailwind setup are gone, every kit class is replaced by sk- hooks, settings need new ui strings, and the header and footer settings become blocks. To update a site:

1. Add tailwindcss and @tailwindcss/vite at exact versions, and the Tailwind Vite plugin in astro.config.mjs.
2. Copy src/styles/global.css, src/styles/theme/ and public/assets/fonts/ from the basics example. To keep the site's colors, write them as a preset in theme/presets/colors/ with the roles in the README's theme section, and point theme/tokens/colors.css at it.
3. Move the site's own CSS to src/styles/site.css.
4. Add the new ui strings: mainNav, footerNav, breadcrumb and home.
5. Rewrite the header and footer settings as blocks (README, "Header and footer"): footer.text becomes a brand block's text, contact a contact block (plus a phone action to show the number in the header), and footer.links and social links blocks in footer.bottom, after a copyright block. Write values that repeat, such as the phone number, as facts.
   Then run npm run decap-config, npm run check:styles, the build, and npx site-kit check-styles --built.

Documentation

• create sites with --no-ai to keep the example's AGENTS.md - (95d9039)

Features

• BREAKING make the kit designless, with styling hooks and the Kestrel example - (cce4c9d)

Miscellaneous Chores

• (version) v0.5.0 - (108cad4)