Field notes
Technical writing on native files, document quality and integration.
Loading field notes…
Technical writing on native files, document quality and integration.
A result-envelope pattern for document APIs that keeps execution failures, fidelity losses, output identity and release evidence apart.
Integration · 8 min readWhy a document API must separate the operations it can describe from the operations its runtime can execute.
Delivery architecture · 10 min readAn engineering checklist for electronic documents in services covered by the European Accessibility Act, with scope and test limits.
Delivery architecture · 8 min readCompare SheetJS, ExcelJS and Runstamp for XLSX in Node.js: parsing, styled reports, native charts and multi-format output.
Integration · 9 min readCreate native Excel chart objects from a typed JSON workbook model, validate the result, and decide when to update an existing workbook instead.
Delivery architecture · 9 min readBuild a Next.js PDF endpoint with input validation, the Node.js runtime, typed Runstamp results, download headers and error handling.
Delivery architecture · 9 min readCompare direct PDF generation, a managed browser and self-hosted Puppeteer by layout needs, runtime limits and output checks.
Delivery architecture · 6 min readInstall the SDK, run a local or managed document operation, handle typed results and keep format input contracts explicit.
Delivery architecture · 8 min readReproduce pdfmake table overflow and row-span page breaks, pick a bounded workaround, and add output checks before release.
Delivery architecture · 10 min readCompare four JavaScript PDF approaches by layout model, runtime, evidence and operating responsibility.
Integration · 12 min readAnalysis of the two three-tool discovery paths in Runstamp's MCP server: operations and reusable Document Jobs.
Integration · 13 min readA canonical architecture for turning model output into editable files: typed intent, validation, normalization, rendering and evidence.
Integration · 9 min readWhere Google Slides API latency comes from, why it hurts in production, and when the API is still the right choice.
Output quality · 9 min readGamma API vs Runstamp on PPTX export quality, native editability, brand control, deployment and embedding rights.
Output quality · 8 min readCompare python-pptx and Runstamp for AI agents that generate editable decks: JSON contracts, validation and deployment.
Integration · 12 min readCompare PowerPoint generation tools for 2026: PptxGenJS, python-pptx, Aspose.Slides, Google Slides API, SlideSpeak, Gamma and Runstamp.
Output quality · 14 min readA PowerPoint repair error is a symptom, not one error code. Keep the original file, then check the package, XML, identifiers, charts and media in order.
Output quality · 5 min readCreate a native PowerPoint file from validated JSON in Node.js with the Runstamp SDK.
Output quality · 7 min readPptxGenJS gotchas that silently corrupt PowerPoint output: mutated option objects, combo-chart repair dialogs, uppercase image paths and fixes.
Delivery architecture · 12 min readCompare JavaScript document libraries for 2026: PptxGenJS, pdfmake, ExcelJS, docx, jsPDF, react-pdf, Carbone, docxtemplater and Runstamp.
Output quality · 9 min readTyped slide JSON, validation, chart data and a clean handoff to native PPTX generation.