refactor(WIP): gnoland home realm
Related to #3249, This PR init the refactor of the gno.land homepage, focusing on content sections and design.
Related: Figma design file.
TODO:
- [x] Columns are implemented in code but require #3763 to be merged in order to appear in the UI.
- [ ] Images need to be added to the assets folder (WIP).
- [ ] Finalized content must be added.
- [ ]Β Once
Columnscomponent is merged, we should add a newInputcomponent to manage the airdrop tracker. - [ ] Add meta title and description
β οΈ Work in progress (WIP) with placeholder text, and the correct content still needs to be provided by the relevant counterparts in this PR.
π PR Checks Summary
All Automated Checks passed. β
Manual Checks (for Reviewers):
- [ ] IGNORE the bot requirements for this PR (force green CI check)
Read More
π€ This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.
β Automated Checks (for Contributors):
π’ Maintainers must be able to edit this pull request (more info) π’ Pending initial approval by a review team member, or review from tech-staff
βοΈ Contributor Actions:
- Fix any issues flagged by automated checks.
- Follow the Contributor Checklist to ensure your PR is ready for review.
- Add new tests, or document why they are unnecessary.
- Provide clear examples/screenshots, if necessary.
- Update documentation, if required.
- Ensure no breaking changes, or include
BREAKING CHANGEnotes. - Link related issues/PRs, where applicable.
βοΈ Reviewer Actions:
- Complete manual checks for the PR, including the guidelines and additional checks if applicable.
π Resources:
Debug
Automated Checks
Maintainers must be able to edit this pull request (more info)
If
π’ Condition met βββ π’ And βββ π’ The base branch matches this pattern: ^master$ βββ π’ The pull request was created from a fork (head branch repo: alexiscolin/gno)Then
π’ Requirement satisfied βββ π’ Maintainer can modify this pull requestPending initial approval by a review team member, or review from tech-staff
If
π’ Condition met βββ π’ And βββ π’ The base branch matches this pattern: ^master$ βββ π’ Not (π΄ Pull request author is a member of the team: tech-staff)Then
π’ Requirement satisfied βββ π’ If βββ π’ Condition β βββ π’ Or β βββ π΄ At least 1 user(s) of the organization reviewed the pull request (with state "APPROVED") β βββ π’ At least 1 user(s) of the team tech-staff reviewed pull request β βββ π’ This pull request is a draft βββ π’ Then βββ π’ And βββ π’ Not (π΄ This label is applied to pull request: review/triage-pending) βββ π’ At least 1 user(s) of the team tech-staff reviewed pull requestManual Checks
**IGNORE** the bot requirements for this PR (force green CI check)
If
π’ Condition met βββ π’ On every pull requestCan be checked by
- Any user with comment edit permission
@leohhhn, should we consider an alternative method to AdminSetOverride for updating content, with future scalability in mind?
@leohhhn, should we consider an alternative method to AdminSetOverride for updating content, with future scalability in mind?
I guess it should be ok, since Manfred updated the realm one week ago with this feature.
Removed the TODO content and this content from the PR, we can add it in later
We need to add the email subscription to the page as well @alexiscolin
This PR is stale because it has been open 3 months with no activity. Remove stale label or comment or this will be closed in 3 months.