Some of these features are so powerful that it changes my entire workflow, and makes it extremely efficient.
However, it is not easy to figure out all these features (especially for non-programmers like me).
My progress is slow because I have to figure out every new feature by myself.
The forum may already have this information, but locating those pages is difficult.
Those pages remain hidden till we happen to discuss that particular topic in the forum and someone posts a link.
And that brings me to this suggestion:
Please list all new features in the help documentation.
That will lead to faster discovery, and also nudge the users to test them out on priority, and give suggestions for betterment.
IMHO the best way to declare new features is to create a new node "Experimental features (Alpha)".
That way, the users will find all new features in a single place.
This node should have subnodes that describe each feature in more detail.
Each page in this section should carry a caution that these are experimental features, and some of them may not appear in the next version of Everything. (Also warn the user to use with caution, etc.)
*******
Adding examples (use cases) to the help documentation:
Many users are not imaginative enough to figure out how to exploit a given feature, just by reading its basic description.
They need examples to catch on.
In fact, this idea applies even to the mature features that already exist in the stable version of Everything.
If the user can read up how to put these features to good use, his productivity will shoot up!
For example, let's consider this topic: "how to use the command line tokens".
To educate a user, this page should have hyperlinks for each token, which takes us to a separate page, which describes how to use that particular token, and provides some example use cases.
This page can also describe how to combine this token with other tokens (and features) to extend the functionality.