Creating an issue just to track my work. This is spawned from #98. One small question that I have is more of a philosophical one, so pinging @marcoieni and @stevenguh.

I'm building out the mapping and would like your thoughts on whether or not I should make additional menus expecting to allow VSpaceCode to eventually build in all mappings available in a theoretically feature-complete Markdown major mode, or should I just do what makes the "most sense" given the commands that are available in Markdown All in One? For example, using the Markdown layer as a basis for implementation, I'd be making the mapping for "bold" SPC m x b instead of SPC m b. The main benefit of this would be reducing the need to shuffle things around down the line when this menu gets more built-out.

The reason why I ask is because right now, it doesn't seem like there will be a ton of keybindings in the "top layer" (i.e. SPC m <something>), despite there not being enough mappings at the start to justify creating whole-new menus. Spacemac's Markdown layer has enough commands to justify the split into several menus, but it doesn't seem like that'll be the case from the get-go for VSpaceCode.