From 9129b07d2f7ea9df3c59a92a16aa2e0592cb2e76 Mon Sep 17 00:00:00 2001 From: Robert Kaussow Date: Sat, 10 Apr 2021 13:06:07 +0200 Subject: [PATCH] add toc to dictionary --- .dictionary | 1 + exampleSite/content/shortcodes/toc.md | 4 ---- exampleSite/content/usage/code-blocks.md | 4 ---- exampleSite/content/usage/configuration.md | 4 ---- exampleSite/content/usage/getting-started.md | 4 ---- exampleSite/content/usage/icons.md | 4 ---- exampleSite/content/usage/menus.md | 4 ---- 7 files changed, 1 insertion(+), 24 deletions(-) diff --git a/.dictionary b/.dictionary index 606e2fe..9e35787 100644 --- a/.dictionary +++ b/.dictionary @@ -4,6 +4,7 @@ Shpak (S|s)hortcode[s]? hugo-book ToC +toc macOS SVG HC-primary diff --git a/exampleSite/content/shortcodes/toc.md b/exampleSite/content/shortcodes/toc.md index 15fdada..4911001 100644 --- a/exampleSite/content/shortcodes/toc.md +++ b/exampleSite/content/shortcodes/toc.md @@ -4,12 +4,8 @@ Simple wrapper to generate a page Table of Content from a shortcode. {{}} ``` - - {{< toc >}} - - ## Level 1 Dolor sit, sumo unique argument um no. Gracie nominal id xiv. Romanesque acclimates investiture. Ornateness bland it ex enc, est yeti am bongo detract re. Pro ad prompts feud gait, quid exercise emeritus bis e. In pro quints consequent, denim fastidious copious quo ad. Stet probates in duo. diff --git a/exampleSite/content/usage/code-blocks.md b/exampleSite/content/usage/code-blocks.md index bf1d12c..856b420 100644 --- a/exampleSite/content/usage/code-blocks.md +++ b/exampleSite/content/usage/code-blocks.md @@ -1,11 +1,7 @@ There are multiple ways to add code blocks. Most of them works out of the box only the Hugo shortcode `` need some configuration to work properly. - - {{< toc >}} - - ## Inline code To display an inline shortcode use single quotes: diff --git a/exampleSite/content/usage/configuration.md b/exampleSite/content/usage/configuration.md index 6c573d7..4bb0e74 100644 --- a/exampleSite/content/usage/configuration.md +++ b/exampleSite/content/usage/configuration.md @@ -3,12 +3,8 @@ title: Configuration weight: -10 --- - - {{< toc >}} - - ## Site configuration {{< tabs "site-config" >}} diff --git a/exampleSite/content/usage/getting-started.md b/exampleSite/content/usage/getting-started.md index 20fa1f8..b29f821 100644 --- a/exampleSite/content/usage/getting-started.md +++ b/exampleSite/content/usage/getting-started.md @@ -5,12 +5,8 @@ weight: -20 This page tells you how to get started with the Geekdoc theme, including installation and basic configuration. - - {{< toc >}} - - ## Install requirements You need a recent version of Hugo for local builds and previews of sites that use Geekdoc. As we are using [gulp](https://gulpjs.com/) as pre-processor the normal version of Hugo is sufficient. If you prefer the extended version of Hugo anyway this will work as well. For comprehensive Hugo documentation, see [gohugo.io](https://gohugo.io/documentation/). diff --git a/exampleSite/content/usage/icons.md b/exampleSite/content/usage/icons.md index e8b2d09..ecef1ae 100644 --- a/exampleSite/content/usage/icons.md +++ b/exampleSite/content/usage/icons.md @@ -2,12 +2,8 @@ title: Icons --- - - {{< toc >}} - - ## Custom icons The only supported source for custom icons are SVG sprites. Some icon frameworks provides ready to use sprites e.g. FontAwesome. If the framework don't provide sprites, you can create your own from raw SVG icons. There are a lot of tools available to create sprites, please choose one that fits your need. One solution could be [svgsprit.es](https://svgsprit.es/). diff --git a/exampleSite/content/usage/menus.md b/exampleSite/content/usage/menus.md index 5d54a5d..3efa152 100644 --- a/exampleSite/content/usage/menus.md +++ b/exampleSite/content/usage/menus.md @@ -1,11 +1,7 @@ The theme supports two different kinds of menus. File-tree menu is the default one and does not require further configuration to work. If you want full control about your menu the bundle menu is a powerful option to accomplish it. - - {{< toc >}} - - ## File-tree menu As the name already suggests, the file tree menu builds a menu from the file system structure of the content folder. By default, areas and subareas are sorted alphabetically by the title of the pages. To manipulate the order the `weight` parameter in a page [front matter](https://gohugo.io/content-management/front-matter/) can be used. To structure your content folder you have to use [page bundles](https://gohugo.io/content-management/organization/#page-bundles), single files are **not** supported. Hugo will render build single files in the content folder just fine but it will not be added to the menu.