|
@@ -11,6 +11,18 @@
|
|
|
<atom:link href="https://heydon.github.io/infusion/index.xml" rel="self" type="application/rss+xml" />
|
|
<atom:link href="https://heydon.github.io/infusion/index.xml" rel="self" type="application/rss+xml" />
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
+ <item>
|
|
|
|
|
+ <title>Code blocks</title>
|
|
|
|
|
+ <link>https://heydon.github.io/infusion/patterns/coding/code-blocks/</link>
|
|
|
|
|
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
|
+
|
|
|
|
|
+ <guid>https://heydon.github.io/infusion/patterns/coding/code-blocks/</guid>
|
|
|
|
|
+ <description>Markdown already supports code samples both inline (using single backticks like `some code here`) and in blocks. Infusion will syntax highlight HTML, CSS, and JavaScript if you provide the correct language in the formulation of the block.
|
|
|
|
|
+So, this&hellip;
|
|
|
|
|
+```html &lt;button aria-pressed="false"toggle me&lt;/button ``` &hellip; will result in this:
|
|
|
|
|
+&lt;button aria-pressed=&quot;false&quot;&gt;toggle me&lt;/button&gt; Note that the syntax highlighting uses a greyscale theme. Infusion is careful not to use color as part of its own design, because these colors may clash with those of the design being illustrated and discussed.</description>
|
|
|
|
|
+ </item>
|
|
|
|
|
+
|
|
|
<item>
|
|
<item>
|
|
|
<title>Library structure</title>
|
|
<title>Library structure</title>
|
|
|
<link>https://heydon.github.io/infusion/patterns/writing/library-structure/</link>
|
|
<link>https://heydon.github.io/infusion/patterns/writing/library-structure/</link>
|
|
@@ -21,6 +33,17 @@
|
|
|
└── content ├── _index.md └── patterns ├── name-of-my-pattern.md └── name-of-my-other-pattern.md /content - This is where all of your content lives. You won&rsquo;t need to visit any other folders very frequently. _index.md — This is the content for your home page. /patterns — This is the folder where individual pattern files are kept.</description>
|
|
└── content ├── _index.md └── patterns ├── name-of-my-pattern.md └── name-of-my-other-pattern.md /content - This is where all of your content lives. You won&rsquo;t need to visit any other folders very frequently. _index.md — This is the content for your home page. /patterns — This is the folder where individual pattern files are kept.</description>
|
|
|
</item>
|
|
</item>
|
|
|
|
|
|
|
|
|
|
+ <item>
|
|
|
|
|
+ <title>CodePen embedding</title>
|
|
|
|
|
+ <link>https://heydon.github.io/infusion/patterns/coding/codepen-embedding/</link>
|
|
|
|
|
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
|
+
|
|
|
|
|
+ <guid>https://heydon.github.io/infusion/patterns/coding/codepen-embedding/</guid>
|
|
|
|
|
+ <description>Sometimes just pictures of the pattern you&rsquo;re documenting aren&rsquo;t enough. Interactive patterns benefit from live demos, so that readers can test their functionality.
|
|
|
|
|
+Infusion offers a couple of ways to do this. The first is by embedding CodePen demos into the content. The codePen shortcode takes just one argument: the codePen&rsquo;s ID.
|
|
|
|
|
+&#x7b;{% codePen VpVNKW %}} This will embed the identified codePen into the content wherever you placed the shortcode, with the result view showing by default:</description>
|
|
|
|
|
+ </item>
|
|
|
|
|
+
|
|
|
<item>
|
|
<item>
|
|
|
<title>Markdown & metadata</title>
|
|
<title>Markdown & metadata</title>
|
|
|
<link>https://heydon.github.io/infusion/patterns/writing/markdown-and-metadata/</link>
|
|
<link>https://heydon.github.io/infusion/patterns/writing/markdown-and-metadata/</link>
|
|
@@ -31,6 +54,16 @@
|
|
|
If you&rsquo;re not familiar with writing markdown, there are a number of tutorials available.</description>
|
|
If you&rsquo;re not familiar with writing markdown, there are a number of tutorials available.</description>
|
|
|
</item>
|
|
</item>
|
|
|
|
|
|
|
|
|
|
+ <item>
|
|
|
|
|
+ <title>Writing inline demos</title>
|
|
|
|
|
+ <link>https://heydon.github.io/infusion/patterns/coding/writing-inline-demos/</link>
|
|
|
|
|
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
|
+
|
|
|
|
|
+ <guid>https://heydon.github.io/infusion/patterns/coding/writing-inline-demos/</guid>
|
|
|
|
|
+ <description>There are some issues with CodePen embedding , like them not working offline. They also come with CodePen branding, which will clash with the pattern you&rsquo;re trying to illustrate.
|
|
|
|
|
+Infusion offers another option: a special demo shortcode that allows you to write HTML, CSS, and JavaScript directly into the markdown file. The outputted demo is encapsulated using Shadow DOM, so you don&rsquo;t have to worry about broken styles and global JS.</description>
|
|
|
|
|
+ </item>
|
|
|
|
|
+
|
|
|
<item>
|
|
<item>
|
|
|
<title>Expandable sections</title>
|
|
<title>Expandable sections</title>
|
|
|
<link>https://heydon.github.io/infusion/patterns/writing/expandable-sections/</link>
|
|
<link>https://heydon.github.io/infusion/patterns/writing/expandable-sections/</link>
|
|
@@ -42,35 +75,12 @@ The expandable shortcode takes three parameters:
|
|
|
label — This is the label for the the section heading. level — This is the heading level (e.</description>
|
|
label — This is the label for the the section heading. level — This is the heading level (e.</description>
|
|
|
</item>
|
|
</item>
|
|
|
|
|
|
|
|
- <item>
|
|
|
|
|
- <title>Code blocks</title>
|
|
|
|
|
- <link>https://heydon.github.io/infusion/patterns/code/code-blocks/</link>
|
|
|
|
|
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
|
-
|
|
|
|
|
- <guid>https://heydon.github.io/infusion/patterns/code/code-blocks/</guid>
|
|
|
|
|
- <description>Markdown already supports code samples both inline (using single backticks like `some code here`) and in blocks. Infusion will syntax highlight HTML, CSS, and JavaScript if you provide the correct language in the formulation of the block.
|
|
|
|
|
-So, this&hellip;
|
|
|
|
|
-```html &lt;button aria-pressed="false"toggle me&lt;/button ``` &hellip; will result in this:
|
|
|
|
|
-&lt;button aria-pressed=&quot;false&quot;&gt;toggle me&lt;/button&gt; Note that the syntax highlighting uses a greyscale theme. Infusion is careful not to use color as part of its own design, because these colors may clash with those of the design being illustrated and discussed.</description>
|
|
|
|
|
- </item>
|
|
|
|
|
-
|
|
|
|
|
- <item>
|
|
|
|
|
- <title>CodePen embedding</title>
|
|
|
|
|
- <link>https://heydon.github.io/infusion/patterns/code/codepen-embedding/</link>
|
|
|
|
|
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
|
-
|
|
|
|
|
- <guid>https://heydon.github.io/infusion/patterns/code/codepen-embedding/</guid>
|
|
|
|
|
- <description>Sometimes just pictures of the pattern you&rsquo;re documenting aren&rsquo;t enough. Interactive patterns benefit from live demos, so that readers can test their functionality.
|
|
|
|
|
-Infusion offers a couple of ways to do this. The first is by embedding CodePen demos into the content. The codePen shortcode takes just one argument: the codePen&rsquo;s ID.
|
|
|
|
|
-&#x7b;{% codePen VpVNKW %}} This will embed the identified codePen into the content wherever you placed the shortcode, with the result view showing by default:</description>
|
|
|
|
|
- </item>
|
|
|
|
|
-
|
|
|
|
|
<item>
|
|
<item>
|
|
|
<title>Color palettes</title>
|
|
<title>Color palettes</title>
|
|
|
- <link>https://heydon.github.io/infusion/patterns/code/color-palettes/</link>
|
|
|
|
|
|
|
+ <link>https://heydon.github.io/infusion/patterns/coding/color-palettes/</link>
|
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
|
|
|
|
- <guid>https://heydon.github.io/infusion/patterns/code/color-palettes/</guid>
|
|
|
|
|
|
|
+ <guid>https://heydon.github.io/infusion/patterns/coding/color-palettes/</guid>
|
|
|
<description>There&rsquo;s no reason why your Infusion-powered pattern library has to be all about functionality. You can include style guide-like information such as color palettes too. The colors shortcode makes it easy to exhibit colors and their values together. Just supply a comma-separated list of CSS color values.
|
|
<description>There&rsquo;s no reason why your Infusion-powered pattern library has to be all about functionality. You can include style guide-like information such as color palettes too. The colors shortcode makes it easy to exhibit colors and their values together. Just supply a comma-separated list of CSS color values.
|
|
|
&#x7b;{% colors "#111111, #cccccc, #ffffff" %}} The result is a one row strip showing each color supplied in order. The colors for Infusion are greyscale:</description>
|
|
&#x7b;{% colors "#111111, #cccccc, #ffffff" %}} The result is a one row strip showing each color supplied in order. The colors for Infusion are greyscale:</description>
|
|
|
</item>
|
|
</item>
|
|
@@ -137,15 +147,5 @@ I can reference the &#x7b;{% pattern "Notes & warnings" %}} patt
|
|
|
npm run serve This will serve your working library from localhost:1313 (the exact URL will be determined by what&rsquo;s in your baseURL and will be revealed to you by your terminal). Whenever you make changes to your library&rsquo;s files, the site will automatically rebuild.</description>
|
|
npm run serve This will serve your working library from localhost:1313 (the exact URL will be determined by what&rsquo;s in your baseURL and will be revealed to you by your terminal). Whenever you make changes to your library&rsquo;s files, the site will automatically rebuild.</description>
|
|
|
</item>
|
|
</item>
|
|
|
|
|
|
|
|
- <item>
|
|
|
|
|
- <title>Writing inline demos</title>
|
|
|
|
|
- <link>https://heydon.github.io/infusion/patterns/code/writing-inline-demos/</link>
|
|
|
|
|
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
|
|
|
-
|
|
|
|
|
- <guid>https://heydon.github.io/infusion/patterns/code/writing-inline-demos/</guid>
|
|
|
|
|
- <description>There are some issues with CodePen embedding , like them not working offline. They also come with CodePen branding, which will clash with the pattern you&rsquo;re trying to illustrate.
|
|
|
|
|
-Infusion offers another option: a special demo shortcode that allows you to write HTML, CSS, and JavaScript directly into the markdown file. The outputted demo is encapsulated using Shadow DOM, so you don&rsquo;t have to worry about broken styles and global JS.</description>
|
|
|
|
|
- </item>
|
|
|
|
|
-
|
|
|
|
|
</channel>
|
|
</channel>
|
|
|
</rss>
|
|
</rss>
|