The current Docusaurus configuration still uses the starter deployment URL:
skel/docs/docusaurus.config.js:11 sets url to https://your-docusaurus-test-site.com.- The same config is used for the Deepfence ThreatMapper documentation site, and the repository has an open site issue plus an existing history of deployment/domain work.
Because Docusaurus uses url when generating canonical URLs, sitemap/SEO metadata, and absolute links, the published site can emit links pointing at the placeholder host. Could this be replaced with the actual documentation host (for example, the currently supported docs.deepfence.io host if that remains canonical), and then verified by inspecting a generated page’s canonical URL and sitemap?
The current Docusaurus configuration still uses the starter deployment URL:
skel/docs/docusaurus.config.js:11setsurltohttps://your-docusaurus-test-site.com.Because Docusaurus uses
urlwhen generating canonical URLs, sitemap/SEO metadata, and absolute links, the published site can emit links pointing at the placeholder host. Could this be replaced with the actual documentation host (for example, the currently supporteddocs.deepfence.iohost if that remains canonical), and then verified by inspecting a generated page’s canonical URL and sitemap?