Getting Started
Caasy is a headless Content Management System (CMS) that allows you to manage content easily without noise. Content is Caasy is built with so-called elements. These can be managed by developers and content creators without a technical background. This is a great opportunity for developers to build individual frontends such as websites, blogs or mobile apps, which then translate these elements to the actual UI.
This documentation is your guide to adopt Caasy in your next project. No worries, Caasy was built with a focus on simplicity. Before you can get started, head over to the Caasy App and sign up your personal Caasy account. Below, we will give you a quick tour, through the Caasy Dashboard.
Sites
Content in Caasy is organized in Sites
. A site pools together blog posts, pages, media items such as images, news and other data. To create your first site, navigate to Manage Sites
in the sidebar on the left and click the Add Site
button. You can create several sites if needed. You might want to create a separate page for each of your client. Finally, select your new site.
Navigation
Once you have selected a site, you will find additional menu items in the sidebar.
Blog Posts: Allows you to manage blog posts. If you invite other users to your site, they will be able to view, add, edit and delete blog posts. More on that later.
Pages: Pages are pretty similar to blog posts. However, pages don't have additional metadata such as preview images and preview text. They should be used if you want to build a website with one or multiple pages.
Media Library: If you like, Caasy will host all kind of files that you need for your site. Images are automatically resized in four different sizes for you.
User Management: By default, only you have access to your site's content. You can add other Caasy users to collaborate on your site by inviting them.
Activity: The activity stream gives you insights into what happened on your site. You can even add deploy information from platforms such as Netlify to your activity stream.
Integrations: Caasy offers granular webhooks that allow you to trigger actions such as build flows in other systems when certain events take place.
Site Settings: Allows you to update your site's settings or delete the site and all its data.
First blog post
To create your first blog post, navigate to Blog Posts
and click the button New Post
. This opens the Caasy Builder that allows you to create and edit content with pre-defined elements. The library of elements is continuously expanding. If you are missing any elements, please use the feedback box and describe the element you would like to see in Caasy. Click the round plus button to add your first element. This will open the library with all elements. Select one to add it to your blog post. When you have several elements, you can re-arrange, edit and delete them as you wish. Once you are done, make sure to save your new post. If you want to make your post publicly available, click the Publish content now
toggle.
Build your website
Caasy is headless, which means its API only gives you the raw data of your content. It's completely up to you how you use that data. You are free to choose the frameworks, tools and platforms you like or need. We have crafted a free blog template with NextJS and our Caasy Javascript SDK that outlines, how we are using Caasy.
User Management
You can also invite other users to your site. This will depending on their role, give them access to your entire site or parts of it. Below you can find an overview of the available roles.
Editor: An editor has access to the media library, blog posts and pages. Editors can only edit existing elements but cannot re-arrange or delete them. They also cannot add new elements.
Creator: They have the same permissions as editors but are also allowed to add new elements to blog posts and pages. They are also able to re-arrange and delete them.
Admin: Admins can also manage integrations and users. They are also able to delete a site and all its data.
Owner: This role cannot be assigned to users. Only the user who created a site gets the
owner
role assigned.