Feature Roadmap

Here's what we're working on in SSE

Feature	Notes	Priority
Component Architecture	Supports component definition and smart code-attached componentry	High
File Copy	Copy non-code assets over	High
SA5 Integration	Integrate SA5 features like debugging	Medium
Augmented Build	Special build processes for assets like HTML	Low

Component Architecture

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

• Specialized form validation

• A fancy multi-step form

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

• Reusability. Your development would should be easy to repurpose on other projects you build.

• 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.

• Create a design paradigm that supports the possibility of multiple "component" instances per page.

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.

Matching the component name to the component is currently

SA5 Integration

Sygnal Attributes 5 ( SA5 ) is Sygnal's open source library of Webflow