Setup
Config
Content Type

Custom Content Type Creation

Overview

Super admins have the flexibility to create custom content types as per their requirements. For instance, if the super admin wants to create a content type for blog posts, they can define a new content type and name it “Posts” or “Blog.” This feature allows for tailored content management suited to various application needs.

Creating a Custom Content Type

When creating a new content type, the following fields and configurations are available:

  1. Brands: Select one or multiple brands to associate with the content type.
  2. Title: The name of the content type (e.g., Posts, Blog).
  3. URL: The unique identifier used in the URL for this content type.
  4. Type of Content: Choose whether the content type will be a Single entry or a Collection of entries.
  5. Editor Type: Select the editing interface: • Page Builder: For a more visual, drag-and-drop interface. • Normal Form: For a standard form-based interface.
  6. Position of Content Type in Admin Navigation: Specify where this content type will appear in the admin panel’s navigation menu.
  7. Admin Navigation Icon: Choose an icon that will represent this content type in the admin navigation.
  8. Admin Navigation Section: Determine which section of the admin panel this navigation item should be added to.
  9. Attachable Type: Define whether this content type can attach other content types. For example, you can attach a Gallery content type to the Blog content type.

Features Checklist

When defining the new content type, super admins can select from the following features:

  • Has Slug (URL): Enable a slug field in the admin panel for creating content. This allows for SEO-friendly URLs.
  • Active: Toggle the activation status of the content type to enable or disable it.
  • Navigation on Collection API: Choose whether to attach navigation menus to the collection API when called from the front-end.
  • Navigation on Detail API: Determine if navigation menus should be included in the detail (single content) API when called from the front-end.
  • Has Form: Enable the custom forms attachment field in the CMS. This form will be available when calling the content API.
  • Has API Endpoint: Specify whether a public API should be available for this content type, allowing for front-end access.
  • Has Meta: Enable meta tags (like title and description) for content creation using this content type.

Example Use Case

Creating a Blog Content Type:

  • Brands: Select from available brands
  • Title: Blog
  • URL: blog
  • Type of Content: Collection
  • Editor Type: Page Builder
  • Position in Admin Nav: 2
  • Admin Nav Icon: (Choose appropriate icon)
  • Admin Nav Section: Content Management
  • Attachable Type: Gallery
  • Features Checklist:
    • Has Slug: Enabled
    • Active: Yes
    • Navigation on Collection API: Enabled
    • Navigation on Detail API: Enabled
    • Has Form: Enabled
    • Has API Endpoint: Yes
    • Has Meta: Enabled

This structured approach allows super admins to create custom content types tailored to their specific needs, enhancing the CMS’s flexibility and usability.

BrandField Config