A good Salesforce document-generation design starts with the business process, not the PDF button.
What this means
Identify who initiates generation, which records supply data, how templates are governed, whether users choose among templates, what automation is required, where files are stored, how documents are delivered, and which accessibility/security requirements apply.
1. Map the document
List output types, recipients, data sources, and ownership.
2. Design templates
Separate reusable layout from dynamic record data and conditional content.
3. Choose invocation patterns
Decide between user-driven, Flow, batch, Apex, or Agentforce generation.
4. Plan storage and delivery
Define retention, Salesforce Files behavior, email, and downstream workflows.
Where Gutenburg fits
Gutenburg is a Salesforce-native PDF generation product built around reusable templates, Salesforce data, automation, and accessible PDF output. Use the interactive demo to see the product experience and the documentation for exact configuration steps.