You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
Currently we support previewing articles in a single context using a single scheme which is not well suited for multiple communities and/or multiple community types.
Domains can be configured on a community by community basis and they can also be shared. When they are shared, the site 'pathprefix' setting is used to separate them.
That said, there is always a 'subdomain' configured for each site/community that works on *.force.com.
The customer may also want to maintain the option of previewing the article in their standard Salesforce instances:
{instanceUrl}/{articleId}
Some customers might be interested in providing their own preview URL if they deliver content to a separate application or platform. This seems like a less critical issue to solve.
The text was updated successfully, but these errors were encountered:
Currently we support previewing articles in a single context using a single scheme which is not well suited for multiple communities and/or multiple community types.
Domains can be configured on a community by community basis and they can also be shared. When they are shared, the site 'pathprefix' setting is used to separate them.
For example:
Article URLs for these communities might be:
For a sandbox this might look like:
Completely custom domains can also be used:
That said, there is always a 'subdomain' configured for each site/community that works on *.force.com.
The customer may also want to maintain the option of previewing the article in their standard Salesforce instances:
Some customers might be interested in providing their own preview URL if they deliver content to a separate application or platform. This seems like a less critical issue to solve.
The text was updated successfully, but these errors were encountered: