docs: comprehensive overhaul and alignment of Talisman wallet setup guide - #966
Conversation
- 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.
✅ Deploy Preview for subspace-docs-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jim-counter
left a comment
There was a problem hiding this comment.
Some changes please @EmmanuelMarv.
… 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.
|
Hi @jim-counter and @EmilFattakhov I have addressed the review requests:
The file is completely updated and ready for review! |
jim-counter
left a comment
There was a problem hiding this comment.
Some additional questions.
|
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:
Ready for your review and the merge check! |
jim-counter
left a comment
There was a problem hiding this comment.
A couple more tweaks please.
And can you remove the retired images in this PR to keep things neat.
- 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.
|
Hi @jim-counter I have addressed the final tweaks in the latest commits:
The file is clean and ready for your final pass! |
jim-counter
left a comment
There was a problem hiding this comment.
The sidebar_custom_props: value needs adjusting please.
jim-counter
left a comment
There was a problem hiding this comment.
Thanks for the contribution @EmmanuelMarv! That's all the wallet refreshes taken care of by my count. This has been a great help 🔥
|
Hi @jim-counter 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, |
Description
The existing
talisman.mdsetup 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
suestring format).Verification
All text entries, headers, and explicit UI strings were manually audited and verified line-by-line against the live client layouts.