Module Assessment | Yext Hitchhikers Platform

You must include a first name and last name in your profile to create challenge environments.

Background

You want to create a job search experience for your jobs site. You’re going to create a separate experience because you want to really customize this to your jobs site.

At the same time, you’ll add your job vertical to your main search experience as well.

Don’t remember how to create a new experience? See these units for step by step instructions on creating a frontend and a configuration from scratch.

Review the Search Configuration flow in the Search Configuration module
Review the frontend flow in the Frontend Overview or in Cards & Pages Module

Before you start this challenge, make sure you’ve completed all of the modules in this track. The instructions are meant to challenge you and will provide less detail at each step than in the feature-specific modules. Don’t hesitate to reference past modules if you’re stuck or can’t remember!

Your Challenge

Update your Existing Experience

Add the jobs vertical in your existing Search Configuration either using the UI or using the JSON code editor. Use the verticalKey “jobs”, add the API name and name the vertical “Jobs”. Include the following as searchableFields:
- Name (name) as Text Search
- Entity Type (builtin.entityType) as NLP Filter
- Employment Type (employmentType) as NLP Filter & Text Search
- Keywords (keywords) as Text Search
- Built-in Location (builtin.location) as NLP Filter
- Job Department (c_jobDepartment) as NLP Filter
Navigate to your JSON editor and update the universal prompts to include a prompt for jobs – you should have seven or more prompts now. Make sure to also add a vertical prompt for the embedded prompt type “open jobs in [[c_jobDepartment]]”. This will make sure that all of the open positions by department dynamically appear on the Jobs vertical search page.
Navigate to Pages > Turtlehead Tacos Search, go to the Code Editor, and click into the master branch. Use Jambo commands to add a new vertical in the frontend:
- Add the Page Name as “jobs”
- Update verticalKey - this should be the same as the verticalKey in your Search Configuration. Open up your Search Configuration in a separate tab to verify.
- Use the card template “job-standard” - this will use the Job card built in to the theme
- Use the Page Template “vertical-standard”
Configure the config > jobs.json file properties
- Update the pageTitle to “Job Search”
Verify your changes using Live Preview.
Commit your changes, monitor the deploy and publish your site to staging.

Create a New Experience for the Careers Site

As we covered in the Creating a Vertical End to End module , there are 3 steps to creating a new vertical (and by extension a new experience):

Make sure the data is in the Knowledge Graph
Create or Update the Search Configuration
Create or Update the Frontend

Now you want to create a brand new experience just for Jobs and FAQs. Good news is, you already updated the Knowledge Graph in the Knowledge Graph Final Challenge to add the jobs and custom fields. In this challenge, you’ll focus on creating a new experience and creating a new frontend.

Navigate to Search > All Search Experiences then click the button to “Add Experience”. Create a new Search Configuration and call it “Jobs Answers” with an Experience Key of “jobs-answers” (note: make sure the experienceKey is “jobs-answers” with the dash exactly).
Check off only Jobs and FAQs for your Entity Types (uncheck the rest).
Review the Searchable Fields. If there are any missing, add them by clicking on +Add / Update Fields. If there are any extra ones, uncheck them to remove.

For Jobs, you want to have:
- Name as Text Search
- Entity Type (builtin.entityType) as NLP Filter
- Employment Type as NLP Filter & Text Search
- Keywords as Text Search
- Built-in Location as NLP Filter
- Job Department (c_jobDepartment) as NLP Filter
For FAQs, you want to have:
- Question as Semantic Text Search
- Keywords as Text Search
- Entity Type (builtin.entityType) as NLP Filter
Click Save to create your experience. Try running a few searches in the Test Search to make sure it’s working.
Create a saved search for FAQs that only includes FAQs that:
- Have Active on Answers = Yes
- Keywords include “career”
- Fields with data includes “Answer”
- Call the filter FAQs on Answers - Jobs
Update the FAQ vertical with the saved search.
Save your Search Configuration. If you are running into any errors saving and you’re using the code editor, double check to see if you have any red errors or underlines in your file to find your issue.
Navigate to Pages > All Sites. Then add a new site and choose to store the repository in an internal Yext org. Name the site “Turtlehead Tacos Jobs Search”.
Select to create a new repository and update the pre-filled reposiotry name to jobs-answers.turtleheadtacos-[accountId].com, for example: “jobs-answers.turtleheadtacos-2499431.com”.
- It is important that you do this EXACTLY with your account ID so that we can accurately grade your experience.
- You can find your account ID by looking in the URL or by navigating to Personal Settings and finding the Account ID field.
- Once you’ve entered a name, select the Search Jambo Template to start.
Set the username / password for the site in Site Settings, which you can access on the Settings tab of your site. To be consistent with the other sites for Turtlehead Tacos, let’s use a username of “test” and a password of “test”.
Click into the Code Editor and select the master branch.
Update the locale_config.json with your experienceKey from Step 1. Keep the default language set to “en”.
Using Jambo Commands, add 2 new verticals:
- Jobs: name it “jobs”, add vertical-standard template, and use the job-standard card template
- FAQs: name it “faqs”, add vertical-standard template, and use the faq-accordion card template
Navigate to the config > json files for your 2 new pages. You decide you want icons for your jobs experience, even though you didn’t use them for your main experience. For both pages:
- Update the pageTitle with “Job Search” and “FAQ Search” respectively.
- Comment in and update the icon with “briefcase” and “callout” respectively.
Using Jambo Commands, add your Universal page (Add Page).
- Use the “universal-standard” page template
- Name it “index”
- Update the pageTitle to “Turtlehead Job Search”
Use Live Preview to preview your changes. You might see a page with desktop/ files. Trying clicking out of the code editor and wait for the build to be completed and refresh the page. Also, if you try to use Live Preview before you create your index page, you’ll need to navigate to desktop > jobs.html or faqs.html directly.
You decide you want to change the mappings for the Job card. Add a new card, forking the job-standard card. Name it “joboverride”.
- Update CTA1 URL to'http://careers.turtleheadtacos.com – only until your job landing pages are ready to go
- Update subtitle to combine the c_jobDepartment field and the employment type field so the end result on the card looks like this: “[jobDepartment] | [employmentType]“, e.g., “Marketing | Full Time”.
Hint: You can concatenate items together using +. Try field1 + ‘ | ’ + field2.
Update the config > jobs.json file to use the new cardType you just created.
Update the branding for Turtlehead. Like you did for the restaurants. Go to the static > scss > answers-variables.scss file and add:
- --yxt-color-brand-primary to #32a85e
- --yxt-color-text-primary to #373a3c
- --hh-answers-background-color to #efefd4
Preview your changes to make sure things look okay.
Commit your changes, then go to the deploys screen. Monitor the deploy for any issues. Once it’s deployed, make sure the most recent deploy is published to staging (this should happen automatically once the deploy is completed!).
Go to the staging URL and run at least 10 searches.
After identifying some good queries, go to your Jobs JSON Search Configuration and add a universalPrompts object within querySuggestions and add at least 3 prompts. Make sure they highlight both jobs and faqs. Ensure that the prompts are showing up in Test Search or live preview.
```
    "querySuggestions": {
      "popularQueriesBlacklistedTerms": [],
      "universalPrompts": [
        "INPUT PROMPT 1",
        "INPUT PROMPT 2",
        "INPUT PROMPT 3",  
      ]
    },
```
Make at least 3 improvements to your experience, either in terms of the UI or the search quality. Use the feedback form in the bottom right of the screen (thumbs up icon) to let us know what you did and show off your work.
Make sure the config labels are up to date and publish your experience that you made from scratch!.

Congrats, you did it! You built your own Search experience end to end!

Module Assessment

+<% util.points %> points

Weekly Challenge Streak: <% util.streakWeekly %>

You must include a first name and last name in your profile to create challenge environments.

Challenge account expires in <% util.expirationHours > 24 ? Math.round((util.expirationHours * 1.0) / 24) : util.expirationHours %> <% util.expirationHours > 24 ? (Math.round((util.expirationHours * 1.0) / 24) == 1 ? 'day' : 'days') : (util.expirationHours == 1 ? 'hour' : 'hours') %>.

Challenge account has expired. Please create a new account.

Report Card

Add searchable fields to the Jobs vertical in the main config

Add Jobs page to the main experience and update verticalKey, pageTitle, and cardType

Add a universal prompt and vertical prompt to query suggestions for the Jobs vertical in the main experience

Add new Search Configuration for Jobs

Add Jobs vertical to the Jobs config

Add searchable fields to the Jobs vertical in the Jobs config

Add FAQ vertical and searchable fields to Jobs experience

Update the locale configuration with your experienceKey and locale

Add Jobs vertical page to the Jobs experience

Add FAQs vertical page to the Jobs experience

Add custom job card to the Jobs experience

Add 3 universal prompts to query suggestions for the Jobs experience

Common Issues

Common CSS Syntax Issues

Make sure that each rule ends with a semicolon ;, otherwise the CSS will be invalid
Check that brackets { } are closed, and any nested CSS is properly contained within its parent container
Check that you’re targetting the right class - inspect your preview link to determine what class you should target
Ensure your rule is not being overriden by a more specific rule elsewhere in the CSS

For a refresher on CSS basics, review the Introduction to CSS module

Configuration changes not saved or showing a message that there are no changes?

This is likely because you included an object that was not recognized and the Yext system is removing it from the config and saving any other changes.

If you’re adding something that is top-level, like the synonyms or autocomplete objects, make sure it’s not nested inside of a vertical. Conversely, if you’re adding a searchable field or a saved filter, make sure it is nested appropriately.

Do you have an error for adding searchable fields?