Of course, my system was not able to process a map it was not aware of. I was planning to build a simple click & drag editor to make drawing maps a no-brainer.
One day I implemented this functionality:
The number one reported issue was 'accidental node creation'.
This issue turned out to be unsolvable. The clutter was growing as new features were taking shape. I was not able to introduce nested maps exactly because of this.
I had to give up and look for a new metaphore.
If you want to move any component, you need to tell the editor that you will be moving them by selecting 'Move' action. This is not that simple as click-and-drag, but it totally removes acciddental component creation. As a side effect, further growth was unlocked. It will be very easy to add more components (or create so demanded undo functionality).
The new editor is still under construction, but you may test it out by adding hash to your map url: