Making this app primarily for Tailwind devs.
But may come in handy for theme devs. When theme API is open and set in stone, it could have an option to export as elements json.
Great job! I’d love to try it when it’s available.
Thanks, pretty much done with the functionality and UI. When I know for sure what to export for Elements themes I’ll can make it happen.
Few more quality of life improvements :
3 Likes
Looks very cool, can’t wait to see and hear more.
That looks very good! I just downloaded the beta and will play around with it.
Does not appear to be a go’er at this point in time. I can export as elements theme json and create a custom theme. But everything that should not be editable by the end user is.
The only reference to theme json I have is one I grabbed in the very early days of Elements when there was a save theme button in theme studio.
I suspect eventually during the process of encryption these elements get locked down, or they maybe a new key / value that is not yet documented 
Also I suspect Elements will do exactly what the app does now, and save the theme directly in theme studio.
Yes, totally agree. When I played with the App, I thought this is exactly how it should be in Elements. We will se 
We’ve not made the Theme creation/saving public yet… but soon you’ll be able to create new themes, save them into packs and ship them on the store 
As you’ve got a “dev theme” you’ll see the save button in the top right hand corner. If you make some changes to the theme values and hit save it’ll update the file. However, this feature is NOT finished and is not really supposed to be public… have fun, but proceed with caution!
Unzip this sample, change the info.json details and sling it in a dev pack
EDIT: and yes, when you ship a theme it’ll be encrypted and customers won’t be able to modify the original theme
Ha, there’s me saying “I suspect you’ll save the theme from theme studio”. The button’s staring me in the face the whole time 
If I were making a theme, this one for example “Dracula” …
Would you expect the default tailwind colours to be muted like I have here? or create a bunch of extra muted colours.
FOR - muting default tailwind colours in the theme:
If the whole feel of the theme is muted, why have a bunch of default Tailwind colours that will never be used (just clutter).
AGAINST - muting default tailwind colours in the theme:
If I mute existing tailwind colours the default names (required) don’t seem relevant
1 Like
You must include the default Element theme colours, like “brand, accent, surface, etc…” as this is what all Projects and Templates use.
Having a standard set of names Tailwind Colours + named Element Theme Colours ensures everything just works out of the box. Make them whatever colour you want, but do ensure all the default names are included
Hope that makes sense.
Theme Docs - What are Themes? | RapidWeaver Elements Docs
Yeah, I was just having a moment, but as long as the standard tailwind colours are included and I don’t set say “amber” to bright blue, then it all makes sense.
Now I have my theme builder tool finished I should fly through them, and have a fairly hefty pack of themes ready for the store opening.
That would make the most sense 
Just to chip in here, and for anyone else reading this thread: the main reason we decided to include all the standard Tailwind colours is to ensure that any Tailwind code you might find on the internet, or generate with AI, “just works” when pasted in to Elements 
@Doobox Awesome, don’t forget all other values (not just colours), like fonts, and border radius etc… can be set in a theme!
Yeah, I haven’t been that adventurous with my little app 
I just Have a macro %$(colors)%% in a default theme.json template hard coded, the macro is replaced with the colours on export. So Lazy
haha, fair enough, I guess you can make any other theme changes you want in the Elements Theme Studio
Exactly. It’s just the colors that are a bit hard at the moment. Am sure it’ll get another pass in time.
EDIT: Number input field first!
To be honest though, Ive a few components in half finished state as need number field property to work properly with rounding true / false, and min / max.
1 Like