What is conditional content
- RoboHelp User Guide
- What's new in RoboHelp (2020 Release) Update 1
- What's New in Adobe RoboHelp?
- What's new in RoboHelp (2020 Release) Update 8
- What's new in RoboHelp (2020 Release) Update 7
- What's new in RoboHelp (2020 Release) Update 6
- RoboHelp system requirements
- Download RoboHelp on Windows and macOS
- RoboHelp FAQs
- Download and install your Adobe app
- Get to know the RoboHelp workspace
- Fixed issues in RoboHelp
- Collaborate with authors
- PDF Layout
- Editing and formatting
- Format your content
- Create and manage cross-references
- Create and manage links
- Single-source with snippets
- Work with images and multimedia
- Create and use variables for easy updates
- Work with Variable Sets
- Use Find and Replace
- Auto save your content
- Side-by-side editing in Split View
- Use the Spell Check feature
- Create and Edit Bookmarks
- Insert and update fields
- Switch between multiple views
- Autonumbering in CSS
- Import and linking
- TOCs, indexes, and glossaries
- Conditional content
- Review and Collaboration
- Generating output
- Publish output
Understand the basics of conditional content and its use cases for output based on roles, output format, expertise levels, and locales.
Conditional content helps organizations to single-source content efficiently to address various documentation purposes and audience needs. In Adobe RoboHelp, you implement conditional content by applying condition tags to your content. Condition tags enable you to generate output with content variations.
Additionally, tag groups help you group multiple related condition tags to provide relevant content to a focus group. You can use tag groups such as audience, platform, product, properties, and other custom groups. For example, use the audience group to provide targetted content to developers, administrators, and so on. Use the platform group to target operating system-related information to appropriate users, such as system requirements for Windows and Mac.
Common use cases
In RoboHelp, you can use condition tags to generate subsets of content from your project as needed. This way, you need not create multiple projects for different output types.
Here are some common scenarios in which you can use condition tags effectively:
- Customize content for output formats
Online documentation often contains elements that are not useful in a printed manual. You can mark these elements using a condition tag, for example, online-only, and exclude them from the printed manual. Alternatively, if your manual is a subset of your online documentation, you can apply a different condition tag, for example, print-only, to the topics and topic content that you want to include in the printed manual. When you generate your project, you can use the print-only or online-only tag as required.
- Target custom content for specific audiences
Sometimes, topics are specific to products, experience levels, or types of users. Using condition tags, you can target such topics for the right audience. This way, the content that an audience receives is relevant and clutter-free. For example, beginners get the content that’s relevant for them and their consumption experience is not suboptimized because of notes and tips that are relevant for advanced users.
- Filter published content based on relevance
Sometimes, all published content may not be relevant to a set of your audience. Using dynamic content filters, you can provide your audience the ability to filter out irrelevant content from the output. For example, in a multi-locale travelogue, users can quickly filter content for specific locales, instead of having to read through or search the entire travelogue.
The end-to-end implementation of conditional content involves performing steps in both authoring and publishing workflows. Also, you can optimize and manage your conditional content.
Optimize and manage conditional content
Prihláste sa do svojho účtu
Rýchle odkazyZobraziť všetky vaše plány Spravujte svoje plány