Workaround for Staticman bug

[VincentTam]

Goal

Provide a workaround for eduardoboucas/staticman#279.

Since I can't open an issue, I've made this PR instead. The main point is to use an alternative API instance instead of the official one to avoid unexpected service interruption caused by unnotified updates on the official one. You may choose either self-hosting your own instance or use an existing one.

• self-hosting guide from Data Science Blog
• use an existing API: see below

P.S. I've authored daattali/beautiful-jekyll#440, which is essentially a port of Minimal Mistake's Staticman integration, but defaulting to @staticmanlab that I've created.

👷‍♂️ Staticman configurations with screenshots

📧 Please don't hesitate to ping me on GitHub/GitLab/leave a comment on my blog/send me an email to ask for help.

1. 🏁 Invite @staticmanlab as a collaborator to your repository (by going to your repository Settings page, navigate to the Collaborators tab).
   
   Image short link: https://git.io/fjZPx

2. ☑️ Help @staticmanlab accept the invitation by going to

    https://staticman3.herokuapp.com/v3/connect/github/<username>/<repo-name>
   

   In your case, that's

    https://staticman3.herokuapp.com/v3/connect/github/PGui/pgui.github.io
   

   
   Figure: image showing setup for my fork of this theme
   Image short link: https://git.io/fjZXG

   
   Figure: @staticmanlab invited to GitHub repo
   Image short link: https://git.io/fjZXZ

3. ✍️ Fill in your repository and branch in the Staticman section of _config.yml.

    # Staticman support 
    staticman: 
      ...
      endpoint   : # I've edited that for you, but feel free to change it to your favorite one.
      ...

4. 📝 Start commenting.