Tailwind CSS Call-to-Action Sections Blocks

All Blocks
Marketing
Call-to-Action Sections

Call-to-Action Sections

Tailwind CSS call-to-action sections with headings, text, and buttons to boost conversions.

Centered Call-to-Action Section with Dual Actions Pro

Short headline copy sits in the center with two primary actions grouped beneath it.

Create a responsive UI block named "Centered Call-to-Action Section with Dual Actions" that visually and behaviorally matches the Preline source block. Use the destination project's existing framework, Tailwind setup, semantic tokens, component primitives, icon system, routing/link conventions, and dark-mode strategy.

Implementation preflight:
- Exact public block reference: https://preline.co/blocks/marketing/call-to-action-sections/#centered-call-to-action-section-with-dual-actions. Open this exact anchored block and inspect its Preview and HTML tabs when browsing is available; do not use neighboring examples or surrounding docs chrome as source.
- Before writing code, inspect the destination project's package manifest, Tailwind/theme configuration, global styles, app shell/container conventions, icon system, and existing components. Reuse or compose an existing implementation when it already represents the same source partial or behavior; do not duplicate its markup, state, assets, or interaction logic.
- If neither the public reference nor local source paths are accessible, use only the explicit source-derived details in this prompt. If those details are insufficient, request the source HTML instead of guessing from the block title or category.

Build only this source block. Do not add unrelated page chrome, marketing sections, dashboard widgets, extra cards, extra modals, placeholder states, or footer content unless they are present in the source block.

Source metadata:
- Catalog family: marketing/call-to-action-sections
- Block ID: centered-call-to-action-section-with-dual-actions
- Source description: Short headline copy sits in the center with two primary actions grouped beneath it.
- Preview iframe: https://preline.co/blocks/marketing/call-to-action-sections/iframes/pro/centered-call-to-action-section-with-dual-actions.html (repo path: blocks/marketing/call-to-action-sections/iframes/pro/centered-call-to-action-section-with-dual-actions.html)
- Source markup reference:
  - partials/pro/saas-startup/layouts-components/cta-section.html

Use the source HTML tab and referenced partials as the source of truth. Preserve exact visible copy, content order, hierarchy, component density, spacing relationships, borders, radii, icons, status markers, dropdown/menu rows, form states, responsive order, and interaction content. If the source imports shared partials or assets, reuse those local components/assets when the destination can import them; otherwise recreate their visible structure faithfully from the source.

Block-specific fidelity rules:
- Preserve the source marketing hierarchy, first-viewport signal, media subject, CTA order, proof/social elements, visual rhythm, and responsive composition.
- Do not convert distinctive hero/marketing visuals into a generic split card layout or invent decorative media that is not present in the source.
- Source content inventory (from the source markup):
  - Copy in order: mono eyebrow `Get started`, then the heading `The Web App powering` / `thousands of companies.` split across two lines by an explicit `<br>`.
  - Exactly two actions, centered and in this order: solid primary `Try it free`, then a borderless text action `Get a demo` carrying a right-arrow icon whose shaft fades/slides in only at `lg` on group hover/focus.
  - Eyebrow is `font-mono text-sm` muted; heading is `font-semibold text-2xl sm:text-4xl`; the header block is `text-center` with `mb-4 sm:mb-8`.
  - Geometry: `max-w-6xl px-4 sm:px-6 lg:px-8 mx-auto` outer container wrapping a panel with `md:-mx-4 xl:-mx-20 px-4 py-6 md:py-12 xl:p-20 bg-linear-to-b from-background-2 to-transparent rounded-2xl`.
  - Buttons are `rounded-lg` anchors sized `py-2 px-3 md:py-2.5 md:px-4` with `text-[13px] md:text-sm`; both `href="#"`.
  - Fully static; no images, avatars, forms, or Preline JS plugins in this section.

Token and Tailwind rules:
- Treat source token classes as semantic roles, not fixed class names to blindly copy.
- Map every source `primary` role to the destination project's current primary token/config/CSS variable. Active links, checked states, progress lines, focus rings, primary gradients, logo primary fills/strokes, and primary buttons must share that destination primary color.
- Do not hardcode Preline blue or emit `text-blue-*`, `bg-blue-*`, `border-blue-*`, `fill-blue-*`, `stroke-blue-*`, `from-blue-*`, `via-blue-*`, `to-blue-*`, or fixed blue hex/rgb values for primary roles unless the destination primary is explicitly blue.
- Before using source-only token classes such as `text-foreground-inverse`, `bg-layer`, `border-layer-line`, `bg-navbar`, `border-line-2`, `bg-dropdown`, or similar Preline tokens, inspect the destination Tailwind config, global CSS/theme variables, and existing components for an equivalent utility/token.
- Prefer existing destination utilities such as `text-white`, `text-primary-foreground`, `text-foreground`, `text-muted-foreground`, `bg-background`, `bg-card`, `bg-popover`, `border-border`, `bg-muted`, `bg-accent`, `ring-ring`, or app-specific tokens when they match the source role.
- If no equivalent exists, add the smallest project-appropriate token or utility before using it. Do not leave undefined source classes in the generated markup.

Asset and icon rules:
- Use exact source images, avatars, product media, branded SVGs, payment marks, channel logos, and app icons when the source provides them.
- Do not replace source assets with initials, emojis, generic icons, generated placeholders, or different stock media.
- Ordinary interface icons should match the destination icon system. If the project uses Lucide-style outline icons, keep the 24 viewBox, `fill="none"`, `stroke="currentColor"`, rounded caps/joins, and source stroke widths.
- Brand/source SVG shape is fixed content. Only map semantic colors such as primary fill/stroke to the destination token.

Behavior and accessibility:
- Preserve source interactions: links, buttons, dropdowns, tooltips, tabs, menus, drawers, modals, toggles, search, filters, form controls, validation states, loading/empty states, and open/closed defaults.
- For source behavior powered by Preline JS or a third-party package, inspect installed dependencies and existing primitives first. Reuse a destination primitive only when it can preserve the source geometry, states, accessibility, and behavior.
- Treat new dependencies as allowed by default unless the user, repository instructions, or package policy explicitly prohibit them. When no faithful equivalent exists, install/use the Preline UI runtime/plugin or the exact source third-party package; do not silently substitute ad hoc JavaScript or custom React state.
- Only under an explicit dependency prohibition may you implement a scoped framework-native equivalent. It must preserve keyboard and focus management, placement and layering, responsive behavior, and accessibility; static or simplified approximations are not acceptable.
- Use semantic HTML and accessible names. Keep `aria-current`, `aria-expanded`, `aria-haspopup`, `role`, labels, focus states, and keyboard behavior when the source exposes them or the destination primitive requires them.
- Desktop and mobile states must not overlap text, clip controls, or shift layout unexpectedly. Controls with icons, counters, badges, and labels should keep stable dimensions across hover/focus/active states.

Final QA:
- Compare the result against the source preview and HTML tab.
- Verify primary color follows the destination project, not Preline's default blue.
- Verify all emitted classes exist in the destination or are added deliberately.
- Verify responsive layout, focus states, dropdown/popover layering, long-text truncation, and source asset paths.
- Keep the final implementation scoped to this block and avoid unrelated refactors.

<div class="max-w-6xl px-4 sm:px-6 lg:px-8 mx-auto">
                      <div class="md:-mx-4 xl:-mx-20 px-4 py-6 md:py-12 xl:p-20 bg-linear-to-b from-background-2 to-transparent rounded-2xl">
                        <div class="mb-4 sm:mb-8 text-center">
                          <p class="mb-2 font-mono text-sm text-muted-foreground-1">
                            Get started
                          </p>
                          <h2 class="font-semibold text-2xl sm:text-4xl text-foreground">
                            The Web App powering<br>thousands of companies.
                          </h2>
                        </div>

Open related SaaS Startup homepage