What is the value of this and can you measure success?
Part of the work to remove the liveblog Message Us feature. Frontend is responsible for the message us service that retrieves the message data stored in s3 and stores it in cache, pertaining to which liveblogs have the feature running. It then passes that to DCR to render the MessageUs component on the page.
What does this change?
This feature, originally added here, has now been decomissioned by Editorial.
All deployment options
- [Deploy build 2345 of `dotcom:frontend-all` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=dotcom%3Afrontend-all&build=2345&stage=CODE&updateStrategy=MostlyHarmless&action=deploy)
- [Deploy parts of build 2345 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=dotcom%3Afrontend-all&build=2345&stage=CODE&updateStrategy=MostlyHarmless)
- [What's on CODE right now?](https://riffraff.gutools.co.uk/deployment/history?projectName=dotcom%3Afrontend-all&stage=CODE)
What is the value of this and can you measure success?
Part of the work to remove the liveblog
Message Us
feature. Frontend is responsible for the message us service that retrieves the message data stored in s3 and stores it in cache, pertaining to which liveblogs have the feature running. It then passes that to DCR to render the MessageUs component on the page.What does this change?
This feature, originally added here, has now been decomissioned by Editorial.