Api Adept : Your Website. Augmented.

Don't let technical problems KILL your AMBITIONS...

  • visitor badge
  • GitHub Followers
  • YouTube Channel Views

    __  __     ____         _____                              __                      __
   / / / ___  / / ____     / ___/__  ______  ___  _____       / ____  ____  ____ ___  / ___  __________
  / /_/ / _ \/ / / __ \    \__ \/ / / / __ \/ _ \/ ___/  __  / / __ \/ __ \/ __ `__ \/ / _ \/ ___/ ___/
 / __  /  __/ / / /_/ /   ___/ / /_/ / /_/ /  __/ /     / /_/ / /_/ / /_/ / / / / / / /  __/ /  (__  )
/_/ /_/\___/_/_/\____/   /____/\__,_/ .___/\___/_/      \____/\____/\____/_/ /_/ /_/_/\___/_/  /____/
                                   /_/

About 1mn to read

I more or less recently stumbled upon the "headless CMS" thing where the actual content is completely separated from the actions one can do to "manipulate" or "act on" the content using an API.




I know that Webservices are coming in Joomla 4 hopefully. But I was wondering if a full fledge "headless CMS" might be the way to go to help Joomla! become popular again to more developers. To me, If more developers do more stuff for Joomla! core and contribute, the whole Joomla community will benefit from it. 

The main benefit of "headless CMS" IMHO, is to lower the barrier to communicate and extend to others php libraries, creating mobile apps to interact easily with Joomla! Or CLI apps for devops, etc... What do you think? Is it worth it?

  • About the author:

    Hi! Alex here,

    Joomla Developer since 2009, focused on Web Services since 2017,

    first in Joomla! 3 with jBackend and com_api

    More recently leveraging Web Services built-in Joomla! core.

    I like paperback format books, challenging projects and defensive cybersecurity "Blue Team".

    You can:

IMPOSSIBLE ?
🡻

Click here and let's find out