See Below for current link…
Numerous bug fixes and polish 
I will try to update them every month or so…
added tons of edit options and fields to WindyTown Audio CMS - sorry they weren’t there before 7:40 PM Chicago Time - Re Download Newer Version Please
Last one
Little fixes…
Looks like I’m in for doing more than a month updates…
These are even more resilient - tested against 3.0.6
Nice work @MichaelDroste 
Coming from you @dan - very high praise - thank you!
@dan a little confused now on devpacks, hopefully you can can answer and clear this up, also asked the last part 3 times, is this still happening. And from this thread and below, is it ok to now distribute devpacks? I have at least 30, can I zip them up and post
extracts from Elements help
Element Dev Packs
Element Dev Packs are for internal use only. Do not distribute or sell them.
An Element Dev Pack (.devpack) is designed strictly for local development. These are uncompiled and unencrypted versions of your components that allow for live editing and testing during development.
However, this live monitoring comes at a cost. If too many Dev Packs accumulate over time, Elements (and macOS) can run out of file handles, leading to components failing to load or update. To avoid performance issues and ensure system stability, Dev Packs must never be shared or sold.
Element Packs
An Element Pack is a compiled and encrypted version of your component. It contains only the essential files, optimised for performance and security. These packs are what you’ll use when sharing or selling your work via the Marketplace or elsewhere. ???
Join the Partner Program
Build and share products on the RapidWeaver Elements Platform.
The partner program is curated and managed on a case by case basis. Not everyone can join. We carefully hand pick partners to ensure the highest standards of quality, reliability, and long term support for RapidWeaver Elements customers.
Elements Store
The Road ahead
In the meantime we want to build in support for sharing of free components. We think this will help meaningfully grow the Elements user base and give everyone access to a much wider range of building blocks.
It’s still not a good idea to distribute Dev packs as it will slow Elements down. They are for Development purposes only. Everything we wrote in the docs still applies.
We’d like to build a way to support sharing of free components, but we have our hands full with finishing Elements 3 and the AI features.
I hope very soon we’ll look at building a solution that allows for easier sharing of free components.
@dan thanks I will wait until sharing in place
I have a lot of components to share, all will be TW4 and kept upto date. Just cannot get involved with selling
@dan very sorry. Let me know what you’d like me to do please… it’s your software your Playground
The real issue here is that there’s apparently no way to have your developed Components in the Store at no cost. Or is there? That would solve the problem.
Well there is, but means signing up to stripe, if you are approved to join the partner programme.
Almost of my components have been built with TW4 for a long time, I had to reference the cdn to run them within Elements, up until v3
Elements components are great, you can do so much, I still believe they are missing a few controls which would raise them to excellent in my mind - if you visit tailwind and look at the classes/options I would like to see some of them added
Simple one is making colors responsive, drives me round the bend I have to write code to achieve this, or hide and add a different component, I like to change colors on smaller screens a lot of the time,
I tried to ‘fill in’ holes in what’s offered on the store and stock components - didn’t want to step on anyone’s toes…
You didn’t I just wanted to clarify the current status, no issues whatsoever
Yes, developers can (and already do) share free components in the Store.