Solanasis Docs

solanasis_executive_bio_pdf_workflow_and_tooling_2026-03-19

10 min read

Solanasis Executive Bio PDF Workflow, Tooling Options, and Claude Code Automation (2026-03-19)

Executive Summary

This file captures the executive-bio-PDF and automation part of the discussion.

The main conclusion is:

  • [Assistant-stated but strongly supported by official docs and user-reported patterns] Stop relying on generic website-page-to-PDF exports as the primary workflow.
  • [Assistant-stated but strongly supported by official docs] Build a dedicated, print-first pipeline.
  • [Assistant-stated but partially verified] The best current stack for Dmitri is likely:
    1. HTML/CSS template + Playwright or Puppeteer
    2. Typst
    3. Google Docs template + Drive export
    4. PPTXGenJS + LibreOffice, if slide-style composition is desired
    5. Canva only if integration friction is acceptable

Purpose of This Document

To help another AI:

  • evaluate the tool options discussed,
  • understand what is actually verified,
  • distinguish official product capabilities from anecdotal Reddit advice,
  • and implement a repeatable executive bio PDF system for Dmitri.

Discussion Context

User-stated problem

  • [User-stated] The current workflow is hacky: taking website pages and outputting them to PDF inconsistently.
  • [User-stated] The user wants professional-looking one-page executive bio PDFs with headers/footers.
  • [User-stated] The user wants to know whether Claude Code can use Canva effectively, or whether other free / CLI / API options are better.
  • [User-stated] The user specifically wanted current sources and user-reported recommendations, including Reddit, not stale generic advice.

Key Facts and Verified Findings

Claude Code / tooling environment

HTML/CSS + browser PDF

Typst

WeasyPrint

Google Docs / Drive export

Canva

Google Workspace CLI (gws)

User-Reported / Community Findings

These items are useful signals but should be treated as anecdotal.

Major Decisions and Conclusions

1. Do not use generic webpage printing as the main workflow

  • [Assistant-stated but strongly supported by the official tool docs and user pain reported in discussion] A dedicated print route/template is preferable to printing arbitrary site pages.

Option A — Best overall

HTML/CSS template + Playwright/Puppeteer

  • Status: Assistant-stated but strongly supported by official docs
  • Why: deterministic layout control, print CSS, easy version control, and likely the cleanest fit for Claude Code’s terminal-centric workflow

Option B — Best for elegant text-first one-pagers

Typst

  • Status: Assistant-stated but strongly supported by official docs
  • Why: purpose-built document tooling, increasingly production-oriented, attractive for premium one-pagers

Option C — Best human-editable collaboration path

Google Docs + Drive export

  • Status: Assistant-stated but partially verified
  • Why: easiest non-technical manual editing path, but export size limit exists and workflow may be less deterministic

Option D — Best if deck and PDF should share a system

PPTXGenJS + LibreOffice

  • Status: Assistant-stated but unverified in this pass
  • Why: good if slide-like layouts or decks and one-pagers should be generated from similar components
  • Caveat: this workflow was discussed conceptually, but not directly re-verified with current docs in this pass

Option E — Canva

Canva template automation

  • Status: Assistant-stated but partially verified
  • Why: workable if a human-designed template and Canva integration are already in place
  • Caveat: integration friction is real; private integrations require Canva Enterprise

3. gws should be treated carefully

  • [Verified + assistant inference] gws is promising for AI-agent workflows across Docs/Drive, but because it is explicitly not an officially supported Google product, it should not be assumed stable enough for production-critical automations without validation.

Reasoning, Tradeoffs, and Why It Matters

Why HTML/CSS + headless browser is attractive

  • [Verified] The underlying browser-PDF tools support the exact kinds of controls Dmitri needs.
  • [Assistant-stated but unverified] The same source content can also be reused for the website or founder page, improving consistency across assets.

Why Typst is attractive

  • [Verified] Typst now explicitly supports automated generation use cases and accessible PDFs.
  • [Assistant-stated but unverified] It may produce more editorial / premium-feeling one-pagers with less CSS/print debugging.

Why Canva is not the best first move

  • [Verified] Canva’s integration model is real but gated.
  • [Assistant-stated but unverified] For a solo founder wanting immediate repeatability, HTML/CSS or Typst is probably faster to operationalize than building or maintaining Canva integrations.

Why Google Docs remains useful

  • [Verified] Official PDF export exists.
  • [Assistant-stated but unverified] It is still a valuable fallback or human-polish layer, even if the primary pipeline is code-based.

Recommended Playbook / Process

Use a structured source file, not one-off manually edited documents.

Suggested content model

Store fields such as:

  • name
  • title
  • positioning statement
  • 3–5 proof bullets
  • short bio
  • longer bio
  • headshot path
  • company logo path
  • contact details
  • CTA
  • optional footer text

Phase 1 — Define the content schema

Create one canonical JSON/YAML/Markdown source for Dmitri’s executive bio content.

Phase 2 — Build one premium print template

Prefer one of:

  • HTML/CSS print template
  • Typst template

Phase 3 — Export deterministically

Use:

  • Playwright/Puppeteer, or
  • Typst CLI, or
  • Docs export

Phase 4 — Reuse across channels

Generate from the same source:

  • one-page executive bio PDF
  • capability statement
  • print-friendly founder page
  • possibly marketplace profile snippets

Concrete Implementation Notes

If using HTML/CSS + Playwright/Puppeteer

  • build a dedicated executive-bio.html
  • use a print stylesheet
  • set margins intentionally
  • test both screen and print media
  • use official header/footer templates only if needed
  • keep the template purposely one-page-oriented

If using Typst

  • create one .typ template
  • pass JSON or YAML content into the generator
  • produce one PDF variant first
  • expand later to a capability statement or partner handout

If using Google Docs + gws / Drive export

  • use a fixed template doc
  • inject content carefully
  • export via Drive API or CLI
  • verify limits and auth behavior in Dmitri’s environment
  • treat the workflow as convenient, not yet guaranteed production-safe

Verified sources

User-reported sources

Risks, Caveats, and Red Flags

  • [Verified] Google Docs PDF export is capped at 10 MB.
  • [Verified] Canva private integrations require Canva Enterprise.
  • [Verified] gws is not officially supported.
  • [Assistant-stated but unverified] Browser-based PDF tooling can still be finicky if print CSS is not carefully constrained.
  • [Assistant-stated but unverified] WeasyPrint may be attractive for document-style output but can introduce Python/dependency friction depending on environment.
  • [Assistant-stated but unverified] Pptx/LibreOffice flows can work but may add unnecessary machinery for a simple one-page executive bio.

Open Questions / What Still Needs Verification

  1. What tools are already installed and permitted in Dmitri’s actual Claude Code / co-work environment?
  2. Is the priority:
    • highest visual polish,
    • easiest automation,
    • easiest manual editing,
    • or easiest reuse across docs and decks?
  3. Does Dmitri want a single-page PDF only, or a system that can also generate:
    • capability statements,
    • one-pagers for Solanasis,
    • proposal covers,
    • and lightweight decks?
  4. Are there existing Google Workspace credentials and scopes already available?
  5. Does Dmitri want to invest in Canva Enterprise or avoid that entire path?

Suggested Next Steps

  1. Choose the initial generator stack:
    • HTML/CSS + Playwright/Puppeteer, or
    • Typst
  2. Define the content schema.
  3. Build one premium one-page template.
  4. Export one executive bio PDF.
  5. Reuse the same source to create a capability statement.

Handoff Notes for Another AI

  • The user cares about repeatability and polish, not just “a PDF somehow.”
  • The user is willing to use smart technical paths if they are reliable.
  • The user is actively using Claude Code / agentic tooling and is open to CLI/API workflows.
  • The user does not want brittle hacks if a more durable pipeline exists.

Reviewer Notes and Improvements Made

Self-review performed; no reviewer agent was available.

Improvements made here:

  • verified the main official-tool claims,
  • separated official capabilities from Reddit anecdotes,
  • clarified where Canva is real but high-friction,
  • and turned the conversation into an implementation-oriented decision memo.

Appendix — Suggested Prompt for Claude Code to Build the PDF Generator

I want you to build a repeatable executive bio PDF generator for me.
 
Do not hack this by printing an arbitrary website page. I want a dedicated print-first workflow.
 
Goal:
- Generate a premium one-page executive bio PDF for Dmitri Sunshine
- Make the system reusable for future one-pagers and capability statements
- Keep the stack simple, deterministic, and easy to maintain
 
Preferred order of solutions:
1. HTML/CSS template + Playwright or Puppeteer
2. Typst
3. Google Docs template + export
4. PPTX-based flow only if there is a strong reason
 
Requirements:
- One canonical structured content source (JSON, YAML, or Markdown frontmatter)
- One reusable template
- Reliable PDF export
- Good typography and spacing
- Optional subtle header/footer treatment if useful
- Easy future reuse for additional variants
 
Content to support:
- name
- title
- positioning statement
- 3-5 outcome/proof bullets
- short bio
- contact details
- Solanasis branding
- headshot if available
 
Deliverables:
- recommended stack with rationale
- file structure
- template implementation
- PDF export script/command
- instructions for updating content
- one first-pass premium bio PDF
 
Also:
- keep it easy for an AI coding agent to maintain
- use print-friendly styling
- avoid brittle dependencies unless there is a compelling advantage
- explain tradeoffs if you choose Typst over HTML/CSS or vice versa
 
Before building, inspect the current repo/tooling environment and tell me what is already available.

Optional Appendix — Tool Decision Snapshot

OptionBest forCurrent status
HTML/CSS + Playwright/Puppeteerdeterministic print-first automationStrong recommendation
Typstpremium text-first documentsStrong recommendation
Google Docs + Drive exporthuman-editable collaborationViable fallback
PPTXGenJS + LibreOfficedeck-like compositionPossible but not first
Canva automationhuman-designed brand templates with integrationReal but friction-heavy

Graph View