* docs(nft): add NFT Collection message flows and images

* * feat(NFTCollection.mdx): add NFT Collection message flows section * fix(NFTCollection.mdx): fix typo in NFT Collection overview section * feat(NFTCollection.mdx): add NFT Collection images for parent-child pattern and message flows
Ton-Dynasty · Oct 19, 2023 · 6a60c7b · 6a60c7b
1 parent f521953
commit 6a60c7b
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 0 deletions.
diff --git a/docs/nft/NFTCollection.mdx b/docs/nft/NFTCollection.mdx
@@ -6,10 +6,23 @@ sidebar_position: 1
 
 This NFT Collection smart contract provides a framework for NFT collections that comply with the [TEP-0062 standard](https://github.com/ton-blockchain/TEPs/blob/master/text/0062-nft-standard.md).
 
+NFT in TON follows parent-child pattern. That is, each NFT item is a child contract of the NFT collection contract.
+![NFT Collection](./images/nft_parent_child.png)
+
 ## Overview
 
 In the TEP-0062 standard, each NFT collection is associated with an NFT Collection smart contract, which stores basic information about the collection, including the next item index, collection content, and owner address.
 
+## Message Flows
+
+![NFT Collection Message Flows](./images/nft_message_flow.png)
+
+Specifically, the `Transfer` flow is as follows:
+
+1. When NFT Item received a `Transfer` message, it will set the current owner to the `newOwner` in payload of `Transfer` message. 
+2. Then, an OwnershipAssigned event will send to NewOwner as a notification.
+3. Last, if there are remaining funds, the NFT Item will send `Excesses` message to previous owner, attaching with the remaining funds.
+
 ### CollectionData Structure
 
 ```typescript

diff --git a/docs/nft/images/nft_message_flow.png b/docs/nft/images/nft_message_flow.png
diff --git a/docs/nft/images/nft_parent_child.png b/docs/nft/images/nft_parent_child.png