diff --git a/README.md b/README.md index 83e84b252..f8c25d343 100644 --- a/README.md +++ b/README.md @@ -44,6 +44,124 @@ To run tests locally, run `npm run test -- --filesToCheck=docs/developing.md,doc Docusaurus automatically checks for broken links and markdown-encoded images when you run `npm run build`. +## Search + +Search on the site is powered by Algolia Docsearch. +The index is in the [Algolia dashboard](https://dashboard.algolia.com/apps/QRIAHGML9Q/dashboard). +Contextual search is enabled according to the [Docusaurus instructions](https://docusaurus.io/docs/search#using-algolia-docsearch), although the site does not currently use contextual search to separate searches by version, language, or other similar factors. + +The search uses [this crawler](https://crawler.algolia.com/admin/crawlers/eaa2c548-8b82-493b-8ab8-0c37e2e5d5cc/configuration/edit) to index the site: + +```js +new Crawler({ + rateLimit: 8, + maxDepth: 10, + maxUrls: 5000, + startUrls: ["https://docs.tezos.com/"], + sitemaps: ["https://docs.tezos.com/sitemap.xml"], + renderJavaScript: false, + ignoreCanonicalTo: true, + ignoreQueryParams: ["source", "utm_*"], + discoveryPatterns: ["https://docs.tezos.com/**"], + schedule: "every 24 hours", + appId: "QRIAHGML9Q", + apiKey: "API_KEY_GOES_HERE", + actions: [ + { + indexName: "tezosdocs", + pathsToMatch: ["https://docs.tezos.com/**"], + recordExtractor: ({ $, helpers }) => { + // priority order: deepest active sub list header -> navbar active item -> 'Documentation' + const lvl0 = + $( + ".menu__link.menu__link--sublist.menu__link--active, .navbar__item.navbar__link--active", + ) + .last() + .text() || "Documentation"; + + return helpers.docsearch({ + recordProps: { + lvl0: { + selectors: "", + defaultValue: lvl0, + }, + lvl1: ["header h1", "article h1"], + lvl2: "article h2", + lvl3: "article h3", + lvl4: "article h4", + lvl5: "article h5, article td:first-child", + lvl6: "article h6", + content: "article p, article li, article td:last-child", + }, + indexHeadings: true, + aggregateContent: true, + recordVersion: "v3", + }); + }, + }, + ], + initialIndexSettings: { + tezosdocs: { + attributesForFaceting: [ + "type", + "lang", + "language", + "version", + "docusaurus_tag", + ], + attributesToRetrieve: [ + "hierarchy", + "content", + "anchor", + "url", + "url_without_anchor", + "type", + ], + attributesToHighlight: ["hierarchy", "content"], + attributesToSnippet: ["content:10"], + camelCaseAttributes: ["hierarchy", "content"], + searchableAttributes: [ + "unordered(hierarchy.lvl0)", + "unordered(hierarchy.lvl1)", + "unordered(hierarchy.lvl2)", + "unordered(hierarchy.lvl3)", + "unordered(hierarchy.lvl4)", + "unordered(hierarchy.lvl5)", + "unordered(hierarchy.lvl6)", + "content", + ], + distinct: true, + attributeForDistinct: "url", + customRanking: [ + "desc(weight.pageRank)", + "desc(weight.level)", + "asc(weight.position)", + ], + ranking: [ + "words", + "filters", + "typo", + "attribute", + "proximity", + "exact", + "custom", + ], + highlightPreTag: '', + highlightPostTag: "", + minWordSizefor1Typo: 3, + minWordSizefor2Typos: 7, + allowTyposOnNumericTokens: false, + minProximity: 1, + ignorePlurals: true, + advancedSyntax: true, + attributeCriteriaComputedByMinProximity: true, + removeWordsIfNoResults: "allOptional", + separatorsToIndex: "_", + }, + }, +}); +``` + ## License This project is open for contribution but the source code itself uses a commercial template and is therefore not licensed under any open-source license. Forking this project as a base for your own projects is not permitted under the license of the original template. diff --git a/docs/architecture.mdx b/docs/architecture.mdx index 1aae651d7..3a150d7cf 100644 --- a/docs/architecture.mdx +++ b/docs/architecture.mdx @@ -151,7 +151,7 @@ Optionally, this node can open its RPC interface to serve different kinds of req For more information about the architecture of Tezos, see: -- [Accounts](./architecture/accounts) +- [Accounts and addresses](./architecture/accounts) - [Tokens](./architecture/tokens) - [Smart Optimistic Rollups](./architecture/smart-rollups) - [Governance](./architecture/governance) diff --git a/docs/architecture/accounts.md b/docs/architecture/accounts.md index 1dad01d8c..f196d96db 100644 --- a/docs/architecture/accounts.md +++ b/docs/architecture/accounts.md @@ -1,21 +1,27 @@ --- -title: Accounts +title: Accounts and addresses authors: "Tim McMackin" last_update: - date: 29 December 2023 + date: 10 January 2024 --- +## Accounts + Tezos uses these types of accounts: -- Classic accounts (also known as _implicit accounts_) store tez (ꜩ) and tickets. -These accounts have addresses that start with "tz1", "tz2", "tz3" or "tz4." -Any wallet application or the Octez command-line tool can create implicit accounts. +- User accounts (sometimes known as _implicit accounts_) store tez (ꜩ) and tickets. +Any wallet application or the Octez command-line tool can create user accounts. -- Smart contract accounts (also known as _originated accounts_) store immutable code, mutable storage, tez (ꜩ), and tickets. -Smart contracts have addresses that start with "KT1." +- Smart contract accounts (sometimes known as _originated accounts_) store immutable code, mutable storage, tez (ꜩ), and tickets. See [Smart contracts](../smart-contracts). -- Smart Rollup accounts are another type of originated account. -Their addresses start with `SR1`. +## Addresses + +- User accounts have addresses that start with "tz1", "tz2", "tz3" or "tz4." + +- Smart contracts have addresses that start with "KT1." + +- Smart Rollups have addresses, but are not accounts because they cannot store tez. +Their addresses start with "SR1". They have a tree of commitments attached to them. See [Smart Optimistic Rollups](./smart-rollups). diff --git a/docs/dApps.md b/docs/dApps.md deleted file mode 100644 index 3e4f61ad1..000000000 --- a/docs/dApps.md +++ /dev/null @@ -1,12 +0,0 @@ -# Decentralized applications (dApps) - -One of the main features of blockchains is the _decentralization_: each transaction sent is verified by multiple nodes and its validation process does not rely on a single trusted third party. -Decentralized applications (dApps or Dapps) take advantage of these features to create applications that are independent, transparent, and trustless. - -In general, dApps have two parts: - -- An on-chain component that consists of one or more smart contracts -- An off-chain component that can act as a user interface to simplify interaction with the on-chain component, run off-chain processing, and get information from the outside world - -The off-chain component can be nearly any kind of program, including a web application, mobile or desktop app, or command-line interface. -It relies on wallets to interact with the smart contract on behalf of a user's Tezos account. diff --git a/docs/dApps.mdx b/docs/dApps.mdx new file mode 100644 index 000000000..f8f808787 --- /dev/null +++ b/docs/dApps.mdx @@ -0,0 +1,52 @@ +--- +title: Decentralized applications (dApps) +authors: Benjamin Pilia, Tim McMackin +last_update: + date: 12 January 2024 +--- + +import LucidDiagram from '@site/src/components/LucidDiagram'; + +One of the main features of blockchains is _decentralization_: each transaction is verified by multiple nodes and its validation process does not rely on a single trusted third party. +Decentralized applications (dApps or Dapps) take advantage of these features to create applications that are independent, transparent, and trustless. + +In general, dApps have these parts: + +- **Frontend**: An off-chain component that can act as a user interface to simplify interaction with the on-chain component, run off-chain processing, and get information from sources that are not available to the on-chain component +- **Middleware**: Optionally, an [indexer](./developing/information/indexers) to interpret the backend information and provide it in a more convenient format for the front-end component +- **Backend**: An on-chain component that consists of one or more [smart contracts](./smart-contracts) + +The off-chain component can be nearly any kind of program, including a web application, mobile or desktop app, or command-line interface. +It relies on wallets and tools to interact with the smart contract on behalf of a user's Tezos account. + + + +Some of these tools that allow an off-chain component to interact with smart contracts include: + +- [Taquito](./dApps/taquito), an SDK for JavaScript/TypeScript applications +- The [Tezos SDK for Unity](./unity), a toolkit for Unity applications +- [Taqueria](https://taqueria.io/), a development platform for dApps + +## Sample dApps + +For example dApps, see [Sample dApps](./dApps/samples). + +## Best practices + +Good programming and design practices make dApps easier to use and provide a better user experience. +See [Best practices and avoiding flaws](./dApps/best-practices). + +## dApp tasks + +For information on typical tasks that dApps do, see: + +- [Connecting to wallets](./dApps/wallets) +- [Sending transactions](./dApps/sending-transactions) + +## Tutorials + +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 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/taquito.md b/docs/dApps/taquito.md index c12c122c0..b418094f7 100644 --- a/docs/dApps/taquito.md +++ b/docs/dApps/taquito.md @@ -89,13 +89,13 @@ Tezos.setWalletProvider(wallet) ## Getting data from the Tezos blockchain -Taquito provides methods to get different types of data from the Tezos blockchain, for example, the balance of an implicit account, the storage of a contract or token metadata. +Taquito provides methods to get different types of data from the Tezos blockchain, for example, the balance of a user account, the storage of a contract or token metadata. > Note: querying data from the blockchain doesn't create a new transaction. ### Getting the balance of an account -Taquito allows developers to get the current balance in tez of an implicit account. The `getBalance` method is available on the instance of the TezosToolkit and requires a parameter of type `string` that represents the address of the account. +Taquito allows developers to get the current balance in tez of a user account. The `getBalance` method is available on the instance of the TezosToolkit and requires a parameter of type `string` that represents the address of the account. The returned value is of type `BigNumber`: diff --git a/docs/overview/glossary.md b/docs/overview/glossary.md index 9092cadde..dbdb12eb2 100644 --- a/docs/overview/glossary.md +++ b/docs/overview/glossary.md @@ -129,7 +129,7 @@ The following is adapted from this [Agora post](https://forum.tezosagora.org/t/n In the context, each account is associated with a balance (an amount of tez available). - An account can be either an originated account or an implicit account. + An account can be a user account or a smart contract. - **Baker** @@ -190,9 +190,9 @@ The following is adapted from this [Agora post](https://forum.tezosagora.org/t/n - **Delegate** - An implicit account that can participate in consensus and in governance. + A user account that can participate in consensus and in governance. Actual participation is under further provisions, like having a minimal stake. - An implicit account becomes a delegate by registering as such. + A user account becomes a delegate by registering as such. Through delegation, other accounts can delegate their rights to a delegate account. The delegate's rights are calculated based on its stake. Note that `tz4` accounts cannot be delegates. @@ -252,15 +252,7 @@ The following is adapted from this [Agora post](https://forum.tezosagora.org/t/n - **Implicit account** - An account that is linked to a public key. Contrary to a smart - contract, an implicit account cannot include a script and it - cannot reject incoming transactions. - - If *registered*, an implicit account can act as a delegate. - - The address of an implicit account always starts with the - letters tz followed by 1, 2, 3, or 4 (depending on the - signature scheme) and finally the hash of the public key. + See [User account](#user-account). - **Layer 1** @@ -345,6 +337,20 @@ The following is adapted from this [Agora post](https://forum.tezosagora.org/t/n An operation to transfer tez between two accounts, or to run the code of a smart contract. + + +- **User account** + + An account that is linked to a public key. Contrary to a smart + contract, a user account cannot include a script and it + cannot reject incoming transactions. + + If *registered*, a user account can act as a delegate. + + The address of a user account always starts with the + letters tz followed by 1, 2, 3, or 4 (depending on the + signature scheme) and finally the hash of the public key. + - **Validation pass** An index (a natural number) associated with a particular kind of diff --git a/docs/smart-contracts/data-types/complex-data-types.md b/docs/smart-contracts/data-types/complex-data-types.md index 801c9c15b..c120d688f 100644 --- a/docs/smart-contracts/data-types/complex-data-types.md +++ b/docs/smart-contracts/data-types/complex-data-types.md @@ -392,7 +392,7 @@ The ticket's information is public and can be read by any contract that holds th Contracts can pass tickets to entrypoints to change which contract is in control of the ticket. If contract A passes a ticket to contract B, contract A loses all access to the ticket. -Contracts can pass tickets only to other contracts (implicit accounts) because the entrypoint must accept a ticket of the correct type; contracts cannot pass tickets to user accounts. +Contracts can pass tickets to other contracts via entrypoints accepting a ticket of the correct type; contracts can also pass tickets to user accounts. ### Ticket features diff --git a/docs/smart-contracts/data-types/primitive-data-types.md b/docs/smart-contracts/data-types/primitive-data-types.md index bb3920e74..d7d56e3f7 100644 --- a/docs/smart-contracts/data-types/primitive-data-types.md +++ b/docs/smart-contracts/data-types/primitive-data-types.md @@ -160,16 +160,16 @@ The following operations are supported on timestamps: ## Addresses {#addresses} -On Tezos, each account is uniquely identified by its `address`, whether it is a user account (implicit account) or a contract (originated account). +On Tezos, each account is uniquely identified by its `address`. Internally, addresses take the form of a `string` type. -For implicit accounts, the string starts with "tz1", "tz2", "tz3" or "tz4". -For originated accounts, the string starts with "KT1". +For user accounts, the string starts with "tz1", "tz2", "tz3" or "tz4". +For smart contract accounts, the string starts with "KT1". | Type of Account | Example | | --- | --- | -| Implicit Account | `tz1YWK1gDPQx9N1Jh4JnmVre7xN6xhGGM4uC` | -| Originated Account | `KT1S5hgipNSTFehZo7v81gq6fcLChbRwptqy` | +| User account | `tz1YWK1gDPQx9N1Jh4JnmVre7xN6xhGGM4uC` | +| Smart contract | `KT1S5hgipNSTFehZo7v81gq6fcLChbRwptqy` | The next part of the string is a `Base58` encoded hash, followed by a 4-byte checksum. diff --git a/docs/smart-contracts/deploying.md b/docs/smart-contracts/deploying.md index 9e3656b26..68a8d3333 100644 --- a/docs/smart-contracts/deploying.md +++ b/docs/smart-contracts/deploying.md @@ -5,7 +5,7 @@ last_update: date: 6 November 2023 --- ## Introduction -In Tezos, deploying a smart contract is often referred to as “origination”. This process essentially creates a new account that holds the smart contract's script. Contracts originated in this manner have addresses that start with `KT1` (known as originated accounts), which distinguishes them from the implicit accounts with addresses beginning with `tz1`, `tz2`, or `tz3`. +In Tezos, deploying a smart contract is often referred to as “origination”. This process essentially creates a new account that holds the smart contract's script. Contracts originated in this manner have addresses that start with `KT1`, which distinguishes them from the user accounts with addresses beginning with `tz1`, `tz2`, or `tz3`. ## Prerequisites - Compile your contract and its initial storage diff --git a/docs/smart-contracts/logic/comparing.md b/docs/smart-contracts/logic/comparing.md index b9843a120..e7791c02e 100644 --- a/docs/smart-contracts/logic/comparing.md +++ b/docs/smart-contracts/logic/comparing.md @@ -17,7 +17,7 @@ How values are compared depends on the type of the values: - Strings, `bytes`, `key_hash`, `key`, `signature` and `chain_id` values are compared lexicographically. - Boolean values are compared so that false is strictly less than true. - Address are compared as follows: - - Addresses of implicit accounts are strictly less than addresses of originated accounts. + - Addresses of user accounts are strictly less than addresses of smart contracts. - Addresses of the same type are compared lexicographically. - Pair values (and therefore records) are compared component by component, starting with the first component. - Options are compared as follows: diff --git a/docs/smart-contracts/multisig-usage.md b/docs/smart-contracts/multisig-usage.md index 6b65c1ac5..67bdf6456 100644 --- a/docs/smart-contracts/multisig-usage.md +++ b/docs/smart-contracts/multisig-usage.md @@ -58,7 +58,7 @@ Note, this section uses the The Generic Multisig allows us to set administrators of the contract (`signerKeys`) and the number of those administrators required to sign -(`threshold`). As of writing, the command line tool only allows `tz1` implicit +(`threshold`). As of writing, the command line tool only allows `tz1` user accounts to be administrators, though the contract allows `KT1` originated accounts as well. diff --git a/docs/smart-contracts/special-values.md b/docs/smart-contracts/special-values.md index ae3a3b5c7..1b25057ce 100644 --- a/docs/smart-contracts/special-values.md +++ b/docs/smart-contracts/special-values.md @@ -27,7 +27,7 @@ For example, assume that user A called contract B that in turn called contract C When C runs, `source` is the address of A, while `caller` is the address of B. :::warning Access permissions -It is best practice to implement permissioning based on `caller` instead of `source` because any implicit account can call any entrypoint on Tezos. +It is best practice to implement permissioning based on `caller` instead of `source` because any user account can call any entrypoint on Tezos. ::: - `self`: The address of the contract itself. diff --git a/docs/tutorials/dapp/part-1.md b/docs/tutorials/dapp/part-1.md index 1854d7d23..27415200b 100644 --- a/docs/tutorials/dapp/part-1.md +++ b/docs/tutorials/dapp/part-1.md @@ -164,7 +164,7 @@ Taqueria is generating the `.tz` Michelson file on the `artifacts` folder. The M The default Tezos testing testnet is called **Ghostnet**. -> :warning: You need an account to deploy a contract with some `tez` (the Tezos native currency). The first time you deploy a contract with Taqueria, it is generating a new implicit account with `0 tez`. +> :warning: You need an account to deploy a contract with some `tez` (the Tezos native currency). The first time you deploy a contract with Taqueria, it is generating a new user account with `0 tez`. 1. Deploy your contract to the `testing` environment. Ut forces Taqueria to generate a default account on a testing config file. diff --git a/docs/tutorials/dapp/part-2.md b/docs/tutorials/dapp/part-2.md index d2d8a93ee..5e8b8b8a9 100644 --- a/docs/tutorials/dapp/part-2.md +++ b/docs/tutorials/dapp/part-2.md @@ -201,7 +201,7 @@ sequenceDiagram - `#import "./pokeGame.jsligo" "PokeGame"` to import the source file as module in order to call functions and use object definitions. - `export type main_fn` it will be useful later for the mutation tests to point to the main function to call/mutate. - - `Test.reset_state ( 2...` this creates two implicit accounts on the test environment. + - `Test.reset_state ( 2...` this creates two user accounts on the test environment. - `Test.nth_bootstrap_account` this return the nth account from the environment. - `Test.to_contract(taddr)` and `Tezos.address(contr)` are util functions to convert typed addresses, contract and contract addresses. - `let _testPoke = (s : address) : unit => {...}` declaring function starting with `_` is escaping the test for execution. Use this to factorize tests changing only the parameters of the function for different scenarios. diff --git a/docs/tutorials/dapp/part-3.md b/docs/tutorials/dapp/part-3.md index ac207fc76..baba11aac 100644 --- a/docs/tutorials/dapp/part-3.md +++ b/docs/tutorials/dapp/part-3.md @@ -49,7 +49,7 @@ Tickets features: - Not comparable: it makes no sense to compare tickets because tickets from same type are all equals and can be merged into a single ticket. When ticket types are different then it is no more comparable. - Transferable: you can send ticket into a Transaction parameter. -- Storable: only on smart contract storage for the moment (Note: a new protocol release will enable it for implicit account soon). +- Storable: only on smart contract storage for the moment (Note: a new protocol release will enable it for user account soon). - Non dupable: you cannot copy or duplicate a ticket, it is a unique singleton object living in specific blockchain instance. - Splittable: if amount is > 2 then you can split ticket object into 2 objects. - Mergeable: you can merge ticket from same ticketer and same type. diff --git a/docusaurus.config.js b/docusaurus.config.js index 656a77851..26b5ba1fc 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -22,7 +22,7 @@ img-src 'self' https://*.googletagmanager.com https://*.google-analytics.com dat media-src 'self'; form-action 'self'; connect-src 'self' https://*.algolia.net https://*.algolianet.com https://*.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; -frame-src https://tezosbot.vercel.app https://calendly.com/ lucid.app;`; +frame-src https://tezosbot.vercel.app lucid.app;`; /** @type {import('@docusaurus/types').Config} */ const config = { @@ -142,7 +142,7 @@ const config = { apiKey: process.env.NEXT_PUBLIC_DOCSEARCH_API_KEY || "57d6a376a3528866784a143809cc7427", indexName: process.env.NEXT_PUBLIC_DOCSEARCH_INDEX_NAME || "tezosdocs", // Optional: see doc section below - contextualSearch: false, + contextualSearch: true, // Optional: Specify domains where the navigation should occur through window.location instead on history.push. Useful when our Algolia config crawls multiple documentation sites and we want to navigate with window.location.href to them. // externalUrlRegex: 'external\\.com|domain\\.com', // Optional: Replace parts of the item URLs from Algolia. Useful when using the same search index for multiple deployments using a different baseUrl. You can use regexp or string in the `from` param. For example: localhost:3000 vs myCompany.com/docs diff --git a/package-lock.json b/package-lock.json index 037d12193..2b672c0b9 100644 --- a/package-lock.json +++ b/package-lock.json @@ -20,7 +20,6 @@ "plugin-image-zoom": "github:flexanalytics/plugin-image-zoom", "prism-react-renderer": "1.3.5", "react": "18.2", - "react-calendly": "4.3.0", "react-dom": "18.2", "rehype-katex": "7.0.0", "remark-math": "6.0.0", @@ -14204,19 +14203,6 @@ "node": ">=0.10.0" } }, - "node_modules/react-calendly": { - "version": "4.3.0", - "resolved": "https://registry.npmjs.org/react-calendly/-/react-calendly-4.3.0.tgz", - "integrity": "sha512-JFZzYhyJBaoZDseB3UqzeOx1rbzCK24nr5pqH/6zJEh7CZ/pn5R49rkIJ0g5E7j5WQ3K7xBSgBD7WgM36v3gZw==", - "engines": { - "node": ">=8", - "npm": ">=5" - }, - "peerDependencies": { - "react": ">=16.8.0", - "react-dom": ">=16.8.0" - } - }, "node_modules/react-dev-utils": { "version": "12.0.1", "resolved": "https://registry.npmjs.org/react-dev-utils/-/react-dev-utils-12.0.1.tgz", diff --git a/package.json b/package.json index 695725b0d..de6a30869 100644 --- a/package.json +++ b/package.json @@ -27,7 +27,6 @@ "plugin-image-zoom": "github:flexanalytics/plugin-image-zoom", "prism-react-renderer": "1.3.5", "react": "18.2", - "react-calendly": "4.3.0", "react-dom": "18.2", "rehype-katex": "7.0.0", "remark-math": "6.0.0", diff --git a/sidebars.js b/sidebars.js index f7382e384..dae502ddc 100644 --- a/sidebars.js +++ b/sidebars.js @@ -176,10 +176,10 @@ const sidebars = { { type: 'category', label: 'Decentralized applications (dApps)', - // link: { // TODO - // id: 'dApps', - // type: 'doc', - // }, + link: { + id: 'dApps', + type: 'doc', + }, items: [ // 'dApps/first-dapp', // TODO 'dApps/samples', diff --git a/src/components/BuildSection/styles.module.css b/src/components/BuildSection/styles.module.css index f8a6b35ca..b6943967c 100644 --- a/src/components/BuildSection/styles.module.css +++ b/src/components/BuildSection/styles.module.css @@ -6,7 +6,6 @@ height: auto; padding: 100px 81px; background: #F2F3F7; - margin-top: 90px; } .container { diff --git a/src/components/CalendlyEmbed.jsx b/src/components/CalendlyEmbed.jsx deleted file mode 100644 index c0ceab351..000000000 --- a/src/components/CalendlyEmbed.jsx +++ /dev/null @@ -1,36 +0,0 @@ -import React, { useState, useEffect } from 'react'; -import { InlineWidget } from 'react-calendly'; - -export default function CalendlyEmbed() { - const url = 'https://calendly.com/developer-success-on-tezos/15min'; - const [isMobile, setIsMobile] = useState(false); - - useEffect(() => { - const handleResize = () => { - setIsMobile(window.innerWidth < 1000); - }; - window.addEventListener('resize', handleResize); - handleResize(); - return () => window.removeEventListener('resize', handleResize); - }, []); - - return ( -
- {isMobile ? ( - - ) : ( - - )} -
- ); -} diff --git a/src/pages/index.js b/src/pages/index.js index d23bdbaef..36ff855e1 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -3,7 +3,6 @@ import clsx from 'clsx'; import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; import Layout from '@theme/Layout'; import HomepageFeatures from '@site/src/components/HomepageFeatures'; -import CalendlyEmbed from '@site/src/components/CalendlyEmbed.jsx'; import styles from './index.module.css'; import BuildSection from '@site/src/components/BuildSection'; import Footer from '@site/src/components/Footer'; @@ -30,11 +29,6 @@ export default function Home() {
-
-

We are here for you

-

Book a 15 min, 1 to 1 session hosted by the TriliTech Developer Success team to discuss and answer your technical questions.

-
-