All documentation pages are written in Markdown and stored in the docs/ folder of your repository. GitHub Pages automatically converts these files into a clean, navigable websiteβno build tools required.
docs/ folder..md extension (e.g., advanced-setup.md).---
title: Advanced Setup
nav_order: 5
---
β Your new page will be live within seconds!
GitHub Pages supports standard GitHub Flavored Markdown (GFM). Here are common examples:
# Page Title (H1)
## Section (H2)
### Subsection (H3)
*Italic* or _italic_
**Bold** or __bold__
~~Strikethrough~~
- Unordered item
- Another item
1. Ordered item
2. Another ordered item
Inline: `code`
Code block with syntax highlighting:
```python
def hello():
print("Hello, docs!")
```
π‘ Supported languages:
python,javascript,bash,yaml,json, and many more.
[Link to GitHub](https://github.com)

π Internal links: Use relative paths
Example:[Configuration](/docs-template/configuration.html)
| Feature | Supported |
|-------------|:---------:|
| Markdown | β
|
| Jekyll | β
|
| Custom JS | β |
Use GitHub emoji shortcodes:
:rocket: :books: :gear: :white_check_mark:
β Renders as: π π βοΈ β
If your theme supports sidebar navigation (like jekyll-theme-primer), use nav_order in front matter to control menu order:
---
title: Getting Started
nav_order: 1
---
Pages without nav_order may appear at the bottom or be excluded from navigation.
For complex documentation:
docs/authentication.md, api-reference.mdπ Tip: Avoid subfolders in
docs/unless your theme explicitly supports them (many GitHub themes do not).
main branch updates your live site in ~1 minute.gem install bundler jekyll
jekyll serve
Then visit http://localhost:4000/your-repo-name/
β οΈ Local preview requires the same plugins and theme as GitHub Pages. When in doubt, trust the live site.
Now go write amazing docs! πβ¨ ```
This version is clean, correct, and user-focusedβperfect for your GitHub Pages documentation template. β