Marketpath CMS Developer Tutorial Series


Last Updated 3/6/2018

Pages are a common topic across Marketpath documentation because they are central to the functionality of nearly every part of the CMS. We cover much of the definition and functionality of pages in other documents, so here we are going to focus on a few ways that developers can get more out of pages.

  1. Use custom fields to select related pages or link to content in new and helpful ways.
  2. Create a page for anything that you want to be "searchable", even if it is consumed using alternate methods on the site. This is because search results only return pages, and only search content on the page itself and on the entity the page belongs to. If the entity does not have a page, it isn't searchable.
    • This does not mean that you have to link to the page anywhere on the site. If you can develop your site to utilize those pages, that's even better, but it is not necessary. If you do not link to the page anywhere on the site, you should remember to preview it from your search results in your QA process.
  3. It is possible (and easy) to pull content for tags, authors, and folders in particular using values passed in query parameters. While this may work well and be easy to code, there are several benefits of pages that you will be able to take advantage of if you make this your primary strategy. It should be just as easy to create a separate tag/author/folder template and create a page for each tag, author, or folder that you want to display in that manner.
  4. You will want to exclude some pages from your search results page (such as thank-you pages, directory listings, certain landing pages, utility pages, and the search results page itself). Double-check that these pages are excluded from search results when you create them and when you go live with your site.
  5. While content creators and editors have the ability to set the Meta Description, Meta Robots, and Keywords properties for each page - and the Browser Title is a required field - they often appreciate it when a developer helps them by setting default values using the {% set_title %}, {% set_description %}, {% set_robots %}, and {% set_keywords %} liquid tags. Be mindful when doing this, though, that if you are not very careful this may cause confusion when editors do not see the same value that they entered. This may also limit your ability to import the same templates onto another site without having to modify them.
---- End of Lesson ----

Question? Correction?

Let's work together to make our documentation as helpful as possible.

What is your name? 
What is your email address?