Getting Started with the CMS
The AppAmbit CMS (Content Management System) allows you to define, manage, and update the content of your applications dynamically from the AppAmbit platform without needing to release new versions of your app.
This guide will walk you through the basics of using the CMS via the AppAmbit online dashboard.
Main Concepts
Understanding how AppAmbit structures your data is the key to building dynamic applications. Think of the CMS as your application's brain in the cloud, organizing information so your apps can fetch it blazingly fast.
Here is how data is structured top-to-bottom:
- Content Types (The Blueprints)
Just like a relational database relies on tables, AppAmbit uses Content Types to define complete categories of data. For instance, if you are building an e-commerce app, you would define a
productsContent Type. - Fields (The Attributes) These are the specific characteristics that make up your blueprint (similar to database columns). A product might need a Price (Number type), a Description (Rich Text), and an Availability Status (Boolean).
- Entries (The Entries)
These are your actual, living entries. When you create a specific "Retro Sneakers" entry using the
productsblueprint you made in step 1, that filled-out entry is saved and served as a row.
Summary
In AppAmbit CMS, your database tables are called Content Types and the rows inside them are called Entries. By using the online dashboard, you can define these structures and manage their entries on the fly, without having to change any code.
Next Steps
Explore the following guides to learn how to actively use the CMS, either from the dashboard or directly via the SDK in your application.
-
Creating a Content Type
Learn how to define your schemas, set up data types, and prepare the foundation for your entries.
-
Creating an Entry
Learn how to add, edit, delete, and publish, draft or archive entries from the dashboard.
-
CMS SDK Integration
Ready to pull data into your app? See how the client SDK handles queries, filtering, and caching.