nexbrand 0.1.0

The first release of nexbrand: your clients' corporate design in one place, on your own server. Colours, fonts, logos, type sizes, rules and example files per client and per project, with every version kept, the checks that go with it and the way into code.

Start it with the docker-compose.yml in this repository or the image ghcr.io/derkezorm/nexbrand:0.1.0. The first account needs the setup code from docker logs nexbrand (or the one you set as NEXBRAND_SETUP_TOKEN). Before you open it to the internet, read "nexbrand on the internet" in the README.

nexbrand is young, and this is the time when ideas and feedback change the most. Tell me what you need in an issue. More on the project site, www.nexbrand.de.

New

• Clients and their design sets. Colours with role and print values, fonts with their licence, logos with their ground, type sizes, rules and example files. Every colour shows its steps from 50 to 950 and its contrast with white and dark.
• Versions on a timeline. Every change starts as a draft and is published with the day it is valid from; after that it stays as it is. "As of" shows any day, "3 years ago" is one click, and two versions side by side show what changed.
• Projects with a CI of their own. An app, a product or a campaign builds on a version of the client, as the client, as the client plus its own, or entirely its own, part by part. A project stays on its version until you move it, so a reprint looks like the first print.
• Dark mode as part of the CI. nexbrand suggests ground, surface, text, muted text, main colour and text on it from the palette; you adjust it, the checks include it and the export carries it.
• Checks that are computed. Contrast of every combination by WCAG 2.2, logos at 3:1, colour vision deficiencies, nearly identical colours, text that is too small, fonts that must not leave the house. Rules for colour pairs, logo grounds and fonts are checked too. The contrast calculator suggests the nearest colour of the same hue that is enough.
• Create a new CI and agree on it. Start from a few words, a picture, a colour or nothing; the workbench suggests colour schemes, neutrals, a font pair and sizes, with a sample page and the checks alongside. The client gets the directions by link, comments on each picture and chooses, and that choice becomes version 1.0.
• Collect from a website, repository or PDF. Colours, fonts and logos are measured and sorted, by rules or with your own AI service, into a draft; or check a page against the CI and find the nearly right shades. Off until the operator allows it.
• As code, through the API and MCP. Every version as CSS variables, a Tailwind 4 theme, SCSS or design tokens, also on a public page for developers without an account. Programs read through /api/v1, an AI in an editor through MCP, and a token of the level "draft" writes a redesign back, always as a draft.
• Around it. Access per client for people and teams, accounts by invitation, a second factor, sign-in through OIDC with a button that sets up authentik, a log in four levels, your own languages as JSON files, and backups you can check, download and upload to a new server. After an update, every account sees what is new in the app itself.