Codebase Overview

This documentation set is generated from the active Stackflo workspace, with a focus on the backend APIs and this docs site.

Primary projects

Backend platform

• Location: stackflo-backend
• Core role: API and business workflows for compliance, risk, policies, evidence, and vendors.
• Runtime stack: Laravel + PHP with Vite tooling.

Documentation app

• Location: stackflo-docs-fumadocs
• Core role: customer-facing docs built on Fumadocs.
• Runtime stack: Next.js, React, Fumadocs.

How routing is organized in backend

The backend central route file wires common auth and middleware behavior, then loads feature route modules (tools, evidence, policy, risk, and more) from dedicated files. This keeps each domain isolated while preserving shared auth and domain checks.

How docs are published

The docs app loads MDX files from content/docs and serves them under /docs, so each new .mdx page in that folder becomes part of the docs experience.