fec-nextjs-project-standard

To structure a Next.js 14 App Router project, enforce conventions for layouts, routing, loading, error, and not-found surfaces. This standardizes project architecture and reduces structural drift across repositories.

Best practices for Next.js server and client boundaries involve establishing clear rules for component separation. Proper boundaries ensure server-first rendering and align with project-wide architecture conventions.

Choose SSR, SSG, or ISR for Next.js data fetching based on specific routing needs. The standard requires clear rules for these rendering strategies to ensure optimal performance and accessibility across your routes.

To generate SEO metadata correctly in Next.js 14, follow metadata generation rules integrated with your data fetching strategies. This ensures proper SEO metadata outputs and maintains performance and accessibility standards.

Yes, this Next.js project standard covers middleware and route handlers. It provides guidelines for middleware placement and route handler patterns to maintain consistent project-wide architecture.

To audit an existing Next.js project against App Router best practices, check it against the standard's rules for server actions, metadata, and component boundaries. This identifies structural drift and enforces consistent conventions.