feat: add commento.io frontend configuration

[NITHINSPACETIME]

fixes #875

Added a commentoFrontend parameter to the config to make setting up self-hosted instances a lot easier for people ig.

If you set commentoFrontend = "https://your-instance.com", it automatically points the script source there. If it's not set, it just falls back to the default CDN like before.

Also added a commented-out example in params.toml so people know it's there.

[davidsneighbour]

I am actually in the process of removing this. I want instead add a layouts/_partials/comments.html that is empty by default and then in the docs have explanations for any comment system.

Regarding the code: I find my solution (full path to commento.js) easier for more common users because they don't need to think about what URL to add and it won't come to issues with trailing slashes or paths. The commento.js file might have a different filename. If a person wants to configure they configure that one full path to the JavaScript file instead of a domain and a path.

Lastly: your comment in the configuration is in site.Params.ananke.home.commentoFrontend and NOT site.Params.commentoFrontend.

I'll keep this open and we'll move it to the docs once that is implemented.

[NITHINSPACETIME]

I am actually in the process of removing this. I want instead add a layouts/_partials/comments.html that is empty by default and then in the docs have explanations for any comment system.

Regarding the code: I find my solution (full path to commento.js) easier for more common users because they don't need to think about what URL to add and it won't come to issues with trailing slashes or paths. The commento.js file might have a different filename. If a person wants to configure they configure that one full path to the JavaScript file instead of a domain and a path.

Lastly: your comment in the configuration is in site.Params.ananke.home.commentoFrontend and NOT site.Params.commentoFrontend.

I'll keep this open and we'll move it to the docs once that is implemented.

Ah, good catch on the config location! I've pushed a fix for that just so the PR is clean for reference.

I understand your point about the full path approach being more flexible. I'll leave this open as requested, and you can close it whenever the new comments system is ready. Thanks for the context man!