Skip to content

Eliminate type:custom pages — push to Tier-4 / ADR-024 #237

@rubenvdlinde

Description

@rubenvdlinde

Current manifest has 3 type:custom pages out of 29 (10%). Goal: convert to typed primitives where possible (CnDetailPage / CnIndexPage / etc.) or justify with _note per ADR-024 v2 schema. Bump manifest $schema to v2.

Audit

  • MeetingIntegrations (route /meetings/:id/integrations) — thin wrapper that just renders CnDetailPage with sidebar.useRegistry: true. Convertible to type: "detail" with config-driven sidebar.
  • LiveMeetingView (route /meetings/:id/live) — genuine realtime UI (WebSocket subscriptions, frame-by-frame, animations). Stays custom with _note.
  • FeaturesRoadmap (route /features-roadmap) — thin wrapper around lib's CnFeaturesAndRoadmapView, but the v2 type enum doesn't include a roadmap primitive. Stays custom with _note.

Plan

  1. Convert MeetingIntegrations to typed detail page (drop component from registry).
  2. Add _note justification to remaining 2 customs.
  3. Bump manifest $schema to app-manifest-v2.schema.json.
  4. Add registry.js (5-kind v2 registry) listing remaining customs as kind: 'page'.
  5. Verify in browser, admin-merge to development.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions