Merge pull request #184 from metaplex-foundation/tony/core-candy-machine-titles-fix

Core Candy Machine - Refixed Titles

src/pages/core-candy-machine/create.md

@@ -1,6 +1,6 @@
 ---
 title: Creating a Core Candy Machine 
-metaTitle: Creating a Core Candy Machine
+metaTitle: Creating a Core Candy Machine | Core Candy Machine
 description: Learn how to create your Core Candy Machine and it's various settings in both Javascript and Rust.
 ---
 

src/pages/core-candy-machine/custom-guards/generating-client.md

@@ -1,6 +1,6 @@
 ---
-title: Generating Custom Guard Client for the new Core Candy Machine
-metaTitle: Core Candy Machine - Generating Custom Guard Client for Core Candy Machine.
+title: Generating Custom Guard Client for Core Candy Machine
+metaTitle: Custom Guard Client | Core Candy Machine.
 description: Learn how to generate a Umi compatible client for your custom built guards for the newest Core Candy Machine program.
 ---
 

src/pages/core-candy-machine/fetching-a-candy-machine.md

@@ -1,6 +1,6 @@
 ---
 title: Fetching a Core Candy Machine
-metaTitle: Core Candy Machine - Fetching a Core Candy Machine
+metaTitle: Fetching a Core Candy Machine | Core Candy Machine
 description: How to fetch the data of a Core Core Candy Machine from the Solana blockchain.
 ---
 

src/pages/core-candy-machine/getting-started/index.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine -  Getting Started
-metaTitle: Core Candy Machine - Getting Started
+title: Getting Started
+metaTitle: Getting Started | Core Candy Machine
 description: The starting point in getting to know the Core Candy Machine program and packages.
 ---
 

src/pages/core-candy-machine/getting-started/js.md

@@ -1,6 +1,6 @@
 ---
-title: Getting Started using JavaScript with Core Candy Machine
-metaTitle: Core Candy Machine - Getting Started - JavaScript
+title: Getting Started using JavaScript
+metaTitle: Javascript SDK | Core Candy Machine
 description: Get started using Javascript with the latest mpl-core-candy-machine packages for Core Candy Machine.
 ---
 

src/pages/core-candy-machine/getting-started/rust.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Getting Started with Rust SDK
-metaTitle: Core Candy Machine - Getting Started - Rust SDK
+title: Getting Started with Rust SDK
+metaTitle: Rust SDK | Core Candy Machine
 description: Get Started with the mpl-core-candy-machine Rust SDK for the Core Candy Machine program from Metaplex.
 ---
 

src/pages/core-candy-machine/guard-groups.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Guard Groups
-metaTitle: Core Candy Machine - Guard Groups
+title: Guard Groups
+metaTitle: Guard Groups | Core Candy Machine
 description: Explains how to configure and use multiple groups of guards with a Core Candy Machine.
 ---
 

src/pages/core-candy-machine/guard-route.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Special Guard Instructions
-metaTitle: Core Candy Machine - Special Guard Instructions
+title: Special Guard Instructions
+metaTitle: Special Guard Instructions | Core Candy Machine
 description: Explains how to execute guard-specific instructions for the Core Candy Machine.
 ---
 

src/pages/core-candy-machine/guards.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Candy Guards
-metaTitle: Core Candy Machine - Candy Guards
+title: Candy Guards
+metaTitle: Candy Guards | Core Candy Machine
 description: Learn about the different types of guards available for the Core Candy Machine and their functionality.
 ---
 

src/pages/core-candy-machine/guards/address-gate.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Address Gate Guard"
-metaTitle: "Core Candy Machine - Guards - Address Gate"
+title: Address Gate Guard
+metaTitle: Address Gate Guard | Core Candy Machine
 description: "The Core Candy Machine 'Address Gate' restricts the minting to a single address provided."
 ---
 

src/pages/core-candy-machine/guards/allocation.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Allocation Guard"
-metaTitle: "Core Candy Machine - Guards - Mint Allocation"
+title: Allocation Guard
+metaTitle: Mint Allocation Guard | Core Candy Machine
 description: "Learn about the Core Candy Machine 'Allocation' guard in which you can specify the maximum number of mints in a guard group for a Core Candy Machine."
 ---
 

src/pages/core-candy-machine/guards/allow-list.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Allowlist Guard"
-metaTitle: "Core Candy Machine - Allowlist Guard"
+title: Allowlist Guard
+metaTitle: Allowlist Guard | Core Candy Machine
 description: "The Core Candy Machine 'Allowlist' guard guard allows you to set a list of predefined wallets that are allowed to mint from your Core Candy Machine"
 ---
 

src/pages/core-candy-machine/guards/asset-burn-multi.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Asset Burn Multi Guard"
-metaTitle: "Core Candy Machine - Guards - Asset Burn Multi"
+title: Asset Burn Multi Guard
+metaTitle: Asset Burn Multi Guard | Core Candy Machine
 description: "The Core Candy Machine 'Asset Burn Multi' guard restricts minting to holders of a predefined Collection and burns the holder's Asset(s) upon purchase."
 ---
 

src/pages/core-candy-machine/guards/asset-burn.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Asset Burn Guard"
-metaTitle: "Core Candy Machine - Guards - Asset Burn"
+title: Asset Burn Guard
+metaTitle: Asset Burn Guard | Core Candy Machine
 description: "The Core Candy Machine 'Asset Burn' guard restricts minting to holders of a predefined Collection and burns the holder's Asset during purchase from the Core Candy Machine."
 ---
 

src/pages/core-candy-machine/guards/asset-mint-limit.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Asset Mint Limit Guard"
-metaTitle: "Core Candy Machine - Guards - Asset Mint Limit"
+title: Asset Mint Limit Guard
+metaTitle: Asset Mint Limit Guard | Core Candy Machine
 description: "The Core Candy Machine 'Asset Mint Limit' guard restricts minting to holders of a specified collection and limits the amount of mints that can be purchased for a provided Asset on the Core Candy Machine."
 ---
 

src/pages/core-candy-machine/guards/asset-payment-multi.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Asset Payment Multi Guard"
-metaTitle: "Core Candy Machine - Guards - Asset Payment Multi"
+title: "Asset Payment Multi Guard"
+metaTitle: "Asset Payment Multi Guard | Core Candy Machine"
 description: "The Core Candy Machine 'Asset Payment Multi' guard that charges other Core Asset(s) from a specific collection as payment for the mint from the Core Candy Machine."
 ---
 

src/pages/core-candy-machine/guards/asset-payment.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Asset Payment Guard"
-metaTitle: "Core Candy Machine - Guards - Asset Payment"
+title: "Asset Payment Guard"
+metaTitle: "Asset Payment Guard | Core Candy Machine"
 description: "The Core Candy Machine 'Asset Payment' guard requires another Core Asset from a specific collection as payment for the mint from the Core Candy Machine"
 ---
 

src/pages/core-candy-machine/guards/bot-tax.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Bot Tax Guard"
-metaTitle: "Candy Machine - Guards - Bot Tax"
+title: "Bot Tax Guard"
+metaTitle: "Bot Tax Guard | Core Candy Machine"
 description: "The Core Candy Machine 'Bot Tax' guard allows you to set up a configurable tax to charge invalid transactions from users. This can deter spam and bots."
 ---
 

src/pages/core-candy-machine/guards/edition.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Edition Guard"
-metaTitle: "Candy Machine - Guards - Edition"
+title: "Edition Guard"
+metaTitle: "Edition Guard | Core Candy Machine"
 description: "The Core Candy Machine 'Edition' guard allows the minting of Editions from a Core Candy Machine."
 ---
 

src/pages/core-candy-machine/guards/end-date.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - End Date Guard"
-metaTitle: "Core Candy Machine - Guards- End Date"
+title: "End Date Guard"
+metaTitle: "End Date Guard | Core Candy Machine"
 description: "The Core Candy Machine 'End Date' guard determines a date to end the minting process for the Core Candy Machine and its phases."
 ---
 

src/pages/core-candy-machine/guards/freeze-sol-payment.md

@@ -1,6 +1,6 @@
 ---
-title: 'Core Candy Machine - Freeze Sol Payment Guard'
-metaTitle: 'Core Candy Machine - Guards - Freeze Sol Payment'
+title: 'Freeze Sol Payment Guard'
+metaTitle: Freeze Sol Payment Guard | Core Candy Machine
 description: "The Core Candy Machine 'Freeze Sol Payment' allows you to set the price of minting in SOL while also freezing the minted Core NFT Assets upon purchase for a set duration of time."
 ---
 

src/pages/core-candy-machine/guards/freeze-token-payment.md

@@ -1,6 +1,6 @@
 ---
-title: 'Core Candy Machine - Freeze Token Payment Guard'
-metaTitle: 'Core Candy Machine - Guards - Freeze Token Payment'
+title: 'Freeze Token Payment Guard'
+metaTitle: 'Freeze Token Payment Guard | Core Candy Machine'
 description: "The Core Candy Machine 'Freeze Token Payment' guard allows you to set an SPL Token as the currency of minting and its value while also freezing the minted Core NFT Assets upon purchase for a set duration of time."
 ---
 

src/pages/core-candy-machine/guards/gatekeeper.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Gatekeeper Guard"
-metaTitle: "Core Candy Machine - Guards- Gatekeeper"
+title: "Gatekeeper Guard"
+metaTitle: "Gatekeeper Guard | Core Candy Machine"
 description: "The Core Candy Machine `Gatekeeper` guard checks whether the minting wallet has a valid Gateway Token from a specified Gatekeeper Network."
 ---
 

src/pages/core-candy-machine/guards/mint-limit.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Mint Limit Guard"
-metaTitle: "Core Candy Machine - Mint Limit Guard"
+title: Mint Limit Guard"
+metaTitle: "Mint Limit Guard | Core Candy Machine"
 description: "The Core Candy Machine 'Mint Limit' guard allows specifying a limit on the number of Assets each wallet can mint."
 ---
 

src/pages/core-candy-machine/guards/nft-burn.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - NFT Burn Guard"
-metaTitle: "Core Candy Machine - NFT Burn Guard"
+title: "NFT Burn Guard"
+metaTitle: "NFT Burn Guard  | Core Candy Machine"
 description: "The Core Candy Machine 'NFT Burn' guard restricts the mint to holders of a predefined Token Metadata NFT/pNFT Collection and burns the holder's NFT during purchase."
 ---
 

src/pages/core-candy-machine/guards/nft-gate.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - NFT Gate Guard"
-metaTitle: "Core Candy Machine - NFT Gate Guard"
+title: "NFT Gate Guard"
+metaTitle: "NFT Gate Guard Guard | Core Candy Machine"
 description: "The Core Candy Machine 'NFT Gate' guard restricts minting to holders of a specified NFT/pNFT collection."
 ---
 

src/pages/core-candy-machine/guards/nft-mint-limit.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - NFT Mint Limit Guard"
-metaTitle: "Core Candy Machine - NFT Mint Limit Guard"
+title: "NFT Mint Limit Guard"
+metaTitle: "NFT Mint Limit Guard | Core Candy Machine"
 description: "The Core Candy Machine 'NFT Mint Limit' guard restricts minting to holders of a specified NFT/pNFT collection and limits the amount of Assets that can be minted for a provided NFT."
 ---
 

src/pages/core-candy-machine/guards/nft-payment.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - NFT Payment Guard"
-metaTitle: "Core Candy Machine - NFT Payment Guard"
+title: "NFT Payment Guard"
+metaTitle: "NFT Payment Guard | Core Candy Machine"
 description: "The Core Candy Machine 'NFT Payment' guard allows minting by charging the payer an NFT/pNFT from a specified NFT collection. The NFT/pNFT used as payment will be transferred to a predefined destination."
 ---
 

src/pages/core-candy-machine/guards/program-gate.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Program Gate Guard"
-metaTitle: "Core Candy Machine - Program Gate Guard"
+title: "Program Gate Guard"
+metaTitle: "Program  Guard Guard | Core Candy Machine"
 description: "The Core Candy Machine 'Program Gate' guard restricts the programs that can be used during the mint transaction."
 ---
 

src/pages/core-candy-machine/guards/redeemed-amount.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Redeemed Amount Guard"
-metaTitle: "Core Candy Machine - Redeemed Amount Guard"
+title: "Redeemed Amount Guard"
+metaTitle: "Redeemed Amount Guard | Core Candy Machine"
 description: "The Core Candy Machine 'Redeemed Amount' guard forbids minting when the number of minted Assets for the entire Core Candy Machine reaches the configured maximum amount."
 ---
 

src/pages/core-candy-machine/guards/sol-fixed-fee.md

@@ -1,7 +1,7 @@
 ---
-title: "Core Candy Machine - Sol Fixed Fee Guard"
-metaTitle: "Core Candy Machine - Sol Fixed Fee Guard"
-description: "The Core Candy Machine 'Sol Fixed Fee' guard charges the payer an amount in SOL when minting."
+title: Sol Fixed Fee Guard
+metaTitle: Sol Fixed Fee Guard | Core Candy Machine
+description: The Core Candy Machine 'Sol Fixed Fee' guard charges the payer an amount in SOL when minting
 ---
 
 ## Overview

src/pages/core-candy-machine/guards/sol-payment.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Sol Payment Guard"
-metaTitle: "Core Candy Machine - Sol Payment Guard"
+title: "Sol Payment Guard"
+metaTitle: Sol Payment Guard Guard | Core Candy Machine
 description: "The Core Candy Machine 'Sol Payment' guard charges the payer an amount in SOL when minting."
 ---
 

src/pages/core-candy-machine/guards/start-date.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Start Date Guard"
-metaTitle: "Core Candy Machine - Start Date Guard"
+title: "Start Date Guard"
+metaTitle: Start Date Guard | Core Candy Machine
 description: "The Core Candy Machine 'Start Date' guard determines the start date of the mint for the Core Candy Machine or phase."
 ---
 

src/pages/core-candy-machine/guards/third-party-signer.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Third Party Signer Guard"
-metaTitle: "Core Candy Machine - Third Party Signer Guard"
+title: Third Party Signer Guard
+metaTitle: Third Party Signer Guard | Core Candy Machine
 description: "The Core Candy Machine 'Third Party Signer' guard requires a predefined address to sign each mint transaction or the transaction will fail."
 ---
 

src/pages/core-candy-machine/guards/token-burn.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Token Burn Guard"
-metaTitle: "Core Candy Machine - Token Burn Guard"
+title: Token Burn Guard
+metaTitle: Token Burn Guard | Core Candy Machine
 description: "The Core Candy Machine 'Token Burn' guard allows minting by setting the minting currency to an SPL token address and value."
 ---
 

src/pages/core-candy-machine/guards/token-gate.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Token Gate Guard"
-metaTitle: "Core Candy Machine - Token Gate Guard"
+title: Token Gate Guard
+metaTitle: Token Gate Guard | Core Candy Machine
 description: "The Core Candy Machine 'Token Gate' guard restricts minting to holders of a configured SPL Token."
 ---
 

src/pages/core-candy-machine/guards/token-payment.md

@@ -1,6 +1,6 @@
 ---
-title: "Core Candy Machine - Token Payment Guard"
-metaTitle: "Core Candy Machine - Token Payment Guard"
+title: Token Payment Guard
+metaTitle: Token Payment Guard | Core Candy Machine
 description: "The Core Candy Machine 'Token Payment' guard allows minting by charging the payer a set value of an SPL Token."
 ---
 

src/pages/core-candy-machine/guards/token2022-payment.md

@@ -1,6 +1,6 @@
 ---
-title: 'Core Candy Machine - Token2022 Payment Guard'
-metaTitle: 'Core Candy Machine - Token2022 Payment Guard'
+title: Token2022 Payment Guard
+metaTitle: Token2022 Payment Guard | Core Candy Machine
 description: "The Core Candy Machine 'Token2022 Payment' guard allows minting by charging the payer a set value of an SPL Token2022."
 ---
 

src/pages/core-candy-machine/index.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Overview
-metaTitle: Core Candy Machine - Overview
+title: Overview
+metaTitle: Overview | Core Candy Machine
 description: Provides a high-level overview of Core Candy Machines.
 ---
 

src/pages/core-candy-machine/insert-items.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine -  Inserting Items
-metaTitle: Core Candy Machine - Inserting Items
+title: Inserting Items
+metaTitle: Inserting Items | Core Candy Machine
 description: How to load Core NFT Assets into a Core Candy Machine.
 ---
 

src/pages/core-candy-machine/mint.md

@@ -1,7 +1,7 @@
 ---
-title: Core Candy Machine - Minting
-metaTitle: Core Candy Machine - Minting
-description: Jow to mint from a Core Candy Machines allowing users to purchase your Core NFT Assets.
+title: Minting
+metaTitle: Minting | Core Candy Machine
+description: How to mint from a Core Candy Machine allowing users to purchase your Core NFT Assets.
 ---
 
 So far, we’ve learned how to create and maintain Candy Machines. We’ve seen how to configure them and how to set up complex minting workflows using guard and guard groups. It’s about time we talk about the last piece of the puzzle: Minting! {% .lead %}

src/pages/core-candy-machine/overview.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Overview of the Core Candy Machine Program
-metaTitle: Core Candy Machine - Overview of the Core Candy Machine Program
+title: Program Overview
+metaTitle: Program Overview | Core Candy Machine
 description: An overview of the Core Candy Machine program and its feature sets to help you create a minting experience.
 ---
 

src/pages/core-candy-machine/preparing-assets.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Preparing Assets
-metaTitle: Core Candy Machine - Preparing Assets
+title: Preparing Assets
+metaTitle: Preparing Assets | Core Candy Machine
 description: How to prepare your files and assets for uploading into a Core Candy Machine.
 ---
 

src/pages/core-candy-machine/references/index.md

@@ -1,6 +1,6 @@
 ---
 title: API References
-metaTitle: Candy Machine - API References
+metaTitle: API References | Core Candy Machine
 description: References and code snippets for Metaplex's Candy Machine product.
 ---
 

src/pages/core-candy-machine/sugar/bring-your-own-uploader.md

@@ -1,126 +0,0 @@
----
-title: Bring Your Own Uploader
-metaTitle: Candy Machine - Sugar - Bring Your Own Uploader
-description: How to bring your own uploader to Sugar.
----
-
-Sugar has an extensible architecture to easily allow the implementation of new upload methods with minimal effort. The upload logic is decoupled from the `upload` command and new methods can be plug-in into the upload flow by implementing a Rust trait, supporting both *free-form* and parallel upload methods:
-
-- `Uploader`: this trait should be implemented directly by upload methods that require full control on how the upload is performed.
-- `ParallelUploader`: this trait abstracts the threading logic and allows methods to focus on the logic of uploading a single asset (file).
-
-The use of the different traits is illustrated in the upload architecture overview below:
-
-![Uploader architecture](https://raw.githubusercontent.com/metaplex-foundation/docs/main/static/assets/sugar/UploaderOverview.png)
-
-To implement your uploader, the first step is to decide whether you need full control of the upload process or your method support parallel upload. This will inform which trait to implement. Independently of the trait that you implement, assets (files) requiring upload are represented by a `AssetInfo` struct:
-
-```rust
-pub struct AssetInfo {
-    /// Id of the asset in the cache.
-    pub asset_id: String,
-    /// Name (file name) of the asset.
-    pub name: String,
-    /// Content of the asset - either a file path or the string
-    /// representation of its content.
-    pub content: String,
-    /// Type of the asset.
-    pub data_type: DataType,
-    /// MIME content type.
-    pub content_type: String,
-}
-```
-
-An `AssetInfo` can represent a physical file, in which case the `content` will correspond to the name of the file; or an in-memory asset, in which case the `content` will correspond to the content of the asset.
-
-For example, for image files, the `content` contains the path of the file on the file system. In the case of json metadata files, the `content` contains the string representation of the json metadata.
-
-## Traits
-
-> More details of the traits' implementations can be found on Sugar's [source code](https://github.com/metaplex-foundation/sugar/blob/main/src/upload/uploader.rs).
-
-### Uploader
-
-The `Uploader` trait gives you full control on how the assets (files) are uploaded. It defines a single function:
-
-```rust
-async fn upload(
-    &self,
-    sugar_config: &SugarConfig,
-    cache: &mut Cache,
-    data_type: DataType,
-    assets: &mut Vec<AssetInfo>,
-    progress: &ProgressBar,
-    interrupted: Arc<AtomicBool>,
-) -> Result<Vec<UploadError>>;
-```
-
-where:
-
-* `sugar_config` - The current sugar configuration
-* `cache` - Asset cache object (mutable)
-* `data_type` - Type of the asset being uploaded
-* `assets` - Vector of assets to upload (mutable)
-* `progress` - Reference to the progress bar to provide feedback to the console
-* `interrupted` - Reference to the shared interruption handler flag to receive notifications
-
-This function will be called to upload each type of asset separately&mdash;e.g., once for your images, once for your metadata and, if present, once for your animation assets. After uploading an asset, its information needs to be updated in the `cache` object and the cache saved to the file system using the `sync_file` function. Syncing the cache to the file system might be slow for large collections, therefore it should be done as frequent as practical to avoid slowing down the upload process and, at the same time, minimizing the chances of information loss in case the user aborts the upload.
-
-Implementations are expected to use the `interrupted` parameter to control when the user aborts the upload process by pressing `Ctrl+C`&mdash;this is useful for large uploads. Any information saved in the cache will not be re-uploaded. The `upload` command will filter out the assets already uploaded, and they will not be included in the vector of assets. The `progress` is a reference to the progress bar displayed on the console and should be used to provide a visual feedback of the progress of the upload by calling its `progress.inc(1)` function to indicate that `1` asset was uploaded.
-
-When all files are uploaded successfully, the `upload` method will return an empty `Vec`; in case of errors, the `Vec` will contain a list of `UploadError`s that will be displayed to the user.
-
-### ParallelUploader
-
-The `ParallelUpload` provides a thread-enabled implementation of the `Uploader` trait's `upload` function to support concurrent uploads, abstracting the threading logic to focus on the logic of uploading a single asset (file). Therefore, methods that can upload assets in parallel need to implement a simplified `upload_asset` function:
-
-```rust
-fn upload_asset(
-    &self,
-    asset: AssetInfo
-) -> JoinHandle<Result<(String, String)>>;
-```
-
-The `upload_asset` function must return a `JoinHandle` object. In most cases, the function will return the value from `tokio::spawn`. This function should only include the logic to upload the asset&mdash;the interruption control and cache synchronization is done automatically by the `ParallelUpload` trait.
-
-### Prepare
-
-All upload methods need to implement an additional trait `Prepare`. The rationale is to prepare the method for the upload of the specified media/metadata files, e.g.:
-- check if any file exceeds a size limit;
-- check if there is storage space for the upload;
-- check/add funds for the upload.
-
-The trait defines a single function:
-
-```rust
-async fn prepare(
-    &self,
-    sugar_config: &SugarConfig,
-    asset_pairs: &HashMap<isize, AssetPair>,
-    asset_indices: Vec<(DataType, &[isize])>,
-) -> Result<()>;
-```
-where:
-* `sugar_config` - The current sugar configuration
-* `asset_pairs` - Mapping of `index` to an `AssetPair`
-* `asset_indices` - Vector with the information of which asset pair indices will be uploaded, grouped by type.
-
-The `asset_pairs` contain the complete information of the assets, but only the assets specified in the `asset_indices` will be uploaded&mdash;e.g., if index `1` is only present in the `DataType::Image` indices' array, only the image of asset `1` will the uploaded.
-
-## Configuration
-
-After implementing the logic of the upload method, you need to integrate your method in Sugar's configuration file. Firstly, you will need to add a new value to the `UploadMethod` [enum](https://github.com/metaplex-foundation/sugar/blob/main/src/config/data.rs#L220-L231) to identify your upload method. Secondly, you need to modify the `initialize` [factory method](https://github.com/metaplex-foundation/sugar/blob/main/src/upload/uploader.rs#L274-L296) to create the `Uploader` object when it is specified in the configuration file.
-
-In case your upload method requires additional parameters, you will need to modify the `ConfigData` [struct](https://github.com/metaplex-foundation/sugar/blob/main/src/config/data.rs#L30-L86). For example, the `aws` upload method requires the user to specify a bucket name for the upload. In the `ConfigData` struct, you will find an `aws_s3_bucket` field, which corresponds to the `awsS3Bucket` property in the configuration file.
-
-Once you completed the upload method trait implementation and added its details to Sugar's configuration file, it is ready to be used to upload assets.
-
-{% callout %}
-
-Do not forget to submit a PR to Sugar's repository to have your implementation added to Sugar's code base.
-
-{% /callout %}
-
-## Next steps
-
-Sugar currently has six [upload methods](https://github.com/metaplex-foundation/sugar/tree/main/src/upload/methods) available&mdash;check their source code for more details about how the upload of assets works and design ideas to implement your own upload method.

src/pages/core-candy-machine/sugar/cache.md

@@ -1,122 +0,0 @@
----
-title: Cache File
-metaTitle: Candy Machine - Sugar - Cache File
-description: Sugar cache file.
----
-
-Sugar keeps track of the Candy Machine and assets created using a cache file. This allows Sugar to resume the upload of assets without having the re-upload all assets. It also provides information regarding the Candy Machine account, such the collection and Candy Machine creator.
-
-You should not need to manually modify the cache file directly – this file is manipulated by Sugar commands. There are specific circumstances that you might to so, as discussed above.
-
-{% callout %}
-
-Keep a copy of your cache file as it containts all asset information and addresses of the accounts created.
-
-{% /callout %}
-
-## Structure
-
-The cache file is a JSON document with the following structure:
-
-```json
-{
-  "program": {
-    "candyMachine": "<PUBLIC KEY>",
-    "candyGuard": "<PUBLIC KEY>",
-    "candyMachineCreator": "<PUBLIC KEY>",
-    "collectionMint": "<PUBLIC KEY>"
-  },
-  "items": {
-    "-1": {
-      "name": "My Collection",
-      "image_hash": "6500707cb13044b7d133abb5ad68e0af660b154499229af49419c86a251a2b4d",
-      "image_link": "https://arweave.net/KplI7R59EE24-mavSgai7WVJmkfvYQKhtTnqxXPlPdE?ext=png",
-      "metadata_hash": "2009eda578d1196356abcfdfbba252ec3318fc6ffe42cc764a624b0c791d8471",
-      "metadata_link": "https://arweave.net/K75J8IG1HcTYJyr1eC0KksYfpxuFMkPONJMpUNDmCuA",
-      "onChain": true
-    },
-    "0": {
-      "name": "My First NFT #1",
-      "image_hash": "209a200ebea39be9e9e7882da2bc5e652fb690e612abecb094dc13e06db84e54",
-      "image_link": "https://arweave.net/-qSoAFO7GWTm_js1eHDyoljgB3D_vszlXspVXBM7HyA?ext=png",
-      "metadata_hash": "cfc45ba94da81c8d21f763ce8bb6bbb845ad598e23e44d5c8db1590672b7653f",
-      "metadata_link": "https://arweave.net/6DRibEPNjLQKA90v3qa-JsYPPT5a6--VsgKumUnX3_0",
-      "onChain": true
-    },
-    ...
-  }
-}
-```
-
-### `program`
-
-The `"program"` section includes the information about the Candy Machine, Candy Guard accounts as well as the addresses of the Candy Machine creator and collection mint. These details are populated once the Candy Machine is deployed. The Candy Guard address is present only if you have enabled guards on your candy machine.
-
-### `items`
-
-The `"items"` section includes the information about the assets of the Candy Machine. This list is created once Sugar validates your assets folder. At this point, all the `"name"`, `"image_hash"` and `"metadata_hash"` are added to the cache file. Once the assets are uploaded, the information of the `"image_link"` and `"metadata_link"` are updated with their final values. Finally, once the Candy Machine is deployed, the `"onChain"` value is set to `true`.
-
-Sugar `upload` will only upload assets that do not have the correspondent "link" value populated – e.g., running `sugar upload` with a cache file containing the following item:
-
-```json
-"0": {
-      "name": "My First NFT #1",
-      "image_hash": "209a200ebea39be9e9e7882da2bc5e652fb690e612abecb094dc13e06db84e54",
-      "image_link": "https://arweave.net/-qSoAFO7GWTm_js1eHDyoljgB3D_vszlXspVXBM7HyA?ext=png",
-      "metadata_hash": "cfc45ba94da81c8d21f763ce8bb6bbb845ad598e23e44d5c8db1590672b7653f",
-      "metadata_link": "",
-      "onChain": false
-},
-```
-
-only the metadata file will be uploaded, since the image link is alredy present.
-
-Sugar stores the "hash" of both image and metadata files, so when the hash value changes as a result of chaging the corresponding file, running `sugar upload` will upload the new file. At this point, the `"onChain"` value will be set to `false` and the change will only be effective (be onchain) after running `sugar deploy`.
-
-## "Advance" cache management
-
-In most cases, you don't need to modify the cache file manually. But there are cases when you might want to do so.
-
-### Deploying a new Candy Machine with the same items
-
-If you want to deploy your Candy Machine to a new address, reusing the same items from the cache file, you can simply remove the `"candyMachine"` public key value from the cache file:
-
-{% totem %}
-{% totem-accordion title="Example" %}
-
-```json
-{
-  "program": {
-    "candyMachine": "",
-    "candyGuard": "",
-    "candyMachineCreator": "6DwuXCUnGEE2NktwQub22Ejt2EQUexGmGADZURN1RF6J",
-    "collectionMint": "5TM8a74oX6HgyAtVnKaUaGuwu44hxMhWF5QT5i7PkuZY"
-  },
-  "items": {
-    "-1": {
-      "name": "My Collection",
-      "image_hash": "6500707cb13044b7d133abb5ad68e0af660b154499229af49419c86a251a2b4d",
-      "image_link": "https://arweave.net/KplI7R59EE24-mavSgai7WVJmkfvYQKhtTnqxXPlPdE?ext=png",
-      "metadata_hash": "2009eda578d1196356abcfdfbba252ec3318fc6ffe42cc764a624b0c791d8471",
-      "metadata_link": "https://arweave.net/K75J8IG1HcTYJyr1eC0KksYfpxuFMkPONJMpUNDmCuA",
-      "onChain": true
-    },
-    "0": {
-      "name": "My First NFT #1",
-      "image_hash": "209a200ebea39be9e9e7882da2bc5e652fb690e612abecb094dc13e06db84e54",
-      "image_link": "https://arweave.net/-qSoAFO7GWTm_js1eHDyoljgB3D_vszlXspVXBM7HyA?ext=png",
-      "metadata_hash": "cfc45ba94da81c8d21f763ce8bb6bbb845ad598e23e44d5c8db1590672b7653f",
-      "metadata_link": "https://arweave.net/6DRibEPNjLQKA90v3qa-JsYPPT5a6--VsgKumUnX3_0",
-      "onChain": true
-    },
-    ...
-  }
-}
-```
-
-{% /totem-accordion %}
-{% /totem %}
-
-### Using pre-existing links
-
-When you already have links to your assets, the information can be added to the cache file manually to avoid Sugar uploading them again. In this case, you should complete the `"image_link"` and `"metadata_link"` with the corresponding links.

src/pages/core-candy-machine/sugar/commands/airdrop.md

@@ -1,55 +0,0 @@
----
-title: airdrop
-metaTitle: Candy Machine - Sugar - airdrop
-description: Command to airdrop (p)NFTs with sugar.
----
-
-## Useage
-
-The `airdrop` command mints NFTs from a Candy Machine to a list of wallets from the command-line.
-
-It requires a file, by default called `airdrop_list.json` which contains the wallet public keys and the amount of NFTs each wallet should receive. In the following example `address1` would receive 2 NFTs, `address2` would receive 7. The file should have the following format:
-
-```json
-{
-"address1": 2,
-"address2": 7
-}
-```
-
-After completing you will find a `airdrop_results.json` file with the results of your airdrop and possible issues.
-
-{% callout %}
-
-It is not possible to use the airdrop command if there are guards enabled.
-
-{% /callout %}
-
-When using the default `cache.json` and `airdrop_list.json`, you can use the following command to initate the airdrop:
-
-```
-sugar airdrop
-```
-
-Otherwise, specify your airdrop_list file with `--airdrop-list`:
-
-```
-sugar airdrop --airdrop-list <AIRDROP_LIST>
-```
-
-By default sugar will use the default cache file `cache.json`. You can also override the cache file name with `--cache`:
-
-```
-sugar mint --cache <CACHE>
-```
-
-You can also tell sugar to use a specific candy machine with `--candy-machine`: 
-
-```
-sugar mint --candy-machine <CANDY_MACHINE>
-```
-
-## Rerunning the command
-In some cases mints will fail, e.g. because a blockhash was not found or similar RPC / Network related reasons. The results of your airdrop will be saved in `airdrop_results.json`. When rerunning the command the airdrop list and airdrop results will be compared.
-
-Be careful: In some cases you will see that a transaction could not be confirmed before a timeout happened. In those cases you should confirm e.g. on an explorer if the NFT was minted.

src/pages/core-candy-machine/sugar/commands/bundlr.md

@@ -1,21 +0,0 @@
----
-title: bundlr
-metaTitle: Candy Machine - Sugar - bundlr
-description: bundlr command.
----
-
-When you use Bundlr as your upload method, Sugar automatically funds your account on the Bundlr Network to cover the storage costs. Once the upload is completed, there could be leftover funds in the account.
-
-You can verify your balance on the Bundlr Network with the following command:
-
-```
-sugar bundlr balance
-```
-
-This will retrieve the balance for the current keypair. You can specify an alternative keypair using the option `--keypair`. The remaining balance (if there is any) can be withdrawn:
-
-```
-sugar bundlr withdraw
-```
-
-At the end of the withdrawal, the funds available on the Bundlr Network will be transferred to your Solana address.

src/pages/core-candy-machine/sugar/commands/collection.md

@@ -1,15 +0,0 @@
----
-title: collection
-metaTitle: Candy Machine - Sugar - collection
-description: collection command.
----
-
-You can use the `collection`` commands to manually set the collection NFT of your Candy Machine. You can only modify the collection before any NFTs have been minted from it.
-
-You can set a pre-existing collection NFT by running:
-
-```
-sugar collection set <COLLECTION MINT>
-```
-
-where `<COLLETION MINT>` is the public key of the collection NFT mint account.

src/pages/core-candy-machine/sugar/commands/config.md

@@ -1,37 +0,0 @@
----
-title: config
-metaTitle: Candy Machine - Sugar - config
-description: config command.
----
-
-The `config` command allows you manage your Candy Machine configuration. By default, Sugar looks for a `config.json` file in the current directory to load the Candy Machine configuration – the configuration file name can be specified with a `-c` or `--config` option on every command that requires it.
-
-You can either create this file manually, following these [instructions](/core-candy-machine/sugar/configuration), or use the config create command:
-
-```
-sugar config create
-```
-
-Executing the command starts an interactive process consisting in a sequence of prompts to gather information about all configuration options. At the end of it, a configuration file is saved (default to config.json) or its content is displayed on screen. To specify a custom file name, use the option `-c`:
-
-```
-sugar config create -c my-config.json
-```
-
-Once your Candy Machine is deployed, any changes to the configuration file must be set to the Candy Machine account using the `update` sub-command:
-
-```
-sugar config update
-```
-
-You can update the Candu Machine authority (the public key that controls the Candy Machine) using the `-n` option:
-
-```
-sugar config update -n <NEW PUBLIC KEY>
-```
-
-You can also change the token standard of the assets minted through the Candy Machine by using the `set` sub-command. This command supports changing the type of asset to either `NFT`s or `pNFT`s using the `-t` option. It also allows you to specify a rule set for minted pNFTs.
-
-```
-sugar config set -t "pnft" --rule-set <PUBLIC KEY>
-```

src/pages/core-candy-machine/sugar/commands/deploy.md

@@ -1,13 +0,0 @@
----
-title: deploy
-metaTitle: Candy Machine - Sugar - deploy
-description: deploy command.
----
-
-Once all assets are uploaded and the cache file is successfully created, you are ready to deploy your items to Solana:
-
-```
-sugar deploy
-```
-
-The deploy command will write the information of your cache file to the Candy Machine account onchain. This effectively creates the Candy Machine and displays its onchain ID (Public Key) — use this ID to query its information onchain using an [explorer](https://explorer.solana.com). You can specify the path for the configuration file with the `-c` option (default `config.json`) and the name of the cache file with the option `--cache` (default `cache.json``) in case you are not using the default names.

src/pages/core-candy-machine/sugar/commands/freeze.md

@@ -1,39 +0,0 @@
----
-title: freeze
-metaTitle: Candy Machine - Sugar - freeze
-description: freeze command.
----
-
-When the Candy Machine has the freeze guard enabled, the `freeze` command can be used to manege its different stages.
-
-After enabling the freeze guard on the default guards or an individual group, it needs to be initialized before minting can start. To initialize the freeza guard, use the `initialize` sub-command:
-
-```
-sugar freeze initialize --period <SECONDS>
-```
-
-where `--period` determines the interval in seconds that minted assets will be frozen. After this period, holders can thaw their assets.
-
-{% callout %}
-
-You can only initialize the freeze once. After initialization, it is not possible to update the period.
-
-{% /callout %}
-
-To thaw an asset, you can use the `thaw` sub-command:
-
-```
-sugar freeze thaw <NFT MINT>
-```
-
-You can also thaw all NFTs from the same Candy Machine using the `--all` option:
-
-```
-sugar freeze thaw --all
-```
-
-Once all NFTs are thaw, the funds can be unlocked:
-
-```
-sugar freeze unlock-funds
-```

src/pages/core-candy-machine/sugar/commands/guard.md

@@ -1,41 +0,0 @@
----
-title: guard
-metaTitle: Candy Machine - Sugar - guard
-description: guard command.
----
-
-The `guard` command is used to manage the [guards](/core-candy-machine/guards) configuration of the Candy Machine.
-
-Once you completed the guards configuration in your Sugar config file, you can add a Candy Guard using:
-
-```
-sugar guard add
-```
-
-At this point, the `mint` command will stop working since the `mint authority` is now the Candy Guard.
-
-To update the Candy Guard configuration, you first need to make the required modification in the Sugar config file and the run the command:
-
-```
-sugar guard update
-```
-
-To print the onchain configuration of the Candy Machine guards, use the command:
-
-```
-sugar guard show
-```
-
-To remove the guards from a Candy Machine, use the command:
-
-```
-sugar guard remove
-```
-
-After removing the guards, you can use the `mint` command to mint from the Candy Machine.
-
-The `remove` command does not close the Candy Guard account. To close the account and retrieve the rent fee, use the command:
-
-```
-sugar guard withdraw
-```

src/pages/core-candy-machine/sugar/commands/hash.md

@@ -1,33 +0,0 @@
----
-title: hash
-metaTitle: Candy Machine - Sugar - hash
-description: hash command.
----
-
-When using *hiddenSettings*, you should specify a hash value in your config file so that the assets can be verified when the mint is complete and a reveal is performed. The hash value is automatically updated by the deploy command when *hiddenSettings* are enabled, but there could be scenarios where you are modifying the cache file manually.
-
-The `hash` command computes a hash of the cache file and updates the hash value in the config file.
-
-```
-sugar hash
-```
-
-It also allows comparing a published hash value with the value from a cache file with the `--compare` option. The cache file can be specified manually with `--cache`, or it will default to the `cache.json` file in the current directory.
-
-Running the `--compare` against the default `cache.json`:
-
-```
-sugar hash --compare 44oZ3goi9ivakeUnbjWbWJpvdgcWCrsi
-```
-
-Running the `--compare` against a specific cache file:
-
-```
-sugar hash --compare 44oZ3goi9ivakeUnbjWbWJpvdgcWCrsi --cache my_custom_cache.json
-```
-
-{% callout %}
-
-After updating the hash value, you will need to update your Candy Machine configuration so that the new value is onchain using the `update` command.
-
-{% /callout %}

src/pages/core-candy-machine/sugar/commands/launch.md

@@ -1,15 +0,0 @@
----
-title: launch
-metaTitle: Candy Machine - Sugar - launch
-description: launch command.
----
-
-The `launch` command is a convenience command that runs five other commands consecutively:
-
-- `create-config`
-- `validate`
-- `upload`
-- `deploy`
-- `verify`
-
-These five commands allow you to start from a project folder with an assets subfolder in it and go through the entire process of setting up and creating a Candy Machine, so it's meant as a quickstart command if you don't want to run each step individually.

src/pages/core-candy-machine/sugar/commands/mint.md

@@ -1,31 +0,0 @@
----
-title: mint
-metaTitle: Candy Machine - Sugar - mint
-description: mint command.
----
-
-The `mint`` command mints NFTs from a Candy Machine from the command-line.
-
-When using the default `cache.json`, you can use:
-
-```
-sugar mint
-```
-
-Otherwise, specify your cache file with the option `--cache`:
-
-```
-sugar mint --cache <CACHE>
-```
-
-You can also specify the number of NFTs to mint using the option `-n` (e.g., 10)`:
-
-```
-sugar mint -n 10
-```
-
-{% callout %}
-
-It is not possible to use the mint command if there are guards enabled.
-
-{% /callout %}

src/pages/core-candy-machine/sugar/commands/reveal.md

@@ -1,13 +0,0 @@
----
-title: reveal
-metaTitle: Candy Machine - Sugar - reveal
-description: reveal command.
----
-
-When using *hiddenSettings* to do a mint and reveal, the `reveal` command can be used to update all minted NFTs with the values from the cache file:
-
-```
-sugar reveal
-```
-
-It works by first retrieving all NFTs minted from the Candy Machine and then match them up to the values in the cache file by NFT number and then update the NFT data. The command checks if an NFTs URI already matches that in the cache file, and if it does, it skips updating, so the command can be rerun to only update newly minted NFTs or to retry ones that failed to update the first run.

src/pages/core-candy-machine/sugar/commands/show.md

@@ -1,13 +0,0 @@
----
-title: show
-metaTitle: Candy Machine - Sugar - show
-description: show command.
----
-
-The `show`` command displays the onchain config of an existing Candy Machine:
-
-```
-sugar show <CANDY MACHINE>
-```
-
-where the `<CANDY MACHINE>` is the Candy Machine ID (Pulic Key) — the ID given by the `deploy` command.

src/pages/core-candy-machine/sugar/commands/sign.md

@@ -1,28 +0,0 @@
----
-title: sign
-metaTitle: Candy Machine - Sugar - sign
-description: sign command.
----
-
-The `sign` command allows signing all NFTs with a creator's keypair, to verify that creator in the creators array in the NFT metadata. Each creator can only sign for themself and only one creator can sign at a time with this command. The creator's keypair can be passed in with the `--keypair` option, otherwise it defaults to using default keypair specified in your Solana CLI config.
-
-Running the command with the default keypair:
-
-```
-sugar sign
-```
-
-And running with a specific keypair:
-
-```
-sugar sign -k creator-keypair.json
-```
-
-Developers can provide a custom RPC URL with the command:
-```
-sugar sign -r <RPC_URL>
-```
-Note using `sugar sign` relies on an inefficient `getProgramAccounts` call on the Metaplex Token Metadata program (i.e., `metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s`). The recommended solution is to sign NFTs individually using the command:
-```
-sugar sign -m <MINT_ADDRESS>
-```

src/pages/core-candy-machine/sugar/commands/update.md

@@ -1,29 +0,0 @@
----
-title: update
-metaTitle: Candy Machine - Sugar - update
-description: update command.
----
-
-The `update` command is used to modify the current configuration of a Candy Machine. Most configuration settings can be updated by this command, except:
-
-- The number of items in the Candy Machine can only be updated when `hiddenSettings` are being used;
-- Switching to use `hiddenSettings` is only possible if the number of items is equal to 0. After the switch, you will be able to update the number of items.
-
-
-To update the configuration, modify your config.json (or equivalent) file and execute:
-
-```
-sugar update
-```
-
-You can also specify custom config and cache files with the `--config` and `--cache` options:
-
-```
-sugar update -c <CONFIG> --cache <CACHE>
-```
-
-{% callout %}
-
-You need to be careful when updating a live Candy Machine, since setting a wrong value will immediately affect its functionality.
-
-{% /callout %}

src/pages/core-candy-machine/sugar/commands/upload.md

@@ -1,25 +0,0 @@
----
-title: upload
-metaTitle: Candy Machine - Sugar - upload
-description: upload command.
----
-
-The `upload`` command uploads assets to the specified storage and creates the cache file for the Candy Machine.
-
-You upload all assets using the default asset folder location (e.g., `assets` folder on the current directory) with the following command:
-
-```
-sugar upload
-```
-
-Alternatively, you can specify a different folder:
-
-```
-sugar upload <ASSETS DIR>
-```
-
-{% callout %}
-
-The `upload` command can be resumed (re-run) at any point in case the upload is not completed successfully — only files that have not yet been uploaded are processed. It also automatically detects when the content of media/metadata files changes and re-uploads them, updating the cache file accordingly. In other words, if you need to change a file, you only need to copy the new (modified) file to your assets folder and re-run the upload command. There is no need to manually edit the cache file.
-
-{% /callout %}

src/pages/core-candy-machine/sugar/commands/validate.md

@@ -1,23 +0,0 @@
----
-title: validate
-metaTitle: Candy Machine - Sugar - validate
-description: validate command.
----
-
-The `validate` command is used to check that all files in the assets folder are in the correct format:
-
-```
-sugar validate
-```
-
-If your assets are in a folder other than the default `assets`, you can specify the folder name:
-
-```
-sugar validate <ASSETS FOLDER>
-```
-
-{% callout %}
-
-It is important to validate your assets before the upload to avoid having to repeat the upload process.
-
-{% /callout %}

src/pages/core-candy-machine/sugar/commands/verify.md

@@ -1,19 +0,0 @@
----
-title: verify
-metaTitle: Candy Machine - Sugar - verify
-description: verify command.
----
-
-The `verify` command checks that all items in your cache file have been successfully written onchain:
-
-```
-sugar verify
-```
-
-To specify a different cache file other than the default `cache.json`, use the `--cache` option:
-
-```
-sugar verify --cache <CACHE>
-```
-
-If you deploy has been successfully, the verification return no errors.

src/pages/core-candy-machine/sugar/commands/withdraw.md

@@ -1,31 +0,0 @@
----
-title: withdraw
-metaTitle: Candy Machine - Sugar - withdraw
-description: withdraw command.
----
-
-When the mint from a Candy Machine is complete, it is possible to recover the funds used to pay rent for the data stored onchain. You can initiate the withdrawal by running:
-
-```
-sugar withdraw --candy-machine <CANDY MACHINE ID>
-```
-
-where the `<CANDY MACHINE ID>` is the Candy Machine ID (Public Key) — the ID given by the `deploy` command. 
-
-It is also possible to withdraw funds from all Candy Machines associated with the current keypair:
-
-```
-sugar withdraw
-```
-
-Alternatively, you can list all Candy Machines and their associated funds from the current keypair:
-
-```
-sugar withdraw --list
-```
-
-{% callout %}
-
-You should not withdraw the rent of a live Candy Machine, as the Candy Machine will stop working when you drain its account.
-
-{% /callout %}

src/pages/core-candy-machine/sugar/configuration.md

@@ -1,219 +0,0 @@
----
-title: Configuration File
-metaTitle: Candy Machine - Sugar - Configuration File
-description: A detailed overview of Sugar configuration file.
----
-
-Sugar uses a JSON configuration file to upload assets and configure a Candy Machine – in most cases, the file will be named `config.json`. The configuration includes the settings that are used to initialize and update the Candy Machine, as well as upload the assets to be minted. It will also include the configuration of guards that will provide access control to minting.
-
-A basic configuration file is shown below:
-
-```json
-{
-  "tokenStandard": "pnft",
-  "number": 10,
-  "symbol": "TEST",
-  "sellerFeeBasisPoints": 500,
-  "isMutable": true,
-  "isSequential": false,
-  "ruleSet": "eBJLFYPxJmMGKuFwpDWkzxZeUrad92kZRC5BJLpzyT9",
-  "creators": [
-    {
-      "address": "PanbgtcTiZ2PveV96t2FHSffiLHXXjMuhvoabUUKKm8",
-      "share": 50
-    },
-    {
-      "address": "PanbgtcTiZ2PveV96t2FHSffiLHXXjMuhvoabUUKKm8",
-      "share": 50
-    }
-  ],
-  "hiddenSettings": null,
-  "uploadMethod": "bundlr",
-  "awsConfig": null,
-  "nftStorageAuthToken": null,
-  "shdwStorageAccount": null,
-  "pinataConfig": null,
-  "sdriveApiKey": null,
-  "guards": {
-    "default": {
-      "botTax": {
-        "value": 0.01,
-        "lastInstruction": true
-      }
-    },
-    "groups": [
-      {
-        "label": "OGs",
-        "guards": {
-          "startDate": {
-            "date": "2022-10-20 12:00:00 +0000"
-          },
-          "tokenGate": {
-            "amount": 1,
-            "mint": "7nE1GmnMmDKiycFkpHF7mKtxt356FQzVonZqBWsTWZNf"
-          },
-          "solPayment": {
-            "value": 1,
-            "destination": "PanbgtcTiZ2PveV96t2FHSffiLHXXjMuhvoabUUKKm8"
-          }
-        }
-      },
-      {
-        "label": "Public",
-        "guards": {
-          "startDate": {
-            "date": "2022-10-20 18:00:00 +0000"
-          },
-          "solPayment": {
-            "value": 2,
-            "destination": "PanbgtcTiZ2PveV96t2FHSffiLHXXjMuhvoabUUKKm8"
-          }
-        }
-      }
-    ]
-  }
-}
-```
-
-The configuration file can be viewed as having three main parts: Candy Machine settings (`"tokenStandard"` to `"hiddenSettings"`), upload settings (`"uploadMethod"` to `"sdriveApiKey"`) and guard settings (`"guards"`).
-
-## Candy Machine settings
-
-Candy Machine settings determine the type of the asset, number of assets available and their metadata information.
-
-| Setting | Options | Value/Type | Description               |
-| ------- | ------- | --------------- | ------------------------- |
-| tokenStandard |   |                 |                           |
-|         |         | "nft"           | Non-Fungible asset (`NFT`)        |
-|         |         | "pnft"           | Programmable Non-Fungible asset (`pNFT`) |
-| number  |         | Integer         | Number of available items |
-| symbol  |         | String          | String representing the symbol of the NFT |
-| sellerFeeBasisPoint  |         | Integer          | The royalties shared by the creators in basis points (i.e., 550 means 5.5%)  |
-| isMutable |       | Boolean         | A boolean indicating if the NFTs Metadata Account can be updated |
-| isSequential |    | Boolean         | A boolean indicating whether a sequential index generation should be used during mint or not |
-| ruleSet  |        | Public Key | *(optional)* The rule set used by minted `pNFT`s |
-
-The `creators` setting allows you to specify up to 4 addresses and their percentage share. 
-
-| Setting | Options | Value/Type | Description               |
-| ------- | ------- | --------------- | ------------------------- |
-| creators |        | Up to 4 creators | List of creators and their percentage share of the royalties |
-|          | address | Public Key | A creator public key |
-|          | share | Integer | A value between `0` and `100` |
-
-{% callout %}
-
-While the metadata onchain stores up to 5 creators, the Candy Machine is set as one of the creators. As a result, there is a limit of 4 creators at most.
-
-The sum of the share values must add up to 100, otherwise an error will be generated.
-
-{% /callout %}
-
-The Candy Machine can be configured to not have the final metadata when an NFT is minted. This is useful when you are planning a revel step once mint is completed. In this case, you can specify the "placeholder" metadata values for the *hidden* NFT:
-
-| Setting | Options | Value/Type | Description               |
-| ------- | ------- | --------------- | ------------------------- |
-| hiddenSettings | | | |
-| | name | String | Name of the mint (can use `$ID$` or `$ID+1$` mint index replacement variables) |
-| | uri | String | URI of the mint (can use `$ID$` or `$ID+1$` mint index replacement variables) |
-| | hash | String | A 32 character hash (in most cases this is the hash of the cache file with the mapping between mint number and metadata so that the order can be verified when the mint is complete)
-
-## Upload settings
-
-Sugar supports a variety of storage providers – the one to be used is define by the `uploadMethod` setting. Depending of the provider, there would be additional configuration needed.
-
-The table below provides an overview of the settings available:
-
-| Setting | Options | Accepted Values | Description               |
-| ------- | ------- | --------------- | ------------------------- |
-| uploadMethod |   |  | Configure the storage to upload images and metadata |  
-|  |   | "bundlr" |  Uploads to Arweave using [Bundlr](https://bundlr.network) and payments are made in SOL (works on both mainnet and devnet; files are only stored for 7 days on devnet)
-|  |   | "aws" | Uploads to Amazon Web Services (AWS) |
-|  |   | "nftStorage" | Uploads to [NFT.Storage](https://nft.storage) (works on all networks; no payment required) |
-|  |   | "shdw" | Uploads to the GenesysGo [Shadow Drive](https://docs.shadow.cloud) (works on mainnet only)
-|  |   | "pinata" | Uploads to [Pinata](https://www.pinata.cloud) (works on all networks; free and tiered subscriptions) |
-|  |   | "sdrive" | Uploads to Shador Drive using [SDrive Cloud Storage](https://sdrive.app) |
-|awsConfig | | | *(required when "aws" is used)* |
-| | bucket | String | AWS bucket name
-| | profile | String | AWS profile to use from the credentials file name |
-| | directory | String | The directory within the bucket to upload the items to. An empty string means uploading files to the bucket root directory. |
-| nftStorageAuthToken | | String | NFT.Storage API Key *(required when "nftStorage" is used)* |
-| pinataConfig | | | *(required when "pinata" is used)* |
-| | JWT | String | JWT authentication token |
-| | apiGateway | String | URL to connect to Pinata API |
-| | apiContent | String | URL to use as the base for creating the asset links |
-| | parallelLimit | Integer | Number of concurrent uploads; use this setting to avoid rate limits |
-| shadowStorageAccount | | String | Shadow Drive storage pubkey *(required when "shdw" is used)* |
-| sdriveApiKey | | String | SDrive API key *(required when "sdrive" is used)* |
-
-Specific upload method settings:
-
-{% totem %}
-{% totem-accordion title="Bundlr" %}
-
-The `"bundlr"` upload method does not require extra configuration. Any fee associated with the upload will be payed in `SOL` using the configured keypair.
-
-{% /totem-accordion %}
-{% totem-accordion title="AWS" %}
-
-The `"aws"` method uploads files to Amazon S3 storage. This requires additional configuration, you need to specify the `bucket`, `profile`, `directory` and `domain` values in the configuration file under `"awsConfig"` and set up the credentials in your system. In most cases, this will involve creating a file `~/.aws/credentials` with the following properties:
-
-```
-[default]
-aws_access_key_id=<ACCESS KEY ID>
-aws_secret_access_key=<SECRET ACCESS KEY>
-region=<REGION>
-```
-
-It is also important to set up the ACL permission of the bucket correctly to enable `"public-read"`` and apply Cross-Origin Resource Sharing (CORS) rules to enable content access requested from a different origin (necessary to enable wallets and blockchain explorers load the metadata/media files). More information about these configurations can be found at:
-
-* [Bucket policy examples](https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html)
-* [CORS configuration](https://aws.amazon.com/premiumsupport/knowledge-center/s3-configure-cors/)
-
-The `profile` value allows you to specify which profile to read from your credentials file. The `directory` value is the name of the directory in the bucket where the files will be uploaded, allowing you to have multiple candy machine or collections in a single bucket separated by different directories. Leaving this as an empty string will upload the files to the root of the bucket. The (optional) `domain` allows you to specify a custom domain to serve the data from AWS — e.g., using the domain as `https://mydomain.com` will create links to files in the format `https://mydomain.com/0.json`. If you do not specify a domain, the default AWS S3 domain will be used (`https://<BUCKET_NAME>.s3.amazonaws.com`).
-
-{% /totem-accordion %}
-{% totem-accordion title="NFT.Storage" %}
-
-NFT.Storage is a popular free service that uploads data on the public IPFS network. You will need to register an account to obtain an API key (token), which need to be specified by `"nftStorageAuthToken"` in the configuration file.
-
-{% /totem-accordion %}
-{% totem-accordion title="Pinata" %}
-
-The `"pinata"` method uploads files to Pinata storage. You need to specify the `jwt`, `apiGateway`, `contentGateway` and `parallelLimit` values in the configuration file under `"pinataConfig"`:
-
-* `jwt``: JWT authentication token
-* `apiGateway`: URL to connect to Pinata API (use `https://api.pinata.cloud` for the public API endpoint)
-* `contentGateway`: URL to use as the base for creating the asset links (use `https://gateway.pinata.cloud` for the public gateway)
-* `parallelLimit`: (optional) number of concurrent upload, adjust this value to avoid rate limits
-
-{% callout %}
-
-The public gateways are not intended to be used in production — they are good to be used for testing as they are heavily rate limited and not designed for speed.
-
-{% /callout %}
-
-{% /totem-accordion %}
-{% totem-accordion title="Shadow Drive" %}
-
-Shadow Drive is a decentralized storage network built specifically for the Solana blockchain. In order to upload data to the Shadow Drive you will need to first create a storage account. This can be done using the [Shadow Drive CLI](https://docs.shadow.cloud/build). After creating a storage account, specify its pubkey address in the configuration file using the property `"shdwStorageAccount"`.
-
-{% callout %}
-
-The Shadow Drive upload method is only available on `mainnet-beta`.
-
-{% /callout %}
-
-{% /totem-accordion %}
-{% totem-accordion title="SDrive" %}
-
-SDrive is a storage app built on top of GenesysGo Shadow Drive. You will need to register an account to obtain an API key (token), which need to be specified by `"sdriveApiKey"` in the configuration file.
-
-{% /totem-accordion %}
-{% /totem %}
-
-## Guard settings
-
-The `guards` settings allows you to specify which guards will be enabled on the Candy Machine.
-
-Candy Machine support a number of guards that provide access control to minting. [Guards](#/core-candy-machine/guards) can be configured into a "default" [guard group](#/core-candy-machine/guard-groups) or appear in multiple guard groups.

src/pages/core-candy-machine/sugar/getting-started.md

@@ -1,93 +0,0 @@
----
-title: Getting Started
-metaTitle: Candy Machine - Sugar - Getting Started
-description: Getting started with Sugar.
----
-
-To get started, first check that you have Sugar installed on your system:
-
-```bash
-sugar --version
-```
-
-The command above should print the Sugar version – e.g., `sugar-cli 2.5.0`.
-
-By default, Sugar uses the keypair and RPC settings from `solana-cli`. You can check your current settings by running:
-
-```bash
-solana config get
-```
-
-And you can set different settings by running:
-
-```bash
-solana config set --url <rpc url> --keypair <path to keypair file>
-```
-
-{% callout %}
-
-Sugar does not require `solana-cli` to be installed on the system. Every command in Sugar accept the flags `-k` (keypair) and `-r` (RPC) to configure the values to use.
-
-{% /callout %}
-
-## Preparing Your Files
-
-Create a folder for your project and within it, create a folder named `assets` to store your json metadata and image file pairs with the naming convention `0.json`, `0.png`, `1.json`, `1.png`, and so on. The metadata extension is `.json` and the image files can be `.png`, `.gif`, `.jpg` and `.jpeg`. Additionally, you will need `collection.json` and `collection.png` files containing the information for your collection NFT.
-
-Your project directory will then look like:
-{% diagram %}
-{% node %}
-{% node #my-project label="my-project/" theme="blue" /%}
-{% /node %}
-
-{% node parent="my-project" y="50" x="100" %}
-{% node #assets label="assets/" theme="indigo" /%}
-{% /node %}
-
-{% node #0-json parent="assets" y="50" x="100" label="0.json" theme="mint" /%}
-{% node #0-png parent="assets" y="95" x="100" label="0.png" theme="mint" /%}
-{% node #1-json parent="assets" y="140" x="100" label="1.json" theme="orange" /%}
-{% node #1-png parent="assets" y="185" x="100" label="1.png" theme="orange" /%}
-{% node #2-json parent="assets" y="230" x="100" label="2.json" theme="mint" /%}
-{% node #2-png parent="assets" y="275" x="100" label="2.png" theme="mint" /%}
-{% node #more parent="assets" y="320" x="100" label=". . ." theme="orange" /%}
-{% node #collection-json parent="assets" y="365" x="100" label="collection.json" theme="purple" /%}
-{% node #collection-png parent="assets" y="410" x="100" label="collection.png" theme="purple" /%}
-
-{% edge from="my-project" to="assets" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="0-json" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="0-png" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="1-json" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="1-png" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="2-json" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="2-png" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="more" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="collection-json" fromPosition="bottom" toPosition="left" /%}
-{% edge from="assets" to="collection-png" fromPosition="bottom" toPosition="left" /%}
-{% /diagram %}
-
-## Running Sugar
-
-Within your project directory, use the `launch` command to start an interactive process of creating your config file and deploying a Candy Machine to Solana:
-
-```bash
-sugar launch
-```
-
-At the end of the execution of the launch command, a Candy Machine will be deployed onchain. You can use the `mint` command to mint an NFT:
-
-```bash
-sugar mint
-```
-
-When all NFTs have been minted, you can close your Candy Machine and reclaim the account rent:
-
-```bash
-sugar withdraw
-```
-
-{% callout %}
-
-The `withdraw` command will close the Candy Machine even if it is not empty, so use it with caution.
-
-{% /callout %}

src/pages/core-candy-machine/sugar/index.md

@@ -1,98 +0,0 @@
----
-title: Overview
-metaTitle: Candy Machine - Sugar - Overview
-description: A detailed overview of Sugar, a CLI tool for managing Candy Machines.
----
-
-Sugar is a command-line tool to interact with Candy Machines. It allows you to manage the whole lifecycle of a Candy Machine and has the following advantages:
-
-- single configuration file with all Candy Machine settings;
-- better performance for upload of media/metadata files and deploy of a Candy Machine — these operations take advantage of multithreaded systems to significantly speed up the computational time needed;
-- robust error handling and validation of inputs with informative error messages;
-- state is maintain even if a command is stopped – e.g., if your upload fails, you can re-run the upload and only the failed ones are retried.
-
-Setting up Sugar is as simple as opening your favourite terminal application and downloading a binary file. 
-
-{% callout %}
-
-View OtterSec's audit of Sugar commissioned by Ape16Z [here](https://docsend.com/view/is7963h8tbbvp2g9).
-
-{% /callout %}
-
-Sugar contains a collection of commands for creating and managing Candy Machines. The complete list of commands can be viewed by running on your command line:
-
-```bash
-sugar
-```
-
-This will display a list of commands and their short description:
-```
-sugar-cli 2.5.0
-Command line tool for creating and managing Metaplex Candy Machines.
-
-USAGE:
-    sugar [OPTIONS] <SUBCOMMAND>
-
-OPTIONS:
-    -h, --help                     Print help information
-    -l, --log-level <LOG_LEVEL>    Log level: trace, debug, info, warn, error, off
-    -V, --version                  Print version information
-
-SUBCOMMANDS:
-    airdrop       Airdrop NFTs from candy machine
-    bundlr        Interact with the bundlr network
-    collection    Manage the collection on the candy machine
-    config        Manage candy machine configuration
-    deploy        Deploy cache items into candy machine config onchain
-    freeze        Manage freeze guard actions
-    guard         Manage guards on the candy machine
-    hash          Generate hash of cache file for hidden settings
-    help          Print this message or the help of the given subcommand(s)
-    launch        Create a candy machine deployment from assets
-    mint          Mint one NFT from candy machine
-    reveal        Reveal the NFTs from a hidden settings candy machine
-    show          Show the onchain config of an existing candy machine
-    sign          Sign one or all NFTs from candy machine
-    upload        Upload assets to storage and creates the cache config
-    validate      Validate JSON metadata files
-    verify        Verify uploaded data
-    withdraw      Withdraw funds a from candy machine account closing it
-```
-
-To get more information about a particular command (e.g., `deploy``), use the help command:
-
-```
-sugar help deploy
-```
-
-This will display a list of options together with a short description:
-
-```
-Deploy cache items into candy machine config onchain
-
-USAGE:
-    sugar deploy [OPTIONS]
-
-OPTIONS:
-    -c, --config <CONFIG>
-            Path to the config file, defaults to "config.json" [default: config.json]
-
-        --cache <CACHE>
-            Path to the cache file, defaults to "cache.json" [default: cache.json]
-
-        --collection-mint <COLLECTION_MINT>
-            The optional collection address where the candymachine will mint the tokens to
-
-    -h, --help
-            Print help information
-
-    -k, --keypair <KEYPAIR>
-            Path to the keypair file, uses Sol config or defaults to "~/.config/solana/id.json"
-
-    -l, --log-level <LOG_LEVEL>
-            Log level: trace, debug, info, warn, error, off
-
-    -r, --rpc-url <RPC_URL>
-            RPC Url
-```
-

src/pages/core-candy-machine/sugar/installation.md

@@ -1,139 +0,0 @@
----
-title: Installation
-metaTitle: Candy Machine - Sugar - Installation
-description: Sugar installation guide.
----
-
-The quickest and easiest way to install Sugar is to download the pre-built binary by running an installation script, available for macOS, Linux and WSL (Windows Subsystem for Linux). For Windows system, see the 📌 below.
-
-Run the following in your terminal:
-```bash
-bash <(curl -sSf https://sugar.metaplex.com/install.sh)
-```
-
-{% callout %}
-
-You will be asked which version you want to use. V1.x is for Candy Machine v2, V2.x is for Candy Machine v3. **We recommend to use the latest version**.
-
-The script will install the binary to your machine and add it to your `PATH`. The modifications to your `PATH` variable may not take effect until the terminal is restarted. Follow the instructions of the installation script to see whether the terminal needs to be restarted or not.
-
-{% /callout %}
-
-{% totem %}
-{% totem-accordion title="📌 Instructions for Windows systems" %}
-
-If you are using Windows, follow the steps below:
-
-1. Download the Winstaller executable from [here](https://github.com/metaplex-foundation/winstaller/releases/latest/download/winstaller.exe).
-
-2. Try to run the binary by double-clicking on it. If you get a pop-up message warning about an untrusted binary try clicking `More Info` and then `Run Anyway`. If you do not have this option, follow steps 3 - 6. 
-
-3. Right-click on the executable file and go to `Properties`.
-
-   ![Properties.PNG](https://raw.githubusercontent.com/metaplex-foundation/docs/main/static/assets/sugar/Properties.png)
-
-4. If you trust the Metaplex developer team, check the `Unblock` button as show in the image below. This will allow you to run this binary on your computer since Microsoft does not trust it automatically.
-
-   ![Unblock.PNG](https://raw.githubusercontent.com/metaplex-foundation/docs/main/static/assets/sugar/Unblock.png)
-
-5. Click `Apply` and `Ok`.
-
-6. Double-click the executable file, and it will open a terminal and begin to install Sugar.
-
-7. If everything completed successfully you will get a message saying `Sugar successfully installed!`
-
-8. Try running `sugar` in your terminal and see if it prints a list of commands you can use. If so you're good to go!
-
-9. Report any errors to the `#sugar` channel on the [Metaplex Discord](https://discord.gg/metaplex).
-   
-{% callout %}
-
-This installer binary downloads the latest Sugar binary version, unzips it and copies it to a folder in your `PATH` environment. If you have Rust, the binary will be copied to `~/.cargo/bin`, otherwise it creates a `SugarCLI` folder in your `%LOCALAPPDATA%` directory. Once the binary is at that location, Windows will find it automatically, and you will be able to run the sugar binary from any directory in your file system as a normal command-line application.
-
-{% /callout %}
-
-{% /totem-accordion %}
-{% /totem %}
-
-## Binaries
-
-Binaries for the supported OS can be found at:
-
-- [Sugar Releases](https://github.com/metaplex-foundation/sugar/releases)
-
-## Other Installation Methods
-
-{% callout %}
-
-When installing from crates.io or from source on Ubuntu or WSL (Windows Subsystem for Linux) you may need to install some additional dependencies:
-```bash
-sudo apt install libudev-dev pkg-config unzip
-``` 
-
-{% /callout %}
-
-### Crates.io
-
-In order to install sugar from Crates.io, you will need to have [Rust](https://www.rust-lang.org/tools/install) installed in your system. It is recommended to install Rust using `rustup`:
-
-```bash
-curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
-```
-
-After the installation completes, running:
-
-```bash
-rustc --version
-```
-
-should print the version of the Rust compiler. If the command fails, check if the `~/.cargo/bin` directory is in your `PATH` environment variable.
-
-The next step is to install Sugar from Crates.io:
-
-```bash
-cargo install sugar-cli
-```
-This will download the Sugar code from Crates.io and automatically install it for you.
-
-
-### Build From Source
-
-In order to build Sugar from the source code, you will need to have [Rust](https://www.rust-lang.org/tools/install) installed in your system. It is recommended to install Rust using `rustup`:
-
-```bash
-curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
-```
-
-After the installation completes, running:
-
-```bash
-rustc --version
-```
-
-should print the version of the Rust compiler. If the command fails, check if the `~/.cargo/bin` directory is in your `PATH` environment variable.
-
-The next step is to clone Sugar repository:
-
-```bash
-git clone https://github.com/metaplex-foundation/sugar.git
-```
-
-This will create a directory `sugar` with the latest code from the repository. Switch to the newly created directory:
-
-```bash
-cd sugar
-```
-
-Then, you can build and install the binary to `~/.cargo/bin`:
-
-```bash
-cargo install --path ./
-```
-
-As long as `./cargo/bin` is in your `PATH` environment variable, you will be able to execute `sugar` from any directory in your file system.
-
-{% callout %}
-
-You need to execute `cargo install` from Sugar source code root directory &mdash; the directory where the `Cargo.toml` is located.
-
-{% /callout %}

src/pages/core-candy-machine/update.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Updating a Core Candy Machine
-metaTitle: Core Candy Machine - Updating a Core Candy Machine
+title: Updating The Core Candy Machine
+metaTitle: Update a Core Candy Machine | Core Candy Machine
 description: Learn how to update your Core Candy Machine and it's various settings.
 ---
 

src/pages/core-candy-machine/withdrawing-a-candy-machine.md

@@ -1,6 +1,6 @@
 ---
-title: Core Candy Machine - Withdrawing a Core Candy Machine
-metaTitle: Core Candy Machine - Withdrawing a Core Candy Machine
+title: Withdrawing a Core Candy Machine
+metaTitle: Withdrawing a Core Candy Machine | Core Candy Machine
 description: How to withdraw a Core Candy Machine and claim back rent from it.
 ---