> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pentaho-ctools/c-tools/community-dashboard-editor.md).

# Community Dashboard Editor

Dashboards made easy ..

{% hint style="info" %}
While the previous Community Dashboard Framework (CDF) covered creating dashboards through code, this chapter introduces a faster, more user-friendly approach using CDE (Community Dashboard Editor). CDE is a Pentaho server plugin that simplifies dashboard creation through its graphical interface, eliminating the need for extensive manual coding.

This chapter focuses on:

* Creating dashboards using a graphical user interface
* Building responsive layouts
* Adding and configuring components
* Incorporating custom code and resources (JavaScript/CSS)
* Managing data sources through the interface

Although CDE builds on the CDF (Community Dashboard Framework) foundation covered previously, you don't need to write CDF code directly. However, understanding CDF's core concepts - especially dashboard and component lifecycles - remains crucial for maximizing CDE's potential. This knowledge will help you create more sophisticated dashboards even when using the graphical interface exclusively.

Through CDE, you'll significantly reduce development time while maintaining full control over your dashboard's functionality. The visual approach makes dashboard creation more accessible without sacrificing the power and flexibility of the underlying framework.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/B36Vh3y5doh2RbQX2zOj/blobs/UQxJs5PLLrxOvVHe6BNZ/image.png" alt=""><figcaption><p>Dashboard Lifecycle</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.pentaho.com/pentaho-ctools/c-tools/community-dashboard-editor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
