diff --git a/docs/primitives/dao.md b/docs/primitives/dao.md index 0d8949a2c38..44889594c40 100644 --- a/docs/primitives/dao.md +++ b/docs/primitives/dao.md @@ -18,7 +18,7 @@ Decentralized Autonomous Organizations (DAOs) are self-organized groups that for ![dao](/assets/docs/primitives/dao.png) In contrast with [FT](./ft/ft.md) and [NFT](./nft/nft.md), DAO contract's are not standardized. Because of this, on this page we will use as -reference the [Astra dao](https://dev.near.org/astraplusplus.ndctools.near/widget/home?page=daos) [contract](https://github.com/near-daos/sputnik-dao-contract). The main concepts covered here should +reference the [sputnik dao contract](https://github.com/near-daos/sputnik-dao-contract). The main concepts covered here should easily generalizable to other DAO implementations. :::tip diff --git a/docs/protocol/account-model.md b/docs/protocol/account-model.md index 09e7e52ac19..57e34793934 100644 --- a/docs/protocol/account-model.md +++ b/docs/protocol/account-model.md @@ -15,7 +15,7 @@ By signing [transactions](./transactions.md) with their account, users can: 4. Help onboard new users by **covering the costs** of their transactions (gas fees) :::tip Want to create an account? -You have multiple ways to create an account, you can [sign-up using your email](https://dev.near.org/signup), get a mobile wallet through [telegram](https://web.telegram.org/k/#@herewalletbot), or create a [web wallet](https://wallet.meteorwallet.app) +Check out our tutorial on [Creating a NEAR Account](../tutorials/protocol/create-account.md) to get started! ::: --- diff --git a/docs/protocol/basics.md b/docs/protocol/basics.md index d8a7b4d5316..79e8d0ddfa2 100644 --- a/docs/protocol/basics.md +++ b/docs/protocol/basics.md @@ -35,7 +35,7 @@ NEAR is a technical marvel, offering built-in features such as named accounts an ### ⭐ Simple to Use 1. Use [**named accounts**](./account-model.md) like `alice.near` -2. Simple sign-up: make an account using [email](https://dev.near.org/signup) or [telegram](https://web.telegram.org/k/#@herewalletbot) +2. Simple sign-up: create an [account for free](../tutorials/protocol/create-account.md), login [with socials](../web3-apps/tutorials/wallet-login.md) or [telegram](https://web.telegram.org/k/#@herewalletbot) 3. Transactions are **fast** _(~1.3s finality)_ and **cheap** _(< 1¢ in fees)_ 4. You don't need to buy crypto thanks to **built-in account abstraction** 5. [Access Keys](./access-keys.md) make it safe and easy to use diff --git a/docs/smart-contracts/what-is.md b/docs/smart-contracts/what-is.md index d9cc7120216..285658ebed0 100644 --- a/docs/smart-contracts/what-is.md +++ b/docs/smart-contracts/what-is.md @@ -54,10 +54,10 @@ Besides, smart contracts can store data in the account's storage. This allows co ## What are they used for? Smart contracts are useful to create **decentralized applications**. Some traditional examples include: -- [Decentralized Autonomous Organizations](https://dev.near.org/applications?cat=dao), where users create and vote proposals -- [Marketplaces](https://dev.near.org/applications?cat=marketplaces), where users create and commercialize digital art pieces -- [Decentralized exchanges](https://dev.near.org/applications?cat=exchanges), where users can trade different currencies -- [And many more...](https://dev.near.org/applications) +- [Decentralized Autonomous Organizations](https://nearcatalog.xyz/?cat=dao), where users create and vote proposals +- [Marketplaces](https://nearcatalog.xyz/?cat=marketplaces), where users create and commercialize digital art pieces +- [Decentralized exchanges](https://nearcatalog.xyz/?cat=exchanges), where users can trade different currencies +- [And many more...](https://nearcatalog.xyz/) For instance, you can easily create a crowdfunding contract that accepts $NEAR. If the goal is met in time, the creator can claim the funds. Otherwise, the backers are refunded. diff --git a/docs/tutorials/examples/global-contracts.md b/docs/tutorials/examples/global-contracts.md index 0ff905190f0..54ba90996f6 100644 --- a/docs/tutorials/examples/global-contracts.md +++ b/docs/tutorials/examples/global-contracts.md @@ -104,8 +104,8 @@ Since there are two ways to reference a global contract ([by account](../../smar To do this, use the `deployGlobalContract` function and set the mode to `accountId`, along with the contract’s code bytes. - @@ -116,8 +116,8 @@ Since there are two ways to reference a global contract ([by account](../../smar To do this, use the `deployGlobalContract` function and set the mode to `codeHash`, along with the contract’s code bytes. - @@ -206,8 +206,8 @@ Let’s see how you can reference and use your global contract from another acco To reference a global contract by account, you need to call the `useGlobalContract` function and pass the source `accountId` where the contract was originally deployed. - @@ -220,8 +220,8 @@ Let’s see how you can reference and use your global contract from another acco const hash = bs58.encode(sha256(wasm)); ``` - diff --git a/docs/tutorials/examples/near-drop.md b/docs/tutorials/examples/near-drop.md index f85a65cdbeb..ac244616ad7 100644 --- a/docs/tutorials/examples/near-drop.md +++ b/docs/tutorials/examples/near-drop.md @@ -17,7 +17,7 @@ Particularly, it shows: :::tip -This example showcases a simplified version of the contract that both [Keypom](https://github.com/keypom/keypom) and the [Token Drop Utility](https://dev.near.org/tools?tab=linkdrops) use to distribute tokens to users +This example showcases a simplified version of the contract that both [Keypom](https://github.com/keypom/keypom) and the [Token Drop Utility](https://docs.near.org/toolbox?tab=linkdrops) use to distribute tokens to users ::: diff --git a/docs/web3-apps/backend/backend.md b/docs/web3-apps/backend/backend.md index 852216a9ad4..680adf5de26 100644 --- a/docs/web3-apps/backend/backend.md +++ b/docs/web3-apps/backend/backend.md @@ -65,5 +65,5 @@ const signature = wallet.signMessage({ message, recipient, nonce: challenge, cal ### 3. Verify the Signature Once the user has signed the challenge, the wallet will call the `callbackUrl` with the signature. The backend can then verify the signature. - + diff --git a/website/package.json b/website/package.json index f125983d5ff..0365e439f95 100644 --- a/website/package.json +++ b/website/package.json @@ -38,6 +38,7 @@ "@docusaurus/preset-classic": "3.9.2", "@docusaurus/theme-mermaid": "3.9.2", "@feelback/react": "^0.3.4", + "@hot-labs/near-connect": "^0.8.2", "@mermaid-js/layout-elk": "^0.2.0", "@saucelabs/theme-github-codeblock": "^0.3.0", "axios": "^1.12.0", diff --git a/website/src/theme/Root.js b/website/src/theme/Root.js index 57928d8bdb1..699587cbbba 100644 --- a/website/src/theme/Root.js +++ b/website/src/theme/Root.js @@ -49,18 +49,6 @@ function Root({ children, location }) { siteConfig: { customFields }, } = useDocusaurusContext(); - useEffect(() => { - // Pass message to dev.near.org (docs is embedded there) - const sendMessage = (url) => - parent.postMessage({ type: 'urlChange', url }, 'https://dev.near.org/'); - sendMessage(location.pathname); - - const unlisten = history.listen((loc) => sendMessage(loc.pathname)); - return () => { - unlisten(); - }; - }, [history]); - useEffect(() => { // Initialize Gleap if (isBrowser) {