Hosting: decide the deploy target and get the course online

The course is not deployed anywhere. Nothing about the app blocks it — this is an infrastructure question.

Why GitHub Pages is not the answer

Pages does not serve private repositories outside GitHub Enterprise Cloud, and this repo is private. So Pages only becomes an option if the repo goes public, which is a separate decision.

The intended path

A Nextcloud-provisioned domain, which needs sysadmin work and will take time. Anna has no access to the website host.

The conversion work, whenever a target exists

The app currently server-renders the track and module routes on demand (ƒ in the build output), so it needs a Node host as-is. It can be made fully static instead — nothing blocks it: no cookies(), headers(), searchParams or fetch anywhere, and all content is filesystem markdown.

For a static deploy:

• generateStaticParams on app/[track]/[level]/page.tsx and app/[track]/[level]/[module]/page.tsx
• output: 'export' in next.config.ts
• basePath if it is served from a subpath (Pages would force /academy)
• a .nojekyll file — without it Pages strips /_next/, silently breaking every asset
• a build-and-deploy workflow

Decide first

Static or Node? That answers whether the conversion above is needed at all.

Done when

The course is reachable at a stable URL.

Start by reviewing the deployment options and the route files app/[track]/[level]/page.tsx and app/[track]/[level]/[module]/page.tsx, then inspect next.config.ts and the build output. Decide between a static export and a Node host before making conversion changes. Done means the course is reachable at a stable URL.