docs: add getting started (alternative to #5519)

[davd-gzl]

Simple getting started documentation + quickstart to install and bootstrap a local environment, to the creation of a transaction on chain.
There's duplicate content from other documentation, I clean them in a follow-up -> #5656

Alternative to #5519

[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
    │       ├── 🔴 At least one of these user(s) reviewed the pull request: [aronpark1007 davd-gzl jefft0 notJoon omarsy MikaelVallenet] (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]

👍 Architecture LGTM. The funnel layering (Try first → TL;DR → Install → Build → Deploy) and the satellite split (#5551, #5552, #5553) is a good pattern.

A few UX points from #5519 that I think are worth carrying over before this lands, mostly newcomer-checkpoint stuff:

1. Verify step after install. gno version / gnokey version / gnodev --help (gnodev has no version subcommand) is the moment a newcomer confirms the toolchain is wired correctly. Without it, any error 5 minutes later leaves them unsure whether install actually succeeded.
2. Inline PATH warning. Currently delegated to install.md (docs: add dedicated installation page #5552), but the vast majority of "command not found" issues come from $(go env GOPATH)/bin (or $HOME/.gno/bin for the one-liner) not being on PATH. Worth a one-line :::info in the funnel itself: users who hit it won't be on the install page yet.
3. gnodev actionable instruction. "banner + http://localhost:8888" tells the user the binary runs, but not what to do next. Worth mentionning r/docs again?
4. Visual break before "Deploy to a shared network". A lot of newcomers stop at gnodev (and that's fine for a first session). A clear separator like --- + a "Ready to go live?" line gives them an explicit choice point.

I'll close #5519 as soon as this one comes out of DRAFT.

It might also be interesting to explore how to write for AI browsing (GEO) BTW (to keep in mind)

[alexiscolin]

You should mention your three other documents related to the PR, as they need to be merged to make sense. Otherwise, we will lose valuable knowledge.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[davd-gzl]

To answer #5592 (comment):

1. I'm waiting gnodev version to be merged, it is ready to be reviewed
2. Added. I consider installer.sh to install in $GOPATH/bin instead of .gno/bin to avoid shadowing binaries.
3. Added
4. Added

I think overall style can still be improved (some part don't looks very human friendly), but I'm open for first reviews @alexiscolin

About GEO I will do a deeper tour.

[davd-gzl]

I think I still need to make it more human friendly

[alexiscolin]

This is the strongest narrative onboarding doc the repo has had, and the dual-page structure (long-form getting-started + commands-only quickstart) is the right structural choice for UX-4 (#5462). Before merge, six blockers: four break the copy-paste promise, two make the contribution invisible/incoherent in production

[davd-gzl]

I removed the dependency to gnodev version for simpler merging

[alexiscolin]

Last factual cleanup before merge: CLA enforcement is disabled on all networks today. Reader hits this section, can't tell whether to expect the error. One-line :::info keeps the doc accurate without removing the section (so when CLA reactivates, the rest stays useful).

[alexiscolin]

Should we put something like :

  **CLA.** Some networks require contributors to acknowledge a
  [Contributor License Agreement](https://github.com/gnolang/gno/blob/master/CLA.md)
  before deploying. If `addpkg` fails with `has not signed the required CLA`,
  sign once at [`r/sys/cla`](https://gno.land/r/sys/cla) and retry.

  :::info
  CLA enforcement is currently **disabled** on all networks (`requiredHash == ""`). You only need this section
  if you actually see the error.
  :::

??

[alexiscolin]

Last factual cleanup before merge: CLA enforcement is disabled on all networks today. Reader hits this section, can't tell whether to expect the error. One-line :::info keeps the doc accurate without removing the section (so when CLA reactivates, the rest stays useful). See above

[davd-gzl]

Good idea @alexiscolin , fix: 8a96d09 + 294057e
Thank you so much! :)