> For the complete documentation index, see [llms.txt](https://attr.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://attr.sygnal.com/sa5-forms/about/sa5-forms-roadmap.md).

# SA5 Forms Roadmap

## Elements

| Element       | Type                          | Status | API                                           |
| ------------- | ----------------------------- | ------ | --------------------------------------------- |
| Input         | Extend native Webflow element |        |                                               |
| Checkbox      | Extend native Webflow element |        |                                               |
| Radio Button  | New element                   |        |                                               |
| Button        | Extend native Webflow element |        |                                               |
| Option        | Extend native Webflow element |        |                                               |
| Radio Button  | Extend native Webflow element |        |                                               |
| Range Input   | New element                   |        | Modes, e.g. 0-n, n-m, star rating, increments |
| Date Input    | New element                   |        |                                               |
| Numeric Input | New element                   |        |                                               |
| Phone Input   | New element                   |        | International options                         |

## Advanced Forms Validation

Multi-Step Forms

## JavaScript API 

Key objectives...

* We ideally want similar elements to share the same API
  * So that they can be swapped easily 
  * Especially Deck-based elements
* Base API
  * Enable / Disable
  * ScrollTo
  * Initialize
  * Clone ? 
* Easy integration and extension into TypeScript projects, especially [Sygnal Site Engine ( SSE )](https://engine.sygnal.com).

### Methods 

| Feature                       | Now                                                   | Planned | Considering                  |
| ----------------------------- | ----------------------------------------------------- | ------- | ---------------------------- |
| Programmatic Navigation       | Navigate to slide number, first, last, next, and prev |         | <p>nextLoop <br>prevLoop</p> |
| Add / remove / reorder slides |                                                       |         | Considering                  |

### Events

| Feature               | Now                        | Planned                                                                             | Considering |
| --------------------- | -------------------------- | ----------------------------------------------------------------------------------- | ----------- |
| Item changed event    | Occurs on any slide change | Will reconsider how this should work in multi-item mode                             |             |
| Item can change event |                            | Can open, can close, etc.  Give dev the ability to reject an open or close request. |             |


---

# 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://attr.sygnal.com/sa5-forms/about/sa5-forms-roadmap.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.