diff --git a/CLAUDE.md b/CLAUDE.md index 190e12c22..e3a631485 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,7 +1,7 @@ # CLAUDE.md - Repository Assistant Guide ## Repository Overview -This is the ar-io/docs repository, which manages the documentation for the AR.IO Developer Platform. It references various services, SDKs and tools for building on and with the AR.IO Network. It also includes documentation for interacting with ArDrive - a flagship consumer dApp that stores data on Arweave. +This is the ar-io/docs repository, which manages the documentation for the ar.io Developer Platform. It references various services, SDKs and tools for building on and with ar.io. It also includes documentation for interacting with ArDrive - a flagship consumer dApp that stores data on Arweave. ## Architecture This repository is built with [Fumadocs](https://fumadocs.dev/), a documentation framework. The general architecture is as follows: @@ -54,11 +54,11 @@ The repository supports OpenAPI documentation import (see recent commit 33af22f2 - Run linting and type checking before committing ## Community Resources -- **Discord**: https://discord.com/invite/HGG52EtTc2 - Join the AR.IO community for updates and discussions +- **Discord**: https://discord.com/invite/HGG52EtTc2 - Join the ar.io community for updates and discussions ## Important Notes - This is a documentation repository - focus on content clarity and accuracy -- Always verify technical details match the actual AR.IO implementation +- Always verify technical details match the actual ar.io implementation - Maintain consistent terminology throughout documentation - Test all code examples before including them in documentation diff --git a/README.md b/README.md index a8da91fa7..049dd2dbd 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ -# Ar.io Documentation +# ar.io Documentation -Ar.io Documentation is a Next.js site built with Fumadocs that hosts the product and developer documentation for the ar.io network and tooling. It contains authored guides, API references, and autogenerated content sourced from scripts in this repository. +ar.io Documentation is a Next.js site built with Fumadocs that hosts the product and developer documentation for the ar.io network and tooling. It contains authored guides, API references, and autogenerated content sourced from scripts in this repository. ## Docs Site diff --git a/content/apis/ar-io-node/admin.mdx b/content/apis/ar-io-node/admin.mdx index 24f0072d8..07f158f8c 100644 --- a/content/apis/ar-io-node/admin.mdx +++ b/content/apis/ar-io-node/admin.mdx @@ -20,12 +20,12 @@ _openapi: url: '#get-bundle-processing-status' - depth: 2 title: >- - Blocks transactions or data-items so your Ar.io Gateway will not serve + Blocks transactions or data-items so your ar.io Gateway will not serve them. url: >- #blocks-transactions-or-data-items-so-your-ario-gateway-will-not-serve-them - depth: 2 - title: Blocks an ARNS name so your Ar.io Gateway will not serve it. + title: Blocks an ARNS name so your ar.io Gateway will not serve it. url: '#blocks-an-arns-name-so-your-ario-gateway-will-not-serve-it' - depth: 2 title: Unblock an ARNS name. @@ -52,11 +52,11 @@ _openapi: - content: Get bundle processing status id: get-bundle-processing-status - content: >- - Blocks transactions or data-items so your Ar.io Gateway will not serve + Blocks transactions or data-items so your ar.io Gateway will not serve them. id: >- blocks-transactions-or-data-items-so-your-ario-gateway-will-not-serve-them - - content: Blocks an ARNS name so your Ar.io Gateway will not serve it. + - content: Blocks an ARNS name so your ar.io Gateway will not serve it. id: blocks-an-arns-name-so-your-ario-gateway-will-not-serve-it - content: Unblock an ARNS name. id: unblock-an-arns-name @@ -69,7 +69,7 @@ _openapi: contents: - content: >- Get detailed information about the current operational state of your - Ar.io Gateway, including information about any current warnings or + ar.io Gateway, including information about any current warnings or errors. heading: admin-debugging-information - content: >- @@ -97,7 +97,7 @@ _openapi: heading: get-bundle-processing-status - content: > Submits a TX ID/data-item ID or sha-256 content hash for content you - do not want your Ar.io Gateway to serve. Once submitted, your Gateway + do not want your ar.io Gateway to serve. Once submitted, your Gateway will not respond to requests for these transactions or data-items. @@ -106,9 +106,9 @@ _openapi: by your Gateway. heading: >- blocks-transactions-or-data-items-so-your-ario-gateway-will-not-serve-them - - content: Blocks an ARNS name so your Ar.io Gateway will not serve it. + - content: Blocks an ARNS name so your ar.io Gateway will not serve it. heading: blocks-an-arns-name-so-your-ario-gateway-will-not-serve-it - - content: Unblock an ARNS name so your Ar.io Gateway will serve it again. + - content: Unblock an ARNS name so your ar.io Gateway will serve it again. heading: unblock-an-arns-name - content: > Initiates an export of data to Parquet format files. This process runs @@ -128,7 +128,7 @@ _openapi: {/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */} -Access several password protected features and functions specific to your Ar.io Gateway. +Access several password protected features and functions specific to your ar.io Gateway. \ No newline at end of file diff --git a/content/apis/ar-io-node/arns.mdx b/content/apis/ar-io-node/arns.mdx index 6edd7f34e..8a4e142d0 100644 --- a/content/apis/ar-io-node/arns.mdx +++ b/content/apis/ar-io-node/arns.mdx @@ -13,7 +13,7 @@ _openapi: {/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */} -Get data from the Ar.io Gateway Arweave Name System +Get data from the ar.io Gateway Arweave Name System \ No newline at end of file diff --git a/content/apis/ar-io-node/gateway.mdx b/content/apis/ar-io-node/gateway.mdx index 3ef95f648..851b6ce45 100644 --- a/content/apis/ar-io-node/gateway.mdx +++ b/content/apis/ar-io-node/gateway.mdx @@ -24,16 +24,16 @@ _openapi: transaction or ArNS-resolved data (e.g., text/html for HTML documents, application/json for JSON documents, application/octet-stream for binary data, etc.). - - content: Get the current health status of the Ar.io Gateway. + - content: Get the current health status of the ar.io Gateway. - content: | - Returns information about the Ar.io Gateway, including: + Returns information about the ar.io Gateway, including: - Gateway wallet address - Process ID - ANS-104 filter configurations - Supported manifest versions - Gateway software release version - content: > - Returns information about Ar.io Gateway peers and Arweave node peers. + Returns information about ar.io Gateway peers and Arweave node peers. For gateways, includes both data and chunk weights used for peer selection. @@ -59,7 +59,7 @@ _openapi: {/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */} -Operations related to the Ar.io Gateway server itself, including health checks, metrics, and gateway-specific information +Operations related to the ar.io Gateway server itself, including health checks, metrics, and gateway-specific information \ No newline at end of file diff --git a/content/apis/ar-io-node/index-querying.mdx b/content/apis/ar-io-node/index-querying.mdx index b70dad8c5..7bb6a52a5 100644 --- a/content/apis/ar-io-node/index-querying.mdx +++ b/content/apis/ar-io-node/index-querying.mdx @@ -27,7 +27,7 @@ _openapi: {/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */} -Get data from the Ar.io Gateway index using GQL +Get data from the ar.io Gateway index using GQL \ No newline at end of file diff --git a/content/apis/ar-io-node/index.mdx b/content/apis/ar-io-node/index.mdx index 621acc591..055132dec 100644 --- a/content/apis/ar-io-node/index.mdx +++ b/content/apis/ar-io-node/index.mdx @@ -1,5 +1,5 @@ --- -title: "Ar.io Gateway APIs" +title: "ar.io Gateway APIs" description: "Core gateway software for accessing, caching, and querying data on Arweave" --- @@ -13,11 +13,11 @@ import { FileText, } from "lucide-react"; -The Ar.io Gateway is the core software for the ar.io network, serving the essential responsibility of gateways for accessing, caching, and querying data stored on Arweave. It provides a robust, decentralized infrastructure for interacting with the permanent web. +The ar.io Gateway is the core software for the ar.io network, serving the essential responsibility of gateways for accessing, caching, and querying data stored on Arweave. It provides a robust, decentralized infrastructure for interacting with the permanent web. ## Core Responsibilities -The Ar.io Gateway handles fundamental operations for the Arweave ecosystem: +The ar.io Gateway handles fundamental operations for the Arweave ecosystem: - **Data Access** - Retrieve transaction data, files, and metadata from Arweave - **Caching** - Intelligent caching strategies for improved performance and availability @@ -27,7 +27,7 @@ The Ar.io Gateway handles fundamental operations for the Arweave ecosystem: ## Advanced Features -Beyond basic gateway functionality, Ar.io Gateway includes sophisticated capabilities: +Beyond basic gateway functionality, ar.io Gateway includes sophisticated capabilities: - **Parquet Generation** - Convert Arweave data into optimized Parquet format for analytics - **Data Verification** - Cryptographic verification of data integrity and authenticity @@ -76,7 +76,7 @@ Beyond basic gateway functionality, Ar.io Gateway includes sophisticated capabil /> -## Get Involved with Ar.io Gateways +## Get Involved with ar.io Gateways } - title="Ar.io Gateway" + icon={ar.io} + title="ar.io Gateway" description="The core gateway software providing access to data on Arweave. Includes data retrieval, ArNS resolution, and network management." href="/apis/ar-io-node" /> } + icon={Turbo} title="Turbo" description="Upload and payment services providing fast, reliable data uploads to Arweave with instant confirmation and transparent pricing." href="/apis/turbo" /> -## Ar.io Gateway APIs +## ar.io Gateway APIs -The Ar.io Gateway serves as the primary interface for accessing Arweave data through the ar.io network. Key endpoints include: +The ar.io Gateway serves as the primary interface for accessing Arweave data through the ar.io network. Key endpoints include: - **Data Access** - Retrieve transaction data and files from Arweave - **ArNS Resolution** - Resolve human-readable names to Arweave transaction IDs diff --git a/content/apis/turbo/meta.json b/content/apis/turbo/meta.json index 47e73a5ff..e8be87602 100644 --- a/content/apis/turbo/meta.json +++ b/content/apis/turbo/meta.json @@ -1,6 +1,6 @@ { "title": "Turbo", - "icon": "/turbo.svg", + "icon": "/ecosystem-logos/logo-turbo.svg", "pages": ["...", "upload-service", "payment-service"], "defaultOpen": false } diff --git a/content/build/access/arns.mdx b/content/build/access/arns.mdx index 25356cddb..e1fb79634 100644 --- a/content/build/access/arns.mdx +++ b/content/build/access/arns.mdx @@ -30,9 +30,9 @@ The easiest way to get an ArNS name is via [arns.ar.io](https://arns.ar.io), whi - **[Wander Chrome Extension](https://chrome.google.com/webstore/detail/wander)** - Browser-based registration - **Wander Mobile App** - Register on iOS and Android -- **Ar.io SDK** - Programmatic registration using the `buyRecord` API +- **ar.io SDK** - Programmatic registration using the `buyRecord` API -### Using the Ar.io SDK +### Using the ar.io SDK For developers, you can register ArNS names programmatically: @@ -52,7 +52,7 @@ console.log('Record purchased:', result); ``` - **Learn More:** For a complete list of Ar.io SDK APIs, see the [ArNS SDK Documentation](/sdks/ar-io-sdk/arweave-name-system-arns). + **Learn More:** For a complete list of ar.io SDK APIs, see the [ArNS SDK Documentation](/sdks/ar-io-sdk/arweave-name-system-arns). ## Fetching Data via ArNS @@ -104,7 +104,7 @@ ArNS provides significant advantages for accessing data on Arweave: } > Learn how to participate in the ar.io ecosystem. diff --git a/content/build/access/find-data.mdx b/content/build/access/find-data.mdx index 61a24bb67..985f3fbc1 100644 --- a/content/build/access/find-data.mdx +++ b/content/build/access/find-data.mdx @@ -28,7 +28,7 @@ This separation allows for powerful data discovery while keeping data retrieval - **Goldsky** - `https://arweave-search.goldsky.com/graphql` - High-performance GraphQL service with full data coverage - **Ar.io Gateways:** ar.io gateways support the `/graphql` endpoint, but they + **ar.io Gateways:** ar.io gateways support the `/graphql` endpoint, but they only return data they've indexed. If you're uploading data and want it unbundled and indexed, you can run a gateway and configure it to unbundle your data, or post data items/bundles via the gateway's APIs (recommended). [Learn diff --git a/content/build/access/wayfinder.mdx b/content/build/access/wayfinder.mdx index a1086b6bc..31c621de7 100644 --- a/content/build/access/wayfinder.mdx +++ b/content/build/access/wayfinder.mdx @@ -1,11 +1,11 @@ --- title: "Wayfinder" -description: "Use Ar.io Wayfinder for decentralized content discovery and optimized data access" +description: "Use ar.io Wayfinder for decentralized content discovery and optimized data access" --- import { Code, Globe, Search, Link } from "lucide-react"; -Wayfinder is a client-side routing and verification protocol that provides **decentralized, cryptographically verified access** to data stored on Arweave via the Ar.io Network. +Wayfinder is a client-side routing and verification protocol that provides **decentralized, cryptographically verified access** to data stored on Arweave via ar.io. ## What is Wayfinder? @@ -103,7 +103,7 @@ function YourComponent() { ## Why Use Wayfinder? -Wayfinder eliminates centralized points of failure by distributing data access across the decentralized Ar.io Network, reducing dependency on arweave.net and providing advanced capabilities for production applications: +Wayfinder eliminates centralized points of failure by distributing data access across ar.io, reducing dependency on arweave.net and providing advanced capabilities for production applications: **Maximum Reliability** diff --git a/content/build/extensions/bundler.mdx b/content/build/extensions/bundler.mdx index bb6bdbec5..962fb5fe2 100644 --- a/content/build/extensions/bundler.mdx +++ b/content/build/extensions/bundler.mdx @@ -1,6 +1,6 @@ --- title: "Bundler" -description: "Learn about the Turbo ANS-104 data item bundler that can be run alongside an Ar.io Gateway to accept and submit data items to Arweave" +description: "Learn about the Turbo ANS-104 data item bundler that can be run alongside an ar.io Gateway to accept and submit data items to Arweave" --- ## Overview @@ -30,7 +30,7 @@ Environmental variables must be provided for the bundler to function and integra BUNDLER_ARWEAVE_WALLET='Stringified JWK wallet. e.g: '{ "n": "...", ... }' BUNDLER_ARWEAVE_ADDRESS='Address for above wallet' -APP_NAME='Ar.io bundler service' +APP_NAME='ar.io bundler service' # Use localstack s3 bucket for shared data source between ar.io gateway and bundler AWS_S3_BUCKET=ar.io diff --git a/content/build/extensions/clickhouse.mdx b/content/build/extensions/clickhouse.mdx index be27cf5f2..c66c028bb 100644 --- a/content/build/extensions/clickhouse.mdx +++ b/content/build/extensions/clickhouse.mdx @@ -19,7 +19,7 @@ Apache Parquet is a columnar storage file format designed for efficient data sto For more information about Parquet, see the [Parquet documentation](https://parquet.apache.org/docs/). -## Current Integration with Ar.io Gateways +## Current Integration with ar.io Gateways In the current ar.io gateway implementation, Parquet and ClickHouse run alongside SQLite rather than replacing it. This parallel architecture allows each database to handle what it does best: @@ -34,7 +34,7 @@ With ClickHouse integration enabled, GraphQL queries are primarily routed to Cli For more information about gateway architecture and data processing, see our [Gateway Architecture](/learn/gateways/architecture) documentation. -## Parquet vs. SQLite in Ar.io Gateways +## Parquet vs. SQLite in ar.io Gateways While SQLite is excellent for transactional workloads and small to medium datasets, it faces challenges with very large datasets: diff --git a/content/build/extensions/compute-unit.mdx b/content/build/extensions/compute-unit.mdx index 01e3ea551..4fada28e6 100644 --- a/content/build/extensions/compute-unit.mdx +++ b/content/build/extensions/compute-unit.mdx @@ -1,6 +1,6 @@ --- title: "AO Compute Unit (CU)" -description: "Steps for deploying an AO Compute Unit (CU) sidecar alongside your Ar.io Gateway." +description: "Steps for deploying an AO Compute Unit (CU) sidecar alongside your ar.io Gateway." --- ## Overview diff --git a/content/build/extensions/grafana.mdx b/content/build/extensions/grafana.mdx index 1ecd811eb..ff777c8f9 100644 --- a/content/build/extensions/grafana.mdx +++ b/content/build/extensions/grafana.mdx @@ -1,6 +1,6 @@ --- title: "Grafana" -description: "Comprehensive guide to deploying and configuring Grafana for Ar.io Gateway monitoring and analytics" +description: "Comprehensive guide to deploying and configuring Grafana for ar.io Gateway monitoring and analytics" --- import { Steps, Step } from "fumadocs-ui/components/steps"; @@ -15,7 +15,7 @@ Ar.io gateways track extensive performance and operational metrics using [Promet The Grafana sidecar is deployed as a separate Docker container that uses the same network as the gateway, making it simple to integrate with your existing setup. -![Grafana Dashboard](/grafana.png) +![Grafana Dashboard](/content/grafana.png) ## Quick Start @@ -353,7 +353,7 @@ docker compose -f docker-compose.grafana.yaml restart - **Grafana Documentation** - [Official Grafana docs](https://grafana.com/docs/) - **Prometheus Metrics** - [Understanding gateway metrics](https://prometheus.io/docs/concepts/metric_types/) -- **Community Support** - Join the [Ar.io Discord](https://discord.com/invite/HGG52EtTc2) for help +- **Community Support** - Join the [ar.io Discord](https://discord.com/invite/HGG52EtTc2) for help ## Useful Docker Commands diff --git a/content/build/guides/depin.mdx b/content/build/guides/depin.mdx index 353401e10..f0ef36821 100644 --- a/content/build/guides/depin.mdx +++ b/content/build/guides/depin.mdx @@ -1,13 +1,13 @@ --- title: "Storing DePIN Data on Arweave Using Turbo" -description: "Complete guide to storing and accessing DePIN network data permanently on Arweave using Turbo and Ar.io Network" +description: "Complete guide to storing and accessing DePIN network data permanently on Arweave using Turbo and ar.io" --- import { Database, Globe, Search, Upload, Tag, Code, Book } from "lucide-react"; DePIN networks require **scalable and cost-effective storage solutions** they can trust. With vast amounts of data generated by decentralized physical infrastructure networks, traditional on-chain storage is prohibitively expensive, yet networks need reliable, long-term access to their device data. -Arweave via Ar.io Network provides **chain-agnostic, permanent and immutable storage** for a one-time fee, ensuring networks can access any device data previously stored and verify it has not been tampered with. +Arweave via ar.io provides **chain-agnostic, permanent and immutable storage** for a one-time fee, ensuring networks can access any device data previously stored and verify it has not been tampered with. ## Getting Started with DePIN Data Storage diff --git a/content/build/guides/hosting-decentralised-apps/deploying-with-arlink.mdx b/content/build/guides/hosting-decentralised-apps/deploying-with-arlink.mdx index 7e8243348..1f187c268 100644 --- a/content/build/guides/hosting-decentralised-apps/deploying-with-arlink.mdx +++ b/content/build/guides/hosting-decentralised-apps/deploying-with-arlink.mdx @@ -8,17 +8,17 @@ import { Card, Cards } from 'fumadocs-ui/components/card'; import { Steps, Step } from 'fumadocs-ui/components/steps'; import { Zap, Github, Globe, Sparkles, FileCode, Rocket, GitBranch } from 'lucide-react'; -![Arlink login page showing GitHub, Wander, and MetaMask authentication options](/arlink-homepage.png) +![Arlink login page showing GitHub, Wander, and MetaMask authentication options](/content/arlink-homepage.png) ## Introduction -In the previous guides in this series, we've used a CLI tool called `permaweb-deploy` to configure and host decentralised apps on Ar.io Network. +In the previous guides in this series, we've used a CLI tool called `permaweb-deploy` to configure and host decentralised apps on ar.io. -In this guide we'll be using [Arlink](https://arlink.ar.io), a visual, web-based platform for hosting decentralised apps on Ar.io Network without needing command-line tools. +In this guide we'll be using [Arlink](https://arlink.ar.io), a visual, web-based platform for hosting decentralised apps on ar.io without needing command-line tools. It offers automated builds, GitHub integration, and seamless ArNS management through an intuitive interface. -Check out the [series introduction](/build/guides/hosting-decentralised-apps) to learn how Ar.io Network enables permanent, decentralised hosting with 100+ independent gateways. +Check out the [series introduction](/build/guides/hosting-decentralised-apps) to learn how ar.io enables permanent, decentralised hosting with 100+ independent gateways. ## What You'll Learn @@ -81,7 +81,7 @@ The deployment process consists of four main phases. For detailed step-by-step i Navigate to the [Arlink Dashboard](https://arlink.arweave.net/) and connect your Arweave wallet (Wander). Then authorize GitHub access to enable repository connections. -![Arlink login page showing GitHub, Wander, and MetaMask authentication options](/arlink-login.png) +![Arlink login page showing GitHub, Wander, and MetaMask authentication options](/content/arlink-login.png) Arlink only requests read access to your repositories and webhook permissions for continuous deployment. @@ -96,7 +96,7 @@ Select your GitHub repository and branch. Arlink will automatically detect: - **Build Command** - Usually `npm run build` - **Output Directory** - `dist/`, `build/`, `out/`, etc. -![Arlink repository selection interface showing GitHub repositories with import buttons](/arlink-repo-select.png) +![Arlink repository selection interface showing GitHub repositories with import buttons](/content/arlink-repo-select.png) Review the auto-detected settings and adjust if needed. Ensure your output directory matches your framework: @@ -107,7 +107,7 @@ Review the auto-detected settings and adjust if needed. Ensure your output direc | Astro | `dist/` | Static by default | | Create React App | `build/` | Default configuration | -![Arlink deploy configuration options](/arlink-deploy-config.png) +![Arlink deploy configuration options](/content/arlink-deploy-config.png) ### 3. Choose Domain @@ -129,7 +129,7 @@ Select how your application will be accessible: Click **Deploy** to start the build process. Arlink will clone your repository, install dependencies, build your application, and upload to Arweave. -![Arlink deployment build monitoring](/arlink-deployment-process.png) +![Arlink deployment build monitoring](/content/arlink-deployment-process.png) **Build Timeline:** - Small apps (~1MB): 2-3 minutes @@ -179,7 +179,7 @@ Undernames use underscore separators: `staging_myapp` not `staging.myapp`. See [ The Arlink dashboard lets you view deployment history, manage undernames, and rollback to previous deployments by updating which transaction ID your ArNS name points to. -![Arlink deployment build monitoring](/arlink-history.png) +![Arlink deployment build monitoring](/content/arlink-history.png) ## Limitations & Considerations diff --git a/content/build/guides/hosting-decentralised-apps/deploying-with-permaweb-deploy.mdx b/content/build/guides/hosting-decentralised-apps/deploying-with-permaweb-deploy.mdx index 697d8b272..ccebca784 100644 --- a/content/build/guides/hosting-decentralised-apps/deploying-with-permaweb-deploy.mdx +++ b/content/build/guides/hosting-decentralised-apps/deploying-with-permaweb-deploy.mdx @@ -16,7 +16,7 @@ import { BookOpen, } from 'lucide-react'; -Permaweb-deploy is the recommended CLI tool for hosting decentralised applications on Ar.io Network. +Permaweb-deploy is the recommended CLI tool for hosting decentralised applications on ar.io. It streamlines the entire deployment process by uploading your build folder to Arweave, creating Arweave manifests, and automatically updating your ArNS records in a single command. diff --git a/content/build/guides/hosting-decentralised-apps/hosting-with-ardrive.mdx b/content/build/guides/hosting-decentralised-apps/hosting-with-ardrive.mdx index 6593e9d11..c09c6c00c 100644 --- a/content/build/guides/hosting-decentralised-apps/hosting-with-ardrive.mdx +++ b/content/build/guides/hosting-decentralised-apps/hosting-with-ardrive.mdx @@ -13,7 +13,7 @@ import { Upload, Globe, Code } from 'lucide-react'; Create **permanent dApps** using the ArDrive web interface. This guide shows you how to deploy your dApp or website to the permaweb using ArDrive's user-friendly interface. -Check out the [series introduction](/build/guides/hosting-decentralised-apps) to learn how Ar.io Network enables permanent, decentralised hosting with 100+ independent gateways. +Check out the [series introduction](/build/guides/hosting-decentralised-apps) to learn how ar.io enables permanent, decentralised hosting with 100+ independent gateways. ## What You'll Learn diff --git a/content/build/guides/hosting-decentralised-apps/index.mdx b/content/build/guides/hosting-decentralised-apps/index.mdx index 1708552c1..59348983c 100644 --- a/content/build/guides/hosting-decentralised-apps/index.mdx +++ b/content/build/guides/hosting-decentralised-apps/index.mdx @@ -1,5 +1,5 @@ --- -title: "Hosting Decentralised Apps on Ar.io Network" +title: "Hosting Decentralised Apps on ar.io" description: "Learn how to deploy permanent, censorship-resistant websites and applications to Arweave with ArNS domain integration" --- @@ -15,7 +15,7 @@ import { The goal of decentralised apps (dapps) has always been full stack. However, until now, that has not been possible due to single points of failure for hosting frontends. -Ar.io Network solves this via: +Ar.io solves this via: - **Permanent Storage**: Pay once and store your site forever on [Arweave](https://arweave.org/). - **Smart Domains**: a sovereign owned domain-space via [Arweave Name System (ArNS)](/learn/arns). @@ -32,7 +32,7 @@ You can repeat this by loading the `docs` subdomain for any of the ~600 active g ## What You'll Learn -In this guide series, you'll learn how to deploy and manage permanent applications on Ar.io Network. +In this guide series, you'll learn how to deploy and manage permanent applications on ar.io. We'll cover the following: diff --git a/content/build/guides/hosting-decentralised-apps/using-undernames-for-versioning.mdx b/content/build/guides/hosting-decentralised-apps/using-undernames-for-versioning.mdx index 5c1592d21..ec114dec4 100644 --- a/content/build/guides/hosting-decentralised-apps/using-undernames-for-versioning.mdx +++ b/content/build/guides/hosting-decentralised-apps/using-undernames-for-versioning.mdx @@ -401,5 +401,5 @@ You now know how to manage multiple environments using ArNS undernames: - **GitHub Actions automation** for branch-based deployments - **Instant rollbacks** through the ArNS app interface -In our next guides we're explore other tools you can use to host websites on Ar.io Network without needing to configure `permaweb-deploy`. +In our next guides we're explore other tools you can use to host websites on ar.io without needing to configure `permaweb-deploy`. diff --git a/content/build/guides/storing-nfts.mdx b/content/build/guides/storing-nfts.mdx index cd702f626..e249119f6 100644 --- a/content/build/guides/storing-nfts.mdx +++ b/content/build/guides/storing-nfts.mdx @@ -1,5 +1,5 @@ --- -title: "Storing NFTs on Ar.io Network" +title: "Storing NFTs on ar.io" description: "Learn how to store NFT assets permanently on Arweave with guaranteed access forever using Turbo and ar:// protocol" --- @@ -8,7 +8,7 @@ import { Steps, Step } from "fumadocs-ui/components/steps"; import { Card, Cards } from "fumadocs-ui/components/card"; import { Shield, DollarSign, Globe, Image } from "lucide-react"; -Storing NFT assets on Ar.io Network ensures they're permanent, immutable and accessible, forever. +Storing NFT assets on ar.io ensures they're permanent, immutable and accessible, forever. We achieve this by providing: @@ -17,18 +17,18 @@ We achieve this by providing: - **Decentralised Gateways**: a network of 100s of incentivized gateways provide access. - **Routing Protocol**: ar://wayfinder ensures an active gateway is selected for all requests. -Once your NFT assets are stored on Ar.io Network, no one can delete, edit or "rug" them. +Once your NFT assets are stored on ar.io, no one can delete, edit or "rug" them. That means Creators can be confident their art will live on forever and Collectors can be confident their investment won't disappear. -## How to Store NFT assets on Ar.io Network +## How to Store NFT assets on ar.io -First, it's important to understand Ar.io Network doesn't let you mint NFTs. What it does provide is permanent storage and access for the media files (images, video, animations) and metadata (artist, attributes, traits) JSON which is used in NFTs. +First, it's important to understand ar.io doesn't let you mint NFTs. What it does provide is permanent storage and access for the media files (images, video, animations) and metadata (artist, attributes, traits) JSON which is used in NFTs. -To mint an NFT you'd typically store your assets and metadata via Ar.io Network and then use another service to "mint" the NFTs onchain. +To mint an NFT you'd typically store your assets and metadata via ar.io and then use another service to "mint" the NFTs onchain. -This guide is targeted at developers. If you're not a developer we strongly recommend uploading to Ar.io Network via [ArDrive](https://ardrive.io), check out this amazing video guide from [Hashlips](https://x.com/Hashlipsnft): +This guide is targeted at developers. If you're not a developer we strongly recommend uploading to ar.io via [ArDrive](https://ardrive.io), check out this amazing video guide from [Hashlips](https://x.com/Hashlipsnft):