[jawngee]

I don't want to be the jerk in the comments but this seems pretty poorly conceived.

* What are you going to do when you hire a non-technical writer down the road?

* The handwringing about control over SEO smacks of NIH and makes little sense. It feels like a very thin justification for this weird scheme.

* You are a technical company but you couldn't figure out how to apply your look and feel, which isn't unique and feels like a bootstrap template, to something or anything else.

* Your content is JSON in JS

I'm going through some of your blog posts and I just don't see where this kind of overkill is necessary. Nothing I'm seeing can't be represented in markdown with a little front matter. I mean MDX lets you use react components, which doesn't feel like a good idea to me either but feels like a better idea than this.

I dunno, kind of a strange read first thing in the morning.

[bemusedthrow75]

I'm going to tack onto your comment because my instinct was just to write "oh for pity's sake! :-o"

You've hit the nail on the head. There is IMO some distance between eating your own dog food and NIH, and they have happily traversed that distance without a thought.

[chilldsgn]

I'm with you 100%

Maybe I am missing the point, but why would people want to manage their content within their code? It seems incredibly weird and prone to quite messy and unmaintainable code.

I wonder if they even looked into headless CMS options? I just don't understand the thinking behind this, it seems really bizarre and inefficient.

Surely you can just run a headless CMS and fetch content using GraphQL or REST, and have your blog look the way you want it to with React or Nuxt SSR?

Weird...