# Build and review a SaaS knowledge base with Document360

Connect the documentation workspace, generate source-based help articles and API pages, then inspect the public support experience.

[HTML](https://lukejbyrne.com/library/guides/i7oegqxutbm/)
Content language: en
Author: Luke Byrne
Video published: 2026-05-09
Guide published: 2026-11-02

[Watch the video](https://www.youtube.com/watch?v=I7OEGqXuTbM)
Video language: English

## Start with the product and its real tasks

Luke demonstrates a Document360 knowledge base generated with AI, using Codex through Document360’s MCP server. The description also mentions Claude, Gemini and Cursor as possible AI tools. The useful starting material is the application code and its actual behaviour, not a generic list of support topics.

1. Open the retained product destination, https://bit.ly/4tvnM80, and follow the setup and dashboard chapters. Identify the knowledge-base project and the intended public support site.
2. Connect Document360 MCP to Codex using the route shown at 2:19. Choose the codebase to inspect and define the customer tasks the first help articles should explain.

## Generate help content and API documentation

The sequence generates categories and articles at 4:47, then creates API documentation from an OpenAPI file at 6:48. These sources answer different questions: customer guidance needs a usable task sequence, while API pages need to reflect the supplied specification.

1. Review the proposed categories and organise the first articles around concrete tasks. Compare instructions with the current app and confirm that a reader can follow them in order.
2. Supply the relevant OpenAPI file for API documentation. Check endpoints, parameters and response examples against that file, keeping unavailable or uncertain behaviour separate from documented capabilities.

## Review publication, chatbot answers and branding

Article review and publication begin at 8:15, followed by an AI chatbot at 11:18 and support-site customisation at 12:51. Publishing creates another view to inspect: correct editor content can still be hard to find or poorly presented on the public site.

1. Read the articles before publishing through the demonstrated workflow. Open the public pages and check navigation, links, formatting and the steps for one representative customer task.
2. Ask the chatbot a question answered by the help content and another the content does not cover. Inspect its answers, then apply the intended branding and domain settings and recheck the finished support pages.

## The takeaway

Build the help centre around verifiable product tasks. Check article accuracy, API fidelity and chatbot responses as separate parts of the support experience.

## Workflow resources

- [bit.ly](https://bit.ly/4tvnM80)

## Chapters

- [0:00 Building a SaaS knowledge base with AI](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=0s)
- [0:41 Setting up Document360](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=41s)
- [1:13 Inside the Document360 dashboard](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=73s)
- [1:47 Viewing the public knowledge base](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=107s)
- [2:19 Connecting Document360 MCP to Codex](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=139s)
- [4:47 Generating the knowledge base with AI](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=287s)
- [6:48 Creating API documentation](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=408s)
- [8:15 Reviewing and publishing articles](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=495s)
- [11:18 Adding an AI chatbot](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=678s)
- [12:51 Customizing the support site](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=771s)
- [14:20 Final thoughts](https://www.youtube.com/watch?v=I7OEGqXuTbM&t=860s)

## Sources and limitations

Prepared 2 November 2026 from the published video description and chapters. The actions are editorial follow-along guidance. The full video was not independently watched or transcribed and no new product test was run. Setup, availability and offers may have changed since the recording.

[Original video](https://www.youtube.com/watch?v=I7OEGqXuTbM)