access_token details and cache flushing should be somewhere more discoverable than "Help and About" in usersettings

[ara4n]

No description provided.

[turt2live]

Where should it be instead?

[lampholder]

We could move access_token to the bottom of the front profile page?

Clearing cache feels like it's maybe fine on the 'help' page, though maybe dressed up as more of a self-service troubleshooting option? Perhaps with some microcopy explaining what sort of problems it can solve and what it will do?

An additional thought I just had - we could dress that whole flow up as a "Shit's gone wonky" button that tells users what it might fix, asks them what they're hoping for it to fix, invites them to submit a bug + logs, then does the clear cache and reset needful?

[t3chguy]

@americanrefugee since you have asked to hide these even more

[americanrefugee]

Danielle and I wanted to move these features to be moved to Dev Tools, not Help & About.

We questioned why normal users would ever need to see this, which is why we moved it in the first place.

@daniellekirkwood what do you think about moving "Access Token" and "Clear Cache" to Account?

@lampholder Can you provide a description of when / why you would need to clear the cache or use the Access token? And is clearing the cache destructive in any way? I can help with final copy / wording, but just wanted to understand myself (which I currently don't).

[t3chguy]

And is clearing the cache destructive in any way?

It is not

[turt2live]

Clear Cache fixes a lot of issues users may be encountering, so should be near bug reporting (but not so close as to cause misclick) in my opinion.

Access token information can move safely to devtools.

[americanrefugee]

Cool. I think that makes sense.

• Access token info will move to Dev Tools, with styling guidance here

• Clearing cache will stay under Help & About, but positioned between User guide and Feedback

  • Additionally, I recommend renaming the sections to "Having a problem?" (clear cache) and simply "Feedback" (form)
  • The logic here is that we want users to resolve the issue themselves first... so RTDM or clear your cash. THEN send feedback if that doesn't fix your problem. I especially advocate for this considering that our current feedback submission go into a void that nobody is currently caring for.
  • I made up the text below "Having a problem"?, please verify or correct me :)

WDYT @turt2live @daniellekirkwood or @t3chguy ?

[t3chguy]

1. Where would the Element FAQ button go?
2. Where would it go for brands which don't call their app Element
3. The Send feedback section isn't enabled on all instances

[turt2live]

from a random user perspective, looks great :)

Thanks for the quick iteration.

[americanrefugee]

1. Where would the Element FAQ button go?
2. Where would it go for brands which don't call their app Element
3. The Send feedback section isn't enabled on all instances

1. It would go here: https://element.io/user-guide. I also just renamed the button to "View user guide" since it's not actually a FAQ page.
2. I don't know... Do we need a generic version of the user guide that clients can host somewhere? It would be unfortunate if we would need to drop that for some clients.
3. Ok. As long as there's a user guide and clear cache, users should be able to get some help. If a worst case scenario is ONLY clear cache and general info, then we should have general info expanded by default.

Of course, the current user guide is very out of date (at least visually). Perhaps @JordanConnor has some insight into the current / future state of this resource?

[t3chguy]

It would go here: element.io/user-guide. I also just renamed the button to "View user guide" since it's not actually a FAQ page.

That user guide won't work for customers with different config options

I don't know... Do we need a generic version of the user guide that clients can host somewhere? It would be unfortunate if we would need to drop that for some clients.

Same as above. Some Element instances run without internet access entirely so ideally the guide would be in the client rather than some external thing.