Skip to content

refactor(home): place hero taglines above the title#526

Draft
tym83 wants to merge 1 commit intomainfrom
refactor/hero-taglines-above-title
Draft

refactor(home): place hero taglines above the title#526
tym83 wants to merge 1 commit intomainfrom
refactor/hero-taglines-above-title

Conversation

@tym83
Copy link
Copy Markdown
Contributor

@tym83 tym83 commented May 3, 2026

Follow-up to #524.

What

Move the three positioning taglines from below the H1 to above it, so they read as an eyebrow line at the very top of the hero. Restore the Get started button to its original spot inside the description column (it had not actually moved on main, but this PR keeps the layout explicit).

Visual order on the homepage becomes:

  1. Taglines (Self-Hosted Alternative to AWS · AI-Ready Infrastructure · Open-Source VMware Alternative)
  2. H1
  3. Description (left) + product video (right)
  4. Get started CTA

Why

After #524 landed, the pills sat between the H1 and the description, which broke the natural reading rhythm — the headline was no longer the first thing the eye lands on. Moving the pills above the title:

  • restores H1 as the primary visual anchor
  • aligns the pills horizontally with the Kubernetes Certified logo on the right, balancing the title row
  • still keeps the positioning text near the top for SEO weight (taglines are now the very first textual content inside the hero section)

Implementation

  • layouts/shortcodes/blocks/hero.html: render taglines block immediately before <h1> inside the title column
  • assets/scss/blocks/_hero.scss:
    • .hero-taglines get the padding-top: 50px that previously lived on <h1>, so they align with the K8s Certified logo
    • .hero-taglines + h1 { padding-top: 0 } keeps the H1 tight under the pills when the taglines are present, but leaves the original H1 spacing intact for any future hero usage without taglines

Preview

Verified with hugo server — pills render aligned with the K8s logo on desktop, wrap to multiple lines on mobile; H1 sits tight beneath them; rest of the homepage (benefits, features, community) unchanged. A Netlify deploy preview will be available on this PR.

Move the positioning pills to the top of the hero block, immediately
above the H1 so they read as an eyebrow line and align with the
Kubernetes Certified logo on the right. Restore the Get started button
to its original spot inside the description column.

Signed-off-by: tym83 <6355522@gmail.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented May 3, 2026

Deploy Preview for cozystack ready!

Name Link
🔨 Latest commit b4bbff2
🔍 Latest deploy log https://app.netlify.com/projects/cozystack/deploys/69f697920a6be20008066f21
😎 Deploy Preview https://deploy-preview-526--cozystack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 3, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f67cd83e-0db9-4ec1-b78b-98b2f694558e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch refactor/hero-taglines-above-title

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get your free trial and get 200 agent minutes per Slack user (a $50 value).


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request reorders the hero section elements in the HTML template, placing taglines above the title and subtitle. Corresponding SCSS changes adjust the padding and margins to accommodate this new layout, specifically setting a 50px top padding for taglines and removing top padding from the title when it follows taglines. A review comment suggests using a SCSS variable for the 50px offset to improve maintainability, as this hardcoded value is now used in multiple locations.

list-style: none;
padding: 0;
margin: 1rem 0 0;
padding: 50px 0 0;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The value 50px is now hardcoded in three separate locations in this file (lines 52, 66, and 95) to ensure the hero content (either the title or the taglines) aligns vertically with the Kubernetes logo on the right. To improve maintainability and prevent alignment issues if this spacing needs to change in the future, consider defining a single SCSS variable for this offset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant