Harbor Docs — A knowledge base the team actually uses

01

Project overview

Make internal knowledge searchable, current, and painless to maintain for a non-technical team.

02

Problem

Guides lived in chat threads and outdated PDFs. Nobody trusted the docs, so everyone asked the same questions. The previous wiki was slow and editing felt like filing paperwork.

P

Process

1. 1

   Kept authoring where the team already writes (Notion) and made the website a read-optimized mirror, not another editor to learn.

2. 2

   Built a sync pipeline with content validation — broken links and missing titles are flagged before publish, not after.

3. 3

   Designed for scanning: strong headings, jump links, and search that tolerates typos and jargon.

03

Solution

Editors write in Notion; a scheduled sync validates and publishes to a fast static site. Search, version history, and ownership labels make each page feel maintained rather than abandoned.

04

Reflection

This is where web dev and automation meet best: the site is only half the product, the pipeline is the other half. Next iteration would add analytics on failed searches to guide what to write next.