feat(gnoweb): rework & Implement new gnoweb design

[gfanton]

address #3191

Reworking the gnoweb package:

• Implement gnoweb new interface design(cc @alexiscolin).
• Move Markdown rendering to the server to enhance speed and security. This change also simplifies the implementation of new components, making it more standardized as a Go library.
• Aim to keep dependencies minimal, using only goldmark for Markdown and chroma for code highlighting, with almost no (in)direct dependencies.
• Transition to Tailwind for simplicity and maintainability.
• Retain all features from the previous gnoweb iteration.

Preview

• Home
  

• Source
  

• Docs
  

TODO:

• port and adapt all previous tests to ensure compatibility (it should not take too long)
• Some cleanup and restructuring + linting.

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• SKIP: Do not block the CI for this PR
• Determine if infra needs to be updated before merging

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)
🟢 The pull request head branch must be up-to-date with its base (more info)

☑️ 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
└── 🟢 The pull request was created from a fork (head branch repo: gfanton/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

The pull request head branch must be up-to-date with its base (more info)

If

🟢 Condition met
└── 🟢 On every pull request

Then

🟢 Requirement satisfied
└── 🟢 Head branch (gfanton:feat/gnoweb-rework) is up to date with base (master): behind by 0 / ahead by 101

Manual Checks

**SKIP**: Do not block the CI for this PR

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

Determine if infra needs to be updated before merging

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: master
    └── 🟢 Or
        ├── 🔴 A changed file matches this pattern: Dockerfile
        ├── 🟢 A changed file matches this pattern: ^misc/deployments (filename: misc/deployments/staging.gno.land/docker-compose.yml)
        ├── 🔴 A changed file matches this pattern: ^misc/docker-
        ├── 🔴 A changed file matches this pattern: ^.github/workflows/releaser.*\.yml$
        └── 🔴 A changed file matches this pattern: ^.github/workflows/portal-loop\.yml$

Can be checked by

• team devops

[leohhhn]

Hey, please confirm with me directly before merging and updating the testX/portal loop gnoweb images; we will be sharing an announcement on social media about the new design revamp and we need to coordinate it. cc @sw360cab

[leohhhn]

We can just add a 2 liner on what gnoweb is along this:

gnoweb is a universal web frontend for the gno.land blockchain. It is built in Go, with xyz for doing xyz. It communicates with the remote RPC of a gno.land network to fetch data about realms and packages, ...

[gfanton]

I've updated it with a minimal description