Synchronized updates between UI components are needed

Breadcrumbs, navigation, types and workflow should be automatically expanded by the content action and distributed to the global store.

The problem is that, in case of slow backends, the whole UX is bad: clicking on a router link causes the whole interface to progressively update, with some of the UI components displaying wrong information for the main content.

From my perspective the above mentioned components (basically the ones triggered by the App.jsx asyncConnect) should not trigger any actions on router pathname change, they should get their props from the global store, which would be populated by getContent.

So getContent, if no subrequest is provided, should pass ?expand=breadcrumbs,navigation,workflow,types to the backend fetch and the content reducer should be updated accordingly.

This refactoring would also make it easier to create a component that would provide visual feedback for backend network fetch.

[sneridagh]

+1000 to explore this further and make it a priority, since it fixes some strange behaviours (happening now under the hood and almost invisible for the day to day but they are there).

[tiberiuichim]

As arguments in support of my issues, I bring:

• the existence of GraphQL. A whole ecosystem to retrieve data in a single pass
• Frameworks such as next.js/after.js frameworks have connected, as a core concept, the router to the prefetching of server data from the backend server. See https://github.com/jaredpalmer/after.js#getinitialprops-ctx--data