> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/10.0.x/developers/understanding-varbase/core-components/varbase-dashboards.md).

# Varbase Dashboards

A dashboard is what's missing for better Drupal administration experience.

<figure><img src="/files/1MsrpconyCs1TaTv5UeK" alt=""><figcaption><p>Enhanced Experience With the Sleek and Stylish Light Mode for Dashboards</p></figcaption></figure>

This dashboard is built on top of [Dashboards with Layout Builder](https://www.drupal.org/project/dashboards) module, utilize Drupal core's Layout Builder for dynamic dashboards management, and several enhanced blocks and widgets for an intuitive and flexible administration experience.

> The idea is made to provide the site admins with an appealing and concise dashboard to become the home of any Drupal site's administration task.

Provides default set of dashboards with configuration and enhancements for dynamic default, editorial, and admin dashboard management system.

## Varbase Dashboards Module

{% hint style="info" %}
Varbase workflow features are bundled through the **Varbase Dashboards** module.

&#x20;GitHub: <https://github.com/Vardot/varbase_dashboards>

&#x20;Drupal.org: <https://www.drupal.org/project/varbase_dashboards>
{% endhint %}

After building a project using the `varbase-project` template, you can see the code of the **Varbase Dashboards** module in:

```
project_directory
|-- docroot
    |-- modules
        |-- contrib
            |-- varbase_dashboards
```

Brings in the following core and contributed modules to your site:

| Module                                                                     | Purpose                                                                                       |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| <p><strong>Layout Builder</strong></p><p><em>(in Drupal core)</em></p>     | Allows users to add and arrange blocks and content fields directly on the content.            |
| <p><strong>Content Moderation</strong></p><p><em>(in Drupal core)</em></p> | Provides additional publication states that can be used by other modules to moderate content. |
| [**Dashboards**](https://www.drupal.org/project/dashboards)                | Dashboards based on layout builder.                                                           |
| [**Dashboards views**](https://www.drupal.org/project/dashboards)          | Setup some views for dashboard.                                                               |

<figure><img src="/files/NuZTQNFX9iQWdJjj2xRW" alt=""><figcaption><p>Switch Effortlessly Between Modes and Enjoy the Seamless Inclusion of Both Light and Dark Mode</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.varbase.vardot.com/10.0.x/developers/understanding-varbase/core-components/varbase-dashboards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.