Is developing themes via https://discourse.theme-creator.io no longer viable?

Is developing themes via https://discourse.theme-creator.io/ no longer applicable?

I followed the steps in Designers Guide: Getting Started with Themes in Discourse - Docs / Developer Guides - Discourse Meta, and everything went smoothly. However, after updating the code locally, the command line indicated it was synchronized. But I cannot see the latest code on My Themes - singi2016cn - Theme Creator, and the configuration on My Themes - singi2016cn - Theme Creator also doesn’t take effect.

I assume you are using an API key to connect with the theme CLI? Theme Creator does have bugs, so I’d recommend using a development environment, or using a GitHub repository with Theme Creator.

1 Like

I am using this key, and then developing locally. I ran discourse_theme watch quectel, but I cannot see the page update in real-time.

1 Like

Yeah as Nate said: we’re aware it’s quite buggy atm. Is there anything in the console that can give an indication?

And is it an option to simply develop locally instead?

Thank you for your reply. Yes, currently, I can only choose local development. Should the tutorial be updated to suggest using a local environment for development as much as possible? Otherwise, it’s easy for newcomers to fall into this predicament again and waste time.

3 Likes

@david good point to maybe steer people away from it. wdyt?

2 Likes

Theme creator is definitely still supported, so please do report any critical issues.

From your screenshot. It looks like your theme was created successfully. Did you use the “Preview” button to see the theme in action?

1 Like

Yes, I used the preview. Then I modified the code locally and ran discourse_theme watch quectel.

However, the effect is not visible on https://discourse.theme-creator.io/. Even though the command line shows Sync successful.

.

Another issue is that the theme configuration edited on https://discourse.theme-creator.io/ cannot be saved. After refreshing the page, it is reset.