Most static websites won’t include a comment section unless they use a third-party service. That’s because they can’t use server-side scripting with whatever host they’re using. I can use everything with my web host, though I choose not to. I can use PHP for form processing even when I choose not to use it for anything else.
The main reason is I want to. I don’t like using a third-party service because my visitors don’t like using it. Even though I have it set up so a visitor doesn’t have to login to comment, most people overlook that option.
Another reason is that third-party comments aren’t part of my content. They’re loaded separately and their content belongs to the third party, technologically speaking. The search engines don’t see them as belonging to me, even if they really do.
I can’t return to WordPress native comments because that requires a database. I’m using a database where the original data resides but not on the server itself. I have to do it differently.
There isn’t any way to magically add native comments to static files. I have to use a four-step process:
While this may seem like a lot of work, it really isn’t. I already sort of complete the last two steps when I write or correct an article. I have my publishing and editing routines down to a science.
There’s one distinct advantage to doing things this way. Comment spam can’t slip through. No how, no way. And I don’t have to worry about forms that just stop working.
Creating the comment form (and changing the comment form on the contact page to replace Formspree) is the easy part. Writing the script to process the form isn’t too difficult either. Both take time and I have to test locally before going live. Not only that, but I have to convert the existing Disqus comments to native comments before I can go live.
It’s not going to happen overnight. In fact, it’ll probably take more than a few days because I get interrupted a lot.