Follow up to #67
In our team, the most used comment by far is to highlight text just to write a comment that says "changed". Often all we need is for other collaborators to look again at text they've read before, or notice an addition or deletion. It'd be nice if there was a comment type that was specific to that workflow, with a specific highlight color or style, and a specific comment look in the sidebar (since there's no need for custom text).
I don't know if this feature is best kept simple (just a "changed" comment type) or if it is better to make it generic (a panel allowing to create "comment types", name them, and decide of options such as color, text, and so on).
It may be a very niche usage that's only useful for us. And for sure, one can use a different highlight plugin without comments for that, but it'd be neater and a nicer experience if a single plugin handled all of this (also, it's easier to remove all highlights following a specific pattern before making a markdown public).
I didn't mark this as a feature request because it's simultaneously pretty complex while being probably of low generic value, so I suggest to wait for more people to use this plugin and to have a need before thinking deeper about it.
Follow up to #67
In our team, the most used comment by far is to highlight text just to write a comment that says "changed". Often all we need is for other collaborators to look again at text they've read before, or notice an addition or deletion. It'd be nice if there was a comment type that was specific to that workflow, with a specific highlight color or style, and a specific comment look in the sidebar (since there's no need for custom text).
I don't know if this feature is best kept simple (just a "changed" comment type) or if it is better to make it generic (a panel allowing to create "comment types", name them, and decide of options such as color, text, and so on).
It may be a very niche usage that's only useful for us. And for sure, one can use a different highlight plugin without comments for that, but it'd be neater and a nicer experience if a single plugin handled all of this (also, it's easier to remove all highlights following a specific pattern before making a markdown public).
I didn't mark this as a feature request because it's simultaneously pretty complex while being probably of low generic value, so I suggest to wait for more people to use this plugin and to have a need before thinking deeper about it.