Search by

drupal / mutamad_admin

Drupal-Infrastructure

The Mutamad administration experience: Drupal CMS's admin UI (Gin, Navigation, Dashboard) in Mutamad's branding.

Package info

git.drupalcode.org/project/mutamad_admin.git

Homepage

Issues

Type:drupal-recipe

pkg:composer/drupal/mutamad_admin

Statistics

Installs: 61

Dependents: 1

Suggesters: 0

1.0.x-dev 2026-11-12 17:40 UTC

This package is not auto-updated.

Last update: 2026-11-16 05:56:46 UTC


README

Mutamad Admin — الإدارة

Mutamad Admin

The administration experience for Mutamad — a drupal-recipe, applied by the mutamad_starter site template on every Mutamad install.

Built and maintained by iSpectra — Imagine. Implement. Inspire. See iSpectra on drupal.org.

It applies Drupal CMS Admin UI unchanged — Gin, core Navigation, the Dashboard, Coffee, Gin Login, Project Browser and the rest — then brands it for Mutamad and adds the admin tooling that applies to Mutamad.

What it changes on top of Drupal CMS

SettingValue
Admin sidebar logo (navigation.settings)The Mutamad emblem
Gin logo and favicon (gin.settings)The Mutamad emblem and favicon
Gin's colour (gin.settings)Mutamad's green, #1B8354, as the accent (buttons, links, the selected tab, the header's tint) and the focus ring
Login page (gin_login.settings)The Mutamad emblem, and Gin Login's own wallpaper instead of the Drupal CMS artwork
Navigation footerDrupal CMS's second "Help" link, which points at the Drupal CMS user guide, becomes a "Mutamad" link to the project page

Who can do what

The three job roles come from mutamad_roles, which this recipe applies first (NCA ECC 1-3-1):

RoleIn the admin area
Content editorMedia library, help, Trash (restore content, media and terms), audit trail, the Tags term list
Content approverAs editor, plus the main and footer menus
Site administratorBlocks, menus, maintenance mode, Trash including purge; user accounts and their email addresses; the audit trail

Every signed-in account also has the administration pages, Navigation and Coffee, from Drupal CMS Admin UI. Nobody can masquerade as another user.

Admin tooling added

ModuleWhat it does
Admin Audit Trail (+ auth, file, media, menu, node, taxonomy, user, user roles)Logs who changed what, at Reports → Admin audit trail
User ProtectOther users cannot change an administrator's email, password, roles, status or delete them — shipped as the Protect administrators rule. Mutamad adds two rules: the email, password and roles of a content approver or site administrator can be changed only by the administrator. So the site administrator, who manages accounts, cannot take over one of those accounts — or approve their own work through it (NCA ECC 1-3-1, 2-2-3). Blocking them stays possible
TrashDeleted content, media and terms can be restored. Files are not trashable: a file removed under a retention rule leaves the disk (NCA DCC 6-2). Only site administrators purge
Prevent Homepage DeletionThe front-page node cannot be deleted
Autosave FormEditors' work is saved while they type
Revision Log DefaultA revision saved without a log message gets one describing what changed, e.g. "Updated the Title field". It does not make the message required
Maxlength, Length IndicatorCharacter limits and counters on text fields
Gin Type Tray, Gin EverywhereA card-style "Add content" page; Gin on edit forms opened from the front end
Taxonomy Access FixPer-vocabulary permissions on core's taxonomy pages
Menu Admin per MenuPermissions per menu
Chaos Tools (ctools, ctools_block, ctools_views)Views blocks configurable where they are placed; entity fields as blocks

It also sets account registration to administrators only, and grants content_editor the audit trail, trash and media overview.

Left out: masquerade (logging in as someone else breaks the audit trail), eca_vbo, ui_icons and canvas_icon_picker (a Canvas theme's icons only), smart_date, config_perms, roleassign, and Taxonomy Manager — vocabularies are managed on core's own taxonomy pages.

Requirements

The logo and favicon are files in the Mutamad profile, referenced at profiles/contrib/mutamad/ — where mutamad_project installs it. A site that places the profile elsewhere needs to change those paths.

Apply it to an existing site

drush recipe ../recipes/mutamad_admin

On a Mutamad site, which already has it, do not apply it again: Drupal CMS's admin UI, which it includes, installs Drupical and the drupal.org announcements feed again, two modules that call drupal.org from the site and that the Mutamad profile removes at installation (NCA ECC 6-1). If it has been applied, drush pm:uninstall drupical announcements_feed removes them.

Maintainers

iSpectra

Built and maintained by iSpectra (on drupal.org).