I’m curious how Companion handles spaces that have multiple subdomains or folders/pages within the same domain, because I can’t quite figure out how it works.
I’m experimenting with Companion and setting up spaces. One of the things I am trying to do is specify what content is visible for specific areas of a website that is used regularly. This means that I have set up separate spaces for subdomains and folders, however they seem to be overridden by the highest level.
Let’s use Docebo instances as an example:
- Homepages are likely yoururl.docebosaas.com/pages
- learning content is yoururl.docebosaas.com/learn
- Admin screens have their own subfolders
- API browser is yoururl.docebosaas.com/api-browser
I was attempting to set up the following:
- general “how to navigate” courses for most pages yoururl.docebosaas.com/*
- API-scpecific training linked to the API page: yoururl.docebosaas.com/api-browser/*
What I found was:
- general content successfully appeared across all subfolders ( …/pages, …/setup, …/pages, etc)
- API specific training never appeared...but neither did the general items.
- When I tried to set up a different space for …/pages or …/learn to see what would trigger different content, the content available either defaulted to the general training, or displayed the general “keep learning” page with no content.
This would also be true for Sharepoints or Intranet usage for many companies. If there is a complex setup, then setting up enough spaces could be very tedious and prohibitive, especially since it is possible that duplicate spaces may be needed. In my mind, the wildcard URLs should be a fallback so that the …/pages is triggered first and then falls back to docebosaas.com/* if no sub-page is visited.
What is your experience with this part of the tool? Do you have any best practices?
