How raulrls/astro-shadcn-portfolio works
Project Type & Purpose
• This is a modern front-end, single-page (or multi-page) personal portfolio website designed to showcase projects, experience, and skills.
• It leverages Astro as the core framework, integrates React-based UI components (from Shadcn), and uses a data-driven approach (with files under /data) to manage content dynamically.
• The README emphasizes learning modern front-end techniques, API/data integration via configuration files, and deployment on Vercel.
Analyzing the File Structure
• Top-level files and directories:
• The presence of configuration files (astro.config.mjs, tailwind.config.mjs, tsconfig.json) indicates a strongly-typed, modern development environment.
• The /public directory suggests that static assets are served from there.
• The /src directory is where the bulk of the application lives, organized into:
▸ /components: Contains UI components like Experience, Footer, Hero, PortfolioFeed, and a dedicated /ui directory with a plethora of UI elements (accordion, button, carousel, etc.).
▸ /data: Holds configuration and content files (experienceData, footerData, heroData, portfolioData) that drive dynamic content.
▸ /layouts: Contains layout files (Layout.astro) that act as wrappers for pages.
▸ /pages: Contains route-specific page files (index.astro as the home page).
▸ /styles: Contains global CSS styling.
▸ /hooks and /lib: Utility hooks and functions (e.g., use-toast, utils.ts) that likely support component logic.
• Central role of the Astro framework, depicting how it ties together layout, data, and components.
• Integration points—especially where React-based Shadcn UI components are being used inside Astro pages.
• That the project is highly modular with the “/data” files driving dynamic content, allowing the portfolio to be easily customizable.
• The Frontend (Astro pages, layouts, components),
• Data sources (configuration and content files),
• Reusable UI libraries especially centered on Shadcn components,
• And the overall data flow from configuration to visual presentation.
This detailed representation will help ensure that every key aspect of the project’s architecture is captured, making it easier for future modifications or scaling.