Core dna help center

Unlike a traditional CMS/eCommerce, which combines content management and front-end delivery, a headless platform has a flexible front-end system to determine how the content is created and presented to the end user. It’s front-end agnostic, meaning that your content is created raw and can be published anywhere, through any framework, thanks to built-in APIs.

Coredna is not only a headless platform but also a hybrid headless Platform. We recognized that Marketers still need the flexibility of an easy to use administration, so we created a fully functioning DXP administration panel that allows the marketer to have a dashboard and the ability to manage multiple websites. With the Headless features of the Core dna DXP you can also create a customized publishing platform, this can be useful if you want to simplify administration functions or create a custom user experience.

Learn more about headless content management.

Gartner defines a digital experience platform (DXP) as, “an integrated set of technologies, based on a common platform, that provides a broad range of audiences with consistent, secure and personalized access to information and applications across many digital touchpoints. Organizations use DXPs to build, deploy and continually improve websites, portals, mobile and other digital experiences.”

An enterprise DXP gives a brand the tools it needs to manage the presentation layer of their digital presence. All great DXPs combine integration and aggregation, content management, personalization, collaboration, workflow management, analytics, multichannel support as well as search and navigation.

The Core dna has an advanced set of solutions 

A decoupled platform — a term that best describes Core dna — is a headless platform, and then some.

With a decoupled platform, your content and other objects like products, orders, blogs are managed separately and can be front-end agnostic, just like a headless platform. Yet, it has front-end delivery tools in the box, like templates, an admin for your staff and other features that can make adopting the platform easier than if it were just a headless platform. These additional tools are designed for people who don't have technical expertise and can simplify your development process. 

The difference is that the back-end and front-end are not “coupled” to each other through a database like with a traditional CMS. Instead, the front-end and back-end communicate to each other through calls to an API.

Learn more about headless content management.

A headless platform gives you a number of benefits. These include:

1. Ability to create your own custom content types that can then be used to build further complex content types that are independent of the original database design.
2. Freedom to develop interfaces based on your own standards without the constraints of your current CMS.
3. The ability for you to distribute your content to multiple channels. For example desktop, mobile, phone, interactive screen, digital banners.
4. A central place for all your content, rather than have it distributed across many different systems.
5. Ability to access content using application programming interfaces (API).
6. Ability to create custom publishing environments that are tailored to your admin requirements.
7. Remove the dependence of your systems on specific systems. You can use API interfaces to access what you need from systems and replace them easily if your needs change.
8. Ability to use microservices for speed and flexibility. 
9. Make changes quickly without the need to engineer your CMS; making it faster to get changes done.
10. Developer friendly, no big learning curves for developers to understand new CMS/eCommerce platforms. Easy-to-learn API interface that gives them the ability to create anything using multiple sources of information.
11. Ability to improve performance: by controlling exactly what you want to deliver to your visitor, without the overheads of a traditional CMS/eCommerce.
12. Improved security through access to distinct APIs that can be controlled by the admin.

Read this next: Headless CMS vs Decoupled CMS: The Ultimate Guide

Pros

• Flexible developer environment to create and manage content across multiple channels
• Ability to create and deploy tailored customer experiences quickly
• Ability to learn, change and iterate direction quickly
• Share content programmatically with other systems
• Create workflows and recurring processes that communicate with the platform and other systems
• Advanced security provided by simple interactions through APIs
• Improved performance, ability to create static content and have websites that are fast
• Scale, ability to handle peaks and large volumes of website content from a single source

Cons

• Have flexibility that may require developer involvement
• Manual application management
• Out-of-the-box functionality may be limited
• Flexibility in the presentation layer can be limited
• Setup maybe be more complex in terms of structuring data types, components and layouts
• Some systems are missing admin/authoring capabilities with features like preview, analytics and permissioning
• Site control can be split amongst a number of content systems
• Personalization may require more development
• Analytics capabilities can be limited

** Many of the Cons above have been solved within the Core dna platform as we continue to provide hybrid support for the traditional authoring environment.

Read this next: Hybrid CMS: A Headless CMS, But With a Front-End

There are a number of differences between headless and decoupled platforms; these include:

1. Flexible content models that allow you to describe your data in the headless platforms.
2. Advanced APIs that can use query languages for APIs like GraphQL.
3. Headless platforms are designed to deliver content quickly and efficiently without any overhead.
4. Decoupled platforms are generally connected to a display layer templating language for building user interfaces.
5. Headless platforms may not have any display of layer templating. Hybrid platforms like Core dna do still offer templating languages and admin interfaces for the convenience of admins.
6. A high degree of customization & flexibility for developers in the headless platform.

This depends on the traditional platform. With a headless CMS, the key difference is its ability to create different content types and then make that content available through an application programming interface (API). 

If a traditional CMS is able to process API requests it can be integrated with a headless platform. If it's not then programmers will need to process the API requests outside of the traditional CMS, through the use of javascript in the display of the website.

Core dna is a decoupled platform, meaning we have headless content management built-in, but we also give you the front-end tools you need to present your content to your end-user.

Core dna is framework agnostic, which means you can create any design using the front-end technology and frameworks that you know and love. Core dna never requires you to use specific templates or libraries. As decoupled platform, Core dna also have server side templating that can be used to deliver projects quickly and efficiently using only HTML, CSS and Javascript. The server side frameworks supported are Twig and Smarty.

There are a number of differences between Monolithic systems and a Headless system, these include:

1. Monolithic systems have lots of functionality built into them that not all customers need.
2. A headless platform gives you access to entities, examples of these are pages, menus, products, blogs, people, etc. Entities are the base objects that you can then modify and enhance to your requirements.
3. Monolithic systems are more focused on delivering solutions to the end client rather than the developer. Core dna’s platform strikes a balance between the developer environment and the admin environment.
4. Headless platforms in many cases don’t come with admin tools for end clients. Core dna continues to provide admin friendly tools inside our headless platform.
5. Access to information from a monolithic system can be difficult.
6. Monolithic systems require you to establish the infrastructure and the security tools to make them work.
7. Monolithic systems can take time to learn and understand the way they work.
8. Headless platforms allow you to create your own publishing environments.

Read this next: Headless CMS vs Decoupled CMS: The Ultimate Guide

You sure can. Global brands trust Core dna to build and operate eCommerce websites in multiple regions and continents. Our eCommerce feature set includes everything from inventory management to detailed analytics. 

See Core dna’s eCommerce features.

Core dna was launched in 2015, but our team was operating as a digital agency since the year 2000, building, tweaking and using Core dna for our clients as we grew.

Our head office is located in Melbourne, Australia. Core dna also has offices in Boston, USA, and Berlin, Germany.

Yes. Microservice architecture helps us scale, which helps our clients scale. Plus, it means we can give each client the exact tools they need without burdening them with superfluous features.

Core dna is a SaaS (Software-as-a-Service) platform, meaning you’ll be charged a monthly subscription fee, with none of the headaches of hosting or maintaining the infrastructure.

Of course! We pride ourselves on being more than just a software vendor. We partner with brands and agencies by providing technical support, digital strategy consulting and more. Core dna originated from an agency and has the professionals to provide insights into the platform, help with the strategy, implementation of the platform and the experts to help with solving onboarding and ongoing questions.

Yes, you can use APIs to deliver content to any channel or device, and to connect with any third-party platform.

There’s no need to wait, you can schedule a demo today.