The Review Tool frontend will provide a focused review experience where subject-matter experts and stakeholders can read content, add comments and annotations, and complete approval actions without leaving the workspace context. In the UI, this should fit naturally into Aleido’s panel and perspective patterns, with clear version context, consolidated feedback, and responsive state updates driven by shared hooks and stores integrated with the platform API. The experience should make review status, discussion history, and version changes easy to understand at a glance while handling loading, permission, and error states consistently across web and desktop. This epic supports faster, less confusing review cycles by giving users a single, structured place to collaborate on content quality and sign-off.
This epic brings analytics and business intelligence into the Aleido frontend as a user-facing experience where teams can explore content-production trends, spot bottlenecks, and identify improvement opportunities directly in the platform. The work should focus on clear visualizations, filters, and drill-in interactions within the existing page and panel patterns, with frontend state and shared hooks coordinating API-backed loading, refresh, and workspace-aware context. It should integrate with the platform API to present reliable, permission-aware data across web and desktop, while handling loading, empty, and failure states through the established error-handling patterns. The outcome is a responsive, trustworthy analytics experience that supports data-driven decisions about content strategy, governance, and resource allocation.
The Import module should give users a clear import flow in the authoring workspace for bringing in new documents or updating previously imported content, with progress, validation, and error states handled consistently across panels, dialogs, and notifications. The UI must surface profiling and classification metadata applied during import so users can review what will be attached to content and understand the outcome once the platform API completes processing. Where supported by permissions and source rules, the frontend should also let teams mark imported content from another CCMS for direct distribution, making that workflow explicit in the import experience while bypassing draft and review states in the user-facing status model. This epic includes the frontend state management and API integration needed to keep import jobs, results, and failures in sync with the wider workspace experience across web and desktop.
The Migration Analyser frontend should give users a clear workspace for understanding migration readiness, with UI that presents KPIs, structure comparisons, and actionable guidance in a way that supports decision-making rather than exposing raw analysis output. In the app, this should be delivered through responsive views and panels that load analysis data from the platform API, manage loading and error states consistently, and keep analysis context in shared state as users move between compared structures and recommendations. The experience should make it easy to see which parts of the source can be migrated automatically versus which require human intervention, with clear visual distinction and drill-down into the underlying information structure. The epic includes the frontend integration patterns needed to surface analysis results reliably across web and desktop, including error boundaries, empty states, and permission-aware access to the feature.
Deliver the video capability in the Authoring experience so users can browse, create, version, and manage video objects as first-class content alongside other CCMS objects, with clear status, metadata, and version history in the existing panel-based UI. Authors should be able to link videos from topics and select precise timestamps or segments through intuitive picker and preview interactions, with frontend state kept in sync with platform APIs and real-time updates where available. The implementation should follow established patterns for panels, shared hooks, and stores, while handling loading, permission-gated actions, and API failures consistently through the platform’s unified error and feedback experience.