diff --git a/_includes/nav.html b/_includes/nav.html index dba0dea..170fcfb 100644 --- a/_includes/nav.html +++ b/_includes/nav.html @@ -1,7 +1,8 @@ diff --git a/_sass/code.scss b/_sass/code.scss index 69a4ef8..f29a97c 100644 --- a/_sass/code.scss +++ b/_sass/code.scss @@ -11,7 +11,7 @@ code { border-radius: $border-radius; } -.highlight { +pre.highlight { padding: $sp-3; margin-bottom: 0; background-color: $code-background-color; diff --git a/_sass/content.scss b/_sass/content.scss index 1dd5256..46fc294 100644 --- a/_sass/content.scss +++ b/_sass/content.scss @@ -4,6 +4,12 @@ // stylelint-disable selector-no-type, max-nesting-depth, selector-max-compound-selectors, selector-max-type .page-content { + a { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; + } + ul, ol { padding-left: 1.5em; diff --git a/docs/configuration.md b/docs/configuration.md index c2f867b..e092418 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -6,7 +6,7 @@ nav_order: 2 # Configuration -Just the Docs has some specific configuration parameters that can be definied in your Jekyll site's `config.yml` file. +Just the Docs has some specific configuration parameters that can be definied in your Jekyll site's `_config.yml` file. ## Search enabled diff --git a/docs/navigation-structure.md b/docs/navigation-structure.md index 8114321..eab6e73 100644 --- a/docs/navigation-structure.md +++ b/docs/navigation-structure.md @@ -27,6 +27,8 @@ By default, all pages will appear as top level pages in the main nav. To specify a page order, use the `nav_order` variable in your pages' YAML front matter. +#### Example +{: .no_toc } ```yaml --- layout: default @@ -35,6 +37,20 @@ nav_order: 4 --- ``` +### Excluding pages + +For specific pages that you do not wish to include in the main navigation, e.g. a 404 page. Use the `nav_exclude: true` parameter in the YAML front matter for that page. + +#### Example +{: .no_toc } +```yaml +--- +layout: default +title: 404 +nav_exclude: true +--- +``` + ### Pages with children Sometimes you will want to create a page with many children (a section). To accomplish this you need to a few things. First, it is recommended that you keep pages that are related in a directory together... For example, in these docs, we keep all of the written documentation in the `./docs` directory and each of the sections in subdirectories like `./docs/ui-components` and `./docs/utilities`. This gives is an organization like: @@ -75,12 +91,14 @@ On the parent pages, add 3 YAML front matter variables: {: .no_toc } ```yaml +--- layout: default title: UI Components nav_order: 2 has_children: true parent: UI Components permalink: /ui-components +--- ``` Here we're setting up the UI Components landing page that is available at `/ui-components`, has children and is ordered second in the main nav. @@ -92,10 +110,12 @@ On child pages, simply set the `parent:` YAML front matter to whatever the paren #### Example {: .no_toc } ```yaml +--- layout: default title: Buttons parent: UI Components nav_order: 2 +--- ``` The Buttons page appears a child of UI Components and appears second in the UI Components section. diff --git a/docs/ui-components/buttons.md b/docs/ui-components/buttons.md index 849071d..8da7729 100644 --- a/docs/ui-components/buttons.md +++ b/docs/ui-components/buttons.md @@ -21,7 +21,6 @@ nav_order: 2 ### Links that look like buttons