Authoring - About smartcontent

With HelpServer, you have a unique approach to supporting dynamic content and ensuring that tailored information reaches your targeted audience. There is no need to write scripts or to develop programming skills. Instead, the dynamic character of the content relies on conditions you define in the system. These can be based on events and behavior in your organization's processes or on the roles, the preferences, or the experience people have in your company.

Once the conditions are defined, you apply these as markers to different areas of your content or you split up a topic into dynamic chunks of information. You can even use tags in a topic to mark words, sentences, or paragraphs that need to be displayed or printed conditionally. This is the way to produce multiple results from one source.

HelpServer keeps all the chunks of content nicely together in its Workbench, which greatly facilitates maintenance and translation.

When your users browse the content, HelpServer checks the conditions against their profile, the occurrence of predefined events, or variable/value pairs entered in the URL or provided by an exit routine. Next, the server dynamically compiles the chunks of content in function of the conditions. Thus, people can browse, export, or print tailored content without having to hunt for it.

With this feature your authors do not require any technical skills. So, there is no downtime waiting for scriptwriters to get the job done. Anyone with basic word processing skills can create dynamic content. Armed with the ability to easily deploy content in the user's own language, authors can now focus on content creation instead of on management and formatting activities.

HelpServer's Smartcontent feature is a mean to support preferred content for your user community. It is not a mean to secure the content, though. To effectively and easily secure content for people with different needs it is recommended to acquire HelpServer's extended security feature.

Implementing and using Smartcontent includes the following steps.

Creating the conditions.


Creating the dynamic content.


Actuating the conditions.


Enter HelpServer, a multi-platform solution to manage enterprise content and online user assistance on the web.

With the HelpServer Workbench, teams of authors can create structured content as reusable and shareable objects. This enables them to keep up with the explosion of information and make projects easy to maintain. These projects can support content management, document and file management as well as context-sensitive help for web and desktop applications.

Authors are able to collaborate on projects even when they are geographically dispersed. They can activate new content and changes to existing content by means of a click.

People all over the world can then access that content in real time over the Internet. The HelpServer server engine dynamically delivers the most relevant information based on the user's specific needs.


HelpServer supports multiple languages at the topic level, so authors and translators can create content for multiple languages in a single project. The Workbench keeps all the translated topics tightly together to facilitate maintenance.

You can extract entire projects or specific topics from the HelpServer platform and then pass them to language suppliers or to translators. As soon as the translations are finished, you can import them into HelpServer’s workflow.

HelpServer supports Unicode language characters and double-byte Asian languages and Eastern European languages.


Providing information in different languages is one of the most important ways to enhance the usability of help and documentation systems. In HelpServer, this feature is unmatched.

In HelpServer people can maintain their own profile and select one or more languages. Once you’ve done the translation, your users will see the content in their own language.

Documents may combine globalized content with content in a ‘fall back’ language, such as English. If a content object is not available in a specific language, then it is automatically replaced by its generic counterpart.


As more and more information becomes available on the web, securing that data becomes increasingly important. And when it comes to getting watertight security, each company will have its own requirements.

In HelpServer, you can distinguish public from private content. HelpServer's basic security mechanism protects the private content, so visitors will not be aware of it. If you also have defined specific user accounts, your visitors can still choose to log on and access the private content.

The basic security mechanism can handle a common security profile for the entire content collection. In environments where different people have access to the content, different parts of the content might require an individual security setup. In that case, setting up and maintaining security can become a burden for your business, so that's where HelpServer's extended security feature comes in.

With this feature you can handle multiple security profiles which are needed to control the access to content by different kinds of user communities and/or authors. Each security profile grants the required permissions to the user accounts and is attached to a specific project or a subset of the content objects. The result is a security model that becomes transparent for you and thus easier to maintain and to extend.

Furthermore, the extended security supports features such as smartcontent and notification.


 About HelpServer
 Starting up and logging on
 The basic working principles
 Using the content in help and documentation systems
 Formatting the content
 Searching and replacing text
 Reusing content with shares
 Navigating with hyperlinks
 Navigating with pointerpaths
 Using bookmarks and jumps
 Duplicating content with clones
 Using tables
 Including media files
 Navigating to web pages
 Using embedded chunks
 Including html code
 Navigating with menus
 Using snippets
 Spelling checking
 Using the view mode
 Creating an index
 Creating a FAQ
 Creating a glossary
 Team authoring
 Working with projects
 Setting up structured authoring
 Generating file based output
 Creating printed output
 Importing files and folders
 Loading files in the project gallery
 Converting legacy content
 Including legacy content in real time
 Transferring objects between installations
 About smartcontent
 Creating the conditions
 Creating the dynamic content
 Actuating the conditions
 Testing the profile based smartcontent
 Use cases
 Customizing the look and feel
 User accounts
 Working with templates
 Working with metadata
 Workflow management
 Using event exits
 Appendix A: The URL parameters
 Appendix B: The object indicators
 Appendix C: Play Javascript