Skip to main content
This audit is based on checked-in source, not live server access.

​
Found in source

AreaEvidenceAudit finding
Docs frontendfoundersnest/docs-site/package.json, foundersnest/docs-site/docusaurus.config.tsFoundersNest docs frontend is a standalone Docusaurus site that reads content from ../docs
Build hooksfoundersnest/package.jsonRoot scripts include docs:install, docs:dev, docs:build, and docs:serve
Static outputfoundersnest/docs-site/README.mdDocusaurus outputs to docs-site/build
Main containerfoundersnest/DockerfileFoundersNest production container builds and serves the main app, not the Docusaurus docs build
Reverse proxyfoundersnest/nginx.confChecked-in Nginx config is for the main app and API gateway, not a docs subdomain
Runtime startupfoundersnest/server/start-prod.shMain runtime starts Nginx plus a Node API process
CI/CDno checked-in foundersnest/.github/workflows directoryNo docs-specific GitHub Actions workflow was present in the repo snapshot

​
What can be reused

  • the separation between docs app and docs content
  • the habit of explicit docs build scripts
  • the domain cutover discipline from the existing FoundersNest docs footprint

​
What should not be reused directly

  • FoundersNest branding, titles, footer links, and .io domain assumptions
  • the Docusaurus app itself, because Introd already has an in-repo Mintlify docs root that better matches the desired final experience

​
What still needs live verification

  • the actual host serving docs.foundersnest.io
  • live SSL renewal mechanism
  • reverse proxy config currently attached to the docs domain
  • live deployment trigger path outside source control
Those items were not recoverable from the checked-in FoundersNest repo alone.