Personal Learning Project

AI-Assisted Engineering Portfolio

This website is both my engineering portfolio and a hands-on learning environment where I practice using AI, VS Code, Astro, Git, and GitHub Pages to turn technical work into clear, accessible project stories.

AstroHTMLCSSVS CodeGitGitHub PagesAI-Assisted DevelopmentResponsive DesignAccessibility
Luis Leon Pineda engineering portfolio displayed in a web browser

Project Type

Living Learning Project

Framework

Astro

Development

VS Code and AI

Deployment

GitHub Pages

Overview

Learning web development by building something useful

I started this website to create a permanent home for my engineering work. Instead of treating it as a one-time portfolio assignment, I am using it as an ongoing way to learn modern development tools and improve how I communicate technical projects.

Every improvement gives me a practical problem to solve: organizing Astro pages, understanding shared layouts, writing responsive CSS, managing images and documents, fixing links, improving metadata, and validating a production build before publishing it.

Learning Process

An iterative workflow built around questions, code, and verification

01

Define the Goal

Start with a concrete page, content, layout, or debugging problem and describe the intended result in plain language.

02

Build with AI

Use AI inside the development workflow to inspect the repository, explain unfamiliar code, suggest changes, and implement focused updates.

03

Review the Code

Read the Astro, HTML, and CSS changes in VS Code to understand what changed, where it is used, and how it affects the page.

04

Verify and Refine

Run a production build, inspect the rendered result, identify problems, and repeat the process with smaller improvements.

AI as a Development Tool

Using AI to accelerate learning without skipping understanding

I use AI as a collaborative tool for exploring the codebase, explaining unfamiliar syntax, locating the source of a visual issue, drafting content, and implementing focused changes. This makes it possible to move from an idea to a working result quickly.

The important part of the process is reviewing the result. I compare the change with the original request, inspect the affected files, run the Astro build, and continue refining anything that does not match the intended design or message.

What I am practicing

  • Writing clear, specific requests for technical work.
  • Reading and editing Astro component markup.
  • Tracing CSS selectors back to the pages that use them.
  • Evaluating AI-generated changes instead of accepting them blindly.
  • Using build output and browser behavior as evidence.

Technical Foundation

A small static site with reusable structure

Astro Pages

File-based routes provide the home, about, experience, contact, project index, and detailed project pages.

Shared Components

A common layout, header, footer, and project-card component keep navigation and repeated content consistent.

Global CSS

Organized design tokens, responsive grids, project layouts, cards, galleries, and mobile breakpoints define the visual system.

Static Deployment

Astro generates static HTML that GitHub Pages can serve directly from the public portfolio URL.

Work Completed

Improving the portfolio one real requirement at a time

  • Built responsive home, about, experience, contact, and project pages.
  • Created reusable project cards and a shared site layout.
  • Developed a detailed FPGA capstone case study with technical diagrams.
  • Organized and documented the global stylesheet by page and feature.
  • Added accessible image descriptions and full-resolution gallery links.
  • Corrected document paths, project links, metadata, and social preview titles.
  • Used repeatable production builds to catch invalid markup and routing issues.

Reflection

The portfolio records both engineering work and technical growth

This project is teaching me that effective AI-assisted development is not only about generating code. It requires describing the goal, preserving context, checking assumptions, understanding file relationships, and verifying that the final result actually works.

As the site grows, I plan to keep improving its project documentation, accessibility, responsive presentation, performance, and deployment workflow while applying what I learn to new engineering projects.

Explore the Project

View the source or return to the portfolio