Using collections to specify blog CTAs

Design help CMS
1

I’m not sure if I will be able to explain this right as my terminology is pretty amateur, but here it goes.

I am trying to use CMS collections to streamline my call to action/offer at the end of different blog articles. For example, if my blog is about websites - I want my website package CTA/Offer to display at the bottom. If it’s about branding - I want my brand package CTA/Offer to display at the bottom.

What I am trying to achieve is, when I am writing the blog I want a drop down to select which CTA/offer I want to display. Sometimes it might be more than one.

I want to make it so it is easy to edit these CTA/Offers later down the track without going to every blog page.

Does anyone know how I might achieve that? Or a video reference that I can check out that might help?

I don’t have a read only link yet as I am still planning.

TIA

Here is my public share link: LINK
(how to access public share link)

2

If the CTA’s follow the same pattern ( image, background color, title, text, CTA button ) then I’d;

  • Make a CTAs collection
  • Add the fields I want
  • Populate it with some CTAs
  • Create a single-ref from your Blog collection to CTAs
  • Select the CTA you want for each
  • on the Blog collection page, design that section and bind it to your CTA fields
  • make that whole CTA part conditionally visible, so that you can choose to have no CTA for a specific blog article and that section will just disappear.

If each CTA is quite different in styling, functionality, etc then I’d probably approach it differently,

  • Create all of the CTA’s a sections directly in the Blog page design
  • Add an option select field to the Blog collection
  • Populate it with the different CTA’s
  • Make each CTA section conditionally visible so that it only appears if the matching CTA is the one chosen in the select
3

Thanks for your reply Michael,

All of the CTA’s will stylistically look the same, however, I think I like your second approach. It seems cleaner, or maybe that’s just because I understand it easier.

With the first approach - Would that mean I would need to select each part of the CTA individually when writing the blog? ie selecting the header, description and price to populate each field?

4

The first approach will be easier to implement and manage then.

No, each CTA is defined once, in the CTA collection.

5

Ahh nice, that just clicked.

Thanks for your help. Exactly what I was after.

1 Like
6

If anyone else stumbles across this post, this video explains how to connect it all up.