The weak wait for the opportunity, the strong make the opportunity ✨.

1 introduction

After setting up the blog yesterday, IT occurred to me what I should do if I had an old friend to interact with me 😶(for those who don’t know how to set up a blog read my last post). I went to fluid’s documentation and did a search for information about blog comments at 👍.

2. Comment on system selection

The documentation clearly states what you should be aware of if you want to use blog comments, and I’m quoting the address here.

Since the author said that domestic users recommended Valine or Utterances, I chose one of the two. Below are screenshots of both reviews.

Utterances 👆Valine 👆

In terms of appearance level and practicality, I chose Utterances because I think her style is better. And you don’t have to fill in the user information and url as Valine does. You can just log in with your GitHub account at ✨.

configuration

Once the selection is made, we modify the configuration file based on the documentation provided by the author and our configuration file, _config.fluid. Yml.

After the configuration file is configured, let’s execute ithexo sCommand to see if there is a similar one under your articlegithub IssueThe comments. I naively thought this was the end. But when I did comment, he got it wrong. It looks like this.

The repository you configured is not boundUtterancesUnbind if you want to use Utterances. Next clickinstall app. The binding installation page is displayed.

Click on theinstallIn the next step, it will ask you to bind all libraries under your nameUtterancesOr just bind to a fixed library, we select our own blog and clickinstallAfter that, you will be asked to input the Github password. We will input the correct password correctly.Then we go back to our blog and comment again and we’ll find that we’re done 🎁.

extension

In fact, the user will make an Issue under the bound repository after actually commenting.

Close or reply to give you free play 🎁.

If you are careful, you may find that I just commented on the Issue. Why do I default the path and article name as the title of the comment and it is still garbled? 🎭 There are two solutions at this point.

• The title of the article is in Chinese.
• Modifying a Configuration File

How do I modify the configuration file? Blog Post ↔️ Issue Mapping translates to article and Issue Mapping. I translated it into something like this.

We select the third article title and page title that does not contain the path this isutterancThe code below the official website will change accordingly.

Yml file, change the “issue-term” to “title”, and you will find that 🎉 is not garbled.

conclusion

At the beginning thought that the comment is particularly simple to modify a configuration can be, and later found that his carelessness did not flash 😕. There’s not a lot of it on the Internet, but I just sort of figured it out a little bit with Google Translate. Fortunately, the fluid and Utterances authors’ documentation is more detailed. See you next time at 🏃♂️.