Headless CMS vs Traditional CMS

[@j.r.r.tolkien8724]

Amazing explanation. The only one that made it easy to understand the point of using a headless cms.

[@YoungLink51423]

This was a great intro. The robot head's falling was a great metaphor that blew my mind, no pun intended. That was what actually made me "get it"

[@AsmarahChoudhry]

Explained so simply. Superb job. Keep it up

[@shiridisaigudla7078]

🎯 Key points for quick navigation: 00:00:01 *📜 Introduction to CMS* - Introduction to the concept of CMS and its role in website development, - Overview of the basic functions of a CMS, including text creation, digital graphics, page layout, and navigation, - Mention of non-technical accessibility due to the absence of coding requirements. 00:00:56 *🏗️ Traditional CMS vs. Headless CMS* - Explanation of traditional CMS which controls both back end and front end of a website. - Definition of headless CMS that manages only the content (back end) without front-end functionalities. - The flexibility of front-end developers in a headless CMS to use any framework they want. 00:02:17 *🌐 API and Front-End Presentation* - Description of how content in a headless CMS is requested and delivered through an API, - Explanation of the separation between the back end and the front end, - Emphasis on the unformatted nature of the content delivered and the responsibility of the front end. 00:02:44 *🚀 Advantages of Headless CMS* - Discussion on the growing popularity and benefits of headless CMS architecture, - Flexibility for developers to use any framework, - Adaptability of the content for any application or device, - Future-proof nature allowing evolution with technology. 00:03:14 *🏢 Porttrap ONE Offerings and Conclusion* - Introduction of Portrait 1's offering of both traditional and headless CMS, - Use case examples for mixing both CMS types depending on the website's needs, - Final remarks and invitation to learn more about Portrait 1's headless API on their website. Made with HARPA AI

[@PremVakilVarma]

the content is too good , explained very well in just 4 minutes.

[@Spelarkivet]

Best explanation I've seen so far. Thanks.

[@anandhunt1000]

one of the best expanation of headless cms..i am now 80 percent clear...

[@harshmathur7817]

that's so much information represented in easy way ..good work

[@mayankvora8329]

Superb explanation with cool graphics. Great job

[@richards16]

What a great explanation! Thank you very much.

[@aliebi13]

this is so understandable way to explain this subject for us.

[@OCTACHRON_iOS_Drum_Sequencer]

Great explanation. Thank you very much! 😊

[@marekb3702]

Amazing explanation!

[@chadgregory9037]

so basically any microservice api is a headless cms (if its hitting a db that is)

[@bullymaguire2335]

mommy voice so good !

[@sayedaliaqamousavi9064]

Excellent explanation 👌

[@coding_tipz]

Great visualization for the explanation, Thanks !

[@KulturanCov]

So what is then the difference between traditional CMS (WordPress, correct?) and these newer website/no-code builders like SquareSpace? Are they the same?

[@nat4466]

Amazing explanation, thank you so much

[@MohammadBarghamadii]

Thank you for Explaining

[@khatariinsaan5284]

Perfect Explanation

[@MartinezCalderonCo]

What are the use case scenarios where non-coders would need a headless cms?

[@josearmandozeballosduran7086]

Such a good explicación

[@redleo4257]

Great explanation.. Thanks mate!!

[@muskaansingh.1]

Very well explained with great visualisation✨✨👏👏

[@sabuein]

Thank you so much.

[@DSudhakarHiriyur]

followed the tutorial exactly right, but still different. Using trial version. Thank you*

[@edisonmondal2798]

wow wow wow. Thanks in a word of this overview. 😃

[@davethewebguy]

I'm confused though. A "headless CMS" is just a different way of saying stored images and other data? Why is that not just FTPing files to someplace for reference in whatever framework?

[@eleissamel]

thank you

[@Frank-ev9gp]

how about Mantine UI?

[@Evercreeper]

deserves more subs

[@chind0na]

6 yrs ago this metaphorical representation of Headless cms was put out as a video by Sanity.

[@Misz1986]

Maybe another quick explanation: HeadLessCMS is editing mainly only data and a simple unique appearance from the CMS level, with no connection to editing features from the frontend, and there are no traces of any code responsible for the appearance of the page in the CMS panel code. Headless mainly brings benefits if the panel is to manage mainly data, and especially the API transferred to various websites/mobile applications android/ios - "One ring that rules the rest". In my opinion, HeadLess is a bit of a bad name. However, if what matters is the quality of appearance and comfort of editing, "traditional" is like UE5 in gamedev - you can see the results immediately., The mentioned flexibility is different and does not mean that there is less of it and rather has greater potential for optimization if the CMS is properly constructed. Front-end frameworks like Nuxt.js provide quite a headache when errors occur, anywhere in the JS code or on the API error side. Traditional provides rather easier error control. Would it be a problem to edit the same data on the Android application? If it also runs HTML, or rather it can be assumed that it does, it is quite the opposite with a well-built CMS.

[@ロジャー-n3s]

Before watching this video, I thought "headless" means no UI (command lline only) for the CMS 🤣

[@naqiabedi]

It helped. Thanks!

[@SetMyCloud]

Nice Video Team

[@MohamedRabi]

Fantastic!

[@rir360master]

Thanks.

[@abdulrasheedaj6674]

great👏👏👏👏

[@Escko]

great , ty

[@문문치연]

Good~

[@wilmotfulton4400]

Lee Barbara Wilson Kevin Thomas Margaret

[@BrianWhite-g1z]

Jackson Angela Jones Frank Clark John

[@wilmotfulton4400]

Thompson Sandra White Kimberly Lee Brenda

[@zarrahjanesales3271]

Its over