Hugoifier
docs: add 'Why Hugo + Cloudflare' about page
Commit
6f1c93091d94a0864d473d42830590f2af20ba55fab923a8779821e88d14be03
Parent
f289d0cbd1dcd92…
2 files changed
+54
+1
+54
| --- a/docs/about.md | ||
| +++ b/docs/about.md | ||
| @@ -0,0 +1,54 @@ | ||
| 1 | +# Why Hugo + Cloudflare? | |
| 2 | + | |
| 3 | +Most websites don't need a database, a server, or a $200/month hosting bill. They need fast, reliable delivery of content that doesn't change on every request. Hugo and Cloudflare Pages are built exactly for that — and together they're one of the best stacks for anyone who just needs a website. | |
| 4 | + | |
| 5 | +--- | |
| 6 | + | |
| 7 | +## Why Hugo | |
| 8 | + | |
| 9 | +### No Database | |
| 10 | + | |
| 11 | +Traditional CMS platforms — WordPress, Drupal, Ghost — hit a database on every page load. That database is the single biggest source of downtime, security vulnerabilities, and scaling headaches. Hugo generates pure static HTML at build time. There is no database. There is nothing to query, nothing to corrupt, nothing to patch. | |
| 12 | + | |
| 13 | +### Unhackable by Design | |
| 14 | + | |
| 15 | +If there's no server-side code running when a visitor hits your site, there's nothing to exploit. No PHP injection. No SQL injection. No session hijacking. No CVE-of-the-week to scramble and patch at 2am. A static site's attack surface is essentially zero — you're just serving files. | |
| 16 | + | |
| 17 | +### Markdown Content | |
| 18 | + | |
| 19 | +Your content lives in plain `.md` files in a Git repository. That means: | |
| 20 | + | |
| 21 | +- **Version-controlled** — every edit is tracked, every change is reversible | |
| 22 | +- **Portable** — no vendor lock-in, no proprietary export format | |
| 23 | +- **Writable anywhere** — any text editor, any machine, offline | |
| 24 | +- **Diffable** — you can review content changes in aFast. Rion enterprises pay for) | |
| 25 | +- Web analytics without tracking scripts | |
| 26 | +- Automatic redirects, custom headers, and edge functions if you ever need them | |
| 27 | + | |
| 28 | +### Git-native Deployments | |
| 29 | + | |
| 30 | +Push to `main`, site updates. Every PR gets a preview deployment at a unique URL. No deploy scripts, no CI configuration required. | |
| 31 | + | |
| 32 | +--- | |
| 33 | + | |
| 34 | +## Why GitHub | |
| 35 | + | |
| 36 | +Your site's content is a Git repository. That's not a technical detail — it's the whole point. | |
| 37 | + | |
| 38 | +Git gives you a complete, timestamped history of every word ever published on your site. Revert a bad edit in seconds. See exactly what changed and when. Run your content through pull request review before it goes live. | |
| 39 | + | |
| 40 | +GitHub adds a layer on top of that: | |
| 41 | + | |
| 42 | +- **Free hosting** — GitHub Pages serves static sites directly from your repo at no cost, with a CDN and HTTPS included | |
| 43 | +- **Collaboration** — anyone with a GitHub account can fork your repo, propose changes, and submit a PR. No user accounts, no permissions system to manage | |
| 44 | +- **Automation** — GitHub Actions runs your Hugo build and deploys it on every push. The workflow is a file in your repo, version-controlled alongside your content | |
| 45 | +- **Decap CMS integration** — Decap CMS (which Hugoifier configures automatically) uses Git Gateway to commit content changes directly back to GitHub. Your editors use a clean web UI; under the hood it's just commits | |
| 46 | +- **Single source of truth** — content, theme, config, and deploy pipeline all live in one place. No external services to keep in sync, no credentials to rotate, no staging environments to maintain | |
| 47 | + | |
| 48 | +GitHub is free for public repositories and has been running reliably for over 15 years. For a website, it's all the infrastructure you need. | |
| 49 | + | |
| 50 | +--- | |
| 51 | + | |
| 52 | +## The Case Against Overbuilding | |
| 53 | + | |
| 54 | +The internet is full of websites that are WordPress or Next.js or a React SPA |
| --- a/docs/about.md | |
| +++ b/docs/about.md | |
| @@ -0,0 +1,54 @@ | |
| --- a/docs/about.md | |
| +++ b/docs/about.md | |
| @@ -0,0 +1,54 @@ | |
| 1 | # Why Hugo + Cloudflare? |
| 2 | |
| 3 | Most websites don't need a database, a server, or a $200/month hosting bill. They need fast, reliable delivery of content that doesn't change on every request. Hugo and Cloudflare Pages are built exactly for that — and together they're one of the best stacks for anyone who just needs a website. |
| 4 | |
| 5 | --- |
| 6 | |
| 7 | ## Why Hugo |
| 8 | |
| 9 | ### No Database |
| 10 | |
| 11 | Traditional CMS platforms — WordPress, Drupal, Ghost — hit a database on every page load. That database is the single biggest source of downtime, security vulnerabilities, and scaling headaches. Hugo generates pure static HTML at build time. There is no database. There is nothing to query, nothing to corrupt, nothing to patch. |
| 12 | |
| 13 | ### Unhackable by Design |
| 14 | |
| 15 | If there's no server-side code running when a visitor hits your site, there's nothing to exploit. No PHP injection. No SQL injection. No session hijacking. No CVE-of-the-week to scramble and patch at 2am. A static site's attack surface is essentially zero — you're just serving files. |
| 16 | |
| 17 | ### Markdown Content |
| 18 | |
| 19 | Your content lives in plain `.md` files in a Git repository. That means: |
| 20 | |
| 21 | - **Version-controlled** — every edit is tracked, every change is reversible |
| 22 | - **Portable** — no vendor lock-in, no proprietary export format |
| 23 | - **Writable anywhere** — any text editor, any machine, offline |
| 24 | - **Diffable** — you can review content changes in aFast. Rion enterprises pay for) |
| 25 | - Web analytics without tracking scripts |
| 26 | - Automatic redirects, custom headers, and edge functions if you ever need them |
| 27 | |
| 28 | ### Git-native Deployments |
| 29 | |
| 30 | Push to `main`, site updates. Every PR gets a preview deployment at a unique URL. No deploy scripts, no CI configuration required. |
| 31 | |
| 32 | --- |
| 33 | |
| 34 | ## Why GitHub |
| 35 | |
| 36 | Your site's content is a Git repository. That's not a technical detail — it's the whole point. |
| 37 | |
| 38 | Git gives you a complete, timestamped history of every word ever published on your site. Revert a bad edit in seconds. See exactly what changed and when. Run your content through pull request review before it goes live. |
| 39 | |
| 40 | GitHub adds a layer on top of that: |
| 41 | |
| 42 | - **Free hosting** — GitHub Pages serves static sites directly from your repo at no cost, with a CDN and HTTPS included |
| 43 | - **Collaboration** — anyone with a GitHub account can fork your repo, propose changes, and submit a PR. No user accounts, no permissions system to manage |
| 44 | - **Automation** — GitHub Actions runs your Hugo build and deploys it on every push. The workflow is a file in your repo, version-controlled alongside your content |
| 45 | - **Decap CMS integration** — Decap CMS (which Hugoifier configures automatically) uses Git Gateway to commit content changes directly back to GitHub. Your editors use a clean web UI; under the hood it's just commits |
| 46 | - **Single source of truth** — content, theme, config, and deploy pipeline all live in one place. No external services to keep in sync, no credentials to rotate, no staging environments to maintain |
| 47 | |
| 48 | GitHub is free for public repositories and has been running reliably for over 15 years. For a website, it's all the infrastructure you need. |
| 49 | |
| 50 | --- |
| 51 | |
| 52 | ## The Case Against Overbuilding |
| 53 | |
| 54 | The internet is full of websites that are WordPress or Next.js or a React SPA |
+1
| --- mkdocs.yml | ||
| +++ mkdocs.yml | ||
| @@ -72,10 +72,11 @@ | ||
| 72 | 72 | - Installation: getting-started/installation.md |
| 73 | 73 | - Quick Start: getting-started/quickstart.md |
| 74 | 74 | - Configuration: getting-started/configuration.md |
| 75 | 75 | - CLI Reference: cli-reference.md |
| 76 | 76 | - Architecture: architecture.md |
| 77 | + - Why Hugo + Cloudflare: about.md | |
| 77 | 78 | |
| 78 | 79 | extra: |
| 79 | 80 | social: |
| 80 | 81 | - icon: fontawesome/brands/github |
| 81 | 82 | link: https://github.com/ConflictHQ/hugoifier |
| 82 | 83 |
| --- mkdocs.yml | |
| +++ mkdocs.yml | |
| @@ -72,10 +72,11 @@ | |
| 72 | - Installation: getting-started/installation.md |
| 73 | - Quick Start: getting-started/quickstart.md |
| 74 | - Configuration: getting-started/configuration.md |
| 75 | - CLI Reference: cli-reference.md |
| 76 | - Architecture: architecture.md |
| 77 | |
| 78 | extra: |
| 79 | social: |
| 80 | - icon: fontawesome/brands/github |
| 81 | link: https://github.com/ConflictHQ/hugoifier |
| 82 |
| --- mkdocs.yml | |
| +++ mkdocs.yml | |
| @@ -72,10 +72,11 @@ | |
| 72 | - Installation: getting-started/installation.md |
| 73 | - Quick Start: getting-started/quickstart.md |
| 74 | - Configuration: getting-started/configuration.md |
| 75 | - CLI Reference: cli-reference.md |
| 76 | - Architecture: architecture.md |
| 77 | - Why Hugo + Cloudflare: about.md |
| 78 | |
| 79 | extra: |
| 80 | social: |
| 81 | - icon: fontawesome/brands/github |
| 82 | link: https://github.com/ConflictHQ/hugoifier |
| 83 |