Is there quick guide to create a Jambo site for an answers experience?

Search
1

Is there a quick step by step guide for creating a Jambo site after creating the Answers experience?

I’m having trouble with the post-creation steps after you use the Jambo repo template.

What is the minimum number of files one needs to add or edit to get a working site?

2

Hi Ben,

We can definitely add this to our backlog, that’s a great idea! Let us know more details about what trouble you’re having to help us make sure we provide the right documentation or debugging for you.

At a minimum, you need to do the following:

  • Update the global_config.json or locale_config.json (depending on what version you’re using) with the experienceKey and locale
  • Add at least one page using Tools > Jambo Commands. If you are not adding an “index” page, remember that clicking live preview will take you to a landing page where you’ll need to pick which html file you want to open.
  • For that one page, you must fill out: verticalKey, verticalsToConfig.verticalKey, verticalsToConfig.cardType.

That should be all you need to get started. Optionally, you can also do things like:

  • Add or remove any components on the pages by updating the pages/html.hbs file (and sometimes also the config/json file)
  • Update any of the CSS variables in the static/scss/answers-variables.scss to quickly change key colors or spacing
  • Provide any custom css in static/scss/answers.scss
  • Fork a card to customize the field mappings or parameters

We also highly recommend using solution templates to get started as you can have a working experience with a couple clicks and then you can add or remove verticals from there.

Thanks!
Liz

1 Like
3

Thanks Liz, that’s helpful!

4

For an index page, what’s the minimum that you need to fill out for Jambo to generate it? It seems like the default isn’t enough? I’m on the latest jambo/sdk in the UI.

index.json:
{
“pageTitle”: “Search”, // !!!REPLACE THIS VALUE!!! The contents of the title tag and meta open graph tag for title
// “metaDescription”: “”, // The meta tag for open graph description
// “canonicalUrl”: “”, // The link tag for canonical URL as well as the meta tag for open graph url
// “keywords”: “”, // The meta tag for keywords
“componentSettings”: {
/**
“QASubmission”: {
“entityId”: “”, // Set the ID of the entity to use for Q&A submissions, must be of entity type “Organization”
“privacyPolicyUrl”: “” // The fully qualified URL to the privacy policy
},
**/
“DirectAnswer”: {
“defaultCard”: “allfields-standard”
},
“SearchBar”: {
“placeholderText”: “Search” // The placeholder text in the answers search bar
}
},
“verticalsToConfig”: {
“Universal”: {
“isFirst”: “true”, // Indicates that this should always appear first in the navigation bar
“label”: “All” // The name of the universal tab in the navigation bar
}
}
}

5

It seems to be working now after committing the change, it just wasn’t showing in live preview

6

I’ll try to see if I can recreate it. Were you clicking Update Preview? You can also look to see if there are errors printed in the Tools > Console which are pretty helpful. Thanks for flagging this though! Let us know if we can help with anything else.