Marketing Asset Document Pipeline Evaluation (2026)
Status: Active
Audience: Platform, Sales Engineering, GTM, Design
Primary goal: Standardize how Brainforge turns source-first markdown and structured copy into branded one-pagers and multi-page PDFs without introducing unnecessary authoring overhead.
Summary
Brainforge already has strong markdown-based asset inputs in knowledge/sales/marketing-assets/ and a distribution surface in the Platform marketing asset browser. What is missing is a clear, reusable generation pipeline between those two layers.
This initiative evaluates a small set of architectures for turning source copy into polished one-pagers and multi-page PDFs while staying compatible with current Brainforge workflows.
An important constraint is that the current visual source of truth lives in Figma. The repo stores source copy and distribution references, but the final composed layouts were originally designed in the Sales Assets Figma file and exported from there.
Why This Exists
- Sales and GTM already create design-ready markdown assets.
- The Platform already catalogs and serves files from
brainforge-files. - The missing layer is repeatable rendering, export, and publishing.
- There are many viable document-generation stacks; this work narrows them to a Brainforge-specific shortlist.
Documents In This Folder
- research-memo.md - Current-state findings, repo references, external research, and OSS landscape.
- architecture-evaluation.md - Shortlist of architectures to test and Brainforge-specific evaluation criteria.
- figma-layout-notes.md - Figma inventory, reusable component patterns, and print-layout constraints.
- implementation-spike-plan.md - Concrete first implementation scope, fixture mapping, component inventory, and verification plan.
- progress-log.md - Running log of research, decisions, and next steps.
Working Recommendation
Start from a source-first pipeline:
- Author in markdown or structured copy.
- Transform into branded HTML using reusable templates.
- Render PDF server-side.
- Publish outputs into the existing asset distribution flow.
The leading baseline to test first is markdown/structured content -> HTML template -> server-side Chromium render, with print-layout tooling layered in only if multi-page polish requires it.
The important refinement from the Figma review is that the template layer should be asset-family-specific and fixed-layout, not a single flowing markdown-to-print template.
The current Spike 1 scope now covers four fixtures so the first renderer is validated across the asset families Brainforge most plausibly needs first:
- one-pager
- service two-pager
- comparison / recommendation asset
- proof-oriented case study
Success Criteria
- One-pagers can be generated from existing markdown source docs with minimal manual cleanup.
- Multi-page PDFs have reliable pagination, headers/footers, and brand consistency.
- Generated layouts are recognizably aligned with the current Figma print system.
- The pipeline fits Brainforge’s current repo and Platform distribution model.
- Design and GTM teams do not need to learn a separate document language unless there is a clear payoff.
Key References
- Platform catalog UI:
apps/platform/src/app/(main)/marketing-assets/page.tsx - GitHub file loader:
apps/platform/src/lib/githubApi.ts - GTM asset hub:
knowledge/sales/marketing-assets/README.md - Design-ready copy examples:
knowledge/sales/marketing-assets/design-ready-copy/ - One-pager prompt:
knowledge/sales/agents/prompts/service-asset-prompts/one-pager-prompt.md - Figma visual source:
Sales Assets(https://www.figma.com/design/mKTpR46wYleYtLKF0qciSc/Sales-Assets)
Last updated: 2026-04-16