> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/features/release-notes/2022/01-28-jan-update.md).

# 01-28 Jan Update

January 2022 Update (Teaxr v0.5.1839)

### :rocket: Major Features

* Editor
  * New properties for text element including background color, background opacity, border color, border thickness. Also added ability to upgrade any existing text element to enable all the new properties
  * A new grow animation option added to all 3d elements.

### :arrow\_double\_up: Minor Improvements

* Editor
  * Documentation for GMetri Plugin Ecosystem
  * Elements can be added inside groups directly from the add element UI
* Viewer
  * Viewer performance optimizations to reduce network calls overhead

### :bug: Bug Fixes

* Viewer
  * Actionbar element styling fix for devices with smaller resolutions
  * Capture text element matches text with regex validation correctly
  * Embed HTML element appears in popup mode when pip is selected to maintain consistency of the UI
* Portal
  * Fixed views and viewers count on deployment analytics page


---

# 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://docs.gmetri.com/features/release-notes/2022/01-28-jan-update.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.