Intro: Types of CMS - Traditional CMS, Headless CMS, DXP 

You are most welcome! Manthan, we just launched a VERY EASY Next.js BLOG starter with automated deployment to Vercel - please try it out and let me know your thoughts: you can start with reading this and watching the video help.agilitycms.com/hc/en-us/articles/360049603332 or just jump in and create your new blog for free here and follow the steps: manager.agilitycms.com/org/subscriptions/instance-setup?template=blog-with-nextjs

Glad you enjoyed it!

Thanks! I think the fact that Agility has pages, modules (components), and sitemaps as native constructs is the biggest differentiator I was getting at here, essentially allowing you to expose component-driven development concepts for your editors.

True, but with Contentful you pay extra for it as an add-on :)

Hey, Kendra. A hybrid headless API adds a layer of customization and control on top of a traditional API. This allows for the separation of content management and delivery, while still providing a familiar interface for developers to work with.

Publii is a flat file CMS, which means it stores website content in files instead of a database. It is designed to be used for creating static websites, and it does not have a built-in API to serve content to other applications- short answer is no, Publii is not a headless CMS, as it does not separate content management from presentation. With a headless CMS, the content management system only provides an API for accessing the content, while the presentation layer is left to the front-end application. This allows for more flexibility and control over the presentation layer, but it requires more development work to build and maintain the front-end. If you prefer to have more control over your content and do not want to use a cloud-based CMS, a flat file CMS like Publii may be a good choice. However, keep in mind that a flat file CMS may not be as flexible or scalable as a traditional CMS or a headless CMS.

You can now start with our blog starters but Wordpress is a very different type of system, hard to compare the two. Agility is more flexible and built for larger, more scalable solutions that need security and the flexibility to share content across multiple channels. If you don't know development or have a development team to setup your initial site then yes Agility CMS would be difficult for you. :)

Aaron, we just launched a VERY EASY Next.js BLOG starter with automated deployment to Vercel - please try it out and let me know your thoughts: you can start with reading this and watching the video help.agilitycms.com/hc/en-us/articles/360049603332 or just jump in and create your new blog for free here and follow the steps: manager.agilitycms.com/org/subscriptions/instance-setup?template=blog-with-nextjs

pretty much.... agilitycms.com/resources/posts/headless-wordpress-bad-idea

While Salesforce Marketing Cloud is not typically classified as a full-fledged Digital Experience Platform (DXP), it does offer several features that are commonly found in DXPs, such as personalized content and experience management, marketing automation, analytics and reporting, and integrations with other systems. However, a DXP typically provides a broader set of capabilities, including content management, customer data management, e-commerce, and digital asset management, among others. In contrast, Salesforce Marketing Cloud is primarily focused on marketing automation and campaign management.

LMAO, and then Con is that you need developer lmao. So lame

This video may help clear up any misconceptions :) ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-E23UGaxYLDo.html