Inconsistent terminology in MODX

[davidpede]

Summary

A number of new clients have had issue with inconsistent action button labels, confirmation + warning dialog, different labels for the same thing etc. Has caused confusion and annoyance with some of them.

Referring to things like:

• Delete action labelled Delete and Remove in different menus/buttons
• Edit action labelled Edit and Update in different menus/buttons
• Create action labelled Create and New in different menus/buttons
• Folders referred to as Directory and Folder in different places
• Warning/Confirmation dialogs not helpful and totally inconstant across resources, elements, file/folder, grids etc (especially delete)
• Warning dialog terminology doesn't match action label
  (There is more but you get the idea)

I'm happy to look at this but can I get some feedback first:

• Do people think this is worth looking at?
• Is this the right place or should it go through the MAB manager group?
• Are there any guidelines for making changes to lexicon files?

Related

#13065, #4834, #1188, #764, #13448, #13497

Environment

MODX all versions

[Mark-H]

• Yes
• While the MAB could take a role in this, don't let that stop you. Perhaps you'll end up draft a set of guidelines on what type of terminology to use. If you then find a member of the MAB that is on board with that to turn, they can act as editor for a recommendation and put it up for a MAB vote to make it "official".
• English lexicons are managed through this repo. Translations via CrowdIn.

To propose changes you'd use the same process as other contributions. Create a git branch, make and commit your changes, send a pull request. I'd recommend branching of 2.x and also sending your changes to 2.x, so these updates could be incorporated into 2.6/2.7.

The lexicon files are in https://github.com/modxcms/revolution/tree/2.x/core/lexicon/en. Having a search tool will help find where each entry is. ;)

Keep in mind lexicons are cached by default. Set cache_lexicon_topics to no so you wont have to clear the cache after each change.

The 'Delete' and 'Remove' labels are tricky; resources that are 'deleted' are just flagged in the database for deletion, while 'remove' actually refers to permanently deleting something from the database.

[davidpede]

Not a simple task but I think it will come down to writing style and striking the balance between simple, consistent UX and technical accuracy.

Were in process of getting more formalised feedback from the clients that have raised these issues which will help a lot and material design will also influence the strategy. Some good reading:

https://material.io/guidelines/style/writing.html#writing-language
https://material.io/guidelines/components/dialogs.html#dialogs-alerts

[wuuti]

@sottwell regarding remove and delete there is additionally the word "purge" being used...

[JoshuaLuckers]

What about we use something like this:

• "Move to Trash" for soft-delete actions
• "Delete Immediatley" for hard-delete actions

[Ruslan-Aleev]

Another unnecessary terminology:
"Extras, add-ons, packages, components".
As I understand it, packages - is an installation archive for components.
The rest (extras, add-ons) is not clear to what applies.

Also sometimes referred to as "plugins", which is somewhat confusing since in MODX "plugins" refers to a specific type of extra, add-on, component.

[Ruslan-Aleev]

Template Variable or TV.
It makes sense, when creating a TV, in the description above, to write both form of the TV title: full and the abbreviation. And then use only the abbreviated form of TV title in manager.

[Ruslan-Aleev]

Settings

• In MODX there are a lot of settings, descriptions or name of which are built from the negative, such as, "If the setting ... , set this to No.", but more correctly - "If the setting ... , set this to Yes."
• Different format for describing settings, for example, somewhere "If the setting ... , set this to Yes.", and somewhere "Set this to Yes, if the setting ...". All the names / description of the settings should be remade according to the pattern: "Description of the setting, then select the status".

[Ruslan-Aleev]

In the "Package Management" section, each package has the "Uninstall" and "Remove" buttons. But their names and actions are not entirely correct.
"Uninstall" sometimes means deleting, although in MODX it works like a downgrade to the previous version, it is better to call it "Downgrade".
"Remove" does not remove the package from the files unless the "Force Package Removal" checkbox is checked, although it should always remove.
It seems that the checkbox "Force Package Removal" is needed for emergency removal, as if the removal is not correct, and it confuses users.

Related with #13554 (comment)