How tom21-xd/landing-prometeondev works
Project type and purpose
• This is a static website built with Astro (an SSG framework).
• Purpose: a multi-page “business/portfolio” site with sections like Home, About, Services, Portfolio, Contact, Our Team.
• No runtime “backend” server—everything is pre-rendered at build time.
File structure
• Top level:
• public/ → static assets (images, videos, favicon).
• src/pages/ → file-based routing (.astro pages).
• src/components/ → UI components organized by page (atoms, molecules, organisms).
• src/layouts/ → shared layout(s).
• src/content/ → markdown data for projects.
• src/lib, src/utils → helper scripts.
• src/styles → global CSS.
• astro.config.mjs, tsconfig.json, package.json → configuration & dependencies.
Read README for insights
• Confirms basic Astro setup.
• No custom server or external API integrations mentioned.
Main components
a. Developer & Tooling
– Developer machine, VS Code, Terminal (npm / pnpm).
– Astro CLI & Node.js environment.
b. Source Code Layer
– src/pages: routing entry points.
– src/layouts: Layout.astro.
– src/components: design system (atoms, molecules, organisms).
– src/content: Markdown files → content layer.
– src/lib/utils.ts + src/utils/lenis.ts.
– src/styles/global.css.
c. Static Assets
– public/images, public/videos.
d. Build Process
– Astro build (reads config, runs Vite under the hood).
– Transforms .astro + MD → static HTML/CSS/JS.
– Bundles assets.
e. Output
– dist/ (or default output folder).
– Deployed to static host (e.g., Netlify, Vercel, GitHub Pages).
f. Browser (end user)
– Fetches pre-rendered HTML, CSS, JS.
Relationships & data flow
• Developer writes code → Astro CLI triggers build → reads source code and content → uses components + layouts to render pages → outputs static files → host serves to user’s browser.
• src/pages imports layouts + components; layouts may import global CSS; components may import utils.
• public/ assets are copied unchanged into the build output.
Architectural patterns & design principles
• Component-based design (Atomic Design: atoms, molecules, organisms).
• File-based routing.
• Static site generation (SSG).
• Separation of concerns: content (MD), presentation (.astro components), and assets.
Essentials
• Component boundaries: pages vs. layouts vs. components.
• Build toolchain: Astro CLI → Vite → output.
• Public assets path → served static.
• Deployment target (e.g., Static Host).