Skip to content

Commit 2893e85

Browse files
authored
fix: revert back to bacbaf7 (#68)
# Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. Fixes # (issue) ## Type of change Please chose options that are not relevant. - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # How Has This Been Tested? Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration - [ ] Test A - [ ] Test B **Test Configuration**: - Firmware version: - Hardware: - Toolchain: - pnpm: # Checklist: - [ ] I have read the [Contributing Guidelines](https://github.com/OSCA-Kampala-Chapter/react-ui/blob/main/CONTRIBUTING.md) and made commit messages that follow the guideline. - [ ] I have run pnpm run test to check if all tests are passing, and/or pnpm run test -- -u to update snapshots if I created and/or updated React Components. - [ ] I have checked that the build works locally and that npm run build work fine. - [ ] I've covered new added functionality with unit tests if necessary. - [ ] I've included issue number in the "Closes #ISSUE-NUMBER" part of the "[What are the relevant tickets?](https://github.com/airqo-platform/AirQo-frontend/blob/staging/.github/PULL_REQUEST_TEMPLATE.md#what-are-the-relevant-tickets)" section to [link the issue.](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules ### How should this be manually tested? Please include the steps to be done inorder to setup and test this PR. ### What are the relevant tickets? Closes
2 parents fed946a + d5f8227 commit 2893e85

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

website/components/pages/landing/index.tsx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ function LandingPage() {
33
<>
44
<main className="relative flex flex-col items-center justify-center w-full h-full overflow-hidden [--geist-foreground:#fff] dark:[--geist-foreground:#000] [--gradient-stop-1:0px] [--gradient-stop-2:120px] sm:[--gradient-stop-1:0px] sm:[--gradient-stop-2:120px]">
55
<h1 className="mt-12 lg:!mt-20 mx-6 w-[300px] md:!w-full font-extrabold text-5xl lg:text-6xl leading-tight text-center mb-4 bg-clip-text text-transparent bg-gradient-to-b from-black/80 to-black dark:from-white dark:to-[#AAAAAA]">
6-
React UI
6+
React-UI
77
</h1>
88
<p className="mx-6 text-xl max-h-[112px] md:max-h-[96px] w-[315px] md:w-[660px] md:text-2xl font-space-grotesk text-center text-[#666666] dark:text-[#888888]">
99
The React Components Library

0 commit comments

Comments
 (0)