feat: docs reorg #350

MSevey · 2024-04-23T14:34:18Z

Overview

Checklist

This PR reorganizes the docs based on some in person discussions.
Key points

Pull out guides into dedicated How To Guides section
Restructure tutorials from Beginner, Intermediate, Advance, to Rollkit, DA, Execution
Remove Recipe app and arabica

Summary by CodeRabbit

New Features
- Added a new "DA" section with tutorial links under the "Beginner" category.
- Introduced a "How To Guides" section with various tutorial links.
Documentation
- Renamed "Networks" to "Testnets" across various documents and updated corresponding links.
- Reorganized and updated tutorial links in multiple sections including "Beginner" (now "Rollkit") and "Intermediate."
- Updated image paths in cosmwasm-testnet.md to reflect new directory structure.
Bug Fixes
- Corrected tutorial version numbering and associated content in the GM world rollup series tutorials.

coderabbitai · 2024-04-23T14:34:27Z

Walkthrough

The updates primarily involve renaming sections and links to better reflect their content, reorganizing tutorials across different levels (beginner to intermediate), and introducing new tutorial sections. These changes enhance navigation and relevance of the documentation, ensuring users find the most appropriate resources efficiently.

Changes

File Path	Change Summary
`.vitepress/config.ts`	Renamed and reorganized sections, updated navigation links, added "How To Guides".
`learn/intro.md`	Updated the term "Networks" to "Testnets" and modified the corresponding link.
`testnets/cosmwasm-testnet.md`	Updated image paths for Faucet.
`tutorials/gm-world-mainnet.md` `tutorials/gm-world-mocha-testnet.md`	Corrected tutorial series part numbers and adjusted content accordingly.
`tutorials/overview.md`	Reorganized tutorial links and sections within Rollkit.
`guides/cw-orch.md`	Added a note and code snippet, adjusted formatting.
`learn/building-and-deploying-a-rollup.md` `tutorials/cosmwasm.md` `tutorials/gm-world-arabica-testnet.md` `tutorials/gm-world.md` `tutorials/polaris-evm.md` `tutorials/recipe-book.md` `tutorials/wordle.md`	Updated various links within the documents.

🐰✨
In the world of docs and codes,
A rabbit hopped and some paths it chose.
From networks wide to testnets neat,
With every jump, the docs complete.
Hop, hop, hurray! Changes are here,
Let's celebrate, with carrots near! 🥕🎉

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 93c647e and 52f8945.

Files selected for processing (10)

guides/cw-orch.md (2 hunks)
learn/building-and-deploying-a-rollup.md (1 hunks)
tutorials/cosmwasm.md (3 hunks)
tutorials/gm-world-arabica-testnet.md (1 hunks)
tutorials/gm-world-mainnet.md (2 hunks)
tutorials/gm-world-mocha-testnet.md (2 hunks)
tutorials/gm-world.md (2 hunks)
tutorials/polaris-evm.md (1 hunks)
tutorials/recipe-book.md (1 hunks)
tutorials/wordle.md (1 hunks)

Additional Context Used

LanguageTool (592)

guides/cw-orch.md (47)

Near line 2: Consider using a different verb to strengthen your wording.
Context: # Speed up your development with cw-orchestrator ...

Near line 5: This sentence does not start with an uppercase letter.
Context: ... with cw-orchestrator ## Introduction cw-orchestrator is the most advanced scripting, testing...

Near line 6: Possible spelling mistake found.
Context: ..., testing, and deployment framework for CosmWasm smart-contracts. It makes it easy to wr...

Near line 8: “you” seems less likely than “your” (belonging to you).
Context: ...ou interact with contracts and simplify you smart-contracts journey. The following ...

Near line 8: Possible spelling mistake found.
Context: ...owing steps will allow you to integrate cw-orch and write clean code such as: ```rust...

Near line 18: Consider a shorter alternative to avoid wordiness.
Context: ...ide, we will review the necessary steps in order to integrate [cw-orch](https://github.co...

Near line 18: Possible spelling mistake found.
Context: ...e necessary steps in order to integrate [cw-orch](https://github.com/AbstractSDK/cw-orc...

Near line 22: Two consecutive dots
Context: ...n everybody else, we suggest looking at a before-after rev...

Near line 24: Possible spelling mistake found.
Context: ...t to go more in depth, [browse the full cw-orch documentation](https://orchestrator.ab...

Near line 28: Consider using a different verb to strengthen your wording.
Context: ...rator.abstract.money/). ## Summary - [Speed up your development with cw-orchestrator](...

Near line 32: Possible spelling mistake found.
Context: ...gle-contract-integration) - [Adding cw-orch to your Cargo.toml file](#adding-cw-...

Near line 32: Possible spelling mistake found.
Context: ...ration) - [Adding cw-orch to your Cargo.toml file](#adding-cw-orch-to-your-cargotom...

Near line 35: Possible typo: you repeated a word
Context: ...(#interaction-helpers) - Using the integration - [Integration in a workspace](#integration-in-a-works...

Near line 44: Possible spelling mistake found.
Context: ...roughout this example, we will be using cw-orch to interact with a simple counter cont...

Near line 46: Possible spelling mistake found.
Context: ..., no matter the complexity. ### Adding cw-orch to your Cargo.toml file To use cw-o...

Near line 46: Possible spelling mistake found.
Context: ...mplexity. ### Adding cw-orch to your Cargo.toml file To use cw-orchestrator, you need...

Near line 48: Possible spelling mistake found.
Context: ...To use cw-orchestrator, you need to add cw-orch to your contract's TOML file. Run the ...

Near line 54: Possible spelling mistake found.
Context: ...tively, you can add it manually in your Cargo.toml file as shown below: ```toml [depende...

Near line 62: Possible missing comma found.
Context: ...ace code to not land in your WASM smart-contracts you need to target-flag it like so: ```...

Near line 96: Unpaired symbol: ‘]’ seems to be missing
Context: ...the interface creation specifics in the [cw-orch documentation](https://orchest...

Near line 106: This sentence does not start with an uppercase letter.
Context: ...act; > ``` ### Interaction helpers cw-orchestrator provides a additional macros that simpl...

Near line 107: The plural noun “macros” cannot be used with the article “a”. Did you mean “a additional macro” or “additional macros”?
Context: ...ction helpers cw-orchestrator provides a additional macros that simplify contract calls and querie...

Near line 107: Possible spelling mistake found.
Context: ...face for each variant of the contract's ExecuteMsg and QueryMsg. Enabling this functio...

Near line 107: Possible spelling mistake found.
Context: ...iant of the contract's ExecuteMsg and QueryMsg. Enabling this functionality is very ...

Near line 109: Possible spelling mistake found.
Context: ...lity is very straightforward. Find your ExecuteMsg and QueryMsg definitions (in `msg.rs...

Near line 109: Possible spelling mistake found.
Context: ...ightforward. Find your ExecuteMsg and QueryMsg definitions (in msg.rs in our exampl...

Near line 109: Possible spelling mistake found.
Context: ...in msg.rs in our example) and add the ExecuteFns and QueryFns derive macros to them l...

Near line 109: Possible spelling mistake found.
Context: ...r example) and add the ExecuteFns and QueryFns derive macros to them like below: ```...

Near line 142: Unpaired symbol: ‘]’ seems to be missing
Context: ...re about the interaction helpers in the [cw-orch documentation](https://orchest...

Near line 193: Possible spelling mistake found.
Context: ...ank">The full integration code with cw-orch added - <a href="https://github.com/co...

Near line 198: Possible spelling mistake found.
Context: ... When using workspaces, you need to add cw-orch to all crates that include `ExecuteMsg...

Near line 198: Possible spelling mistake found.
Context: ...dd cw-orch to all crates that include ExecuteMsg and QueryMsg used in your contracts ...

Near line 198: Possible spelling mistake found.
Context: ...ll crates that include ExecuteMsg and QueryMsg used in your contracts and derive the ...

Near line 198: Possible spelling mistake found.
Context: ...used in your contracts and derive theExecuteFnsandQueryFns` on them. Refer above t...

Near line 198: Possible spelling mistake found.
Context: ...ntracts and derive the ExecuteFns and QueryFns on them. Refer above to [Interaction ...

Near line 202: Possible spelling mistake found.
Context: ... on the cw20-base contract (where the QueryMsg are defined) as well as on the cw20 ...

Near line 202: Possible spelling mistake found.
Context: ...ell as on the cw20 package (where the ExecuteMsg are defined). ### Creating an interfa...

Near line 206: Consider a shorter alternative to avoid wordiness.
Context: ...or defining your contract's interfaces. In order to do that, use: ```shell cargo new inter...

Near line 206: Consider a more expressive alternative.
Context: ...your contract's interfaces. In order to do that, use: ```shell cargo new interfac...

Near line 213: Possible spelling mistake found.
Context: ...the interface package to your workspace Cargo.toml file ```toml [workspace] members = ["...

Near line 220: Did you mean “integrating”? Or maybe you should add a pronoun? In active voice, ‘advise’ + ‘to’ takes an object, usually a pronoun.
Context: ...nside this interface crate, we advise to integrate all your contracts 1 by 1 in separate f...

Near line 242: “you” seems less likely than “your” (belonging to you).
Context: ... Integrating single contracts Now that you workspace is setup, you can [integrate ...

Near line 242: The verb ‘set up’ is spelled as two words. The noun ‘setup’ is spelled as one.
Context: ...le contracts Now that you workspace is setup, you can [integrate with single contrac...

Near line 248: Possible spelling mistake found.
Context: ...-orchestrator` repo: - Some examples <a href="https://github.com/AbstractSDK/cw-orch...

Near line 249: Possible spelling mistake found.
Context: ... chains. - Some other examples show <a href="https://github.com/AbstractSDK/cw-orch...

Near line 251: Possible spelling mistake found.
Context: ...AL ADVICE**: Learn more and explore our <a href="https://orchestrator.abstract.money" t...

Near line 251: Possible spelling mistake found.
Context: ...or.abstract.money" target="blank" >full cw-orch documentation !.

learn/building-and-deploying-a-rollup.md (20)

Near line 1: Possible spelling mistake found.
Context: # 🗞️ Building a rollup and testnet deployment The following t...

Near line 1: Possible spelling mistake found.
Context: # 🗞️ Building a rollup and testnet deployment The following tutorials wil...

Near line 4: Possible spelling mistake found.
Context: ...DK and EVM applications that connect to Celestia's data availability (DA) layer via Roll...

Near line 5: Possible spelling mistake found.
Context: ...stia's data availability (DA) layer via Rollkit to Celestia's [Mocha testnet](https://d...

Near line 5: Possible spelling mistake found.
Context: ... availability (DA) layer via Rollkit to Celestia's [Mocha testnet](https://docs.celestia...

Near line 6: Possible spelling mistake found.
Context: ... layer via Rollkit to Celestia's [Mocha testnet](https://docs.celestia.org/nodes/mocha-...

Near line 7: Possible spelling mistake found.
Context: ...ia.org/nodes/mocha-testnet) or [Arabica devnet](https://docs.celestia.org/nodes/arabic...

Near line 7: Possible spelling mistake found.
Context: ...devnet). We call those chains Sovereign Rollups. You can get started with the followin...

Near line 13: This phrase is duplicated. You should probably use “GM world” only once.
Context: ...orials: ## 1. Beginner {#beginner} - GM world - GM world frontend...

Near line 16: Possible spelling mistake found.
Context: .../tutorials/recipe-book) - Restart your rollup ## 2️. Interm...

Near line 21: Possible spelling mistake found.
Context: ... - Wordle game - CosmWasm rollup ## 3️. Ad...

Near line 21: Possible spelling mistake found.
Context: ...le game](/tutorials/wordle) - CosmWasm rollup ## 3️. Advanced ...

Near line 25: Possible spelling mistake found.
Context: ...nced {#advanced} - [Full-stack modular dapp with Celestia](https://docs.celestia.or...

Near line 25: Possible spelling mistake found.
Context: ...anced} - [Full-stack modular dapp with Celestia](https://docs.celestia.org/developers/f...

Near line 29: Possible spelling mistake found.
Context: ... tutorials will explore developing with Rollkit, which is still in Alpha stage. If you ...

Near line 30: You might be missing the article “the” here.
Context: ...eloping with Rollkit, which is still in Alpha stage. If you run into bugs, please wri...

Near line 30: The official name of this software platform is spelled with a capital “H”.
Context: ...e. If you run into bugs, please write a Github [issue](https://github.com/rollkit/docs...

Near line 33: Possible spelling mistake found.
Context: ...tps://t.me/rollkit). Furthermore, while Rollkit allows you to build sovereign rollups o...

Near line 33: Possible spelling mistake found.
Context: ...e Rollkit allows you to build sovereign rollups on Celestia, it currently does not supp...

Near line 34: Possible spelling mistake found.
Context: ...llows you to build sovereign rollups on Celestia, it currently does not support fraud pr...

tutorials/cosmwasm.md (76)

Near line 1: Possible spelling mistake found.
Context: # 🗞️ CosmWasm rollup CosmWasm is a smart contracting...

Near line 1: Possible spelling mistake found.
Context: # 🗞️ CosmWasm rollup CosmWasm is a smart contracting platfo...

Near line 2: Possible spelling mistake found.
Context: # 🗞️ CosmWasm rollup CosmWasm is a smart contracting platform built f...

Near line 6: Possible spelling mistake found.
Context: ..., we will be exploring how to integrate CosmWasm with Celestia's [data availability laye...

Near line 6: Possible spelling mistake found.
Context: ...xploring how to integrate CosmWasm with Celestia's [data availability layer](https://doc...

Near line 8: Possible spelling mistake found.
Context: ...ia-works/data-availability-layer) using Rollkit. ::: tip This tutorial will explore de...

Near line 11: Possible spelling mistake found.
Context: ...s tutorial will explore developing with Rollkit, which is still in Alpha stage. If you ...

Near line 12: The official name of this software platform is spelled with a capital “H”.
Context: ...e. If you run into bugs, please write a Github [Issue ticket](https://github.com/rollk...

Near line 16: Possible spelling mistake found.
Context: ...e/rollkit). Learn how to restart your rollup. ::: ::: w...

Near line 20: Possible spelling mistake found.
Context: ...e script for this tutorial is built for Celestia's [Mocha testnet](https://docs.celestia...

Near line 21: Possible spelling mistake found.
Context: ...tutorial is built for Celestia's [Mocha testnet](https://docs.celestia.org/nodes/mocha-...

Near line 24: Possible spelling mistake found.
Context: ...testnet). ::: You can learn more about CosmWasm here...

Near line 27: Possible spelling mistake found.
Context: ...or this tutorial is one provided by the CosmWasm team for Nameservice purchasing. You c...

Near line 27: Possible spelling mistake found.
Context: ...s one provided by the CosmWasm team for Nameservice purchasing. You can check out the cont...

Near line 31: Possible spelling mistake found.
Context: ...ow to write the Rust smart contract for Nameservice is outside the scope of this tutorial. ...

Near line 32: After an expression of time at the start of a sentence, a comma is usually used.
Context: ...side the scope of this tutorial. In the future we will add more tutorials for writing ...

Near line 32: Possible spelling mistake found.
Context: ... we will add more tutorials for writing CosmWasm smart contracts for Celestia. ## 💻 Co...

Near line 33: Possible spelling mistake found.
Context: ...or writing CosmWasm smart contracts for Celestia. ## 💻 CosmWasm dependency installatio...

Near line 35: Possible spelling mistake found.
Context: ...sm smart contracts for Celestia. ## 💻 CosmWasm dependency installations {#dependencies...

Near line 39: Possible spelling mistake found.
Context: ...s tutorial, we will be using curl and jq as helpful tools. You can follow the g...

Near line 52: Possible spelling mistake found.
Context: ...t installation {#install-rust} #### 🔨 Rustup {#rustup} First, before installing Rus...

Near line 54: Possible spelling mistake found.
Context: ...talling Rust, you would need to install rustup. On Mac and Linux systems, here are t...

Near line 82: The verb ‘set up’ is spelled as two words. The noun ‘setup’ is spelled as one.
Context: ...stallation, follow the commands here to setup Rust. ```bash rustup default stable ca...

Near line 116: Possible spelling mistake found.
Context: ...ocs.docker.com/engine/install). ### 💻 Wasmd installation {#wasmd-installation} Her...

Near line 118: Possible spelling mistake found.
Context: ...n} Here, we are going to pull down the wasmd repository and replace CometBFT with R...

Near line 118: Possible spelling mistake found.
Context: ...down the wasmd repository and replace CometBFT with Rollkit. Rollkit is a drop-in repl...

Near line 119: Possible spelling mistake found.
Context: ...tory and replace CometBFT with Rollkit. Rollkit is a drop-in replacement for CometBFT t...

Near line 119: Possible spelling mistake found.
Context: ...t. Rollkit is a drop-in replacement for CometBFT that allows Cosmos-SDK applications to ...

Near line 120: Possible spelling mistake found.
Context: ...s Cosmos-SDK applications to connect to Celestia's data availability network. ```bash g...

Near line 139: Possible spelling mistake found.
Context: ...) } ``` This is a temporary fix until [CosmWasm/wasmd#1785](https://github.com/CosmWasm...

Near line 139: Possible spelling mistake found.
Context: ...This is a temporary fix until [CosmWasm/wasmd#1785](https://github.com/CosmWasm/wasmd...

Near line 149: Possible spelling mistake found.
Context: ...l ``` ::: tip You will have to install gcc if you are trying it on a clean linux ...

Near line 149: Possible spelling mistake found.
Context: ...l gcc if you are trying it on a clean linux vm. ::: ### ✨ Celestia node {#celestia...

Near line 152: Possible spelling mistake found.
Context: ...ying it on a clean linux vm. ::: ### ✨ Celestia node {#celestia-node} You will need a ...

Near line 155: Possible spelling mistake found.
Context: ...node running with test tokens on [Mocha testnet](https://docs.celestia.org/nodes/mocha-...

Near line 155: Consider a shorter alternative to avoid wordiness.
Context: .../docs.celestia.org/nodes/mocha-testnet) in order to complete this tutorial. Complete [the t...

Near line 167: Possible spelling mistake found.
Context: ... ## 🌌 Setting up your environment for CosmWasm on Celestia {#setting-up-environment-on...

Near line 167: Possible spelling mistake found.
Context: ...ing up your environment for CosmWasm on Celestia {#setting-up-environment-on-celestia} ...

Near line 169: Possible spelling mistake found.
Context: ...ng-up-environment-on-celestia} Now the wasmd binary is built, we need to setup a lo...

Near line 169: The verb ‘set up’ is spelled as two words. The noun ‘setup’ is spelled as one.
Context: ...the wasmd binary is built, we need to setup a local network that communicates betwe...

Near line 170: Possible spelling mistake found.
Context: ...local network that communicates between wasmd and Rollkit. ### 🗞️ Initializing Cos...

Near line 170: Possible spelling mistake found.
Context: ...k that communicates between wasmd and Rollkit. ### 🗞️ Initializing CosmWasm rollup ...

Near line 172: Possible spelling mistake found.
Context: ...smd` and Rollkit. ### 🗞️ Initializing CosmWasm rollup with a bash script {#initialize-...

Near line 172: Possible spelling mistake found.
Context: ...Rollkit. ### 🗞️ Initializing CosmWasm rollup with a bash script {#initialize-rollup}...

Near line 186: Possible spelling mistake found.
Context: ... our init.sh script to initialize our CosmWasm rollup. You can view the contents of t...

Near line 187: Possible spelling mistake found.
Context: ...t.sh` script to initialize our CosmWasm rollup. You can view the contents of the scri...

Near line 190: Possible spelling mistake found.
Context: ...the script to see how we initialize the CosmWasm Rollup. You can initialize the script ...

Near line 190: Possible spelling mistake found.
Context: ...t to see how we initialize the CosmWasm Rollup. You can initialize the script with th...

Near line 198: Possible spelling mistake found.
Context: ...sh bash init.sh ``` With that, we have kickstarted our wasmd network! View your rollup ...

Near line 198: Possible spelling mistake found.
Context: ...``` With that, we have kickstarted our wasmd network! View your rollup by [finding...

Near line 200: Possible spelling mistake found.
Context: ...started our wasmd network! View your rollup by [finding your namespace or account C...

Near line 201: Possible spelling mistake found.
Context: ...p by finding your namespace or account Celenium. [View the examp...

Near line 203: Possible spelling mistake found.
Context: ...ttps://celenium.io). [View the example rollup's namespace on Celenium](https://celeni...

Near line 203: Possible spelling mistake found.
Context: ...[View the example rollup's namespace on Celenium](https://celenium.io/namespace/00000000...

Near line 203: Unpaired symbol: ‘[’ seems to be missing
Context: ...e example rollup's namespace on Celenium](https://celenium.io/namespace/000000000...

Near line 208: Possible spelling mistake found.
Context: ...ection, but it is important to know how Rollkit is initializing the cosmwasm rollup. V...

Near line 208: Possible spelling mistake found.
Context: ...to know how Rollkit is initializing the cosmwasm rollup. View the script [here](https:/...

Near line 208: Possible spelling mistake found.
Context: ...ow Rollkit is initializing the cosmwasm rollup. View the script [here](https://github...

Near line 213: Possible spelling mistake found.
Context: ...init.sh). ## 📒 Contract deployment on CosmWasm with Rollkit {#contract-deployment-on-c...

Near line 213: Possible spelling mistake found.
Context: ...📒 Contract deployment on CosmWasm with Rollkit {#contract-deployment-on-cosmwasm} ###...

Near line 217: Possible spelling mistake found.
Context: ...the following commands to pull down the Nameservice smart contract and compile it: ```bash...

Near line 227: Possible spelling mistake found.
Context: ... The compiled contract is outputted to: target/wasm32-unknown-unknown/release/cw_nameservice.wasm. ### 🧪 Unit tests {#unit-tests}...

Near line 232: Possible spelling mistake found.
Context: ...do so with the following command in the ~/cw-contracts/contracts/nameservice directory: ```bash cargo unit-test ``...

Near line 241: Possible spelling mistake found.
Context: ...eploying the compiled smart contract to wasmd, we want it to be as small as possible...

Near line 245: Possible spelling mistake found.
Context: ... The CosmWasm team provides a tool called `rust-optim...

Near line 246: Consider a shorter alternative to avoid wordiness.
Context: ...requires Docker in order to compile.  Run the following command in the ~/cw-contracts/contracts/nameservice directory: ::: code-group ```bash [A...

Near line 270: Possible spelling mistake found.
Context: ...::: This will place the optimized Wasm bytecode at artifacts/cw_nameservice.wasm. ##...

Near line 270: Possible spelling mistake found.
Context: ...ll place the optimized Wasm bytecode at artifacts/cw_nameservice.wasm. ### 🚀 Contract deployment {#co...

Near line 275: Consider a shorter alternative to avoid wordiness.
Context: ... Let's now deploy our smart contract! In order to deploy a contract, you can use the comm...

Near line 280: Possible spelling mistake found.
Context: ...cw-orch.md). Run the following in the ~/cw-contracts/contracts/nameservice directory: ::: code-group  Now you’re ready to implement the AppendRecipe function at the top of the file above ...

Near line 266: Possible spelling mistake found.
Context: ...function at the top of the file aboveGetRecipeCountandSetRecipeCount`: ```go title="re...

Near line 266: Possible spelling mistake found.
Context: ... of the file above GetRecipeCount and SetRecipeCount: ```go title="recipes/x/recipes/keepe...

Near line 298: Possible spelling mistake found.
Context: ...ransaction that contains a message type MsgCreateRecipe is broadcast, the message is routed to...

Near line 299: An apostrophe may be missing.
Context: ...broadcast, the message is routed to the recipes module. - k.CreateRecipe calls `Appe...

Near line 301: This sentence does not start with an uppercase letter.
Context: ...the recipes module. - k.CreateRecipe calls AppendRecipe, which gets the recipe c...

Near line 301: Possible spelling mistake found.
Context: ...cipes module. - k.CreateRecipe calls AppendRecipe, which gets the recipe count, adds a r...

Near line 308: Consider a shorter alternative to avoid wordiness.
Context: ... ### 🖥 Query recipes {#query-recipes} In order to query your recipes, scaffold a query wi...

Near line 352: Consider a shorter alternative to avoid wordiness.
Context: ...ta1.PageResponse pagination = 2; } ``` In order to implement recipe querying logic in `rec...

Near line 413: Possible spelling mistake found.
Context: ...MD013 --> ## 👩‍🍳 Running the recipes rollup {#running-recipes-rollup} ### ✨ Run a ...

Near line 415: Possible spelling mistake found.
Context: ... {#running-recipes-rollup} ### ✨ Run a Celestia light node {#run-celestia-light-node} ...

Near line 417: Possible spelling mistake found.
Context: ... instructions to install and start your Celestia Data Availability layer Light Node sele...

Near line 418: Possible spelling mistake found.
Context: ... layer Light Node selecting the Arabica Devnet. You can find instructions to install a...

Near line 421: Possible spelling mistake found.
Context: ...e Go and Ignite CLI installed, and your Celestia Light Node running on your machine, you...

Near line 423: Possible spelling mistake found.
Context: ...ld, test, and launch your own sovereign rollup. Be sure you have initialized your nod...

Near line 430: Possible spelling mistake found.
Context: ...e#keys-and-wallets) and fund it with a [testnet tokens](https://docs.celestia.org/nodes...

Near line 439: Possible spelling mistake found.
Context: ...e Go and Ignite CLI installed, and your Celestia Light Node running on your machine, you...

Near line 441: Possible spelling mistake found.
Context: ...ld, test, and launch your own sovereign rollup. ### 🗞️ Start the recipes rollup {#st...

Near line 443: Possible spelling mistake found.
Context: ...eign rollup. ### 🗞️ Start the recipes rollup {#start-recipes-rollup} We have a hand...

Near line 458: Possible spelling mistake found.
Context: ...it.sh` script to initialize our Recipes Rollup. You can view the contents of the scri...

Near line 461: Possible spelling mistake found.
Context: ...pt to see how we initialize the Recipes Rollup. 🟢 From your project working director...

Near line 469: Possible spelling mistake found.
Context: ...sh bash init.sh ``` With that, we have kickstarted our recipesd network! ![recipe-start...

Near line 469: Possible spelling mistake found.
Context: ...``` With that, we have kickstarted our recipesd network! ![recipe-start.gif](/recipes...

Near line 474: Possible spelling mistake found.
Context: ...ress on an Arabica explorer to see your PayForBlobs transactions](https://explorer.modular...

Near line 476: Possible spelling mistake found.
Context: ...ia-arabica/transactions). Open another teminal instance. Now, create your first recipe...

Near line 490: Consider removing “of” to be more concise
Context: ...CLI {#query-recipes-with-cli} To query all of the on-chain recipes: ```bash recipesd q r...

Near line 498: Possible spelling mistake found.
Context: ...ve now successfully built a recipe book rollup.

tutorials/wordle.md (126)

Near line 5: Possible spelling mistake found.
Context: ... tutorial guide will go over building a cosmos-sdk app for Rollkit, the Sovereign-Rollup i...

Near line 6: Possible spelling mistake found.
Context: ...l go over building a cosmos-sdk app for Rollkit, the Sovereign-Rollup implementation of...

Near line 6: Possible spelling mistake found.
Context: ...lding a cosmos-sdk app for Rollkit, the Sovereign-Rollup implementation of CometBFT, for the pop...

Near line 6: Possible spelling mistake found.
Context: ... the Sovereign-Rollup implementation of CometBFT, for the popular game [Wordle](https://...

Near line 9: The verb ‘set up’ is spelled as two words. The noun ‘setup’ is spelled as one.
Context: ...ml). This tutorial will go over how to setup Rollkit in the Ignite CLI and use it to...

Near line 9: Possible spelling mistake found.
Context: ...This tutorial will go over how to setup Rollkit in the Ignite CLI and use it to build t...

Near line 16: Possible spelling mistake found.
Context: ...s tutorial will explore developing with Rollkit, which is still in Alpha stage. If you ...

Near line 17: You might be missing the article “the” here.
Context: ...eloping with Rollkit, which is still in Alpha stage. If you run into bugs, please wri...

Near line 17: The official name of this software platform is spelled with a capital “H”.
Context: ...e. If you run into bugs, please write a Github [Issue ticket](https://github.com/rollk...

Near line 21: Possible spelling mistake found.
Context: ...e/rollkit). Learn how to restart your rollup. ::: ::: w...

Near line 25: Possible spelling mistake found.
Context: ...e script for this tutorial is built for Celestia's [Arabica devnet](https://docs.celesti...

Near line 26: Possible spelling mistake found.
Context: ...torial is built for Celestia's [Arabica devnet](https://docs.celestia.org/nodes/arabic...

Near line 37: Unpaired symbol: ‘’ seems to be missing
Context: ...rld * Recipe Book or [Blog and Mo...

Near line 37: Unpaired symbol: ‘]’ seems to be missing
Context: ...Recipe Book](/tutorials/recipe-book) or [Blog and Module Basics](https://docs.ign...

Near line 38: Possible spelling mistake found.
Context: ...://docs.ignite.com/guide/blog/intro) * [Nameservice Tutorial](https://docs.ignite.com/v0.25...

Near line 41: Consider a shorter alternative to avoid wordiness.
Context: ...ge) You do not have to do those guides in order to follow this Wordle tutorial, but doing ...

Near line 58: Possible missing comma found.
Context: ...ght means it’s a correct letter for the Wordle included in the wrong position. A grey ...

Near line 59: Possible spelling mistake. ‘grey’ is British English.
Context: ...ordle included in the wrong position. A grey highlight means the letter isn’t part o...

Near line 78: Possible spelling mistake found.
Context: ...ment. ## ⛓️ Ignite and scaffolding the wordle chain {#ignite-scaffold-wordle-chain} <...

Near line 83: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...--> ### 🔥 Ignite {#ignite} Ignite is an amazing CLI tool to help us get started buildin...

Near line 84: Possible spelling mistake found.
Context: ...tarted building our own blockchains for cosmos-sdk apps. It provides lots of power tooling...

Near line 85: Possible spelling mistake found.
Context: ...mos-sdk apps. It provides lots of power toolings and scaffoldings for adding messages, t...

Near line 85: Possible spelling mistake found.
Context: ... It provides lots of power toolings and scaffoldings for adding messages, types, and modules...

Near line 86: Possible spelling mistake found.
Context: ...ages, types, and modules with a host of cosmos-sdk libraries provided. You can read more ...

Near line 97: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...ocal/bin/ ``` This installs Ignite CLI in your local machine. This tutorial uses ...

Near line 98: The operating system from Apple is written “macOS”.
Context: ...our local machine. This tutorial uses a MacOS but it should work for Windows. For Win...

Near line 98: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ocal machine. This tutorial uses a MacOS but it should work for Windows. For Windows...

Near line 111: Possible missing comma found.
Context: ...p ``` You should see an output of help commands meaning Ignite was installed successful...

Near line 114: Possible spelling mistake found.
Context: ...d successfully! ### ⛓️ Scaffolding the wordle chain {#scaffolding-wordle-chain} Now,...

Near line 129: The verb ‘set up’ is spelled as two words. The noun ‘setup’ is spelled as one.
Context: ... We first run the following command to setup our project for our new blockchain, Wor...

Near line 136: Possible spelling mistake found.
Context: ... scaffolds a new chain directory called wordle in your local directory from which you...

Near line 150: Possible spelling mistake found.
Context: ...l directories and architecture for your cosmos-sdk blockchain. | File/directory | Purpose...

Near line 152: Possible typo: you repeated a whitespace
Context: ... blockchain. | File/directory | Purpose | | -------------- | -------------------...

Near line 154: Possible typo: you repeated a whitespace
Context: ...------------------------------- | | app/ | Files that wire together the blockchai...

Near line 154: You might be missing the article “the” here.
Context: ...mportant file is app.go that contains type definition of the blockchain and functi...

Near line 155: Possible typo: you repeated a whitespace
Context: ...ns to create and initialize it. | | cmd/ | The main package responsible for the C...

Near line 155: Possible typo: you repeated a whitespace
Context: ...onsible for the CLI of compiled binary. | | docs/ | Directory for proje...

Near line 156: Possible typo: you repeated a whitespace
Context: ... | | docs/ | Directory for project documentation. B...

Near line 156: Possible spelling mistake found.
Context: ...r project documentation. By default, an OpenAPI spec is generated. ...

Near line 156: Possible typo: you repeated a whitespace
Context: ... default, an OpenAPI spec is generated. | | proto/ | Protocol buffer fil...

Near line 157: Possible typo: you repeated a whitespace
Context: ... | | proto/ | Protocol buffer files describing the d...

Near line 157: Possible typo: you repeated a whitespace
Context: ...er files describing the data structure. | | testutil/ | Helper functions fo...

Near line 158: Possible spelling mistake found.
Context: ... | | testutil/ | Helper functions for testing. ...

Near line 158: Possible typo: you repeated a whitespace
Context: ... | | testutil/ | Helper functions for testing. ...

Near line 158: Possible typo: you repeated a whitespace
Context: ...l/ | Helper functions for testing. | | vue/ | A Vue 3 web app tem...

Near line 159: Possible spelling mistake found.
Context: ... | | vue/ | A Vue 3 web app template. ...

Near line 159: Possible typo: you repeated a whitespace
Context: ... | | vue/ | A Vue 3 web app template. ...

Near line 159: Possible typo: you repeated a whitespace
Context: .../ | A Vue 3 web app template. | | x/ | Cosmos SDK modules ...

Near line 160: Possible typo: you repeated a whitespace
Context: ... | | x/ | Cosmos SDK modules and custom modules....

Near line 160: Possible typo: you repeated a whitespace
Context: ... Cosmos SDK modules and custom modules. | | config.yml | A configuration fil...

Near line 161: Possible typo: you repeated a whitespace
Context: ... | | config.yml | A configuration file for customizing a...

Near line 161: Possible typo: you repeated a whitespace
Context: ...for customizing a chain in development. | | readme.md | A readme file for y...

Near line 162: Possible typo: you repeated a whitespace
Context: ... | | readme.md | A readme file for your sovereign appli...

Near line 162: Possible spelling mistake found.
Context: ... | | readme.md | A readme file for your sovereign application-spe...

Near line 169: Possible spelling mistake found.
Context: ...e the x directory. ## 🛠️ Setting up Rollkit {#setting-up-rollkit} Before we contin...

Near line 171: Possible spelling mistake found.
Context: ...lding our Wordle App, we need to set up Rollkit on our codebase. ### 🗞️ Installing Ro...

Near line 174: Possible spelling mistake found.
Context: ...it on our codebase. ### 🗞️ Installing Rollkit {#installing-rollkit} Run the followin...

Near line 176: Possible spelling mistake found.
Context: ...} Run the following command inside the wordle directory. ```bash go mod edit -repla...

Near line 184: Possible spelling mistake found.
Context: ...go mod download ``` With that, we have Rollkit changes added to the project directory....

Near line 187: Possible spelling mistake found.
Context: ...uild the Wordle app! ## ✨ Creating the wordle module {#creating-wordle-module} For t...

Near line 212: Possible spelling mistake found.
Context: ...kinds of accounts (notably delegating/undelegating for vesting accounts). It exposes sev...

Near line 238: Possible spelling mistake found.
Context: ...sages with ignite. * The first one is: SubmitWordle and it only passes the Wordle of the D...

Near line 239: Possible spelling mistake found.
Context: ...Wordle of the Day. * The second one is: SubmitGuess and it attempts to guess the submitted...

Near line 240: Possible spelling mistake found.
Context: ...nd it attempts to guess the submitted wordle. It also passes a word as a guess. Wit...

Near line 246: Possible spelling mistake found.
Context: ...{#scaffolding-a-message} To create the SubmitWordle message, we run the following command:...

Near line 252: Possible spelling mistake found.
Context: ...ubmit-wordle word ``` This creates the submit-wordle message that takes in `word` as a para...

Near line 254: Possible spelling mistake found.
Context: ...eter. We now create the final message, SubmitGuess: ```bash ignite scaffold message subm...

Near line 267: Possible spelling mistake found.
Context: ...ssages we created. ### 🏗️ Scaffolding wordle types {#scaffolding-wordle-types} ```b...

Near line 275: Consider using “who” when you are referring to a person instead of an object.
Context: ...submitter` is the address of the person that submitted the Wordle. The second type ...

Near line 294: Possible typo: you repeated a whitespace
Context: ...DK module is a piece called the keeper. The keeper handles interactions with the...

Near line 305: Possible spelling mistake found.
Context: ...gic for each message we create. ### 📤 SubmitWordle function {#submitwordle-function} We ...

Near line 307: Possible spelling mistake found.
Context: ...rdle-function} We first start with the SubmitWordle function. Open up the following file:...

Near line 385: Possible spelling mistake found.
Context: ... } } return true } ``` Here in the SubmitWordle Keeper function, we are doing a few th...

Near line 396: Possible spelling mistake found.
Context: ...dy been submitted. Remember, only one wordle can be submitted per day. Everyone el...

Near line 397: Possible spelling mistake found.
Context: ...veryone else has to guess the submitted wordle. * We also have a helper function in th...

Near line 401: Possible spelling mistake found.
Context: ... contains alphabet characters. ### ⌛ SubmitGuess function {#submitguess-function} The ...

Near line 510: Possible missing comma found.
Context: ...the hash string of the current day. * Next we create a hash string of current day ...

Near line 510: You might be missing the article “the” here.
Context: ... day. * Next we create a hash string of current day and the Submitter. This allows us...

Near line 510: Possible typo: you repeated a whitespace
Context: ...tring of current day and the Submitter. This allows us to create a Guess type wi...

Near line 513: Possible spelling mistake found.
Context: ...y and an address wants to guess the new wordle of the day. The index setup ensures t...

Near line 513: Possible typo: you repeated a whitespace
Context: ...nts to guess the new wordle of the day. The index setup ensures they can continu...

Near line 514: Possible spelling mistake found.
Context: ...nsures they can continue guessing a new wordle every day up to the max of 6 tries pe...

Near line 515: Possible missing comma found.
Context: ... continue guessing a new wordle every day up to the max of 6 tries per day. * We ...

Near line 517: Possible spelling mistake found.
Context: ...ss type for the Submitter for today’s wordle did reach 6 counts. If it hasn’t, we in...

Near line 517: Possible typo: you repeated a whitespace
Context: .... If it hasn’t, we increment the count. We then check if the guess is correct. W...

Near line 521: Possible spelling mistake found.
Context: ...the updated count to the state. ### 📦 Protobuf file {#protobuf-file} A few files ne...

Near line 525: Possible spelling mistake found.
Context: ...odified for this to work. The first is proto/wordle/wordle/tx.proto. Inside this file, fi...

Near line 527: Possible spelling mistake found.
Context: .... Inside this file, fill in the empty MsgSubmitGuessResponse` with the following code: ```go title=...

Near line 539: Possible spelling mistake found.
Context: ...d_keepers.go` Here, we need to add the SendCoins method to the BankKeeper interface in o...

Near line 539: Possible spelling mistake found.
Context: ...need to add the SendCoins method to the BankKeeper interface in order to allow sending the...

Near line 540: Consider a shorter alternative to avoid wordiness.
Context: ...oins method to the BankKeeper interface in order to allow sending the reward to the right g...

Near line 551: Possible spelling mistake found.
Context: ...it out for a test drive. ## ⛓️ Run the wordle chain  ### 🪶 Run a Celestia light node {#run-celestia-light-node} ...

Near line 556: Possible spelling mistake found.
Context: ... instructions to install and start your Celestia Data Availability layer Light Node sele...

Near line 557: Possible missing comma found.
Context: ... Celestia Data Availability layer Light Node selecting the Arabica Devnet. You can f...

Near line 557: Possible spelling mistake found.
Context: ... layer Light Node selecting the Arabica Devnet. You can find instructions to install a...

Near line 560: Possible spelling mistake found.
Context: ...e Go and Ignite CLI installed, and your Celestia Light Node running on your machine, you...

Near line 562: Possible spelling mistake found.
Context: ...ld, test, and launch your own sovereign rollup. Be sure you have initialized your nod...

Near line 572: Possible spelling mistake found.
Context: ...e Go and Ignite CLI installed, and your Celestia Light Node running on your machine, you...

Near line 574: Possible spelling mistake found.
Context: ...ld, test, and launch your own sovereign rollup. ### 🟢 Building and running wordle ch...

Near line 576: Possible spelling mistake found.
Context: ...gn rollup. ### 🟢 Building and running wordle chain {#build-and-run-wordle-chain} We...

Near line 591: Possible spelling mistake found.
Context: ...nit.sh` script to initialize our Wordle Rollup. You can view the contents of the scri...

Near line 594: Possible spelling mistake found.
Context: ...ipt to see how we initialize the Wordle Rollup. You can initialize the script with th...

Near line 602: Possible spelling mistake found.
Context: ...sh bash init.sh ``` With that, we have kickstarted our wordled network! Find [your acco...

Near line 602: Possible spelling mistake found.
Context: ...``` With that, we have kickstarted our wordled network! Find [your account address o...

Near line 605: Possible spelling mistake found.
Context: ...ress on an Arabica explorer to see your PayForBlobs transactions](https://explorer.modular...

Near line 616: Possible spelling mistake found.
Context: ...rrors. With Rollkit as a replacement to CometBFT, we need to wait for Celestia's Data-...

Near line 617: Possible spelling mistake found.
Context: ...ment to CometBFT, we need to wait for Celestia's Data-Availability network to ensure a...

Near line 619: Possible spelling mistake found.
Context: ...ding to the next block. Currently, in Rollkit, the single aggregator is not moving fo...

Near line 620: Possible typo: you repeated a whitespace
Context: ...it the current block to the DA network. In the future, with leader selection, bl...

Near line 621: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...ection, block production and sync logic improves dramatically. This will ask you to c...

Near line 667: Possible missing comma found.
Context: ... then get a response with a transaction hash as shown here: ```bash code: 0 codespa...

Near line 710: Possible spelling mistake found.
Context: ...r confirming the transaction, query the txhash given the same way you did above. You ...

Near line 722: Possible spelling mistake found.
Context: ...r confirming the transaction, query the txhash given the same way you did above. You ...

Near line 726: Possible spelling mistake found.
Context: ... characters. Now try to submit another wordle even though one was already submitted ...

Near line 734: Possible spelling mistake found.
Context: ... transactions and confirming, query the txhash given the same way you did above. You ...

Near line 735: Possible spelling mistake found.
Context: ...did above. You will get an error that a wordle has already been submitted for the day....

Near line 738: When ‘five-letter’ is used as a modifier, it is usually spelled with a hyphen.
Context: ... for the day. Now let’s try to guess a five letter word: <!-- markdownlint-disable MD013 ...

Near line 746: Possible spelling mistake found.
Context: ... transactions and confirming, query the txhash given the same way you did above. Give...

Near line 748: Possible spelling mistake found.
Context: ..., it will increment the guess count for wordle-key's account. We can verify this by query...

Near line 756: Only proper nouns start with an uppercase character (there are exceptions for headlines).
Context: ...ess --output json ``` This outputs all Guess objects submitted so far, with the inde...

Near line 760: Possible spelling mistake found.
Context: ... Wordle using Cosmos-SDK and Ignite and Rollkit. Read on to how you can extend the code...

Near line 771: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ... correct word. 2. You can hash the word prior to submitting it to the chain, ensuring ...

Near line 777: You might be missing the article “the” here.
Context: ...mblebun/wordle-cli). 4. You can improve current date to stick to a specific timezone. 5...

Near line 778: Possible spelling mistake found.
Context: ... 5. You can create a bot that submits a wordle every day at a specific time. 6. You ca...

Near line 779: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...wordle every day at a specific time. 6. You can create a vue.js front-end with Igni...

Additional comments not posted (12)

learn/building-and-deploying-a-rollup.md (1)

16-16: Update link to match new documentation structure.

The change from "/tutorials/restart-rollup" to "/guides/restart-rollup" aligns with the restructuring objectives to improve clarity and organization by moving practical guides to a dedicated section.

tutorials/gm-world-mainnet.md (1)

1-1: Correct tutorial part number.

The change from "Part 4" to "Part 3" in the tutorial title ensures accuracy and consistency with the actual content covered in the tutorial series.

tutorials/gm-world-mocha-testnet.md (1)

1-1: Correct tutorial part number.

The change from "Part 3" to "Part 2" in the tutorial title ensures accuracy and consistency with the actual content covered in the tutorial series.

tutorials/gm-world-arabica-testnet.md (1)

Line range hint 1-1: Update hyperlink to absolute path.

The change from a relative path to an absolute path in the hyperlink ensures better reliability and accessibility of the link, especially when the documentation is viewed from different contexts.

tutorials/polaris-evm.md (1)

18-18: Update link to point to the new "How To Guides" section.

Ensure that the new link is accessible and correctly redirects to the intended page.

guides/cw-orch.md (2)

25-25: Added a note to explore the full cw-orch documentation.

This addition is helpful for users seeking more in-depth information.

104-104: Added details about interface creation specifics.

This addition provides valuable information on how to create interfaces for smart contracts using cw-orch.

tutorials/cosmwasm.md (3)

16-16: Update to absolute path for tutorial link is correct.

278-278: Update to absolute path for tutorial link is correct.

314-314: Update to absolute path for tutorial link is correct.

tutorials/recipe-book.md (1)

25-25: Update to absolute path for tutorial link is correct.

tutorials/wordle.md (1)

21-21: Update the link to restart the rollup guide.

The link update from restart-rollup.md to /guides/restart-rollup.md correctly reflects the new documentation structure. Ensure that the new link is functional and accessible.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai generate interesting stats about this repository and render them as a table.
- @coderabbitai show all the console.log statements in this repository.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

github-actions · 2024-04-23T14:35:18Z

PR Preview Action v1.4.7
Preview removed because the pull request was closed.
2024-04-23 15:47 UTC

jcstein · 2024-04-23T15:08:25Z

thoughts on top level navigation, may want to decrease number of options

coderabbitai

Actionable comments posted: 1

guides/overview.md

tutorials/overview.md

coderabbitai

Actionable comments posted: 2

tutorials/gm-world.md

MSevey added 4 commits April 23, 2024 10:10

chore: rename networks to testnets

a0db89f

chore: move guides into separate section

bfd9719

chore: reorg tutorials

ea65cf8

chore: fix minor missed text updates

37db810

docs: remove home from top level nav

93c647e

coderabbitai bot reviewed Apr 23, 2024

View reviewed changes

guides/overview.md Show resolved Hide resolved

docs: fix restart-rollup backlinks

fe1652a

jcstein reviewed Apr 23, 2024

View reviewed changes

tutorials/overview.md Show resolved Hide resolved

docs: fix other links

52f8945

jcstein approved these changes Apr 23, 2024

View reviewed changes

coderabbitai bot reviewed Apr 23, 2024

View reviewed changes

tutorials/gm-world.md Show resolved Hide resolved

tutorials/gm-world.md Show resolved Hide resolved

jcstein merged commit 2c86a1c into main Apr 23, 2024
4 checks passed

jcstein deleted the sevey/docs-reorg branch April 23, 2024 15:46

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: docs reorg #350

feat: docs reorg #350

MSevey commented Apr 23, 2024 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Apr 23, 2024 •

edited

Loading

Chat

CodeRabbit Commands (invoked as PR comments)

CodeRabbit Configration File (`.coderabbit.yaml`)

Documentation and Community

github-actions bot commented Apr 23, 2024 •

edited

Loading

jcstein commented Apr 23, 2024

coderabbitai bot left a comment

coderabbitai bot left a comment

feat: docs reorg #350

feat: docs reorg #350

Conversation

MSevey commented Apr 23, 2024 • edited by coderabbitai bot Loading

Overview

Checklist

Summary by CodeRabbit

coderabbitai bot commented Apr 23, 2024 • edited Loading

Walkthrough

Changes

Chat

CodeRabbit Commands (invoked as PR comments)

CodeRabbit Configration File (.coderabbit.yaml)

Documentation and Community

github-actions bot commented Apr 23, 2024 • edited Loading

jcstein commented Apr 23, 2024

coderabbitai bot left a comment

Choose a reason for hiding this comment

coderabbitai bot left a comment

Choose a reason for hiding this comment

MSevey commented Apr 23, 2024 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Apr 23, 2024 •

edited

Loading

CodeRabbit Configration File (`.coderabbit.yaml`)

github-actions bot commented Apr 23, 2024 •

edited

Loading