Migrate portfolio to Astro (content collections, new layout system, blog & contact refresh)#1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the Gatsby-based portfolio with a static Astro site: content-driven pages (case studies, blog, bio), shared layout and SEO components, Tailwind styling with Typography for long-form prose, and GitHub Pages–friendly static output. This branch also aligns hero width and chrome across pages, refines blog and contact UX, and trims footer legal/demo links.
Migration highlights
outputstatic by default).src/content.config.ts; case studies and blog posts as MDX, bio and legal as Markdown.@astrojs/tailwind;@tailwindcss/typographypowers the sharedProsewrapper.npm run dev; production build withnpm run build→dist/(unchanged deploy story for GitHub Pages where applicable)./about→/resumeinastro.config.mjs.Layout & components
BaseLayout.astro— document shell, SEO (Seo.astro), header/footer, optionalfullWidthMainfor edge-to-edge sections (projects carousel).TopHeroCard— shared top-of-pagehero-shell(gradient + grid) with consistentaria-labelledbywiring.PageContentColumn—max-w-5xl+ horizontal padding for use underfullWidthMainso the hero lines up with the default content column.SocialIconLinks— GitHub / LinkedIn icon links (accessible labels,noopeneron external URLs).Pages & UX
PageContentColumn+TopHeroCard./aboutredirect to/resume.hero-shelltreatment as other heroes (gradient + grid); typographic rhythm matches blog/projects (eyebrow + title + intro).References (docs & tools)
How to verify
npm install npm run build npm run preview # optional: smoke-test production build locallySpot-check:
/,/projects,/resume,/blog, a single/blog/...post, and/contactfor hero width, two-column blog layout on a wide viewport, and footer content.Notes for reviewers
src/tree and lockfile shrink.