Proof of concept: render component in stand alone webpage

[tomrf1]

Currently we use interactive atoms as a way to insert bespoke content into fronts. E.g. thrashers.
We'd prefer to build these as react components in dotcom-rendering.

• On web, the component could be used as a normal react component.
• On apps, we'd render it in a webview (as we currently do for interactive atoms). To make this possible we'd need a stand alone page that just renders the required component.

This branch demonstrates this, using the existing DesignableBanner component.
It includes a purely server-rendered version, which is not interactive, and a client-rendered version that uses an island. This is important because it means we can use e.g. interactive "choice cards".

http://localhost:3030/AppsComponent/banner
http://localhost:3030/AppsComponent/static-banner

[github-actions]

Deploy build 23983 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 23983 of dotcom:rendering-all to CODE
• Deploy parts of build 23983 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.