The end-user manual for PageSeeder

Word Support

The support for Microsoft Word in PageSeeder is continually improving. In many ways the PageSeeder workflow allows users to create Word documents that are superior to those created in Word. 

How can that be?

Word is a powerful application that supports a range of possible solutions to any given problem. The hard part is getting users to apply these solutions consistently. When writers collaborate through PageSeeder, it is much easier to reduce the options available to users. Rather than making them less productive, constraints allow authors to focus on content. Because PageSeeder is a structured editor, validation can be used to either encourage, or mandate, consistency. This leads to disciplined, regular documents that has been validated by PageSeeder and then formatted by Word.

Because the transformation from PageSeeder to Word is managed by a developer, instead of an end user, the final document can use the most sophisticated features of Word without additional user training or risk of misuse.

Advanced Numbering

It is difficult to find a Word user that has not experienced some frustration with the numbering capabilities of Word. It is sometimes hard to convince people that Word's numbering capabilities can work correctly and predictably – but it's true.

For many scarred users, the risk that the numbering will fail at the worst possible time, leads to documents that are under-numbered, manually numbered or simply unnumbered. 

Using PageSeeder to create complex documents can change the way you think of Word. Below are screens from a PageSeeder- created Word document. It has several thousand cross references to both numbered and unnumbered objects. Using the advanced presentation options of Word's numbering, this document supports the kind of numbering used in legal contracts and legislation. This convention says references to a location “beneath” the start of the reference should not be the full address. Instead the reference should only be long enough to be unambiguous.


The numbering in this document is the result of processing PSML into a Word template to support the following capability. Because of the way it is created, users can expect this to work every time a version of this document is exported.

Created on , last edited on