I wouldn't recommend to show credits in captions (if it's not required legally), as this is piece of information not particularly important for the reader — and all the captions might become pretty lengthy and messy without additional value for the end user.
Anna Zabolotnaya I suppose it depends on how it's implemented. I know we use LiveFyre here at The Times
Maybe FB comments too, there may be a couple of others I can't recall right now
I'd recommend Postmatic or Epoch; checkout this article
Second the idea of keeping comments native, but extending them. Comments are content and, as such, valuable to media organizations, so they should be kept inside the CMS.
Thanks for the feedback everyone! Clearly both models need to be available — to that end, dealing with comments might be outside of what we want to accomplish with this (especially since commenting isn't really something specific to news and journalism).
Alex Vasquez Edit Flow is definitely what I had in mind, though I've gotten quite a lot of mixed feedback about it from various people on the News Nerdery Slack team.
This is a crazy-cool idea; particularly because this is a place where The Times can lend serious expertise. How are you thinking? OAuth combined with something like Stripe? What about something micropayment-y?
Yeah that sounds like the right sort of combo. The plugin should create the appropriate sign up / payment pages and configure the gateways for payment (Stripe, PayPal I guess) in a similar way to WooCommerce does it. Then it should also have multiple membership styles (so hard paywall, leaky paywall with tokenised URLs, first 10 articles free etc.) and allow them all to be configured by the site owner. It may, at the beginning, just start as a on/off membership system, with a view to being expanded in the future.
I'd recommend it as a separate, but companion plugin (add-on if you will). Not all news organizations use paywalls and integrating them into the main thing would unnecessarily clutter the main product.