Skip to content

Conversation

@taniandjerry
Copy link
Contributor

@taniandjerry taniandjerry commented Jun 12, 2025

This pull request introduces an exciting new landing page:

The home to our Public Events Calendar and Community Spotlight!

community.landing.page.mov

But that's not all...

The community spotlight has also become Community All Stars program!

This program is where EVERY contributor is highlighted, including team members across Block! Here's how:

Each month, the list of all contributors to the block/goose project are pulled from GitHub, and are then analyzed and populated into the following lists by goose & @taniashiba:

  1. Community Stars - This list consists of the top 5 contributors from the external community
  2. Team Stars - This list consists the top 5 contributors from the internal community, aka the goose team and any contributors from Block!
  3. Monthly Leaderboard - This lists consists of all contributors for the month, both internal and external members.

The best part? This landing page was made with help from goose!

This landing page is linked in the bottom nav bar currently.

To update this community landing page each month is relatively simple:

  1. Create new month file
  • Go to goose/documentation/src/data/community/
  • Copy template.json → rename to [month]-[year].json (e.g., june-2025.json)
  • Fill in the data:
    • communityStars: 5 external contributors (name + GitHub handle)
    • teamStars: 5 Block team contributors (name + GitHub handle)
    • leaderboard: All contributors ranked with medals for top 3
  1. Update config
  • Open config.json in same folder • Add new month to availableMonths array • Update defaultMonth to show new month by default
  1. Update community.tsx
  • Go to goose/documentation/src/pages/community.tsx and add the import for your new JSON file at the top, add it also to the communityDataMap object. For example:
    • Add import line: import june2025Data from "../data/community/june-2025.json"; •
    • Add to data map: "june-2025": june2025Data,
  1. Test & Deploy!

Quick Tips

  • Use GitHub handles - avatars will load automatically.
  • Use "handle": "TBD" for placeholders
  • Only top 3 get medals in the leaderboard 🥇🥈🥉
  • File naming: month-year.json format

That's basically it! You can also use goose to do this update in a commit, so long as you have the three lists mentioned above ( communityStars, teamStars, and leaderboard)

@taniandjerry taniandjerry self-assigned this Jun 12, 2025
@taniandjerry taniandjerry added the documentation Improvements or additions to documentation label Jun 12, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jun 12, 2025

PR Preview Action v1.6.0
Preview removed because the pull request was closed.
2025-06-16 21:34 UTC

@taniandjerry
Copy link
Contributor Author

Main help I could use other than general ♻️ review is the link label:
image

Currently, it's labeled Spotlight, and the url is block.github.io/goose/community. Which works well! But open to suggestions. It lives here because the top is already cluttered, and I don't want to take away from our top two links (to GitHub and Discord).

cc @angiejones @blackgirlbytes

@blackgirlbytes
Copy link
Contributor

I loooove thsi. This is a super nitpick, but the numbers/words for the to community ppl could have better contrast

Screenshot 2025-06-12 at 1 00 36 AM Screenshot 2025-06-12 at 1 00 44 AM

Copy link
Contributor

@agiuliano-square agiuliano-square left a comment

Choose a reason for hiding this comment

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

This page is FANTASTIC! I'm obsessed. It looks like Goose made some interesting decisions WRT implementation, so I think we can clean this up a bit, but it's all small things. Great job @taniashiba!

Copy link
Contributor

Choose a reason for hiding this comment

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

For consistency's sake, I think it might be better to create a "community" folder under "pages" and then put this "data" folder within that "community" folder. That way it will be structured the same way as the prompt-library folder.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ohhhhh gotcha! That's a good point, thank you Anthony!

"handle": "lily-de"
}
],
"leaderboard": [
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm curious where is this data being pulled from. I wonder if this can just be reduced to an array with each of the handles and then just use the order to determine the rank instead of having a separate "rank" field. That said, if the place you're pulling the data from structures it like this then I think it would be better to keep it as is.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The list of people was provided to goose, which consists of all GitHub handles that goose found! Except two people, which is where I provided an avatar URL from Discord.

The rank is provided in the list given to goose by me, so it is technically already ranked! I think goose added this in case I wanted to change someone's rank after the fact as I was working through it. 🤔

import Layout from "@theme/Layout";
import Heading from "@theme/Heading";

import styles from "./index.module.css";
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't believe this is actually used anywhere. Can probably get rid of it

Copy link
Contributor

Choose a reason for hiding this comment

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

we may have to make the commits for Tania since she doesn't code regularly!

Copy link
Contributor

Choose a reason for hiding this comment

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

Absolutely! I can take a stab at this. @taniashiba sorry to throw a bunch of comments at you! I wasn't sure what you're coding experience was like.

Copy link
Contributor Author

@taniandjerry taniandjerry Jun 12, 2025

Choose a reason for hiding this comment

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

Oh no worries at all, all comments welcome! I don't code regularly, but have a general working understanding I'd say. 😉 I do well with some guidance and pick up things faster than you'd think, I'd say! 🥺

I did work with goose to try to get rid of some of this fluff, because it kept what was no longer used from past iterations for sure!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank yall for taking the time <3 If you wouldn't mind, after your review together, would you be able to give me a list of general guidelines I could give to goose to avoid leaving random bloat & making weird choices to the layout styling? 🙏 I know if I can specifically state what to do vs what not to change, I can make future changes easier!

Copy link
Contributor

Choose a reason for hiding this comment

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

Of course! I think that's a great idea

return (
<section className="container margin-vert--lg">
<div className="row">
<div className="col col--12">
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like Goose made some interesting style decisions in this file. Based on what I've seen in other files in this directory, it looks like Tailwind is the prevailing styling method. I think the whole file could probably benefit from a pass at converting everything to tailwind. I'm happy to assist with this if you'd like

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah i think both of us can team up and convert this to following the site's styling and format.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That would be awesome! I tried to tell goose to use Tailwind actually, but goose just didn't change it. So I was like okay, let me leave it be for now I guess 🙏

avatar.style.transform = 'rotate(0deg)';
}
}}
>
Copy link
Contributor

Choose a reason for hiding this comment

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

These onMouse functions can probably be traded for hover effects. Tailwind should help with that.

style={{
display: 'flex',
alignItems: 'center',
padding: bgColor ? '12px' : '10px',
Copy link
Contributor

Choose a reason for hiding this comment

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

I know technically the bgColor indicates that this is a top 3 contributor, but semantically this doesn't quite read right to me. Maybe we create a separate variable to capture this and then style everything based on that variable.

Copy link
Contributor

Choose a reason for hiding this comment

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

true. good catch!

gap: '6px',
transition: 'opacity 0.3s ease'
}}>
Scroll for more ↓
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: could maybe use a background color here to improve readability

- Move community data files from src/data/community/ to src/pages/community/data/
- Rename community.tsx to community/index.tsx for better organization
- Consolidate community-related files under src/pages/community/
@agiuliano-square
Copy link
Contributor

Committed some changes to move to Tailwind. This is certainly not perfect, but I think it's passable for now. There are more changes I'd like to make in the future, but I think those will require larger refactors (i.e componentizing different elements, updating tailwind config, etc.) I'm happy to start to chip away at some of those refactors next quarter if folks would find that beneficial.

@blackgirlbytes feel free to take a pass at this if there is anything you don't like.

@blackgirlbytes
Copy link
Contributor

Committed some changes to move to Tailwind. This is certainly not perfect, but I think it's passable for now. There are more changes I'd like to make in the future, but I think those will require larger refactors (i.e componentizing different elements, updating tailwind config, etc.) I'm happy to start to chip away at some of those refactors next quarter if folks would find that beneficial.

@blackgirlbytes feel free to take a pass at this if there is anything you don't like.

hmm @agiuliano-square yeah there are a few things I want to fix but will take me a minute. I agree that tania could merge for now and then we do a refactor.

@taniandjerry taniandjerry requested review from agiuliano-square and blackgirlbytes and removed request for EbonyLouis and acekyd June 16, 2025 17:12
@taniandjerry
Copy link
Contributor Author

Committed some changes to move to Tailwind. This is certainly not perfect, but I think it's passable for now. There are more changes I'd like to make in the future, but I think those will require larger refactors (i.e componentizing different elements, updating tailwind config, etc.) I'm happy to start to chip away at some of those refactors next quarter if folks would find that beneficial.
@blackgirlbytes feel free to take a pass at this if there is anything you don't like.

hmm @agiuliano-square yeah there are a few things I want to fix but will take me a minute. I agree that tania could merge for now and then we do a refactor.

Thank you Rizel! I re-requested review from yall, then once it's merged the refactor can be done. Thank you so much for all your help 🥺

@taniandjerry
Copy link
Contributor Author

Made two minor CSS changes to format okay with 3 top stars vs 5, and then updated both month's team star lists. The leaderboard still includes the goose dev team and the devrel team because without them the leaderboard would be limited!

@taniandjerry taniandjerry merged commit 516e5fe into main Jun 16, 2025
8 checks passed
@taniandjerry taniandjerry deleted the community-landingpage branch June 16, 2025 21:33
btdeviant pushed a commit to btdeviant/goose that referenced this pull request Jun 25, 2025
Co-authored-by: Tania Chakraborty <[email protected]>
Co-authored-by: Anthony Giuliano <[email protected]>
s-soroosh pushed a commit to s-soroosh/goose that referenced this pull request Jul 18, 2025
Co-authored-by: Tania Chakraborty <[email protected]>
Co-authored-by: Anthony Giuliano <[email protected]>
Signed-off-by: Soroosh <[email protected]>
cbruyndoncx pushed a commit to cbruyndoncx/goose that referenced this pull request Jul 20, 2025
Co-authored-by: Tania Chakraborty <[email protected]>
Co-authored-by: Anthony Giuliano <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants