Reworked examples in getting started guide

This commit is contained in:
squidfunk 2020-04-05 13:23:13 +02:00
parent 85fc057b2f
commit db6e133648

View File

@ -150,12 +150,14 @@ following command:
mkdocs serve mkdocs serve
``` ```
Point your browser to [http://localhost:8000][11] and your documentation should Point your browser to http://localhost:8000 and your documentation should great
great you in a new look. If you're starting from scratch, the following you in a new look. If you're starting from scratch, the following configuration
configuration can be used as a starting point: can be used as a starting point:
??? summary "Example configuration" ??? summary "Example configuration"
This is an excerpt from the [`mkdocs.yml`][11] used to render these pages:
``` yaml ``` yaml
# Project information # Project information
site_name: Material for MkDocs site_name: Material for MkDocs
@ -205,7 +207,7 @@ configuration can be used as a starting point:
permalink: true permalink: true
``` ```
[11]: http://localhost:8000 [11]: https://github.com/squidfunk/mkdocs-material/blob/master/mkdocs.yml
### Feature flags ### Feature flags
@ -246,13 +248,14 @@ Note that all *top-level pages* (i.e. all top-level entries that directly refer
to an `*.md` file) defined inside the `nav` entry of `mkdocs.yml` will be to an `*.md` file) defined inside the `nav` entry of `mkdocs.yml` will be
grouped under the first tab which will receive the title of the first page. grouped under the first tab which will receive the title of the first page.
If you want to maintain absolute control over the navigation bar, you can opt This means that there will effectively be no collapsible subsections for the
in to group all top-level pages under one entry (so all top-level entries have first tab, as each subsection is rendered as another tab. If you want more
subentries now). This way you can have nested navigation items in conjunction fine-grained control, i.e., collapsible subsections for the first tab, you can
with tabs, as nesting works as expected from the second level on when tabs are move all *top-level pages into a subsection*, so that the top-level is entirely
enabled. Keep in mind that mobile navigation isn't affected by tabs, however, made up of subsections. Note that tabs are only shown for larger screens, so
which means that your top-level entries correspond to top-level mobile make sure that navigation is plausible on mobile devices.
navigation items.
As an example, see the [`mkdocs.yml`][11] used to render these pages.
### Language ### Language