How gl-ensias-community/gl-ensias works
Project type and purpose
• This is a full-stack JAMstack web application built with Next.js (app directory + React components).
• It delivers marketing pages (about, blog, tools, statistics), authentication flows (signin/signup), a contact form, and an admin/dashboard interface.
• It uses Netlify for hosting + serverless functions, Drizzle ORM for database migrations, and a mail service for contact form notifications.
File structure
• src/app/… → Next.js 13 app-folder routing: page.tsx files drive each route (about, blog, contact, dashboard, auth, etc.).
• src/components/… → Reusable React UI components grouped by domain (Blog, Features, Contact, Header, Footer, etc.).
• public/… → Static assets: HTML fallbacks, JSON data, images, favicons.
• server/… → All backend logic:
– server/functions/api.js → Netlify serverless entrypoint(s)
– server/actions/*.js → Business logic for contact, mail
– server/db/… → Drizzle ORM schemas & migrations
– server/netlify.toml → Function configuration + build settings
• config files: next.config.js, tailwind.config.js, jsconfig.json, tsconfig.json, etc.
README
• Confirms Next.js template usage
• Deployment on Netlify (badge)
• Node v20.x + npm install → npm run dev
Detail without over-fragmenting
• Subsystem (routing, data, UI, storage, external)
• Avoid drawing every single React component – group by domain (Blog, Contact, Dashboard)