Skip to content

Website: bring back CTA buttons on homepage#45089

Merged
eashaw merged 2 commits into
mainfrom
website-uncomment-homepage-buttons
May 8, 2026
Merged

Website: bring back CTA buttons on homepage#45089
eashaw merged 2 commits into
mainfrom
website-uncomment-homepage-buttons

Conversation

@eashaw
Copy link
Copy Markdown
Contributor

@eashaw eashaw commented May 8, 2026

Changes:

Summary by CodeRabbit

  • Style

    • Refined homepage button styling with improved padding, typography, height, and layout properties for a more polished visual presentation.
  • New Features

    • Updated homepage feature section content with refreshed descriptions and newly activated call-to-action links directing users to detailed product information for device management, orchestration, and infrastructure-as-code features.

Copilot AI review requested due to automatic review settings May 8, 2026 22:22
@fleet-release fleet-release added the ~ga4-annotation This label is automatically applied to certain website changes label May 8, 2026
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

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

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

Tip: disable this comment in your organization's Code Review settings.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

Review Change Stack

Walkthrough

This PR updates the Fleet homepage styling and feature content. A new CSS rule for [purpose='platform-button'] elements applies the existing .cta-button() mixin with specific padding, height, font size, fit-content width, and 32px top margin. Three homepage feature sections ("Freedom at every level", "See reality clearly", and "Get things done faster") are restructured with a new markup hierarchy (feature-list, feature-text, feature-block containers) and updated copy. Previously commented-out CTA links are activated, routing to /device-management, /orchestration, and /infrastructure-as-code respectively.

Possibly related PRs

  • fleetdm/fleet#45004: Both PRs modify the same homepage.ejs feature sections' CTA links — the main PR re-enables/changes those CTAs while the retrieved PR comments them out to disable them.
  • fleetdm/fleet#45001: Both PRs modify the same homepage.ejs feature sections by updating feature text and activating CTAs like "Explore device management" and "More about visibility".
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description is minimal but sufficient for the change scope. It mentions what was done (uncommented and updated styles of CTA buttons) and references a related PR. However, it does not follow the repository's PR description template at all. While the description conveys the basic change, it does not include the template structure (related issue, checklist items, testing notes). Confirm whether the template is mandatory for this change scope.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: uncommenting and bringing back CTA buttons on the homepage. It is concise and specific enough that a teammate would understand the primary change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch website-uncomment-homepage-buttons

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

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@website/views/pages/homepage.ejs`:
- Around line 82-99: The markup now uses purpose="feature-list" but the CSS and
responsive breakpoints target purpose="feature-list-block", causing layout
regressions; fix by either changing the markup back to
purpose="feature-list-block" (replace purpose="feature-list" with
purpose="feature-list-block" on the container elements) or update the stylesheet
to include an alias selector for purpose="feature-list" alongside
purpose="feature-list-block"; ensure you also check sibling elements with
purpose="feature-text" and purpose="feature-block" for consistency and apply the
same change to the other two occurrences referenced in the PR.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f954c02e-9045-4a02-8547-e5416fcd43c5

📥 Commits

Reviewing files that changed from the base of the PR and between aa49a03 and b18673e.

📒 Files selected for processing (2)
  • website/assets/styles/pages/homepage.less
  • website/views/pages/homepage.ejs

Comment on lines +82 to 99
<div purpose="feature-list">

<div purpose="feature-text">
<div purpose="feature-block">
<h5>One platform for every OS — even Linux</h5>
<p>Manage macOS, Linux, Windows, iOS, and Android from a single console, without compromising management and security.</p>
</div>
<div purpose="feature-block">
<h5>UI, API, or infrastructure as code</h5>
<p>Work in the UI, automate with the API, or manage settings as code.</p>
</div>
<div purpose="feature-block">
<h5>All features, flexible deployment</h5>
<p>Unlike other solutions, you can let us host Fleet for you or deploy it yourself. You get the same experience either way.</p>
</div>
</div>
<!-- <a purpose="cta-button" href="/device-management">Explore device management</a> -->
<a purpose="platform-button" href="/device-management">Explore device management</a>
</div>
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.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

feature-list markup no longer matches the existing responsive selectors.

The updated sections now use purpose="feature-list", but homepage styles (including breakpoint behavior) are wired to purpose="feature-list-block". This can cause layout regressions across desktop/mobile in these three blocks.

Proposed CSS alias fix
diff --git a/website/assets/styles/pages/homepage.less b/website/assets/styles/pages/homepage.less
@@
-    [purpose='feature-list-block'] {
+    [purpose='feature-list-block'],
+    [purpose='feature-list'] {
       display: flex;
       flex-direction: row;
       gap: 24px;
@@
-      [purpose='feature-list-block'] {
+      [purpose='feature-list-block'],
+      [purpose='feature-list'] {
         flex-direction: column;
         width: 33%;
       }
@@
-      [purpose='feature-list-block'] {
+      [purpose='feature-list-block'],
+      [purpose='feature-list'] {
         flex-direction: row;
         width: 100%;
       }

Also applies to: 109-125, 135-157

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@website/views/pages/homepage.ejs` around lines 82 - 99, The markup now uses
purpose="feature-list" but the CSS and responsive breakpoints target
purpose="feature-list-block", causing layout regressions; fix by either changing
the markup back to purpose="feature-list-block" (replace purpose="feature-list"
with purpose="feature-list-block" on the container elements) or update the
stylesheet to include an alias selector for purpose="feature-list" alongside
purpose="feature-list-block"; ensure you also check sibling elements with
purpose="feature-text" and purpose="feature-block" for consistency and apply the
same change to the other two occurrences referenced in the PR.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR reintroduces and restyles homepage call-to-action (CTA) links, adjusting the homepage feature-section markup to support the new button placement and reversing one feature-with-image layout to match the intended section order.

Changes:

  • Replaced previously commented-out homepage CTAs with new links using purpose="platform-button" and reorganized feature section markup.
  • Updated homepage layout ordering by adding class="reverse" to a feature-with-image section.
  • Removed stale script includes from the global website layout.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File Description
website/views/pages/homepage.ejs Adds back CTA links and wraps feature text/buttons in a new feature-list container; reverses one section layout.
website/views/layouts/layout.ejs Removes script tags for JS assets that no longer exist in the repo.
website/assets/styles/pages/homepage.less Adds styling for the new platform-button CTA on the homepage.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread website/views/pages/homepage.ejs
@eashaw eashaw merged commit e8f0139 into main May 8, 2026
9 checks passed
@eashaw eashaw deleted the website-uncomment-homepage-buttons branch May 8, 2026 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

~ga4-annotation This label is automatically applied to certain website changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants