How biznessology/vibeathon-landing-page-build works
Project type and purpose
• This is a single-page frontend application built with Vite, React, and TypeScript.
• It renders a static marketing/event site (“Lovable”) with sections like Agenda, Prizes, Timeline, RegistrationForm, etc., using shadcn-ui and Tailwind CSS for styling.
File structure
• Top-level files & configs
• index.html, public/robots.txt – static entry point and public assets
• vite.config.ts, postcss.config.js, tailwind.config.ts – build & CSS pipelines
• tsconfig*.json, eslint.config.js – TypeScript & linting
• src/
• main.tsx → mounts the root React App
• App.tsx / App.css → top-level layout & global styles
• pages/Index.tsx, NotFound.tsx → route targets
• components/… → feature sections (Agenda, Hero, Timeline, etc.)
• components/ui/… → shadcn-ui primitives & custom wrapped components
• hooks/… → React hooks (useMobile, useToast)
• lib/utils.ts → shared utilities
• No backend code or database; it’s purely client-side.
Key insights from README
• Tech stack: Vite, TypeScript, React, shadcn-ui, Tailwind
• Deployment via Lovable platform (publishes a static bundle)
• Editing via IDE or Lovable’s online editor
a. Main components
• Developer environment
• Code repository (Git + Lovable)
• Build system (Node.js, npm, Vite)
• Static asset pipeline (PostCSS, Tailwind)
• React runtime in browser
• Component hierarchy (App → Pages → Feature Components → UI Primitives)
• External services (Lovable platform for CI/CD & hosting, CDN)
b. Relationships & interactions
• Developer → Git pushes → Lovable CI → Vite build → static bundle
• Browser requests index.html → bundle.js, CSS → React hydrates App
• App uses React Router (implicit via pages/) to switch views
• Pages import and compose feature components → each uses UI primitives
• Components call hooks for responsiveness/toast → utils for helper functions
c. Architectural patterns & design principles
• Component-based architecture (React)
• Atomic design via shadcn-ui primitives → composable UI building blocks
• Single entry point (SPA) with client-side routing
• Separation of concerns: styling (Tailwind), logic (hooks), presentation (components)
d. Key technologies/frameworks
• Vite: fast dev server & bundler
• TypeScript: type safety
• React: UI library
• shadcn-ui: headless/unopinionated component primitives
• Tailwind CSS: utility-first styling
• Lovable: git-integrated hosting/CI