Migration Guide
Content migration from existing CMS platforms is planned for a future release. In v0.2.0, demo data is available via chukfi seed, and content can be created programmatically via the CLI or REST API.
Note: This video demonstrates a planned import workflow. v0.2.0 does not include a built-in import command. Content can be created via
chukfi content createor the REST API.
Creating Content Programmatically (v0.2.0)
Section titled “Creating Content Programmatically (v0.2.0)”While the one-click import is planned, you can populate Chukfi today:
# Create a page via CLIchukfi content create \ --type pages \ --title "About Us" \ --fields '{"body":"<p>Our story.</p>"}' \ --status draft \ --json
# Upload mediachukfi media upload --path ./photo.jpg --alt "Team photo" --json
# Publishchukfi content update --id <uuid> --status published --jsonFuture Import Support
Section titled “Future Import Support”The following formats are on the roadmap:
| Source | Format | Status |
|---|---|---|
| WordPress | WXR (.xml) |
Planned |
| Sanity | NDJSON export | Planned |
| Strapi | JSON export | Planned |
For custom migration scripts, the CLI Reference documents all content and media commands you can use to build your own import pipeline.
After Creating Content
Section titled “After Creating Content”Run chukfi codegen to regenerate TypeScript types for your frontend:
chukfi codegen --out src/types