Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 37 ยท Getting Started

A Tour of the Drupal Admin Interface

Walk through the Drupal administration area: the toolbar, Content, Structure, Appearance, Extend, Configuration, People and Reports, and how to find things fast.

Once Drupal is installed you log in and land on a site with an administration toolbar along the top. Nearly everything you configure lives behind it. Learning where things are saves hours, because Drupal's admin is organized by job, not by feature name.

This lesson describes the standard Claro administration theme and the default toolbar. Labels can differ slightly between versions, but the structure has been stable for years. You will use these pages in nearly every lesson that follows.

The toolbar's main menu items

The top level has a handful of entries:

  • Content: lists all content, lets you add and edit it, and manage comments and media.
  • Structure: the site builder's area: content types, taxonomy, menus, blocks, Views, display settings.
  • Appearance: install and switch themes, choose the admin theme.
  • People: users, roles and permissions.
  • Extend: install and uninstall modules (the "module list").
  • Configuration: site-wide settings grouped by topic (system, content authoring, media, regional, development, web services).
  • Reports: logs, available updates, status report, field list, top search phrases.
  • Help: documentation links and module help.

A good habit is to ask: "Is this about content, about structure, about behavior or about people?" Then open the matching menu.

flowchart LR
    A["Admin toolbar"] --> B["Content: what editors write"]
    A --> C["Structure: how content is modeled and shown"]
    A --> D["Appearance: themes"]
    A --> E["People: users, roles, permissions"]
    A --> F["Extend: modules"]
    A --> G["Configuration: site settings"]
    A --> H["Reports: logs and status"]

Each toolbar entry answers one kind of question.

Content: editors live here

The Content page (/admin/content) shows a table of every node with title, type, author, status and last updated time. You can filter by type, published status and language, and run bulk actions such as publish, unpublish or delete. Choosing Add content lists the content types you have created, such as Basic page and Article in the standard installation.

Every node form has the same pattern: fields on the left, a sidebar with menu settings, URL alias, authoring information and publishing options on the right. Saving can create a new revision, so previous versions remain.

Structure: where site building happens

Structure (/admin/structure) is the busiest page for builders:

  • Content types (/admin/structure/types): define what kinds of content exist and their fields.
  • Taxonomy: vocabularies for categories and tags.
  • Menus: navigation trees.
  • Block layout: which blocks appear in which region of the theme.
  • Views: reusable listings of content.
  • Display modes and form modes: how entities are shown and edited.

If you ever think, "I need a new kind of thing", you start here.

Appearance, Extend and Configuration

Appearance lists installed themes. One is the default front-end theme; another, usually Claro, is the administration theme. Installing a theme from drupal.org starts with Composer (shown later), then enabling it here.

Extend shows every module with a checkbox. Core ships many modules that are off by default, for example Media Library, Layout Builder, JSON:API and Content Moderation. Turning one on here is how you opt into features. Uninstalling removes its configuration, so read the warnings.

Configuration groups settings under headings such as System (site name, cron, performance), People (account settings), Regional and language, Development (performance, logging) and Web services.

People and Reports

People (/admin/people) lists accounts, lets you add users, assign roles and block accounts. Sub-pages manage roles and the permissions matrix.

Reports includes two pages you will visit constantly:

  • Status report (/admin/reports/status): a health check showing PHP version, database, file permissions, cron status and pending updates.
  • Recent log messages (/admin/reports/dblog): errors and notices, when the Database Logging module is enabled.

Finding things quickly

Because Drupal's URL paths are consistent, you can memorize a handful:

Task Path
Content list /admin/content
Content types /admin/structure/types
Views /admin/structure/views
Modules /admin/modules
Permissions /admin/people/permissions
Status report /admin/reports/status
Clear caches /admin/config/development/performance

Typing a path directly is often faster than clicking. The admin toolbar also has a shortcut icon and, with the contributed Admin Toolbar module, drop-down menus for every level.

Here is a stand-in that models the toolbar as data and finds a page by keyword. It is a teaching sketch, not Drupal's actual menu system, but real Drupal does store links as a tree like this.

JS Stand-in: a searchable admin menu tree

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Reading the status report

After every install or update, visit the status report. It marks items as OK, Warning or Error. Typical warnings point to missing cron runs, an out-of-date database schema (run updates), or file permission problems. A new site should show no errors before you build on it.

Roles of the admin UI versus code

Many Drupal tasks are configuration, not programming. Creating a content type, a View or a menu requires no PHP. Drupal stores these as configuration, which you can export to YAML files and deploy, as you will see in Configuration Management Basics. The admin UI is therefore a real development tool, not just a convenience.

A second stand-in shows how a status report could be summarized. Again, this imitates the idea: Drupal's real report is generated by hooks from modules.

JS Stand-in: a status report summary

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where would you go to create a new content type?

    Content types are site structure, so they live under Structure at /admin/structure/types.
  2. 2. Which page gives a health check of PHP, database and cron?

    The status report at /admin/reports/status lists environment checks with severity levels.
  3. 3. What does the Extend page do?

    Extend shows the module list where you enable or uninstall modules.
  4. 4. Why is the admin UI considered a real development tool?

    Content types, Views and menus are configuration made through the UI and exported for deployment.

Summary

  • The toolbar is organized by job: Content, Structure, Appearance, People, Extend, Configuration, Reports.
  • Structure is the site builder's home; Extend enables modules; Reports holds the status report and logs.
  • Admin paths are consistent and worth memorizing.
  • Much of what you do in the UI is exportable configuration.

Next: Drupal Community and the Release Cycle