You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure that all pre-migration issues have been completed and that the specific guide is prepared (tests are passing, there are no TODO links left over
Confirm DNS records are up-to-date for the OLD guide domain
Remove redirects from the new URL to the old guides (ie, stop guides.18f.gov/[guide-name] from redirecting to [guide-name].18f.gov)
Add the new guide in the Search.gov admin panel instructions
Hard release
Permanently redirect old guide URLs to the new guide (ie, [guide-name].18f.gov/etc/etc2/ redirects to guides.18f.gov/[guide-name]/etc/etc2/)
Post release
Monitor analytics for the new site for some specified period of time
Update 18f.gsa.gov website to use new guides link
Turn on automatic reviewer tagging for guide
Update the working migration doc with any refinements of the process, to make future migrations easier
Other resources
pages-redirects repository where the routing changes will be made (see the migration doc)
Billable?
Yes
No
If yes, tock code:
Skills needed
Any human
Design
Content
Engineering
Acquisition
Product
Other
Timeline
Does this need to happen in the next two weeks?
Yes
No
How much time do you anticipate this work taking?
The changes should be straightforward, but the merge and deploy of reroutes will take an unspecified amount of time, as it relies upon Cloud-gov's internal processes.
Acceptance Criteria
guides.18f.gov/ux-guide/ points to the new, live, replatformed UX guide
Analytics is able to show incoming data for the new UX guide after some specified period of time
We have a refined migration doc available for future migrations
The text was updated successfully, but these errors were encountered:
🟢 UX IS READY TO GO 🟢
A description of the work
We will migrate the UX guide to the new consolidated, replatformed guides setup.
As with the migration of all guides, we will also be using this opportunity to refine the guide/checklist for migrating individual guides.
Point of contact on this issue
@christophermather
Reproduction steps (if necessary)
Most of the steps we expect to follow can be found in the draft individual migration guide document. From a high level, these include:
Soft release
TODO
links left overguides.18f.gov/[guide-name]
from redirecting to[guide-name].18f.gov
)Hard release
[guide-name].18f.gov/etc/etc2/
redirects toguides.18f.gov/[guide-name]/etc/etc2/
)Post release
Other resources
Billable?
If yes, tock code:
Skills needed
Timeline
Does this need to happen in the next two weeks?
How much time do you anticipate this work taking?
The changes should be straightforward, but the merge and deploy of reroutes will take an unspecified amount of time, as it relies upon Cloud-gov's internal processes.
Acceptance Criteria
guides.18f.gov/ux-guide/
points to the new, live, replatformed UX guideThe text was updated successfully, but these errors were encountered: