Page MenuHomePhabricator

Unify error messages in MobileFrontend/Minerva Neue
Open, MediumPublic

Description

Error message voice & tone, how we're speaking to our users in case of an error, is organically grown and very mixed.
List of current error messages in MobileFrontend:

  • "mobile-frontend-cite-error-title": "Error loading citations",
  • "mobile-frontend-cite-error": "A problem occurred while attempting to load citations due to a bad revision identifier.",
  • "mobile-frontend-references-citation-error": "An error occurred and it was not possible to load this citation.",
  • "mobile-frontend-editor-error": "Error, edit not saved.",
  • "mobile-frontend-editor-error-conflict": "Error, another user has edited this page.",
  • "mobile-frontend-editor-error-loading": "Error, can't load the editor.",
  • "mobile-frontend-editor-error-preview": "Error, something unexpected happened upon loading the preview. Please close and try again.",
  • "mobile-frontend-nearby-error": "{{SITENAME}} Nearby is having some issues.",
  • "mobile-frontend-nearby-error-guidance": "Try refreshing your location.",
  • "mobile-frontend-references-citation-error": "An error occurred and it was not possible to load this citation.",
  • "mobile-frontend-save-error": "Error saving settings. Please make sure that you have cookies enabled.",
  • "mobile-frontend-talk-topic-error": "The topic can't be added due to an unknown error.",
  • "mobile-frontend-watchlist-error": "There was a problem watching this page. Please try again.",

Expected result

  • Use similar wording, not once “error”, once “problem”
  • Find similar voice and tone for all error messages

Questions

  • Should we remove “Error, ” at beginning of messages and rather use description of action and “failed”. Example: “Saving settings failed.”