Hugoifier
Convert any website to a production-ready Hugo site with Decap CMS — pixel-perfect, no content loss.
How it works
Hugoifier takes three types of input and produces a deployable Hugo site with CMS:
| Input | Method | AI needed? |
|---|---|---|
| Hugo theme | Assembles, patches deprecated APIs, adds CMS | No |
| Next.js app | Captures rendered HTML from dev server | No |
| Raw HTML | Extracts head/body directly into Hugo templates | No |
AI is only used as a fallback (Next.js without a running dev server) or for lightweight structural analysis.
Quick start
pip install hugoifier
# Convert a Hugo theme
hugoifier complete themes/my-theme
# Convert a Next.js app (start your dev server first)
hugoifier complete path/to/nextjs-app
# Convert a raw HTML site
hugoifier complete path/to/html-site
Output goes to output/{name}/ — a complete Hugo site ready to serve:
cd output/my-site && hugo serve
What you get
- Hugo site with all content, styles, and assets preserved
- Decap CMS at
/admin/with GitHub OAuth (Cloudflare Pages Functions) functions/api/auth.js+callback.jsfor OAuth flow- Whitelabel CMS branding (
--cms-name,--cms-logo,--cms-color)
Deploy to Cloudflare Pages
hugo --minify
npx wrangler pages deploy public --project-name my-site
Set GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET as environment variables for CMS auth.
Configuration
# Choose AI backend (only needed for fallback conversion)
HUGOIFIER_BACKEND=anthropic # or openai, google
ANTHROPIC_API_KEY=sk-...
# Whitelabel CMS
hugoifier complete my-site --cms-name "My CMS" --cms-logo https://... --cms-color "#515be3"
Development
git clone https://github.com/ConflictHQ/hugoifier.git
cd hugoifier
pip install -e ".[dev]"
pytest
Built with
Hugoifier is built on top of two excellent open-source projects:
- Hugo — The world's fastest static site generator. Apache 2.0 licensed. Created by Steve Francia and Bjarne Pedersen and contributors.
- Decap CMS (formerly Netlify CMS) — Open-source content management for Git workflows. MIT licensed. Maintained by the Decap community.
We're grateful to both communities for building the tools that make this project possible.
License
MIT — see LICENSE for details.
Made by Conflict.
Release files for hugoifier 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hugoifier-0.3.0.tar.gz | 38.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hugoifier-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 72.8 kB
Release files / hugoifier-0.3.0.tar.gz
| Download URL | hugoifier-0.3.0.tar.gz |
|---|---|
| Size | 38.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6cbc2aa29f31babbe224af2ee93ad1624bde25bd51210d69003d4365134ab4cb
|
|
BLAKE2b-256 checksum How to use checksums |
456d1990a4bdeec084438c5edeeb937f44626e15697c434560340d6088fe92c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 18, 2026.
Transparency logRelease files / hugoifier-0.3.0-py3-none-any.whl
| Download URL | hugoifier-0.3.0-py3-none-any.whl |
|---|---|
| Size | 34.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01898553e385194e75eaefe89c246d6e95b8862232bf8bcd36bda230e02a42da
|
|
BLAKE2b-256 checksum How to use checksums |
62c55e45a0b52a2c7b51be2e61ebe7ab38aab7e49883f9440f6c9fa2c4d69f84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 18, 2026.
Transparency log