Skip to content

Project architecture setup #1

Description

@algerian-tech-makers

Description

Scaffold the base folder structure for the web project according to the agreed architecture. No components, no layout, no placeholder UI.

Folders to create

  • components/ - reusable UI components
  • components/ui/ - shadcn components only
  • app/api/ - Next.js route handlers
  • lib/ - third party configs and utility functions
  • hooks/ - custom React hooks
  • types/ - shared TypeScript types (API responses, common types)
  • services/ - reusable backend caller methods as classes, using fetch (no axios)
  • services/actions/ - Next.js server actions

Rules to respect (add as a comment or README in each folder)

  • Never use axios, use native fetch for edge compatibility
  • Services must be classes
  • Server actions go under services/actions, be mindful of Next.js caching
  • shadcn components go under components/ui only
  • Custom hooks go under hooks, never inline in components
  • Types shared across features go under types

Acceptance Criteria

  • All folders exist with a .gitkeep or a short explanatory comment file
  • No placeholder components or layout are created
  • Folder structure matches the architecture above

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood first issueGood for newcomers

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions