# Current Thoughts

Based on experiments done so far, here's our current view. 

* Webflow's existing May-2025 set of elements are outdated 
  * Difficult to enhance 
  * In some cases, use script where CSS can now be used 
  * Are rigid in their thinking 
    * e.g. Section / Container 
    * e.g. Custom Radio buttons and Checkboxes 
  * Require workarounds for common needs 
    * Form submit button with an icon   

To some extent these can be reconstructed as components, as follows;

* Determine the HTML, pre-webflow\.js 
* Recreate as custom elements 
* Convert to a component 
  * The outermost element must be the outermost custom element 
    * This is cleaner but buggy, as the outermost element is "locked" in the component element arrangement.  
* Create properties to mimic
* Add a few extension properties 
* Create additional elements for special uses
  * Default v. Custom 

However, in many cases the component structure and cooresponding webflow\.js and CSS are outdated or would benefit from a rethink.  

This leads to; 

* Current 
*

|   | Now | Temp CC | CC2 |
| - | --- | ------- | --- |
|   |     |         |     |
|   |     |         |     |
|   |     |         |     |


---

# 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://sygnal.gitbook.io/sygnal-webflow-components/current-thoughts.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.