Use case pages made for sharing
Each use case is its own page with a title, summary, preview image and screenshots, so a short LinkedIn post can link to the full story and show a proper preview card.
The problem
A case study per project is too long for a social post, and a post without a link proves nothing. What works is one problem, one page: short enough to read, specific enough to show how the software solves it.
How dok.sh solves it
- A use case belongs to a project and has its own address (
/use-cases/<slug>), title, summary, tags, publication date and preview image. - The write-up is Markdown with screenshots and Mermaid diagrams. Screenshots can be pasted or dropped straight into the editor.
- Every page is listed on
/use-cases, on its project's page, in the sitemap and inllms.txt, and is described to search engines as an article with its publication date. - The LinkedIn post can be linked back: once posted, its address is saved on the use case and the page links to the discussion.
- The whole set is part of the content export, so it can be prepared locally and loaded on the live site in one step.


The result
Twenty pages about real features of two products, each one ready to be shared on its own.
Technologies
Angular, Spring Boot, Content model, LinkedIn
- Published: 2026-11-03
- Project: dok.sh — Portfolio and CV Platform
- Case study