Skip to content

feat: scaffold route groups for feed detail auth and static segments #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
aminamos wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

feat: scaffold route groups for feed detail auth and static segments #224

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/feed-detail-route-groups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Feed Detail Route Groups Architecture

## Motivation
Previously, feed detail routes used a proxy rewrite pattern:
- The proxy intercepted `/feeds/:feedDataType/:feedId` and rewrote it internally to `/feeds/:feedDataType/:feedId/authed` or `/feeds/:feedDataType/:feedId/static`.
- The `authed` and `static` route folders relied on custom HTTP header guards (`x-mdb-authed-proxy`, `x-mdb-static-proxy`) and called `notFound()` if accessed directly.

## Solution: Next.js Route Groups
Using route groups `(authed)` and `(static)` inside `src/app/[locale]/feeds/[feedDataType]/[feedId]`:
- URL paths remain clean and canonical: `/feeds/:feedDataType/:feedId` without exposing `/authed` or `/static` in URL segments.
- `(static)`: Leverages Next.js SSG / ISR for search engines and public visitors.
- `(authed)`: Serves authenticated users with personalized features (subscriptions, custom actions) using dynamic server rendering.
- Eliminates header guard vulnerabilities and simplifies the proxy routing middleware.