Web Development


When should we use a headless CMS?

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?
Thread display: Collapse - | Expand +

All Answers

Share your knowledge

Related Discussions

Related Forums