> For the complete documentation index, see [llms.txt](https://help.fjordnfts.com/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fjordnfts.com/product-docs/creator-info/how-to-create-a-fjord-drop.md).

# How to Create a Fjord Drop

There are two ways to create a fair launch via Fjord NFTs:

**Option A - No Code Required via Manifold:** Don't know solidity programming? Don't worry! We support Manifold Studio NFT contracts so that you can easily create an NFT drop with zero smart contract coding required. [Click for full details.](https://help.fjordnfts.com/product-docs/creator-info/how-to-create-a-fjord-drop/option-a-no-code-required-via-manifold)

**Option B - Adding a Smart Contract Extension:** Before deploying your NFT ERC-721 contract you must add a custom Fjord NFTs extension to it in order to enable an integration with our Fair Drop. This is a simple process that requires minimal additional developer knowledge. Steps on how to undertake this process will be provided in the documentation below. [Click for full details.](/product-docs/creator-info/how-to-create-a-fjord-drop/option-b-adding-a-smart-contract-extension.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.fjordnfts.com/product-docs/creator-info/how-to-create-a-fjord-drop.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.