hugopoi
/
cupper-hugo-theme
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

clarity on subsections

This commit is contained in:
Heydon Pickering 2017-09-12 15:19:26 +01:00
parent f6252466c7
commit b84e948479
4 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/patterns/writing/project-structure.md
View File

@ -35,8 +35,7 @@ You may have noticed that this site's navigation is divided partly into subsecti
* tooltips.md * tooltips.md
{{% /fileTree %}} {{% /fileTree %}}
{{% note %}} Subfolders like `/popups` must each have an `_index.md` file. This file doesn't need any content except the TOML metadata defining the title (name) of that subsection:
Note that subfolders like `/popups` must each have an `_index.md` file. This file doesn't need any content except the TOML metadata defining the title (name) of that subsection:
``` ```
+++ +++
@ -44,9 +43,10 @@ title = "Popups"
+++ +++
``` ```
For each subfolder you create, you must also create one of these `_index.md` files. The `/patterns` folder itself does not need indexing explicitly in this way. This title is what labels the subsection in the navigation (examples: "Writing" and "Media" for **Infusion**'s documentation). For each subfolder you create, you must also create one of these `_index.md` files. The `/patterns` folder itself does not need one, however.
**Infusion** does not currently support _sub_-subsections. {{% note %}}
**Infusion** does not currently support _sub_-subsections. You can only create child folders under `/patterns`.
{{% /note %}} {{% /note %}}
Now that you know where to put everything, it's time to talk about how to actually write individual patterns. Don't worry, it's pretty straightforward. Turn to {{% pattern "Markdown & metadata" %}}. Now that you know where to put everything, it's time to talk about how to actually write individual patterns. Don't worry, it's pretty straightforward. Turn to {{% pattern "Markdown & metadata" %}}.

16
docs/patterns/writing/project-structure/index.html
View File

@ -462,21 +462,21 @@
</div> </div>
<aside aria-label="note" class="note"> <p>Subfolders like <code>/popups</code> must each have an <code>_index.md</code> file. This file doesn&rsquo;t need any content except the TOML metadata defining the title (name) of that subsection:</p>
<div>
<svg aria-hidden="true" viewBox="0 0 41.667306 41.66729" focusable="false">
<use xlink:href="#info"></use>
</svg>
<p>Note that subfolders like <code>/popups</code> must each have an <code>_index.md</code> file. This file doesn&rsquo;t need any content except the TOML metadata defining the title (name) of that subsection:</p>
<pre><code>+++ <pre><code>+++
title = &quot;Popups&quot; title = &quot;Popups&quot;
+++ +++
</code></pre> </code></pre>
<p>For each subfolder you create, you must also create one of these <code>_index.md</code> files. The <code>/patterns</code> folder itself does not need indexing explicitly in this way.</p> <p>This title is what labels the subsection in the navigation (examples: &ldquo;Writing&rdquo; and &ldquo;Media&rdquo; for <strong>Infusion</strong>&rsquo;s documentation). For each subfolder you create, you must also create one of these <code>_index.md</code> files. The <code>/patterns</code> folder itself does not need one, however.</p>
<p><strong>Infusion</strong> does not currently support <em>sub</em>-subsections.</p> <aside aria-label="note" class="note">
<div>
<svg aria-hidden="true" viewBox="0 0 41.667306 41.66729" focusable="false">
<use xlink:href="#info"></use>
</svg>
<p><strong>Infusion</strong> does not currently support <em>sub</em>-subsections. You can only create child folders under <code>/patterns</code>.</p>
</div> </div>
</aside> </aside>

16
docs/print-version/index.html
View File

@ -783,21 +783,21 @@ theme = "infusion"
</div> </div>
<aside aria-label="note" class="note"> <p>Subfolders like <code>/popups</code> must each have an <code>_index.md</code> file. This file doesn&rsquo;t need any content except the TOML metadata defining the title (name) of that subsection:</p>
<div>
<svg aria-hidden="true" viewBox="0 0 41.667306 41.66729" focusable="false">
<use xlink:href="#info"></use>
</svg>
<p>Note that subfolders like <code>/popups</code> must each have an <code>_index.md</code> file. This file doesn&rsquo;t need any content except the TOML metadata defining the title (name) of that subsection:</p>
<pre><code>+++ <pre><code>+++
title = &quot;Popups&quot; title = &quot;Popups&quot;
+++ +++
</code></pre> </code></pre>
<p>For each subfolder you create, you must also create one of these <code>_index.md</code> files. The <code>/patterns</code> folder itself does not need indexing explicitly in this way.</p> <p>This title is what labels the subsection in the navigation (examples: &ldquo;Writing&rdquo; and &ldquo;Media&rdquo; for <strong>Infusion</strong>&rsquo;s documentation). For each subfolder you create, you must also create one of these <code>_index.md</code> files. The <code>/patterns</code> folder itself does not need one, however.</p>
<p><strong>Infusion</strong> does not currently support <em>sub</em>-subsections.</p> <aside aria-label="note" class="note">
<div>
<svg aria-hidden="true" viewBox="0 0 41.667306 41.66729" focusable="false">
<use xlink:href="#info"></use>
</svg>
<p><strong>Infusion</strong> does not currently support <em>sub</em>-subsections. You can only create child folders under <code>/patterns</code>.</p>
</div> </div>
</aside> </aside>

2
docs/service-worker.js
View File

File diff suppressed because one or more lines are too long