A project stores the custom settings for the groups it contains and all groups in the project have the same customizations. The project template is the set of files used for these custom settings.
They include:
Templates are generally additive and apply from most specific first to least specific – the project template extends the global template which extends the default template.
The effective project template is the collection of all the files that are taken into account in the project when you include the default and global template.
To compute the effective template, PageSeeder includes the files from all the applicable templates (default, global and the local project). If some configuration files have the same name and path, the file from the most specific template takes precedence.
Avoid overriding the built-in document types (default, help, and references) in the default project template. It makes it harder to explain the behavior to end-users and might have some unexpected side-effects. Extending them, by adding a Schematron or custom styles is generally okay.
Labels are used in many contexts within a project. Use the project labels page, to configure labels.
PageSeeder doesn’t define any default labels – the labels configuration in the default template is empty. Use the global template to define labels to use everywhere in PageSeeder.
If you define both global template labels and a project template labels, the project template labels override the global template labels.
Email templates let you change the content, wording, and style of the emails sent by PageSeeder. Use the email templates page, to make changes and test the modifications.
If you only need to customize the branding of your emails (logo, color scheme, styles, footer or domain), use the organization configuration.
If the project template is the global template, then PageSeeder uses these email templates instead of the default ones.
The publish scripts page lets you define publish, export and import actions.
The publish scripts page only shows scripts defined in the current project template, not the global or default templates.
The template configuration includes:
If you’re an administrator, you can view and manage the template files directly.
If you add a new document type for the project, PageSeeder automatically creates a folder and any related required file, and prefills them with sample content to quick start the process.
For example, if you change the labels, we also create a label folder and the label-config.xml file with the labels for that project.
The PageSeeder user manual
© Allette Systems (Australia)