Audience Profiling
Use Cases
Consider profiling your content with the audience attribute in the following scenarios:
- Your customers use the same product but have different features enabled. This way, each customer can get personalized documentation that covers only relevant features.
- You want to provide content that applies to different roles in your product. For example, users with Administrator roles may need system configuration information, but users with Reviewer role do not.
- You want to include internal-only content in the documentation set. You can hide internal content from customer-facing deliverables and include it in internal documents.Tip: You can use internal content in your documentation to provide test-related information for your quality assurance (QA) team or restricted information for your technicians.
Audience Profiling Example
By default, all content is included in published deliverables, unless you have applied conditional processing (profiling).
This example shows an internal step element (3). The step is not a part of the customer-facing documentation.
This example shows internal step result elements. This way, the profiled elements are a part of the internal documentation for the quality assurance team but are not visible in customer-facing documentation.
This example shows an internal reference topic. The “Reference A” topic appears in the internal documentation for the field engineers but does not appear in the customer-facing documentation.
This example shows a DITAVAL that excludes internal content in the customer-facing output.