A-Z glossary of PageSeeder concepts


A fundamental capability of PageSeeder, comments are a class of XLink that can be attached to different locations in the data or system. Because commenting is so integral to PageSeeder's architecture, understanding how they work can help to explain the broader concepts.

Comments can be attached to:

A task is simply a comment with additional properties, such as status or due date. There are different parts of the user interface that allow existing comments to be edited so that they may become tasks.

Groups can be configured so that comments can be posted by:

When a group is open to the public, comments are typically moderated. This means they are first routed to a moderator who can delete the comment, edit or move it, before releasing it to the group.

PageSeeder generates a unique comment ID for every comment. This ID is a useful reference when tasks are significant to external systems such as software code. This allows PageSeeder to function as an issue tracker such as Jira or Bugzilla.

Posting a comment without it being broadcast

Every review group has an email address. This address is comprised of the group name plus the server name. (e.g. <> where <demo-project> is the group and <> is the PageSeeder server.

If a member would like to simply lodge a comment with the review group but not have it redirected to all the group members, simply insert "--silent" just before the "@" symbol. (e.g. <>)

To accomplish the same result when posting from a web form simply un-check the box next to "This comment will be emailed..." (this option requires special access rights).

To accomplish the same result using the Acrobat Commenting Tools insert "silent: " at the start of the first line of the comment content.

Created on , last edited on