Use labels (review needed, in progress, or paused) to declare status
What does this PR do?
This creates a new widget area, Migrated Content Notice, which is loaded on the 404 template to allow site builders to create custom notices about migrated content.
Helpful background context (if appropriate)
This feature is intended to be used as part of a new website for Distinctive Collections, which involves the retirement or migration of almost 2000 pieces of content. Because it will not be possible to create redirects for each piece of retired or migrated content - thus guaranteeing that some traffic will make its way to the theme's 404 template - we are enabling the creation of content advisories at that step in the process.
How can a reviewer manually see the effects of these changes?
This branch has been deployed to the staging server, and a sample advisory created for the /foo* path. The content we anticipate being used for the new DC site is at /test-404
Screenshots:
Current 404 page:
New default 404 page (seen when no widgets are defined - phrasing changes slightly)
New custom 404 page (content now provided by a widget for a specified URL pattern, replacing the default)
Todo:
[x] Stakeholder approval
Requires new or updated plugins, themes, or libraries?
Status
Use labels (
review needed,in progress, orpaused) to declare statusWhat does this PR do?
This creates a new widget area,
Migrated Content Notice, which is loaded on the 404 template to allow site builders to create custom notices about migrated content.Helpful background context (if appropriate)
This feature is intended to be used as part of a new website for Distinctive Collections, which involves the retirement or migration of almost 2000 pieces of content. Because it will not be possible to create redirects for each piece of retired or migrated content - thus guaranteeing that some traffic will make its way to the theme's 404 template - we are enabling the creation of content advisories at that step in the process.
How can a reviewer manually see the effects of these changes?
This branch has been deployed to the staging server, and a sample advisory created for the
/foo*path. The content we anticipate being used for the new DC site is at/test-404Screenshots:
Current 404 page:
New default 404 page (seen when no widgets are defined - phrasing changes slightly)
New custom 404 page (content now provided by a widget for a specified URL pattern, replacing the default)
Todo:
Requires new or updated plugins, themes, or libraries?
NO
Requires change to deploy process?
NO