General Questions - Help

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

[Read more]

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

[Read more]

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.

[Read more]

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.

[Read more]

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.

[Read more]

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

[Read more]

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.

[Read more]

Thanks to Core dna’s decoupled nature, paired with our microservice architecture, our DXP is ready for anything. If your content is managed by Core dna, you’ll always be able to deliver it to any new device that emerges on the market.

[Read more]

Yes. Core dna can build intranets and social communities for professionals that enhance communication and collaboration.

See Core dna’s digital workplace features.

[Read more]

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.

[Read more]

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

[Read more]

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.

[Read more]

The easiest way to determine if a headless platform is best for you is to ask yourself these questions:

  1. What are your business requirements and does a headless platform solve these requirements?
  2. Do you have access to qualified individuals to help with the setup and ongoing management of the platform?
  3. Can you determine the content types that you will require (e.g. buttons, headers, lists, options, etc.)?
  4. Do you want to design your own components using the content types you can define? You can always add components later but planning up front will help with organizing your content for distribution.
  5. Determine if you want to enrich your content with templates and styling to create consistent output and not just data.
  6. Do you want to test the output from the headless platform using tools that allow you to make API calls?
  7. Do you want to configure the destination systems to accept the information?

In the case of Core dna, we provide an admin panel to help with the creation of the content and preview of the content. We also give you a number of tools for security and personalization. Finally, we have defined a number of entities that give you the starting point for your project to help with quick deployment.

Read this next: How to Choose The Best CMS Platform to Help Drive Your Business Growth

[Read more]

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.

[Read more]

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.

[Read more]