This repository contains the RKVST support website frontend running on the Zendesk Guide platform.
This is a forked copy of the Evoko Theme.
The theme is based of the default Zendesk Copenhagen theme which is designed to be responsive and accessible. Check out the Using themes and customizing your Help Center section and developer documentation to learn more.
When importing a theme to Zendesk Guide it will mainly look for the following files and folders:
templates/- contains all markup.Style.css- contains all CSS.script.js- main script file that will be included in the page<head>.assets/- assets such as scripts or images.manifest.json- project metadata and settings.settings/- files to be used in settings inmanifest.json.
Other files and folders can be added to the project but will (to my knowledge) be ignored when importing.
For markup Zendesk Guide uses Handlebars and each template is stored in the templates/ folder. All available templates for a Zendesk Guide theme that has all the features enabled are included however not all of them are used in our case (like "Community").
- Article page (
article_page.hbs) - Category page (
category_page.hbs) - Community post list page (
community_post_list_page.hbs) - Community post page (
community_post_page.hbs) - Community topic list page (
community_topic_list_page.hbs) - Community topic page (
community_topic_page.hbs) - Contributions page (
contributions_page.hbs) - Document head (
document_head.hbs) - Error page (
error_page.hbs) - Footer (
footer.hbs) - Header (
header.hbs) - Home page (
home_page.hbs) - New community post page (
new_community_post_page.hbs) - New request page (
new_request_page.hbs) - Requests page (
request_page.hbs) - Search results page (
search_results.hbs) - Section page (
section_page.hbs) - Subscriptions page (
subscriptions_page.hbs) - User profile page (
user_profile_page.hbs)
Additionally you can add up to 10 optional templates for:
- Article page
- Category page
- Section page
You do this by creating files under the folders templates/article_pages/, templates/category_pages/ or templates/section_pages/.
Learn more here.
The styles that Zendesk Guide will read are in the style.css file located in the project root.
For development this project uses the CSS preprocessor Sass with the .scss syntax where we split styles into Sass partials. All the partials are put under the styles/ folder and included in the index.scss which is then compiled to style.css.
styles/_partial.scss 🡆 styles/index.scss 🡆 style.css
The main JavaScript file script.js is located in the project root and will be added in the document <head> of every page.
JavaScript that you do not think belong in the document <head> can be added inline in templates or added as regular *.js files in the assets folder and then be included in the appropriate template(s).
You can add assets as images and files to the assets/ folder and use them in your CSS and templates, for example:
# template
{{asset 'cat-image.jpg'}}
# css
$assets-cat-image-jpgThe assets will be uploaded to Zendesk CDN (theme.zdassets.com). You can read more about assets here.
The manifest.json contains theme metadata and allows you to define a group of settings for your theme that can then be changed via the UI in theming center.
You can read more about the manifest file here.
If you have a type variable of file, you need to provide a default file for that variable in the settings/ folder. This file will be used on the settings panel by default and users can upload a different file if they like.
For Example, if you'd like to have a variable for the background image of a section, the variable in your manifest file would look something like this:
{
...
"settings": [{
"label": "Images",
"variables": [{
"identifier": "background_image",
"type": "file",
"description": "Background image for X section",
"label": "Background image",
}]
}]
}And this would look for a file inside the settings/ folder named background_image.
To start contributing, clone the repository (git clone https://github.com/rkvst/zendesk-theme.git) and create a feature/bug branch (e.g. git checkout -b feature/that-new-feature or bug/fix-for-that-bug) to work on.
You can use your favorite IDE to develop and preview your changes locally in a web browser using the Zendesk Apps Tools (ZAT) which is installed as a Ruby gem. For more details, see Previewing theme changes locally.
To avoid having to enter your Zendesk credentials every time you start your development environment you can create a .zat file in the project root which contains your credentials in json format, for example like this:
{
"subdomain": "erm",
"username": "[email protected]/token",
"password": "YOUR_API_TOKEN"
}To make use of some development tools you will need to have Node.js installed and then run the below command:
npm installIn package.json you will find a list of the dev dependencies along with some npm scripts. Example on how to run a script:
# Watch Sass changes and write to style.css
npm run styles:watch
# Complies Sass, minify and autoprefix to style.css
npm run styles:buildFor deploying changes to production we use the Zendesk GitHub integration, the workflow can be summarized to:
- Increment the
versioninmanifest.json(without this Zendesk won't recognize an update). - Commit your changes and merge your branch to the master branch.
- In the Zendesk Guide theming center press Update from GitHub.
- Changes should now be live! 🎉
If you'd like to test your changes on a live website (instead of Local previewing) before updating production then you could keep the changes on a separate branch than master and import the theme to the Sandbox environment.