-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat(UI): Add Hero component #1336
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 181cbfd:
|
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.
Great Job! ✨
Do we have the starters' PRs already?
Co-authored-by: Eduardo Formiga <eduardo.formiga@gmail.com>
Thanks for reviewing! Just one starter PR in draft. I'll open it soonn ~ |
Co-authored-by: Filipe W. Lima <filipe.lima@vtex.com.br>
What's the purpose of this pull request?
This PR is part of the Component Placement project, to bring some components from our starters (gatsby.store/nextjs.store).
How it works?
The
Hero
component works together with its own wrapper components for each content's details:HeroImage
: the wrapper component for the hero's image;HeroHeading
: the wrapper component for the content (title, description and call to action link).How to test it?
Unit tests through Jest:
yarn test packages/ui/src/organisms/Hero/Hero.test.tsx
References
Component Placement - FSSS-351