A call for folks interested in working on Notational Velocity

Update: Most of the wishes in my Notational Velocity wish list have now been granted by Brett Terpstra and others. My current choice for Notational Velocity is Brett's nvALT.

* * *

The most popular PE posts by far continue to be several that I wrote earlier this year on Markdown, MultiMarkdown, and Notational Velocity and how I use them in my writing workflows:

These workflows are made possible by three four key individuals. I owe them a huge thanks because I use their creations like crazy. These guys are:

I’ve had several email exchanges with Steven about my personal interest in working on Notational Velocity. He’s been really helpful and responsive.

But the reality is that I’m not a programmer. Moreover, I just can’t find the time to get myself up to speed enough to do anything meaningful with the Notational Velocity source code myself. But I definitely have a few ideas on how it could be enhanced to add even more value to my writing workflows.

Given all the interest in (Multi)Markdown and Notational Velocity here at PE through comments, emails, and search traffic, I thought I would just throw out some of my own ideas for future enhancements.

How I can help you

If you are interested in extending Notational Velocity further, feel free to use the ideas in this post, leave comments here, or contact me.

If you implement any of these ideas (or others that come along later) to create a new stable version of Notational Velocity, I can help you in the following ways:

  • Promote your work with a blog post
  • Provide a permanent link to your work on this site
  • Provide design feedback based on my own use
  • General beta testing

So without further rambling, here is my wishlist…

4 ideas for extending Notational Velocity

Each of these is intended to enhance Notational Velocity as a web writer’s tool while keeping the interface as minimalist as possible:

  1. Move HTML preview pane into a ‘fly-out’ drawer
  2. View HTML source
  3. Export as HTML
  4. Add support for MultiMarkdown

Idea 1: Move HTML preview pane into a ‘fly-out’ drawer

If you’ve ever used a program like Path Finder, you’re familiar with the fly-out drawers that expand and collapse on each side of the main interface.

When I write in Steven’s version of Notational Velocity, I often keep the HTML preview pane at the bottom hidden until I’m ready to review things.  As I edit, I find myself going back and forth between the two panes as I edit what I’ve written.

I think that if the HTML preview pane was on the right side (and the same height as the Notational Velocity writing area), it would be easier to go back and forth. A “right to left” flow is also consistent with core Mac design principles that can be found in everything from file menus to iOS apps.

Here is an unartistic sketch of how an HTML 'fly-out' drawer might be implemented on the right side of the main Notational Velocity window:

The user would have the option of keeping the drawer hidden or exposed by clicking a discreet button somewhere, or perhaps through a keyboard shortcut.

Synchronous scrolling between the writing area and drawer pane would be a bonus too.

Idea 2: View HTML source

I’ve already written about how I use Hazel to automate the conversion of Markdown to HTML. If I could view the HTML source underlying the HTML pane in Notational Velocity, I could cut Hazel out of my workflow. (It won’t hurt her feelings; I promise.)

I’m pretty sure that the HTML preview pane is a web browser, so perhaps just adding “View Source” menu option (like a regular web browser) would suffice.

Idea 3: Export as HTML

As an alternative to Idea 2, a menu option that lets the user export the current note as an HTML file would also be great.

Idea 4: Add support for MultiMarkdown

This one is self-explanatory, I think. By adding support for MultiMarkdown, not just Markdown, the HTML preview pane would be capable of displaying MultiMarkdown-specific items like HTML tables.

From here

As I said above, I’m really grateful to everyone that’s played a role in creating these great tools. Steven Frank’s version of Notational Velocity is awesome, and it’s changed how I write for the better.

If you like or dislike my ideas above, let me know. If you have your own, let me know those too. Let’s worth together to make Notational Velocity as great as it can be.

A few more resources: