> For the complete documentation index, see [llms.txt](https://sygnal.gitbook.io/sygnal-webflow-components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sygnal.gitbook.io/sygnal-webflow-components/about-sygnals-dev-process.md).

# About Sygnal's Dev Process

I think of it this way;<br>

* Code components are exceptional for building reusable components that have standard, mostly-unstyled interfaces with a lot of code/interactivity.  So maps with pins, accordions, sliders, modals, a drag-drop file upload component, even an appstore QR code renderer.  None of those depend strongly on class-based styling, so variables are generally enough.
* Regular components are exceptional for building highly-styled components that have virtually no code.&#x20;
* Once the AI builder is out, and for large custom builds, DevLink helps fill the gap in between.  Project-styled code components, that aren't really reusable elsewhere.

The code components I'm focused on currently are in group 1, all about reusability across projects.  But since we won't have a marketplace for awhile, I'm just working out the deployment processes to make them community accessible.