refactor : refactoring footer component #531
Conversation
This PR adds more accessibility to the hero section and also seo bost becuase search engine crawlers understand more the semantic html feat open-sauced#530
this pr refactor code inside the footer componenet and move the constant footercontext to seperate file inside the constants folder i have created to add more readibility to the code
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Issue Reference
In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.
Conventional Commit PR Title
In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass.
Most often, our PR titles are something like one of these:
- docs: correct typo in README
- feat: implement dark mode"
- fix: correct remove button behavior
Linting Errors
- Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"
- No subject found
✅ Deploy Preview for hot-sauced-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Description
This PR refactor the footer component by moving the footer context to separate file for more readability to components
Related Tickets & Documents
feat #532
Mobile & Desktop Screenshots/Recordings
N/A
Steps to QA
N/A
Tier (staff will fill in)
[optional] What gif best describes this PR or how it makes you feel?