Module 3 assessment

[Bryan_Rivas]

Hello,

I don’t know where to begin. The instructions are not clear enough at least to me. Need help with these 2 steps:

Step 1: Add FAQs Vertical

1. Navigate to the Edit as JSON screen. This is your JSON file that has your full Search configuration. Click into the file and search (CTRL+F) for “faqs”. You’ll notice that there’s nothing returned – this is because you don’t have a vertical set up for FAQs yet! Feel free to scroll through this file to get familiar before we switch over to the UI to create your vertical.
2. Navigate to Verticals under the Configuration section. Click the dropdown at the top (where it says Settings for:) and click to + Add Vertical.

[Kristy_Huang]

Hi @Bryan_Rivas,

I updated the instructions to try to clarify the steps. Can you take another look and let me know if it’s clear now? What specifically is not clear?

Also here are some resources that may help:

• Navigate Yext Search training
• Add a New Vertical training

[Bryan_Rivas]

For step 6 in module 3 assessment, the below input is not working in JSON. Say’s format is wrong.

“restaurants”: {
“name”: “restaurant”,
“savedSearchId”: “<112002255>”

[Kristy_Huang]

Remove the <> brackets. These are to signal that the value <INSERT SAVED FILTER ID> should be replaced.

[Bryan_Rivas]

I removed them and is not working. Please see screenshot.

[Kristy_Huang]

Hi Bryan,

In this case, the restaurants vertical already exists in the Search config, so you should add this property (savedSearchId) to that existing restaurants object (instead of adding a whole new restaurants object like you were doing). Be sure to add a comma to separate the new property you add.

I see how the instructions can be confusing. I’ve made some updates to the challenge instructions as well as the training section that introduces verticals in the JSON config.

[Bryan_Rivas]

Hello,

I am still stuck. I am not understanding. I need you to send what it is supposed to look like. I tried many things. nothing works.

[Kristy_Huang]

Hi Bryan,

So sorry for the confusion and really appreciate your patience with this! We’re open to feedback, so please let me know if there’s anything you think we could do to make this clearer.

Here’s what the savedSearchId property should look like within the restaurants object. Note I collapsed the events and faqs objects (there are little carrot brackets next to the line numbers) so you could see where it falls within the verticals object.

The purpose of this step is to introduce you to editing in the JSON editor, but this is optional! You can also edit the saved filter in the platform UI as well. There are a handful of advanced properties that can only be edited in the JSON editor, which is when you may want some experience navigating around it.

[Bryan_Rivas]

Hello,

In module 4 assessment, when I submitted the assessment, it keeps saying I haven’t done the synonym set highlighted. Please see screenshot since I did it and it’s not catching it.

Report Card

Add synonym set for restaurant and location
Add a query rule to boost the FAQs vertical
Add at least four universal prompts
Add vertical prompts for FAQs, Events, and Restaurants

[Kristy_Huang]

Hi Bryan,

I’m actually seeing that you’re passing all the rules for this challenge in the backend. Can you try to submit again and include a screenshot of the report card if you don’t pass it?

[Bryan_Rivas]

Hi again,

I completed all the steps in the front-end assessment 2 and it’s giving an incomplete report card. I completed the steps twice to double check as well.

[Bryan_Rivas]

Hello,

Please check why these two incomplete items on the checklist are not reflecting. I completed them.

[Kristy_Huang]

Hi Bryan,

I checked your account and it looks like you are now passing the challenge rule for page title for the FAQs vertical. For the label for FAQs vertical rule, there are a couple of things to call out. You can see below this list for your current code and the solution.

1. The label is still commented out, which means the code editor will not read that code. You need to remove the // to comment in the code. Read more about commented out code in the training.
2. When commenting in properties, you should leave the property name ("label") there and just add in the value for the property.
3. Remember to separate properties with a comma.
4. Not directly related to this grading rule, but I noticed you have files for config > FAQ Search.json and pages > FAQ Search.html.hbs. Note that these file names dictate the search results page URL, so you wouldn’t want to use capital letters or spaces. (Training here)

This is what your config > faqs.json file currently looks like:

Here is the solution:

[Bryan_Rivas]

Hi Kristy,

I don’t understand the commented-out code. I looked at the screenshot and made the edits. Still not working.

[Kristy_Huang]

Hi Bryan,

Please make the changes in the faqs.json file, NOT the FAQ Search.json file. The grading rule is looking for faqs.json and as I mentioned in point #4 above, naming a file FAQ Search.json is not best practice.

[Bryan_Rivas]

Thanks…
I have a question on this one. I added this on the JSON and it does not work.

Assessment 3 front end

Make just the c_restaurantFeatures field searchable by adding this in your Facets object:

"fields": {
  "c_restaurantFeatures": {
    "searchable": true,
    "searchLabelText": "Search for our features",
    "placeholderText": "Search"       
  }
}

[Kristy_Huang]

Hi Bryan,

Looks like you added that code snippet to the end of the file. You actually want to add it to the Facets object as specified in the directions.

You can see an example of this in the Facets training (look at the second code snippet in this section).

Also remember to comment in the Facets object (the instructions say to " remove the /** before and the **/ after the Facets object"). Commenting out means that there are sections of code that is not read and executed by the code editor. Each type of file (.json, .js, .html, etc.) may use different symbols to denote comments, but comments will always appear more faded than the rest of the code (in this case they’re green instead of a brighter blue). In this case, the Facets code was provided in the template, but commented out by default - you just need to comment them in so it is applied. Read more about commented out code in the training.

[Bryan_Rivas]

Is there an easier step by step instructions to complete module 3-11, assessments? I have no experience with this platform. Ive trying for hours now and can’t complete the assessment. I’ve completed the reading and the tests.

[Bryan_Rivas]

Hi Kristy,

Can you please why the last step in adding the SCSS styling for font family isn’t working. Is the last item I need to complete this assessment (6)

[Kristy_Huang]

Hi Bryan,

For the font family property, you can specify the names of the fonts you want to use, instead of the URL link for the fonts.

This is what you currently have. However, you already pulled in these fonts with the embed codes in step 4.

For step 5, fill in the font family with the list given in the instructions:

The result will look like:

  .yxt-Card,
  .HitchhikerFaqAccordion-title,
  .HitchhikerLocationStandard-title,
  .yxt-Results-title, 
  .yxt-Results-viewAllLink, 
  .yxt-Results-changeFilters, 
  .yxt-Results-filterValue
  {
    font-family: Pangolin, 'Open Sans', sans-serif;
  }

  .yxt-AutoComplete-option--item,
  .yxt-SearchBar-input
  {
    font-family: 'Roboto Mono', 'Open Sans', sans-serif;
  }

Apologies for not responding to your previous post. Your CSM reached out to you - we’re interested in getting your feedback on how we can improve the training.

It may also be helpful for you to go through the Technical Skills track. In particular modules 3-7 are related to Search (HTML, CSS, JSON, Handlebars, Javascript) and link out to additional resources.