diff --git a/docs/architecture/tokens.md b/docs/architecture/tokens.md index 5ba3e6f94..78235e5f8 100644 --- a/docs/architecture/tokens.md +++ b/docs/architecture/tokens.md @@ -21,7 +21,7 @@ One exception is tickets, which are directly stored and managed by smart contrac To learn about tokens, see these tutorials: - [Create an NFT](../tutorials/create-an-nft) -- [Build your first app on Tezos](../tutorials/build-your-first-app) +- [Build a simple web application](../tutorials/build-your-first-app) ## Fungible and non-fungible tokens diff --git a/docs/dApps.mdx b/docs/dApps.mdx index f8f808787..ded06035e 100644 --- a/docs/dApps.mdx +++ b/docs/dApps.mdx @@ -47,6 +47,6 @@ For information on typical tasks that dApps do, see: These tutorials cover dApps of different complexities: -- For a simple dApp, see [Build your first app on Tezos](./tutorials/build-your-first-app) +- For a simple dApp, see [Build a simple web application](./tutorials/build-your-first-app) - For a dApp that mints NFTs, see [Mint NFTs from a web app](./tutorials/create-an-nft/nft-web-app) - For a large dApp that allows users to buy and sell NFTs, see [Build an NFT marketplace](./tutorials/build-an-nft-marketplace) diff --git a/docs/dApps/sending-transactions.md b/docs/dApps/sending-transactions.md index ce64a1615..fda2b0529 100644 --- a/docs/dApps/sending-transactions.md +++ b/docs/dApps/sending-transactions.md @@ -82,7 +82,7 @@ try { } ``` -For examples of calling smart contracts, see tutorials such as [Build your first app on Tezos](../tutorials/build-your-first-app) or [Create a contract and web app that mints NFTs](../tutorials/create-an-nft/nft-taquito). +For examples of calling smart contracts, see tutorials such as [Build a simple web application](../tutorials/build-your-first-app) or [Create a contract and web app that mints NFTs](../tutorials/create-an-nft/nft-taquito). For more information about using Taquito, see [Smart contracts](https://tezostaquito.io/docs/smartcontracts) in the Taquito documentation. diff --git a/docs/dApps/wallets.md b/docs/dApps/wallets.md index 877f20c65..4c8ddbc05 100644 --- a/docs/dApps/wallets.md +++ b/docs/dApps/wallets.md @@ -29,7 +29,7 @@ The primary tools that dApps use to connect to wallets are: ## Beacon and Taquito Most of the time, dApps use Beacon and Taquito together for a straightforward way to connect to wallets and submit transactions. -For an example, see the tutorial [Build your first app on Tezos](../tutorials/build-your-first-app). +For an example, see the tutorial [Build a simple web application](../tutorials/build-your-first-app). ### Connecting to wallets @@ -49,7 +49,7 @@ const address = await wallet.getPKH(); When this code runs, Beacon opens a popup window that guides the user through connecting their wallet. Then the application can send transactions to Tezos. -See [Part 3: Sending transactions](../tutorials/build-your-first-app/sending-transactions) in the tutorial [Build your first app on Tezos](../tutorials/build-your-first-app). +See [Part 3: Sending transactions](../tutorials/build-your-first-app/sending-transactions) in the tutorial [Build a simple web application](../tutorials/build-your-first-app). ### Reconnecting to wallets diff --git a/docs/developing/testnets.md b/docs/developing/testnets.md index 53341a819..1f50a1401 100644 --- a/docs/developing/testnets.md +++ b/docs/developing/testnets.md @@ -17,7 +17,7 @@ Waiting for the next block every time you inject a new transaction takes a lot o To make testing a lot faster, options are available, depending on the language and tools you are using, that don't use a network or even a single node at all, and skip all the consensus mechanism steps. -- The **Michelson interpreter** is an OCaml function that can be used by tools to simulate a call to any entry point of any smart contract, given an initial value of the storage and parameters. Some programming languages like **LIGO** or **Smartpy** use this as part of their testing frameworks. +- The **Michelson interpreter** is an OCaml function that can be used by tools to simulate a call to any entry point of any smart contract, given an initial value of the storage and parameters. Some programming languages like **LIGO** or **SmartPy** use this as part of their testing frameworks. - The **mockup mode** of `octez-client` can be used to test contract calls and other features such as some RPC calls, all without running an actual node, saving the time of going through the consensus mechanism and waiting to get blocks created and validated. Tools like **Completium**, built by the team behind the **Archetype** language, use this for their testing framework. Find out more in the [documentation of the mockup mode](https://tezos.gitlab.io/user/mockup.html). diff --git a/docs/overview/common-applications.md b/docs/overview/common-applications.md index db0ee374a..135f2348a 100644 --- a/docs/overview/common-applications.md +++ b/docs/overview/common-applications.md @@ -22,7 +22,7 @@ Tezos is being used by the French Armies and Gendarmerie's Information Center to In recent years, the concept of Central Bank Digital Currencies (CBDCs) has gained traction, with several countries around the world exploring their own CBDC projects. Société Générale carried out a series of successful tests [using Tezos](https://decrypt.co/112127/societe-generales-crypto-division-lands-regulatory-approval-france) to explore the potential of CBDCs. In September 2020, the bank announced that it had completed a pilot program using a custom-built version of the Tezos blockchain to simulate the issuance and circulation of CBDCs. The pilot involved testing the technology's ability to handle transactions, make payments, and settle transactions in a digital environment. -The Califonia DMV is also using Tezos for its project to [put car titles on the blockchain](https://fortune.com/crypto/2023/01/26/california-announces-dmv-run-blockchain-through-partnership-with-tezos/). +The California DMV is also using Tezos for its project to [put car titles on the blockchain](https://fortune.com/crypto/2023/01/26/california-announces-dmv-run-blockchain-through-partnership-with-tezos/). [Sword Group](https://www.sword-group.com/2020/09/28/sword-launches-tezos-digisign/) an international technology company, launched DigiSign, an open-source tool built on Tezos that enables users to digitally sign, certify, and verify the authenticity of digital documents. diff --git a/docs/overview/quickstart.md b/docs/overview/quickstart.md index 10bd53e33..c7aeb3743 100644 --- a/docs/overview/quickstart.md +++ b/docs/overview/quickstart.md @@ -3,4 +3,4 @@ Simple page to provide links to tutorials and what you learn from each one. - To learn about smart contracts, go to 'Deploy your first smart contract' -- To learn about dApps, go to 'Build your first app on Tezos' \ No newline at end of file +- To learn about dApps, go to 'Build a simple web application' \ No newline at end of file diff --git a/docs/smart-contracts/creating.md b/docs/smart-contracts/creating.md index 1803df43d..63f788fbd 100644 --- a/docs/smart-contracts/creating.md +++ b/docs/smart-contracts/creating.md @@ -10,7 +10,7 @@ This documentation provides step-by-step instructions for creating smart contrac ## Choosing your smart contract language Tezos supports a variety of smart contract [languages](./languages): Michelson, SmartPy, LIGO, Archetype. -You can select a language based on your familarity with programming paragims, the complexity of the contract you want to deploy, and the specific features you require. Here's a more detailed table for each language: +You can select a language based on your familiarity with programming paradigms, the complexity of the contract you want to deploy, and the specific features you require. Here's a more detailed table for each language: | | **Michelson** | **SmartPy** | **LIGO** | **Archetype** | |:----------------:|:----------------------------------------------------------:|:-----------------------------------------------------:|:-------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| @@ -18,7 +18,7 @@ You can select a language based on your familarity with programming paragims, th | **Capabilities** | Full control over contract, optimal for gas efficiency | Easy to write, automatically manages stack operations | Statically-typed, strong error checking | Specialized for formal verification and correctness | | **Use Cases** | Optimized contracts, developers with blockchain experience | Python developers, rapid prototyping | Developers familiar with static typing, variety of mainstream programming backgrounds | High-security contracts, developers looking for formal proof of contract behavior | -For beginners, we recommand **SmartPy** or **LIGO** for their higher-level more abstracted approach. +For beginners, we recommend **SmartPy** or **LIGO** for their higher-level more abstracted approach. ## Making a strategic choice diff --git a/docs/smart-contracts/data-types/primitive-data-types.md b/docs/smart-contracts/data-types/primitive-data-types.md index d7d56e3f7..629d5cfce 100644 --- a/docs/smart-contracts/data-types/primitive-data-types.md +++ b/docs/smart-contracts/data-types/primitive-data-types.md @@ -137,8 +137,8 @@ For more information about serialization, see [Serialization](../serialization). Boolean types on Tezos (`bool`) work the same way as in most programming languages. -- A boolean value can be `True` or `False` -- Comparison operators produce boolean values +- A Boolean value can be `True` or `False` +- Comparison operators produce Boolean values - Boolean values can be used in conditional statements or `while` loops - The usual logic operators are supported: `AND`, `OR`, `XOR`, `NOT` diff --git a/docs/smart-contracts/languages/ligo.md b/docs/smart-contracts/languages/ligo.md index 9ac6b4da6..9da88a75c 100644 --- a/docs/smart-contracts/languages/ligo.md +++ b/docs/smart-contracts/languages/ligo.md @@ -8,7 +8,7 @@ LIGO is a functional programming language that is intended to be both user-frien LIGO offers two syntaxes: -- JsLIGO, a sytax that is inspired by TypeScript/JavaScript +- JsLIGO, a syntax that is inspired by TypeScript/JavaScript - CameLIGO, a syntax that is inspired by OCaml You can use either syntax and compile to Michelson to run on Tezos. @@ -16,7 +16,7 @@ You can use either syntax and compile to Michelson to run on Tezos. To learn LIGO, see these tutorials: - [Deploy a smart contract with CameLIGO](../../tutorials/smart-contract/cameligo) -- [Deploy a smart contract with jsLIGO](../../tutorials/smart-contract/jsligo) +- [Deploy a smart contract with JsLIGO](../../tutorials/smart-contract/jsligo) Let's define a LIGO contract in the two flavours above. diff --git a/docs/tutorials.mdx b/docs/tutorials.mdx index 391d61525..16bfc8711 100644 --- a/docs/tutorials.mdx +++ b/docs/tutorials.mdx @@ -54,7 +54,7 @@ These tutorials contain multiple parts and are intended for developers with some /> > "$HOME/octez-baker.log" 2>&1 ``` -We can check that the DAL is now subscribed to the relevant topics by retrying the following RPC, which should now return all the topics of the form `{"slot_index":,"pkh":"
"}` where `index` varies between `0` included and the number of slot indexes (`32` on Weeklynet) exluded: +We can check that the DAL is now subscribed to the relevant topics by retrying the following RPC, which should now return all the topics of the form `{"slot_index":,"pkh":"
"}` where `index` varies between `0` included and the number of slot indexes (`32` on Weeklynet) excluded: ``` curl http://localhost:10732/p2p/gossipsub/topics @@ -17,7 +17,7 @@ We can also look at the baker logs to see if it manages to inject the expected o - inject a preattestation for it (log message: "injected preattestation ... for my_baker (<address>) for level ..., round ...") - receive a block (log message: "received new head ... at level ..., round ...") - inject an attestation for it (log message: "injected attestation ... for my_baker (<address>) for level ..., round ...") -- inject a DAL attestation indicating which of the shards assigned to the baker have been seen on the DAL network (log message: "injected DAL attestation ... for level ..., round ..., with bitset ... for my_baker (<address>) to attest slots published at level ..."); if no shard was seen (either because they did not reach the DAL node for some reason or simply because nothing was published on the DAL at the targetted level), the operation is skipped (log message: "Skipping the injection of the DAL attestation for attestation level ..., round ..., as currently no slot published at level ... is attestable.") +- inject a DAL attestation indicating which of the shards assigned to the baker have been seen on the DAL network (log message: "injected DAL attestation ... for level ..., round ..., with bitset ... for my_baker (<address>) to attest slots published at level ..."); if no shard was seen (either because they did not reach the DAL node for some reason or simply because nothing was published on the DAL at the targeted level), the operation is skipped (log message: "Skipping the injection of the DAL attestation for attestation level ..., round ..., as currently no slot published at level ... is attestable.") Optionally, we can also launch an accuser which will monitor the behaviour of the other Weeklynet bakers and denounce them to the Tezos protocol if they are caught double-signing any block or consensus operation. diff --git a/docs/tutorials/join-dal-baker/run-node.md b/docs/tutorials/join-dal-baker/run-node.md index 8232802df..540bf3c20 100644 --- a/docs/tutorials/join-dal-baker/run-node.md +++ b/docs/tutorials/join-dal-baker/run-node.md @@ -6,7 +6,7 @@ Once the Octez node has been configured to join Weeklynet, we can launch it and octez-node run --rpc-addr 127.0.0.1:8732 --log-output="$HOME/octez-node.log" ``` -At first launch, the node will generate a fresh identity file used to identify itself on the Weeklynet L1 network, it then bootstraps the chain which means that it downloads and applies all the blocks. This takes a variable amount of time depending on when during the week these instructions are followed but at worse, on a tuesday evening, it takes a few hours. Fortunately, we can continue to set up our Weeklynet baking infrastructure while the node is bootstrapping, all we have to do for this is to use another, already bootstrapped, node as RPC endpoint for `octez-client` when we want to interact with the chain. +At first launch, the node will generate a fresh identity file used to identify itself on the Weeklynet L1 network, it then bootstraps the chain which means that it downloads and applies all the blocks. This takes a variable amount of time depending on when during the week these instructions are followed but at worst, on a Tuesday evening, it takes a few hours. Fortunately, we can continue to set up our Weeklynet baking infrastructure while the node is bootstrapping, all we have to do for this is to use another, already bootstrapped, node as RPC endpoint for `octez-client` when we want to interact with the chain. A public RPC endpoint URL for Weeklynet is linked from the https://teztnets.com/weeklynet-about page, let's record it in a shell variable: ``` diff --git a/docs/tutorials/mobile/part-1.md b/docs/tutorials/mobile/part-1.md index 64bced378..59c2bf7f5 100644 --- a/docs/tutorials/mobile/part-1.md +++ b/docs/tutorials/mobile/part-1.md @@ -7,7 +7,7 @@ last_update: On this first section, you will: -- Create the game smart contract importing an existing Ligo library +- Create the game smart contract importing an existing LIGO library - Deploy your smart contract to the Ghostnet - Get the Shifumi Git repository folders to copy the game UI and CSS for the second party @@ -22,7 +22,7 @@ On this first section, you will: taq install @taqueria/plugin-ligo ``` -1. Download the Ligo Shifumi template, and copy the files to Taqueria **contracts** folder: +1. Download the LIGO Shifumi template, and copy the files to Taqueria **contracts** folder: ```bash TAQ_LIGO_IMAGE=ligolang/ligo:1.2.0 taq ligo --command "init contract --template shifumi-jsligo shifumiTemplate" diff --git a/docs/tutorials/mobile/part-2.md b/docs/tutorials/mobile/part-2.md index ce96dc543..eda7a7d5e 100644 --- a/docs/tutorials/mobile/part-2.md +++ b/docs/tutorials/mobile/part-2.md @@ -22,7 +22,7 @@ A web3 mobile application is not different from a web2 one in terms of its basic ionic start app blank --type react ``` -1. Generate smart contract types from the taqueria plugin: +1. Generate smart contract types from the Taqueria plugin: This command generates Typescript classes from the smart contract interface definition that is used on the frontend. @@ -452,7 +452,7 @@ A web3 mobile application is not different from a web2 one in terms of its basic - `import "@ionic..."`: Default standard Ionic imports. - `import ... from "@airgap/beacon-types" ... from "@taquito/beacon-wallet" ... from "@taquito/taquito"`: Require libraries to interact with the Tezos node and the wallet. - - `export class Action implements ActionCisor, ActionPaper, ActionStone {...}`: Representation of the Ligo variant `Action` in Typescript, which is needed when passing arguments on `Play` function. + - `export class Action implements ActionCisor, ActionPaper, ActionStone {...}`: Representation of the LIGO variant `Action` in Typescript, which is needed when passing arguments on `Play` function. - `export type Session = {...}`: Taqueria exports the global storage type but not this sub-type from the storage type; it is needed for later, so extract a copy. - `export const UserContext = React.createContext(null)`: Global React context that is passed along pages. More info on React context [here](https://beta.reactjs.org/learn/passing-data-deeply-with-context). - `const refreshStorage = async (event?: CustomEvent): Promise => {...`: A useful function to force the smart contract storage to refresh on React state changes (user balance, state of the game). diff --git a/docs/tutorials/smart-contract.md b/docs/tutorials/smart-contract.md index 93f8ea809..84ee56f22 100644 --- a/docs/tutorials/smart-contract.md +++ b/docs/tutorials/smart-contract.md @@ -24,6 +24,6 @@ You can run the tutorial with the version of the language you are most familiar You do not need an experience in these languages to run the tutorial. - To use SmartPy, a language similar to Python, see [Deploy a smart contract with SmartPy](./smart-contract/smartpy) -- To use jsLIGO, a language similar to JavaScript and TypeScript, see [Deploy a smart contract with jsLIGO](./smart-contract/jsligo) +- To use JsLIGO, a language similar to JavaScript and TypeScript, see [Deploy a smart contract with JsLIGO](./smart-contract/jsligo) - To use CameLIGO, a language similar to OCaml, see [Deploy a smart contract with CameLIGO](./smart-contract/cameligo) - To learn the Archetype language, try [Deploy a smart contract with Archetype](./smart-contract/archetype). diff --git a/docs/tutorials/smart-contract/archetype.md b/docs/tutorials/smart-contract/archetype.md index 73a694d97..05c958f4e 100644 --- a/docs/tutorials/smart-contract/archetype.md +++ b/docs/tutorials/smart-contract/archetype.md @@ -10,7 +10,7 @@ It uses the completium-cli command-line tool, which lets you work with Archetype - If you are more familiar with Python, try [Deploy a smart contract with SmartPy](./smartpy). - If you are more familiar with OCaml, try [Deploy a smart contract with CameLIGO](./cameligo). -- If you are more familiar with JavaScript, try [Deploy a smart contract with jsLIGO](./jsligo). +- If you are more familiar with JavaScript, try [Deploy a smart contract with JsLIGO](./jsligo). In this tutorial, you will learn how to: @@ -324,5 +324,5 @@ Then, you can verify the updated storage on the block explorer or by running the Now the contract is running on the Tezos blockchain. You or any other user can call it from any source that can send transactions to Tezos, including command-line clients, dApps, and other contracts. -If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build your first app on Tezos](../build-your-first-app/). +If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build a simple web application](../build-your-first-app/). You can also try adding your own endpoints and originating a new contract, but you cannot update the existing contract after it is deployed. diff --git a/docs/tutorials/smart-contract/cameligo.mdx b/docs/tutorials/smart-contract/cameligo.mdx index dcb19a6d2..77524c426 100644 --- a/docs/tutorials/smart-contract/cameligo.mdx +++ b/docs/tutorials/smart-contract/cameligo.mdx @@ -8,7 +8,7 @@ last_update: This tutorial covers writing and deploying a simple smart contract with the LIGO programming language. Specifically, this tutorial uses the CameLIGO version of LIGO, which has syntax similar to OCaml, but you don't need any experience with OCaml or LIGO to do this tutorial. -- If you are more familiar with JavaScript, try [Deploy a smart contract with jsLIGO](./jsligo). +- If you are more familiar with JavaScript, try [Deploy a smart contract with JsLIGO](./jsligo). - If you are more familiar with Python, try [Deploy a smart contract with SmartPy](./smartpy). - To learn the Archetype language, try [Deploy a smart contract with Archetype](./archetype). @@ -288,5 +288,5 @@ It also allows you to call the contract. Now the contract is running on the Tezos blockchain. You or any other user can call it from any source that can send transactions to Tezos, including Octez, dApps, and other contracts. -If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build your first app on Tezos](../build-your-first-app/). +If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build a simple web application](../build-your-first-app/). You can also try adding your own endpoints and originating a new contract, but you cannot update the existing contract after it is deployed. diff --git a/docs/tutorials/smart-contract/jsligo.mdx b/docs/tutorials/smart-contract/jsligo.mdx index eeb26626d..2d98625d1 100644 --- a/docs/tutorials/smart-contract/jsligo.mdx +++ b/docs/tutorials/smart-contract/jsligo.mdx @@ -1,12 +1,12 @@ --- -title: Deploy a smart contract with jsLIGO +title: Deploy a smart contract with JsLIGO authors: 'John Joubert, Sasha Aldrick, Claude Barde, Tim McMackin' last_update: date: 3 January 2024 --- This tutorial covers writing and deploying a simple smart contract with the LIGO programming language. -Specifically, this tutorial uses the jsLIGO version of LIGO, which has syntax similar to JavaScript, but you don't need any experience with JavaScript or LIGO to do this tutorial. +Specifically, this tutorial uses the JsLIGO version of LIGO, which has syntax similar to JavaScript, but you don't need any experience with JavaScript or LIGO to do this tutorial. - If you are more familiar with Python, try [Deploy a smart contract with SmartPy](./smartpy). - If you are more familiar with OCaml, try [Deploy a smart contract with CameLIGO](./cameligo). @@ -303,5 +303,5 @@ It also allows you to call the contract. Now the contract is running on the Tezos blockchain. You or any other user can call it from any source that can send transactions to Tezos, including Octez, dApps, and other contracts. -If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build your first app on Tezos](../build-your-first-app/). +If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build a simple web application](../build-your-first-app/). You can also try adding your own endpoints and originating a new contract, but you cannot update the existing contract after it is deployed. diff --git a/docs/tutorials/smart-contract/smartpy.mdx b/docs/tutorials/smart-contract/smartpy.mdx index 50da77700..a51717c5e 100644 --- a/docs/tutorials/smart-contract/smartpy.mdx +++ b/docs/tutorials/smart-contract/smartpy.mdx @@ -9,7 +9,7 @@ This tutorial covers writing and deploying a simple smart contract with the Smar SmartPy has syntax similar to Python, but you don't need any experience with Python or SmartPy to do this tutorial. - If you are more familiar with OCaml, try [Deploy a smart contract with CameLIGO](./cameligo). -- If you are more familiar with JavaScript, try [Deploy a smart contract with jsLIGO](./jsligo). +- If you are more familiar with JavaScript, try [Deploy a smart contract with JsLIGO](./jsligo). - To learn the Archetype language, try [Deploy a smart contract with Archetype](./archetype). SmartPy is a high-level programming language that you can use to write smart contracts for the Tezos blockchain. @@ -290,5 +290,5 @@ It will not be shown again. Now the contract is running on the Tezos blockchain. You or any other user can call it from any source that can send transactions to Tezos, including Octez, dApps, and other contracts. -If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build your first app on Tezos](../build-your-first-app/). +If you want to continue working with this contract, try creating a dApp to call it from a web application, similar to the dApp that you create in the tutorial [Build a simple web application](../build-your-first-app/). You can also try adding your own endpoints and originating a new contract, but you cannot update the existing contract after it is deployed. diff --git a/docs/unity/quickstart.md b/docs/unity/quickstart.md index dea0105da..d127ca169 100644 --- a/docs/unity/quickstart.md +++ b/docs/unity/quickstart.md @@ -19,7 +19,7 @@ These instructions cover: 1. In your Unity project, in the Package Manager panel, click the `+` symbol and then click **Add package from git URL**. -1. Enter the url `https://github.com/trilitech/tezos-unity-sdk.git` and click **Add**. +1. Enter the URL `https://github.com/trilitech/tezos-unity-sdk.git` and click **Add**. The Package Manager panel downloads and installs the SDK. You can see its assets in the Project panel under Packages > Tezos Unity SDK. diff --git a/docs/unity/reference/DAppMetadata.md b/docs/unity/reference/DAppMetadata.md index 2e9a3dc4f..6bb60fce2 100644 --- a/docs/unity/reference/DAppMetadata.md +++ b/docs/unity/reference/DAppMetadata.md @@ -15,7 +15,7 @@ These properties are read-only: - `Name`: The name of the project, which is shown in wallet applications when users connect to the project - `Url`: The home page of the project - `Icon`: The URL to a favicon for the project -- `Description`: A description of hte project +- `Description`: A description of the project ## Methods diff --git a/docs/unity/scenes.md b/docs/unity/scenes.md index 7a27b7864..75bb36ed6 100644 --- a/docs/unity/scenes.md +++ b/docs/unity/scenes.md @@ -56,7 +56,7 @@ This scene includes buttons that link to the other scenes. ## Wallet Connection scene -This scene shows how to to use the TezosAuthenticator prefab to connect to a user's wallet and get information about their account. +This scene shows how to use the TezosAuthenticator prefab to connect to a user's wallet and get information about their account. The scene uses the platform type to determine how to connect to a user's wallet. In the TezosAuthenticator `SetPlatformFlags` function, it checks what platform it is running on: diff --git a/sidebars.js b/sidebars.js index 8ace4d6d1..e1749ba90 100644 --- a/sidebars.js +++ b/sidebars.js @@ -249,156 +249,154 @@ const sidebars = { }, ], tutorialsSidebar: [ + { + type: 'doc', + label: 'Tutorials home', + id: 'tutorials', + }, + { + type: 'html', + value: '
Beginner
', + className: 'menu__divider', + }, { type: 'category', - label: 'Tutorials', + label: 'Deploy a smart contract', link: { type: 'doc', - id: 'tutorials', + id: 'tutorials/smart-contract', }, items: [ - { - type: 'category', - label: 'Deploy a smart contract', - link: { - type: 'doc', - id: 'tutorials/smart-contract', - }, - items: [ - 'tutorials/smart-contract/jsligo', - 'tutorials/smart-contract/cameligo', - 'tutorials/smart-contract/smartpy', - 'tutorials/smart-contract/archetype', - ], - }, - { - type: 'category', - label: 'Create an NFT', - link: { - type: 'doc', - id: 'tutorials/create-an-nft', - }, - items: [ - 'tutorials/create-an-nft/nft-tznft', - 'tutorials/create-an-nft/nft-taquito', - { - type: 'category', - label: 'Mint NFTs from a web app', - link: { - type: 'doc', - id: 'tutorials/create-an-nft/nft-web-app', - }, - items: [ - 'tutorials/create-an-nft/nft-web-app/setting-up-app', - 'tutorials/create-an-nft/nft-web-app/defining-functions', - 'tutorials/create-an-nft/nft-web-app/lets-play', - ], - }, - ], - }, - { - type: 'category', - label: 'Build your first app', - link: { - type: 'doc', - id: 'tutorials/build-your-first-app', - }, - items: [ - 'tutorials/build-your-first-app/setting-up-app', - 'tutorials/build-your-first-app/wallets-tokens', - 'tutorials/build-your-first-app/sending-transactions', - 'tutorials/build-your-first-app/getting-information', - ], - }, - - { - type: 'category', - label: 'Start with a minimum dApp and add new features', - link: { - type: 'doc', - id: 'tutorials/dapp', - }, - items: [ - 'tutorials/dapp/part-1', - 'tutorials/dapp/part-2', - 'tutorials/dapp/part-3', - 'tutorials/dapp/part-4', - ], - }, - - { - type: 'category', - label: 'Deploy a smart rollup', - link: { - type: 'doc', - id: 'tutorials/smart-rollup', - }, - items: [ - 'tutorials/smart-rollup/set-up', - 'tutorials/smart-rollup/debug', - 'tutorials/smart-rollup/optimize', - 'tutorials/smart-rollup/deploy', - 'tutorials/smart-rollup/run', - ], - }, - { - type: 'category', - label: 'Implement a file archive with the DAL', - link: { - type: 'doc', - id: 'tutorials/build-files-archive-with-dal', - }, - items: [ - 'tutorials/build-files-archive-with-dal/get-dal-params', - 'tutorials/build-files-archive-with-dal/get-slot-info', - 'tutorials/build-files-archive-with-dal/publishing-on-the-dal', - 'tutorials/build-files-archive-with-dal/using-full-slot', - ], - }, - { - type: 'category', - label: 'Join the DAL as a Weeklynet baker', - link: { - type: 'doc', - id: 'tutorials/join-dal-baker', - }, - items: [ - 'tutorials/join-dal-baker/get-octez', - 'tutorials/join-dal-baker/run-node', - 'tutorials/join-dal-baker/prepare-account', - 'tutorials/join-dal-baker/run-dal-node', - 'tutorials/join-dal-baker/run-baker', - 'tutorials/join-dal-baker/conclusion', - ], - }, - { - type: 'category', - label: 'Build an NFT marketplace', - link: { - type: 'doc', - id: 'tutorials/build-an-nft-marketplace', - }, - items: [ - 'tutorials/build-an-nft-marketplace/part-1', - 'tutorials/build-an-nft-marketplace/part-2', - 'tutorials/build-an-nft-marketplace/part-3', - 'tutorials/build-an-nft-marketplace/part-4', - ], - }, - { - type: 'category', - label: 'Create a mobile game', - link: { - type: 'doc', - id: 'tutorials/mobile', - }, - items: [ - 'tutorials/mobile/part-1', - 'tutorials/mobile/part-2', - 'tutorials/mobile/part-3', - 'tutorials/mobile/part-4', - ], - }, + 'tutorials/smart-contract/jsligo', + 'tutorials/smart-contract/cameligo', + 'tutorials/smart-contract/smartpy', + 'tutorials/smart-contract/archetype', + ], + }, + { + type: 'category', + label: 'Mint NFTs from a web app', + link: { + type: 'doc', + id: 'tutorials/create-an-nft/nft-web-app', + }, + items: [ + 'tutorials/create-an-nft/nft-web-app/setting-up-app', + 'tutorials/create-an-nft/nft-web-app/defining-functions', + 'tutorials/create-an-nft/nft-web-app/lets-play', + ], + }, + { + type: 'category', + label: 'Start with a minimum dApp and add new features', + link: { + type: 'doc', + id: 'tutorials/dapp', + }, + items: [ + 'tutorials/dapp/part-1', + 'tutorials/dapp/part-2', + 'tutorials/dapp/part-3', + 'tutorials/dapp/part-4', + ], + }, + { + type: 'html', + value: '
Intermediate
', + className: 'menu__divider', + }, + { + type: 'category', + label: 'Build a simple web application', + link: { + type: 'doc', + id: 'tutorials/build-your-first-app', + }, + items: [ + 'tutorials/build-your-first-app/setting-up-app', + 'tutorials/build-your-first-app/wallets-tokens', + 'tutorials/build-your-first-app/sending-transactions', + 'tutorials/build-your-first-app/getting-information', + ], + }, + 'tutorials/create-an-nft/nft-taquito', + 'tutorials/create-an-nft/nft-tznft', + { + type: 'html', + value: '
Advanced
', + className: 'menu__divider', + }, + { + type: 'category', + label: 'Deploy a Smart Rollup', + link: { + type: 'doc', + id: 'tutorials/smart-rollup', + }, + items: [ + 'tutorials/smart-rollup/set-up', + 'tutorials/smart-rollup/debug', + 'tutorials/smart-rollup/optimize', + 'tutorials/smart-rollup/deploy', + 'tutorials/smart-rollup/run', + ], + }, + { + type: 'category', + label: 'Build an NFT marketplace', + link: { + type: 'doc', + id: 'tutorials/build-an-nft-marketplace', + }, + items: [ + 'tutorials/build-an-nft-marketplace/part-1', + 'tutorials/build-an-nft-marketplace/part-2', + 'tutorials/build-an-nft-marketplace/part-3', + 'tutorials/build-an-nft-marketplace/part-4', + ], + }, + { + type: 'category', + label: 'Create a mobile game', + link: { + type: 'doc', + id: 'tutorials/mobile', + }, + items: [ + 'tutorials/mobile/part-1', + 'tutorials/mobile/part-2', + 'tutorials/mobile/part-3', + 'tutorials/mobile/part-4', + ], + }, + { + type: 'category', + label: 'Implement a file archive with the DAL', + link: { + type: 'doc', + id: 'tutorials/build-files-archive-with-dal', + }, + items: [ + 'tutorials/build-files-archive-with-dal/get-dal-params', + 'tutorials/build-files-archive-with-dal/get-slot-info', + 'tutorials/build-files-archive-with-dal/publishing-on-the-dal', + 'tutorials/build-files-archive-with-dal/using-full-slot', + ], + }, + { + type: 'category', + label: 'Join the DAL as a Weeklynet baker', + link: { + type: 'doc', + id: 'tutorials/join-dal-baker', + }, + items: [ + 'tutorials/join-dal-baker/get-octez', + 'tutorials/join-dal-baker/run-node', + 'tutorials/join-dal-baker/prepare-account', + 'tutorials/join-dal-baker/run-dal-node', + 'tutorials/join-dal-baker/run-baker', + 'tutorials/join-dal-baker/conclusion', ], }, ], diff --git a/src/css/custom.css b/src/css/custom.css index 2423fd415..9426cf4df 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -148,6 +148,18 @@ nav.navbar { color: #0D61FF; } +/* Headings for tutorials sidebar */ +.menu__divider { + font-family: 'GT Eesti Display', sans-serif; + font-weight: bold; + font-size: 16px; + line-height: 26px; + color: #4A4E52; + transition: color 0.3s; + padding-left: var(--ifm-menu-link-padding-horizontal); + padding-top: 30px; +} + /* breadcrumbs menu */ .breadcrumbs__item--active .breadcrumbs__link { color: #0D61FF;