# Widget configuration documentation

**URL:** <https://community.openhab.org/t/widget-configuration-documentation/139819>\
**Category:** UIs\
**Tags:** oh-data-series\
**Created:** [October 9, 2022, 11:37am UTC](https://community.openhab.org/t/widget-configuration-documentation/139819 "2022-10-09T11:37:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JustinG](https://community.openhab.org/user_avatar/community.openhab.org/justing/32/55948_2.png) [@JustinG](https://community.openhab.org/u/JustinG)\
**Post date:** [October 9, 2022, 3:57pm UTC](https://community.openhab.org/t/widget-configuration-documentation/139819/2 "2022-10-09T15:57:31Z")

</div>

See here for some advice on basic widgets:

> [@YAML Widget formatting](https://community.openhab.org/t/yaml-widget-formatting/132077/4):
>
> Honestly, in my experience you could do everything with rows because you can override the default flex settings (for that matter you could do nearly everything with just f7-blocks too). But I think that using the alternating rows and cols if you’re actually building a grid of component is just slightly cleaner and easier code to read. I do all my widget development in the MainUI editor. Nothing else that I’m aware of at the moment is going to give you the autocomplete ([ctrl] + [space]) fea…

However, the gauges you are referring to are charts and the chart system utilizes apache eCharts so the documentation for the complete list of those configurations is found on the eCharts pages.

> **[Documentation - Apache ECharts](https://echarts.apache.org/en/option.html#title)**
>
> Apache ECharts, a powerful, interactive charting and visualization library for browser

---

_[View the full topic](https://community.openhab.org/t/widget-configuration-documentation/139819)._
