The problem
Playbooks for non-technical staff lived in chat threads and scattered files. New hires learned by word of mouth, and finding the current version of anything was a guess.
Restaurants & hospitality
A knowledge base for a sushi restaurant chain
An internal portal instead of chat threads and emailed PDFs: sections and articles with media, role-based access, and a deploy on every push.
Restaurants & hospitality
Суши Love
<2 minfrom a push to main to production
0developer hours per content edit
24/7access from any device
What we did
We built a portal on Next.js and Express with PostgreSQL: sections and articles with images through a web editor, access controlled by roles and groups. Deploys run on GitOps — a merge to main ships itself.
The outcome
Non-technical staff edit articles themselves, no developer required. One source of truth instead of a dozen versions of the same document, reachable from any device.
We used to dig up onboarding instructions from old chat threads. Now there is one portal the team edits itself, no developer on call.