Replies: 1 comment 2 replies
-
Thanks for the suggestions, @lmc395. I temporarily unlocked wiki for editing so that you can edit the pages yourself. It's usually restricted to prevent harmful edits. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First off: sorry if the wiki's not open for feedback. If it is, though, I've got some suggestions for the documentation on finding user tokens:
Troubleshooting.md
.Putting all that into action,
Obtaining-Token-and-Channel-IDs.md
'd look something like this:Attached is an edit of
Obtaining-Token-and-Channel-IDs.md
with the above changes: Obtaining-Token-and-Channel-IDs-a.mdThat all said, hopefully this isn't overbearing, but I'd like to pitch a rewrite for the above:
Attached is an edit of
Obtaining-Token-and-Channel-IDs.md
with the above changes: Obtaining-Token-and-Channel-IDs-b.md (Heads up, by the way: the images in this one use alignment tags that don't work on mobile browsers. Rather than floating to right, the images'll display inline before the text on mobile.)This all might seem a bit excessive (especially considering what's already in the wiki does a better job than most dedicated guides), but I think these changes are worth while. More detailed, clear, well-structured instructions with images'll be more intuitive to users-- and it's worth considering Discord isn't exclusively used by the kinds of people who'll feel comfortable using "web developer tools," and wanting your chat logs exported isn't a niche ask. More complete instructions'll cover more users and give them more alternatives if they run into issues. Polishing things up (formatting, structure, etc) and linking to authoritative sources'll help earn the user's trust (which I'm guessing is pretty important given user tokens're involved).
Beta Was this translation helpful? Give feedback.
All reactions