This document explains the use case and approach for embedding KB content into an external (i.e. non-KB) website or web-based application that your organization manages.
Your organization or unit maintains one or more websites outside of the KnowledgeBase, and you would like to display some your KB content there as well.
Your organization or unit develops one or more web-based applications, and you would like to embed "how-to" or other supplemental information directly within the application.
While this can seem like the easiest option, copying and pasting information from your KB into another website results in the duplication of content. While this doesn't necessarily cause a problem in the short-term, it will create extra work in the future, and worse, could lead to conflicting information.
When the published information inevitably needs to be updated, someone will need to manually update it in both places. This could play out in a few ways, some of which are worse than others, and none of which are ideal:
Doing this also helps ensure that the information you wish to provide to your end users is readily available to them in the appropriate contexts. If you believe someone may need to see a policy directly associated with information on your website, you don't have to send them somewhere else to find it. In the case of a web-based application, you can surface relevant help information at the exact moment it is needed.
The great part about embedding content using our API is that only the content itself gets delivered. This means that the actual appearance of the content (for example, the font being used, link styling, etc) will match that of the website where you are embedding it.
The only exception to this is if your document contains inline CSS for styling, as that will be present in the body of the document. This can be used to your advantage, or removed if it is causing problems.
To see an example of this in action, open the following webpage in your browser: My Official Service Website