Landing page [WIP]

[LanesGood]

Update landing page styles for Source.coop

---

Todo

• Ensure color changes are accurate throughout app (potentially have unique palette for landing page)
• Update product card settings for homepage (or update for whole app)
• Add interactive case study carousel
• Homepage specific footer - refine copyright (or update for whole app)
• Check all links and images
• Insert video in hero if available

[vercel]

@LanesGood is attempting to deploy a commit to the Radiant Earth Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
source-cooperative	Error		Mar 2, 2026 9:53pm

[jedsundwall]

@alukach FYI, this isn't building. LMK if you're able to troubleshoot why Vercel is failing.

[alukach]

@LanesGood there were some build errors (fixed via 322887f & 9cfa79b). You can test the build locally via npm run build (make sure docker compose up is also running).

[LanesGood]

@alukach thanks for the build fixes. This is getting close. FYI I did do a pretty big reshuffle to create route groups, simply to have a different layout page for the landing page, which avoids needing pathname detection in the top navigation (and ideally the footer). However, if this is overly complex and/or we want to simply update the navigation to follow the new proposed designs throughout the whole application, we could likely remove this route group update.

[LanesGood]

@alukach this is ready for review

[alukach]

This looks great 🎉 ! I've added @PowerChell and @jedsundwall for review and will defer to them for final say on aesthetics. A few things stand out to me:

1. Merge Conflicts: Looking like the merge may be painful. @LanesGood Can you bring in main to your branch (or maybe try to rebase on top of it?)

2. Globe Overflow: The dithered globe overflows out of the layout column on my screen by default. It also is a bit awkward in how it adjusts on variable viewport sizes.

   Screen.Recording.2026-02-17.at.2.31.38.PM.mov

3. Colors: @jedsundwall @PowerChell it would be good to get verification of colors. What stands out to me the most is changing the body background color (not header background), it's a little more tan in light mode and a little more blue in dark mode.

   Light - after
   

   Light - before
   

   Dark - after
   

   Dark - before
   

4. Products List It's not clear to me what is the significance of the different style for the first element ("Archive of data.gov") in the featured products list. Is that kind of like "ultra-featured"?
   

5. Homepage Link I'm unsure if back to the marketing page is the most appropriate place to link when authenticated users click on the Source logo from within the application. At this point we have the users as members of source.coop so marketing messaging may not be as valuable as a place where they could participate with source.coop. At the offsite, we discussed possible redirecting a user to their user profile. Alternatively, perhaps redirecting to /featured or /products. It's worth noting that both Vercel and Github serve/redirect-to a dashboard for / when a user is authenticated and use /home (1, 2) to make their marketing page accessible to authenticated users. I'm purely noting this as a pattern, I definitely don't think we need to mimic for the sake of mimicry; we don't currently have a dashboard element to claim the homepage today.

Note

I don't think we need to go off and make changes for all of the aforementioned thoughts. Rather, I think it makes sense for us to figure out which things should be left as is, which (if any) should be changed before merging this PR, and which (if any) should be changed in another PR.

[jedsundwall]

Looks amazing, @LanesGood! And thanks for starting the review like this, @alukach!

I'm off this week. Very open to comments from @PowerChell in the meantime. I'll add my review (maybe my own PR) next week, hopefully while en route to DC!

[LanesGood]

Thanks for the initial feedback @alukach. A few quick responses:

1. Yes, I can merge in main and deal with the conflicts. I think the vast majority here are caused by the new routing group sub-folder structure in this pr - hopefully you can chime in on whether this new nesting is OK for implementation
2. Globe - is your dithering conversion tool able to produce videos? I had hoped to swap this in.
3. Color palette - I attempted to make the color changes limited in scope to the landing page - looks like I need to fix that. For some reason it is working correctly locally for me (keeping the existing palette for all pages other than landing)
4. The first-item product styling is not from my pr - this exists in prod, and may just seem more (over-?) emphasized in this branch
5. Homepage link - defer to you all here, but I agree that a redirect to the user's own profile, or just the featured products page as currently exists, would be the right move.

[PowerChell]

I have a lot of thoughts! My comments are a mix of content feedback (perhaps more for Jed than Lane) and some design thoughts. FWIW, I met with Jen Marcus from Taylor Geospatial today and went through the page as is right now, and she both affirmed my thoughts and gave me some more perspective from someone who pretty closely fits our target market for the landing page.

1. I think Jed had Lane move the featured products up last time, but I think those should be back at the bottom of the landing page & redesigned (see my thoughts lower down). We will lose people quick if it dives into the data so fast, and especially just in the raw preview form.
2. The Challenge and Our Mission should go right after the first section, but make it more condensed. Perhaps side by side. Also, remove the duplicate Why Source headers. Can we combine that section with the Data publishing for everyone section? That section has a lot of unnecessary negative space under the title, and it would be great if we could condense the layouts better so that there is less unnecessary scrolling for the user
3. Conversation around docs being a separate site vs embedded in source.coop. I have less of a strong opinion about the technical docs, but I think about Source / FAQ sort of stuff really should be on the main Source website, since people who are first asking this question are coming to source.coop, not docs.source.coop. Even hyperlinking to the docs page can feel kind of clunky/less professional/confusing for certain site visitors who just want to better understand Source and want to feel like the website has all the information they are looking for.

• If it were totally up to me, I would put anything that's just learning about Source and the case studies under the source.coop site. Can we just embed the information on docs.source.coop somewhere on the source.coop page?
• Ive got a draft PR out for organizing the docs differently (about source, using source, case studies). if we want to keep all this information in the docs, we could add a button that says "more about source" or something that links to the "about source" section of the docs. We would still have a "read the docs" button that goes to either the general docs or the "using source" section

4. Featured products section redesign idea:

• (Workshopped this with Jen, and I think it's smart)
• Have our featured products be very intentionally chosen with our own verbiage, each product showcasing why it's special and why Source is valuable. This is our place to show why we need Source Cooperativ,e and we need to be using this opportunity more effectively
• Why not develop a more in-depth case study for each featured product that will be shown on the splash page? Then you can link to read more on it from there
• Have the logos in their section to have more visual appeal. With the FTW dataset, we would perhaps have multiple logos and explain how it's this greater collaboration between multiple entities. Right now, having the display be from Kerner Labs doesn't mean anything to most people. Its ofc fine for when you're logged in since that's where the data is hosted, but we can control the landing page more and therefore we should!

I'll stop there for now 😅

[LanesGood]

This needs approval for redeployment on Vercel.

I've fixed merge conflicts. Have looked through @PowerChell's review above, and did remove the duplicate section headers mentioned in item 2, but will assume I should wait on further discussions or signal on go-ahead from @jedsundwall and anyone else before implementing other changes to content, layout, etc.

[jedsundwall]

@alukach and @LanesGood I promise I'm going to look at this on Monday. Can either of you see why it's failing on deployment (I'm pretty sure it's not failing because it needs Vercel auth)?

[alukach]

@jedsundwall take a look at https://source-cooperative-git-feature-landing-page-radiantearth.vercel.app/

[alukach]

This needs to be moved to globals.css for the project to build successfully. Otherwise, we get:

Syntax error: Selector ":root, .light, .light-theme, .radix-themes" is not pure (pure selectors must contain at least one local class or id)

[alukach]

This looks good in day mode, but in night mode I think mix-blend-mode: color-dodge; is more natural:

[LanesGood]

@alukach agree with you on the globe mix mode. On the global styles, strangely this build error doesn't present locally for me. Keeping these variables on the landing page module is what allows me (on my local build) to see distinct color palette styles for the homepage vs the rest of the pages:

Homepage	Product page
Local	Local
Preview	Preview

[jedsundwall]

This is solid. Further comments coming on the PR to refine our look and feel over the coming weeks.

[jedsundwall]

Hi team: I think this is good to push live as it is now. A few notes on what I'd like us to work on separately in the future. We can probably create issues for these.

1. A new logo. I like where we're going with the new logo mark, but I want the lockup to be a bit "lighter."

2. We should dial in the different color schemes. I like where we're heading with things being a bit more off-white or off-black, but we should spend more time looking at the implications across the site.

3. I agree with Michelle on just about everything, but we should keep the data products up at the top. We need to add publisher logos to the data product cards, and we should work with the providers who we feature on the home page to make sure their titles and descriptions are exemplary.

4. We should create a three.js (or something like it) point cloud animation thing inspired by the 3D globe.

In the meantime, @alukach can you please help us get this live asap? Today if possible?