Stackbit integration (3 Part Series)
I've been using dev.to a little over the last year, and a lot more over the last month. It makes sense for me to use this content in my job hunt. I also had a languishing personal page. Originally made as a little experiment with hugo, it hadn't seen love in a while, and due to some jankey usage of high quality photos performance wise it was pretty bad. I'd been meaning to overhaul it for a while, and when the dev.to x stackbit collab came to my attention, it was a perfect fit.
- Use the content I've written, and will be continuing to write, to prove I know at least a few things about programming.
- Get that content wrapped up neatly with a contact page, a statement that I'm looking for work, and a brief about me
- Use my daveparr.info domain
- Make the website more performant than it's current iteration
- Use a clean, simple, slightly professional theme
- Read the instructions in @ben 's post
- Go through the creation flow
- Assign the domain in netlify (I had a netlify hosted JAMstack previously, and my domain was already loaded in there. YMMV)
- Clone the project @stackbit created from GitHub, and follow the readme they left there to help you authenticate correctly
- Update the boilerplate stuff
- Push the changes back to GitHub
I was a little surprised when my local copy suddenly got all my blog files that I then just commited, but that seemed to be ok. Pretty sure I've not broken anything :)
Goals achieved, faster website, with better styling, that will be kept more up to date.
If you are reading this on my website, this is all actually managed through a headless CMS called dev.to. You can use the link to my profile on the left of this article. If you are reading this on dev.to you can see my running website at daveparr.info.