README.md in sutty-minima-2.5.0 vs README.md in sutty-minima-2.5.1

- old
+ new

@@ -116,11 +116,11 @@ The site's default CSS has now moved to a new place within the gem itself, [`assets/css/style.scss`](assets/css/style.scss). In Minima 3.0, if you only need to customize the colors of the theme, refer to the subsequent section on skins. To have your *CSS overrides* in sync with upstream changes released in future versions, you can collect all your overrides for the Sass variables and mixins inside a sass file placed at `_sass/minima/custom-variables.scss` and all other overrides inside a sass file -placed at path `_sass/minima/custom.scss`. +placed at path `_sass/minima/custom-styles.scss`. You need not maintain entire partial(s) at the site's source just to override a few styles. However, your stylesheet's primary source (`assets/css/style.scss`) should contain the following: - Front matter dashes at the very beginning (can be empty). @@ -214,23 +214,23 @@ ### Enabling comments (via Disqus) Optionally, if you have a Disqus account, you can tell Jekyll to use it to show a comments section below each post. -To enable it, add the following lines to your Jekyll site: +:warning: `url`, e.g. `https://example.com`, must be set in you config file for Disqus to work. +To enable it, after setting the url field, you also need to add the following lines to your Jekyll site: + ```yaml disqus: shortname: my_disqus_shortname ``` You can find out more about Disqus' shortnames [here](https://help.disqus.com/installation/whats-a-shortname). Comments are enabled by default and will only appear in production, i.e., `JEKYLL_ENV=production` If you don't want to display comments for a particular post you can disable them by adding `comments: false` to that post's YAML Front Matter. - -:warning: `url`, e.g. `https://example.com`, must be set in you config file for Disqus to work. ### Author Metadata From `Minima-3.0` onwards, `site.author` is expected to be a mapping of attributes instead of a simple scalar value: