You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each one takes the user into a page dedicated for it, for example, Music would take the user to a page which shows them how to play music, the supported sources, how to control it, who can control it, the music dashboard...
An example of what they can contain, and how would they be useful for the end-user:
Let's say the user wants to use reaction roles, then in the main guides page, they'd enter on the Roles button and look for Reaction Roles, in that page, Skyra will show how to configure them in different sections (add new ones, remove existing ones...), using Discord messages. We could use skyra-project/discord-components#22 to be done first so we can show-case this, same for starboard.
A more complex matter is that we cannot tell users what Skyra can do in a burst, Skyra is huge and the technical list of features is huge!
Besides, users aren't really interested on knowing everything Skyra can do, but rather, whether or not she can do the things they want. Showing them a full list of features (plus +240 commands in /commands) when they just want a bot for some basic logging and reaction roles makes them lose a lot of time.
Naturally, users will explore and not only see if Skyra has everything they want/need, and how to proceed with everything as we'll not only show them if Skyra can do what they want, but we'd also show them step-by-step how to set-up everything, and even, show them how Skyra's messages look like (e.g. how Skyra's starboard messages look like), but they will also explore other features they weren't looking for in the first place (let's say they wanted Skyra to take care of reaction roles, but then they needed a new word filter system because they used another bot, and wasn't working well).
The text was updated successfully, but these errors were encountered:
There should be a way to display guides to users in an organized manner.
In the main guides's page, we'd show a few buttons (possibly more than those 6, e.g. starboard, rough draft here):
Each one takes the user into a page dedicated for it, for example,
Music
would take the user to a page which shows them how to play music, the supported sources, how to control it, who can control it, the music dashboard...An example of what they can contain, and how would they be useful for the end-user:
Let's say the user wants to use reaction roles, then in the main guides page, they'd enter on the
Roles
button and look forReaction Roles
, in that page, Skyra will show how to configure them in different sections (add new ones, remove existing ones...), using Discord messages. We could use skyra-project/discord-components#22 to be done first so we can show-case this, same for starboard.A more complex matter is that we cannot tell users what Skyra can do in a burst, Skyra is huge and the technical list of features is huge!
Besides, users aren't really interested on knowing everything Skyra can do, but rather, whether or not she can do the things they want. Showing them a full list of features (plus +240 commands in /commands) when they just want a bot for some basic logging and reaction roles makes them lose a lot of time.
Naturally, users will explore and not only see if Skyra has everything they want/need, and how to proceed with everything as we'll not only show them if Skyra can do what they want, but we'd also show them step-by-step how to set-up everything, and even, show them how Skyra's messages look like (e.g. how Skyra's starboard messages look like), but they will also explore other features they weren't looking for in the first place (let's say they wanted Skyra to take care of reaction roles, but then they needed a new word filter system because they used another bot, and wasn't working well).
The text was updated successfully, but these errors were encountered: