drupal / mutamad_content_base
The Basic page content type and what Mutamad's content types share: a page an editor drafts and another person approves, in Arabic and English, with a description for search engines, tags and SEO fields, laid out by a Canvas template, in the sitemap; Topics and Audiences, attachments and related con
Package info
git.drupalcode.org/project/mutamad_content_base.git
Type:drupal-recipe
pkg:composer/drupal/mutamad_content_base
Requires
- drupal/core: ~11.4.0
- drupal/field_group: ^4.0
- drupal/mutamad_canvas: ~1.0.0
- drupal/mutamad_editor: ~1.0.0
- drupal/mutamad_media: ~1.0.0
- drupal/mutamad_multilingual: ~1.0.0
- drupal/mutamad_roles: ~1.0.0
- drupal/mutamad_seo: ~1.0.0
- drupal/mutamad_workflow: ~1.0.0
- drupal/taxonomy_access_fix: ~4
- drupal/token_or: ^2.3
- drupal/yoast_seo: ^2.2
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
This package is not auto-updated.
Last update: 2026-11-16 06:01:53 UTC
README
Mutamad Content Base
The Basic page content type (page), and what Mutamad's content types
share: fields and the Topics and Audiences vocabularies. A
drupal-recipe, applied by
mutamad_starter.
Built and maintained by iSpectra — Imagine. Implement. Inspire. See iSpectra on drupal.org.
Why a page is content, not a Canvas Page
A page that must be approved goes through the Mutamad workflow: an editor
drafts and submits it, an approver who did not write it publishes it, with a
reason for every edit, notifications and its history. Canvas Pages cannot do
that — Canvas publishes onto the live page and has no workflow; its
maintainers chose Workspaces instead. So pages are nodes, laid out by a Canvas
content template, and Canvas Pages are kept for a few landing pages
(mutamad_canvas).
What it sets up
- Basic page, with its form in two tabs:
- Basic information, the page itself:
- Language first: a new page is in the language the editor is
working in —
/en/node/add/pagean English page,/ar/node/add/pagean Arabic one — and stays changeable, between the site's languages only (not Not specified or Not applicable); - Title;
- Body, required, in the Rich editor (
field_content); - a Featured image from the media library, shown at the top of the page and when it is shared;
- Language first: a new page is in the language the editor is
working in —
- SEO, marked as having a required field:
- an SEO title and SEO image that replace the defaults;
- the SEO description, required: the page's one short summary, shown in search results, link previews and page lists;
- the real-time SEO analysis.
- Basic information, the page itself:
- The Mutamad workflow.
- Arabic and English translation, of pages and of the media they show:
- a page's featured image is the same media item in both languages;
- every media type translates, from the media item's Translate tab: whoever may edit a media item may translate it;
- an image — an SVG image, a video's cover image — keeps one file for both languages, and its alternative text and title are each language's own: an Arabic page's image is described in Arabic, an English page's in English. Replacing the file in one language replaces it in both;
- a document, an audio file or a video can have its own file per language;
- a caption is written where the media is placed, in the body, and is translated with it;
- until a media item is translated, both languages show its original alternative text.
- The sitemap, and an address from the page's title and menu position.
- A Canvas content template for the full page: the featured image, then the content. The site administrator changes the design in Canvas; editors write in the page's form and never change its layout.
- What the other content types share —
News,
Events,
Resources and
People and the others — so each adds only
its own:
- field storages: body, featured image, the SEO fields, Topics, Audiences, Attachments, Related content and a publication date;
- the Topics vocabulary — what content is about: visitors filter lists
by topic, and each topic has a public page at
/topics/<name>listing its content — and the Audiences vocabulary — who content is for. Both are translatable. Approvers manage their terms; editors pick them.
Who does what
| Role | Pages |
|---|---|
| Content Editor | Creates and edits pages; submits them for review; picks topics and audiences |
| Content Reviewer | The same, publishes them — never their own — and deletes them; manages the Topics and Audiences terms |
| App Admin (IT) | The template (in Canvas); writes no content |
Requirements
Mutamad Roles, Multilingual, Media, Workflow, SEO, Canvas and Editor; the
recipe applies each first. Field Group, Token OR, Taxonomy Access Fix and Real-time SEO for Drupal (yoast_seo) come with
it through Composer.
Apply it to an existing site
On a site not started from the Mutamad project
template, add it with Composer
first. Composer accepts an alpha only if the site's own composer.json allows
it, so the command allows Canvas Translate, which this project needs and which
has no stable release:
composer require drupal/mutamad_content_base \
'drupal/canvas_translate:^1.0@alpha'
Then:
drush recipe ../recipes/mutamad_content_base
Licence
GPL-2.0-or-later.
Maintainers
Built and maintained by iSpectra (on drupal.org).
