Content you can move, review and restore
The whole site text is one readable YAML file that can be exported, checked and imported section by section, next to full database backups taken from the admin.
The problem
A database is a poor place to review changes: you can't diff it, you can't read it, and moving a site to a new server means copying everything, including old contact messages.
How dok.sh solves it
- Site content as one YAML file: resume, skills, projects and case studies, services, use cases, settings and CV defaults. It can be read, compared and kept in git.
- Import by section. A file that contains only
useCases:replaces only the use cases; every other section is left as it is. The file is checked first, and nothing changes until you confirm. - A seed for a new server. The same file ships with the application and fills an empty database on the first start.
- Full backups of the whole database, including uploads, messages and history, are taken and restored from the admin.
- Every import and backup is recorded in the history with who started it and what it contained.

The result
New content is prepared and checked locally, then loaded on the live site in one step, and a new server starts with the real content instead of an empty page.
Technologies
YAML, Backups, MongoDB, Docker
- Published: 2026-11-03
- Project: dok.sh — Portfolio and CV Platform
- Case study