The CMS package provides common objects and tools for building user-facing Web sites.

composer require charcoal/cms

For Charcoal projects, the service provider can be registered from your configuration file:

{
    "service_providers": {
        "charcoal/cms/service-provider/cms": {}
    }
}

• Section
• Tag
• Event
• FAQ
• News

A section, in Charcoal, is a reachable page on the website, as part of the full hierarchical site map. They can be displayed in menus or breadcrumbs and be reached with a unique URL (routable).

Types of sections:

• blocks
  • Blocks sections define their content as a structured map of blocks.
• content
  • Content sections define their content in a single, simple HTML property.
• empty
  • Empty sections are linked to a template but do not require any custom content.
• external
  • External sections are simply a redirect to an external (or internal) URL.

All section types, except external, make use of a Template object to be rendered. Typically, a charcoal view make sure of linking the template (by default, mustache

Sections are standard Charcoal Model, meaning they are describable with a Metadata object (which define a map of properties) and storable with a Source object.

Base section properties:

From model:

• Describable: The objects can be defined by Metadata.
• Storable: Objects have unique IDs and can be stored in storage / database.

From content:

• Content: A "managed" charcoal model (describable with metadata / storable).
• Authorable: Creation and modification user (admin) are kept in the storage.
• Revisionable: Copy of changes will be kept upon each object update in the storage.
• Timestampable: Creation and modification time are kept into the storage.

From charcoal/object:

• Hierarchicale: The objects can be stacked hierarchically.
• Publishable: Objects have publish status, date and expiry. Allows moderation.
• Routable: Objects are reachable through a URL.

From charcoal/cms:

• Metatag: The objects have meta-information for SEO purpose.
• Searchable: Extra keywords can be used to help search engine.
• Templateable: The objects can be rendered with a template / controller / config combo.

The \Charcoal\Cms\Section\* objects are final. To extend, use the \Charcoal\Cms\AbstractSection base object instead, to make sure no metadata conflicts arise.

Tag objects link any objects together by providing an extra taxonomy layer. Tags may also be used to enhance internal search engines.

Charcoal Event is a specialized content object to describe an event, which typically happens at a given date in a certain location.

Base events properties:

From model:

• Describable: The objects can be defined by Metadata.
• Storable: Objects have unique IDs and can be stored in storage / database.

From content:

• Content: A "managed" charcoal model (describable with metadata / storable).
• Authorable: Creation and modification user (admin) are kept in the storage.
• Revisionable: Copy of changes will be kept upon each object update in the storage.
• Timestampable: Creation and modification time are kept into the storage.

From charcoal/object:

• Categorizable: The objects can be put into a category.
• Publishable: Objects have publish status, date and expiry. Allows moderation.
• Routable: Objects are reachable through a URL.

From charcoal/cms:

• Metatag: The objects have meta-information for SEO purpose.
• Searchable: Extra keywords can be used to help search engine.
• Templateable: The objects can be rendered with a template / controller / config combo.

The \Charcoal\Cms\Event object is final. To extend, use the \Charcoal\Cms\AbstractEvent base object instead, to make sure no metadata conflicts arise.

Event category objects are simple charcoal/object/category used to group / categorize events. The default type is Charcoal\Cms\EventCategory.

Events implement the Categorizable interface, from charcoal/object.

FAQ objects are a special content type that is split in a "question" / "answer" format.

FAQ category objects are simple charcoal/object/category used to group / categorize FAQ objects. The default type is Charcoal\Cms\FaqCategory.

FAQs implement the Categorizable interface, from charcoal/object.

News object are a special content type that with a specific news date.

Base news properties:

From model:

• Describable: The objects can be defined by Metadata.
• Storable: Objects have unique IDs and can be stored in storage / database.

From content:

• Content: A "managed" charcoal model (describable with metadata / storable).
• Authorable: Creation and modification user (admin) are kept in the storage.
• Revisionable: Copy of changes will be kept upon each object update in the storage.
• Timestampable: Creation and modification time are kept into the storage.

From charcoal/object:

• Categorizable: The objects can be put into a category.
• Publishable: Objects have publish status, date and expiry. Allows moderation.
• Routable: Objects are reachable through a URL.

From charcoal/cms:

• Metatag: The objects have meta-information for SEO purpose.
• Searchable: Extra keywords can be used to help search engine.
• Templateable: The objects can be rendered with a template / controller / config combo.

The \Charcoal\Cms\News object is final. To extend, use the \Charcoal\Cms\AbstractNews base object instead, to make sure no metadata conflicts arise.

News category objects are simple charcoal/object/category used to group / categorize events. The default type is Charcoal\Cms\NewsCategory.

News implement the Categorizable interface, from charcoal/object.

• Contributing
• Report issues and send pull requests in the main Charcoal repository