Working on a theme locally

Return to top
Have more questions? Submit a request


  • PA-eps

    The "Importing your theme" instruction assumes the theme has been "built" already, but I don't see the instruction on how to build in prior section. Not sure if I missed it somehow.

    After editing the theme locally and previewing with ZAT, what do I need to do in order to build it?


  • Nicole Saunders
    Zendesk Community Team

    Hi PA-eps, 

    I see that this is your first post - welcome to the Zendesk Community! 

    You'll want to review the sections above on starting a new theme and editing your theme to learn about building it. 

    If you have additional questions as you go through, you may want to check out the Guide Q&A topic in the community. There are a number of theme customization experts who spend time there and can give advice and help with custom code. 

  • Abdulrahman Jami

    I've seen the github option, I'm wondering if there is an automatic building and publishing when I push to github, much like a CI/CD pipeline 

  • Erika Camille Sundian
    Zendesk Community Team

    Hi Abdulrahman Jami,

    Just to confirm, you want to update the theme continuously? The GitHub integration can help with the CI/CD pipeline. The theme can be updated with the latest version, you can update any files on GitHub and test them locally, or even on an “offline” theme in Guide.

    Hope this helps! :)

  • Austin Vieth

    Good Morning,


    When working with the ZAT preview is there a way to recompile the SASS on update? I'm using VSCode and with other projects I'd use a bundler like Parcel or Webpack that automatically watches the SASS for updates, is that at all possible within the ZAT bundle?


    Thank You,

    Austin Vieth

  • Bryan - Community Manager
    Zendesk Developer Support Team

    Hello Austin Vieth,

    While zat theme preview monitors for changes in the local directory where your theme's source code is, it doesn't have features to set up pipelines for other forms of transpiling. I haven't tried it, but I could see another watcher of some sort set up that monitors your SASS code, transpiles it, then pushes the result to the theme's source code directory. zat theme preview should then pick up the change and refresh the running theme with the change. Just a thought.

  • Diego Hernandez

    When I preview my theme via $zat theme preview and paste the /start link in my Chrome URL, I receive a 'blocked by CORS policy' error in the console. The origin is my own subdomain URL as expected, and it attempts to fetch at *myMappedDomain*/hc/activity. , which is a URL that throws a 404 error so as far as I can tell, the theme loads trying to fetch data from a page that doesnt exist. This is not part of our code in the templates.

    I did allow for mixed contents to be loaded as per a this article, but there is no mention specifically about the CORS issue.

    While I do use ZAT Tools in this case the troubleshooting step of the Troubleshooting CORS article:

    As part of the Apps framework, a back-end proxy server is available via the client.request() call. Use this proxy by setting cors:false in the client.request's settings (note: false is also the setting's default value).

    does not help since I have the "special case" of previewing the Zendesk Theme which I downloaded from the Guide, there are no explicit client requests being made in the theme files .



  • Cheeny Aban
    Zendesk Customer Advocate

    Hi Diego,

    We have the CORS Troubleshooting that will surely help you find a solution for this issue.

    All the best



Please sign in to leave a comment.

Powered by Zendesk