> For the complete documentation index, see [llms.txt](https://docs.unisat.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unisat.io/misc/knowledge-base/assets-and-collections/how-to-submit-collection-in-github.md).

# How to Submit Collection in GitHub?

This document provides a detailed guide for project teams on how to submit an application to **list new collections** on the UniSat Marketplace on Fractal.

1. Prepare the contents of the two files, `meta.json` and `inscriptions.json`, for the collection.
2. Sign in to GitHub and open <https://github.com/unisat-wallet/fractal-ordinals-collections> (templates for `meta.json` and `inscriptions.json` are available on this page).
3. Click "Fork" on the page.

<figure><img src="/files/wctIB5IrDcTZkEsgZB4C" alt=""><figcaption></figcaption></figure>

4. It will automatically load the info for "Owner" and "Repository name" on the next page. Then click "Create fork".

<figure><img src="/files/SSVYHZNCbbQ33kX4P7Cg" alt=""><figcaption></figcaption></figure>

5. Wait a few seconds for the fork to be created. Once done, click "collections".&#x20;

<figure><img src="/files/Bp2tPOSIHGiVNI7PBmLk" alt=""><figcaption></figcaption></figure>

6. Click "Add file" -> "Create new file".&#x20;

<figure><img src="/files/Y562hwxclCdIdZle2WoH" alt=""><figcaption></figcaption></figure>

7. In the textbox below, create your collection folder. **NOTE:** The folder name must end with a `/`, for example, `test1/`. The folder name is the slug in the conllections meta.json.

<figure><img src="/files/DAcrrzqA7izUviVNYToM" alt=""><figcaption></figcaption></figure>

8. Create the file under the collection folder, enter `meta.json` in the textbox after the folder name as shown below, then copy/paste the related content of `meta.json` into the edit box. Finally, click "Commit changes...".

<figure><img src="/files/hnNrTWPStsGUqE0SYmym" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/MUZ8HiMCkGJXMClXu5IV" alt="" width="302"><figcaption></figcaption></figure>

9. You can check the left column to confirm that the `meta.json` file was created successfully.

<figure><img src="/files/iPttDjMVjnFmuXKw9Cau" alt=""><figcaption></figcaption></figure>

10. Use the same method to create the second file, `inscriptions.json`.

<figure><img src="/files/6GCDkmsBfO06KKysqnst" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/OZYSMwDhgoPN3RxXaikq" alt=""><figcaption></figcaption></figure>

11. Once both files are added, click the "Pull requests" tab -> "New pull request".

<figure><img src="/files/sdSjgK8QnLagu3kmLFBV" alt=""><figcaption></figcaption></figure>

12. If the page shows a green "Able to merge" message, click "Create pull request".

<figure><img src="/files/LsuQhCIl3n5hoCYmTiuC" alt=""><figcaption></figcaption></figure>

13. Add a title and description (optional), then click "Create pull request".

<figure><img src="/files/3rEx1HAP9PzePy15rf2d" alt=""><figcaption></figcaption></figure>

13. All done! You can find your request listed under "Pull requests".

<figure><img src="/files/ug9Fl1Wqkz4o2reSMYJd" alt=""><figcaption></figcaption></figure>

**Please keep the following in mind when submitting your request**:

* Be patient while we process your request.
* Pay attention to the comments in your request. If your submission doesn't meet the requirements, we will specify the reason, and requests with invalid JSON files will be closed.
* Do not repeatedly submit requests.
* Submit a complete collection in one request. Do not spread files across multiple requests.
* Do not submit multiple collections in one request. If one collection doesn't meet the criteria, it could affect the approval of others in the same request.