# Key Features

YDS consists of various components, from elements to widgets to applications - the simplicity of drag-and-drop and the power to develop custom functionality:

* **Elements:** Foundational building blocks such as select boxes, date pickers, sliders, and more. Elements are tightly bound to model variables for seamless interactions whether controlled by the user or programmatically.
* **Widgets**: Pre-built widgets to drag-and-drop within the Designer. Widgets utilize theme colors and are customizable via options.
* **Applications**: Intelligent web apps built on Service Portal. More than a widget, applications are modern web apps that can offer unlimited functionality.

#### **YDS is proven Service Portal components:**

* Consistent look & feel across the framework
* Modular architecture for simplified implementation & maintenance
* Compatible with most modern browsers and devices
* QA-tested and production-ready

#### **YDS offers documentation & support beyond the industry standard**

* Dedicated documentation site with examples, screenshots, and code snippets
* Included test page with diagnostics, sample code, and documentation links
* Dedicated email support
* Prioritized YDS additions, updates, and fixes for active subscribers

#### **YDS is alive!**

* New elements, widgets, and applications added frequently
* Feedback from subscribers drives the development pipeline
* YDS gets better and better and better…

[See more at the YDS Docsite.](https://www.yansalabs.com/yds)


---

# Agent Instructions: 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:

```
GET https://docs.yansalabs.com/yds/overview/key-features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
