Post Publishing Tool

[shrunyan]

Is your feature request related to a problem? Please describe.
People are unable to gain an understanding of the interconnected published state of items. e.g. When items are related how to you understand what version (read: state of the content) should be the expected publicly available one.

Describe the solution you'd like
Potentially we can create a "Publish Dashboard". This would be an area which shows all the latest publish events and would ideally be able to describe the related nature of items. Additionally it would be useful to provide the current state upstream CDN object. Allowing for investigation of why the render requests do not meet the expect state of what the CMS shows.

Describe alternatives you've considered
A simple list of publish actions would be the quickest solution which may provide the insight people want but could use more thought. This will need a full feature development cycle (user research, design, testing) to build a truly considered solution.

Additional context
The need becomes most painful when a publish event occurs and the front-end breaks (read: does not meet the publishers expectations). At which point someone without intimate knowledge of the pattern won't know how to determine if it's something they changed or even where to start determining this.

[d88naimi]

I think this may also be related to #37