Our Mission

Read more about Contenta’s mission in this blog post.

The mission of Contenta CMS

Quick install

The quick installation is intended for local development only. For this to work you will need to have composer installed in your local machine. See get composer for more details. Also, make sure that the sqlite-extension is installed (sudo apt-get install php-sqlite3 in debian/ubuntu).

php -r "readfile('https://raw.githubusercontent.com/contentacms/contenta_jsonapi/8.x-1.x/installer.sh');" > contentacms.sh
chmod a+x contentacms.sh
./contentacms.sh

Goals

One of the conclusions of DrupalCon Baltimore was that Drupal 8 has impressive tools to build a decoupled application. However, assembling all the tools together and setting them up correctly can be a little bit daunting. On top of that, once you have everything set up you need to figure out the ins and outs of your front-end project.

With this in mind, Contenta CMS is born to make your content happy. Contenta CMS is the response of the community to build an API-First Drupal distribution. The goals of Contenta are simple: provide a standard platform that is API ready along with demo content and example front-end applications. In summary, Contenta intends to ease the pain of using, or simply trying, decoupled Drupal.

Installation

The Bigger Drupal Community

We know you have questions about the different API-First distributions. We had them as well recently. These are some clarifications that may help you.

Demos

An integral part of Contenta is to provide an out of the box content model and demo content ready for you to start working with it. The demo chosen by the community is a recipe magazine.

With this in mind, every demo consumer will implement this recipe magazine site with the goal in mind to compare the different implementations.

Example Consumers

Choosing your own front-end technology is one of common reasons to choose a decoupled approach. In a decoupled architecture you can also have multiple front-ends at the same time. Contenta gives you examples on how to build a consumer application in different technologies.

We will implement the same wireframes as the Out of the Box Initiative, so all the demo applications can be compared. Even though all applications will have the same structure, each one will choose their look and feel. Angular may use material design, elm may use bootstrap, etc.

Front-end Status Example Code
Angular Running demo Website Repo
Elm Running demo Website Repo
Ember Need help Not yet Repo
Ionic   Running demo Not yet Repo
React In progress Not yet Repo
Vue.js + Nuxt.js In progress Website Repo
Chatbot Running demo Blog post Repo

If you want to contribute to any of the demo apps above or add a new one, join the Slack channel and become part of the project!

Development

Join the discussion in the #contenta Slack channel.

For documentation on the development on contenta_jsonapi itself, see docs/development.