Pros and Cons of writing your own CMS

#react #webdev #serverless

While working on my own personal brand, grantwatson.app (which is still under development), one item came up for my consideration:

How am I going to handle my blog portal?

For this app, I wanted to use the fast and lightweight approach for development.

The following is major techs used:

    * React
    * Firebase

Pretty straight forward. I have worked on a few smaller apps that I used Firebase to store small nodes of information and called them to the React UI, and if I wanted to use that same functionality in this current app, I went ahead and made the connections.

After a few iterations of my app, the issue of how to implement a blogging system was nagging at me. I should have considered using something like a headless CMS at the beginning, but I also did not want to scrap what I already created to start anew.

So, I began working on the CMS part. The struggle I am facing is simple, CMS engines like Strapi and Wordpress are pretty much ready out of the box. They also have most areas already covered and considered when it comes to API calls and delivery systems set in place.

The aspect of learning this on the go, and not having to worry about hosting two separate apps seem to be the only areas that is stopping me from using something like the two aforementioned CMS tools.

How I fixed 20 seconds of lag for every user in just 20 minutes.

Our AI agent was running 10-20 seconds slower than it should, impacting both our own developers and our early adopters. See how I used Sentry Profiling to fix it in record time.