Vanilla Markdown Tricks For Much Better README Files. Everything you need to build high-end documentation without external dependencies.
| Category | Feature | Link |
|---|---|---|
| Navigation | Todo & Rules | #todo |
| Text & UI | Alerts & Collapsibles | #alerts / #collapsible-sections |
| Code | Permalinks & Diffs | #permanent-link-to-a-code-snippet / #diff-highlighting |
| Advanced | Diagrams, Maps, & 3D | #diagrams / #maps / #3d-models |
| Media | Videos & Math | #videos / #math |
| Other | Jekyll & Footnotes | #yaml-jekyll / #footnotes |
- Vanilla MD Implementation
- Jekyll/GitHub Pages Integration
- Non-vanilla resource curation
- Project README examples
- Online editor via GitHub Pages
- Future: UI decoration (social links, custom fonts)
- Resource list for README enhancements
- README Best Practices guide
Keep documentation clean by nesting logs, secondary code, or deep-dives.
βΆ Click to expand details
Standard Markdown works perfectly inside these blocks.
Visualize code changes or version comparisons natively.
- const status = 'legacy';
+ const status = 'cool-markdown';Reference specific code blocks that stay accurate even if the file is updated.
[https://github.com/USERNAME/REPOSITORY/blob/COMMIT_HASH/FILENAME?plain=1#LX-LX](https://github.com/USERNAME/REPOSITORY/blob/COMMIT_HASH/FILENAME?plain=1#LX-LX)
Example: Permanent Link Reference
Standardized GitHub callouts for highlighting critical information.
Note
Useful info even if you're skimming.
Tip
Best practices and shortcuts.
Important
Critical information for the user.
Warning
Potential breaking changes or issues.
Caution
High-risk actions.
Interactive task lists that track progress and link directly to project management.
- #1 (Direct Issue Reference)
- Pull Request Link
- Project milestone completion
Status Reward:
π everything done, go touch grass
Leverage GitHub Pages to treat Markdown files as dynamic components.
---
title: cool-markdown
description: markdown tricks
---Enables variables, loops, and reusable components within your documentation environment.
Native code snippet visualization. Since GitHub strips scripts, this uses a high-fidelity image link to maintain a "code-block" aesthetic.
Showcase repository status and statistics using dynamic pinned-style cards.
-----Generate complex flows using Mermaid syntax.
graph LR;
subgraph Development_Cycle [Project Lifecycle]
Start([π Start Project]) --> Build{ποΈ Build Phase}
Build -- "Success" --> Tests{π§ͺ CI/CD Tests}
Build -- "Failure" --> Debug[π οΈ Debugging]
Debug --> Build
Tests -- "Passed" --> Documentation[π Update Docs]
Tests -- "Failed" --> Refactor[βοΈ Refactor Code]
Refactor --> Build
end
subgraph Community_Interaction [Open Source Growth]
Documentation --> Engagement{β¨ Community}
Engagement --> |"Appreciation"| Star[β Star Repo]
Engagement --> |"Contribution"| Fork[π΄ Fork Repo]
Fork --> PullRequest[β€΄οΈ Pull Request]
PullRequest --> CodeReview{π Code Review}
CodeReview -- "Approved" --> Merge[π Merge to Main]
Merge --> Tests
end
subgraph Deployment_Stage [Production]
Merge --> Release[π¦ Create Release]
Release --> Deploy{π Deployment}
Deploy --> |"Cloud"| Vercel[β² Vercel/Netlify]
Deploy --> |"Container"| Docker[π³ Docker Hub]
Deploy --> |"Static"| GH_Pages[π₯οΈ GitHub Pages]
end
%% Styling
style Start fill:#f9f,stroke:#333,stroke-width:2px
style Deploy fill:#00ff00,stroke:#333,stroke-width:4px
style Debug fill:#ff9999,stroke:#333
style Community_Interaction fill:#e1f5fe,stroke:#01579b
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": { "name": "Al Quds" },
"geometry": {
"type": "Polygon",
"coordinates": [
[[35.1, 31.7], [35.3, 31.7], [35.3, 31.9], [35.1, 31.9], [35.1, 31.7]]
]
}
}
]
}
{
"type": "Topology",
"objects": {
"area": {
"type": "GeometryCollection",
"geometries": [
{
"type": "Polygon",
"arcs": [[0]],
"properties": { "name": "Mecca Region" }
}
]
}
},
"arcs": [
[[39.8, 21.3], [39.9, 21.3], [39.9, 21.4], [39.8, 21.4], [39.8, 21.3]]
]
}
Natively render 3D STL files within the repository browser.
solid exported
facet normal 0 0 1
outer loop
vertex -20 -20 40
vertex 20 -20 40
vertex -20 20 40
endloop
endfacet
facet normal 0 0 -1
outer loop
vertex 20 20 0
vertex -20 -20 0
vertex -20 20 0
endloop
endfacet
facet normal 0 0 -1
outer loop
vertex -20 -20 0
vertex 20 20 0
vertex 20 -20 0
endloop
endfacet
facet normal 0 0 1
outer loop
vertex 20 20 40
vertex -20 20 40
vertex 20 -20 40
endloop
endfacet
facet normal 0 -1 0
outer loop
vertex -20 -20 0
vertex 20 -20 0
vertex 20 -20 40
endloop
endfacet
facet normal -1 0 0
outer loop
vertex -20 -20 0
vertex -20 20 40
vertex -20 20 0
endloop
endfacet
facet normal 1 0 0
outer loop
vertex 20 20 40
vertex 20 -20 40
vertex 20 -20 0
endloop
endfacet
facet normal 0 1 0
outer loop
vertex -20 20 0
vertex -20 20 40
vertex 20 20 40
endloop
endfacet
facet normal -1 0 0
outer loop
vertex -20 -20 0
vertex -20 -20 40
vertex -20 20 40
endloop
endfacet
facet normal 1 0 0
outer loop
vertex 20 -20 0
vertex 20 20 0
vertex 20 20 40
endloop
endfacet
facet normal 0 -1 0
outer loop
vertex 20 -20 40
vertex -20 -20 40
vertex -20 -20 0
endloop
endfacet
facet normal 0 1 0
outer loop
vertex 20 20 40
vertex 20 20 0
vertex -20 20 0
endloop
endfacet
endsolid exported
Embed high-quality video demonstrations directly into the file.
frequency.mp4
Standard LaTeX support for complex equations and formulas.
Inline:
Block:
Add citations or secondary notes without interrupting the core content1.
- Prioritize Scannability: Use headers and tables to guide the eye.
- Visuals Over Text: One GIF or diagram provides more value than multiple paragraphs.
- Performance Matters: Limit heavy widgets to ensure fast loading times.
- Maintain Utility: Do not let aesthetic features obscure installation and usage instructions.
Contributions are welcome. New tricks will be added as they are discovered.
Footnotes
-
Footnotes appear automatically at the bottom of the file. β©