Update Rust NFT zero-to-hero tutorials (#2077)

* updates

* fix version

docs/3.tutorials/nfts/0-intro.md

@@ -15,7 +15,7 @@ To complete these tutorials successfully, you'll need:
 
 - [Rust](https://www.rust-lang.org/tools/install)
 - [A Testnet wallet](https://testnet.mynearwallet.com/create)
-- [NEAR-CLI](/tools/near-cli#setup)
+- [NEAR-CLI-RS](../../4.tools/cli-rs.md#setup)
 - [cargo-near](https://github.com/near/cargo-near)
 
 :::info New to Rust?
@@ -36,14 +36,10 @@ These are the steps that will bring you from **_Zero_** to **_Hero_** in no time
 | 4    | [Upgrade a contract](/tutorials/nfts/upgrade-contract)        | Discover the process to upgrade an existing smart contract.                                                            |
 | 5    | [Enumeration](/tutorials/nfts/enumeration)                    | Explore enumeration methods that can be used to return the smart contract's states.                                    |
 | 6    | [Core](/tutorials/nfts/core)                                  | Extend the NFT contract using the core standard which allows token transfer.                                        |
-| 7    | [Approvals](/tutorials/nfts/approvals)                        | Expand the contract allowing other accounts to transfer NFTs on your behalf.                                           |
-| 8    | [Royalty](/tutorials/nfts/royalty)                            | Add NFT royalties allowing for a set percentage to be paid out to the token creator.                                   |
-| 9    | [Marketplace](/tutorials/nfts/marketplace)                    | Learn about how common marketplaces operate on NEAR and dive into some of the code that allows buying and selling NFTs. |
-
-<!--
-1. [Events](/tutorials/nfts/events): in this tutorial you'll explore the events extension, allowing the contract to react on certain events.
-2. [Marketplace](/tutorials/nfts/marketplace): in the last tutorial you'll be exploring some key aspects of the marketplace contract.
--->
+| 7    | [Events](/tutorials/nfts/events)                              | The events extension, allowing the contract to react on certain events.                                              |
+| 8    | [Approvals](/tutorials/nfts/approvals)                        | Expand the contract allowing other accounts to transfer NFTs on your behalf.                                           |
+| 9    | [Royalty](/tutorials/nfts/royalty)                            | Add NFT royalties allowing for a set percentage to be paid out to the token creator.                                   |
+| 10   | [Marketplace](/tutorials/nfts/marketplace)                    | Learn about how common marketplaces operate on NEAR and dive into some of the code that allows buying and selling NFTs. |
 
 ---
 

docs/3.tutorials/nfts/0-predeployed.md

@@ -10,15 +10,7 @@ Create your first non-fungible token by using a pre-deployed NFT smart contract
 
 ## Prerequisites
 
-To complete this tutorial successfully, you'll need [a NEAR Wallet](https://testnet.mynearwallet.com/create) and [NEAR CLI](/tools/near-cli#setup)
-
-:::tip
-You can install near-cli through the following command:
-
-```bash
-npm install -g near-cli
-```
-:::
+To complete this tutorial successfully, you'll need [a NEAR Wallet](https://testnet.mynearwallet.com/create) and [NEAR CLI RS](../../4.tools/cli-rs.md#setup)
 
 ---
 
@@ -35,7 +27,7 @@ To interact with the contract you will need to first login to your NEAR account
 Log in to your newly created account with `near-cli` by running the following command in your terminal:
 
 ```bash
-near login
+near account import-account using-web-wallet network-config testnet
 ```
 
 Set an environment variable for your account ID to make it easy to copy and paste commands from this tutorial:
@@ -50,10 +42,10 @@ export NEARID=YOUR_ACCOUNT_NAME
 
 We have already deployed an NFT contract to `nft.examples.testnet` which allows users to freely mint tokens. Let's use it to mint our first token.
 
-Run this command in your terminal, remember to replace the `token_id` with a string of your choice. This string will uniquely identify the token you mint. 
+Run this command in your terminal, remember to replace the `token_id` with a string of your choice. This string will uniquely identify the token you mint.
 
 ```bash
-near call nft.examples.testnet nft_mint '{"token_id": "TYPE_A_UNIQUE_VALUE_HERE", "receiver_id": "'$NEARID'", "metadata": { "title": "GO TEAM", "description": "The Team Goes", "media": "https://bafybeidl4hjbpdr6u6xvlrizwxbrfcyqurzvcnn5xoilmcqbxfbdwrmp5m.ipfs.dweb.link/", "copies": 1}}' --accountId $NEARID --deposit 0.1
+near contract call-function as-transaction nft.examples.testnet nft_mint json-args '{"token_id": "TYPE_A_UNIQUE_VALUE_HERE", "receiver_id": "'$NEARID'", "metadata": { "title": "GO TEAM", "description": "The Team Goes", "media": "https://bafybeidl4hjbpdr6u6xvlrizwxbrfcyqurzvcnn5xoilmcqbxfbdwrmp5m.ipfs.dweb.link/", "copies": 1}}' prepaid-gas '100.0 Tgas' attached-deposit '0.1 NEAR' sign-as $NEARID network-config testnet sign-with-legacy-keychain send
 ```
 
 <details>
@@ -82,7 +74,7 @@ You can also replace the `media` URL with a link to any image file hosted on you
 To view tokens owned by an account you can call the NFT contract with the following `near-cli` command:
 
 ```bash
-near view nft.examples.testnet nft_tokens_for_owner '{"account_id": "'$NEARID'"}'
+near contract call-function as-read-only nft.examples.testnet nft_tokens_for_owner json-args '{"account_id": "'$NEARID'"}' network-config testnet now
 ```
 
 <details>
@@ -134,7 +126,7 @@ Now that you're familiar with the process, you can jump to [Contract Architectur
 
 At the time of this writing, this example works with the following versions:
 
-- near-cli: `4.0.13`
-- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.1.0`
+- near-cli-rs: `0.11.0`
+- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.0.0`
 
 :::

docs/3.tutorials/nfts/1-skeleton.md

@@ -236,12 +236,12 @@ Since this source is just a skeleton you'll get many warnings about unused code,
  │   |                             ^^^^^^^^^^  ^^^^^^^^^  ^^^^^^^^^^^^  ^^^^^^^^^^^^
  │   |
  │   = note: `#[warn(unused_imports)]` on by default
- │ 
+ │
  │ warning: unused import: `Base64VecU8`
  │  --> src/lib.rs:4:28
  │   |
  │ 4 | use near_sdk::json_types::{Base64VecU8, U128};
- │   |   
+ │   |
 
  │ warning: `nft_contract_skeleton` (lib) generated 48 warnings (run `cargo fix --lib -p nft_contract_skeleton` to apply 45 suggestions)
  │     Finished release [optimized] target(s) in 11.01s
@@ -256,13 +256,14 @@ Building the skeleton is useful to validate that your Rust toolchain works prope
 ## Conclusion
 
 You've seen the layout of this NFT smart contract, and how all the functions are laid out across the different source files.
-Using `yarn`, you've been able to compile the contract, and you'll start fleshing out this skeleton in the next [Minting tutorial](/tutorials/nfts/minting).
+Using `yarn`, you've been able to compile the contract, and you'll start fleshing out this skeleton in the next [Minting tutorial](2-minting.md).
 
 :::note Versioning for this article
 At the time of this writing, this example works with the following versions:
 
 - rustc: `1.76.0`
 - near-sdk-rs: `5.1.0`
-- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.1.0`
+- cargo-near: `0.6.1`
+- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.0.0`
 
 :::

docs/3.tutorials/nfts/2-minting.md

@@ -7,7 +7,7 @@ import {Github} from "@site/src/components/codetabs"
 
 This is the first of many tutorials in a series where you'll be creating a complete NFT smart contract from scratch that conforms with all the NEAR [NFT standards](https://nomicon.io/Standards/NonFungibleToken/).
 
-Today you'll learn how to create the logic needed to mint NFTs and have them show up in your NEAR wallet. You will be filling a bare-bones [skeleton smart contract](/tutorials/nfts/skeleton) to add minting functionalities.
+Today you'll learn how to create the logic needed to mint NFTs and have them show up in your NEAR wallet. You will be filling a bare-bones [skeleton smart contract](1-skeleton.md) to add minting functionalities.
 
 :::info Contracts
 You can find the skeleton contract in our [Skeleton folder](https://github.com/near-examples/nft-tutorial/tree/main/nft-contract-skeleton)
@@ -19,7 +19,7 @@ A completed version of this tutorial can be found in the [Basic NFT folder](http
 
 ## Introduction
 
-To get started, go to the `nft-contract-skeleton` folder in our repo. If you haven't cloned the repository, refer to the [Contract Architecture](/tutorials/nfts/skeleton) to get started.
+To get started, go to the `nft-contract-skeleton` folder in our repo. If you haven't cloned the repository, refer to the [Contract Architecture](1-skeleton.md) to get started.
 
 ```
 cd nft-contract-skeleton/
@@ -221,16 +221,16 @@ Now that the logic for minting is complete and you've added a way to query for i
 
 ### Deploying the contract {#deploy-the-contract}
 
-For deployment, you will need a NEAR account with the keys stored on your local machine. Navigate to the [NEAR wallet](https://testnet.mynearwallet.com//) site and create an account.
+For deployment, you will need a NEAR account with the keys stored on your local machine. Navigate to the [NEAR wallet](https://testnet.mynearwallet.com/) site and create an account.
 
 :::info
 Please ensure that you deploy the contract to an account with no pre-existing contracts. It's easiest to simply create a new account or create a sub-account for this tutorial.
 :::
 
-Log in to your newly created account with `near-cli` by running the following command in your terminal.
+Log in to your newly created account with [`near-cli-rs`](../../4.tools/cli-rs.md) by running the following command in your terminal.
 
 ```bash
-near login
+near account import-account using-web-wallet network-config testnet
 ```
 
 To make this tutorial easier to copy/paste, we're going to set an environment variable for your account ID. In the command below, replace `YOUR_ACCOUNT_NAME` with the account name you just logged in with including the `.testnet` portion:
@@ -277,7 +277,7 @@ You've just deployed and initialized the contract with some default metadata and
 Now that the contract has been initialized, you can call some of the functions you wrote earlier. More specifically, let's test out the function that returns the contract's metadata:
 
 ```bash
-near view $NFT_CONTRACT_ID nft_metadata
+near contract call-function as-read-only $NFT_CONTRACT_ID nft_metadata json-args {} network-config testnet now
 ```
 
 This should return an output similar to the following:
@@ -314,7 +314,7 @@ Let's mint an NFT with a title, description, and media to start. The media field
   - **receiver_id**: "'$NFT_CONTRACT_ID'"
 
 ```bash
-near call $NFT_CONTRACT_ID nft_mint '{"token_id": "token-1", "metadata": {"title": "My Non Fungible Team Token", "description": "The Team Most Certainly Goes :)", "media": "https://bafybeiftczwrtyr3k7a2k4vutd3amkwsmaqyhrdzlhvpt33dyjivufqusq.ipfs.dweb.link/goteam-gif.gif"}, "receiver_id": "'$NFT_CONTRACT_ID'"}' --accountId $NFT_CONTRACT_ID --amount 0.1
+near contract call-function as-transaction $NFT_CONTRACT_ID nft_mint json-args '{"token_id": "token-1", "metadata": {"title": "My Non Fungible Team Token", "description": "The Team Most Certainly Goes :)", "media": "https://bafybeiftczwrtyr3k7a2k4vutd3amkwsmaqyhrdzlhvpt33dyjivufqusq.ipfs.dweb.link/goteam-gif.gif"}, "receiver_id": "'$NFT_CONTRACT_ID'"}' prepaid-gas '100.0 Tgas' attached-deposit '0.1 NEAR' sign-as $NFT_CONTRACT_ID network-config testnet sign-with-legacy-keychain send
 ```
 
 :::info
@@ -329,7 +329,7 @@ Now that the NFT has been minted, you can check and see if everything went corre
 This should return a `JsonToken` which should contain the `token_id`, `owner_id`, and `metadata`.
 
 ```bash
-near view $NFT_CONTRACT_ID nft_token '{"token_id": "token-1"}'
+near contract call-function as-read-only $NFT_CONTRACT_ID nft_token json-args '{"token_id": "token-1"}' network-config testnet now
 ```
 
 <details>
@@ -366,7 +366,7 @@ near view $NFT_CONTRACT_ID nft_token '{"token_id": "token-1"}'
 
 ## Viewing your NFTs in the wallet
 
-If you navigate to the [collectibles tab](https://testnet.mynearwallet.com//?tab=collectibles) in the NEAR wallet, this should list all the NFTs that you own. It should look something like the what's below.
+If you navigate to the [collectibles tab](https://testnet.mynearwallet.com/?tab=collectibles) in the NEAR wallet, this should list all the NFTs that you own. It should look something like the what's below.
 
 ![empty-nft-in-wallet](/docs/assets/nfts/empty-nft-in-wallet.png)
 
@@ -388,15 +388,16 @@ After the contract was written, it was time to deploy to the blockchain. You [de
 
 ## Next Steps
 
-In the [next tutorial](/tutorials/nfts/upgrade-contract), you'll find out how to deploy a patch fix and what that means so that you can view your NFTs in the wallet.
+In the [next tutorial](2-upgrade.md), you'll find out how to deploy a patch fix and what that means so that you can view your NFTs in the wallet.
 
 :::note Versioning for this article
 
 At the time of this writing, this example works with the following versions:
 
-- near-cli: `4.0.13`
+- rustc: `1.77.1`
+- near-cli-rs: `0.11.0`
 - cargo-near `0.6.1`
-- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.1.0`
+- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.0.0`
 - Metadata standard: [NEP177](https://nomicon.io/Standards/Tokens/NonFungibleToken/Metadata), version `2.1.0`
 
 :::

docs/3.tutorials/nfts/2-upgrade.md

@@ -5,7 +5,7 @@ sidebar_label: Upgrade a Contract
 ---
 import {Github} from "@site/src/components/codetabs"
 
-In this tutorial, you'll build off the work you previously did to implement the [minting functionality](/tutorials/nfts/minting) on a skeleton smart contract. You got to the point where NFTs could be minted and the wallet correctly picked up on the fact that you owned an NFT. However, it had no way of displaying the tokens since your contract didn't implement the method that the wallet was trying to call.
+In this tutorial, you'll build off the work you previously did to implement the [minting functionality](2-minting.md) on a skeleton smart contract. You got to the point where NFTs could be minted and the wallet correctly picked up on the fact that you owned an NFT. However, it had no way of displaying the tokens since your contract didn't implement the method that the wallet was trying to call.
 
 ---
 
@@ -52,7 +52,7 @@ cargo near deploy $NFT_CONTRACT_ID without-init-call network-config testnet sign
 Once the contract has been redeployed, let's test and see if the state migrated correctly by running a simple view function:
 
 ```bash
-near view $NFT_CONTRACT_ID nft_metadata
+near contract call-function as-read-only $NFT_CONTRACT_ID nft_metadata json-args {} network-config testnet now
 ```
 
 This should return an output similar to the following:
@@ -72,7 +72,7 @@ This should return an output similar to the following:
 **Go team!** At this point, you can now test and see if the new function you wrote works correctly. Let's query for the list of tokens that you own:
 
 ```bash
-near view $NFT_CONTRACT_ID nft_tokens_for_owner '{"account_id": "'$NFT_CONTRACT_ID'", "limit": 5}'
+near contract call-function as-read-only $NFT_CONTRACT_ID nft_tokens_for_owner json-args '{"account_id": "'$NFT_CONTRACT_ID'", "limit": 5}' network-config testnet now
 ```
 
 <details>
@@ -109,7 +109,7 @@ near view $NFT_CONTRACT_ID nft_tokens_for_owner '{"account_id": "'$NFT_CONTRACT_
 
 ## Viewing NFTs in the wallet {#viewing-nfts-in-wallet}
 
-Now that your contract implements the necessary functions that the wallet uses to display NFTs, you should be able to see your tokens on display in the [collectibles tab](https://testnet.mynearwallet.com//?tab=collectibles).
+Now that your contract implements the necessary functions that the wallet uses to display NFTs, you should be able to see your tokens on display in the [collectibles tab](https://testnet.mynearwallet.com/?tab=collectibles).
 
 ![filled-nft-in-wallet](/docs/assets/nfts/filled-nft-in-wallet.png)
 
@@ -119,14 +119,15 @@ Now that your contract implements the necessary functions that the wallet uses t
 
 In this tutorial, you learned about the basics of [upgrading contracts](#upgrading-contracts). Then, you implemented the necessary [modifications to your smart contract](#modifications-to-contract) and [redeployed it](#redeploying-contract). Finally you navigated to the wallet collectibles tab and [viewed your NFTs](#viewing-nfts-in-wallet).
 
-In the [next tutorial](/tutorials/nfts/enumeration), you'll implement the remaining functions needed to complete the [enumeration](https://nomicon.io/Standards/Tokens/NonFungibleToken/Enumeration) standard.
+In the [next tutorial](3-enumeration.md), you'll implement the remaining functions needed to complete the [enumeration](https://nomicon.io/Standards/Tokens/NonFungibleToken/Enumeration) standard.
 
 :::note Versioning for this article
 
 At the time of this writing, this example works with the following versions:
 
-- near-cli: `4.0.13`
+- rustc: `1.77.1`
+- near-cli-rs: `0.11.0`
 - cargo-near `0.6.1`
-- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.1.0`
+- NFT standard: [NEP171](https://nomicon.io/Standards/Tokens/NonFungibleToken/Core), version `1.0.0`
 
 :::