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 search experience for your jobs site. You’re going to create a separate experience because you want to customize it to your jobs site.

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 backend flow in the Search Configuration Overview module.
Review the frontend flow in the Overview of Search Frontend Theme module.

Before you start this challenge, make sure you’ve completed all of the modules in both the Search Backend and Search Frontend Theme tracks. 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

Step 1: Create a Backend for the Jobs Search Experience

There are three high level steps to creating a new search vertical (and by extension a new experience):

Make sure the data is in Knowledge Graph
Create or update the Search configuration
Create or update the frontend

You want to create a brand new experience just for jobs and job-related FAQs. Good news is, you already updated the data in the Knowledge Graph Final Challenge to add the job entities and custom fields. In this challenge, you’ll focus on creating a new experience with both a new backend config and a new frontend.

Navigate to Search > All Search Experiences, and then click Add Experience. Create a new Search configuration and call it “Jobs Search” with an experience ID of “jobs-search” (note: make sure the experience ID is “jobs-search” with the dash exactly).
Once the experience is added, click Add Vertical. Add a Jobs vertical.
Click Add Vertical to add the FAQs vertical.
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:
- Entity Type (builtin.entityType) as Inferred Filter
- Location (builtin.location) as Inferred Filter
- Employment Type as Inferred Filter & Keyword Search
- Keywords as Phrase Match
- Name as Keyword Search
- Job Department (c_jobDepartment) as Inferred Filter
For FAQs, you want to have:
- Entity Type (builtin.entityType) as Inferred Filter
- Keywords as Phrase Match
- Question as Semantic Search
Save your experience. Try running a few searches in Test Search to make sure it’s working.
Navigate to Knowledge Graph. Create a saved filter for FAQs (name it FAQs on Search - Jobs) that only includes FAQs that:
- Have Active On Search = Yes
- Keywords include “career”
- Fields with data includes “Answer”
Update the FAQ vertical with the saved filter.
Save your Search configuration.

Step 2: Create a Frontend for the Jobs Search Experience

Navigate to Pages > All Sites. Click Add New Site:
- Choose to store the repository in an internal Yext org.
- Name the site “Jobs Search”.
- Create a new repository and add “.com” to the end of what was autofilled (”jobs_search_ [[accountId]].com”, for example: “jobs_search_2499431.com”).
  - While most of this was filled in by default, it is important to check that this is correct and formatted EXACTLY as listed so that we can accurately grade your experience.
  - For reference, you can also find your account ID by looking in the URL or by navigating to Personal Settings and finding the Account ID field.
- Select the Search Jambo Template to start.
Navigate to the Settings screen of the site and set the username / password for the site in Site Settings. To be consistent with the other sites, 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 file with your experience ID from the Jobs Search backend you created in the previous step. Keep the default locale set to “en”.
Add your universal page using Jambo Commands (Add Page).
- Page Name: “index”
- Page Template: “universal-standard”
- Once the page is created, update the page title to “Job Search” in the index.json file.
Using Jambo Commands, add two new verticals (make sure to map to the vertical keys that are in your backend configuration):
- Jobs: Name it “jobs”, use the job-standard card template, and use the vertical-standard page template.
- FAQs: Name it “faqs”, use the faq-accordion card template, and use the vertical-standard template.
Navigate to the config > json files for your two 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 page title to “Job Search” and “FAQ Search” respectively.
- Comment in and update the icon to “briefcase” for the Jobs vertical and “callout” for the FAQs vertical.
Use Live Preview to preview your changes. If you see a page with desktop/ files, try 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 “job-override”.
- Update the URL of CTA1 to 'http://careers.turtleheadtacos.com' – only until your job landing pages are ready to go.
- Update the subtitle to combine the job department field and the employment type field so the end result on the card looks like this: “[[job department]] | [[employment type]]“, e.g., “Marketing | Full Time”. Be sure to include a space on either side of the |. Hint: You can concatenate items together using +. Try field1 + ‘ | ’ + field2. Remember to use the API names for fields to pull in the correct ones. Check out the View Field API Name (Knowledge Graph) help article.
Update the config > jobs.json file to use the new cardType you just created.
Update the branding for the jobs search like you did for the main brand search. Go to the static > scss > answers-variables.scss file and update:
- -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!).

Step 3: Iterate on your Search Experience

Go to the staging URL. You will need to input the username and password you set in the Settings screen. Run at least 10 searches.
After identifying some good queries, go to your Jobs Search configuration and add at least three universal prompts. Make sure they highlight both jobs and FAQs. Ensure that the prompts are showing up in Test Search or live preview.
Look over the vertical prompts for each vertical. By default, each vertical already has [[name]] to start with.
- Add a vertical prompt for jobs vertical: “open jobs in [[c_jobDepartment]]”. The embedded job department field will dynamically surface prompts for users to search for jobs by department.
Make at least three 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 a new search config for Jobs Search

Add a Jobs vertical to the Jobs Search config

Update the searchable fields for the Jobs vertical

Add an FAQs vertical to the Jobs Search config

Add a saved filter for the FAQs vertical in the Jobs Search config

Update the experience key in the frontend to match the search config

Add an index page to the Jobs Search frontend

Add the Jobs vertical to the frontend

Update the page title for the Jobs vertical

Update the card type for the Jobs vertical

Add the FAQs vertical to the frontend

Add a job override card and update the subtitle

Update the CTA URL on the job override card

Update the branding SCSS variables for the jobs site

Add query suggestions to the Jobs Search config

Common Issues

Common CSS Syntax Issues

Make sure that each rule ends with a semicolon (;).
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 that 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?

If your configuration changes are not saved, or if you are seeing a message that you haven’t made any changes, it is likely because you included an object that was not recognized. In this case, the unrecognized object is removed from the config and any other changes are saved.

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. 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?