Tracking issue for new and updated documentation

[jhaaaa]

This tracking issue lists all the documentation pages that need to be updated or reviewed for XMTP V3.

Items with 🏗️ may require code updates before docs can be updated.

Get started

• /get-started/developer-quickstart. Content needs to be updated for V3. Link to legacy doc
• /get-started/examples. 🏗️ Example apps and tools need to be updated to use V3. Link to legacy doc
• /get-started/references. Review Browser, Swift, and Node with Eng to verify SDK references are building as intended.
• /get-started/references. Add RN and Kotlin SDK references.

---

Inboxes

• /dms/troubleshoot. Review with Dev Rel and GTM - start fresh for V3.

History

• /protocol/v3/message-history. 🏗️ Write content once the feature is ready.

Smart contract wallets

• /protocol/v3/smart-wallet. 🏗️ Write content once the feature is ready.

Groups

• /groups/group-permissions. Browser code samples. Link to legacy doc
• /groups/group-metadata. Browser code samples Link to legacy doc
• /groups/group-permissions. Link to legacy doc
• /groups/group-metadata. Link to legacy doc

Open Frames

• /open-frames/open-frames. 🏗️ Open Frames need to be updated to use V3. Link to legacy doc
• /open-frames/subscription-open-frames. 🏗️ Example subscription Open Frame needs to be updated to use V3. Link to legacy doc
• /open-frames/transactional-open-frames. 🏗️ Example transactional Open Frame needs to be updated to use V3. Link to legacy doc

To follow the progress of Open Frames engineering work, see xmtp/libxmtp#1225.

Content types

• /content-types/transaction-refs - Provide code samples for RN, Kotlin, and Swift SDKs
• /content-types - Provide code samples for Node SDKs
• /content-types - Provide code samples for Browser SDKs
• /content-types/content-types. Review with Eng to ensure code samples are up to date. Link to legacy doc
• /content-types/remote-attachment. Review with Eng to ensure code samples are up to date. Link to legacy doc
• /content-types/reaction. Review with Eng to ensure code samples are up to date. Link to legacy doc
• /content-types/reply. Review with Eng to ensure code samples are up to date. Link to legacy doc
• /content-types/read-receipt. Review with Eng to ensure code samples are up to date. Link to legacy doc
• /content-types/transaction-ref. Review with Eng to ensure code samples are up to date. Link to legacy doc
• /content-types/custom. Review with Eng to ensure code samples are up to date. Link to legacy doc

---

Subscribe/Broadcast/Consent proofs

• /consent/subscribe. 🏗️ Update Broadcast, Subscribe, and Consent Proof functionality to use V3. Link to legacy doc
• /consent/broadcast. 🏗️ Update Broadcast, Subscribe, and Consent Proof functionality to use V3. Link to legacy doc
• /consent/consent-quickstarts. 🏗️ Update Broadcast, Subscribe, and Consent Proof functionality to use V3. Link to legacy doc
• /consent/build-engagement. 🏗️ Update Broadcast, Subscribe, and Consent Proof functionality to use V3. Link to legacy doc

---

Chat widgets

• /chat-widget/chat-widget. 🏗️ Update chat widgets to use V3. Link to legacy doc

---

Protocol concepts

• /protocol/signatures. Content needs updating to remove V2 signature types for V3. Link to legacy doc
• /protocol/xmtp-versions. Content needs to be updated to act as a deprecation schedule doc for V2 and V1.
• /protocol/portable-inbox. Content needs to be updated to reflect installations and history. Link to legacy doc
• /protocol/protocols. Review with Eng to find the best way to convey protocol specs.

---

Performance

• /perf-ux/xmtp-metamask-snap. Review with Eng to ensure useSnaps and SnapKeystore use V3. Link to legacy doc
• /perf-ux/optimistic-sending. Review with Eng to see if this doc is necessary with V3. Link to legacy doc
• /perf-ux/get-featured. Review with Eng and GTM to refresh for V3. Link to legacy doc
• /perf-ux/debug-and-test. Review with Eng to refresh for V3; consider if 🏗️ xmtp-debug repo needs updates. Link to legacy doc