Exactly one year ago I asked the dev community what tech they used to build their personal website/portfolio and later compiled the answers.
dev.to communityβs top tech to build a website/portfolio
Jacob Baker γ» Mar 1 '20
#discuss
#webdev
#career
#showdev
So to carry on the tradition (tradition!):
What tech did you use to build your personal website/portfolio?
Bonus question if you answered last year: has it changed?
Feel free to shamelessly plug your website/portfolio if you answer!
Latest comments (55)
I used Next and Node and it works fine. Next time I will try Gatsby because I am yet to use it in production.
I used Hugo and Gitlab Pages for a site generator and hosting, along with org-mode for my website. The university I attend has a program for hosting websites, so when I leave the university in May, I'll be setting up a custom domain. I am still working on it, along with some projects to actually add to my portfolio (namely, my first full project is a curses RSS aggregator written in python).
n3rd.github.io , I built it with noting complex, just plain 'ol HTML, CSS and JavaScript but spiced it up with a few eye catching into animations
I have an unusually simple setup: a pure HTML/CSS/JS site running on GitHub pages, because in my opinion that's really all you need. I haven't migrated since (though it's been tempting to switch to something like Netlify or Vercel), primarily because of GitHub's excellent handling of my domain. My root domain (micahlindley.com) is connected to the micahlt/micahlt.github.io repository, but I've grown to love the fact that every GitHub repo built in vanilla HTML/CSS/JS can be easily deployed to Pages with no additional domain setup. It's simple and elegant, and it gives me a challenge to keep the site performant without utilizing server-side rendering or React.
I did the same thing with the Github pages. pages.github.com/ It was just a really easy way to quickly get up and running. And not needing to worry about maintaining a domain was a big selling point for me.
I didn't do the extra layer of fancy though that you did to have your root domain connected to your repo. I like that extra touch :)
torik17.github.io/
This year I rebuilt my personal site, justmatt.co. I challenged myself to see how small and fast I could make the final result, and so I decided to use a static site generator. I eventually settled on Metalsmith because it's written in Node and has a large number of plugins that make development easy.
I started with Bootstrap for the layout, but I only included the grid system, which comes out to about ~7kb. I focused on a lightweight design, taking care to only include code and resources that were actually being used on each individual page. I implemented lazy-loading for images and an image-scaling pipeline in my site generator that creates several resolutions of each image in both WebP and jpeg format to minimize downloads to the client.
In the end, a typical article on my site is ~150kb gzipped with a header image and loads in under a second on my laptop. The basic article template with with a small amount of content and no image is ~80kb gzipped. I'm pretty proud of what I ended up with and I think it will serve me for a long time.
Still doing GitHub pages and Jekyll. Visit at canro91.github.io
I use Ghost for my two blogs (candost.blog and bitekdunya.com) and Jimdo for my portfolio page (candostdagdeviren.com). I like the both options. I just finished the work on my blogs. They are working with DigitalOcean the setup was really easy.
I built both of my current sites with plain CSS/HTML/JS. π΄
kay.is
fllstck.dev
Both hosted on GitHub.
Flask for backend, and MaterializeCSS with custom SCSS styles (including vanilla JS and anime.js) for frontend stuff
In hindsight, I should have taken the bullet and use NodeJS for my backend as well, but that's for my next web-based project. With python as your backend language, frontend technologies are always an afterthought.
I built mine, andreigatej.dev, with Gatsby and I could say it was a pretty smooth experience building something with it.
It also made me more curious about how it works under the hood, so I hope one day I'll find the time to explore.