• Creator
  • #2145127

    When should we use a headless CMS?

    by techrepub1567763275 ·

    We have a substantial API made in Laravel (no UI, just scripts) and the tech leads have made the decision to make a CRM / CMS using the “Angular” framework because when we get around to rewriting the frontend that’s what we are going to be using.

    If we install a headless CMS (built with Angular) that “has it’s own API” does that mean that API is a sending point that messages to our Laravel Receiving Point?

    Additionally our front-end would function similarly; it will also have an API Sending Point that will also message our Laravel Receiving Point to get the data to display to a user/customer?

    Are their better terms for the Sender / Receiver Points?

You are posting a reply to: When should we use a headless CMS?

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our Community FAQs for details. All submitted content is subject to our Terms of Use.

All Answers

Share your knowledge