# Art to collect, create and preserve

Immutables.art brings together an artist's program, an edition's identity on Ethereum and a viewer that runs the work. Start with the guide that fits what you want to do.

- [Collectors](/docs/collectors): Understand editions, find a work and make it part of your collection.
- [Artists & Coders](/docs/artists): Build, test and publish generative artwork with the project wizard.
- [Galleries & Museums](/docs/galleries-museums): Acquire, exhibit and care for works that run as software.

## Find an answer

- **How do I mint or check an edition?** Read [minting and ownership](/docs/collecting).
- **How do I use the artwork on my phone?** Read [viewing your collection](/docs/viewing).
- **How do I make and test a project?** Start in [Artists & Coders](/docs/artists).
- **How do we display a particular work?** Follow [exhibition setup](/docs/exhibiting).
- **What should an archive contain?** Use [conservation and archives](/docs/preservation).
- **Where do code, images and metadata live?** Read [storage and metadata](/docs/storage).

## Three things to keep distinct

**The code page NFT** identifies an owned page on Immutables Code, currently branded Immutables.co. Code posts belong to that page's history; an individual post is not automatically a separate NFT.

**The art project** references one code-post transaction. It has its own settings, artist address and royalty manager.

**An edition NFT** belongs to the art project. Its mint transaction and edition number are inputs the viewer can use to recreate the artwork.

The [Technical Reference](/docs/technical-reference) connects these concepts. Read [contracts and identity](/docs/contracts) when comparing project numbers, edition numbers, global token IDs or transaction hashes.

## Bring an assistant

The copy button provides instructions suited to the section you are reading. The [LLM index](/llms.txt) organizes the same guides for assistants, and the [complete reference](/llms-full.txt) includes every chapter. Artists also have a detailed [authoring brief](/docs/llm-guide).

## Scope

Contract behavior is checked against the deployed platform sources. Settings such as fees, active projects and royalty rates can change; read the current values before signing. The [current/proposed feature guide](/docs/future) identifies work that is not part of the deployed artist workflow.