docs: expand learning-resources.mdx with curated tutorials per 'Coming Soon' section. Addresses community demand for practical guides. Links to agents, Base Account, etc.#1479
Open
parado451 wants to merge 1 commit into
Conversation
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
Fits existing structure: No new top-level sections. The get-started/learning-resources page already exists and has a "Coming Soon" placeholder for updated tutorials, community-contributed resources, etc. This is a natural fit under Resources / Quickstart/Guides concepts.
Addresses real gaps: Docs emphasize AI-friendly, runnable content and cross-links. Community feedback and "Coming Soon" notes show demand for more practical learning paths (e.g., agents, smart accounts, mini-apps, tokens). Recent commits show active updates around agents, Builder Codes, notifications, etc., but learning resources lag.
Small, focused PR: One page update with links, short descriptions, and verification notes. Prioritizes happy path + cross-links.
Notes to reviewers
Consistent terminology (e.g., Base Account, OnchainKit, Agents).
AI-friendly: Explicit tool names, direct links, copy-paste friendly notes.
No new subsections proliferation; use lists/Tabs if needed.
Validates examples by selecting runnable/official ones.