Case Study CMS Guide

Overview: This guide explains how to complete the fields on the backend of the Case Study page. Case studies will appear in the case study feed, and your inputs affect how they are displayed across the website.

Step-by-step guide to completing the Case Study:

1. Brand:

  • Description: Select the brand for which the case study is relevant. This determines where the case study will appear on the website and which brand-specific styling or branding elements are applied.
  • Important Caveat: Currently, the website has been set up with CMTG as the master brand for content. This means that when a case study is created, the content will be shared across brands. For example, a case study created for Beran will still return users to CMTG when they click through to the full case study. This behavior is subject to a development ticket that is in progress but temporarily on hold while the DJB website content is being tidied up. Please bear this in mind while adding new content.
  • Options
    • Beran
    • Prosig
    • SEI
    • Semia
    • CMTG
    • DJB
    • Helitune
  • Action: Choose the appropriate brand from the dropdown.

2. Title

  • Description: Enter the title of the case study. This will be displayed as the headline on the case study page.
  • Action: Type the full title of the case study.

3. Title Background

  • Description: This is where you can upload a background media item (such as an image) for the case study title.
  • Note: No media items are selected indicating there is no background image currently set.
  • Action
    • Click to select the media item for the background. You will be prompted to upload an image or select one from the media library.

4. Content

  • Overview
    • Description: The Overview field must be filled in as it shows up on the case study feed (similar to news and event pages). It is the short description or summary that will appear in case study blocks across the website.
    • Action: Provide a brief, impactful summary of the case study that highlights its key points, making it enticing for users to click and read more.
    • Text Format: Choose Filtered HTML for a basic text format without advanced styling options.
  • Body
    • Description: The Body is the detailed content of the case study. This is where you can provide the full explanation, process, results, and other in-depth details of the case study.
    • Action: Write or paste the full text of the case study here. You can format the text with headings, bullet points, images, etc., depending on the case study’s complexity.
    • Text Format: Choose Filtered HTML for standard formatting.

5. Show Row Weights

  • Description: This setting controls the order in which elements like fields or content appear on the page.
  • Action: Leave this as default unless you need to rearrange rows manually (typically, this isn’t necessary for most users).

6. Related Products

  • Description: Link any related products to this case study. These products will be shown on the case study page as additional information or recommendations.
  • Action: Start typing the name of the product in the Related products field. As you type, products matching the name will appear in a list. Click on the appropriate product to add it. You can add as many related products as needed, but it is recommended to only select products that are highly relevant to the case study.

7. Assets

  • Description: This is where you can add related files, documents, or other media (e.g., PDFs, videos) associated with the case study.
  • Action: Upload or select any relevant assets for the case study.

8. Last Saved

  • Description: Displays the last time the page was saved.
  • Action: This is for reference only and does not require input.

9. Author

  • Description: This field automatically fills with your name if you’re logged in as the author (e.g., Debs).
  • Action: No action needed unless you are editing as someone else.

10. Revision Log Message

  • Description: A brief description of the changes made to the page.
  • Action: Enter a short note explaining what edits were made (e.g., Added new case study content).

11. Scheduled Moderation State Change

  • Description: Set when the case study should be published or moved to a different moderation state (e.g., Draft, Published).
  • Action: Set this only if the case study needs to be published at a specific time or reviewed by a moderator before going live. For most cases, this can be left as "Not in menu."

12. Menu Settings

  • Description: Controls where the case study will appear in the site's menu.
  • Action: Leave as Not in menu unless you want the case study to appear in the navigation.

13. Metatags

  • Description: Metatags are used to improve SEO (Search Engine Optimization) by providing important metadata about the page content. These tags are visible in the source code of the page and can influence search engine rankings and how pages appear in search results.
  • Important Note: We require the Meta Title, Meta Description, Abstract, and Keywords fields to be completed for every page of content to ensure consistent SEO optimization across the site.
  • Action: For each page, fill in the following fields:
    • Meta Title: A concise title (ideally 50-60 characters) that accurately describes the content of the page. This title appears as the clickable headline in search engine results.
    • Meta Description: A short summary (ideally 150-160 characters) that gives search engines and users a brief idea of what the page is about. This appears below the meta title in search engine results.
    • Abstract: A more detailed summary (up to 250 characters) used by some search engines to describe the page content. This may be displayed in search results, social media previews, etc.
    • Keywords: A list of relevant keywords (separated by commas) that describe the content of the page. These keywords help search engines understand the topic of the page. Ensure they are highly relevant to the content, avoiding irrelevant or overly general terms.

14. Search API Exclude

  • Description: Use this setting if you want to exclude this case study from search results.
  • Action: Leave this unchecked unless the case study should not appear in search results.

15. URL Alias

  • Description: The URL alias determines the web address for the case study page.
  • Action: Leave as Automatic alias unless you need to specify a custom URL.

16. Authoring Information

  • Description: Shows who created and last edited the case study, including the date and time.
  • Action: No action needed.

17. Promotion Options

  • Description: Allows you to set whether this case study should be promoted (e.g., featured on the homepage or in a case study block).
  • Action: Leave these options as default unless specified otherwise by the marketing team.

Final steps

  • Once you've filled in all the fields, double-check for accuracy and completeness.
  • Click Save to save your changes.
  • If you want to preview how the case study will appear, use the Preview option before saving.

This guide will help you efficiently complete the Case Study page in the CMS and ensure the correct information is displayed across the site. Let me know if you need more detailed instructions for any specific field!