Improved rendering of Content Explorer

[tmkarlsen]

Investigate and document

Improved rendering of Content Explorer

By removing the React application, which is rendered both server-side and client-side, we'll reduce the number of requests to the backend APIs and event listeners being synchronized when loading the page (hydrating) in Content Explorer. Rendering templates on the server will enable the browser to display HTML unprocessed, decreasing response time and increasing performance in general.

• This will make the list of resources load faster
• The 503 error often seen on the first load of Edlib every day should also disappear.

Content Explorer will consist of HTML and CSS

Needs to be concluded upon

• [ ] CSS framework

Any downsides with the new rendering? What will we lose?

• Previews of external content? (needs verification)
• Losing access to the React system