[reports] scaffold out front-end

[jhmullen]

This should be pretty close to the CMS, as it will be almost the same blocks. However, we will have to handle SSR / URL parsing/canon-need considerations

[jhmullen]

@davelandry

I have created a dead-simple front-end in /src/frontend. It contains only Report.jsx and Section.jsx. Section reaches into the various renderers (currently being worked on by @greenrhyno ) to draw the blocks.

There is a lot of forthcoming work to make selector callbacks work and other interactive components. Further, in a more general sense, we are obviously trying to make the Front end and CMS as close as possible.

However - the CMS currently has tons of drag and drop code mashed in there, lots of of edit button dispatches, etc. My ask here is:

Can you scaffold out as much layout as you can into these front-ends, so that it looks more like a real page? There may be some way, ultimately, for them to rely on identical code paths, but for now, I want to keep them separate, especially as we approach next.js and other SSR/need-based differences.

[jhmullen]

I'm removing myself temporarily while you take over this issue. Please ping me once I can take back over to handle front-end interactions, click events, etc.

[davelandry]

passing this back to @jhmullen now for "front-end interactions, click events, etc." 😘