From 95eb6e188c10d4e1fa090a89f454504b5ebed177 Mon Sep 17 00:00:00 2001 From: Gregory Marcilhacy Date: Sun, 21 Jan 2024 09:51:50 -0800 Subject: [PATCH] Add Hashlip alternative --- .../00-sugar/03-guides/01-preparing-assets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03-developer-tools/00-sugar/03-guides/01-preparing-assets.md b/docs/03-developer-tools/00-sugar/03-guides/01-preparing-assets.md index ae6999680..02806e922 100644 --- a/docs/03-developer-tools/00-sugar/03-guides/01-preparing-assets.md +++ b/docs/03-developer-tools/00-sugar/03-guides/01-preparing-assets.md @@ -7,7 +7,7 @@ Your assets consist of a collection of images (e.g., `.png`) and metadata (`.jso i.e., each image has a corresponding metadata file. There are a multitude of unique ways to generate images and metadata, and in most scenarios, you will automate this -process. A good example of an image generation tool is [HashLips](https://github.com/HashLips/hashlips_art_engine). In +process. A good example of an image generation tool is [HashLips](https://github.com/HashLips/hashlips_art_engine) or [NFT Art Generator](https://nft-generator.art) (paid). In this guide we will cover the creation of a simple collection to illustrate the metadata requirements and Candy Machine distribution. You should familiarize yourself with the [Token Metadata Standard](/programs/token-metadata/token-standard).