-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Cohorts section and content tweaks for Supporting Devs section #19
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
packages/nextjs/pages/index.tsx
Outdated
<span className="ml-2 font-bold"> | ||
{ | ||
// Calculation for Total Number of Hackers | ||
cohortsData?.reduce((acc, cohort) => acc + Object.keys(cohort.builders).length, 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can do this calculation in getStaticProps
and pass in totalHackers
:
// getStaticProps
return {
props: {
stats,
cohortsData,
totalHackers,
},
// 6 hours refresh.
revalidate: 21600,
};
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice suggestion! I've just updated all calculations to do them in getStaticProps
🙌
If I didn't do it in the right way, let me know please! 😅
packages/nextjs/pages/index.tsx
Outdated
@@ -209,37 +217,125 @@ const Home: NextPage<{ stats: Stats }> = ({ stats }) => { | |||
|
|||
{/* Supporting Devs*/} | |||
<div className="bg-base-300"> | |||
<div className="mx-auto lg:max-w-[1980px] bg-none lg:bg-[url('/assets/funding.png')] md:[background-position-x:40vw] md:bg-contain bg-no-repeat xl:bg-right"> | |||
<div className="mx-auto lg:max-w-[1980px] bg-none lg:bg-[url('/assets/support-high-impact-devs.png')] md:[background-position-x:45vw] [background-position-y:50%] md:bg-auto bg-no-repeat "> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was wondering if we should keep this full image similar to other section, also found in Figma we have it similar to the other section (lol maybe Andrea was tweaking a few things while I was viewing) :
But I think I like it how we have it for other sections.
Also noticed that for some reason website image looks a bit blurry :
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tried this section making similar to other sections at 07a8cde as discussed in TG :
But on screens b/w 1024 - 1180
it looks a bit weird since we have alot description in this section as compared to other sections :
Current section | Other similar section with less description |
---|---|
Screen.Recording.2023-09-20.at.7.35.55.PM.mov |
Screen.Recording.2023-09-20.at.7.36.38.PM.mov |
I have commented on your code below, lol was not sure which looks better maybe we could ask Andrea for suggestions too?
Here is the comparison links :
Current with new changes : https://buidlguidl-l2angsz0j-buidlguidldao.vercel.app/
Old one : https://buidlguidl-7ku1uzgrz-buidlguidldao.vercel.app/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for playing with it and proposing a new version, I prefer your approach ♥.
I'll ask Andrea too 🙌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tysm @Pabl0cks !!! Looks nice ! added few small comments 🙌
I think maybe you got this notion because daisy But yeah I think its fine we apply our own classes to table instead of relying on daisyUI v2 So its fine if we don't use daisyUI |
Thanks for the awesome review and explanations Shiv, and thanks for the research on daisyUI v2 I solved (or tried to!) all of the review issues except the Supporting Devs background that we discussed on TG. Let me know if you see anything else, or if any of my fixes does not have the correct approach 🙌 |
Tysm Pablo the changes looks great !! Just updated "supporting dev section" #19 (comment) was not sure which looks better so kept the previous one commented below because I kinda like that one too, we should remove either one before merging 🙌 One last thing (we could also maybe tackle this in another PR), regarding the Cohort section So maybe we should add this to "next iteration" of #19 (comment) :
|
Andrea saw OK current Tried adding it to not make table grow with more cohorts, but found myself with problems because of the I think we can work on it on a future iteration, yep 🙌 Added to the "For next iteration" section from PR description |
I've just added Cohort stats badges on mobile, let me know if you would change its appearance or see any other issue 🙌 Thanks a lot for the reviews, appreciate your patience with this task!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great !! Tysm Pablo 🙌
Amazing work @Pabl0cks and @technophile-04 !! |
Added Cohorts section and modified content from current Supporting Devs section according to figma prototypes and notion docs specifications.
Moving this PR to revision, specially to check this stuff that I'm not sure if it's implemented properly:
<table>
but then it didn't display the styles I tried to pass with tailwind classes, or withglobals.css
.tailwind.config.js
globals.css
There are some details pending to confirm, but the will be minor tweaks over the core changes that are currently implemented in this PR.
ToDos
For next iteration