# Feature Roadmap

<table><thead><tr><th width="196">Feature</th><th width="246">Notes</th><th>Priority</th></tr></thead><tbody><tr><td>Component Architecture</td><td>Supports component definition and smart code-attached componentry</td><td>High</td></tr><tr><td>File Copy</td><td>Copy non-code assets over</td><td>High</td></tr><tr><td>SA5 Integration</td><td>Integrate SA5 features like debugging </td><td>Medium</td></tr><tr><td>Augmented Build</td><td>Special build processes for assets like HTML </td><td>Low </td></tr></tbody></table>

## Component Architecture&#x20;

SSE's page routing model allows us to cleanly separate page-specific code in a very manageable way. But in some cases your code needs to be tied to a "component";

* A specially configured SwiperJS setup
* A custom component you've built such as an accordion&#x20;
* Specialized form validation&#x20;
* A fancy multi-step form&#x20;

Often, these "components" need to be reused on multiple pages, and your design team might

### Goals

* Efficient code execution, only run code when it's needed
* Code isolation, e.g. the code & CSS for a multi-step form should be distinct from the rest of your source ode&#x20;
* Reusability. Your development would should be easy to repurpose on other projects you build.&#x20;
* Webflow Component support. Take full advantage of the Webflow Team's work on components and  leverage it in every way possible to maximize the finished "smart" component.&#x20;
* Create a design paradigm that supports the possibility of multiple "component" instances per page.&#x20;

### Implementation

Our early experiments involve the use of a new custom attribute;

`sse-component` = ( component name ).

You apply this to the outer DIV of any "component" on your page, and SSE's router automatically knows to instantiate that named component, and pass it the element.  From there, it's up to the component code to decide what it wants to do, focusing within that element.&#x20;

Matching the component name to the component is currently&#x20;

## SA5 Integration

Sygnal Attributes 5 ( SA5 ) is Sygnal's open source library of Webflow&#x20;


---

# 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://engine.sygnal.com/feature-roadmap.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.