Skip to content

docs: add Getting Started section in features.mdx #394

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
syslog368 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add Getting Started section in features.mdx #394

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions pages/developers/intelligent-contracts/features/features.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,16 @@ import { Card, Cards } from 'nextra-theme-docs'
<Card title="🤖 Calling LLMs" href="calling-llms" />
<Card title="🌏 Web Access" href="web-access" />
</Cards>

## Getting Started with Intelligent Contracts

If you are new to GenLayer, follow this recommended order:

1. **[first-intelligent-contract.mdx](../first-intelligent-contract.mdx)** — Create your first Intelligent Contract
2. **[deploying.mdx](../deploying.mdx)** — Deploy on Bradbury Testnet
3. **[testing.mdx](../testing.mdx)** — Test your contract
4. **[debugging.mdx](../debugging.mdx)** — Fix errors and debug
Comment on lines +33 to +36
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Use descriptive text instead of filenames in link text.

The link text displays filenames like first-intelligent-contract.mdx, which is not user-friendly. The descriptive text that appears after the em-dash should be used as the link text instead.

✨ Proposed fix: improve link text for better UX 
-1. **[first-intelligent-contract.mdx](../first-intelligent-contract.mdx)** — Create your first Intelligent Contract
-2. **[deploying.mdx](../deploying.mdx)** — Deploy on Bradbury Testnet
-3. **[testing.mdx](../testing.mdx)** — Test your contract
-4. **[debugging.mdx](../debugging.mdx)** — Fix errors and debug
+1. **[Create your first Intelligent Contract](../first-intelligent-contract)**
+2. **[Deploy on Bradbury Testnet](../deploying)**
+3. **[Test your contract](../testing)**
+4. **[Fix errors and debug](../debugging)**
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
1. **[first-intelligent-contract.mdx](../first-intelligent-contract.mdx)** — Create your first Intelligent Contract
2. **[deploying.mdx](../deploying.mdx)** — Deploy on Bradbury Testnet
3. **[testing.mdx](../testing.mdx)** — Test your contract
4. **[debugging.mdx](../debugging.mdx)** — Fix errors and debug
1. **[Create your first Intelligent Contract](../first-intelligent-contract)**
2. **[Deploy on Bradbury Testnet](../deploying)**
3. **[Test your contract](../testing)**
4. **[Fix errors and debug](../debugging)**
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@pages/developers/intelligent-contracts/features/features.mdx` around lines 33
- 36, Replace the filename link text with the descriptive text after the em-dash
for each entry in features.mdx: change
"[first-intelligent-contract.mdx](../first-intelligent-contract.mdx)" to use
"Create your first Intelligent Contract" as the link text, similarly replace
"[deploying.mdx](../deploying.mdx)" with "Deploy on Bradbury Testnet",
"[testing.mdx](../testing.mdx)" with "Test your contract", and
"[debugging.mdx](../debugging.mdx)" with "Fix errors and debug" so the visible
links are user-friendly while keeping the same target paths.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify that the documentation files referenced in the Getting Started section exist

# Current file is at: pages/developers/intelligent-contracts/features/features.mdx
# Links use ../ so they should resolve to pages/developers/intelligent-contracts/

echo "Checking for linked documentation files..."
fd -t f -e mdx "^(first-intelligent-contract|deploying|testing|debugging)\.mdx$" pages/developers/intelligent-contracts/

Repository: genlayerlabs/genlayer-docs

Length of output: 401

🏁 Script executed:

cat -n pages/developers/intelligent-contracts/features/features.mdx | sed -n '1,40p'

Repository: genlayerlabs/genlayer-docs

Length of output: 2005

🏁 Script executed:

# Search for markdown link patterns in mdx files
rg '\]\([^)]*\.mdx\)' pages/ -A 0 -B 0 --max-count 10

Repository: genlayerlabs/genlayer-docs

Length of output: 621

🏁 Script executed:

# Search for markdown links to mdx files without the extension
rg '\]\(\.\./[a-z-]+\)' pages/ -A 0 -B 0 --max-count 10

Repository: genlayerlabs/genlayer-docs

Length of output: 52

🏁 Script executed:

# Find all markdown link patterns
rg '\]\([^)]*\)' pages/ -g '*.mdx' --max-count 5

echo "---"

# Check nextra configuration
fd -e js -e json -e ts . | xargs grep -l "nextra" 2>/dev/null | head -5

Repository: genlayerlabs/genlayer-docs

Length of output: 41054

Remove .mdx extensions from markdown links.

Lines 33-36 include .mdx file extensions in the links, which is inconsistent with the documentation convention throughout this codebase. All other markdown links use the format [text](../path/to/file) without the extension. Remove .mdx from both the link text and the path.

Proposed fix 
-1. **[first-intelligent-contract.mdx](../first-intelligent-contract.mdx)** — Create your first Intelligent Contract
-2. **[deploying.mdx](../deploying.mdx)** — Deploy on Bradbury Testnet
-3. **[testing.mdx](../testing.mdx)** — Test your contract
-4. **[debugging.mdx](../debugging.mdx)** — Fix errors and debug
+1. **[first-intelligent-contract](../first-intelligent-contract)** — Create your first Intelligent Contract
+2. **[deploying](../deploying)** — Deploy on Bradbury Testnet
+3. **[testing](../testing)** — Test your contract
+4. **[debugging](../debugging)** — Fix errors and debug
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
1. **[first-intelligent-contract.mdx](../first-intelligent-contract.mdx)** — Create your first Intelligent Contract
2. **[deploying.mdx](../deploying.mdx)** — Deploy on Bradbury Testnet
3. **[testing.mdx](../testing.mdx)** — Test your contract
4. **[debugging.mdx](../debugging.mdx)** — Fix errors and debug
1. **[first-intelligent-contract](../first-intelligent-contract)** — Create your first Intelligent Contract
2. **[deploying](../deploying)** — Deploy on Bradbury Testnet
3. **[testing](../testing)** — Test your contract
4. **[debugging](../debugging)** — Fix errors and debug
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@pages/developers/intelligent-contracts/features/features.mdx` around lines 33
- 36, The markdown links in the list (link texts and target paths like
"first-intelligent-contract.mdx", "deploying.mdx", "testing.mdx",
"debugging.mdx") include the ".mdx" extension; update each link to remove the
".mdx" from both the visible text and the URL so they become e.g.
[first-intelligent-contract](../first-intelligent-contract),
[deploying](../deploying), [testing](../testing), and [debugging](../debugging)
to match the project's link convention.


**Pro Tip:** Use **GenLayer Studio** in your browser for the fastest way to write, test and deploy contracts.

Need help? Join the Discord and ask in the `#dev-help` channel.