BRAND AS CODE

Your brand,
in the repo.

Rules, pages and theme as YAML beside the files they point at. Change either side: each reaches the other, and a clash is named, not lost.

Start free Read the guide

acme/websitecolor-page

# brand/pages/color.yaml
title: Color
lede: Blue carries the weight.
sections:
  - template: palette
    keys: [color.nope]    keys: [color.primary, color.ink]  - template: dodont
    items:
      - asset: assets/logo-on-red.png
        verdict: dont

Open A page on color #43

✕Artbucket / brand pages/color.yaml:5: no rule "color.nope"; this brand has color.primary, color.ink

✓Artbucket / brand Fixed in the next commit: every file valid

artbucket bot

Adds the page color. Merging releases it as Acme @6.

Preview the guidelines ↗

WHAT IT DOES

Reviewed like code.
Read like a brand.

The same rules, pages and theme the builder edits, as files a person reads and reviews.

Files you can read
brand.yaml, rules/, pages/ and assets/. Defaults left out; a pull keeps your comments and layout.
Both ways
Merged a rule at a time. Where both sides changed the same rule, the clash is named, and the side that lost is a restore away.
Checked at the line
Every push checks every file and answers with the problem at its file and line. In CI, a diff with a problem exits 1.
Previews
A link to the brand's site as a pull request's files say it, with what it would change. No account needed to open it.
You pick what releases
On Cloud: a merge updates the draft, or each merge releases, or a GitHub release does. Each release posts a GitHub deployment.
Any Git host, from CI
Self-hosted, or on GitLab: one CI job with a write key pushes the brand's folder when it changes.

THE CLI

Pull, diff, push.
That's the loop.

The artbucket package on npm, a thin client over the same API. Each push is one version of the brand's history, undone like any other edit.

The GitHub App on Cloud does it for you
A README badge with the release that is live

~/acme

$ npx artbucket brand pull brand --brand acme --assets
$ npx artbucket brand diff brand
pages/color.yaml:5: no rule "color.nope"
$ npx artbucket brand push brand --publish --note "Bluer primary"
✓ Released, to BrandHub and every portal showing it

Built for
the repo you have.

Brand as code guide GitHub Actions and GitLab CI CLI

SHIP THE BRAND LIKE CODE.

Open a pull request.
Release on merge.

Free in the beta, Git included.

Start free in the beta

Your brand,in the repo.

Reviewed like code.Read like a brand.

Files you can read

Both ways

Checked at the line

Previews

You pick what releases

Any Git host, from CI

Pull, diff, push.That's the loop.

Built forthe repo you have.

Open a pull request.Release on merge.

Your brand,
in the repo.

Reviewed like code.
Read like a brand.

Pull, diff, push.
That's the loop.

Built for
the repo you have.

Open a pull request.
Release on merge.