-
Notifications
You must be signed in to change notification settings - Fork 374
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.
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
feat: add r/docs/home #3160
feat: add r/docs/home #3160
Conversation
Signed-off-by: moul <[email protected]>
Signed-off-by: moul <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3160 +/- ##
==========================================
- Coverage 63.80% 63.79% -0.01%
==========================================
Files 549 549
Lines 78833 78833
==========================================
- Hits 50301 50294 -7
- Misses 25143 25149 +6
- Partials 3389 3390 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
Signed-off-by: moul <[email protected]>
Signed-off-by: moul <[email protected]>
Signed-off-by: moul <[email protected]>
Signed-off-by: moul <[email protected]>
Signed-off-by: moul <[email protected]>
We should have a "root" README for the I can help bootstrap these files if needed. They're meant to give context to the users about what the namespace is for. Also, all/most r/docs realms would correspond to a specific package, concept, usage; we should reference those when it makes sense; maybe as a |
Introducing the
r/docs
namespace, where the homepage currently lists subrealms manually. In the future, we may implement a registry, but for now, we’re keeping the source code as lean as possible. The namespace includes several interactive examples to guide users through key concepts.The
r/docs/hello
example provides a simple Render function and invites users to click on "view source" to understand the basics of customization. Ther/docs/avl_pager
example demonstrates path-based interactions, allowing users to explore an avl tree structure with pagination links to navigate between items. Users are encouraged to click on these links for inspiration before manually adjusting parameters in the URL. The addedr/docs/add
example introduces interactivity through transactions, allowing users to adjust a number by submitting transactions, and see the updated result with each interaction.These examples are designed to engage users with Render-based UI interactions, path handling, and transaction-based updates. Once we have more content in r/docs, this section could serve as the main documentation link in the navbar, providing a comprehensive, hands-on introduction to Gno.
Addresses #3084
Addresses https://github.com/gnolang/docs-v2/pull/27#discussion_r1848481556
Addresses #2953