Skip to main content

Overview

AccPacks and Skeleton Projects are grouped by what they do. Each category covers a distinct part of a priint:suite project. Most projects use AccPacks from more than one category.

Don't know where to start?​

We have accelerating packs that could come in handy in many different project situations. AccPacks are optional, modular extensions. Each one targets a specific use case. Install only the ones that fit your project.

The Consistent Demo System bundles several AccPacks in a working environment based on the Baroque 'N' Heart demo scenario. It is useful for exploring AccPacks hands-on, running demos, and as a starting point for small projects. The demo contains sample data and an Excel import profile already included.

Data Integration​

Before content can appear in a document, it needs to be in the system. This category covers getting data in and out of priint:suite: file-based imports, entity exports, and connections to external content systems.

  • Data Import: Configurable import of CSV and Excel files into PublishingHubDB or MuaDB. Supports transformation, validation, and scheduled hotfolder processing.
  • Entity Data Export: Export entity data as a structured deployment package.
  • Content System Connectors: Pre-configured RestConnector setups for ContentServ, Akeneo, Informatica, Perfion, Stibo, and Syndigo. Available on request.

Placeholders​

Placeholders are the link between data and the InDesign frame. This category covers the AccPacks that handle what goes into a frame: attributes, images, text, document parameters, and table structures built from child buckets.

  • Generic Placeholder: Covers 80% of placeholder use cases. Handles text, attributes, media assets, document parameters, and more.
  • Table Placeholder: Rule-based selection of child buckets and attributes for table creation. Configurable styles, merging rules, and attribute mapping.

Layout & Templates​

Once you know what goes into a frame, you need to control where frames sit on the page and how they adapt to content. This category covers the scripting libraries and utilities that handle frame positioning, sizing, and page-level layout logic.

  • Dynamic Templating: Utility methods for Grid Planning. Supports RealGridElements, merging grids, and dynamic frame placement based on layout rules and conditions.
  • Page Layout: Reusable Python layout rules and conditions. Covers frame sizing, layer assignment, table styling, and masterpage switching.
  • Index Tabs: Tab-based index layouts for publications with alphabetical or category dividers.

Planning & Rendering​

This category covers the automation between planning and output. It handles which products end up in a publication and how rendering is triggered without manual steps in the planner.

  • Product List by Rule: Rule-based product selection for buildup scripts. Traverses planning trees to determine which products go to the rendering service.

Output & Delivery​

After rendering, documents need to go somewhere. This category covers delivery to external systems and sending notifications as part of a workflow.

  • Upload to FTP: Upload files to an FTP server. Includes support for Cominto Blätterkatalog integration.
  • HTML Emails: Store HTML templates, fill placeholders, and send emails as part of a Camunda process.