DSRC-65: Call to action block

[jamesbiggs]

Ticket URL: DSRC-65 + DSRC-68

About these changes

Adds a CTA block (DSRC-65) and a button block (DSRC-68)

In the API:

In the CMS:

Before assigning to reviewer, please make sure you have

• Checked things thoroughly before handing over to reviewer
• Checked PR title starts with ticket number as per project conventions to help us keep track of changes
• Ensured that PR includes only commits relevant to the ticket
• Waited for all CI jobs to pass before requesting a review
• Added/updated tests and documentation where relevant

Merging PR guidance

Follow docs\developer-guide\contributing.md

Deployment guidance

Follow docs\infra\environments.md

[ahosgood]

Was there a requirement for the ability to have multiple CTA buttons next to one another?

We also need a boolean field for the button which is accented, defaulting to False. Setting to True would allow the editor to add an accented (coloured) button.

We also need an optional title field so editors can include a longer, more descriptive title of where the button goes.

[ahosgood]

Another thought - are these going into article pages or the yet-to-be-defined "standard page"?

[jamesbiggs]

Another thought - are these going into article pages or the yet-to-be-defined "standard page"?

I just had a chat with Lizzy and she said they will be in a "standard" page, so I'll make a PR before this one is merged to add a standard page, add these components to that, and remove them from Article pages.

Was there a requirement for the ability to have multiple CTA buttons next to one another?

Content haven't asked for it... But I think there could be a case for that (at some point). We can always allow this to add multiple buttons at a later point if that's the case 🙂

We also need a boolean field for the button which is accented, defaulting to False. Setting to True would allow the editor to add an accented (coloured) button.

👍

We also need an optional title field so editors can include a longer, more descriptive title of where the button goes.

They have the sub-heading feature at the minute, I think they would use that here instead of having a dedicated CTA "title"?

[jamesbiggs]

[ahosgood]

Was there a requirement for the ability to have multiple CTA buttons next to one another?

Content haven't asked for it... But I think there could be a case for that (at some point). We can always allow this to add multiple buttons at a later point if that's the case 🙂

Could we make it a list with a max of 1? I'm just thinking about the future - it would be more pain to change a dict to a list because the new format would "break" the frontend whereas adding more buttons, it might just not display them.

We also need an optional title field so editors can include a longer, more descriptive title of where the button goes.

They have the sub-heading feature at the minute, I think they would use that here instead of having a dedicated CTA "title"?

I was on about a specific title attribute on the button itself but looking at it more, I don't think this is needed. We'll just need give advice to devolved editors on how to properly write button text. Carry on!