About this site

How this portfolio was built.

A technical overview of the architecture, content model, tooling, and decisions behind carlosmarte.dev.

Astro-first portfolio

Technical SEO

Static generation

CMS-ready content

GitHub repository View Projects

Overview

Built like a real frontend project.

This portfolio is more than a personal landing page. It is structured as a maintainable Astro project with typed content, reusable components, static routes, SEO metadata, and a data layer that can later move from local TypeScript files to a CMS.

Page content is separated by context under local data modules.
Shared TypeScript contracts define the shape components consume.
The UI is composed from reusable Astro components instead of one-off page markup.
SEO and social metadata are handled through the shared layout.

Project facts

Project type

Personal portfolio and technical showcase

Role

Design, frontend development, content modeling, and SEO setup

Rendering

Static site generated with Astro

Content source

Local typed data prepared for a future CMS

Tech stack

The active stack used by this portfolio as an Astro project.

framework

Astro

Generates the static pages and keeps the portfolio Astro-first.

language

TypeScript

Defines the shared content contracts used by page data and components.

styling

Tailwind CSS v4

Provides utility-first styling, responsive layouts, and design tokens.

content

Local structured data

Keeps page copy, navigation, projects, skills, and contact content organized like CMS records.

Current features

Responsive homepage, about page, contact page, and project detail route.
StageLink case study with structured project content and gallery assets.
Dark and light theme support through shared layout components.
Global SEO metadata, sitemap generation, robots file, and social preview support.
CMS-ready local data split by page, project, skills, navigation, and social links.

What I learned

A portfolio becomes easier to maintain when content is modeled before the UI is built.
Shared page types make it easier to catch broken content shapes during Astro checks.
A small static site can still benefit from project-level architecture and technical SEO.

Future improvements

Move local content into a CMS while keeping the same frontend contract.
Add more project case studies with deeper technical notes and screenshots as I complete new projects.
Expand image management for social previews, project galleries, and page-level assets.

Current features

Responsive homepage, about page, contact page, and project detail route.
StageLink case study with structured project content and gallery assets.
Dark and light theme support through shared layout components.
Global SEO metadata, sitemap generation, robots file, and social preview support.
CMS-ready local data split by page, project, skills, navigation, and social links.

What I learned

A portfolio becomes easier to maintain when content is modeled before the UI is built.
Shared page types make it easier to catch broken content shapes during Astro checks.
A small static site can still benefit from project-level architecture and technical SEO.

Future improvements

Move local content into a CMS while keeping the same frontend contract.
Add more project case studies with deeper technical notes and screenshots as I complete new projects.
Expand image management for social previews, project galleries, and page-level assets.

Want to see the rest of the work?

Explore the featured project case study or get in touch about frontend opportunities and practical web projects.

View Projects Contact Me