Skip to content

Instantly share code, notes, and snippets.

@sholsinger
Last active July 31, 2023 03:13
Show Gist options
  • Star 10 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save sholsinger/3ff2b30bb43e4b90929f19fc7136a7be to your computer and use it in GitHub Desktop.
Save sholsinger/3ff2b30bb43e4b90929f19fc7136a7be to your computer and use it in GitHub Desktop.
SFCC B2C Documentation as a Search Engine in your Browser

How to easily look up things in the SFCC B2C Docs from your URL bar

This guide is intended for use with Chrome, but this feature exists in several browsers. It will walk you through adding a cusom SFCC B2C search engine shortcut to your Chrome profile.

Updated 2023-07-30

Setup

Step 1 In Chrome, go to Settings > Search engine > Manage search engines (Or just navigate to: chrome://settings/searchEngines)

Step 2 Click the "Add" button.

Step 3 Enter the details:

Search engine: SFCC B2C Documentation

Keyword: sfcc (or whatever you want the trigger to be)

URL with %s in place of query: https://help.salesforce.com/s/search-result?language=en_US#q=cc.b2c%20%s&t=allResultsTab&sort=relevancy&f:@sflanguage=[en_US]

Note: The above prefixes all searches with cc.b2c which appears to be an ID prefix used in the pages that were migrated from the old infocenter and gives reasonably good filtration of content. Without that, it's extremely difficult to determine what is relevant to B2C Commerce.

Step 4 Click the "Add" button at the bottom of the form to save.

Step 5 Test it out. Click into your URL bar or use Cmd+L/Ctrl+L. Type your keyword and then press the 'Tab' key. eg:

sfcc<tab>

You'll see the URL bar switch to show the name of the search engine and then you can type your query and press enter. If you enter job step import and hit enter, then you should end up seeing a URL like this be loaded in that tab:

https://help.salesforce.com/s/search-result?language=en_US#q=cc.b2c%20job+step+import&t=allResultsTab&sort=relevancy&f:@sflanguage=[en_US]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment