Project Structure

Recommended folder structure for gettemplate projects

Project Structure

Here's the recommended folder structure when using gettemplate templates:

my-project/
β”œβ”€β”€ components/
β”‚   β”œβ”€β”€ ui/           # Reusable UI components
β”‚   β”œβ”€β”€ layouts/      # Layout components
β”‚   └── sections/     # Page sections (Hero, Features, etc.)
β”œβ”€β”€ pages/            # Next.js pages (or app/ for App Router)
β”‚   β”œβ”€β”€ _app.js
β”‚   β”œβ”€β”€ _document.js
β”‚   └── index.js
β”œβ”€β”€ styles/
β”‚   └── globals.css   # Global styles + Tailwind imports
β”œβ”€β”€ lib/
β”‚   └── utils.js      # Utility functions
β”œβ”€β”€ public/
β”‚   └── images/       # Static assets
β”œβ”€β”€ tailwind.config.js
β”œβ”€β”€ next.config.js
└── package.json

Component Organization

We recommend organizing templates by category:

components/
β”œβ”€β”€ Hero/
β”‚   β”œβ”€β”€ KlipHeroSection.jsx
β”‚   β”œβ”€β”€ AgentoHeroSection.jsx
β”‚   └── index.js
β”œβ”€β”€ Portfolio/
β”‚   β”œβ”€β”€ DeveloperPortfolio.jsx
β”‚   └── DesignerPortfolio.jsx
β”œβ”€β”€ Payment/
β”‚   β”œβ”€β”€ CheckoutPage.jsx
β”‚   └── PricingSection.jsx
└── Forms/
    β”œβ”€β”€ LoginForm.jsx
    └── SignupForm.jsx

Best Practices

1.Keep components isolated - Each template should be self-contained
2.Use consistent naming - PascalCase for components
3.Extract reusable parts - Create shared UI components
4.Maintain clean imports - Use index files for exports