Backend: a missing piece in the puzzle

After learning all that frontend- and backend-stuff in fcc I wonder how a real-world-application is built up. Let’s say a customer wants to have a website for his company and to be able to maintain all that data (texts, images) himself.
I’m coming from PHP-world (with CMS like typo3, contao etc) with ready-backed backend-solutions where a user can create pages, articles and add headlines, paragraphs (with wysiwyg-editors), images etc.
Is there something similar for node?
Is there a ready-to-use backend for maintining content?

1: Is there something similar for node? yes check out this link:

1 Like

Actually I was looking for an alternative to eg typo3 based on node.js, so my explanation was not so good.

But your link helped me. In searching for typo3 on I found:


There have been a few but they normally die off relatively quickly, and normally lack any kind of comprehensive support. Ghost, for blogs, is the only open source one that’s really stuck around, as it’s used by a fair few large organizations (but that obviously has quite specialised use case).

The question I would ask is why do you need one written in Node? What possible benefit does that give? There already exist self-hosted solutions (eg the ones you mention, typo3, contao) that are well established, work fine, have vast amounts of documentation, and have things like long term support available.

Note now there are huge amount of headless CMS’ available which normally expose a REST API (though newer ones may provideGraphQL) and just need to be plugged in. ie:

1 Like
Seems to be the “node.js”-version of WordPress; Blogs + simple websites.

It’s intresting that these projects “die off quickly”. Maybe most of the smaller websites are still created by traditional CMS.


Ha! I didn’t expect that question, at least not in this forum…
The sad truth is that I don’t know because I never build a (real-world) website with node.js.
But let’s assume that node is not better than typo3 or contao.

So what is the typical use-case for node.js?
There are also php-frameworks like

General CMS’ (as opposed to an application with an admin panel written for a specific purpose) are difficult to write and maintain and have fairly limited use. It’s not really necessary to reinvent the wheel by rewriting existing, perfectly functional CMS’ framework in another language.

Also, if you dig through the history of CMS’, you’ll find an absolute ton are built by Web Design agencies, who seem to be the main users (outside of enterprise, who generally use SharePoint or similar anyway). An agency builds a CMS (normally in PHP) for themselves so they can build sites quickly to spec. Agency dies or they realise it’s too much work to maintain, project dies, rinse and repeat. I’d be willing to bet that this covers a large % of all CMS’ that have existed in the last 15 years or so. But right now, if you were running an agency, just use a hosted solution and build the front-end using Next.js or similar, maintaining a CMS, even an one you’re hosting, is a massive pain in the ass

1 Like

ok, a variation I didn’t think of: using my “old” cms for backend and some React or whatever for frontend. Good point.

1 Like