docs: use NDG #54

Open
opened 2026-04-26 12:26:38 +03:00 by c · 0 comments
Owner

The current system uses two branches; one branch for code, the other as the website.
I am too lazy to switch branches and update the website each time.

Move documentation to markdown files in a docs/ directory. Documentation can then be generated and served via NDG.
Additionally, package it for Nix and expose it at .#docs. This way, I can selfhost the docs...

Possibly, later on, the docs markdown files themselves could be generated from the code itself. I believe this is possible, but perhaps this is for a later, separate issue.

The current system uses two branches; one branch for code, the other as the website. I am too lazy to switch branches and update the website each time. Move documentation to markdown files in a docs/ directory. Documentation can then be generated and served via [NDG](https://github.com/feel-co/ndg). Additionally, package it for Nix and expose it at .#docs. This way, I can selfhost the docs... Possibly, later on, the docs markdown files themselves could be generated from the code itself. I believe this is possible, but perhaps this is for a later, separate issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
c/takina#54
No description provided.