What if I moved my blog from <a href="https://preposter.us">Preposter.us</a> to <a href="https://nextjs.org">Next.js</a>?
I don't plan on abandoning the Preposter.us project, but I'd like to get more intimate with the software that comes from the company I work for, and it would be nice to take a break from blog programming for awhile.
The first step is to create a basic blog in Next.js and get it hosted. As you can see I've begun this process with the help of the <a href="https://nextjs.org/learn/basics/create-nextjs-app">Next.js tutorial</a>. This embryonic blog is currently deployed and hosted at <a href="https://nextjs-blog-five-olive.vercel.app/">nextjs-blog-five-olive.vercel.app</a>.
So what's next?
<h3>Preposter.us to Next.js TODO:</h3>
<ul>
<li>~~Write a script to export Preposter.us posts as Markdown w/ YAML Front Matter~~</li>
<li>~~Import Markdown posts into this repository~~</li>
<li>~~Deploy to staging site~~</li>
<li>~~Point <a href="https://jasongullickson.com">jasongullickson.com</a> at the new site~~</li>
<li>Clean-up (issues with Markdown hyperlinks, strikethrough, etc.)</li>
<li>Import legacy content (everything that wasn't currently on the Preposter.us version of jasongullickson.com</li>
</ul>
I think that's about it.
Of course there will be ongoing work to improve the basic Next.js blog code itself. I'm sure there's all sorts of interesting things that I'll be able to add as I get more familiar with the technology. For now this move will put me in frequent contact with the code and give me an excuse to hack on it when I'm working on my own projects as well as the ones I do for Vercel professionally.