Skip to content

docs: comprehensive overhaul and alignment of Talisman wallet setup guide - #966

Merged
jim-counter merged 7 commits into
autonomys:mainfrom
EmmanuelMarv:patch-3
Jul 8, 2026
Merged

jim-counter merged 7 commits into
autonomys:mainfrom
EmmanuelMarv:patch-3

Conversation

@EmmanuelMarv

Copy link
Copy Markdown
Contributor

Description

The existing talisman.md setup documentation contained legacy steps and terminology that no longer align with the current version of the Talisman extension application (v3.7.1). This PR completely restructures the user flow to prevent friction for ecosystem users and network ambassadors.

Key Changes

  • Onboarding Alignment: Updated initial setup steps to correctly reflect privacy checks, master password flows, and introductory buttons.
  • Account Creation Fixes: Clarified the selection of a "Substrate" account type over legacy terms and integrated the newly required seed backup verification checkbox.
  • Network Navigation: Outlined exact interactions with the "Select network" modal to cleanly isolate Autonomys addresses (native sue string format).
  • Import Paths Disambiguation: Separated the import instructions into two distinct, easy-to-follow routes: Path A (Recovery Phrase via Substrate menu) and Path B (JSON upload via browser filesystem targeting Polkadot.js).

Verification

All text entries, headers, and explicit UI strings were manually audited and verified line-by-line against the live client layouts.

- Rewrote installation and onboarding workflow steps to mirror the current Talisman browser extension UI (v3.7.1).
- Updated creating an account steps to use the proper "New Substrate Account" terminology.
- Consolidated multi-step recovery warning instructions into single accurate screen reference.
- Explicitly documented the network search selection pathway for finding native 'sue' public addresses.
- Restructured advanced wallet recovery options to explicitly show separate JSON file uploads and Substrate recovery phrase paths.
@netlify

netlify Bot commented Jul 3, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for subspace-docs-staging ready!

Name Link
🔨 Latest commit ce069c4
🔍 Latest deploy log https://app.netlify.com/projects/subspace-docs-staging/deploys/6a4d6768cdbeb60007683898
😎 Deploy Preview https://deploy-preview-966--subspace-docs-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@EmilFattakhov
EmilFattakhov self-requested a review July 3, 2026 22:02

@jim-counter jim-counter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some changes please @EmmanuelMarv.

Comment thread docs/ai3_token/wallets/talisman.md Outdated
Comment thread docs/ai3_token/wallets/talisman.md Outdated
Comment thread docs/ai3_token/wallets/talisman.md Outdated
Comment thread docs/ai3_token/wallets/talisman.md
… path

- Updated the native Autonomys public address prefix notation from 'sue' to 'su' per maintainer review feedback.
- Swapped the missing placeholder image path 'Talisman-7-name.png' back to the verified 'Talisman-8.png' asset.
- Cleared the asset reference mismatch to allow the Netlify staging deploy preview check to pass.
…re backup section

- Corrected the native Autonomys mainnet address prefix indicator to 'su'.
- Removed the invalid reference to non-existent 'Talisman-7-name.png'.
- Restored 'Talisman-9.png' back into the onboarding flow sequence.
- Re-added the complete, missing wallet 'Backup Your Wallet' section before Troubleshooting.
@EmmanuelMarv

Copy link
Copy Markdown
Contributor Author

Hi @jim-counter and @EmilFattakhov I have addressed the review requests:

  • Fixed the address prefix to show the correct native su identifier string.
  • Cleared out the missing Talisman-7-name.png string which was breaking the Netlify check.
  • Restored Talisman-9.png back into the step sequence.
  • Fully re-inserted the missing "Backup Your Wallet" segment directly above Troubleshooting.

The file is completely updated and ready for review!

@jim-counter jim-counter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some additional questions.

Comment thread docs/ai3_token/wallets/talisman.md Outdated
Comment thread docs/ai3_token/wallets/talisman.md
Comment thread docs/ai3_token/wallets/talisman.md
Comment thread docs/ai3_token/wallets/talisman.md
@EmmanuelMarv

Copy link
Copy Markdown
Contributor Author

Hi @jim-counter thanks for digging into this flow! You caught some excellent points on asset alignment. Here is the breakdown of the updates made in the latest commit to address your feedback:

  1. Text vs. Screenshot Mismatch: You are completely correct. Talisman uses "Polkadot" branding for its Substrate accounts on that onboarding screen. I have updated the markdown text step 3 to read "Create a new Polkadot account" to strictly match the visual string inside Talisman-2.png.
  2. Dropped Screenshots (1-7) & Flow Validation: Yes, this flow has been validated against the modern extension workflow. Talisman heavily streamlined their onboarding; they cut out several intermediate informational splash pages that existed in the legacy documentation. The old images 3, 4, 5, and 7 are no longer part of the path. I have updated the text to perfectly frame the active assets (Talisman-1, Talisman-2, Talisman-6, and Talisman-9). Once this PR is approved, I will submit a quick follow-up chore PR to delete the unreferenced image files from the repository to prevent asset bloat.
  3. Backup & Import Layouts: I have restructured the backup and import text blocks so they stand alone perfectly with clear step actions using the verified active images (Talisman-6 for selection and Talisman-9 for the final step).

Ready for your review and the merge check!

@jim-counter jim-counter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple more tweaks please.

And can you remove the retired images in this PR to keep things neat.

Comment thread docs/ai3_token/wallets/talisman.md Outdated
Comment thread docs/ai3_token/wallets/talisman.md
Comment thread docs/ai3_token/wallets/talisman.md
- Reinstated original sidebar_position: 1 and sidebar_custom_props metadata.
- Re-added the official Talisman support documentation URL to the troubleshooting section.
- Permanently deleted unreferenced legacy onboarding screenshots (Talisman 3, 4, 5, 7) from the repository.
- Reinstated original sidebar_position: 1 and sidebar_custom_props metadata.
- Re-added the official Talisman support documentation URL to the troubleshooting section.
- Permanently deleted unreferenced legacy onboarding screenshots (Talisman 3, 4, 5, 7) from the repository.
@EmmanuelMarv

Copy link
Copy Markdown
Contributor Author

Hi @jim-counter I have addressed the final tweaks in the latest commits:

  • Reinstated the original sidebar_position: 1 and restored the sidebar_custom_props frontmatter block.
  • Added the official Talisman support documentation link back into the Troubleshooting introduction.
  • Completely removed the retired, unreferenced image assets (Talisman-3, -4, -5, and -7) directly within this branch to keep the repository neat.

The file is clean and ready for your final pass!

@EmmanuelMarv
EmmanuelMarv requested a review from jim-counter July 7, 2026 14:56

@jim-counter jim-counter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sidebar_custom_props: value needs adjusting please.

Comment thread docs/ai3_token/wallets/talisman.md

@jim-counter jim-counter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution @EmmanuelMarv! That's all the wallet refreshes taken care of by my count. This has been a great help 🔥

@jim-counter
jim-counter merged commit 6fc914e into autonomys:main Jul 8, 2026
6 checks passed
@EmmanuelMarv

Copy link
Copy Markdown
Contributor Author

Hi @jim-counter
Thank you! I am glad we got both the Polkadot.js and Talisman wallet overhauls dialed in perfectly and merged cleanly into main. I really enjoyed working through the details with you to get the user onboarding sharp.

Now that these refreshes are taken care of, I wanted to let you know that I am actively available for additional work. Beyond documentation updates, my core background is in frontend development, Web3 systems architecture, and technical ecosystem growth.

I am heavily aligned with the Autonomys mission and am looking for open developer, technical writing, or technical ambassador management opportunities within the ecosystem. If there are any open contract roles, tasks, or positions where the team needs consistent technical execution, I’d love to jump in and take them off your plate.

Let me know if there is an open path or someone specific I should connect with to discuss this further!

Best regards,
Emmanuel Chibuzor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants