Virtual Registry: Standalone pages for Create Upstream

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

Overview

As the Create Upstream form grows (e.g. the addition of new Restrictions section in #548654), the form has become increasingly lengthy and visually dense. To improve the user experience and maintain consistency, we propose moving both the Create upstream forms to dedicated standalone pages.

Current State

• The Create Upstream form is currently presented inline within a table component (#493842[Create-upstream.png]).
• The Create action calls a GraphQL mutation which combines the behaviour of 2 REST APIs creation & association with registry
• The Edit Upstream form already uses a standalone page (#493842[Edit-upstream.png]).

Proposed Change

• Move the Create upstream form to a dedicated standalone page.
• Adjust the Edit upstream form to align structurally and visually with the new Create form for consistency.

Why is this needed?

• The inline Create form has become long and less usable as more sections are added (e.g. Restrictions).
• A standalone page improves clarity, scannability, and focus.
• Aligning the Create and Edit experiences reduces cognitive load and helps users form consistent mental models across similar workflows.