Theme Workflow

Create a hosted project, work against a dev theme locally, and publish changes to the live theme.

This walks through the day-to-day flow of building a hosted Bolder theme locally with the CLI, from scaffolding to publishing.

Create the project

bolder login
bolder shops use
bolder new my-theme

Choose Hosted theme, then start either from an existing theme on the shop (its templates are downloaded) or from an empty v2 scaffold. The project directory gets a .bolder.json binding it to the shop and theme.

To use a directory you already have, run bolder pair inside it instead.

Work against a dev theme

A dev theme is a copy of the live theme, so changes don’t affect the live site until you publish. If your project doesn’t have one yet (always the case after an empty scaffold):

bolder dev

Edit locally

bolder diff          # what differs between local and remote
bolder pull          # download remote templates
bolder push          # upload every changed or new template
bolder push templates/product.liquid   # or just one file

bolder watch

Watches the template directories and pushes each file as you change it. There’s no conflict detection against concurrent remote edits, so avoid watching a theme someone else is editing.

Publish

When the dev theme looks right:

bolder publish

This publishes the dev theme to live.

Coming from the old CLI

The old bootic_cli commands (bolder setup, themes clone, themes sync, themes backup, runner) don’t exist in this CLI. Use bolder login to authenticate, bolder pull to download a theme and bolder run for scripts. sync and backup have no equivalent yet.