Make adding Disqus comments to a site easier

[tboutell]

This documentation:

 http://trac.apostrophenow.org/wiki/ManualBlogPlugin

Covers how to add Disqus but it is needlessly complicated. And you have to override big partials which we then can't upgrade without breaking your site.

This is silly, let's fix it. At a minimum we should write (and document!) empty partials with obvious names where all the comment stuff should go, so we can upgrade the blog plugin without breaking your comment-enabled site.

Better yet, those partials should already be populated, with an app.yml check wrapped around them that looks to see if your Disqus ID or whatever it is has been configured yet. I really like that idea.

We could even have it print "set your Disqus ID (see this link for help) or set it to false to remove this message."

This is maybe an hour or two and will really pay dividends.

[johnnyoffline]

Disqus should be enabled and working by default in the sandbox right?

It's much easier to disable / remove something than it is to add it in later. It's also easier to design for it.

I've haven't seen Disqus installed and working, I would be excited to check it out

[tboutell]

Sure, enable it as much as you can... maybe there's a way to use a Disqus test account or something. We don't want to irritate them, but I'm sure they appreciate the exposure. What we can definitely do is have it all stubbed right in and a simple place to set your Disqus API key and light it up and a message explaining the need to do that or expressly disable it. Then people won't miss our comments feature outright (and we'll add it to our own client sites more than we presently do perhaps).

[jake]

This is complete and committed. You now only need to put

aBlog:

disqus_enabled: true
disqus_shortname: yourshortname

into app.yml, and you'll have disqus comments in the blog plugin.

[tboutell]

You are the wind beneath my wings