Introducing the new theming experience for Zendesk Guide

Have more questions? Submit a request

40 Comments

  • Matthias

    Wow, it seems you guys have finally stepped up development of Guide/Help Center again. I was writing you off after my first trial a few months ago due to slow progress, but am considering switching to Zendesk again. Keep it up!

    0
  • Nicole - Community Manager

    Hey Matthias - 

    There's always a ton of development work being done. Some projects take a long time, and sometimes they get interrupted by other priorities. But I'm glad to hear that you appreciate this development. 

    2
  • Mads Berner

    Very cool, good job :-)

    0
  • Angela Cesere

    This is just an update to the UI, correct? If I upgrade, I will not loose any custom CSS/HTML/JS changes that I have made to my theme?

    0
  • Ryan McGrew

    Hi @Angela,

    Your existing theme will remain unchanged when you migrate over. We've improved the tools and features to build and manage your theme are much improved!

    Thanks!

    1
  • Dan Ross

    Ryan, I just wanted to say that I was able to take advantage of the live/staging feature today, to deploy a new feature to one of our Guides. So painless.

    Being able to do all the work and test it out with a copy of our live theme and content, and then deploy it easily was such a pleasant experience.

    Thanks to you and your team for this feature!

    0
  • Ryan McGrew

    Thanks for the feedback Dan! We appreciate it.

    0
  • Brian Lehnen

    Perfect timing! Have spent the past few weeks custom theming our new Help Center in Sandbox. Was not looking forward to manually migrating to PRD, but just took care of this in 30 seconds. This just made my week, thank you! Now if you could just package/import custom forms and fields ;)

    2
  • Cosley Campbell

    We're really excited about this possibility! Would the edited or modified themes be supported by Zendesk and automatically updated when new features are released?  Per this article https://support.zendesk.com/hc/en-us/articles/203664326-Customizing-your-Help-Center-theme-Guide-Professional- that was not the prior functionality. 

    0
  • Dan Ross

    @Cosley I doubt it, they'd have no way of knowing what customizations have been done on a user's theme and wouldn't want to risk breaking anything by auto-applying a patch.

    That said, I'd love if there was a feature for custom themes to apply a differential patch from Zendesk with whatever new updates are available in the master theme. That way, we could see what changed and test out the newest version of the theme against our custom one and decide if we want to apply the patch.

    0
  • Ronald Devine

    We have a web designer who works in our sandbox making updates and changes to the Guide theme and we don't want this person to have the ability to push things over to the live environment. The primary owner of the site must make all approvals before anything to move to the live site at our company.

    Are there role options that can be set in the sandbox that allows someone to have admin role but to disable the option in this new feature so they cannot push changes over to the live environment?

    We want to turn this feature on but it was not even considered or planned to have this kind of restrictions in the sandbox we cant use it.

     

    0
  • Dan Ross

    there isn't a set of permissions like you're describing now, but you can export your developer's work from the sandbox and deploy into your production really easily with the new import feature.

    0
  • Remi Barraquand

    @ryan thanks for the update!

    I tested it and here is few bugs I found:

    • the woff2 filetype is not supported. In the current theme I am using we have an asset "dripicons-v2.woff2", exporting and importing the theme fails due to this font being rejected. Woff2 is required for us, so I see this issue as a regression.
    • manifest.json does not accept: (a) empty variables, meaning having "variables": [] is not allowed, importing the theme will fail with such settings. (b) the field "options" requires at least 2 elements, providing only one option will be rejected. This is a minor issue, but still worth looking into.

    Best,
    Remi

    0
  • Ryan McGrew

    Hi @Remi,

    Woff2 files should be supported and I've reached out via a ticket to try and address the issue you're experiencing.

    With respect to the manifest.json, we have some required variables that must be included. You can find documentation on that here

    Thanks!

    0
  • Remi Barraquand

    The issue happened after importing our theme that I just exported from Zendesk: the theme was working fine, I exported it, and could not import it back (without making any change, the same zip). I'll contact you directly in the ticket.

    Thanks!

     

    0
  • Gene Henson

    I've had the same export/import issue with the maniffest.json files. Please let me know if I should create a ticket for it too.

    0
  • Ryan McGrew

    Hi @Gene,

    The behavior in the manifest as Remi described is expected. If you read the linked documentation that should give you more information on the requirements of the manifest.json file.

    If you're running into other issues, you may want to reach out to support so we can escalate the issue and try and resolve it.

    Thanks!

    0
  • Aaron Ilika

    Hi folks, 

    I get this error when I try to duplicate my current (live) theme:

    Failed to duplicate theme

    There was an error

    Nothing urgent on my end, just wanted to flag for your review.

    Thanks,
    Aaron

    0
  • Oxana Noa Umansky

    I have the same issue as Aaron

    0
  • Sean Wattles

    How do I revert back if at all possible? .

    0
  • Ryan McGrew

    Hey @Sean,

    I'm concerned there might be some misunderstanding on the functionality of the product. I'm going to go ahead and open a ticket so we can resolve the issues you're encountering.

    Thanks!

    0
  • Nitya Subramani

    I believe this has been answered previously, but I wanted to confirm that we won't lose any functionality with custom themes, correct? We recently signed a Zendesk services engagement and had a custom Help Center designed to suit our needs, so I wanted to confirm that we will still maintain all the functionality of our Help Center after upgrading to the new theming experience?

    0
  • Ronald Devine

    I have the exact same issue and concerns as Nitya above.  We just had a custom theme designed and deployed just a month ago and I need to know 100% that enabling this new feature and or using it will not change or create a single issue for our theme in production.

    0
  • Dan Ross

    Hey Nitya and Ronald,

    I don't work for Zendesk and can't guarantee anything for you and your mileage may vary, but while you're waiting for Zendesk to reply, I thought I would share that we have 4 help centres, all with custom themes and extensions that migrated seamlessly to the new Theme Editor.

    For us, it's been a developmental renaissance is easily the best update Zendesk has made this year.

     

    1
  • Ryan McGrew

    Hi Ronald and Nitya

    We have worked hard to make this migration process backward compatible. We don't anticipate any issues for customers migrating into the new system. You can migrate one brand at a time if you have multi brand enabled to test and validate the migration. You can also migrate your sandbox first, if you have one just to verify. If for whatever reason you were to run into issues, please just open a ticket with our support team and we'll get it escalated and resolved as soon as we can.

    Thanks!

    0
  • Jens Herlevsen

    Hi guys,

    Thought this might be of interest to some of you:

    Since the new help center theme platform is now publicly available, we have released a tool/boilerplate that can help you compile your theme templates, javascript and css. It's available here: https://github.com/Cloudhuset/Zendesk-Guide-Theme-Boilerplate 

    First of all you can develop locally, thanks to the ZAT tool from Zendesk. It also compiles your templates with posthtml, your sass files with node-sass and your javascript files with webpack and babel. It lets you use environment specific configuration files to compile different values for different environments. It also help you minify your build and package a zip file that you can import directly to the new theme platform.

    Hope someone will find this useful and please get in touch if you have any suggestions or feedback :-)

    Jens Herlevsen
    Cloudhuset.dk

    3
  • Luis Almeida

    Hi Jens,

    This is really exciting!

    I believe you've forgot to make the repo public or the url might be incorrect as we're getting a 404 page.

    Could you look into it so we can have access to the repo?

     

    Thanks!!

    0
  • Jens Herlevsen

    Hi Luis,

    Oh sorry, you are right. it's public now :-)

    0
  • Luis Almeida

    @Jens,

    I can imagine this tool will be quite useful to other theme developers as well so thanks a lot for the work you put in it and for making it public!

    I can see you're using the Copenhagen theme as your starting point. Have you looked into the copenhagen-theme official repo and how the styles are split into partials?

    Just pointing it out as you're also providing SASS compilation with partial support.

    0
  • Jens Herlevsen

    Hi Luis,

    Thanks for the suggestion. I wasn't aware the sass files was publicly available. I have added it to the repository along with the license that you use :-)

    0

Please sign in to leave a comment.

Powered by Zendesk