Pages inside pages
The tree is navigation and structure at once. A branch moves – every link stays valid.
Documentation, handbook and blog in one calm interface – a page tree instead of folders, databases as views, two themes from one token set.
✓ No tracking ✓ No external requests ✓ MIT licence
Six things Atlas does differently – each of them is the same component in the product and in these docs.
Content as nested pages – the way a team thinks anyway. The tree is the navigation.
Table, board, gallery: the same entries, different angles. No export, no duplicates.
Light and dark follow the system preference. Rebranding is one line in brand.css.
Command palette, slash menu and shortcuts – every action is reachable without a mouse.
Titles, descriptions and tags are indexed. Results grouped by area.
Docs and blog come from Markdown files. Headings, tables and code look like they do in the product.
Every visual here is built from the same components as the product – no image, no screenshot.
The tree is navigation and structure at once. A branch moves – every link stays valid.
Board, table, gallery – the same entries, different angles.
Light and dark from one token set. Rebranding is one line.
Command palette with ⌘K, slash menu in the editor, shortcuts for everything – every action without a mouse.
"Use this template" on GitHub or via the Astro CLI. The project runs locally right away.
npm create astro -- --template JUNGHERZ/NotionKit-Web atlas-docs
cd atlas-docs && npm install && npm run dev Docs pages and blog posts are Markdown files with a few frontmatter fields. The page tree grows out of the folder.
---
title: First page
section: start
order: 2
icon: 📄
---
## Let’s go
Atlas renders Markdown in the Notion look. One line in brand.css recolours focus rings, buttons and highlights – both themes included.
:root { --nk-accent: #2f8f5b; }
[data-theme="dark"] { --nk-accent: #5cbf87; } We replaced three wikis with Atlas. The page tree brought more order than any folder structure before it.
Finally docs that do not look like an afterthought in dark mode. The team actually reads them.
Markdown in, finished page out. Our engineers write again because it does not hurt.
Three plans, no hidden tiers. Paying yearly saves two months.
For one person and one project.
€0 forever
For teams that write together.
€8 per person / month
For organisations with requirements.
On request
Start with the documentation or write to us – we usually reply the same day.
Questions about Atlas, the template or a project? We usually reply the same day.