This repository holds the information, structure and design in www.adrianmoreno.info. This is a playground where I experiment with some technologies, try to optimize the website with Google Page Speed Insights, or test some gulp scripts.
It's a good excuse to overengineer a CV-website, isn't it? ;-)
Theme: Adritian
The page theme is open sourced independently from this site, as a hugo theme Adritian in its own repo.
The content is generated with Hugo, a very fast, flexible and tuneable static content generator. It's made with go, the first reason I started to play around with it - later I discovered its power and strong community.
Installing Hugo is a pre-requirement.
After that, the commands from Hugo CLI can be used, like hugo serve.
The code in this repo is later processed with Github Actions - which will generate the HTML with Hugo, process the CSS, images and JS with Gulp, and export the contents to Vercel.
As simple as it gets!
To customize which branches get to be built by Vercel, the build command and ignore step are customized. This allows me to still keep the generated content in the gh-pages branch, and have that branch ignored by Vercel deployments.
Build command:
echo VERCEL_GIT_COMMIT_REF=$VERCEL_GIT_COMMIT_REF; if [ "$VERCEL_GIT_COMMIT_REF" == "gh-pages" ]; then echo "Skipping build" && exit 0; else echo "Looking for build script" && test -f vercel-build.sh && chmod +x vercel-build.sh && ./vercel-build.sh; fi;
echo VERCEL_GIT_COMMIT_REF=$VERCEL_GIT_COMMIT_REF; if [ "$VERCEL_GIT_COMMIT_REF" == "gh-pages" ]; then echo "Skipping build" && exit 0; else echo "Continuing build!" && exit 1; fi;
Note on Vercel vs Cloudfront
I switched from AWS Cloudfront to Vercel because Cloudfront doesn't support a root object defined for all folders (ie: an index.html for the /experience path). At some point, I might try the option to make them work with Lambda functions, but that will be also a chance to revamp the project infrastructure and set it up as Infrastructure as Code (setting it up with CDK or Terraform).
Do you want some more info about how or why I did something on the site? Drop me a line! (the form is connected to formspree.io by the way, another great piece of software).
Posts with newsletter = true in their frontmatter are emailed to subscribers. The
workflow creates a draft in Resend for review — nothing sends automatically.
Preview locally with npm run newsletter:dry-run.
See docs/plans/2026-07-25-newsletter-system-design.md.