DNS record management UI

[witha-c]

Issue description

Current designs exist for users to manage name servers and DS data. We need to scale those designs to accommodate other record types. Users should be able to select the type of record they want to add, see the required fields appear, enter information, save, and see a summary of all of the records in a single table.

Acceptance criteria

• Design forms for adding record types A, CNAME, TXT (full list here) (see landscape analysis here)
• Flows to design
  • A registrant has newly registered their domain (after approval), logs in, and clicks "manage"
  • A registrant decides to not use .gov dns hosting
• Incorporate the new nav Nav updates to fit DNS hosting menu items #3501 to design page(s) for org model and non-org model
• Plan workshops/discussions w/product and dev as needed
• Document design decision in a new tab in the DNS hosting summary doc
• Annotate wireframes to show where content work needs to be done
• Review wireframes with trusted tester to check accessibility

Additional context

In scope:

• User can edit multiple records at the same time (this is useful for copying data across multiple records at the same time). Each record will have its own save/cancel/delete button.
• User can search & filter records

Out of scope

• Export / Import options
• Batch editing (using a checkbox to select multiple rows or all rows at once to make changes with 1 save button.

Links to other issues

No response

[h-m-f-t]

@witha-c, Product reviewed the "landscape analysis" doc and made some yes/maybe/no calls.

• "Yes" should be planned for MVP.
• "Maybe" is nice-to-have for MVP, but have more complicated input fields, so they're probably "no".
• "No" is not MVP, but something we'll want to support later.

(cc: @lizpearl and @allly-b)

[witha-c]

@witha-c, Product reviewed the "landscape analysis" doc and made some yes/maybe/no calls.

• "Yes" should be planned for MVP.
• "Maybe" is nice-to-have for MVP, but have more complicated input fields, so they're probably "no".
• "No" is not MVP, but something we'll want to support later.

(cc: @lizpearl and @allly-b)

Clarification that the yes/no/maybe list is in the spreadsheet, not landscape analysis miro!

[witha-c]

I limited this ticket to three record types that represent different form requirements. tagging @gabo0oo to look at the ACs, then we can clone this ticket for the other record types. ty!

[gabo0oo]

@witha-c Looks great! I added some details on intro/outro flows to consider and details in the additional context section on what is in and out of scope. Maybe @katypies or @h-m-f-t can confirm those as my memory is a bit fuzzy.

[h-m-f-t]

Thanks @witha-c and @gabo0oo. Solid edits.