announcements: migrate components to `@backstage/ui` design system

[kurtaking]

Workspace

announcements

Summary

This issue tracks the remaining work to complete the migration of all announcements plugin components to the new @backstage/ui design system.

Current Progress

Completed

• AnnouncementsAdminPage [announcements] Use header from @backstage/ui in admin portal for nfs #6426
• CategoriesContent [announcements] Admin categories and tags rewrite with @backstage/ui for NFS #6484
  • CategoriesTableCard
  • CategoriesTable
  • CreateCatagoryDialog
• TagsContent [announcements] Admin categories and tags rewrite with @backstage/ui for NFS #6484
  • TagsTableCard
  • TagsTable
  • CreateTagDialog
• DeleteConfirmationDialog [announcements] Use header from @backstage/ui in admin portal for nfs #6426
• CreateTitleDialog [announcements] Use header from @backstage/ui in admin portal for nfs #6426
• AnnouncementsPage [announcements] Update end-user announcements page for nfs to use @backstage/ui #6521
  • AnnouncementPage - Single announcement view
  • ContextMenu - Header context menu (bui menu)

Not Migrating

• AnnouncementsTimeline - Deprecated (will not be replaced)
• AnnouncementsAdminPortal (Old public exported component extension) - Deprecated (replaced with AnnouncementsAdminPage available via direct /announcements/admin url or context menu)

Remaining Migration Tasks

Complete Admin

• AnnouncementsContent - Admin announcements table
• AnnouncementForm - Create/edit announcement form
  • Keep: @uiw/react-md-editor (markdown)
  • Sub-components:
    • CategoryInput - likely use Searchable Select
    • TagsInput - likely use Searchable Multi Select
    • OnBehalfTeamDropdown - likely use Searchable Select

Widgets

• AnnouncementsCard - Dashboard widget
• (BLOCKED) AnnouncementBanner - New announcement notification
  • No Toast/Snackbar equivalent

Search

• AnnouncementSearchResultListItem - Search result display

Cleanup

• Update alpha Router to import all components from alpha directory
• Consider upgrading existing frontend plugin to use new components

Notes

• InfoCard from core-components → Card
• Utility files do not need migration
• MarkdownRenderer can remain unchanged

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

Yes I am willing to submit a PR!