Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update inventory of content on transition #3884

Closed
5 tasks done
Tracked by #138
dorothyyeager opened this issue Jul 9, 2020 · 3 comments
Closed
5 tasks done
Tracked by #138

Update inventory of content on transition #3884

dorothyyeager opened this issue Jul 9, 2020 · 3 comments
Assignees
Milestone

Comments

@dorothyyeager
Copy link
Contributor

dorothyyeager commented Jul 9, 2020

Summary

What we are after:
In order to help us prioritize what to get off transition next, it would be good to revisit and update the inventory of pages on there that we made in #1472.

Quick list of things to migrate 🔒

Spreadsheet/inventory of transition pages to migrate: https://docs.google.com/spreadsheets/d/10BodftlKF--VBavaAtDJirGVGrKY8Oow-K4M0ht2Ovw/edit#gid=1102356871 🔒

Related issues

List any relevant related issue(s)

Action items

  • Compare inventory spreadsheet to quick list to identify any pages/items that are missing
  • Quick list is updated and prioritized
  • Quick list is shared with content team and product managers so we can make informed decisions going forward about what to move next.
  • Any needed tickets for future work are put in.

Completion criteria:**

  • Quick list of transition pages to migrate is finalized and agreed to
@dorothyyeager dorothyyeager added this to the Sprint 13.6 milestone Jul 9, 2020
@dorothyyeager dorothyyeager self-assigned this Sep 22, 2020
@dorothyyeager
Copy link
Contributor Author

We need to prioritize this. Rather than update a giant spreadsheet, I'm making a quick list and we'll go through directory together and update as needed.

@dorothyyeager
Copy link
Contributor Author

Did the comparison yesterday and found a few pages that should have been redirected already, so added them to our redirect spreadsheet.

I also found a few more things we still have live and that we will need to either retire, redirect, or add to the migration list. Will share out with content members Friday/Monday and from those discussions, will be able to put in the new tickets.

@dorothyyeager
Copy link
Contributor Author

Data shared out with content team this morning. I've groomed a couple tickets after that. We have a couple of conversations we need to have with business owners; those may result in a few more tickets.

The larger spreadsheet still needs some clean-up, but I've updated throughout. It revealed a few old things that needed redirecting, so those redirects were added to #4073.

We've developed this priority list of tickets: https://docs.google.com/document/d/1liKQT4XwW4z4evfJdMMWWdzuyeQVNGmijir4kUxfDhE/edit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants