Serve The Product Page Outside The Application Runtime
Context
TenCtrl needed a public page on tenctrl.fr while the application, which holds Microsoft sessions, stays on a private development host. The application is a Next.js app, so a marketing route inside it was the obvious shortcut.
Decision
Publish tenctrl.fr as static HTML and CSS from its own repository, served directly by nginx as a separate site, with a default-src 'self' Content-Security-Policy.
Alternatives Considered
A route group inside the Next.js application
Pros
- One codebase and one design system.
- Shared components.
Cons
- Exposes the application runtime to unauthenticated public traffic.
- Every application restart or deploy affects the public page.
A hosted website builder
Pros
- No server work.
Cons
- Third-party scripts and cookies by default.
- Another account and platform to manage.
Reasoning
A static site has no runtime to attack and no dependency on the application's health. It keeps the same nginx contract as the ABD Labs portfolio, and it can move to a static generator later without changing how it is served.