docs: resolve documentation TODOs and add missing badges

README.md

@@ -121,7 +121,7 @@ repository.
   * tm2: [![codecov](https://codecov.io/gh/gnolang/gno/branch/master/graph/badge.svg?token=HPP82HR1P4&flag=tm2)](https://codecov.io/gh/gnolang/gno/tree/master/tm2)
   * gnovm: [![codecov](https://codecov.io/gh/gnolang/gno/branch/master/graph/badge.svg?token=HPP82HR1P4&flag=gnovm)](https://codecov.io/gh/gnolang/gno/tree/master/gnovm)
   * gno.land: [![codecov](https://codecov.io/gh/gnolang/gno/branch/master/graph/badge.svg?token=HPP82HR1P4&flag=gno.land)](https://codecov.io/gh/gnolang/gno/tree/master/gno.land)
-  * examples: TODO
+  * examples: [![codecov](https://codecov.io/gh/gnolang/gno/branch/master/graph/badge.svg?token=HPP82HR1P4&flag=examples)](https://codecov.io/gh/gnolang/gno/tree/master/examples)
 
   Go Report Card:
 

gno.land/cmd/gnoland/README.md

@@ -8,11 +8,6 @@ For **local development**, we recommend using [gnodev](../../../contribs/gnodev)
 
 ## Getting Started
 
-To run your own local gno.land node, follow this guide from the [gnops blog](https://gnops.io/):  
-👉 [Setting up a local Gno chain from scratch](https://gnops.io/articles/guides/local-chain/)
-
-**TODO:** Make this README self-sufficient so that we don’t depend on this blog.
-
 ### Install `gnoland`
 
 ```bash
@@ -21,12 +16,48 @@ cd gno/gno.land
 make install.gnoland
 ```
 
-### Run gnoland
+### Quick Start (Development Mode)
+
+For quick local testing, you can start a node with default settings:
 
 ```bash
 gnoland start -lazy -skip-genesis-sig-verification
 ```
 
+This command:
+- `-lazy`: Delays transaction execution for better development experience
+- `-skip-genesis-sig-verification`: Skips signature verification during genesis (development only)
+
+### Full Setup (Production Mode)
+
+For a production-like setup, initialize the configuration first:
+
+1. **Initialize configuration:**
+   ```bash
+   gnoland config init
+   ```
+   This creates the necessary configuration files in your data directory.
+
+2. **Initialize secrets (validator keys):**
+   ```bash
+   gnoland secrets init
+   ```
+
+3. **Start the node:**
+   ```bash
+   gnoland start
+   ```
+
+### Configuration
+
+The node configuration is stored in your data directory (default: `$HOME/.gnoland`). You can:
+
+- View configuration: `gnoland config get`
+- Update configuration: `gnoland config set <key> <value>`
+- Manage validator keys: `gnoland secrets get/verify`
+
+### Interacting with the Node
+
 Once running, you can interact with it using:
 - [gnokey](../gnokey) – CLI wallet & tool
 - [gnoweb](../gnoweb) – Web-based interface

gnovm/cmd/gno/README.md

@@ -46,4 +46,25 @@ Or
 
 ## Getting started
 
-TODO
+Once installed, you can use `gno` to develop and test Gno packages locally.
+
+**Quick examples:**
+
+```bash
+# Run a Gno file
+gno run main.gno
+
+# Test Gno packages
+gno test ./...
+
+# Format Gno code
+gno fmt ./...
+
+# Start an interactive REPL
+gno repl
+```
+
+For comprehensive guides on developing with Gno, see:
+- [Installing gno and developing locally with gnodev](../../../docs/builders/local-dev-with-gnodev.md)
+- [Writing Gno code](../../../docs/builders/anatomy-of-a-gno-package.md)
+- [Testing Gno](../../../docs/resources/gno-testing.md)