Docs
Core Commands
Core Commands
Main workflow to generate and publish documentation with Artisaan CLI
Main workflow
Initialize the project
Creates the .artisaan/ folder and the base project configuration file.
artisaan init
Review configuration
Confirm language, project type, and search paths before generation.
.artisaan/config.json
Generate documentation
Processes your code and generates/updates documentation files.
artisaan docs generate
Sync to remote
Sends docs to the configured bucket/project, updating published pages.
artisaan docs sync
Main commands
| Command | Purpose | When to use |
|---|---|---|
artisaan init | Initializes local configuration | First run in the repository |
artisaan docs generate | Generates docs from your code | After project changes |
artisaan docs sync | Publishes/syncs remote docs | After local validation |
Run by operating system
artisaan init
artisaan docs generate
artisaan docs syncMinimum recommended configuration
{
"slug": "my-project",
"language": "typescript",
"project": "nextjs",
"search_paths": [
"app",
"lib",
"src"
],
"ignore_paths": [
"node_modules",
"dist",
".next"
]
}Common issues
missing field "slug"
This error occurs in artisaan docs sync when .artisaan/config.json does not contain the slug field.
Add "slug" to the .artisaan/config.json file. Example: "slug": "my-project"
Empty or incomplete documentation
- Check whether your source folders are listed in
search_paths. - Confirm that relevant content is not blocked in
ignore_paths. - Run
artisaan docs generateagain after adjustments.
Quick checklist
artisaan initexecuted in the correct repository..artisaan/config.jsonincludesslug,language, andproject.search_pathscovers the real source code folders.artisaan docs generatecompletes without errors beforeartisaan docs sync.
On This Page
Coming Soon
Deploy your docs
Host your Artisaan documentation on our edge network. Fast, secure, and always in sync with git.
Deploy NowPowered by Artisaan CLIv0.1.4