Carlos Eduardo Gatti Ferreira

Repo Structure

This repo mixes App Router routes in /app with legacy Pages Router routes in /pages. Keep code changes minimal and avoid changing runtime behavior.

Top-level layout

• /app
  App Router routes and route handlers. Do not place shared UI here.
• /pages
  Legacy Pages Router routes and API routes. Keep for backward compatibility.
• /src
  Shared code for products and features.
  • /src/components shared UI components (used across projects)
  • /src/lib shared libraries (API clients, config, helpers)
  • /src/utils small generic utilities
  • /src/types shared TypeScript types
  • /src/constants shared constants (app-focused)
• /components
  Legacy/shared UI used primarily by Pages Router routes and marketing UI.
• /constants
  Legacy/shared constants used by Pages Router routes and marketing UI.
• /lib
  Legacy/shared libraries used by Pages Router routes and marketing UI.
• /styles
  Global styles (e.g., globals.css).
• /public
  Static assets.
• /docs
  Architecture and operational documentation.
• /scripts
  Maintenance scripts.

Rules of thumb

• Prefer /src/* for new shared code used by App Router projects.
• Prefer /components, /lib, /constants only for legacy Pages Router usage.
• Do not move or delete /pages routes without verifying runtime usage.
• Use alias imports when possible:
  • @/src/... for modern shared code
  • @/components, @/lib, @/constants for legacy Pages Router code

Ownership

• Product/app routes: /app/(projects)/*
• Global flows: /app/(global)/*
• Legacy marketing pages: /pages/*