> workflow
Initialize a project, configure your chrome, select niches and schemas, generate content with AI, and build static HTML — all from the command line.
Run contento init in any directory to create a project. Contento writes a contento.config.json next to your existing site code — commit it to git, share it with your team, and reference its project ID for every later command.
$ contento init \
--name "DevTools Resources"
✓ Project created
ID proj_8f3a...
Name DevTools Resources
Domain example.com
Status active
$ contento projects chrome proj_8f3a... \
--header chrome/header.html \
--footer chrome/footer.html \
--css chrome/styles.css
✓ Chrome updated
Project chrome updated successfully.
Upload your site's header, footer, and CSS via the contento projects chrome command. Point it at your local HTML and CSS files, and generated pages will look like native pages on your existing site.
Browse 150+ niches across 8 categories. Each niche carries structured context — audience profile, pain points, monetization strategies, and subtopics — that is injected into every AI prompt.
$ contento niches list --category "Software"
Name Category Subtopics
────────────────────────────────────────────────
Developer Tools Software / SaaS 20
Project Management Software / SaaS 18
CRM Platforms Software / SaaS 15
DevOps Software / SaaS 22
... 21 more
$ contento niches fork --id niche_01... \
--name "Custom DevTools"
Forked: Custom DevTools (niche_f8a2...)
$ contento schemas list
Slug Title Pattern
──────────────────────────────────────────────
idea-list {count} {subtopic} Ideas for {year}
checklist The Ultimate {subtopic} Checklist
how-to How to {action} with {subtopic}
comparison {A} vs {B}: Which Is Better?
alternatives Best {tool} Alternatives
faq {subtopic} FAQ: {n} Questions
glossary {niche} Glossary: {n} Terms
resource-list Top {subtopic} Resources
template-pack Free {subtopic} Templates
tool-page {subtopic} Calculator
Select from 10 built-in content types. Each schema defines the exact JSON structure the AI must produce, with field-level constraints (item counts, string lengths, enums) and a deterministic title pattern.
Create a collection that combines your niches and schema, then kick off a generation job. Contento's concurrent AI workers expand subtopics, build prompts, generate JSON, validate output, and retry failures — all streamed to your terminal in real time.
$ contento collections generate col_9d2f...
✓ Generation started (Job: job_4a1b...)
[00:04] ██▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 6/48 (12%)
[00:12] ███████▁▁▁▁▁▁▁▁▁ 22/48 (46%)
[00:20] ████████████▁▁▁▁ 36/48 (75%)
[00:26] ████████████████ 48/48 (100%)
Validation: 46 passed, 2 retried, 0 failed
✓ Generation complete!
$ contento build proj_8f3a... --output ./dist
✓ Built 48 pages to ./dist/
HTML files: 48
Sitemap: ./dist/sitemap.xml
Deploy with your existing pipeline: git push, netlify deploy, rsync, etc.
# Deploy with your existing pipeline:
# rsync, Netlify, Vercel, S3, GitHub Pages, etc.
$ netlify deploy --dir=./dist --prod
Run contento build <project-id> --output ./dist and Contento renders every published page locally — chrome applied, internal links inserted, sitemap written. The output is plain HTML in your dist/ directory. Deploy with whatever pipeline you already use.
Every step is available through the CLI. Add --json to any command for machine-readable output.
Initialize contento init
│
▼
Configure Chrome contento projects chrome
│
▼
Select Niches contento niches list
│
▼
Pick Schema contento schemas list
│
▼
Generate contento collections generate
│ └ subtopic expansion
│ └ concurrent AI workers
│ └ schema validation
▼
Build contento build <project-id> --output ./dist
│ └ chrome applied
│ └ internal linking pass
│ └ sitemap + JSON-LD + OG
▼
Deploy with your pipeline Netlify, Vercel, S3, rsync...
Install the CLI and build your first batch of pages in under 10 minutes.