Create new Themes only in Pro?

No. What if I want a new sub domain project file of my website? I would like the ability to just use the theme I created and saved. Instead of all of the frustrating overrides.

Just had a quick play with that. While it does let you edit each section via override, it really is kludgy…

Not a fan™ of this

I am 50/50 on not being able to create new themes in a nice way, but we should definitely be able to directly edit them to get what we want.

Thanks but correct me if I’m am wrong as Beta 2 has only just come out with the function how has anyone been able to use? I know confusion just comes with my age -Ive got Thursday socks on to day! I know it’s Tuesday but didnt have any of them but got Thursdays ready for tomorrow - nothing like being prepared! :slight_smile:

I see what your saying. Before the ability to create my own theme was released, I was working on creating a template project that was basically a wireframe of the website I wanted to reuse, this was going to serve as my theme.

Some users coming from Classic understand the word ‘theme’ differently.

In Elements, the “theme” is similar to the “theme style” in Classic (specific for each theme); it’s not a physical object but a list of font color settings and more.

The theme in Classic is something completely different, and the ability to change the project’s template (the theme in Classic) with a click and see the site ‘completely change’ is gone with Classic.

With Elements, the theme (meaning Classic) is integrated into the project. Once started, you can change colors, fonts, and other values ​​with a click, but not the site structure (as was the case in Classic).

Even the project in the integrated store, even if updated, has no impact on the project already started. If you buy 1.1 and then the store updates to 1.2, your project will continue to use the original version.

While in Classic, updating the theme also updated the entire project already started. These are two different things.

So it looks like theme creation is branded as “Developer Tools” in the pricing table.
Maybe there is more to follow in terms of developer tools in the Pro level plan :man_shrugging:

Just spit balling here… But would you not think if anything, the subscription may have been cheaper of free for developers, being that the only route to market will be through the store where they planned to take a 20% cut (As previously documented) :man_shrugging:

Are you talking about Themes or Projects? Because Themes are something you can create without the Pro version, you just do it manually as a private Dev Pack, whereas automating creating new Themes for new clients definitely seems like a Pro-minded task. I’m not sure why you’d think you should be selling a Theme standalone.

Hi all, I’m just spitballing here. I have a pro subscription, not because I am a pro, but I thought I would send more funding to the RW development team. In the Pro version you get an Add Theme button, if you click the button it says, “No Dev Packs Found - To create a custom theme, you first need a Dev Pack. Create a Dev Pack folder and load it in Elements to get started.”

I have no clue what that means or how to do that or where to get the Dev Pack from. If someone could point me in the right direction, I could play with it.

But for clarity, is there anything else in a custom theme that you are not able to setup in the existing Theme settings?

And if not, could you not simply override the settings in one of the themes and save it as a project that you could then reuse?

Other than to sell themes on the store, what advantage is there to creating custom themes?

Overriding the theme settings to customize is kludgy and not particularly user friendly™. It has been what we have been doing since the beginning, since the theme settings were locked. We (plus users), should, at a minimum, be able to directly edit the themes. I am still 50/50 on easy creation…

I would say the advantage is that (I think) it would be easier to use the tools provided by the program to do something, than to manually edit JSON files in a DEV PACK. While I do not professionally create websites for a living, I have my main site, a few other personal sites, and might do one or two for family members.

Okay, I figured out how to load the dev pack and was able to create a Theme.

That puts it in the Theme Studio, but it is set up exactly as the theme that you used under “Copy from”. You do have to create and Icon for it. You then have to go in and make all the changes you want and when finished click Save Theme. So if you think the Theme Studio interface is kludgy, you still are using it to modify your theme.

But are you editing your theme directly, or overriding it??

Directly

That was kind of my point… :nerd_face:

But that’s a good thing right?
wether its worth extra £100 is debatable.

I created an app to automate my “Theme” creation a while back :

Very nice! I’d say you’ve already done enough nice things for Elements :clap:

Maybe you’re too ahead :face_with_raised_eyebrow: