Skip to Content

Spaces and Community Topic Pages

Spaces are going away in the new platform. Content will no longer be bound to a “space” but will be searchable through metadata instead. When you write a question or create a blog, you will not need to assign that content to a space. You will just need to pick an appropriate tag for that content instead.

The new landscape will help us to eliminate the sense of many individual communities built around inflexible spaces and move to a single community experience that supports the most relevant topics with user-generated content -- sometimes referred to as “UGC.”

In place of spaces, we'll have community topic pages to provide a quick, consolidated view of dynamically fed, user-generated content related to a specific topic. It's important to note that not all spaces will become a community topic page.

Community topic pages will replace some existing space overview pages but there will not be a one-to-one shift of space overview pages to topic pages. We conducted an analysis of relevant, active Jive spaces as a way to provide continuity in terms of user experience and expectation. As a result of that analysis and an alignment with the SAP product portfolio and 1DX metadata model, community topic pages were selected. Current spaces that did not get selected will either be consolidated with other related topics or discontinued.

The benefits of moving from spaces to community topic pages

The consolidation of spaces based on the SAP product portfolio and overall alignment with 1DX metadata will help users find and focus on content related to the most relevant topics. Page editors will be able to feature content and links, but automated feeds of user-generated content will surface the most recent activity on a community topic page without the need for editors to place content manually.

This user-generated content will not be limited to a single community topic page -- as this content is not confined to a single space. The tagging schema will allow user-generated content to be easily fed to multiple topic pages based on how the user tags the content.

How tagging works in the new community

In the new community tagging model, managed tags allow users to align their content (e.g., blogs and Q&A) with the related topic(s). All managed tags are defined according to the 1DX metadata schema.

When users click “Create” from the future UI, like today, they will be presented with an interface in which they put in content and metadata, but with an intuitive UI that enables easy tagging.

Users must select a single managed tag, called a “primary tag,” to designate the main subject matter of their content. They may select additional managed tags as well.

User-generated tags are also permitted to provide an additional layer of content categorization.

In either case, tags will be suggested by type-ahead functionality, and users will be able to create their own user tags.

Content will aggregate around both types of tags. In other words, users will be able to see content when they click on either type of tag, although there may be more to display around the managed tags.

Users may only choose a single primary tag (and they must choose one before publishing), but they can enter as many additional tags as they want.

For more on spaces vs. tags, take a look at these blogs:






Back to top