Resources
Everything we know about the things we ship.
Documentation, knowledge base and how-to guides for every Code Nation product — written by the people who built them, in the order you will actually need them. When a new product launches, its docs land here the same day.
- Products covered
- 2, so far
- Written by
- The people who built it
- Answers become
- Articles
- Marketing content
- None
Knowledge base
Start with the category, not the search box.
Getting started
Your first hour with any Code Nation product: account, brand setup, and the one setting everyone misses.
BrowseWhite-label setup
Your logo, your domain, your email address on every client-facing surface. Checking our name appears nowhere.
BrowseIntegrations
Asana, Trello, Jira, Monday, Slack, and the webhooks for everything else. Payload samples included.
BrowseAccounts & billing
Seats, invoices, the partner discount, and exporting your data when you leave. Especially that last one.
BrowseTroubleshooting
When something looks wrong: what to check, what to send us, and what is already a known issue.
BrowseProduct updates
Release notes in plain sentences, and the roadmap items early-access feedback has voted up.
BrowseDocumentation
One shelf per product · New products land here at launch
The docs shelf.
Briefroom
Early accessThe scoping and intake tool. Docs cover the client-facing side and yours.
- Create your first branded intake linkSetup
- Configure the question engine per project typeGuide
- Review open-question flags before quotingGuide
- Export a brief to your PM tool or a PDFReference
Relaydesk
In developmentThe white-label support queue. Docs are being written alongside the build.
- Point your support address at the queueSetup
- Define SLAs your client actually needsGuide
- Set up the monthly client reportGuide
- Escalation paths and after-hours coverReference
API reference
REST endpoints, webhook payloads and auth for every product, versioned together. Ships with the public launch of Briefroom.
Status: with public launch
Changelog
What shipped, dated, in plain sentences. No “improvements and bug fixes” entries — if it changed, it is named.
Updated with every release
How-to guides
One task, one page, done in the time it says.
Every guide is timed against a real run-through, not an optimistic one. If it says four minutes, it took four minutes.
Not in the docs? That is a docs bug.
Ask the question anyway. A human answers within 24–48 hours, and the answer becomes an article so the next person never has to ask.