We could use twitter to attach discussion threads to any Prose documents. Might be easy to implement. Same approach as on the developmentseed blog, except we'd show the actual tweet not just the user.
@samanpwbb @gundersen what do you think?
@michael you thinking more for people using Prose for their blog tat would want to see the tweets?
@gundersen Nah, that's left over to the website developer. I'm actually referring to the post creation process, such making comments/suggestions on an unpublished article. But now that I think about it, tweets may not be the way to go here. They're too explicit or official for this usecase. I've looked into the GitHub API since they feature comments as well, but they stick on commits, and I'd rather have them just attached to a particular file.
Doesn't have high priority though. It was just a thought to improve the collaborative writing / review process.
I think we should place collaborative / community editing in general outside the scope of the Prose backend.
@michael ah, ok. Yeah, I know internally we would never tweet about drafts we are working on - we would use a ticket in Github for this.
@samanpwbb Mhh not sure. Actually I consider this as one of the main-use cases, since that's what we do. Someone writes up a blogpost and other give comments and alter the text until it gets published. It would be very convenient to have this discussion available right within Prose, instead of using an external discussion thread.
@gundersen yeah, that's what I mean.. it could be even easier. :)
@michael cool, I am not seeing a workflow issue with using tickets to talk about the status of a page or a blog post, since we use tickets to talk about everything. It would be more complicated to have to have a separate ticketing system just for publishing. A lot of ideas just start as tickets, not as posts, so I don't see how this would work since the thread would be on a ticket to begin with and we are using github a lot to refer to other tickets like #ticketnumber when talking about a post etc.
@michael Hm, I get what you're saying, definitely. Right now using the GitHub issue tracker to discuss posts makes a lot of sense for our internal use case. So the question is, 'how do we abstract this same discussion away from GitHub for people that want to use Prose, but don't want to deal directly with GitHub?". That's a big question, but if we do go about tackling it, I think it should be based on GitHub if possible, not through some other system.
What about using HTML comments that wouldn't show up in preview?
Maybe we could use HTML comments?
<!-- A comment that would be rendered differently in prose's preview mode.
The publish button could purge comments like this as part of the commit? -->
Out of scope for the next version. Pls see #295