Over the festive period I'm planning to redo my personal website.
So, for a hit of inspiration, what tech did you use to build yours?
And feel free to shamelessly plug it if you answer!
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (72)
I went with Gatsby since I wanted to mess around in React land. I also wrote it in TypeScript since I'm currently not using TypeScript at work. Here's the full list, iamdeveloper.com/thanks/
The thanks page is really cool. I definitely should borrow that idea for myself.
Looking like that's the path I'm going to go down. Do enjoy a bit of TypeScript.
I do like the thanks page as well; might do something like that for mine.
Wordpress. And I'm extremely not sorry.
When I first built my super simple site, I used PHP, and customized everything. I wanted to show off my skills I learned in college, etc etc.
I didn't follow the web developer track - I went into mobile. After doing so, I realized a few things about maintaining my website.
Today my website is 100% blog. I'm hoping to add a store to sell some of the things I've designed. But Wordpress has made it a no-mess no-stress task for me, and completely meets my needs for now.
That's awesome Kim! WordPress and PHP used to, maybe still do, get a sideways look sometimes but they are solid, aren't going anywhere and are solid. I'm trying to take my PHP scrappiness over to Laravel. You might check it out if you like WP.
No judgement here! My long-standing website is currently WordPress with a custom theme because it was the quickest & easiest thing for me to do at the time to get something out there with my name on it.
Your reasons are so on point.
I used Gridsome because I really like the static site concept for a personal project and I like Vue. Additionally I used TailwindCSS for styling.
That's it... Hosted on netlify and done.
Drewtown.dev
Blazing fast! Congrats man
Agreed. Wicked fast. Congrats Drew on your high Google PageSpeed scores!
Hi, I just went for plain HTML, CSS, JavaScript.
Usually, my portfolio is something that I use to test my skills. Before this, my portfolio was built in Vue since I was learning Vue back then.
This time I just wanted to see how far can I go without a dependency (and I had a lot of free time :D) and I do not regret it. I loved working in vanilla JavaScript.
Here's the website: saurabhdaware.in
I think it's good to know how things work at a vanilla level, certainly if you've the time to learn.
Very cool. Impressive achievements list. And, very fast indeed. Congrats!
I'm on the JAMstack as many others. I use Gatsby/React with markdown files (markdownRemark).
On top of that, I use images I make myself or some I find on places like freepik.com where you are required to attribute the creator.
For image editing, I use Gimp or PS as needed, and for vectors, Illustrator.
Furthermore, I am fond of hemingwayapp.com and grammarly.com for proofreading.
Cool. Ya, I love the Hemingway app. Been using it for years. Grammarly is great too. If you need a headline analyzer, I'm digging this one at the moment. headlines.sharethrough.com/
Enjoy!
Hemmingway App is interesting; haven't seen that one before. I'll give it a go-- thanks!
My blog is currently using Middleman for static site generation and hosted on Netlify. Neovim for editing. I used HTML from a template on pixelarity.com/
I'm in the middle of a headless rebuild which uses Craft CMS for the backend - hosted on a tiny Dokku VPS, Nuxt.JS for static site generation, Netlify for hosting, and Tailwind for the CSS.
Link: fullstackstanley.com
Ah, I’ve been looking at possible CMS solutions this morning, how is Craft? Any other recommendations of ones worth looking at?
There's a lot to love about Craft. It's really easy to get an admin area set up fast. There's a decent plugin ecosystem available, and the free tier is pretty good for a single user website.
If you want to create HTML sites with it, the templating engine is Twig and it's pretty easy to use although requires building the HTML from scratch (Personally I prefer it this way so I can optimize stuff).
The downside is that if you need more than one user, or GraphQL support, then you'll have to pay for the Pro license. Personally, I just use the Element API plugin instead for generating JSON endpoints.
I've also used Ghost CMS (blog.snipline.io) which is pretty great too for a standard blog and includes everything you need out of the box. Theming is easy and it's self-hostable for free, also has good SEO out of the box so no need to worry about that. It's built in Node which is a little trickier to deploy than Craft (which is PHP) but nothing too bad.
I went with a static site/blog generator jekyll and used minimal mistakes as theme. It's hosted on github pages and all I have to do is push a commit and my website automatically gets updated
My website and portfolio are still incomplete but I can provide my stack thing.
For the old one
How are you finding using Gatsby? It’s something I was considering when I redo mine.
Great. It does a great job creating blogs. With Gatsby, you can use data sources you like. Customization is easy.
Gatsby also provides adequate starter kits and plugins. You don't need to worry about Webpack config so much.
I used (headless) wordpress and gatsby to build my blog @ byteschool.io. Wordpress is self-hosted, frontend is running on Netlify.
How do find using headless WordPress? I did a fair number of projects using WordPress in the past and being able to decouple the front & backend would have been nice.
The WordPress REST API is very good now. I built a site using WP as the backend for my client to manage custom post types and then Axios with VueJS for the front-end. For me at the time, not having to build a CMS was a good thing.
It was alright! A Gatsby plugin did most of the work in terms of hooking things up and fetching data.I'm not an expert at WordPress so customising some things was harder for me, but should be easier for you 😊
That sounds quite useful actually. I've a project due to begin in the new year that we were going to use Markdown for part of it, but I'll take a look at AsciiDoc as an alternative. Especially if it is easier to extend.