devportfolio: an Astro portfolio where one config file decides what renders
A modern, minimalist portfolio template built with Astro and Tailwind CSS. Perfect for developers looking to showcase their skills, experience, and projects in a clean, professional way.
At a glance
- What is it?
- RyanFitzgerald/devportfolio is an Astro and Tailwind CSS v4 portfolio template whose entire content model is src/config.ts, so removing a key removes the section from the page. Underneath it is a single index.astro, seven components, and no published releases.
- Who is it for?
- Choose devportfolio if you want a personal site up quickly and can live with one page driven by one file, because it suits a developer whose work fits into skills, projects, experience and education lists. Walk away if you need a blog, extra routes or a test suite, since none of those are wired up.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- Mainly Astro, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- RyanFitzgerald/devportfolio4,995 β Β· +25
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| RyanFitzgerald/devportfolio | 5k | 5k |
25 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
src/config.ts drives every section, and a missing key hides it
The template keeps its entire content model in one TypeScript file, src/config.ts. The keys are grouped by purpose: name, title and description, an accentColor for the theme, a social object with email, linkedin, twitter and github, an aboutMe paragraph, and then the skills, projects, experience and education collections. The first block looks like this:
name: "Your Name",
title: "Your Job Title",
description: "Brief site description",
accentColor: "#1d4ed8", // Hex color for themeThe social object is entirely optional, key by key, so a portfolio without a LinkedIn profile simply leaves that key out. The four collections matter more: if skills, projects, experience or education are removed from the config, those sections are hidden completely instead of rendering empty headings. That single rule is both the extension mechanism and the trap. There is no second content source, so anything that should appear on the page has to arrive through this object.
accentColor is the only theme knob, and Tailwind v4 does the rest
One hex value is the entire theming surface. Changing accentColor in the config changes the accent color site wide, and nothing else in the config touches appearance: sections have no per-entry styling, and there is no theme object, no dark mode flag, and no second accent slot. Everything else visual lives in src/styles/global.css, with Tailwind CSS v4 doing the utility work.
The dependency set is small and current: astro ^5.12.3, tailwindcss ^4.1.11, and @tailwindcss/vite ^4.1.11, which is how the framework is wired into the Vite pipeline. TypeScript is listed as the config language for type-safe editing. The repository also ships tsconfig.json and astro.config.mjs at the top level.
The consequence for anyone restyling is concrete. If you want a second brand color, a dark scheme, or per-project accents, you are editing global.css and the components by hand, because the config offers exactly one colour variable.
Local development is three commands and one npm script
Running the site locally is the shortest part of the setup:
git clone https://github.com/RyanFitzgerald/devportfolio.git
cd devportfolio
npm installThen the Astro dev server:
npm run devWhat that script does is declared in package.json rather than in prose, which is worth reading before you assume anything about the toolchain:
"scripts": {
"dev": "astro dev",
"build": "astro build",
"preview": "astro preview",
"astro": "astro"
},The package is named devportfolio, marked as an ES module with `"type": "module"`, and versioned 0.0.1. A package-lock.json is committed, so the dependency tree is pinned for anyone who wants a reproducible install. Notice what is absent from the scripts: there is no test command and no lint command, so a fork inherits no automated check of any kind. The site is a static Astro build, which means `build` produces files you can serve from anywhere.
Seven components sit under one index.astro page
The README's project structure lists these files under public and src:
devportfolio/
βββ public/
β βββ favicon.svg # Site favicon
βββ src/
β βββ components/ # Astro components
β β βββ About.astro # About section
β β βββ Education.astro # Education section
β β βββ Experience.astro # Work experience section
β β βββ Footer.astro # Site footer
β β βββ Header.astro # Navigation header
β β βββ Hero.astro # Hero/intro section
β β βββ Projects.astro # Projects showcase
β βββ pages/
β β βββ index.astro # Main page layout
β βββ styles/
β β βββ global.css # Global styles
βSeven named components, one page, one stylesheet and one favicon. The listing does not show src/config.ts; the README names that file, the one the whole template depends on, in its configuration section.
Because the sections are components rather than config-driven markup, removing a key from the config hides the section but leaves the component file sitting unused in the repository. That is the cheap way to start, and it is also the file you will edit when you outgrow the eight config fields.
A blog or a second page means writing Astro routing yourself
Read the tree honestly and the scope is clear: src/pages contains index.astro and nothing else. There is no second route, no content collection, no blog directory, and no CMS binding anywhere in the structure. Nothing in the README covers adding a page, and the components list has no entry for posts or a case study template.
So the limits are concrete. A developer who wants a writing section cannot add it by editing config; it means new routes, a content collection or a data source, and a component to render it. There is no contact form, no analytics snippet, no i18n, and no sitemap or 404 guidance in the documentation. Combined with the missing test and lint scripts, a fork starts with no net under it: an edit to config.ts or to a component is only checked by loading the page in a browser.
What you get instead is speed. Static output, one stylesheet, three dependency entries, and a config file small enough to read in a minute.
A fork inherits CLAUDE.md, .cursor/rules and .vscode
The top level of the repository is worth reading before you clone it: .cursor/, .gitignore, .vscode/, CHANGELOG.md, CLAUDE.md, LICENSE.md, README.md, astro.config.mjs, package-lock.json, package.json, public/, src/ and tsconfig.json. CLAUDE.md and .cursor/rules are called out in the README as files that ship with the template so it fits existing AI workflows.
That is a gift and a liability. The rules encode another author's conventions for editing the project, and they arrive in your fork whether or not you use the same tools. Decide before your first commit whether to keep them, since an editor assistant reading stale instructions is a worse problem than no instructions at all. The same goes for .vscode, which pins editor behaviour only you may not want.
One more thing to know before upgrading an older site: the README says this version was completely rebuilt from the ground up from V1. A V1 site is not a drop-in upgrade path into this structure.
Static hosts are the deployment target, and the base path is unstated
Deployment is presented as a short list of static hosts: Netlify, Vercel, GitHub Pages, Cloudflare Pages and Render, each linking to the matching guide in the Astro documentation, with a pointer to the rest of those guides for anywhere else. The claim is that any static hosting service works, and in most cases at no cost. Since the build is a static Astro site, that claim follows from the output rather than from anything special in the template.
What is not stated is the part that bites project sites. The repository homepage and the live preview both point at https://ryanfitzgerald.github.io/devportfolio/, a GitHub Pages project URL, yet no site or base path setting is mentioned anywhere in the README. If you publish under a subpath rather than a domain root, verify that setting before you assume asset URLs resolve.
There is also no custom domain walkthrough and no 404 page in the structure, so both of those are your own work.
Version 0.0.1, no tagged releases, last push 2026-05-14
package.json still reads version 0.0.1, and the repository has no GitHub releases at all, so there is no tag to pin a deployment to. The last push landed on 2026-05-14. The repository is not archived, and a CHANGELOG.md exists that the README points you to for the history.
That shapes how you consume updates: you either track the default branch and read the changelog yourself, or you fork and stop. Neither choice is documented, so decide deliberately rather than assuming a release train.
The other thing to check before publishing is the sample data. The example bullets ship with illustrative numbers: serving 1M+ users, a 40 percent API response time reduction, a 3.8 GPA, a Dean's List. They are placeholders in a config file, and they read like achievements. Replace every one of them, since a stale placeholder is the failure mode a template like this invites.
Editorial conclusion
Choose devportfolio if you want a personal site up quickly and can live with one page driven by one file, because it suits a developer whose work fits into skills, projects, experience and education lists. Walk away if you need a blog, extra routes or a test suite, since none of those are wired up. Before publishing, replace the sample bullets such as the 1M+ users line, check the base path in astro.config.mjs if you deploy under a subpath, and read CHANGELOG.md since there are no tagged releases to diff against.
Frequently asked questions
How do I customize the devportfolio template?
Edit src/config.ts. It holds name, title, description, accentColor, an optional social object with email, linkedin, twitter and github, aboutMe, and the skills, projects, experience and education collections. Removing skills, projects, experience or education hides that section entirely.
What does devportfolio need before I can run it locally?
Clone the repository, change into the devportfolio directory and run `npm install`, then `npm run dev`, which package.json maps to `astro dev`. The same file maps `build` to `astro build` and `preview` to `astro preview`, and there is no test or lint script.
Which versions of Astro and Tailwind does devportfolio use?
package.json pins astro ^5.12.3, tailwindcss ^4.1.11 and @tailwindcss/vite ^4.1.11, with the project itself at version 0.0.1 and marked as an ES module. Icons come from Tabler Icons and the config is TypeScript.
Can I deploy devportfolio to GitHub Pages or Netlify?
The README lists Netlify, Vercel, GitHub Pages, Cloudflare Pages and Render, each linking to the matching Astro deployment guide, and says any static hosting service works at no cost in most cases. No site or base path setting is mentioned for subpath deployments.
Does devportfolio include a blog or more than one page?
No. The structure lists a single page, src/pages/index.astro, with components for About, Education, Experience, Footer, Header, Hero and Projects. No blog route or content collection is documented, so extra pages mean writing Astro routing yourself.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ryanfitzgerald-devportfolio)Star history chart for your README
[](https://hysenlabs.com/projects/ryanfitzgerald-devportfolio)Was this useful?