Skip to content

Fix landing page issues (#350) - #431

Open
Om7035 wants to merge 8 commits into
QuoteVote:mainfrom
Om7035:fix/landing-page-issue-350
Open

Fix landing page issues (#350)#431
Om7035 wants to merge 8 commits into
QuoteVote:mainfrom
Om7035:fix/landing-page-issue-350

Conversation

@Om7035

@Om7035 Om7035 commented Jul 19, 2026

Copy link
Copy Markdown
Collaborator

Matched exact Zeplin designs for the homepage including Private Conversations section, footer layout, specific fonts, and community card order. Closes #350.

omkawale-regtech and others added 3 commits June 29, 2026 23:44
…uoteVote#350

Implement comprehensive homepage redesign to match Zeplin specifications:
- Added Platform Principles section (4 core values)
- Added Community Use Cases section (6 use case cards)
- Added Private Conversations section with buddy system
- Preserved existing sections (Hero, Features, Product Showcase, etc.)
- Updated imports to include new icons (Lock, BookOpen, Code, Smile)

All sections are fully responsive and accessible. Maintains existing
analytics and invite request tracking.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Add test coverage for:
- Platform Principles section (4 principle cards)
- Community Use Cases section (6 use case cards)
- Private Conversations section (buddy system)

Tests verify rendering, card presence, and description text.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
'Open Source' appears multiple times on the page (hero section + principles).
Updated test to use getAllByText for proper assertion.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 19, 2026

Copy link
Copy Markdown

@Om7035 is attempting to deploy a commit to the Louis Girifalco's projects Team on Vercel.

A member of the Team first needs to authorize it.

@Om7035
Om7035 force-pushed the fix/landing-page-issue-350 branch from dfaacd2 to b7d894c Compare July 19, 2026 20:19

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

Copy link
Copy Markdown

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: dfaacd21b6

ℹ️ 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".

Comment on lines +251 to +253
<div className="flex w-full max-w-[280px] h-[48px] mb-4 rounded-[12px] overflow-hidden border-[1px] border-[#E5E5E5] focus-within:border-[#1AAE5A] focus-within:ring-1 focus-within:ring-[#1AAE5A]">
<input type="email" placeholder="you@example.com" className="bg-transparent px-4 h-full text-[13px] text-[#2A2A2A] placeholder-[#A0A0A0] flex-1 focus:outline-none min-w-0" />
<button className="bg-[#1AAE5A] text-white px-6 h-full text-[13px] font-bold hover:opacity-90 transition-colors flex-shrink-0">Subscribe</button>

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 Restore a working subscription submit handler

For visitors who enter an email in the new "Please be in touch" block, the input and Subscribe button are not inside a form and neither control has an onSubmit/onClick handler or mutation wired up, so clicking Subscribe or pressing Enter does nothing and gives no validation/feedback. This replaces the previous landing-page contact flow that called REQUEST_USER_ACCESS_MUTATION, so the visible email capture is now a dead control.

Useful? React with 👍 / 👎.

Comment on lines +304 to +306
<li><Link href="/how-it-works" className="hover:text-white transition-colors">How It Works</Link></li>
<li><Link href="/pricing" className="hover:text-white transition-colors">Pricing</Link></li>
<li><Link href="/faq" className="hover:text-white transition-colors">FAQ</Link></li>

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 Replace footer links that route to 404s

For logged-out visitors using the new footer, these newly exposed internal links point to routes that do not exist in this commit; I checked quotevote-frontend/src/app pages and next.config.ts redirects, and there is no /how-it-works, /pricing, or /faq target. The same pattern repeats for several footer links below (/mission, /team, /blog, /press, /docs, /community, /contact), so users will hit 404s unless these are changed to existing pages or the pages are added.

Useful? React with 👍 / 👎.

Comment on lines 31 to 34
export function LandingPageContent({
totalRaised = '$500+',
progressPct = 50,
totalRaised: _totalRaised = '$500+',
progressPct: _progressPct = 50,
}: LandingPageContentProps) {

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 Stop fetching donation stats when they are unused

Because src/app/page.tsx still awaits fetchCollectiveStats() and passes totalRaised/progressPct into this component, aliasing both props to unused variables leaves the homepage waiting on the OpenCollective request on cache misses while rendering none of the result. On a slow or unavailable API this delays the root page solely for discarded data; either render the stats/progress again or remove the server fetch.

Useful? React with 👍 / 👎.

@motirebuma
motirebuma self-requested a review July 21, 2026 20:41

@motirebuma motirebuma left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Hi @Om7035 nice work, but this PR has merge conflicts and can't merge as-is. CI hasn't run. Beyond that, there are several issues that need to be resolved before this can move forward.

1. Images are duplicated. The same images appear in both public/assets/ and public/images/ (with identical filenames and @2x/@3x variants). That's ~220 retina image files that exist in two places. Pick one directory and remove the other.

2. Hardcoded inline styles — same issue from #406. The previous PR (#406) was given changes-requested specifically for this: use Tailwind classes or CSS custom properties instead of hardcoded hex values. This PR has the same problem:

  • text-[#1AAE5A], text-[#4F46E5], bg-[#EAF6F0], text-[#2A2A2A] etc. appear throughout
  • Inline style={{ background: '#1AAE5A' }} patterns

These colors should be added to the Tailwind config as named tokens (e.g., text-brand-green, bg-section-light) so they're consistent and maintainable.

3. Removes existing functionality without replacement. The old landing page had a search bar, featured posts carousel, animated counters, and interactive sections. This PR strips all of that and replaces it with static content. I know the zeplin design lacks this functionality So could you please add search functionality to the landing page,

4. Unused props. totalRaised and progressPct are renamed to _totalRaised and _progressPct to suppress unused-variable warnings. If these props aren't needed in the new design, remove them from the interface entirely instead of prefixing with underscore.

5. Unrelated changes bundled in. This PR also modifies:

  • SelectionPopover.tsx — removes topOffset from a useEffect dependency array
  • ChatList.test.tsx — adds an eslint-disable comment
  • ProfileHeaderMessage.test.tsx — fixes a mock pattern

These should be in their own PRs. Bundling unrelated fixes into a redesign PR makes it harder to review and harder to revert if something breaks.

6. Spaces in directory names. public/assets/all the group of characters/ — spaces in file paths cause problems with some build tools and CI environments. Use hyphens or camelCase.

7. Merge conflicts. The PR status shows CONFLICTING. Please rebase onto main and resolve conflicts before requesting review.

To summarize what's needed:

  • Resolve merge conflicts
  • deduplicate images
  • Move hardcoded colors into Tailwind config
  • Remove or separate unrelated changes
  • Search functionality (search/featured posts/counters)
  • Fix the directory naming

Verdict: changes requested.

Thank You @Om7035

@flyblackbox @Om7035

@flyblackbox

Copy link
Copy Markdown
Contributor

Okay good point @motirebuma I have solution.

This landing page will be Quote.Vote/about with a link that takes you directly to Quote.Vote.

When you land on Quote.Vote it should show the search box with the latest posts in chronological order. @Om7035 can you implement this or do you need better specifications or design?

Copy link
Copy Markdown
Contributor

@Om7035 this appears to be the more current candidate for completing #350, but it needs a narrower integration path before maintainers can evaluate it as the canonical homepage PR.

Could you please address or explicitly respond to the three unresolved review findings already attached to this PR:

  1. Restore a functioning submit handler and validation for the visible email subscription control.
  2. Replace or remove footer links that currently route to nonexistent pages.
  3. Remove the OpenCollective statistics fetch if those values remain unused, or render the data again.

The branch also has a large, currently non-mergeable diff. Please rebase it onto current main, resolve conflicts without reintroducing superseded migration code, and update the PR description with a concise list of the remaining #350 acceptance criteria.

@flyblackbox @motirebuma, once Om confirms that #431 contains the intended work from #406, could one of you designate #431 as the canonical implementation path? That decision would reduce duplicated review and give the contributor a stable target.

@Om7035

Om7035 commented Jul 25, 2026

Copy link
Copy Markdown
Collaborator Author

@flyblackbox #431
is the PR to be considered
i have closed the PR
and work on the issues and fix them

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.

Homepage Redesign (Zeplin Implementation)

4 participants