Display CTA component with a slot

[Polo2]

Purpose of this PR is to display the CTA button in guides section 'OpenAPI specification'.

I noticed that component Shared::BumpCta was already included in layout _documentation.erb, as a slot named :after in component Shared::Sidebar, but it was not displayed.

What is done in this PR:

• change condition to display this component: favor ready-to-use boolean resource.data.display_cta

• render the slot in the component, with <%= slotted :after %>

• add basic CSS to keep space between this CTA and the sidebar links 😇 (no dinguerie I swear!)

• set data.slug to 'openapi-specification', used as utm_content.

ℹ️ Data display_cta is responsible to display the BumpCta component. We would need to change value to false where it's not necessary.

Now:

---

context: Slack discussion

[netlify]

✅ Deploy Preview for bump-content-hub ready!

Name	Link
🔨 Latest commit	f61aae0
🔍 Latest deploy log	https://app.netlify.com/sites/bump-content-hub/deploys/67e2bf25c826c900085a5e17
😎 Deploy Preview	https://deploy-preview-345--bump-content-hub.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[thimy]

I left a suggestion concerning the CSS, but otherwise this seems good to me!

[thimy]

I think it would be better to put this margin directly on the cta, since this margin should only exist when the cta follows the sidebar-list.

It would look like this:

        .sidebar-list + bump-cta {
          margin-block-start: var(--spacing-8);
        }

Here we favour the usage of the logical property margin-block-start (which is similar to margin-top as it would be more flexible in case of using languages having different reading directions.

Also, I think it would be better to comment directly in github when submitting your PR instead of adding the comment in the code. This way it opens the discussion, and in case the code is alright, we don't have an irrelevant message to remove. 😊

[Polo2]

I think it would be better to put this margin directly on the cta, since this margin should only exist when the cta follows the sidebar-list.

Indeed it looks really more clear with your suggestion, thanks for the explanation

Also, I think it would be better to comment directly in github when submitting your PR instead of adding the comment in the code. This way it opens the discussion, and in case the code is alright, we don't have an irrelevant message to remove. 😊

Sure 😄
In this case I was quite sure my CSS was not enough, ne need to merge this in first state, so I was quite sure to remember to remove the comment.