What I love about the Drupal 7 CMS from a site administration perspective

Illustration: Drupalcity - ref.

[Post status: unfinished.public.draft]

I hope this list can aid administrators/site owners during early project planning stages when one needs to decide which CMS to choose.

As an administrator of quite a few Drupal-powered web sites ever since Drupal's beginning, I have extensive experience in what makes life a lot easier for CMS administration tasks.

Version 7 of the Drupal CMS (CMF) has tools (modules) that let me handle the following quite conveniently:

  • Mixed-mode security: can work on a site from more than one url, for example from BOTH httpS:// AND , so that one can make use of existing SSL certificates to gain secure access to a site for administrators without having to install separate SSL certificates for each domain/site if that web site does not offer user logins for others.
  • Easy to change the URL of the login path and the administration pages, to help reduce the attack surface for web robots/hackers.
  • Super-convenient and time saving User account switching without needing each user's passwords, for admins to test how things looks like for different users/roles, and also for covenient multi-account usage for selected roles/users.
  • Limiting login sessions to 1 (optional number) per user (and/or role) and automatical logout based on inactivity, so that if someone forgets to log out, their forgotten session/cookie is invalidated after a set amount of time, or automatically directly invalidating the previous session when logging back in from a different location/browser.
  • Onsite manual + scheduled backup of website database and/or user files/system files to online folder and/or local download folder. (Also possible to delegate to other user roles than the default admin role.
  • Roles can be renamed, moved, etc. User names can be (optionally) allowed to be renamed by users themselves or selected roles.
  • Captchas for comments/forms/etc. can be made invisible and automated elegantly.
  • Automatic contextual visibility for sidebar elements, blocks, etc. based on parametres such as roles, (partial)paths, content types, sections, etc.
  • Theme variants and automatic theme switching based on contexts/parametres such as paths/sections, users, etc.
  • Roles-based user themes selection.
  • Gravatar integration or pre-selected user avatars (from site-provided selection), OR even super-cool integration with for automatic generation of graphic avatar from the characters in the user name..! :-)
  • Automatic variants of just the menu background color to easily distinguish between the test/development version and production version of the same site.
  • Roles/permissions setup to ease delegating tasks to "semi-admins" that only should have permissions to do selected admin tasks (dont give away the keys to the whole kingdom).
  • Delegation of creating (and subsequent maintenance of) user accounts and automatic administration permissions to ONLY the user accounts a particular admin has created him/herself.
  • Delegation of theme customization without having to give administrator permissions to the Theme developer / customizer.
  • Easily overriding CSS (and creating new classes) directly from within the GUI interface without having to edit/change theme files. These customizations goes into the database, and are therefore retained across theme updates, so less need to keep track of or administer changes to themes, saving unnecessary extra work during each update.
  • Various alternatives regarding Two-Factor Authentication, including email-login-links(only), TOTP/Google Authenticator, Yubikey OTP, and more.
  • Version-controlled Terms-of-Service with history and per-user/role automatic acceptance prompts for new ToS changes to retain the same access to a site.
  • (optional) Drupal administration command line interface (through SSH) saves incredible amount of admin time in some areas.
  • Exportable configuration as automatically generated new modules ("functions") to save time implementing similar (portions of) setup on multiple sites.
  • Multilingual features with translation server, entity/revisions support (including categories/taxonomy), and updates moderation.
  • Any accounts, including the main Admin account(s) can be renamed, given new roles/permissions, etc.
  • Contextual automation: chained events (if X happens for role Y, automatically do Z).
  • Direct handling of "Robots.txt" rules inside the admin GUI instead of needing to edit the Robots.txt file through FTP or external control panel.
  • (2bcontinued)

[Post status: unfinished.public.draft]

Related content: Tags: Related topics: