No wrong answers here, what tools/stack would you choose and why?
What tools would you choose to create a personal portfolio site if starting from scratch?
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (95)
I would mostly stick to what I am currently using which includes:
Why a custom site generator? This is related to last bullet above. I wanted to be able to generate my publication list as well as abstract pages for each publication directly from a BibTeX file. I also wanted structured data markup for this. So since no existing site generators did this, I hacked something together. The code is a mess (in a private repo for that reason). I wrote it quickly and have hacked in new features as I've wanted them. Think duct tape and silly putty holding it all together.
Site is at: cicirello.org/
The publication list page generated by the site generator from a BibTeX file is at:
cicirello.org/publications/ .
And an example of one of the abstract pages also derived from the BibTeX file: cicirello.org/publications/cicirel...
The content for rest of site is maintained in a hacked together format. This is what I'd change if I started over. Not sure what I'd use exactly.
Astro.js and Tailwind CSS
My most recent portfolio was built with this tech stack:
No need for anything too complicated because this current portfolio is more of a landing page that links to my other profiles. Single page and lightweight andrewbaisden.com/
I built my very first website using HTML/CSS and some JavaScript. But for my personal portfolio I am planning to use react to apply the concepts I learned.
Tools I'd use:
Using only a FE framework I also would use Git versioning from day one.
I wouldn't use a toolkit for complex webapps like react or such unless there are solid reasons to do so, like if your backend is already in place and is API-first or something. If you want to use the opportunity to use and learn something new the I'd go for offline static site generation with Gatsby or Hugo or something. But I'd rather avoid that as it's probably overkill for a personal portfolio website. You want to concentrate on other things when building that rather than learning new stuff meant for fringe cases.
I do not need a portfolio page, but I finally got my personal page to be as I want it: Built on Emacs org-mode publish, static site, with vcs-provided newest change on the first page, categories and clean PDF export, some of the pages embedding Javascript to provide purely frontend interactive content, with local tooling in Emacs, so creating new pages needs just a simple command, and autotools for full make distcheck to ensure that it works.
This page is what I use to publish everything I create — from simple comments (integrated with org-capture) over drawings and notes from roleplaying sessions to lecture slides; and all categorized so it stays easy to find.
It does not showcase technologies, but shows that I know what I use and understand how tools interact.
And it is free and copyleft licensed, so others can build on it: hg.sr.ht/~arnebab/draketo
Missing:
Just plain HTML and CSS. In most cases you don't even need JavaScript. Developers really love to over-engineer. Actually you can skip coding and just grab an HTML Template. Or just grab a WordPress Theme. I personally prefer simple things...Vanilla.
The tools that will help me make my personal portfolio
TailwindCSS, Angular, Firebase hosting, Github actions
How about using Hugo hosted on Netlify. Easy peezy, with SSL and CDN, commit and deploy straight from git. A bit like static hosting with S3 and Cloudfront but all the deployment handled for you Netfly.