When javafx was bundled with JDK 9 and JDK 10, there was no need
to specify a module path to locate the fx modules.
Running today with the unbundled SDK, you do need to specify it,
when compiling and running. Since the controls module requires
most of the modules to run a typical application there are recommendations such as
javac --module-path $PATH_TO_FX --add-modules=javafx.controls HelloFX.java
java --module-path $PATH_TO_FX --add-modules=javafx.controls HelloFX

But why controls ? I believe it would be better to have an aggregator module similar to java.se, which will require all the modules which will deal with
some special cases and just generally have a more logical name.
Apps wanting a smaller set can still use jlink to create a minimal image.

Some suggestions for the name are :
javafx.javafx
javafx.all
javafx.runtime