Configuration

Configuration lives in .config/dodeca.yaml in your project root.

Basic settings

yaml

content: content
output: public

Link checking

ddc build checks all internal and external links, failing the build if any are broken.

Configuration options

yaml

link_check:
  rate_limit_ms: 1500
  skip_domains:
    - linkedin.com
    - twitter.com
    - x.com

Option	Type	Default	Description
`rate_limit_ms`	integer	`1000`	Minimum delay between requests to the same domain (milliseconds)
`skip_domains`	list of strings	none	Domains to skip checking entirely

When to skip domains

Some sites aggressively block automated requests. Consider skipping:

Social media: linkedin.com, twitter.com, x.com, facebook.com
Sites with CAPTCHAs: Some documentation sites require JavaScript
Rate-limited APIs: Sites that return 429 errors frequently

Example with multiple skip domains

yaml

link_check:
  rate_limit_ms: 2000
  skip_domains:
    - linkedin.com
    - twitter.com
    - x.com
    - facebook.com
    - instagram.com

Internal links (links to other pages in your site) are always checked and cannot be skipped.

Code execution

If the code execution helper is available (ddc-cell-code-execution), Rust code blocks can be executed as part of the build.

At the moment, .config/dodeca.yaml contains a code_execution section, but it is not fully wired through to the build yet (defaults are used). If you need to disable code execution, use the environment variable DODECA_NO_CODE_EXEC=1.

Stable assets

Some assets (like favicons) should keep stable URLs for caching:

yaml

stable_assets:
  - favicon.svg
  - robots.txt

Full example

yaml

content: content
output: public

link_check:
  rate_limit_ms: 1000
  skip_domains:
    - example.com

stable_assets:
  - favicon.svg