@Qwxlea @kaushalmodi for lifewithalacrity.com I used webmention.herokuapp.com (It shows them with js) see http://www.lifewithalacrity.com/2016/04/the-path-to-self-soverereign-identity.html for a post with mentions. That's a decent starting point before you move to building them into the pages
There are multiple aspects to "Indiewebifying" your site.
@kevinmarks: Correct me where I am wrong below.
1. #IndieAuth: You have a website be *you*, YOUR identity. That's where rel=me comes in. For lazy folks like me, I identify myself and link that to my GitHub profile.
2. #Microformats2: This makes your web pages parseable by the Webmention endpoints (like webmention.io, that heroku app, etc.)
3. #Webmention endpoint setup: This is where you start receiving webmentions. PHP folks are known to create their own end points and host them. I use #Netlify that can host only static sites (no PHP scripts, etc.). For folks like me (who don't have experience with PHP, etc. and cannot host such scripts), webmention.io is a boon!
With that set up, you can start receiving wm's, *but not yet display anywhere*. You can access them by browsing to webmention.io dashboard.
4. Showing Webmentions: The popular way to to embed JS/iframe to show webmentions from the wm.io or heroku app wm endpoints. I did not want to use JS. So I developed this JSON parsing flow using #Hugo that I mentioned earlier.
5. Sending Webmentions: The easiest way is https://telegraph.p3k.io/. You basically mention where you are sending the wm from and to whom. For my site, I use this Go template to auto-set the "from" part to the page URL.
There's lot more in the #Indieweb world which is out of my reach and understanding (micropub, microsub, etc. which requires you to deploy on servers allowing scripts to run; Netlify won't work.)
The indieweb IRC is very helpful.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!