- decoupling the tool from the native code. As installing the native parts never is an easy task, and exporting a map is not a critical functionality, the tool will work now even if it is impossible to export maps as png.
- decoupling from the stormpath user management. I have relied on the stormpath for all those out-of-the-box integrations, which was great for all but developers. Scott introduced a developer mode, which opens a lot of possibilities (especially for testing). All of this is accompanied by documentation improvements.
- and last but not least - x axis got more detailed labels:
I am very proud to announce that the mapping tool has received first contributions authored by @scottweinstein, which include:
What's more, Scott hinted he is working on "corporate directory integration". I find this to be hilarious news for the tool!
Looking for user needs is difficult (you do remember that I would like to know your opinion about the mapping tool, do you?). Anyway, I thought I would make the editor a bit more friendly to the user, so I have implemented support for first three steps of the mapping process defined by Simon.
After you create a map, you are in the first step and you are expected to define user needs. And you are told how to do it.
The 'Mark complete' button visible on the Screenshot 2 becomes active once there are some user needs on the map. And each component put on the map is by default marked as user need. And, if it was not enough, clicking on the blue question marks brings you knowlegde you need (see Screenshot 3).
As I have said - there are three steps supported - I'm too tired today to describe them all, so just see yourself:
This functionality is enabled only for newly created maps.
Yes, that's true that I implement things a bit randomly, so, if there is a feature that you would like to see, tell me, now:
Today I have discovered that my map editor reacted very poorly to window resize attempts. The problem was that the background image with axes was scaled proportionately to the map canvas while the map was never scaled and relied on overflow, which was giving really weird effects.
This is fixed since now.
And, as a bonus, auxiliary lines marking certain evolution phases were added.
It has been exactly a year since I have stumbled upon Simon's talk, realized what I have found, read the entire blog a couple of times, and thought that the world is mine now :).
The year was fantastic, and running wardleymaps.com taught me one thing - mapping is just a fraction of the whole fun. Scenario planning and execution are also constitutional parts of it, therefore knowing what to do does not imply how to do it. Simple things looking easy on the map are hard to execute. Let's look for example at the following map:
It looks simple, but believe me, it is not :-). During this small step I am supposed to find out what are the actual user needs instead of what I thought they are. So I would like to ask you for a favor - please answer this one simple question:
Thank you in advance for any answers!
I can't stress enough how important they are for me!