{"action":"created","issue":{"url":"https://api.github.com/repos/netlify/netlify-cms/issues/1193","repository_url":"https://api.github.com/repos/netlify/netlify-cms","labels_url":"https://api.github.com/repos/netlify/netlify-cms/issues/1193/labels{/name}","comments_url":"https://api.github.com/repos/netlify/netlify-cms/issues/1193/comments","events_url":"https://api.github.com/repos/netlify/netlify-cms/issues/1193/events","html_url":"https://github.com/netlify/netlify-cms/issues/1193","id":308347646,"number":1193,"title":"NetlifyCMS handling Staticman comment moderation","user":{"login":"aleksandarbasara","id":198876,"avatar_url":"https://avatars0.githubusercontent.com/u/198876?v=4","gravatar_id":"","url":"https://api.github.com/users/aleksandarbasara","html_url":"https://github.com/aleksandarbasara","followers_url":"https://api.github.com/users/aleksandarbasara/followers","following_url":"https://api.github.com/users/aleksandarbasara/following{/other_user}","gists_url":"https://api.github.com/users/aleksandarbasara/gists{/gist_id}","starred_url":"https://api.github.com/users/aleksandarbasara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aleksandarbasara/subscriptions","organizations_url":"https://api.github.com/users/aleksandarbasara/orgs","repos_url":"https://api.github.com/users/aleksandarbasara/repos","events_url":"https://api.github.com/users/aleksandarbasara/events{/privacy}","received_events_url":"https://api.github.com/users/aleksandarbasara/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-25T12:58:53Z","updated_at":"2018-03-27T22:11:22Z","closed_at":null,"author_association":"NONE","body":"\r\n**- Do you want to request a *feature* or report a *bug*?**\r\n\r\nFeature\r\n\r\n**- What is the expected behaviour?**\r\n\r\nNetlifyCMS handling [Staticman](https://staticman.net) comment moderation.\r\n\r\n**Staticman brings user-generated content to static sites like reviews, comments and ratings**\r\n\r\n[Staticman Rating Demo](http://popcorn.staticman.net/)\r\n"},"comment":{"url":"https://api.github.com/repos/netlify/netlify-cms/issues/comments/376692788","html_url":"https://github.com/netlify/netlify-cms/issues/1193#issuecomment-376692788","issue_url":"https://api.github.com/repos/netlify/netlify-cms/issues/1193","id":376692788,"user":{"login":"erquhart","id":2112202,"avatar_url":"https://avatars3.githubusercontent.com/u/2112202?v=4","gravatar_id":"","url":"https://api.github.com/users/erquhart","html_url":"https://github.com/erquhart","followers_url":"https://api.github.com/users/erquhart/followers","following_url":"https://api.github.com/users/erquhart/following{/other_user}","gists_url":"https://api.github.com/users/erquhart/gists{/gist_id}","starred_url":"https://api.github.com/users/erquhart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/erquhart/subscriptions","organizations_url":"https://api.github.com/users/erquhart/orgs","repos_url":"https://api.github.com/users/erquhart/repos","events_url":"https://api.github.com/users/erquhart/events{/privacy}","received_events_url":"https://api.github.com/users/erquhart/received_events","type":"User","site_admin":false},"created_at":"2018-03-27T22:11:22Z","updated_at":"2018-03-27T22:11:22Z","author_association":"MEMBER","body":"This request seems small, but it has major implications that I'm pretty excited about. Here's why.\r\n\r\nStaticman comment moderation happens via pull requests, the same method we're currently using for the editorial workflow. This is going to become a common pattern as git based projects embrace the JAMstack moving forward. That said, the editorial workflow interface isn't ideal for comments for a few reasons:\r\n\r\n* Ideally, you'd burn through a bunch of comment approvals and then merge them all at once, in a single build. The editorial workflow produces a commit per item, which would result in a crazy number of superfluous build requests for sites with any volume.\r\n* There should be a way to separate comments from different parts of a site, whereas the editorial workflow combines everything into one view.\r\n* The editorial workflow is a kanban board, and would likely prove cumbersome for comment moderation.\r\n\r\nThe point is, it should be possible to create entire new views within Netlify CMS, and to have full access to all available data from within those views. This would enable a Staticman plugin to be created with an ideal comment moderation interface and the ability to interact with pull requests as it sees fit.\r\n\r\n### Netlify CMS as a platform\r\nThis is a precursor to a more detailed writeup that I'll get together at some point, but I thought I'd drop a preview here:\r\n\r\n**Every view within Netlify CMS, including the collections view and the editor, should be built as an extension.**\r\n\r\nWe're just scratching the surface of what can be done on the JAMstack, and Netlify CMS is in position to make all of it user editable, so long as we give the community something to build on. If everything is an extension, and a shared library of UI components is available for continuity, we could make it straightforward to create a dedicated comment moderation view.\r\n\r\nSo sort of a good news/bad news thing. Good news is, we should definitely support staticman and tools like it, and I believe we're going to. Not as good news is that it's going to take some time. I'll link back to this ticket when a real write up is in place for tracking."}}
{"actor":{"display_login":"erquhart"}}