← Back to Roadmap

PDF publishing

5 features

πŸ“‹ Description

PDF Publishing delivers fast, high-quality formatted outputs directly from the CCMS, enabling teams to generate professional, print-ready documents with minimal effort. With customizable templates and automated layout handling, it ensures consistent branding.

πŸ’Ž Business Value

Enables customers to create branded PDF publications from single source content, reducing production time for manuals, guides, and reports while maintaining consistent brand identity across all outputs.

πŸ—ΊοΈ Roadmap Features (1)

Specification

Origin:https://dev.azure.com/aleidotech/_git/AleidoTechCore?path=/specs/038-pdf-publishing/spec.md&version=GB038-pdf-publishing&_a=contentsMain:https://dev.azure.com/aleidotech/_git/AleidoTechCore?path=%2fspecs%2f038-pdf-publishing%2fspec.md&version=GBmain&_a=contents

βœ“ Merged to main
πŸ• Development time: 6d-01h-11m⏱ Time to deployment: 0d-00h-07m

πŸ“ Specification

πŸ“‹ Development Summary

Summary: This work establishes the Phase 1 foundation for PDF publishing, delivering the initial MVP across models, APIs, and infrastructure needed to support document generation and publishing workflows. The implementation was refined with clearer blob storage handling in PDF dispatch and expanded infrastructure support through dedicated containers for stylesheet configurations and publish jobs. Specification updates also clarified scope and deferred lower-priority styling capabilities to keep the initial delivery focused. Key Changes: - Delivered the initial PDF publishing MVP, including core models, APIs, and infrastructure components. - Added dedicated `PdfStylesheetConfigs` and `PdfPublishJobs` containers to support stylesheet management and job tracking. - Refactored PDF dispatch logic to use explicit blob storage parameters for clearer and more reliable storage integration. - Added and refined the PDF publishing feature specification, including scope clarification and removal of stylesheet file upload from Phase 1. - Resolved specification priority conflicts by deferring the no-code styling scenario to a later story. Impact: These changes provide the technical foundation for scalable PDF publishing while improving clarity in storage integration and operational job management. By tightening scope and deferring nonessential features, the team reduced delivery risk and accelerated readiness for future PDF publishing enhancements.

πŸ”§ API Changes (6 files)

  • A src/Aleido.Platform.API/Endpoints/PdfPublishingEndpoints.cs
  • M src/Aleido.Platform.API/Extensions/ServiceRegistrationExtensions.cs
  • M src/Aleido.Platform.API/Extensions/WebApplicationExtensions.cs
  • A src/Aleido.Platform.API/Models/Requests/PdfPublishingRequests.cs
  • A src/Aleido.Platform.API/Models/Responses/PdfPublishingResponses.cs
  • A src/Aleido.Platform.API/Services/PdfPublishArtifactExpiryHostedService.cs

πŸ“ Commit Log

f0f6f0805 Add PdfStylesheetConfigs and PdfPublishJobs containers 486994ea4 Refactor PDF dispatch to use explicit blob storage params aa505b5d9 Merge branch 'main' into 038-pdf-publishing 153f503ab Initial PDF publishing MVP: models, APIs, infra 3c7cc5714 Merge branch 'main' into 038-pdf-publishing 713dfe693 docs(spec-038): resolve P1/P3 priority conflict by deferring no-code styling scenario to Story 1b 8221da4d7 docs(spec-038): add FR-012 tombstone (stylesheet file upload removed) 7c93a012d feat(specs): add PDF publishing feature specification (038-pdf-publishing)

πŸ’» Development Features (4)

Recipe publishing and diagnostics

No description available

Single-object publishing and job lifecycle

No description available

Admin stylesheet and variant management

No description available

Publishing foundation and renderer infrastructure

No description available

πŸ“– Backend User Stories (1)

User stories linked from other projects

πŸ“– High-Volume PDF Publishing

Approved

## Story Statement As a publishing administrator, I want the platform to handle high-volume PDF publishing loads so that large releases complete reliably within required timelines. ## Business Value - Improves publishing throughput and release predictability. - Reduces output defects across variants and formats. - Strengthens downstream readiness with consistent publish artifacts.

View in Azure DevOps β†’