I disagree on not building your own blog engine as a general rule: Building a blog engine can be as simple as using a markdown-to-HTML converter library on your server, and using your backend's admin interface. Or a simple HTML page with a big text box and submit button. Depending on use case, this can be fine. The cognitive complexity of integrating with a 3rd-party engine can be more complicated than writing a simple one.
Which brings me to a big point the article missed: Page loading speed is important for search ranking. I have a blog I add to once every other month. It uses HTML and CSS, and I write it in Django admin using markdown. Lots of room for improvement UI-wise, for both reader experience and writing interface. Yet, it's a low-traffic site, and most of the blog entries show up on the first page of Google for relevant keywords. Relevant: It gets a perfect Google Page Speed Insights score, by virtue of being an HTML/CSS page.
I bring this up for 2 reasons: Using a blog engine will probably make it tougher to get fast load times. You can rank high on Google just by having good content and fast load times.
Which brings me to a big point the article missed: Page loading speed is important for search ranking. I have a blog I add to once every other month. It uses HTML and CSS, and I write it in Django admin using markdown. Lots of room for improvement UI-wise, for both reader experience and writing interface. Yet, it's a low-traffic site, and most of the blog entries show up on the first page of Google for relevant keywords. Relevant: It gets a perfect Google Page Speed Insights score, by virtue of being an HTML/CSS page.
I bring this up for 2 reasons: Using a blog engine will probably make it tougher to get fast load times. You can rank high on Google just by having good content and fast load times.