How limense/astro-instituto-educa works
Project Type and Purpose
• This is a static, content-driven marketing/information website for “Instituto EDUCA,” built with Astro (SSG), Tailwind CSS, and React.
• Purpose: high-performance, SEO-optimized, responsive site with reusable components, no dynamic backend/API.
Key Architectural Components
a. Developer Environment
• Code editor/IDE (VSCode)
• Node.js + npm/Yarn CLI
• Astro CLI (npm run dev/build)
• generate-placeholders.js script (SVG generation)
b. Source Content & Components
• src/pages (Astro page files → route definitions)
• src/layouts/Layout.astro (shared layout wrapper)
• src/components/*.astro (UI building blocks: Header, Footer, Hero, News, etc.)
• src/styles/global.css + tailwind.config.mjs (Tailwind utilities & custom themes)
• src/env.d.ts & tsconfig.json (TypeScript typings/config)
c. Public Assets
• public/images (SVG, JPG placeholders, logos, artwork)
• public/js/main.js (client-side scripts if any)
• favicon.svg
d. Build Pipeline
• Astro’s static site generator compiles .astro pages + React components → HTML, CSS, JS
• Tailwind CSS processes global.css + component classes → minified CSS
• Framer Motion/React code → bundled JavaScript chunks
• generate-placeholders.js → regenerates placeholder SVGs in public/images
e. Output & Deployment
• Dist folder (build output): static HTML, CSS, JS, images
• Hosting on any static CDN (e.g., Vercel, Netlify, Cloudflare Pages)
• Optional: sitemap.xml generation, image optimization plugins
Relationships & Data Flows
• Developer edits source → Astro build pipeline
→ Tailwind processor → PostCSS → final CSS
→ Astro prerender → static HTML+JS
• Build output → Deployed to CDN/host
• End-user browser requests pages → served directly as static assets
• Components interact in browser via React hydration (only where needed)
Architectural Patterns & Design Principles
• Static Site Generation (SSG) for performance & SEO
• Component-based UI (Astro + partial React hydration)
• Utility-first styling (Tailwind CSS)
• Separation of concerns:
• Content & routing: src/pages
• Layouts & site wrapper: src/layouts
• Reusable components: src/components
• Styling: src/styles + tailwind.config.mjs
• Build scripts & config clearly separated at project root