# Setting up a solid workflow for custom theme development **URL:** \ **Category:** Development\ **Created:** [December 9, 2018, 5:12pm UTC](https://meta.discourse.org/t/setting-up-a-solid-workflow-for-custom-theme-development/103841 "2018-12-09T17:12:46Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\ **Post date:** [December 10, 2018, 9:56pm UTC](https://meta.discourse.org/t/setting-up-a-solid-workflow-for-custom-theme-development/103841/8 "2018-12-10T21:56:23Z")
Using the built-in editor in `Admin > Customize > Themes` might be the best way if you can’t get the CLI to work. The CLI was built because there really wasn’t an ideal way to develop themes for Discourse previously, so I’d like to help you get that worked out if possible. Are you able to install Discourse locally using any of the methods here: [Topics tagged dev-install](https://meta.discourse.org/tags/dev-install)? You can point the Theme CLI at localhost, which might help avoid any of the network issues you were running into. ~~Have you tried using a Discourse instance that’s not hosted by nodechef? I wonder if there’s a peculiarity with them specifically (I’m going to try an install there and see if I run into any issues).~~ Update: Just tried using nodechef and didn’t have any issues with getting the CLI up and running. --- _[View the full topic](https://meta.discourse.org/t/setting-up-a-solid-workflow-for-custom-theme-development/103841)._