Moving FAQ - Updating user information

[Melkeb]

No description provided.

[jennaj]

This is good

Actually, I would rename this so that it matches the terms used in the Galaxy application. Suggest this even though is long. It matches the path to where the action is performed in Galaxy.

account_user_preferences_manage_information

The original FAQ content (creating an account) had account changes/updates included for a specific reason -- if your email changes, you don't need to make another account, should instead update the current account. Very few people understand that. The function was was split out and lost context, and it is probably Ok. We could consider adding in phrases we think people would try to search with to the end of the FAQs -- like: "My email changed"

The primary "account preferences" FAQ was this one: https://galaxyproject.org/support/account-updates/. It covers mostly the same info, but also includes how to reset a password -- "I forgot my password" is what I would name that content to make it searchable. The stuff about API keys can probably be dropped.

Long term goal is to have Galaxy directly open the GTN pop-up, at the FAQ, instead of redirecting to a link in another browser tab. If the files are named the same as the paths one would follow in Galaxy, could be easier to organized/map them back to functions. But I'm not stuck on this (too much).

[shiltemann]

we do already have one other FAQ with area: user preferences (the one for the API key), so this could go there as well

[Melkeb]

Thanks for the comments. Forgot Password is not included in this FAQ because it looked like a different issue from updating/ changing user preferences (was thinking of a separate FAQ for this). I will add common phrases on the FAQ that people might search for.

[Melkeb]

I updated the area, and included "email changes" in a sentence as well as information about updating current account at the bottom of the FAQ.

[beatrizserrano]

This PR looks good to me, so unless I'm missing something (@shiltemann @hexylena), we could merge :) Thank you @Melkeb 🎉