Deploy your export to GitHub Pages

On GitHub, create a new public repository named exactly yourusername.github.io, substituting your real username. The name is the magic: GitHub treats a repo with this name as a website and serves its contents at that address.

Skip the README/gitignore options — you want an empty repository, since your export already has its own files.

Extract the ZIP you downloaded from PortfolioDIY. Inside you'll find index.html at the top level, an assets/ folder with your CSS, JS, and images, plus robots.txt, sitemap.xml, and a README with these same instructions.

The structure matters: index.html must end up at the root of the repository, not inside a subfolder. If your unzip tool created a wrapping folder, upload the files inside it, not the folder itself.

In your empty repository, GitHub shows an "uploading an existing file" link. Click it, drag all the extracted files in — including the assets folder — and commit to the main branch.

If you prefer the command line: clone the repo, copy the files in, then git add, commit, and push. Either path ends in the same place.

GitHub Pages builds automatically on every push to main. Within a minute or two, https://yourusername.github.io serves your portfolio with HTTPS included.

Open it and click through every link — nav anchors, project links, the contact button. What you're looking at is byte-for-byte the code you exported; there's no build step that could have changed anything.