Help Center templating cookbook (Guide Professional and Enterprise)

Each Help Center theme consists of a collection of editable page templates. You can use the Help Center templating language, Curlybars, to access Help Center data and manipulate the content in your pages.

This article provides a list of recipes with code snippets you can use. Keep in mind that, some of the functionality in these recipes might already be in your Help Center, depending on whether you are using a standard theme or a customized theme and the date you enabled your Help Center.

Access to the page code is available on Guide Professional and Enterpise.

Note: Trial users are given the Guide Professional plan, which includes code editing options, but they can no longer access that feature if they do not purchase Guide Professional or Enterprise.

This article covers the following topics:

• About the Curlybars templating language
• Recipe list

Related topics:

• Using the Help Center templating language
• Help Center templating language reference
• Customizing content with Curlybars
• Help Center CSS cookbook
• Help Center Javascript cookbook

About the Curlybars templating language

Help Center is built on a theming framework that includes its own templating language for advanced customizations.

Each Help Center theme consists of a collection of  editable page templates that define the layout of different types of pages in Help Center. For example, there's a template for knowledge base articles, a template for the list of requests, and so on. A template is simply a text file to be rendered into an HTML page when a user wants to see it. Each template consists of a mix of HTML markup and expressions identifiable by double curly brackets such as {{post.title}}.

The templating language is named Curlybars and implements a large subset of the Handlebars language. But unlike Handlebars which renders on the client-side, Curlybars renders on the server-side.

You can use the Help Center templating language to access Help Center data and manipulate the content in your pages. In the following example, Help Center renders a list of names and avatars of all the people who left comments on the page:

{{#each comments}}
  <li>
    <div class="comment-avatar">
      <img src="{{author.avatar_url}}" alt="Avatar" />
    </div>
    <div class="comment-author">
      {{author.name}}
    </div>
  </li>
{{/each}} 

Previously you could use components to customize Help Center, but you could not customize the components themselves, except for manipulating them with Javascript. With Curlybars you can get access to the HTML that was previously hidden inside component and edit it.

For more information, see:

• Help Center templating language reference
• Using the Help Center templating language

Recipe list

We'll be adding more recipes over time but we can never hope to be exhaustive. The number of things you can do with the templating language is limited only by your imagination. Please post your recipes in the comments section and we'll add them to this cookbook.

• Customize page templates for specific categories, sections, or articles
• Customize the language names in the language selector
• Hide one or more languages in the language selector
• Let users sort article comments by date or votes
• Add a formatting toolbar to the article comment editor
• Enable users to vote on article comments
• Add Instant Search (autocomplete) results to your Help Center
• Add sorting for subscription types in the My Activities Following page
• Add sorting options “created at” and “updated at” for requests in My Activities
• Add Follow/Unfollow for users in a shared organization
• Add ability for users to CC other users on support requests
• Add a link on follow-up requests to the parent request
• Add voting buttons to articles
• Link author names and avatars to Help Center profiles (Professional and Enterprise)

Customize page templates for specific categories, sections, or articles

You can customize the Category, Section, and Article templates for specific categories, sections, and articles respectively.

Applicable templates

• Category
• Section
• Article

Recipe

• Specify the category, section, or article id in a is block:

  {{#is id 200646205}}
    ...
  {{/is}}

Example

Inserting the following block in the Section template customizes the template for sections 200646205 and 203133596:

{{#is section.id 200646205}}
  <p><strong>This is important security information! Pay attention!</strong></p>
{{/is}}
{{#is section.id 203133596}}
  <p>Videos available at <a href="https://www.somelink.com">Learning to fly</a></p>
{{/is}}

Reference

• is helper

Customize the language names in the language selector

You can customize the language names in the language selector on every page of Help Center. This is useful if you want to use one language variant, such as "English (U.S.)", for all the language's variants, such as "English".

Applicable template

• Header

Applicable expression

• {{#if alternative_locales}}...{{/if}}

Recipe

• Replace the {{current_locale.name}} expression with the following conditional expression:

  {{#is current_locale.name 'English (US)'}}
    English
  {{else}}
    {{current_locale.name}}
  {{/is}}

  Also replace the alternative locale {{name}} expression with the following conditional expression:

  {{#is name 'English (US)'}}
    English
  {{else}}
    {{name}}
  {{/is}}

Example

{{#if alternative_locales}}
  <div class="dropdown language-selector" aria-haspopup="true">
  <a class="dropdown-toggle">
  {{#is current_locale.name 'English (US)'}}
    English
  {{else}}
    {{current_locale.name}}
  {{/is}}
  </a>
  <span class="dropdown-menu dropdown-menu-end" role="menu">
  {{#each alternative_locales}}
    <a href="{{url}}" dir="{{direction}}" rel="nofollow" role="menuitem">
    {{#is name 'English (US)'}}
      English
    {{else}}
      {{name}}
    {{/is}}
    </a>
  {{/each}}
  </span>
  </div>
{{/if}}

Reference

• is helper

Hide one or more languages in the language selector

Hiding a language in the language selector can be useful if the content in that language isn't ready for release.

Applicable template

• Header

Applicable expression

• {{#each alternative_locales}}...{{/each}}

Recipe

• Replace the <a href="{{url}}" dir="{{direction}}" rel="nofollow" role="menuitem"> {{name}} </a> expression with the following conditional expression:

  {{#is name 'Français'}}
    {{! do nothing }}
  {{else}}
    <a href="{{url}}" dir="{{direction}}" rel="nofollow" role="menuitem">
    {{name}}
    </a>
  {{/is}}

Example

{{#each alternative_locales}}
  {{#is name 'Français'}}
    {{! do nothing }}
  {{else}}
    <a href="{{url}}" dir="{{direction}}" rel="nofollow" role="menuitem">
      {{name}}
    </a>
  {{/is}}
{{/each}}

Reference

• is helper

Let users sort article comments by date or votes

By default, article comments are sorted by date from the most recent to the least. You can add Date and Votes links that users can click to sort the comments by date or by the number of votes.

Note: The Date and Votes sorting links are available by default in standard themes and themes that were customized after the release of the new Community on November 30th, 2015.

Applicable template

• Article

Applicable HTML element

• <section class="article-comments">...</section>

Recipe

• Insert the following div tag after the comment section's heading tag, <h2>{{t 'comments'}}</h2>, preferably after the {{#if comments}} expression, if any, to ensure the sorters don't appear if nobody left comments yet:

  <div class="comment-sorter">
    Sort by: 
    {{#each comment_sorters}}
      <a aria-selected="{{selected}}" href="{{url}}">{{name}}</a>
    {{/each}}
  </div> 

Example

<section class="article-comments">
  <h2>{{t 'comments'}}</h2>
    {{#if comments}}

    <div class="comment-sorter">
      Sort by: 
      {{#each comment_sorters}}
        <a aria-selected="{{selected}}" href="{{url}}">{{name}}</a>
     {{/each}}
    </div> 
     
    <ul class="comment-list">
      {{#each comments}}
      ...

Reference

• comment_sorters property

Add a formatting toolbar to the article comment editor

You can add a formatting toolbar to the editor for article comments. Users can add bold and italics, unordered or ordered lists, images, and links.

Note: The formatting toolbar is available by default in standard themes and themes that were customized after the release of the new Community on November 30th, 2015.

Applicable template

• Article

Applicable object

• {{#form 'comment'}}...{{/form}}

Recipe

• Find and replace the {{textarea 'body'}} expression in the form object with {{wysiwyg 'body'}}

Example

{{#form 'comment' class='comment-form'}}
  <div class="comment-avatar">
    {{user_avatar class='user-avatar'}}
  </div>

  <div class="comment-container">
     {{wysiwyg 'body'}}
     <div class="comment-form-controls">
       {{input type='submit'}}
     </div>
  </div>
{{/form}}

Reference

• wysiwyg helper

Enable users to vote on article comments

By default, users can vote on articles. You can also let them vote on article comments.

Note: The voting links are available by default in standard themes and themes that were customized after the release of the new Community on November 30th, 2015.

Applicable template

• Article

Applicable expression

• {{#each comments}}...{{/each}}

Recipe

• Insert the following div tag after the <li id="{{anchor}}"> tag:

  <div class="comment-vote vote">
    {{vote 'up' class="article-vote-up" selected_class="vote-voted"}}
    {{vote 'sum' class="article-vote-sum"}}
    {{vote 'down' class="article-vote-down" selected_class="vote-voted"}}
  </div>

  The vote helpers above borrow the CSS classes for articles votes to style the comment vote links. You can define your own classes to style the comment votes.

Example

{{#each comments}}
  <li id="{{anchor}}" class="comment">

  <div class="comment-vote vote">
    {{vote 'up' class="article-vote-up" selected_class="vote-voted"}}
    {{vote 'sum' class="article-vote-sum"}}
    {{vote 'down' class="article-vote-down" selected_class="vote-voted"}}
  </div>
  
  <div class="comment-avatar {{#if author.agent}} comment-avatar-agent {{/if}}">
    <img src="{{author.avatar_url}}" alt="Avatar">
  </div>
  ...

Reference

• vote helper

Add Instant Search (autocomplete search) results to your custom Help Center theme

You can display links to suggested articles as the user types in the Search box by adding Instant Search to your custom theme. 

Note: Instant Search is on by default in standard themes and themes that were customized after the release Instant Search on July 5th, 2016. In standard themes you can disable Instant Search if needed.

When Instant Search is enabled, a maximum of six suggested articles appear as the user types their search term in the Search box. Articles are matched based on the article title only. The user can select matched articles directly from the Search box without going to the search results page first. 

 

Applicable templates

• Whichever template contains your Search expression (most often it's the Header or Home page template)

Applicable expression

• {{search}}

Recipe

• Add instant=true to the Search expression.

  {{search instant=true}}

Example

<div class="search-box">
  <h1 class="help-center-name">{{help_center.name}}</h1>
  {{search instant=true}}
</div>

Add sorting for subscription types in the My Activities Following page

You can make it easier for users to view their subscriptions by enabling them to sort subscriptions by type in the My Activities > Following page.

Applicable templates

• Following page

Recipe

• Under the <nav> tag, insert the following code:

  <div class="my-activities-following-header">
    <span class="dropdown">
      <span class="dropdown-toggle">
        {{current_filter.label}}
      </span>
      <span class="dropdown-menu" role="menu">
        {{#each filters}}
          <a href="{{url}}" aria-selected="{{selected}}" role="menuitem">
            {{name}}
          </a>
        {{/each}}
      </span>
    </span>
  </div>
  
  

Add sorting options “created at” and “updated at” for requests in My Activities

You can add the sorting options “created at” and “updated at” for end-users on the request page in My Activities.

Note: The “created at” and “updated at” sorting options are available by default in standard themes and themes that were customized after August 2016.

Applicable template

• Request list page

Recipe

• Replace {{t 'created'}} with:

  {{#link 'requests' sort_by='created_at'}}{{t 'created'}}{{/link}}

• Replace {{t 'last_activity'}} with:

  {{#link 'requests' sort_by='updated_at'}}{{t 'last_activity'}}{{/link}}

Reference

• requests link helper

Add Follow/Unfollow for users in a shared organization

You can enable users to receive email notifications for requests in their shared organization. The {{subscribe}} helper inserts a "follow" button that users can click if they want to receive email notifications when requests are created or updated in their shared organization. Users also have the option to unfollow if they no longer want to receive updates.

Note: The Follow button for shared organizations is available by default in standard themes and themes that were customized after January 23th, 2016.

Applicable template

• Request list page

Applicable object

• {{#form 'requests_filter'}}...{{/form}}

Recipe

• Add the {{subscribe}} helper to the form object.

Example

{{#form 'requests_filter' class='request-table-toolbar'}}
  {{input 'query' id='quick-search' type='search' class='requests-search'}}
  <div class="request-table-filters">
    {{label 'organization' for='request-organization-select' class='request-filter'}}
    {{select 'organization' id='request-organization-select' class='request-filter'}}
    {{subscribe}}
    {{label 'status' for='request-status-select' class='request-filter'}}
    {{select 'status' id='request-status-select' class='request-filter'}}
  </div>
{{/form}}

Reference

• subscribe helper

Add ability for signed-in users to CC other users on support requests

You can add the ability for signed-in users to add CCs to new and existing support requests in Help Center. When a CC is added to a support request, the copied user will receive email notifications for ticket updates.

Note: The CC option is available for support requests by default in standard themes and themes that were customized after December 14th, 2015.

After you add the code to your custom theme, you must enable the feature (see Setting CC permissions).

Applicable template

• Request page

Applicable object

• {{#form 'comment' class='comment-form'}}...{{/form}}

Recipe

• Insert the following snippet inside the comment form.

  {{#if help_center.request_ccs_enabled}}  
    <div class="comment-ccs">
       {{token_field 'ccs'
          class="ccs-input"}}
    </div>
   {{/if}}

Add a link on follow-up requests to the parent request

You can display a link in a follow-up request to the parent request, if there is one.

Note: The link to the parent request in the follow-up request is available by default in standard themes and themes that were customized after August 2016.

Applicable template

• Request page

Recipe

• Add the following snippet to the Request page template where you want to display the link to the parent ticket (if one is present):

  {{#if request.followup_source_id}}
    <dl class="request-details">
      <dt>{{t 'followup'}}</dt>
      <dd>{{link 'request' id=request.followup_source_id}}
  </dd>
    </dl>
  {{/if}}

Reference

• new request page

Add voting buttons to articles

The vote buttons on articles are part of the standard Copenhagen theme. But if you don't see the option to vote on your articles, you might have removed the buttons from your theme.

The code to add voting buttons can vary from theme to theme, but this is the code from the standard Copenhagen theme, in case you need it.

Applicable template

• Article

Recipe

• Add the following code to the Article Page template:

  <div class="comment-actions-container">
   <div class="comment-vote vote" role='radiogroup'>
   {{vote 'up' role='radio' class='vote-up' selected_class='vote-voted'}}
   {{vote 'sum' class='vote-sum'}}
   {{vote 'down' role='radio' class='vote-down' selected_class='vote-voted'}}
   </div>
   <div class="comment-actions actions">
   {{actions}}
   </div>
   </div>