Skip to content

fix(website): restore homepage — revert Phase 01 scaffold placeholder#854

Merged
ashleyshaw merged 1 commit into
developfrom
fix/website-restore-index-homepage
Jun 6, 2026
Merged

fix(website): restore homepage — revert Phase 01 scaffold placeholder#854
ashleyshaw merged 1 commit into
developfrom
fix/website-restore-index-homepage

Conversation

@ashleyshaw
Copy link
Copy Markdown
Member

Summary

PR #851 (feat(ag-p01): Astro project scaffold) replaced website/src/pages/index.astro with a one-line placeholder:

# Phase 01 scaffold — page content coming in Phase 05

This caused the deployed site at https://github.lightspeedwp.agency/ to show only that text.

Fix

Restores index.astro from commit d6e17d7e (the last good state before #851), which contains the full AwesomeGithubLayout-based homepage with:

  • Hero section with CTAs
  • Stats bar
  • Browse by type catalogue grid
  • Getting started section
  • All responsive styles

Testing

Merging to develop will trigger the awesome-github-site.yml deploy workflow, which builds and publishes to GitHub Pages automatically.

PR #851 replaced index.astro with a scaffold placeholder
('Phase 01 scaffold — page content coming in Phase 05').
Restores the full AwesomeGithubLayout-based homepage from
d6e17d7 so the deployed site shows the correct content.

Fixes #851
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 6, 2026

Warning

Review limit reached

@ashleyshaw, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 25 minutes and 24 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 44630ca5-4d94-4df3-9e7b-179680dad70f

📥 Commits

Reviewing files that changed from the base of the PR and between 298694a and 607b7e7.

📒 Files selected for processing (1)
  • website/src/pages/index.astro
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/website-restore-index-homepage

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.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 6, 2026

⚠️ A merged PR reached develop without passing the template content guardrail.

Missing required section(s): Linked issues, Changelog, Global DoD checklist

This is a post-merge backstop for admin bypasses. Please review branch protection for develop.

@ashleyshaw ashleyshaw requested a review from Copilot June 6, 2026 15:06
@github-actions github-actions Bot added status:needs-review Awaiting code review type:bug Bug or defect priority:normal Default priority type:chore Chore / small hygiene change meta:needs-changelog Requires a changelog entry before merge labels Jun 6, 2026
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 replaces the initial scaffold homepage with a fully styled landing page using the AwesomeGithubLayout component. It introduces sections for a hero banner, statistics, category browsing, and getting started onboarding, along with scoped styles. The review feedback highlights two important accessibility improvements: scoping the .ag-lead text color to the hero section to prevent low-contrast issues on light backgrounds, and adding aria-hidden="true" to the decorative bullet point in the eyebrow element to improve screen reader compatibility.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment on lines +152 to +158
.ag-lead {
font-size: var(--fs-lead);
line-height: var(--lh-loose);
color: var(--c-slate-300);
margin: 0 0 var(--space-8) 0;
max-width: 60ch;
}
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.

high

The .ag-lead class has its color set to var(--c-slate-300) (which resolves to #909090) globally within this scoped style block. While this provides good contrast on the dark background of the .ag-hero section, it also applies to the .ag-lead elements in the non-hero sections (such as "Browse by type" and "Getting started").

In light mode, these sections have a white or light gray background (var(--bg) / var(--bg-alt)). A color of #909090 on a white background results in a contrast ratio of only 2.92:1, which violates the WCAG AA minimum contrast requirement of 3:1 for large text.

To fix this, keep the general .ag-lead styles neutral (allowing them to inherit the default text color var(--fg-2)), and scope the var(--c-slate-300) color override specifically to the hero section.

  .ag-lead {
    font-size: var(--fs-lead);
    line-height: var(--lh-loose);
    margin: 0 0 var(--space-8) 0;
    max-width: 60ch;
  }

  .ag-hero .ag-lead {
    color: var(--c-slate-300);
  }

<section class="ag-hero">
<div class="ag-container">
<div class="ag-eyebrow">
<span class="ag-eyebrow-dot">●</span>
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 bullet character is purely decorative and should be hidden from screen readers to prevent them from reading it aloud (e.g., "black circle" or "bullet"). Adding aria-hidden="true" improves the accessibility of the eyebrow element.

        <span class="ag-eyebrow-dot" aria-hidden="true">●</span>

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 6, 2026

🔍 Reviewer Summary for PR #854

CI Status:success
Files changed: 1
Risk Distribution: 0 critical, 0 high, 1 medium, 0 low

Recommendations

  • Ready to proceed pending human review

@ashleyshaw ashleyshaw merged commit 4877cf6 into develop Jun 6, 2026
18 of 20 checks passed
@ashleyshaw ashleyshaw deleted the fix/website-restore-index-homepage branch June 6, 2026 15:07
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 607b7e724a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

.ag-lead {
font-size: var(--fs-lead);
line-height: var(--lh-loose);
color: var(--c-slate-300);
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Use a contrast-safe colour for non-hero lead copy

In light theme, this restored homepage applies #909090 (--c-slate-300) to every .ag-lead, including the “Browse by type” and “Getting started” paragraphs rendered on var(--bg)/var(--bg-alt) light backgrounds. That combination is only about 3.2:1 at the 20px normal-weight lead size (and worse on mobile when it drops to body size), so those paragraphs fail WCAG AA contrast; keep the lighter colour scoped to the dark hero or use a semantic text token such as --fg-2 for the light sections.

Useful? React with 👍 / 👎.

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

Restores the public website homepage by replacing the Phase 01 placeholder index.astro with the full AwesomeGithubLayout-based homepage content, so the deployed GitHub Pages site shows the intended landing experience again.

Changes:

  • Replaces the placeholder homepage with a full hero + CTA section, stats bar, and “Browse by type” catalogue grid.
  • Wires homepage content to existing catalogue data (CATEGORIES, ITEMS, getCategoryCounts) and uses BASE_URL for correct GitHub Pages routing.
  • Adds page-scoped responsive styles for the restored homepage sections.

<section class="ag-hero">
<div class="ag-container">
<div class="ag-eyebrow">
<span class="ag-eyebrow-dot">●</span>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

meta:needs-changelog Requires a changelog entry before merge priority:normal Default priority status:needs-review Awaiting code review type:bug Bug or defect type:chore Chore / small hygiene change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants