Hugoifier
docs: add 'Why GitHub' section to about page
Commit
45626e1993375b327af307fa1c22f0212f923eef6f070f324892c3eb1382ed8f
Parent
6f1c93091d94a08…
1 file changed
+18
+18
| --- docs/about.md | ||
| +++ docs/about.md | ||
| @@ -56,10 +56,28 @@ | ||
| 56 | 56 | |
| 57 | 57 | ### Git-native Deployments |
| 58 | 58 | |
| 59 | 59 | Push to `main`, site updates. Every PR gets a preview deployment at a unique URL. No deploy scripts, no CI configuration required. |
| 60 | 60 | |
| 61 | +--- | |
| 62 | + | |
| 63 | +## Why GitHub | |
| 64 | + | |
| 65 | +Your site's content is a Git repository. That's not a technical detail — it's the whole point. | |
| 66 | + | |
| 67 | +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. | |
| 68 | + | |
| 69 | +GitHub adds a layer on top of that: | |
| 70 | + | |
| 71 | +- **Free hosting** — GitHub Pages serves static sites directly from your repo at no cost, with a CDN and HTTPS included | |
| 72 | +- **Collaboration** — anyone with a GitHub account can fork your repo, propose changes, and submit a PR. No user accounts, no permissions system to manage | |
| 73 | +- **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 | |
| 74 | +- **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 | |
| 75 | +- **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 | |
| 76 | + | |
| 77 | +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. | |
| 78 | + | |
| 61 | 79 | --- |
| 62 | 80 | |
| 63 | 81 | ## The Case Against Overbuilding |
| 64 | 82 | |
| 65 | 83 | The internet is full of websites that are WordPress or Next.js or a React SPA backed by a database — not because those sites need any of that, but because that's what the developer knew how to build. |
| 66 | 84 |
| --- docs/about.md | |
| +++ docs/about.md | |
| @@ -56,10 +56,28 @@ | |
| 56 | |
| 57 | ### Git-native Deployments |
| 58 | |
| 59 | Push to `main`, site updates. Every PR gets a preview deployment at a unique URL. No deploy scripts, no CI configuration required. |
| 60 | |
| 61 | --- |
| 62 | |
| 63 | ## The Case Against Overbuilding |
| 64 | |
| 65 | The internet is full of websites that are WordPress or Next.js or a React SPA backed by a database — not because those sites need any of that, but because that's what the developer knew how to build. |
| 66 |
| --- docs/about.md | |
| +++ docs/about.md | |
| @@ -56,10 +56,28 @@ | |
| 56 | |
| 57 | ### Git-native Deployments |
| 58 | |
| 59 | Push to `main`, site updates. Every PR gets a preview deployment at a unique URL. No deploy scripts, no CI configuration required. |
| 60 | |
| 61 | --- |
| 62 | |
| 63 | ## Why GitHub |
| 64 | |
| 65 | Your site's content is a Git repository. That's not a technical detail — it's the whole point. |
| 66 | |
| 67 | 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. |
| 68 | |
| 69 | GitHub adds a layer on top of that: |
| 70 | |
| 71 | - **Free hosting** — GitHub Pages serves static sites directly from your repo at no cost, with a CDN and HTTPS included |
| 72 | - **Collaboration** — anyone with a GitHub account can fork your repo, propose changes, and submit a PR. No user accounts, no permissions system to manage |
| 73 | - **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 |
| 74 | - **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 |
| 75 | - **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 |
| 76 | |
| 77 | 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. |
| 78 | |
| 79 | --- |
| 80 | |
| 81 | ## The Case Against Overbuilding |
| 82 | |
| 83 | The internet is full of websites that are WordPress or Next.js or a React SPA backed by a database — not because those sites need any of that, but because that's what the developer knew how to build. |
| 84 |