Workflow · Data and web
Database, server and web integration. So catalogs come straight from product data, exports run without a click, and people who don't work in InDesign can still plan, brief and approve.
The page database, server export and web portals can be commissioned separately or joined into one workflow.
A page database with a REST API, searchable, with change history, roles and permissions. Excel, ERP and pricing data can be connected.
Saved pages are output automatically as PDFs and preview images. A queue works through the jobs and the status shows on a dashboard. For standard cases we're developing D7server as a ready-made product.
A page gallery, drag-and-drop page planning, briefing forms and approval in the browser.
Example scenario
Product data from Excel or an ERP is placed on pages by hand and transferred into the layout.
Data from Excel or your ERP is read in, pages are allocated and layouts prepared, with page management and online approval included.
Building block: Page database with a REST API
Example scenario
Designers export every page on its own and report the status by email.
A service on InDesign Server exports every saved page as a PDF and preview image and reports its status to a dashboard.
Building block: InDesign Server export
Example scenario
Anyone who wants the current state of a page asks the design team.
Every current page is searchable in the browser, filterable by item number, with change history.
Building block: Web portals
Example scenario
Briefings arrive as email or a spreadsheet, and texts and tables are typed in again.
Product managers fill in an online briefing, and the plugin builds the text, size table and icons straight into InDesign.
Building block: Web portals
Example scenario
Page allocation lives in an Excel list that keeps being redistributed.
Products are placed on pages in the browser, and the result is ready for layout right away.
Building block: Web portals
On an intro call we'll clarify the next steps.