refactor(WIP): gnoland home realm

[alexiscolin]

Related to #3249, This PR init the refactor of the gno.land homepage, focusing on content sections and design.

Related: Figma design file.

TODO:

• Columns are implemented in code but require feat(gnoweb): Add gno-columns extension #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 Columns component is merged, we should add a new Input component 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.

[Gno2D2]

🛠 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:

1. Fix any issues flagged by automated checks.
2. 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 CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

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 request

Pending 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
        └── 🟢 Not (🔴 This label is applied to pull request: review/triage-pending)

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[alexiscolin]

@leohhhn, should we consider an alternative method to AdminSetOverride for updating content, with future scalability in mind?

[alexiscolin]

@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.

[moul]

you should not remove these things, they are about allowing to have dynamic content on the homepage which is a target.

ps: you should also use some of them in the template code.

[alexiscolin]

@moul We plan to use them (dynamic parts) for other purpose (roadmap for ex).

[moul]

we should not use H2 just to make text bigger.

[alexiscolin]

I think it's a good idea to use it as an H2 for SEO purposes (not for text size).

[moul]

@leohhhn can you make this dynamic, i.e., by having like r/gnoland/blog to have a "news" tag?

[alexiscolin]

@moul OK, that's what I wrote above about the dynamic sections