So I built a build test for nova app that has the goal of adding default control groups as seem in core components into your components. Here’s how it works.
But as said in video recreating them all will be tedious and they must be exact.
If anyone wants to contribute and recreate any of the default groups to be added to the build tasks fragments , much appreciated. I have only done “Spacing” so far for testing.
This is cool @Doobox.
Related question, does Nova have any AI assistant integration yet? I saw they were recently having a promotion for like $49 for the app, and was wondering if that was in response to newer AI IDEs like Cursor and Windsurf etc.
This looks interesting! So will it add all property groups that are in the fragments directory or can you select which ones to add?
At the moment it will add all the group json files inside fragments.
I have a half baked version as a nova extension that gives more flexibility but needs more work.
Dont think there is any AI integration, certainly not like high level coding assistant.
Gary brill, I am away for a while but can get to a computer in next day or two. I have codes for image weeks, video wells, sliders and a few others for custom components is this what you want us to give you? TIA
The goal is to have all the default groups:
Once I have those, I can do something. On reflection, it’s all well and good having a build task or Extension for Nova. But I think a MacOS app will be a better tool, so you will be able to drop your properties.json on the app, and select what groups you want added. You’d also be able to add you’re own custom groups you have created for repeated use.
Looks very heath Robinson at the moment, but mostly just UI design and polish from here
Good Progress
You can literally see the groups being added live in Elements, Love it!
Gary,
This is just bloddy amazing!
What a timesaver this will be, sure wish I had it for the project I have jus tbeen working on. Wow! I’m really impressed. Can’t wait to see where you take this, could make component development that much smoother.
Fantastic work.
Game Changer Feature
Gary Image well code for 3 wells and video wells is this the sort of things you want?
"groups": [
{
"title": "RBC Images",
"icon": "paintpalette",
"properties": [
{
"title": "Circle1",
"id": "image1",
"image": {}
},
{
"title": "Circle2",
"id": "image2",
"image": {}
},
{
"title": "Circle3",
"id": "image3",
"image": {}
},
]
}
]
}
Video well
{
"groups": [
{
"title": "Gallery Images",
"icon": "photo.on.rectangle",
"properties": [
{
"title": "Gallery Videos",
"icon": "film",
"properties": [
{
"title": "Video 1",
"id": "video1",
"resource": {
"accepts": "mp4, mov, youtube, vimeo"
}
},
{
"title": "Video 2",
"id": "video2",
"resource": {
"accepts": "mp4, mov, youtube, vimeo"
}
}
]
}
]
}
Thanks, but you will be able to add those as user groups in the app for repeated use on you’re projects.
What I need is exact replications of these core groups as found on most all of the core built in components
:
+1
I’m working on it thanks to @ben
Replicating a scenario similar to the basic options requires RMS to provide a complete HTML + JSON + Hooks example with all nested elements properly ordered.
Despite my experience with stacks, the scenario is different, and in order to produce valid components to distribute in the store, developers should have access to the basic component structure.
This is also for consistency with the sales contract that RMS will propose for the new store. Users expect an equivalent level of quality, and we must satisfy them. 
This would be way easier if the enabled key when disabled stopped the value going to the dom.
Woooweeee, what a thread 
Here’s some quick thoughts and feedback:
And just so you know, we had plans to implement a visual properties builder in Elements, we discussed it waaaay back with @handshaper. However, I’m not sure when we’ll get around to it, as we have a bunch of more user focused features we need to add first.@Doobox I hope that’s all helpful, and do let me know if you need anything else, keep up the awesome work!
Thanks @dan they will be a huge help.
It’s hitting home how complex the next stage of the apps dev will be. To make it much more user friendly, I’m going to have to have my group type carry a javascript payload as well, to write to the hooks file in the case of many of the core groups. 
For now though, I’ll have it just build the required UI group elements, then come back to that.
Brilliant! I want it!
