Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to connect the account to Stash #3

Merged
merged 2 commits into from Nov 12, 2022
Merged

How to connect the account to Stash #3

merged 2 commits into from Nov 12, 2022

Conversation

DogmaDragon
Copy link
Contributor

It's the same information as from the pinned message, but for completeness, it's worth adding.

Based on Scruffy suggestion.

It's the same information as from the pinned message, but for completeness, it's worth adding. 

Based on Scruffy suggestion.
@DogmaDragon
Copy link
Contributor Author

Copied from Discord https://discord.com/channels/559159668438728723/559159931505213440/1040890400715587634

This came up not too long ago from someone else following the guide, but I still feel like we should try to avoid repeating ourselves as much as we can. Having our documentation split across half a dozen places and trying to keep all of them up to date every time we change something is a big part of the confusion already. I think we need those instructions here already because this is where the invite codes are and this is where you ask Infinite for the edit role. So I decided to skip those details in the guide so we would only need to update them in one place for once.

I think the opposite is true. Invite codes are pinned in the first message and most people will never scroll down to the bottom if the keys at the top work. So they will never even see there is a second pinned message. Then they ask for help and will be directed to the same pinned messages again.

And I agree generally with you that having to update multiple places is a big headache, the instructions for creating an account are pretty constant.

If the instructions would have existed in their current form, they would have needed to be updated twice. First, when preferences changed to settings and second when the Discord channel name changed from stashbox-invites to stashdb-invites. It's a good record of consistency in my view.

@AdultSun AdultSun added the update section Update to existing documentation label Nov 12, 2022
Updates the whole section of instructions to provide more detail and adjusts formatting slightly (limits `code` to snippets users are expected to copy and consistently uses **bold** for every quoted button/section/heading users are asked to find).
@AdultSun
Copy link
Collaborator

I expanded the new instructions section with a little more detail. I also adjusted the formatting a little because it was a bit inconsistent: limiting code to snippets that users are expected to copy and using bold for everything else that users are asked to find.

I'm not at my desktop so I can't build a local preview first to test everything, but I'm not too worried about merging it as-is. We can fix any inconsistencies that pop up later if we need to.

@AdultSun AdultSun merged commit 5e0d0d8 into stashapp:main Nov 12, 2022
@DogmaDragon DogmaDragon deleted the patch-2 branch November 14, 2022 10:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
update section Update to existing documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants