-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #543 from guardian/doml/microsite-doc-update
Update Microsite deletion docs
- Loading branch information
Showing
1 changed file
with
18 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,20 @@ | ||
## Microsites | ||
|
||
Are sections and are often used by commercial. Unlike tags there is | ||
currently no option to delete a microsite in Tagmanager. | ||
|
||
Occasionally there is a request to delete a microsite in order for a redirect | ||
to work. Steps to do this: | ||
|
||
* Check the microsite has no content (including expired) associated to it in the | ||
Content API (ask the content-platform team to check Elasticsearch). | ||
* Check that other pieces of content don't refer directly to the microsite page. For example, articles containing links. | ||
* Check our github repo for references to the microsite. We occasionally find hardcoded references to tag pages. | ||
* Providing that is okay delete the microsite directly in Dynamo. | ||
* The microsite will also need to be deleted in Elasticsearch of CAPI. | ||
* The redirect will need to put in place (Dotcom does this). | ||
Microsites are sections and are often used by commercial. Unlike tags there is currently no option to delete a microsite in Tagmanager. | ||
|
||
Occasionally there is a request to delete a microsite in order for a redirect to work. Steps to do this: | ||
|
||
Tasks for the WebX team: | ||
|
||
- Check that other pieces of content don't refer directly to the microsite page. For example, articles containing links. | ||
- Check our github repo for references to the microsite. We occasionally find hardcoded references to tag pages. | ||
|
||
Tasks for the CAPI team: | ||
|
||
- Check the microsite has no content (including expired) associated to it in the Content API (ask the CAPI team to check Elasticsearch). | ||
- Providing that is okay, delete the microsite directly in Dynamo. | ||
- The microsite will also need to be deleted in Elasticsearch of CAPI. | ||
|
||
Tasks for CP: | ||
|
||
- The redirect will need to put in place. |