v0.1.1

What's changed

The dev server was missing half your edits: ?t= cache-busted the template itself, but a relative import does not inherit the query, so a shared theme.ts or a color constant stayed frozen in the module cache until a restart. Editing what a template imports now shows up on the next refresh, thumbnails included.

• An unknown URL answers with a real not-found page in the browser window, pointing back to the nearest folder that exists, instead of a line of plain text.

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Full Changelog: v0.1.0-rc.6...v0.1.0

v0.1.0-rc.6

What's changed

Every user-facing string is now in English: the CLI help and errors, the engine's error messages, the dev server's interface, and what generated projects print or ship (Calame's asset scripts, fonts/NOTICE.md). create-brand-artisan and the docs already were.

Full Changelog: v0.1.0-rc.5...v0.1.0-rc.6

v0.1.0-rc.5

What's changed

A LinkedIn carousel is now delivered as what LinkedIn actually accepts: one PDF.

• New brand-artisan pdf <project>/<folder>: assembles a folder of slides into a PDF, one slide per page. LinkedIn paginates it into a swipeable document post; the same images posted directly come out as a mosaic.
• Pages follow natural order (card-2 before card-10), and mixed ratios are refused since LinkedIn takes the document's ratio from its first page.
• The dev server offers a folder's PDF as soon as it exists, and warns when a slide is more recent.
• Calame ships a five-slide demo carousel, and the linkedin-carousel skill now asks which kind you mean: document post (PDF) or carousel ad (1:1 PNGs).
• Fixed: portrait visuals overflowed the gallery view.

Full Changelog: v0.1.0-rc.4...v0.1.0-rc.5

v0.1.0-rc.4

What's changed

A polish release, split between the dev server and the generated skeleton. The rendering engine is untouched.

• The dev server pages now carry a favicon: the BrandArtisan mark, inlined as a data URI in the shared window shell, so every page gets it with no extra route and no file read.
• Both READMEs open on the project's social preview, the same image set as the GitHub social preview. It is referenced by its absolute raw URL, since README.md also renders on npm where relative paths break.
• Generated projects brief their agents better. A new "How to work" section condenses the engine repo's own working principles into what a visuals project can actually use, including the rule that committing and pushing each need an explicit go-ahead. The instructions also state that Calame is an example, not a model: its code shows how the API is consumed, but its palette, type and compositions belong to Calame alone, and a new project starts from its own guidelines.
• Generated projects no longer version skills-lock.json: it is rebuilt by npx skills, like the installed skill copies, so it does not belong in the repository.

Full Changelog: v0.1.0-rc.3...v0.1.0-rc.4

0.1.0-rc.3

What's changed

Two fixes in the generator, both about the first minute of use. The engine is unchanged and rides along, both packages having to carry the same version.

• npx create-brand-artisan . no longer ends on cd <folder>, pointing at the directory you already stand in.
• Generated projects install silently again. npm 12 blocks install scripts unless allowed, so every new project greeted its owner with a warning about esbuild's postinstall. The skeleton now records "allowScripts": { "esbuild": false }, since that script is not needed here: esbuild delivers its platform binary through optionalDependencies. The generated README says how to allow it instead, on a platform where that optional package does not install.

Full Changelog: v0.1.0-rc.2...v0.1.0-rc.3

0.1.0-rc.2

What's changed

Everything public is now in English: the fifteen skills, Calame's brand guidelines and editorial voice, its three reference visuals, both npm descriptions and the toolchain README. The skills install from an international registry, so an English speaker was getting instructions in French, pointing at a French demo brand, producing a French visual on their first command.

Releases are published by CI, not from a laptop. A tag triggers the workflow, npm authenticates over OIDC, and both packages carry a SLSA provenance attestation linking the tarball to the commit that produced it. No npm token exists in this repository.

Calame is the repository's reference brand. The author's real brands left. Calame is fictional and made to be reused, and it is what the generator ships as its skeleton, so the example you clone is the one the documentation describes.

Breaking

• The campagne skill is now campaign. Anyone who installed it under the old name keeps an orphan folder after skills update.
• rostand-migan and comptaopen are gone. Calame is the only brand.

Full Changelog: 20e7813...v0.1.0-rc.2