{"id":519,"date":"2017-10-18T13:14:41","date_gmt":"2017-10-18T17:14:41","guid":{"rendered":"http:\/\/amy.imarketbeta.com\/blog\/?page_id=519"},"modified":"2017-11-14T12:20:38","modified_gmt":"2017-11-14T20:20:38","slug":"template-variables","status":"publish","type":"page","link":"http:\/\/amy.imarketbeta.com\/blog\/part-2-staff-user-guide\/creating-and-editing-pages-and-weblinks\/template-variables\/","title":{"rendered":"Template Variables"},"content":{"rendered":"

Template Variables<\/h1>\n

A template variable is a custom field that extends the default attributes for a Page. In other words, template variables allow you to make custom changes to an individual page’s behavior. Certain template variables exist by default across all iMarket sites. Site-specific template variables are added by Development to add functionality based on the site’s design. We’ll explore both default and custom template variables below.<\/p>\n

Location of Template Variables<\/h2>\n

To modify a page’s template variables, first open it for editing (instructions about editing pages can be found here<\/a>). Template Variables appear in the General Tab under the Main Content section.<\/p>\n

\"\"<\/p>\n

Default Template Variables<\/h2>\n

The iMarket CMS has default template variables that appear on every site and are used for SEO purposes. For example, every site has the option to exclude a page from the XML sitemap.<\/p>\n

There are additional default fields highlighted below, with descriptions to follow.<\/p>\n

\"\"
These highlighted fields are template variables included in all iMarket sites.<\/figcaption><\/figure>\n
    \n
  • duplicate_content_id<\/span><\/strong> = Using this in conjunction with an iMarket-specific shortcode will allow you to make a duplicate version of a page. This is often used for pages that appear in multiple sections of a website (for example: A Heat Pumps page that appears under both Heating and Plumbing.)<\/li>\n
  • xml_sitemap_exclude<\/span><\/strong> = Checking this box excludes the page from the XML sitemap.<\/li>\n
  • Meta Description<\/span><\/strong> = Content entered in here will make up the Meta Description of the page, which is used for SEO purposes.<\/li>\n
  • Meta Keywords<\/span><\/strong> = Content entered in here will make up the Meta Keywords of the page. In the past this feature was used for SEO purposes, but it is done less so now.<\/li>\n
  • Any additional meta tags<\/span><\/strong> = As the name implies, this field can be used for additional meta tags.<\/li>\n
  • Meta Robots<\/span><\/strong> = This is typically used to add NOINDEX,NOFOLLOW robots to a page, which is used for SEO purposes.<\/li>\n<\/ul>\n

    Custom Template Variables<\/h2>\n

    Every site has custom template variables that are included by Development during the initial site build. Most often these template variables give an iMarketStaff user the ability to toggle on\/off certain blocks from the Subpage template.<\/p>\n

    It is now a best practice for Developers to include template variables to toggle off any\/all subpage sidebar blocks, however, older sites may not have this functionality included.<\/strong><\/p>\n

    Since each site has a different selection of custom template variables based on its design, let’s look at one site as an example:<\/p>\n

    \"\"<\/p>\n

    If we open this page in the iMarket CMS manager, we’ll see that the highlighted elements have template variables included for customization (pictured below).<\/p>\n

    \"Template<\/p>\n

    The functionality of each template variable should be evident in the title\/description, but some may be a little less clear. Let’s look at each one individually:<\/p>\n

      \n
    • Use image in page design automatically:<\/strong>
      \nThis refers to the Featured Image of the subpage. Checking “off” will hide the image (and in this case, will also hide the Hero text).<\/li>\n
    • Exclude text for hero image
      \n<\/strong>As the description explains, checking this box will hide the hero text from the featured image (in this case, the “Heating” text with the white box background).<\/li>\n
    • Text for hero image<\/strong>
      \n<\/strong>By default, this site uses a shortcode to automatically fill in the Hero Text with the Menu Title. An iMarketStaff user could remove this shortcode and add custom text in this field.<\/li>\n
    • Checkbox to Exclude All Sidebar Content
      \n<\/strong>Checking this box excludes the entire sidebar and makes the top and main content full-width.<\/em><\/li>\n
    • Checkbox to Exclude Promotions Sidebar
      \n<\/strong>Checking this box excludes the promotions block from the sidebar.<\/li>\n
    • Checkbox to Exclude Testimonial Sidebar
      \n<\/strong>Checking this box excludes the reviews block from the sidebar.<\/li>\n
    • Checkbox to Exclude Service Area Section from Sidebar
      \n<\/strong>Checking this box excludes the service areas block from the sidebar.
      \n<\/strong><\/li>\n
    • Checkbox to Exclude Newsletter Signup Sidebar
      \n<\/strong>Checking this box excludes the newsletter signup block from the sidebar.
      \n<\/strong><\/li>\n<\/ul>\n

      Since each site design is custom, there will likely be other template variables you come across that are not illustrated in this example. Reading the title and description of the\u00a0template variable should give you a clue about how it functions. If something is unclear, please open a ticket to Development.<\/p>\n

      Otherwise, iMarketStaff users should feel free to use the available template variables to customize pages based on client requests.<\/p>\n

       <\/p>\n","protected":false},"excerpt":{"rendered":"

      How to use template variables to customize website functionality on a page-by-page basis. <\/p>\n","protected":false},"author":1,"featured_media":0,"parent":500,"menu_order":25,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/pages\/519"}],"collection":[{"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/comments?post=519"}],"version-history":[{"count":1,"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/pages\/519\/revisions"}],"predecessor-version":[{"id":1660,"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/pages\/519\/revisions\/1660"}],"up":[{"embeddable":true,"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/pages\/500"}],"wp:attachment":[{"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/media?parent=519"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/categories?post=519"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/amy.imarketbeta.com\/blog\/wp-json\/wp\/v2\/tags?post=519"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}