Integration compatibility
StratoLMS is an Astro site. Integrations are allowed, and the build guard
(stratolmsGuard) is the last integration so a later plugin cannot make a paid
lesson static or weaken the CSP.
Supported and tested
Section titled “Supported and tested”- The
fixtures/integration-compatsite (P3.2) @astrojs/mdx,@astrojs/sitemap,@astrojs/rss(already in the starter)
Supported with CSP additions
Section titled “Supported with CSP additions”Analytics, error reporting, and hosted fonts. Declare hosts in
stratolms.config.mjs under csp.additions. buildCsp rejects 'unsafe-inline'
in script-src, wildcards, and HTTP hosts.
Supported with the style-attribute opt-in
Section titled “Supported with the style-attribute opt-in”Shiki syntax highlighting and KaTeX need csp.allowInlineStyleAttributes: true.
Unsupported
Section titled “Unsupported”<ClientRouter />— not supported by Astro’s CSP@astrojs/partytown— inline bootstrap and worker proxying defeat the CSP@astrojs/db— use the StratoLMS store- Starlight — its own routing and styling; run documentation as a separate site
- Any integration that sets
output: 'server', turns sessions on, or makes/learnstatic — the guard stops those builds
Change adapters with stratolms init --adapter, never astro add <adapter>.