Introduction
Your blog at blog.adarshrust.com is a static site generated by Eleventy and deployed by GitHub Actions to GitHub Pages.
The entire publishing workflow is:
- Open github.com/Webrowse/adarshrust-blog.
- Navigate to
content/YYYY/MM/. - Create or edit a Markdown file.
- Commit.
- GitHub Actions builds and deploys. The article is live in about a minute.
There is no CMS, no admin dashboard, no database, and no local setup required to publish. Everything on the site — homepage, archive, tag pages, RSS, sitemap, search, related articles — is regenerated from your Markdown files on every build.
The mental model
Think of the repository as the blog:
| You do | The build does |
|---|---|
| Add a Markdown file | Creates the article page, adds it everywhere it belongs |
Edit frontmatter tags: | Updates the tag pages and tag cloud |
Set published: false | Removes the article from the entire site |
Set a future date: | Hides the article until that day |
| Delete the file | Removes the article and every reference to it |
You never edit HTML, never update an index page, and never touch configuration to publish.
Where things live
adarshrust-blog/
├── content/ ← articles, organized by year/month
│ └── 2026/
│ └── 05/
│ ├── hello-world.md
│ └── images/
├── pages/ ← standalone pages (/about/, /now/, …)
├── _includes/ ← HTML layouts (rarely touched)
├── _data/site.js ← site title, URL, author
├── eleventy.config.js ← the build logic
└── .github/workflows/deploy.yml ← build + deploy pipeline
The rest of this book walks through each part of the workflow.