Hub microsite builder [MAP-194] [CC-102]

[janbaykara]

This PR adds features that can be used to build hub-style microsites on top of Mapped, so that coalitional campaign data and content can be brought together to coordinate activists.

Description

• Adds Wagtail to Mapped
• Adds a per-organisation frontend editor for pages of the hub
• Adds a staff-only administration area for hub configuration — ahead of org self-service

Motivation and Context

The Hub & Spoke model of organising commonly points to "digital hub"-style infrastructure. Coalitions have multiple event sources, local group databases, actions, asks, and member lists.

Coalescing this on a map is one part of the problem that Mapped solves for organisers internally; sharing this back out to the public is the next step along the road.

But publicly shared data visualisations are most powerful when they can be adapted to their audience, and when data is married to guidance and framing content. Hubs aren't just for directories of data; they're also for narrative, news, guides and resources.

One option is to make Mapped reports embeddable via iframe or script tag. This is on the roadmap.

However the broader concept of a digital hub does well when it can deeply integrate data and other content. Hence this PR.

How Can It Be Tested?

1. Go to Django cms route: http://127.0.0.1/cms and login using your superuser account

On sidebar, Pages -> click "Pages", and create a new page (HubHomepage) and select your org as the owner

Create a Site with hostname united.theclimatecoalition.org and define the hubhomepage as the root page

Go to the react app and click "Hub" in the top to enter the editor; make some changes

Click "Preview in new tab" to review

How Will This Be Deployed?

As above, in prod.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I've checked the spec (e.g. Figma file) and documented any divergences.
• My code follows the code style of this project.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I've updated the documentation accordingly.
• Replace unused checkboxes with bullet points.

[linear]

MAP-194 CMS for hub

[joaquimds]

does this clash with Hero/styles.module.css below?

[janbaykara]

CSS modules not being used. We can delete them.

[linear]

CC-102 Calendar timeline block for trainings