Closed as not planned
Description
Continuing the migration of components from nodejs.dev
that we started here, we want to migrate a few other small Components that are used in a few pages but that don't really belong anywhere right now.
This issue will keep track of these components and their development progress.
The Migration of each Component
- Each Component has its sub-folder (e.g.,
components/Banner
) - The folder structure should pretty much be the same (CSS components, React, and sub-components), but feel free to make changes if you see deemed
- Please add some if the Component still needs to get unit tests. At least to ensure the Component is rendering. If the Component has states/CTAs (Buttons/Triggers), please cover them too.
- The Storybook of each component should allow interaction with all possible states of the Component
- If the Component depends on Hooks, please migrate them too, with the following caveat:
- If that component only uses the Hook, move it to the same folder of the Component
- Otherwise, migrate it to the
hooks
folder of the repository.
- If the Component has a Gatsby-specific logic (e.g.
Dark Theme Switcher
), if it is straightforward enough (e.g. a dark theme switcher plugin for Next.js or it is simple enough to code by ourselves, e.g. a Hook that we manage together with a React Provider) then feel free to do it.- Otherwise, if you have questions, please ask them on this Issue or your Draft PR for the Component.
List of Components to Migrate
-
NodeFeature
@AugustinMauroy- This Component should go under
components/Home
- This Component should go under
-
BlogCard
@Harkunwar- This Component should go under
components/Blog
- This Component should go under
-
Hero
@ktssr- This Component should be placed within
components/Home
- The
NodeReleasesData
type should be changed to the existing types we have for Node Release Data - Note to check if this issue still happens
- This Component requires Migrate
useDetectOs
hooks fromnodejs.dev
#5310 to be done first
- This Component should be placed within