{"data":{"site":{"siteMetadata":{"title":"This web dev stuff is hard","author":"Paul Armstrong"}},"markdownRemark":{"id":"7d401bf4-9fef-5df3-be7f-28fe9d667132","excerpt":"It’s been a long time since I wrote a blog. I kept one somewhat active from about 2003 until 2008. The problem was that I never really had a project or life to…","html":"

It’s been a long time since I wrote a blog. I kept one somewhat active from about 2003 until 2008. The problem was that I never really had a project or life to concentrate on, so I spent more time redesigning the site and rewriting the application than actually writing content.

\n

I eventually gave up on the blog. Hunkered down on a life and career. And I learned. I learned a lot.

\n

Something clicked for me recently and I’ve decided to start pouring things out.

\n

The hard part about starting a new blog? I want to rewrite the blog software.

\n

I’ve decided to use Gatsby.js for the software. Why? No reason, really. I haven’t used it before. I have absolutely no understanding of it other than I know that it uses React.js, can create static sites, and is easily deployed.

\n

I’ve created a new project in my editor and filtered out everything but the content/ directory from my eyes so that I concentrate on writing posts instead of rewriting the software. Don’t get me wrong, Gatsby looks great! I just have a terrible habit of rewriting everything I see to just work a little bit differently.

\n

Here’s to a new blog. One which I turn a blind eye to the source, the design, and all the details of the blog, other than just writing.

","frontmatter":{"title":"A new blog","date":"December 31, 2018"}}},"pageContext":{"slug":"/01-new-blog/","previous":null,"next":{"fields":{"slug":"/02-prop-types/"},"frontmatter":{"title":"Prop type performance considerations for React"}}}}