Inline Profiling on the frontend will let authors mark and manage conditional text directly inside the editor so they can see, edit, and understand profiled content in context without leaving the authoring workflow. The experience should fit naturally into the existing authoring layout, using editor affordances and contextual panels where needed, while keeping profiling state in sync with platform APIs and workspace permissions. The UI should clearly communicate applied conditions, loading and save states, and validation or failure cases through the platform’s standard state management and error-handling patterns. This delivers the same
Business Value
of producing multiple targeted outputs from a single source while reducing duplicate content and making audience-specific authoring easier and more reliable.
Input Navigator on the frontend gives users a clear Work Package experience for uploading eligible files, tracking their staging and parsing status, and inspecting the resulting input objects in context before completion. In the Authoring workspace, this should surface as governed panels and views that let users move from file selection to visual inspection with responsive loading, unified error handling, and state that stays in sync with platform API processing and real-time updates where available. The UI should make traceability visible by preserving the relationship between the original upload, derived input object, and any context-governed insights, while handling partial, failed, and completed states in a way that is auditable and understandable to the user. At Work Package completion, the frontend must present the finalized source set as a durable, inspectable record that downstream analysis and compliance workflows can rely on.
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.
Translation Management on the frontend should give users a clear, end-to-end localization experience inside the authoring workspace, where they can prepare content for translation, send it, monitor status, and bring translated variants back into the correct language context with minimal manual effort. The UI should surface translation actions and progress in the relevant object and language workflows, using the existing panel and dialog patterns, permission-aware controls, and shared state/hooks to keep status current as platform API data changes. The experience should handle loading, partial failures, and reintegration errors gracefully through consistent notifications and error boundaries, while keeping the workflow understandable across both web and desktop clients. This epic delivers the user-facing layer that makes centralized translation management visible, actionable, and efficient for global content teams.
Component Reuse for the frontend should make reusable content elements discoverable and easy to apply within the Authoring experience, so authors can select, insert, and manage shared components without leaving their normal workflow. The UI should fit naturally into the existing panel and perspective patterns, with clear loading, empty, and error states, and use shared hooks and store-managed state to stay in sync with platform API data and workspace context. Where users can update reuse relationships, the experience should feel responsive through optimistic UI where safe, while unified error handling and recovery patterns protect against failed saves or permission issues. This epic supports faster authoring and more consistent, brand-aligned content by making reuse visible, understandable, and reliable in the interface.
The Comparison Tool frontend will let users open two objects or versions side by side in the authoring workspace and clearly surface differences in content, structure, and metadata through a focused comparison view. The experience should fit Aleido’s panel and perspective patterns, keeping selection, version context, loading, and empty states understandable while integrating with the platform API for fetching the compared entities and their diff data. The UI should help users move confidently between compared items, handle permission or missing-data scenarios with consistent error and access handling, and remain responsive across web and desktop. This delivers a faster, more accurate review experience that supports confident decision-making as content evolves.
Draft Creator should provide an authoring experience that lets users enter or confirm the context for AI generation, trigger creation of a first draft, and review the result directly in the UI without leaving their workspace. In the Authoring area, the feature should support a side-by-side layout so the generated draft can be compared against the source context or current content, using the existing panel and perspective patterns where appropriate. The frontend should manage generation state clearly with loading, success, and failure feedback, integrate with the platform API for draft creation and retrieval, and handle retries and error states through the shared error-handling approach.
PDF Publishing on the frontend should let users generate branded, print-ready PDF outputs from CCMS content through clear authoring workflows, exposing template selection, publication options, progress feedback, and downloadable results in the existing workspace UI. The feature should fit naturally into the Authoring experience using the platform’s panel and dialog patterns, with frontend state handling for request lifecycle, validation, loading, success, and recoverable error states while integrating cleanly with the publishing APIs. The UI should make automated layout and template-driven consistency visible and understandable to users, so they can confidently produce manuals, guides, and reports from single-source content with minimal effort. This epic delivers the customer-facing experience that reduces production time while maintaining consistent branding across generated PDF publications.
Deliver an interactive relationships visualizer in the authoring experience that lets users explore how a selected content item connects to other items through references, dependencies, shared metadata profiles, and semantic similarity. The frontend should present this as a graph-focused workspace or panel experience with clear node selection, navigation, and detail states, backed by shared hooks and store-managed view state that stay in sync with workspace context and URL where appropriate. It should integrate with the platform API for real-time loading and refresh of relationship data, while handling loading, empty, error, and access-denied states consistently through existing error-handling patterns. This gives editors and governance users a fast, explorable way to understand downstream impact and reduce missed ripple effects when planning or reviewing content changes.
Build the PDF-to-XML Converter frontend as an AI Tools experience that lets users upload PDFs and other supported unstructured files, review the detected bookmark-based topic splits, and work through conversion in a clear side-by-side workspace. The UI should support iterative adjustment of the intermediate markdown structure before final DITA conversion, using panel-based layouts, shared hooks, and store-backed state to keep file status, selection, edits, and conversion progress in sync with the platform API. The experience should provide responsive loading, clear validation and error states, and safe handling of long-running conversion steps so users can confidently refine results without losing work. This delivers the migration value of reducing manual copy-paste effort and speeding up conversion from legacy documents into structured XML.
On the Authoring workspace, the Info Designer frontend should let users trigger and review AI-generated information objects for both create and update scenarios, presenting the proposed structure and metadata in familiar panels and object-list views before they continue authoring. The UI should clearly show what is new versus what should be updated, using platform API results based on product context, existing content, and the predefined information architecture, so users can understand and act on the assistant’s recommendations. Frontend state and interactions should support loading, partial results, retries, and unified error handling, while keeping the experience fast and approachable for both expert writers and novice SMEs. This delivers a usable first-pass content structure that reduces manual setup and speeds handoff into draft creation or direct human editing.
Deliver the Reuse Suggestions experience in the authoring UI so users can see and act on suggested reusable content in the context of the object they are working on, using existing panel and overlay patterns rather than exposing raw API concepts. The frontend should fetch and render suggestion states through shared hooks and store-backed state, clearly handling loading, empty, error, and permission-restricted cases with the platform’s unified error handling and feedback patterns. Interactions should support responsive updates when suggestions are requested, refreshed, or applied, with appropriate optimistic UI only where the API contract safely allows it and with clear recovery if a request fails. This epic also covers integrating the feature cleanly into the existing workspace and object-selection flow so suggestions stay in sync with the active workspace, selected object, and real-time content changes.
Deliver a frontend experience in Authoring that runs terminology checks against content and surfaces the results where editors work, so deviations from approved vocabulary are easy to spot and correct without leaving the page. The UI should present flagged terms, approved replacements, and clear status/loading states through existing panel and overlay patterns, with frontend state coordinated through shared hooks/stores and synchronized with the platform API. The experience should support efficient review by letting users inspect suggestions in context, apply corrections with responsive feedback, and recover gracefully from API or permission errors via the platform’s unified error-handling patterns. This epic improves editorial speed and consistency by reducing manual proofreading effort while keeping terminology guidance visible and actionable in the core workflow.