The Input Navigator epic provides a governed interface for staging, parsing, and inspecting uploaded files in the context of a Work Package. It ensures each eligible upload is converted into a traceable input object, enriched with context-governed insights, and made available for visual inspection while preserving a durable record at work package completion. This capability delivers a consistent, auditable source set that downstream processes can reliably use for analysis, reuse, and compliance.
The draft creator saves time by automatically create a first draft based on the context given and defined by the user. Allows for side-by-side view to enable verification.
The migration analyser provides KPIs and guidance for migration approach and efforts. It supports the migration process through identifying and comparing information structures and provide a plan for what parts can be automatically migrated and what parts needs human interaction.
The Integrated Editor provides a seamless, intuitive authoring experience directly within the CCMS, allowing creators to write, structure, and refine content without switching tools.
Business Value
Streamlines workflows and improves author productivity by eliminating tool switching and complexity. Customers do not need to install and manage their own editor, reducing infrastructure costs and administrative overhead.
Analytics and Business Intelligence provides insights into the content production. By visualizing trends, identifying bottlenecks, and highlighting opportunities for improvement.
Business Value
Enables data-driven decision-making—helping organizations optimize their content strategy, governance, and resource allocation.
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.
Deliver the Reuse Analyser as a user-facing AI tool that helps information analysts explore and understand reuse potential across repository content through a clear, responsive interface in the Aleido Platform. The frontend should present analysis results in the established workspace and panel patterns, support loading, empty, and error states consistently, and integrate with the platform API through shared hooks and store-managed state so users can refine context and review findings without losing navigation state. The experience should make repository-wide analysis understandable and actionable with accessible result presentation, progressive feedback while AI processing runs, and resilient error handling for failed or partial responses.
This epic brings Work Package Context into the frontend as a persistent, version-aware experience that lets users see, understand, and maintain the shared context a work package depends on throughout its lifecycle. In the UI, that means exposing context in the relevant workspace views and panels with clear loading, empty, error, and version states, so both human users and AI-assisted workflows can reliably work from the same current and traceable information. The frontend should manage this through shared hooks and store-backed state integrated with the platform API, including refresh and real-time update handling where available, while keeping edits and saves understandable and resilient through consistent feedback and error handling. The result should make context feel visible, trustworthy, and continuously up to date without breaking existing authoring and delivery flows.
The Integrated Editor brings authoring directly into the Authoring workspace so users can create, structure, and refine content in a single, uninterrupted UI flow instead of switching to external tools. On the frontend, this means embedding the editor into the existing panel and perspective patterns, with clear save, loading, and unsaved-change states, and integrating editor actions with the platform API through shared hooks and store-managed workspace state. The experience should feel responsive and reliable across web and desktop, using consistent error handling, recovery messaging, and real-time updates where platform data changes affect the current editing session. This delivers the
Business Value
by reducing friction for authors while removing the need for customers to deploy and maintain a separate editor environment.
Release Manager on the frontend gives users a dedicated workspace to review incoming content, understand how it aligns to recipe-based product structures, and control what is released to which external targets. The experience should make release scope, target channels and markets, and release status visible through clear panels, lists, and detail views, with state managed consistently across navigation, filtering, selection, and API-backed actions. Frontend implementation should integrate tightly with platform release APIs to support responsive feedback, optimistic updates where safe, and robust error handling for failed validations or delivery actions. This enables users to move from publication-focused delivery to product-focused delivery with greater confidence, traceability, and less manual effort.