@Katherine-Osos - is this pertaining to beta.get.gov or registrar?

@Katherine-Osos, has this been subsumed into the larger content review work? https://github.com/cisagov/manage.get.gov/issues?q=is%3Aissue+is%3Aopen+review+label%3Acontent

@michelle-rago filed a targeted example to fix, too.

@h-m-f-t For the most part, yes. However, we have multiple people reviewing the content so there's still a chance for inconsistencies in approach. We also need to document the standard in our content guide.

I think we should keep this ticket to do one final pass thru after the content review is completed. But it should be fairly quick.

Ran into issues with my sandbox - will delete branch, pull from main, and redo

Added "dev" label: during pre-sprint planning, the decision from the leads were to assign the remaining work to the dev team. Slotted remaining work for sprint 45.

In hindsight @vickyszuchin I should have realized this needs a bit of refinement before we switched it to dev. I realize this requires a content decision as well as documentation for that content decision, @kristinacyin is that part done? Is the decision just to do "Gov domain request | page title"? This was my assumption but I realized that was based on the PR not on what is documented here.

I temporarily moved this to sprint 46 since there is an outstanding question. cc @Katherine-Osos

Added "refinement" label, see comment from Alysia on 5/6.

I finally finished updating this doc: https://docs.google.com/document/d/1Nk92LNq0pbPDS0EOjIsIcDEiP2da0Q5j7HoJF7l3xqo/edit?usp=sharing

The suggestions that haven't been accepted yet are changes that still need to be implemented.

There is a current PR for get.gov changes: cisagov/get.gov#293

There is no current PR for manage.get.gov changes.

FYI: @abroddrick @vickyszuchin

"refinement" label added: while the document is being reviewed by dev team.

@kristinacyin

1. Am I understanding correctly that this document is meant to show the actual html page titles we want, and thus that part is decided and now we just need to update them in the code, correct?

2. were route/url changes also supposed to be included in this ticket as an AC or no?

@abroddrick

1. Only suggestions in the doc need to paid attention to, everything else is what already exists/have already been changed. The suggestions are the changes we want and have already been decided on.
2. Yes, changes in the doc are included in the ticket, but can be split to another ticket if it makes more sense to do so.

Thanks @kristinacyin that clarifies things! I will make it clear the scope is just the html page titles not the routes. Kristina, I am finding it hard to use the suggestions. I can't click a suggestion and have it take to that spot, so I have to scroll through the document and the coloration is kind of hard to tell what's a suggestion because it switches colors based on what was changed. I would not recommend using this format going forward as it's hard for me to actually see the scope of the changes and it will be difficult for someone to make sure they completed everything.

@vickyszuchin can we get a ticket for the get.gov portion and any routes that need to be adjusted