How bliss-e-v/webpage works
Project type and purpose
• This is a static, content-driven website built with the Astro framework.
• It uses component-based .astro and .tsx files to assemble pages, with Markdown frontmatter driving the blog.
• Styling is handled by Tailwind (via @astrojs/tailwind + PostCSS), and there’s a 3D effect via Three.js and three-noise.
• Output is a set of purely static files deployed to Vercel (vercel.json).
Main components
a. Developer Environment
• Code repos (GitHub)
• Local dev server (astro dev)
• Scripts (generate_final_newsletter.cjs, postcss-replace-attribute-selectors.cjs)
b. Source Code
• src/pages → route definitions (.astro pages + Markdown posts)
• src/layouts → Layout.astro (site-wide) & Newsletter.astro (email layout)
• src/components → UI primitives, 3D scenes, data modules (members, media, events)
• src/utils → helpers (getSortedPosts, types)
• src/global.css & tailwind.config.cjs → global styles
• astro.config.mjs → build configuration
c. Public Assets
• public/ → all static assets (images, fonts, site.webmanifest, _headers)
• subdivided into authors/, images/, posts/, assets/
d. Build Pipeline
• Astro compiler → parses .astro/.tsx, injects components, resolves frontmatter → HTML
• Tailwind JIT → transforms classes → CSS
• PostCSS plugin → attribute-selector rewrite
• Output → /dist (static site)
e. Deployment & Hosting
• Vercel pulls from GitHub → runs build → serves /dist behind CDN
Relationships & data flows
• Developer commits code → GitHub
• Vercel CI/CD → runs astro build (uses astro.config.mjs + tailwind.config.cjs + postcss.config.js)
• Astro build:
• Reads src/pages & Markdown → generates HTML via Layout & components
• Styles via Tailwind + PostCSS → bundled CSS
• Copies public/ → dist/
• Browser requests pages from Vercel CDN → static HTML/CSS/JS served
• Interactive bits (Three.js) loaded at runtime from components
Architectural patterns & principles
• Component-based SSG (Static Site Generation)
• Separation of concerns:
• Presentation (components & layouts)
• Content (Markdown frontmatter + data modules)
• Styling (Tailwind + PostCSS)
• Scripts/automation (newsletter generator)
• Utility-first CSS (Tailwind) & minimal JS
Technologies & integrations
• Astro (framework)
• Node.js scripts (newsletter, PostCSS plugin)
• TailwindCSS + @astrojs/tailwind
• PostCSS + custom attribute-selector replacer
• Three.js + three-noise for 3D backgrounds
• TypeScript / TSX for type safety
• Vercel hosting
Final advice
• Be exhaustive but clear: break the system into “Developer → CI/CD → Build → Output → Runtime.”
• Every folder that feeds into the build (src/pages, src/components, public/)
• Third-party integrations (Tailwind, Three.js, Vercel)