README.md in jekyll-nagymaros-2.2.0 vs README.md in jekyll-nagymaros-3.0.0

@@ -1,13 +1,13 @@
 # jekyll-nagymaros
 
 Nagymaros is a [Jekyll](https://jekyllrb.com) theme designed for conferences, workshops, meetings, and similar events. It has a simple and intuitive structure featuring four pages that provide key information about the event:
 
-- An index, meant for basic details and links to external sources, such as submission systems.
+- An index for alerts, basic details, and links to external sources such as submission systems.
 - A program, allowing for single or multi-day schedules and color-coded event categories.
 - A map of conference locations, customizable with markers, areas, and tooltips.
-- An alphabetical list of contributors, with optional roles and email addresses.
+- An alphabetical list of participants, with optional roles, affiliations, and email addresses.
 
 The theme is based on [Bootstrap 5](https://getbootstrap.com/), which makes it mobile-first and fully responsive. Body text is set in Inter, a clean sans-serif typeface that guarantees readability at small screen sizes. A slab-serif typeface, Zilla Slab, is used instead in display headings. The layout is adapted from [jekyll-conference-theme](https://github.com/DigitaleGesellschaft/jekyll-theme-conference) and remains quite similar to it, but compared to this theme, Nagymaros aims to be simpler and easier to customize.
 
 See the [demo](https://piazzai.github.io/jekyll-nagymaros/) to find out what the theme looks like.
 
@@ -21,19 +21,19 @@
 
 ```bash
 .
 ├── 404.md
 ├── _config.yml
-├── contributors.md
 ├── _data
-│   ├── contributors.yml
 │   ├── index.yml
-│   ├── locations.yml
+│   ├── map.yml
+│   ├── participants.yml
 │   └── program.yml
 ├── Gemfile
 ├── index.md
-├── locations.md
+├── map.md
+├── participants.md
 └── program.md
 
 ```
 
 To install the theme, you can then add this line to your `Gemfile`:
@@ -59,12 +59,16 @@
 
 To customize hidden files, you can create new files with the same names and paths. For example, to change the layout of the index page, you can create a `_layouts` folder and a file `index.html` within this folder that contains your custom code. During build, Jekyll will give priority to your files over the theme's.
 
 ## Usage
 
-Core customization occurs in `_config.yml`. Aside from the usual configuration variables, you can set a value for `copyright`, which corresponds to the name of the copyright holder in the notice within the theme's footer. If no value is provided for this variable, the whole copyright notice is suppressed (this is the default). Finally, you can set a value for `indexing`, which tells search engine crawlers whether to index your site. The default value is `false`, and in this case the following code is included in the head of every page:
+Core customization occurs in `_config.yml`. Aside from the usual configuration variables, you can set a value for `home`, which will determine the destination of the site title button in the header, as well as the return link from the 404 page. Only use this if you want these buttons to lead somewhere different than the index.
 
+Next, you can set a value for `copyright`, which corresponds to the name of the copyright holder in the notice within the theme's footer. If no value is provided for this variable, the whole copyright notice is suppressed (default).
+
+Finally, you can set a value for `indexing`, which tells search engine crawlers whether to index your site. The default value is `false`, and in this case the following code is included in the head of every page:
+
 ```html
 <meta name="robots" content="none">
 ```
 
 If you set the value to `true`, however, the above code will not be included, crawlers will be allowed to index your site, and Jekyll will populate the head of every page with SEO tags through the `jekyll-seo-tag` plugin.
@@ -73,10 +77,10 @@
 
 The order of appearance of pages in the theme's navigation bar is determined by the value of `navorder` set in each page's front matter. For example, setting `navorder: 1` will make the page appear first in the list. Note that a page will only appear in the navigation bar if the `navorder` variable is set, so it is possible to hide some pages from navigation simply by not giving this variable a value.
 
 Customizing the CSS is possible by creating a file `_sass/_custom.scss`. You can use this both to define new styles or to overwrite the theme's defaults. The file will be automatically compiled during build.
 
-For convenience, customization of the theme's color scheme is also possible via YAML. In this case, create a file called `skin.yml` in your `_data` folder and assign new colors from the [Open Color](https://yeun.github.io/open-color) library to various HTML elements using the color-number convention. Here is an example:
+For convenience, customization of the theme's color scheme is also possible via YAML. In this case, create a file `_data/skin.yml` and assign new colors from the [Open Color](https://yeun.github.io/open-color) library to various HTML elements. Make sure to stick to the library's color-number naming convention. Here is an example:
 
 ```yaml
 a:
   color: blue-7         # links
   hover: blue-9         # links when hovering