0

I'm a full stack MERN developer and I've never used a headless CMS .

I've searched everywhere to understand what are pros and cons of using a headless CMS versus implementing my own rest API solution but just found answers comparing headless CMS versus CMS.

When should I use headless CMS and when should I implement my own Rest API soloution?

  • This question appears to be off-topic because it is about web development which is off-topic at Pro Webmasters. Web development questions may be asked at Stack Overflow but be sure to read their FAQ before posting to ensure your question meets their guidelines. – John Conde Aug 26 at 17:49
0

As usual, the main advantage of a pre-built solution is that a bunch of work is done for you, and the main advantage of a homegrown solution is that you get complete control of it.

A headless CMS will do what it does, and it will come with an admin UI so that people can insert content into it without you having to build the admin UI. You will just need to set up the data structures and then pull the data out for your website.

A homegrown solution will let you structure the data however you like, easily make use of whatever existing databases you have, and do whatever server-side processing you like on the data.

A hybrid solution (where you pull data from a headless CMS with server-side code) will give you a mix of the benefits and drawbacks of each.

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.