> 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-framework.md).

# Community Dashboard Framework

{% hint style="info" %}
Community dashboards can be built using either the Community Dashboards Framework (CDF) or the Community Dashboard Editor (CDE). While CDE offers a faster development path, it ultimately relies on CDF under the hood. Understanding CDF's core concepts is essential even when using CDE, as it enables better utilization of both tools.

So were going to cover some concepts in this workshop:

* Dashboard and component lifecycle
* Essential CDF API methods and functions
* Component configuration and query parameters
* Interactive filtering and component event handling
* Internationalization features:
  * Language localization
  * Regional number formatting
  * Date formatting based on user settings
    {% endhint %}

{% hint style="info" %}
By the end of this workshop, you will understand:

* The complete dashboard lifecycle
* Available CDF API methods and their usage
* How to create interactive, globally accessible dashboards
  {% endhint %}

x

x

x

x


---

# 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://academy.pentaho.com/pentaho-ctools/c-tools/community-dashboard-framework.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.