Closed taoeffect closed 8 years ago
There are quite a few options for commenting systems. The two main contenders seem to be Disqus and Discourse.
There's also isso, which I'll look into.
Awesome! Thanks for that beautiful comparison. Open source + self-hosting is the way to go! 😄
If you think Isso might be better than Discourse I'd love to hear. :)
Also, as per your request for a reminder: make the side-nav bar TOC thing an optional per-post setting
OK, see my comment here: https://github.com/okTurtles/groupincome.org/issues/11#issuecomment-226054535
Per that, I'm really starting to have second thoughts as to the wisdom of using a static-site generator for a blog.
Here are two posts giving strong reasons to stick with WP for now. I'll summarize the points that jumped out at me (plus other ones that I thought of):
Unless you are cool with it, I don't want to just throw out all the amazing work you've put into this so far.
So some ways forward I see (and feel free to suggest more), include:
Thoughts?
Pros (of Option 2):
Cons (of Option 2):
OTOH, I honestly don't consider this wasted work, as:
Some of the posts' anti-static points are irrelevant for our purposes, but you mentioned the relevant ones: multiple authors & comments. And sunk cost.
Multiple Authors Multiple authors is definitely easier on WP. 👍 (Gitlab has more fine-grained permissions than Github, but they don't seem to help here.)
Comments
WP's Akismet is better at spam protection
Akismet is impressive, but it might be on par with Discourse for spam protection. Some sites have zero spam with Discourse, without site-owner comment moderation. Discourse gives mod privileges to all users.
Discourse has a high memory requirement (1GB!), so SHWPC sounds better for now, but we can keep Discourse in mind at least to see what features we'd like to implement. [Note: if we switch to WP but want Discourse after all, there's a WP Discourse plugin we can try out.]
Pairing blog comments & forum threads is a great feature. We don't necessarily need Discourse to do this, but it's a feature we should implement.
Sunk Cost Some of the work from the static site will carry over to WP just fine -- feature wishlist, picking a theme we like, customizing a theme that's close, etc. We can also use the current static site until WP is live. If WP works better, I'm fine with switching from hexo to WP.
Conclusion WP is the best option for multiple authors, and a good option for self-hosted comments. If you think it will work out better, I'm fine with switching from hexo to WP. Whichever we choose, we should tie the blog comments to the forum, à la Discourse.
Some of the work from the static site will carry over to WP just fine -- picking a theme we like, customizing a theme that's close, etc. We can also use the current static site until WP is live. If WP works better, I'm fine with switching from hexo to WP.
Awesome, glad to hear that and sorry again for not thinking this through enough before. The earlier we notice these kinds of design issues the less of an issue they become later on. I think we caught this one reasonably early enough. :)
WP is the best option for multiple authors, and a good option for self-hosted comments. If you think it will work out better, I'm fine with switching from hexo to WP. Whichever we choose, we should tie the blog comments to the forum, à la Discourse.
Thinking this through some more, while it's easy to code it to read & display comments from our forums, it's much more difficult to code it to post to them from the static site; sufficiently so that I think just going with SHWPC is the way to go.
So, as far as next-steps, let's do this (unless you see any issues):
https://fixingtao.com/2016/05/gregs-list-of-cool-companies-that-pledge-to-never-advertise-on-twitter/
(obv. domain not for fixingtao but for groupincome)I'll launch the static site and we'll move to WP shortly after; exporting & importing comments as appropriate.
Blog entries with some third-party commenting system (yes I know...) that at least allows exporting commentsDisqus commentsyear/month/day/title
permalinks