Correct wording for Start Nodes #18663
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Start Node terminology is very technical and not very specific.
'Start' does not specify that this is about limiting the users access.
'Node' is not a term we use anywhere in the UI. Technical users may understand it, but then again it is off with our general wording which uses terms like 'Item, Document, Media Item, Folder'.
So we will correct this to be more friendly to new comers, and make the experience of the UI more consistent.
Instead, it will be called 'access' if further specification is needed, like variable name wise, then Access Limitation could be the term. For a start, this PR mainly corrects the displayed wording.
This PR makes it look like this:
And all other places where the wording 'start node' was used.