In our Document360 project, we have several workspaces.

Maintaining the different workspaces and related site customizations is quite cumbersome.

• Each workspace has its own ‘Home’ site, which can be turned off.

• One workspace is the ‘main’ workspace.

• Each workspace has its own ‘Site header & footer’ settings.

• etc.

Issues:

This setup causes several issues. For example:

• Set up ‘Site header & footer’ separately for each workspace. Running the risk of inconsistencies.

• Breadcrumbs are not project based (generic).

o Breadcrumb ‘Home’ icon leads to the workspace ‘Home’ instead of a project ‘Home’.

o When workspace ‘Home’ is switch off, no home icon is shown in breadcrumbs, breaking the navigation.

o There’s a ‘Documentation’ part in the breadcrumbs, that should show the workspace name.

Solution:

To solve this, an architectural change is required for the Document360 platform.

The solution for this would be to introduce a project ‘Home’.

Benefits would, for example, be:

• One site setup (headers, footers, etc.) that can be inherited by the project workspaces. (You can still keep the workspace-specific site setup, but make it by default inherit the project site setup)

• Project-based breadcrumbs:

o ‘Home’ icon always can be shown and navigates to the project Home.

o Workspace names can be shown in the breadcrumbs.

• Improved ‘workspace’ switch in the published sites.

• More flexibility (less restrictions) in the documentation web site setup.

• No need to mark one workspace as ‘Main’, with all related technical consequences and limitations.