About¶

This knowledge base is a small sample site built to test the Docs Chat browser extension. The content is entirely fictional and describes an imaginary product called the Northwind Driver App — a mobile app for delivery drivers. Nothing here represents a real product, company, or service.

Purpose¶

The site exists so the Docs Chat extension has realistic pages to work with. The extension lets you browse a published docs site, select text you want to change, and have an AI agent edit the underlying Markdown source file in the repo. These pages provide a natural, varied body of content to select and rewrite during testing.

The site also serves as a hands-on learning resource for anyone getting familiar with managing a knowledge base in GitHub — editing Markdown files, navigating a repo, and understanding how docs changes flow from source to published site.

What is inside¶

Product Context covers the people and problems at the centre of the Northwind Driver App. It describes who the primary users are (delivery drivers and dispatchers), the core workflows they follow, and the boundaries of what the app does and does not handle.

Architecture explains the overall system shape. It outlines the main components — the mobile client, the backend API, and the supporting services — and describes how those pieces connect and communicate with each other.

Operations documents the practical side of running the app. It covers the available environments (development, staging, and production), the release stages a change goes through before it reaches drivers, and the steps the team follows when an incident occurs.

FAQ collects the questions that come up most often from people reading or working with these docs. Answers are kept concise and link out to the relevant sections where more detail is available.

Glossary defines the key terms used consistently across the documentation. Consulting it first is useful whenever a word or abbreviation appears whose meaning is not immediately obvious from context.

Decisions is a running log of significant architectural decisions. Each entry records what was decided, the reasoning behind the choice, and any alternatives that were considered but not taken.

Credits lists the contributors who put this sample site together. Because the content is fictional and exists purely for testing, the credits page also notes the nature of each person's involvement.

Safe to edit¶

All content here is safe to edit, break, and regenerate. It is intended to be changed as part of testing the extension's edit flow. If something looks wrong or inconsistent, that is probably the result of a previous test run.