-
Notifications
You must be signed in to change notification settings - Fork 1
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
docs: Create Welcome Page on Storybook #543
docs: Create Welcome Page on Storybook #543
Conversation
…ded Team members info, but still need social media links.
Gridiron Survivor Application
Project name: Gridiron Survivor Application
Project name: Gridiron Survivor Application
Only deployments on the production branch are activated automatically. If you'd like to activate this deployment, navigate to your deployments. Learn more about Appwrite Function deployments.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
stories/Welcome.mdx
Outdated
<a href="https://appwrite.io/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={appwriteLogo} /> | ||
<h3>Appwrite</h3> | ||
</a> | ||
<a href="https://blogrecorder.com/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={blogRecorderLogo} /> | ||
<h3>Blog Recorder</h3> | ||
</a> | ||
<a href="https://www.frontendmentor.io/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={frontendMentorLogo} /> | ||
<h3>Frontend Mentor</h3> | ||
</a> | ||
<a href="https://www.gitkraken.com/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={gitkrakenLogo} /> | ||
<h3>GitKraken</h3> | ||
</a> | ||
<a href="https://usepastel.com/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={pastelLogo} /> | ||
<h3>Pastel</h3> | ||
</a> |
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.
Feels like we could automate this a bit with a map array, where we have a list of objects with the sponsor name, sponsor link, and sponsor logo and loop through those. This would also make it easier to add future sponsors.
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.
100% agreed.
I did try to create something similar for the team member section, but was unsuccessful. I wish I wrote down what the exact error was, but @ryandotfurrer had helped me with it, so I doubt the problem was with how it was built.
That being said, I will take a look into map arrays tonight and see if I can get that built.
I ran into a handful of limitations while working on this. Not sure if it's a limitation of Storybook, the fact that it's a .mdx file, or a skill issue.
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.
Looking at [MDX docs])https://mdxjs.com/docs/using-mdx/#how-mdx-works), storybook array of objects, you might have to import it from a JSX or TSX file. I would be open to workshoping this with you sometime though.
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.
This is complete with my latest push.
stories/Welcome.mdx
Outdated
<div> | ||
<h4>Alex Appleget</h4> | ||
<p>Software Engineer</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/alexappleget" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/alex-appleget/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> | ||
<div class="team-member flex flex-col gap-2"> | ||
<div> | ||
<h4>Richard Choi</h4> | ||
<p>DevRel Engineer</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/choir27" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/richard-choir/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> | ||
<div class="team-member flex flex-col gap-2"> | ||
<div> | ||
<h4>Ryan Furrer</h4> | ||
<p>UX Engineer</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/ryandotfurrer" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/ryanfurrer/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> | ||
<div class="team-member flex flex-col gap-2"> | ||
<div> | ||
<h4>Walter Furrer</h4> | ||
<p>Documentation Engineer</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/FurrerW" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/furrerw/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> | ||
<div class="team-member flex flex-col gap-2"> | ||
<div> | ||
<h4>Shashi Lo</h4> | ||
<p>Engineering Manager</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/shashilo" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/shashilo/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> | ||
<div class="team-member flex flex-col gap-2"> | ||
<div> | ||
<h4>Corina Murg</h4> | ||
<p>Frontend Engineer</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/CorinaMurg" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/corinamurg/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> | ||
<div class="team-member flex flex-col gap-2"> | ||
<div> | ||
<h4>Chris Nowicki</h4> | ||
<p>Software Engineer</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/chris-nowicki" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/chris-nowicki/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> | ||
<div class="team-member flex flex-col gap-2"> | ||
<div> | ||
<h4>Mai Vang</h4> | ||
<p>Frontend Engineer</p> | ||
</div> | ||
<div> | ||
<a href="https://github.com/vmaineng" target="_blank" rel="noreferrer">GitHub</a> | ||
<a href="https://www.linkedin.com/in/mai-vang-swe/" target="_blank" rel="noreferrer">LinkedIn</a> | ||
</div> | ||
</div> |
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.
feels like we could automate this a bit with a map array, where we have a list of objects with the team member name, their role, and their links. It also makes it easier to add members. Also are we presenting the members in a particular order, like in alphabetical order or by role?
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.
Going to refer to my comment here: #543 (comment)
As far as presenting in a particular order, I went with alphabetical (last name). I am open to suggestions for the order, though.
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.
Refer to my response to my comment
I like alphabetical, but I would be open to other suggestions.
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.
I have this set as alphabetical, other than Shashi. Shashi will always appear first in the array.
stories/Welcome.mdx
Outdated
</a> | ||
</header> | ||
<section class="hero space-y-12"> | ||
<h1 class="pl-16">What is Gridiron Survivor?</h1> |
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.
How come we're not using mdx syntax?
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.
When I finally got to put my time back into this an re-commit myself to it, I found it easier to get it built in a way that I was more familiar with. I felt that in time I could create an issue for myself to refactor using mdx syntax, but I wanted to get a "finished" product first before worrying about that.
Please feel free to rip that thought process to threads if I should have taken the time to use mdx syntax and style it with their tools instead.
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.
While I admire the initiative to push this out as a PR to get feedback, we want to maintain consistency and syntax accuracy throughout docs and code. Please look at the MDX syntax to find out how to use it.
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.
I have re-written everything using MDX Syntax, in addition to React components for the Sponsors and Team Members section.
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.
I think we, as a team or Shashi + the Documentation Engineers need to discuss and decide where they want to use JSX/TSX Syntax and where they want to use MDX Syntax.
I propose using JSX/TSX with Tailwind for layout. Use MDX for content.
Thoughts?
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.
@choir27 Discussed in discord.
https://discord.com/channels/964903664265359430/1285782346997436529/1293598332794699878
Please resolve at your earliest convenience!
stories/Welcome.mdx
Outdated
<a href="https://appwrite.io/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={appwriteLogo} /> | ||
<h3>Appwrite</h3> | ||
</a> | ||
<a href="https://blogrecorder.com/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={blogRecorderLogo} /> | ||
<h3>Blog Recorder</h3> | ||
</a> | ||
<a href="https://www.frontendmentor.io/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={frontendMentorLogo} /> | ||
<h3>Frontend Mentor</h3> | ||
</a> | ||
<a href="https://www.gitkraken.com/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={gitkrakenLogo} /> | ||
<h3>GitKraken</h3> | ||
</a> | ||
<a href="https://usepastel.com/" target="_blank" rel="noreferrer" class="sponsor-card"> | ||
<Image src={pastelLogo} /> | ||
<h3>Pastel</h3> | ||
</a> |
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.
Looking at [MDX docs])https://mdxjs.com/docs/using-mdx/#how-mdx-works), storybook array of objects, you might have to import it from a JSX or TSX file. I would be open to workshoping this with you sometime though.
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.
@FurrerW great work so far! I'd reduce the logo down to just 1/3 of it's size. No need for a huge logo. Also, collapse the about and technical docs sections by default. |
…ith content below them.
#543 (review) @chris-nowicki Just fixed the indent issue. Should be good to go! |
…on Storybook to be collapsed by default.
Both requests are complete. |
- Finished adding new team members to the array, including social links. - Created FC for Sponsors section. Styled it. - Confirmed fonts and all sections look good on various breakpoints. - Opted to not include photos of team members for now. - Added link to our GitHub and the GIS website. - Styled similar to our website, but not dark mode. - There is some invisible padding that I cannot find out how to get rid of in Storybook. Will require more configuration. - Added some universal styling in styles.css, but most of the styling is done via Tailwind. - Moved assets from the stories folder to the public folder, as Storybook was not able to pull from the stories folder. - I tried messing with the config files to allow us to pull from the stories folder, but was unsuccessful.
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.
You have failing linting builds, please look into this. I also cannot pnpm run storybook
, I run into the following build error when running the command pnpm run storybook
: Error: Failed to load static files, no such directory: ./public/assets/* Make sure this directory exists.
This is located in your .storybook/main.ts file, please look into this and fix this.
stories/Sponsors.tsx
Outdated
className="transition-transform group-hover:scale-110" | ||
/> | ||
</div> | ||
<h6 className="pt-8 pb-0 text-center">{sponsor.name}</h6> |
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.
Q: Why is this h6 and not h3, h4, or h5?
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.
Does it need to go down incrementally? If so, I was not aware. I just wanted the sizing that h6 offered.
I am aware that siblings must be the same size or smaller if below the larger one, but I thought the rules were different if they were nested, as this h6 is nested in the Sponsors section.
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.
This needs to be an H3
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.
Fixed in the latest push.
stories/Sponsors.tsx
Outdated
className="transition-transform group-hover:scale-110" | ||
/> | ||
</div> | ||
<h6 className="pt-8 pb-0 text-center">{sponsor.name}</h6> |
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.
This needs to be an H3
stories/TeamMembers.tsx
Outdated
const sortedTeamMembers = [...TeamMembersArray].sort((a, b) => { | ||
// Put Shashi Lo first | ||
if (a.name === 'Shashi Lo') return -1; | ||
if (b.name === 'Shashi Lo') return 1; | ||
|
||
// For the rest, sort by last name | ||
const lastNameA = a.name.split(' ').pop() || ''; | ||
const lastNameB = b.name.split(' ').pop() || ''; | ||
return lastNameA.localeCompare(lastNameB); |
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.
Remove this functionality and keep the data static in order.
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.
Fixed in the latest push.
stories/TeamMembers.tsx
Outdated
}); | ||
|
||
return ( | ||
<div> |
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.
No classless divs. Give this a className of team-members
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.
Fixed in the latest push.
stories/TeamMembers.tsx
Outdated
<h2 className="pt-24 pb-8 text-center sm:text-left">Meet the Team</h2> | ||
<div className="team-members-container m-auto grid grid-cols-1 gap-y-8 sm:grid-cols-2 md:grid-cols-3 lg:grid-cols-4"> | ||
{sortedTeamMembers.map((member) => ( | ||
<div |
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.
nit: Make this into a component. Pass the props you need into it.
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.
Completed in the latest push.
… the TeamMember component into two componments, removed unnecessary comments, added/configured eslint, added jsdocs comments, fixed non-incremental <h> tags, correct alt spelling for GIS Logo on Welcome.mdx, fixed the storybook/static files directory issues.
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.
LGTM 🚀
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.
LGTM 🚀
<Image | ||
src={gridironLogo} | ||
alt="Gridiron Survivor Logo" | ||
className="block max-w-full m-auto py-8 justify-center" | ||
/> |
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.
NIT: How do you feel about linking to the Gridiron Survivor application URL upon the user clikcing on the logo?
Closes #246