Mapping a documentation source

A scraped documentation site becomes useful once ModuleDesk knows which module each page belongs to. That is what mapping does.

Why a wrong mapping is quiet

The AI will happily cite whatever documentation it was told is relevant. Mapped to the wrong module, the drafts read perfectly well and reference features your customer's module does not have. Nothing flags it — the only symptom is replies that are confidently off-topic.

It applies to a whole prefix

Mapping is by URL prefix, not by page: every page under it is reassigned at once. That is what makes it quick, and what makes a wrong click expensive.

Doing it safely

Map the narrowest prefix that identifies the module — /docs/mymodule/ rather than /docs/. Then open a page from the list and check the module shown next to it before mapping the rest.

Also available in: Español