docs: add editor setup guide

[davd-gzl]

Changes can be seen at: https://github.com/gnolang/gno/pull/5553/changes/0721d1a56c82bd9990150fe55353f1c8bb8408bd..01d038b35ae95533873b58a6e49e54412a43a24a

Depends on (must be merged before):

• docs: add getting started (alternative to #5519) #5592 (editor setup page linked from this guide)

[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: davd-gzl/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
    │       ├── 🟢 User notJoon already reviewed PR 5553 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[notJoon]

LGTM 👍

also related to: gnoverse/gnopls#39

[alexiscolin]

Since you worked on this, I'd love to get your opinion on this @gfanton.
The plugin list looks accurate and the structure is clean, but the page is missing the "show me, don't tell me" pieces that editor-setup guides typically lean on like:

• Screenshots of a working LSP. This is the biggest gap. A user finishes the setup with no way to know if it worked: autocomplete popup, hover info, diagnostics underline are all
  invisible from a CLI. Even one screenshot per officially supported editor changes the page.
• A concrete "did it work?" check. gnopls version only proves the binary runs. Add a stepwise check: "open a .gno file, type pri you should see println suggested". Same idea as a smoke test in install docs.
• The gnodev save-loop. Save .gno → gnodev hot-reloads → result in the browser is the killer Gno workflow. It also belongs in an editor-setup guide: at minimum a mention with a pointer?

These are additive, the page looks nice today, but each item beyond the screenshots gives a noticeable conversion lift on the "I want to be productive in 10 minutes" path no ?

[davd-gzl]

I've updated to add some of the propositions.
I've not yet added screenshot / visual clue (same for other documentation: getting started, cheatsheet, ...), and it should be added in a next work / this PR.

I added a next step for auto save + gnodev mention.

[moul]

This PR competes with the README of gnopls: https://github.com/gnoverse/gnopls.

I prefer to keep only gnopls' README as the main source of truth and reference the gnoverse repository from here.

[davd-gzl]

Per #5651 and #5553 (comment), I think we should close that PR and add a reference to gnopls documentation in #5552

Except if we make it step by step (as a comprehensive tutorial, which is not the current scope), this work don't add any real value.

If missing information, I will update gnopls documentation in a next work.

[davd-gzl]

After deeper thinking, it's better in my opinion to separate "installation" and "editor setup" in two documents as they have different utilities, but limit the strict necessary and official to this document, while the community and detailed setup to gnopls README.

davd-gzl@aa464e8

The new rewrite shouldn't compete anymore with the gnopls README.