This section will explain the various terms and concepts that you will encounter using Burdy.
Burdy uses Posts entities (IPost interface) to store all your content. You can use it to store almost any content. Out of the box burdy offers multiple Post Types:
post- used mostly for repeatable content that is changing often such as Blogs
folder- hierarchical posts that are used by Burdy Sites and allow author to structure and organize posts in a familiar way.
post_version- when ever we have an update on any of the pre defined posts, a new version will be created and the content will be stored in
Assets are primarily used to store and organize content such as Images, Documents, Folders and more. Assets are storing metadata of the file in the Database while main content is being stored in either FileSystem or AWS S3 depending of the setup.
Burdy also supports Asset of mimeType application/vnd.burdy.folder that represents folder in the system giving authors OneDrive experience while managing assets.
Content Types is a way to manage schemas that represent definition of our Editor. Content Types are allowing Authors or Developers to define what fields can author edit in the post or page.
.Out of the box Burdy offers 16 field types. 12 Core and 4 Layout fields. Our Hook system allows developers to add any custom field with ease. To learn more about how to extend content types please take a look at adding new field.
Tags are a way of allowing authors to group posts or assets in a meaningful way such as Category and more.
The first level of the Tags is called namespace and each subsequent child is called Tag. The tag can also have children Tags allowing full hierarchical representation of Taxonomies.
The user represents an Administrator or Author or anyone who can access the Burdy Admin panel. These users should be different from Customers (coming soon via plugins).
To create granular permissions for example Author can only access Posts, Pages, Tags, and Assets without access to User Management or Content Types we are using Groups and assigning permissions. There is no limit to how many groups a super admin can create.