[Feature Request] comments (that don't get rendered) & document stats

[evejk]

I couldn’t find these features in Quiver (neither requests for it), so here I am: I loveee Quiver so far, but I’m really missing the following for writing longer texts, so maybe you could consider adding them in some future update :)

1 - Comments (that don't get rendered)

Ability to write comments into notes (inside Markdown cells) that are only visible in the editor but don’t get exported/rendered.

A bit like in this writing app that starts with Uly … ;D. They use %% for block comments and ++ for line comments. It’s a very useful feature if you want to keep future reminders or "to-write" infos inside your notes while still being able to export it whenever necessary – rather than having to keep comments in a separate note.

2- Document info/stats

If writing longer texts or papers etc. it can be very helpful to know things like:

• Counts of words and characters (with and without spaces)
• Number of pages (if exported/printed)
• Reading time

I can imagine those stats living in the top bar of the document, next to the tags (e.g.). Or with a symbol at the bottom right, next to the star. I know Quiver is rather a devs notebook than a writing app, but I can see it being helpful in a lot of cases. (At least for me, haha)

Thanks! <3

[tflo]

Comments (that don't get rendered)

You could use the usual HTML comment syntax: <!-- my comment --> This will not get rendered, but of course it will get exported (as comment) in the HTML source.

For more (creative) tips see this Stackoverflow post.

I'm not a big fan of adding private features (à la Ulysses) to Markdown. The main effect is that can't use your text in other Markdown editors anymore. And there are already more than enough Markdown flavors ;)

– Tom

[evejk]

For more (creative) tips see this Stackoverflow post.

Thanks, Tom!

I personally don't mind private features, but I understand where you're coming from ... Too much flavours make it hard to brew a universally usable soup ;) – especially if you want to use it with other editors. (I wouldn't mind if the feature is for a text cell though ... so Markdown can stay untouched).

All of the creative tips in that link of yours work with Quiver – but only if there's an empty line before the comment, and only for single line comments.

I mainly export to PDF, so the HTML comment inside Markdown is the best option for me so far (since it allows multi line). If in a separate Markdown cell, it will add a bit of empty space to the exported file - but it will not, if it's in a Markdown cell with other (visible) Markdown. So, yeah ... it's not perfect, but I guess I can live with that, haha. Thanks again :)

[ylian]

I am also inclined to keep Quiver's Markdown support as close to CommonMark as possible. If there is a reasonable workaround, I prefer not to implement a private feature. I think comments fall into this category.

The other suggestion of document stats is certainly useful.

[matchavez]

I'd like to see it as close to GFM as humanly possible. I mean, we are here...

https://github.github.com/gfm/