Create domain request process diagram for get.gov

[waiwanwong]

Issue description

Users have confusion about the domain request process and what services get.gov can provide.

Acceptance criteria

• Identify content areas where diagram should be included
• List and confirm steps with product/analysts in domain request process are accurate
• Generate concepts for early alignment
• Refine chosen diagram direction and ensure the style aligns with the .gov brand identity
• Route for approvals and team consensus
• Create implementation ticket

Additional context

This task was recommended after conducting a content review of get.gov where we identified content gaps and provided recommendations to remediate these gaps. The Final Summary Report that identifies these content gaps and recommendations can be found here.

Questions to consider

• Consider the style of diagram, should it be a user flow? a step-by-step guide with spot illustrations? an IKEA style instruction diagram?
• What steps should be included or omitted for brevity & visual impact
• How does the diagram behave at smaller viewports?

Links to other issues

Follow-up to #512

[katypies]

Tentatively slotting for Sprint 17 - we should timebox this and make sure that it's the main/key parts of the process a user needs to know, and not necessarily reflective of every possible thing.