Comfortable Documentation

Last updated 3 months ago

Welcome to Comfortable 👋

Comfortable is a API-first headless CMS that makes it easy to manage content of your websites and applications without the overhead of a traditional CMS.

Dynamic content is everywhere nowadays. Traditional CMS reach their limits when it comes to delivering content to many different platforms and devices. A flexible content API can help you to deliver content where you need it and supports you to use the appropriate tools for a project.

💬 Support

If you have any questions or find something is missing from the documentation? Feel free to contact our support the Intercom chat widget or at support@cmft.io. We're happy to help!

💡Feature Requests

We're always curious and excited about ideas to push things forward. You can view a list of existing feature requests on GitHub, or approach us directly with the Intercom chat widget or at support@cmft.io.

Cheers, The Comfortable Team

Getting started

This introduction will get you a quick overview of the basic things to know, when working with Comfortable.

Accounts

To get started you'll need to create an account. Each account can have repositories for themselves or can be invited to join and collaborate within foreign repositories at an appropriate access level.

Repositories

Spaces for projects are called repositories. A repository is the place where you keep all the content related to a single project.

Documents

Each document represents a content entity. That might be a page, a product, some content element, or anything else.

Document Types

Document types define reusable schemas for documents. You could for example create a document type called Page, Product or Article.

Collections

Collections are powerful filters for documents that can be used as endpoints and be managed through the web interface. Create lists of products, categories, display articles or elements of a section of your site, collect dates, or aggregate sets of data. Do almost anything you would do with client-side filtering, but keep the content accessible and comprehensible for your editors.

Content Tree

The Content Tree holds all of the collections and linked documents to provide developers and editors with structure and orientation.