mirror of https://github.com/akveo/blur-admin
Update 2016-05-17T10:22:06.741Z
Vladimir Lugovsky
parent
e2f6f8fd41
commit
468aea3ae7
|
|
@ -81,5 +81,10 @@
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -83,5 +83,10 @@ npm install
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -94,5 +94,10 @@ To do this, add following code to some configuration block, for example to <code
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -77,5 +77,10 @@
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -103,5 +103,10 @@ This will allow you to easily switch off some pages in the future if needed
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -90,5 +90,10 @@ To do this replace theme in file <code>src/sass/theme/common.scss</code>:</p>
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -164,5 +164,10 @@ That means if there’s a parent abstract state for some state and they both hav
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,147 +0,0 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<meta name="keywords" content="admin,dashboard,template,angular,bootstrap,blur,panel,html,css,javascript">
|
||||
<title>BlurAdmin documentation - Code and stuff!</title>
|
||||
<link rel="alternate" href="http://localhost:8080/feed.xml" type="application/rss+xml" title="Ramblings of an immor(t)al demigod">
|
||||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900italic,900|Anonymous+Pro:400,700,400italic,700italic&subset=latin,greek,greek-ext,vietnamese,cyrillic-ext,latin-ext,cyrillic">
|
||||
<link rel="stylesheet" href="/blur-admin/css/main.css">
|
||||
<link rel="shortcut icon" href="/blur-admin/images/favicon.png">
|
||||
</head>
|
||||
<body>
|
||||
<div class="container">
|
||||
<div class="nav-main">
|
||||
<div class="wrap"><a href="/blur-admin/" class="nav-home"><img src="/blur-admin/images/blur-admin-logo.png" width="36" height="36" class="nav-logo"> <span class="blur-label">Blur</span>Admin</a>
|
||||
<ul class="nav-site nav-site-internal">
|
||||
<li><a href="/blur-admin/">Home</a></li>
|
||||
<li><a href="/blur-admin/articles/red-herring/" class="active">Docs</a></li>
|
||||
</ul><span class="nav-docs-right">Need some help? Let us know! <a href="mailto:help@akveo.com">help@akveo.com</a></span>
|
||||
</div>
|
||||
</div>
|
||||
<section class="content wrap documentationContent">
|
||||
<div class="nav-docs">
|
||||
<div class="nav-docs section">
|
||||
<h3>Second Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/red-herring/">A red herring</a></li>
|
||||
<li><a href="/blur-admin/articles/bamboo-cutter/">Taketori Monogatari</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>First Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/another-test/" class="active">Code and stuff!</a></li>
|
||||
<li><a href="/blur-admin/articles/hello-world/">README</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>Third Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/markdown-syntax/">Markdown syntax</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="inner-content">
|
||||
<h1>Code and stuff!</h1>
|
||||
<div class="subHeader"></div><p>Syntax highlighting with <a href="http://softwaremaniacs.org/soft/highlight/en/">highlight.js</a>.
|
||||
The theme used is tomorrow, you can find more themes <a href="http://jmblog.github.io/color-themes-for-highlightjs/">here</a>.</p>
|
||||
<p><span class="more"></span></p>
|
||||
<h3 id="javascript">JavaScript</h3>
|
||||
<pre><code class="lang-javascript"><span class="function"><span class="keyword">function</span> <span class="title">getRandomNumber</span>(<span class="params"></span>) </span>{
|
||||
<span class="keyword">return</span> <span class="number">4</span>; <span class="comment">// chosen by fair dice roll.</span>
|
||||
<span class="comment">// guaranteed to be random.</span>
|
||||
}
|
||||
</code></pre>
|
||||
<h3 id="coffeescript">CoffeeScript</h3>
|
||||
<pre><code class="lang-coffeescript"><span class="class"><span class="keyword">class</span> <span class="title">Animal</span></span>
|
||||
<span class="comment">### Intellegent design ###</span>
|
||||
getDNA: <span class="function">-></span>
|
||||
<span class="built_in">print</span> <span class="string">'sequencing...'</span>
|
||||
<span class="keyword">while</span> <span class="literal">true</span>
|
||||
sleep <span class="number">1</span>
|
||||
|
||||
<span class="class"><span class="keyword">class</span> <span class="title">Monkey</span> <span class="keyword">extends</span> <span class="title">Animal</span></span>
|
||||
speak: <span class="function">-></span>
|
||||
<span class="built_in">print</span> <span class="string">'ah ah ah'</span>
|
||||
|
||||
<span class="class"><span class="keyword">class</span> <span class="title">Human</span> <span class="keyword">extends</span> <span class="title">Monkey</span></span>
|
||||
speak: <span class="function">-></span>
|
||||
<span class="built_in">print</span> [<span class="string">'yolo'</span> <span class="keyword">unless</span> i % <span class="number">3</span>] + [<span class="string">'swag'</span> <span class="keyword">unless</span> i % <span class="number">5</span>] <span class="keyword">or</span> i <span class="keyword">for</span> i <span class="keyword">in</span> [<span class="number">1.</span><span class="number">.100</span>]
|
||||
</code></pre>
|
||||
<h3 id="c">C</h3>
|
||||
<pre><code class="lang-c"><span class="meta">#<span class="meta-keyword">include</span> <span class="meta-string"><stdio.h></span></span>
|
||||
|
||||
<span class="function"><span class="keyword">int</span> <span class="title">main</span><span class="params">(<span class="keyword">void</span>)</span>
|
||||
</span>{
|
||||
<span class="built_in">printf</span>(<span class="string">"Hello world\n"</span>);
|
||||
<span class="keyword">return</span> <span class="number">0</span>;
|
||||
}
|
||||
</code></pre>
|
||||
<h3 id="c-">C++</h3>
|
||||
<pre><code class="lang-cpp"><span class="meta">#<span class="meta-keyword">include</span> <span class="meta-string"><iostream></span></span>
|
||||
|
||||
<span class="function"><span class="keyword">int</span> <span class="title">main</span><span class="params">()</span>
|
||||
</span>{
|
||||
<span class="built_in">std</span>::<span class="built_in">cout</span> << <span class="string">"Hello World!"</span> << <span class="built_in">std</span>::<span class="built_in">endl</span>;
|
||||
<span class="keyword">return</span> <span class="number">0</span>;
|
||||
}
|
||||
</code></pre>
|
||||
<h3 id="c-sharp">C-sharp</h3>
|
||||
<pre><code class="lang-cs"><span class="keyword">class</span> <span class="title">ExampleClass</span>
|
||||
{
|
||||
<span class="function"><span class="keyword">static</span> <span class="keyword">void</span> <span class="title">Main</span>(<span class="params"></span>)
|
||||
</span>{
|
||||
System.Console.WriteLine(<span class="string">"Hello, world!"</span>);
|
||||
}
|
||||
}
|
||||
</code></pre>
|
||||
<h3 id="erlang">Erlang</h3>
|
||||
<pre><code class="lang-erlang">io:format(<span class="string">"~s~n"</span>, [<span class="string">"hello, world"</span>])
|
||||
</code></pre>
|
||||
<h3 id="go">Go</h3>
|
||||
<pre><code class="lang-go"><span class="keyword">package</span> main
|
||||
|
||||
<span class="keyword">import</span> <span class="string">"fmt"</span>
|
||||
|
||||
<span class="keyword">func</span> main() {
|
||||
fmt.Println(<span class="string">"Hello World!"</span>)
|
||||
}
|
||||
</code></pre>
|
||||
<h3 id="java">Java</h3>
|
||||
<pre><code class="lang-java"><span class="keyword">public</span> <span class="class"><span class="keyword">class</span> <span class="title">HelloWorld</span> </span>{
|
||||
<span class="function"><span class="keyword">public</span> <span class="keyword">static</span> <span class="keyword">void</span> <span class="title">main</span><span class="params">(String[] args)</span> </span>{
|
||||
System.out.println(<span class="string">"Hello world!"</span>);
|
||||
}
|
||||
}
|
||||
</code></pre>
|
||||
<h3 id="objectivec">ObjectiveC</h3>
|
||||
<pre><code class="lang-objectivec"><span class="meta">#import <span class="meta-string"><stdio.h></span></span>
|
||||
|
||||
<span class="keyword">int</span> main(<span class="keyword">void</span>)
|
||||
{
|
||||
printf(<span class="string">"Hello, World!\n"</span>);
|
||||
<span class="keyword">return</span> <span class="number">0</span>;
|
||||
}
|
||||
</code></pre>
|
||||
<h3 id="php"><span class="caps">PHP</span></h3>
|
||||
<pre><code class="lang-php"><span class="meta"><?php</span> <span class="keyword">echo</span> <span class="string">'Hello, world'</span>; <span class="meta">?></span>
|
||||
</code></pre>
|
||||
<h3 id="python">Python</h3>
|
||||
<pre><code class="lang-python">print(<span class="string">"Hello World"</span>)
|
||||
</code></pre>
|
||||
<h3 id="ruby">Ruby</h3>
|
||||
<pre><code class="lang-ruby">puts <span class="string">"Hello world!"</span>
|
||||
</code></pre>
|
||||
|
||||
</div>
|
||||
</section>
|
||||
<footer class="wrap">
|
||||
<div class="left">Powered by Angular, Bootsrap, Gulp and more...</div>
|
||||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,147 +0,0 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<meta name="keywords" content="admin,dashboard,template,angular,bootstrap,blur,panel,html,css,javascript">
|
||||
<title>BlurAdmin documentation - Taketori Monogatari</title>
|
||||
<link rel="alternate" href="http://localhost:8080/feed.xml" type="application/rss+xml" title="Ramblings of an immor(t)al demigod">
|
||||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900italic,900|Anonymous+Pro:400,700,400italic,700italic&subset=latin,greek,greek-ext,vietnamese,cyrillic-ext,latin-ext,cyrillic">
|
||||
<link rel="stylesheet" href="/blur-admin/css/main.css">
|
||||
<link rel="shortcut icon" href="/blur-admin/images/favicon.png">
|
||||
</head>
|
||||
<body>
|
||||
<div class="container">
|
||||
<div class="nav-main">
|
||||
<div class="wrap"><a href="/blur-admin/" class="nav-home"><img src="/blur-admin/images/blur-admin-logo.png" width="36" height="36" class="nav-logo"> <span class="blur-label">Blur</span>Admin</a>
|
||||
<ul class="nav-site nav-site-internal">
|
||||
<li><a href="/blur-admin/">Home</a></li>
|
||||
<li><a href="/blur-admin/articles/red-herring/" class="active">Docs</a></li>
|
||||
</ul><span class="nav-docs-right">Need some help? Let us know! <a href="mailto:help@akveo.com">help@akveo.com</a></span>
|
||||
</div>
|
||||
</div>
|
||||
<section class="content wrap documentationContent">
|
||||
<div class="nav-docs">
|
||||
<div class="nav-docs section">
|
||||
<h3>Second Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/red-herring/">A red herring</a></li>
|
||||
<li><a href="/blur-admin/articles/bamboo-cutter/" class="active">Taketori Monogatari</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>First Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/another-test/">Code and stuff!</a></li>
|
||||
<li><a href="/blur-admin/articles/hello-world/">README</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>Third Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/markdown-syntax/">Markdown syntax</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="inner-content">
|
||||
<h1>Taketori Monogatari</h1>
|
||||
<div class="subHeader"></div><p>Long, long ago, there lived an old bamboo wood-cutter.</p>
|
||||
<p>He was very poor and sad also, for no child had Heaven sent to cheer his old age, and in his heart there was no hope of rest from work till he died and was laid in the quiet grave. Every morning he went forth into the woods and hills wherever the bamboo reared its lithe green plumes against the sky. When he had made his choice, he would cut down these feathers of the forest, and splitting them lengthwise, or cutting them into joints, would carry the bamboo wood home and make it into various articles for the household, and he and his old wife gained a small livelihood by selling them.</p>
|
||||
<p><span class="more"></span></p>
|
||||
<p><img src="/blur-admin/articles/bamboo-cutter/taketori_monogatari.jpg" alt="Taketori Monogatari"></p>
|
||||
<p>One morning as usual he had gone out to his work, and having found a nice clump of bamboos, had set to work to cut some of them down. Suddenly the green grove of bamboos was flooded with a bright soft light, as if the full moon had risen over the spot. Looking round in astonishment, he saw that the brilliance was streaming from one bamboo. The old man. full of wonder. dropped his ax and went towards the light. On nearer approach he saw that this soft splendor came from a hollow in the green bamboo stem, and still more wonderful to behold, in the midst of the brilliance stood a tiny human being, only three inches in height, and exquisitely beautiful in appearance.</p>
|
||||
<p>“You must be sent to be my child, for I find you here among the bamboos where lies my daily work,” said the old man, and taking the little creature in his hand he took it home to his wife to bring up. The tiny girl was so exceedingly beautiful and so small, that the old woman put her into a basket to safeguard her from the least possibility of being hurt in any way.</p>
|
||||
<p>The old couple were now very happy, for it had been a lifelong regret that they had no children of their own, and with joy they now expended all the love of their old age on the little child who had come to them in so marvelous a manner.</p>
|
||||
<p>From this time on, the old man often found gold in the notches of the bamboos when he hewed them down and cut them up; not only gold, but precious stones also, so that by degrees he became rich. He built himself a fine house, and was no longer known as the poor bamboo woodcutter, but as a wealthy man.</p>
|
||||
<p>Three months passed quickly away, and in that time the bamboo child had, wonderful to say, become a full-grown girl, so her foster- parents did up her hair and dressed her in beautiful kimonos. She was of such wondrous beauty that they placed her behind the screens like a princess, and allowed no one to see her, waiting upon her themselves. It seemed as if she were made of light, for the house was filled with a soft shining, so that even in the dark of night it was like daytime. Her presence seemed to have a benign influence on those there. Whenever the old man felt sad, he had only to look upon his foster-daughter and his sorrow vanished, and he became as happy as when he was a youth.</p>
|
||||
<p>At last the day came for the naming of their new-found child, so the old couple called in a celebrated name-giver, and he gave her the name of Princess Moonlight, because her body gave forth so much soft bright light that she might have been a daughter of the Moon God.</p>
|
||||
<p>For three days the festival was kept up with song and dance and music. All the friends and relations of the old couple were present, and great was their enjoyment of the festivities held to celebrate the naming of Princess Moonlight. Everyone who saw her declared that there never had been seen any one so lovely; all the beauties throughout the length and breadth of the land would grow pale beside her, so they said. The fame of the Princess’s loveliness spread far and wide, and many were the suitors who desired to win her hand, or even so much as to see her.</p>
|
||||
<p>Suitors from far and near posted themselves outside the house, and made little holes in the fence, in the hope of catching a glimpse of the Princess as she went from one room to the other along the veranda. They stayed there day and night, sacrificing even their sleep for a chance of seeing her, but all in vain. Then they approached the house, and tried to speak to the old man and his wife or some of the servants, but not even this was granted them.</p>
|
||||
<p>Still, in spite of all this disappointment they stayed on day after day, and night after night, and counted it as nothing, so great was their desire to see the Princess.</p>
|
||||
<p>At last, however, most of the men, seeing how hopeless their quest was, lost heart and hope both, and returned to their homes. All except five Knights, whose ardor and determination, instead of waning, seemed to wax greater with obstacles. These five men even went without their meals, and took snatches of whatever they could get brought to them, so that they might always stand outside the dwelling. They stood there in all weathers, in sunshine and in rain.</p>
|
||||
<p>Sometimes they wrote letters to the Princess, but no answer was vouchsafed to them. Then when letters failed to draw any reply, they wrote poems to her telling her of the hopeless love which kept them from sleep, from food, from rest, and even from their homes. Still Princes Moonlight gave no sign of having received their verses.</p>
|
||||
<p>In this hopeless state the winter passed. The snow and frost and the cold winds gradually gave place to the gentle warmth of spring. Then the summer came, and the sun burned white and scorching in the heavens above and on the earth beneath, and still these faithful Knights kept watch and waited. At the end of these long months they called out to the old bamboo-cutter and entreated him to have some mercy upon them and to show them the Princess, but he answered only that as he was not her real father he could not insist on her obeying him against her wishes.</p>
|
||||
<p>The five Knights on receiving this stern answer returned to their several homes, and pondered over the best means of touching the proud Princess’s heart, even so much as to grant them a hearing. They took their rosaries in hand and knelt before their household shrines, and burned precious incense, praying to Buddha to give them their heart’s desire. Thus several days passed, but even so they could not rest in their homes.</p>
|
||||
<p>So again they set out for the bamboo-cutter’s house. This time the old man came out to see them, and they asked him to let them know if it was the Princess’s resolution never to see any man whatsoever, and they implored him to speak for them and to tell her the greatness of their love, and how long they had waited through the cold of winter and the heat of summer, sleepless and roofless through all weathers, without food and without rest, in the ardent hope of winning her, and they were willing to consider this long vigil as pleasure if she would but give them one chance of pleading their cause with her.</p>
|
||||
<p>The old man lent a willing ear to their tale of love, for in his inmost heart he felt sorry for these faithful suitors and would have liked to see his lovely foster-daughter married to one of them. So he went in to Princess Moonlight and said reverently:</p>
|
||||
<p>“Although you have always seemed to me to be a heavenly being, yet I have had the trouble of bringing you up as my own child and you have been glad of the protection of my roof. Will you refuse to do as I wish?”</p>
|
||||
<p>Then Princess Moonlight replied that there was nothing she would not do for him, that she honored and loved him as her own father, and that as for herself she could not remember the time before she came to earth.</p>
|
||||
<p>The old man listened with great joy as she spoke these dutiful words. Then he told her how anxious he was to see her safely and happily married before he died.</p>
|
||||
<p>“I am an old man, over seventy years of age, and my end may come any time now. It is necessary and right that you should see these five suitors and choose one of them.”</p>
|
||||
<p>“Oh, why,” said the Princess in distress, “must I do this? I have no wish to marry now.”</p>
|
||||
<p>“I found you,” answered the old man, “many years ago, when you were a little creature three inches high, in the midst of a great white light. The light streamed from the bamboo in which you were hid and led me to you. So I have always thought that you were more than mortal woman. While I am alive it is right for you to remain as you are if you wish to do so, but some day I shall cease to be and who will take care of you then? Therefore I pray you to meet these five brave men one at a time and make up your mind to marry one of them!”</p>
|
||||
<p>Then the Princess answered that she felt sure that she was not as beautiful as perhaps report made her out to be, and that even if she consented to marry any one of them, not really knowing her before, his heart might change afterwards. So as she did not feel sure of them, even though her father told her they were worthy Knights, she did not feel it wise to see them.</p>
|
||||
<p>“All you say is very reasonable,” said the old man, “but what kind of men will you consent to see? I do not call these five men who have waited on you for months, light-hearted. They have stood outside this house through the winter and the summer, often denying themselves food and sleep so that they may win you. What more can you demand?”</p>
|
||||
<p>Then Princess Moonlight said she must make further trial of their love before she would grant their request to interview her. The five warriors were to prove their love by each bringing her from distant countries something that she desired to possess.</p>
|
||||
<p>That same evening the suitors arrived and began to play their flutes in turn, and to sing their self-composed songs telling of their great and tireless love. The bamboo-cutter went out to them and offered them his sympathy for all they had endured and all the patience they had shown in their desire to win his foster-daughter. Then he gave them her message, that she would consent to marry whosoever was successful in bringing her what she wanted. This was to test them.</p>
|
||||
<p>The five all accepted the trial, and thought it an excellent plan, for it would prevent jealousy between them.</p>
|
||||
<p>Princess Moonlight then sent word to the First Knight that she requested him to bring her the stone bowl which had belonged to Buddha in India.</p>
|
||||
<p>The Second Knight was asked to go to the Mountain of Horai, said to be situated in the Eastern Sea, and to bring her a branch of the wonderful tree that grew on its summit. The roots of this tree were of silver, the trunk of gold, and the branches bore as fruit white jewels.</p>
|
||||
<p>The Third Knight was told to go to China and search for the fire-rat and to bring her its skin.</p>
|
||||
<p>The Fourth Knight was told to search for the dragon that carried on its head the stone radiating five colors and to bring the stone to her.</p>
|
||||
<p>The Fifth Knight was to find the swallow which carried a shell in its stomach and to bring the shell to her.</p>
|
||||
<p>The old man thought these very hard tasks and hesitated to carry the messages, but the Princess would make no other conditions. So her commands were issued word for word to the five men who, when they heard what was required of them, were all disheartened and disgusted at what seemed to them the impossibility of the tasks given them and returned to their own homes in despair.</p>
|
||||
<p>But after a time, when they thought of the Princess, the love in their hearts revived for her, and they resolved to make an attempt to get what she desired of them.</p>
|
||||
<p>The First Knight sent word to the Princess that he was starting out that day on the quest of Buddha’s bowl, and he hoped soon to bring it to her. But he had not the courage to go all the way to India, for in those days traveling was very difficult and full of danger, so he went to one of the temples in Kyoto and took a stone bowl from the altar there, paying the priest a large sum of money for it. He then wrapped it in a cloth of gold and, waiting quietly for three years, returned and carried it to the old man.</p>
|
||||
<p>Princess Moonlight wondered that the Knight should have returned so soon. She took the bowl from its gold wrapping, expecting it to make the room full of light, but it did not shine at all, so she knew that it was a sham thing and not the true bowl of Buddha. She returned it at once and refused to see him. The Knight threw the bowl away and returned to his home in despair. He gave up now all hopes of ever winning the Princess.</p>
|
||||
<p>The Second Knight told his parents that he needed change of air for his health, for he was ashamed to tell them that love for the Princess Moonlight was the real cause of his leaving them. He then left his home, at the same time sending word to the Princess that he was setting out for Mount Horai in the hope of getting her a branch of the gold and silver tree which she so much wished to have. He only allowed his servants to accompany him half-way, and then sent them back. He reached the seashore and embarked on a small ship, and after sailing away for three days he landed and employed several carpenters to build him a house contrived in such a way that no one could get access to it. He then shut himself up with six skilled jewelers, and endeavored to make such a gold and silver branch as he thought would satisfy the Princess as having come from the wonderful tree growing on Mount Horai. Every one whom he had asked declared that Mount Horai belonged to the land of fable and not to fact.</p>
|
||||
<p>When the branch was finished, he took his journey home and tried to make himself look as if he were wearied and worn out with travel. He put the jeweled branch into a lacquer box and carried it to the bamboo-cutter, begging him to present it to the Princess.</p>
|
||||
<p>The old man was quite deceived by the travel-stained appearance of the Knight, and thought that he had only just returned from his long journey with the branch. So he tried to persuade the Princess to consent to see the man. But she remained silent and looked very sad. The old man began to take out the branch and praised it as a wonderful treasure to be found nowhere in the whole land. Then he spoke of the Knight, how handsome and how brave he was to have undertaken a journey to so remote a place as the Mount of Horai.</p>
|
||||
<p>Princess Moonlight took the branch in her hand and looked at it carefully. She then told her foster-parent that she knew it was impossible for the man to have obtained a branch from the gold and silver tree growing on Mount Horai so quickly or so easily, and she was sorry to say she believed it artificial.</p>
|
||||
<p>The old man then went out to the expectant Knight, who had now approached the house, and asked where he had found the branch. Then the man did not scruple to make up a long story.</p>
|
||||
<p>“Two years ago I took a ship and started in search of Mount Horai. After going before the wind for some time I reached the far Eastern Sea. Then a great storm arose and I was tossed about for many days, losing all count of the points of the compass, and finally we were blown ashore on an unknown island. Here I found the place inhabited by demons who at one time threatened to kill and eat me. However, I managed to make friends with these horrible creatures, and they helped me and my sailors to repair the boat, and I set sail again. Our food gave out, and we suffered much from sickness on board. At last, on the five-hundredth day from the day of starting, I saw far off on the horizon what looked like the peak of a mountain. On nearer approach, this proved to be an island, in the center of which rose a high mountain. I landed, and after wandering about for two or three days, I saw a shining being coming towards me on the beach, holding in his hands a golden bowl. I went up to him and asked him if I had, by good chance, found the island of Mount Horai, and he answered:”</p>
|
||||
<p>“‘Yes, this is Mount Horai!’”</p>
|
||||
<p>“With much difficulty I climbed to the summit, here stood the golden tree growing with silver roots in the ground. The wonders of that strange land are many, and if I began to tell you about them I could never stop. In spite of my wish to stay there long, on breaking off the branch I hurried back. With utmost speed it has taken me four hundred days to get back, and, as you see, my clothes are still damp from exposure on the long sea voyage. I have not even waited to change my raiment, so anxious was I to bring the branch to the Princess quickly.”</p>
|
||||
<p>Just at this moment the six jewelers, who had been employed on the making of the branch, but not yet paid by the Knight, arrived at the house and sent in a petition to the Princess to be paid for their labor. They said that they had worked for over a thousand days making the branch of gold, with its silver twigs and its jeweled fruit, that was now presented to her by the Knight, but as yet they had received nothing in payment. So this Knight’s deception was thus found out, and the Princess, glad of an escape from one more importunate suitor, was only too pleased to send back the branch. She called in the workmen and had them paid liberally, and they went away happy. But on the way home they were overtaken by the disappointed man. who beat them till they were nearly dead, for letting out the secret, and they barely escaped with their lives. The Knight then returned home, raging in his heart; and in despair of ever winning the Princess gave up society and retired to a solitary life among the mountains.</p>
|
||||
<p>Now the Third Knight had a friend in China, so he wrote to him to get the skin of the fire-rat. The virtue of any part of this animal was that no fire could harm it. He promised his friend any amount of money he liked to ask if only he could get him the desired article. As soon as the news came that the ship on which his friend had sailed home had come into port, he rode seven days on horseback to meet him. He handed his friend a large sum of money, and received the fire-rat’s skin. When he reached home he put it carefully in a box and sent it in to the Princess while he waited outside for her answer.</p>
|
||||
<p>The bamboo-cutter took the box from the Knight and, as usual, carried it in to her and tried to coax her to see the Knight at once, but Princess Moonlight refused, saying that she must first put the skin to test by putting it into the fire. If it were the real thing it would not burn. So she took off the crape wrapper and opened the box, and then threw the skin into the fire. The skin crackled and burnt up at once, and the Princess knew that this man also had not fulfilled his word. So the Third Knight failed also.</p>
|
||||
<p>Now the Fourth Knight was no more enterprising than the rest. Instead of starting out on the quest of the dragon bearing on its head the five-color-radiating jewel, he called all his servants together and gave them the order to seek for it far and wide in Japan and in China, and he strictly forbade any of them to return till they had found it.</p>
|
||||
<p>His numerous retainers and servants started out in different directions, with no intention, however, of obeying what they considered an impossible order. They simply took a holiday, went to pleasant country places together, and grumbled at their master’s unreasonableness.</p>
|
||||
<p>The Knight meanwhile, thinking that his retainers could not fail to find the jewel, repaired to his house, and fitted it up beautifully for the reception of the Princess, he felt so sure of winning her.</p>
|
||||
<p>One year passed away in weary waiting, and still his men did not return with the dragon-jewel. The Knight became desperate. He could wait no longer, so taking with him only two men he hired a ship and commanded the captain to go in search of the dragon; the captain and the sailors refused to undertake what they said was an absurd search, but the Knight compelled them at last to put out to sea.</p>
|
||||
<p>When they had been but a few days out they encountered a great storm which lasted so long that, by the time its fury abated, the Knight had determined to give up the hunt of the dragon. They were at last blown on shore, for navigation was primitive in those days. Worn out with his travels and anxiety, the fourth suitor gave himself up to rest. He had caught a very heavy cold, and had to go to bed with a swollen face.</p>
|
||||
<p>The governor of the place, hearing of his plight, sent messengers with a letter inviting him to his house. While he was there thinking over all his troubles, his love for the Princess turned to anger, and he blamed her for all the hardships he had undergone. He thought that it was quite probable she had wished to kill him so that she might be rid of him, and in order to carry out her wish had sent him upon his impossible quest.</p>
|
||||
<p>At this point all the servants he had sent out to find the jewel came to see him, and were surprised to find praise instead of displeasure awaiting them. Their master told them that he was heartily sick of adventure, and said that he never intended to go near the Princess’s house again in the future.</p>
|
||||
<p>Like all the rest, the Fifth Knight failed in his quest–he could not find the swallow’s shell.</p>
|
||||
<p>By this time the fame of Princess Moonlight’s beauty had reached the ears of the Emperor, and he sent one of the Court ladies to see if she were really as lovely as report said; if so he would summon her to the Palace and make her one of the ladies-in-waiting.</p>
|
||||
<p>When the Court lady arrived, in spite of her father’s entreaties, Princess Moonlight refused to see her. The Imperial messenger insisted, saying it was the Emperor’s order. Then Princess Moonlight told the old man that if she was forced to go to the Palace in obedience to the Emperor’s order, she would vanish from the earth.</p>
|
||||
<p>When the Emperor was told of her persistence in refusing to obey his summons, and that if pressed to obey she would disappear altogether from sight, he determined to go and see her. So he planned to go on a hunting excursion in the neighborhood of the bamboo-cutter’s house, and see the Princess himself. He sent word to the old man of his intention, and he received consent to the scheme. The next day the Emperor set out with his retinue, which he soon managed to outride. He found the bamboo-cutter’s house and dismounted. He then entered the house and went straight to where the Princess was sitting with her attendant maidens.</p>
|
||||
<p>Never had he seen any one so wonderfully beautiful, and he could not but look at her, for she was more lovely than any human being as she shone in her own soft radiance. When Princess Moonlight became aware that a stranger was looking at her she tried to escape from the room, but the Emperor caught her and begged her to listen to what he had to say. Her only answer was to hide her face in her sleeves.</p>
|
||||
<p>The Emperor fell deeply in love with her, and begged her to come to the Court, where he would give her a position of honor and everything she could wish for. He was about to send for one of the Imperial palanquins to take her back with him at once, saying that her grace and beauty should adorn a Court, and not be hidden in a bamboo-cutter’s cottage.</p>
|
||||
<p>But the Princess stopped him. She said that if she were forced to go to the Palace she would turn at once into a shadow, and even as she spoke she began to lose her form. Her figure faded from his sight while he looked.</p>
|
||||
<p>The Emperor then promised to leave her free if only she would resume her former shape, which she did.</p>
|
||||
<p>It was now time for him to return, for his retinue would be wondering what had happened to their Royal master when they missed him for so long. So be bade her good-by, and left the house with a sad heart. Princess Moonlight was for him the most beautiful woman in the world; all others were dark beside her, and he thought of her night and day. His Majesty now spent much of his time in writing poems, telling her of his love and devotion, and sent them to her, and though she refused to see him again she answered with many verses of her own composing, which told him gently and kindly that she could never marry any one on this earth. These little songs always gave him pleasure.</p>
|
||||
<p>At this time her foster-parents noticed that night after night the Princess would sit on her balcony and gaze for hours at the moon, in a spirit of the deepest dejection, ending always in a burst of tears. One night the old man found her thus weeping as if her heart were broken, and he besought her to tell him the reason of her sorrow.</p>
|
||||
<p>With many tears she told him that he had guessed rightly when he supposed her not to belong to this world–that she had in truth come from the moon, and that her time on earth would soon be over. On the fifteenth day of that very month of August her friends from the moon would come to fetch her, and she would have to return. Her parents were both there, but having spent a lifetime on the earth she had forgotten them, and also the moon-world to which she belonged. It made her weep, she said, to think of leaving her kind foster- parents, and the home where she had been happy for so long.</p>
|
||||
<p>When her attendants heard this they were very sad, and could not eat or drink for sadness at the thought that the Princess was so soon to leave them.</p>
|
||||
<p>The Emperor, as soon as the news was carried to him, sent messengers to the house to find out if the report were true or not.</p>
|
||||
<p>The old bamboo-cutter went out to meet the Imperial messengers. The last few days of sorrow had told upon the old man; he had aged greatly, and looked much more than his seventy years. Weeping bitterly, he told them that the report was only too true, but he intended, however, to make prisoners of the envoys from the moon, and to do all he could to prevent the Princess from being carried back.</p>
|
||||
<p>The men returned and told His Majesty all that had passed. On the fifteenth day of that month the Emperor sent a guard of two thousand warriors to watch the house. One thousand stationed themselves on the roof, another thousand kept watch round all the entrances of the house. All were well trained archers, with bows and arrows. The bamboo-cutter and his wife hid Princess Moonlight in an inner room.</p>
|
||||
<p>The old man gave orders that no one was to sleep that night, all in the house were to keep a strict watch, and be ready to protect the Princess. With these precautions, and the help of the Emperor’s men- at-arms, he hoped to withstand the moon-messengers, but the Princess told him that all these measures to keep her would be useless, and that when her people came for her nothing whatever could prevent them from carrying out their purpose. Even the Emperors men would be powerless. Then she added with tears that she was very, very sorry to leave him and his wife, whom she had learned to love as her parents, that if she could do as she liked she would stay with them in their old age, and try to make some return for all the love and kindness they had showered upon her during all her earthly life.</p>
|
||||
<p>The night wore on! The yellow harvest moon rose high in the heavens, flooding the world asleep with her golden light. Silence reigned over the pine and the bamboo forests, and on the roof where the thousand men-at-arms waited.</p>
|
||||
<p>Then the night grew gray towards the dawn and all hoped that the danger was over–that Princess Moonlight would not have to leave them after all. Then suddenly the watchers saw a cloud form round the moon–and while they looked this cloud began to roll earthwards. Nearer and nearer it came, and every one saw with dismay that its course lay towards the house.</p>
|
||||
<p>In a short time the sky was entirely obscured, till at last the cloud lay over the dwelling only ten feet off the ground. In the midst of the cloud there stood a flying chariot, and in the chariot a band of luminous beings. One amongst them who looked like a king and appeared to be the chief stepped out of the chariot, and, poised in air, called to the old man to come out.</p>
|
||||
<p>“The time has come,” he said, “for Princess Moonlight to return to the moon from whence she came. She committed a grave fault, and as a punishment was sent to live down here for a time. We know what good care you have taken of the Princess, and we have rewarded you for this and have sent you wealth and prosperity. We put the gold in the bamboos for you to find.”</p>
|
||||
<p>“I have brought up this Princess for twenty years and never once has she done a wrong thing, therefore the lady you are seeking cannot be this one,” said the old man. “I pray you to look elsewhere.”</p>
|
||||
<p>Then the messenger called aloud, saying:</p>
|
||||
<p>“Princess Moonlight, come out from this lowly dwelling. Rest not here another moment,”</p>
|
||||
<p>At these words the screens of the Princess’s room slid open of their own accord, revealing the Princess shining in her own radiance, bright and wonderful and full of beauty.</p>
|
||||
<p>The messenger led her forth and placed her in the chariot. She looked back, and saw with pity the deep sorrow of the old man. She spoke to him many comforting words, and told him that it was not her will to leave him and that he must always think of her when looking at the moon.</p>
|
||||
<p>The bamboo-cutter implored to be allowed to accompany her, but this was not allowed. The Princess took off her embroidered outer garment and gave it to him as a keepsake.</p>
|
||||
<p>One of the moon beings in the chariot held a wonderful coat of wings, another had a phial full of the Elixir of Life which was given the Princess to drink. She swallowed a little and was about to give the rest to the old man, but she was prevented from doing so.</p>
|
||||
<p>The robe of wings was about to be put upon her shoulders, but she said:</p>
|
||||
<p>“Wait a little. I must not forget my good friend the Emperor. I must write him once more to say good-by while still in this human form.”</p>
|
||||
<p>In spite of the impatience of the messengers and charioteers she kept them waiting while she wrote. She placed the phial of the Elixir of Life with the letter, and, giving them to the old man, she asked him to deliver them to the Emperor.</p>
|
||||
<p>Then the chariot began to roll heavenwards towards the moon, and as they all gazed with tearful eyes at the receding Princess, the dawn broke, and in the rosy light of day the moon-chariot and all in it were lost amongst the fleecy clouds that were now wafted across the sky on the wings of the morning wind.</p>
|
||||
<p>Princess Moonlight’s letter was carried to the Palace. His Majesty was afraid to touch the Elixir of Life, so he sent it with the letter to the top of the most sacred mountain in the land. Mount Fuji, and there the Royal emissaries burnt it on the summit at sunrise. So to this day people say there is smoke to be seen rising from the top of Mount Fuji to the clouds.</p>
|
||||
|
||||
</div>
|
||||
</section>
|
||||
<footer class="wrap">
|
||||
<div class="left">Powered by Angular, Bootsrap, Gulp and more...</div>
|
||||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 380 KiB |
|
|
@ -1,118 +0,0 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<meta name="keywords" content="admin,dashboard,template,angular,bootstrap,blur,panel,html,css,javascript">
|
||||
<title>BlurAdmin documentation - README</title>
|
||||
<link rel="alternate" href="http://localhost:8080/feed.xml" type="application/rss+xml" title="Ramblings of an immor(t)al demigod">
|
||||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900italic,900|Anonymous+Pro:400,700,400italic,700italic&subset=latin,greek,greek-ext,vietnamese,cyrillic-ext,latin-ext,cyrillic">
|
||||
<link rel="stylesheet" href="/blur-admin/css/main.css">
|
||||
<link rel="shortcut icon" href="/blur-admin/images/favicon.png">
|
||||
</head>
|
||||
<body>
|
||||
<div class="container">
|
||||
<div class="nav-main">
|
||||
<div class="wrap"><a href="/blur-admin/" class="nav-home"><img src="/blur-admin/images/blur-admin-logo.png" width="36" height="36" class="nav-logo"> <span class="blur-label">Blur</span>Admin</a>
|
||||
<ul class="nav-site nav-site-internal">
|
||||
<li><a href="/blur-admin/">Home</a></li>
|
||||
<li><a href="/blur-admin/articles/red-herring/" class="active">Docs</a></li>
|
||||
</ul><span class="nav-docs-right">Need some help? Let us know! <a href="mailto:help@akveo.com">help@akveo.com</a></span>
|
||||
</div>
|
||||
</div>
|
||||
<section class="content wrap documentationContent">
|
||||
<div class="nav-docs">
|
||||
<div class="nav-docs section">
|
||||
<h3>Second Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/red-herring/">A red herring</a></li>
|
||||
<li><a href="/blur-admin/articles/bamboo-cutter/">Taketori Monogatari</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>First Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/another-test/">Code and stuff!</a></li>
|
||||
<li><a href="/blur-admin/articles/hello-world/" class="active">README</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>Third Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/markdown-syntax/">Markdown syntax</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="inner-content">
|
||||
<h1>README</h1>
|
||||
<div class="subHeader"></div><p>Welcome to your new blog! This is the default blog template with <span class="caps">RSS</span>, pagination and an archive. There are other templates available – run <code>wintersmith new --help</code> to list them.</p>
|
||||
<h2 id="_repeat-after-me-_-this-is-my-blog-there-are-many-like-it-but-this-one-is-mine-my-blog-is-my-best-friend-it-is-my-life-i-must-master-it-as-i-must-master-my-life-my-blog-without-me-is-useless-without-my-blog-i-am-useless-"><em>Repeat after me:</em> This is my blog. There are many like it, but this one is mine. My blog is my best friend. It is my life. I must master it as I must master my life. My blog, without me, is useless. Without my blog, I am useless.</h2>
|
||||
<p>Good, now, the directory structure of your blog is as follows:</p>
|
||||
<pre><code>├── config.json <- site configuration
|
||||
├── contents
|
||||
│ ├── about.md
|
||||
│ ├── archive.json
|
||||
│ ├── articles <– each article has its own directory
|
||||
│ │ ├── another-test
|
||||
│ │ │ └── index.md
|
||||
│ │ ├── bamboo-cutter
|
||||
│ │ │ ├── index.md
|
||||
│ │ │ └── taketori_monogatari.jpg
|
||||
│ │ ├── hello-world
|
||||
│ │ │ └── index.md
|
||||
│ │ ├── markdown-syntax
|
||||
│ │ │ └── index.md
|
||||
│ │ └── red-herring
|
||||
│ │ ├── banana.png
|
||||
│ │ └── index.md
|
||||
│ ├── authors <- author metadata, check author.jade
|
||||
│ │ ├── baker.json
|
||||
│ │ └── the-wintersmith.json
|
||||
│ ├── css
|
||||
│ │ └── main.css
|
||||
│ └── feed.json
|
||||
├── plugins
|
||||
│ └── paginator.coffee <- paginator plugin
|
||||
├── templates
|
||||
│ ├── archive.jade
|
||||
│ ├── article.jade
|
||||
│ ├── author.jade
|
||||
│ ├── feed.jade
|
||||
│ ├── index.jade
|
||||
│ └── layout.jade
|
||||
└── views
|
||||
└── articles.coffee <- view that lists articles
|
||||
</code></pre><p>Articles are sorted by date and 3 are shown per page, you can configure this and more in config.json. Check paginator.coffee for all options related to pagination, most plugins also have their own options.</p>
|
||||
<h3 id="a-typical-article">A typical article</h3>
|
||||
<pre><code class="lang-markdown">---
|
||||
title: Hear me blog
|
||||
author: johndoe
|
||||
<span class="section">date: 2012-12-12 12:12
|
||||
---</span>
|
||||
|
||||
This will be shown as the article excerpt.
|
||||
|
||||
<span class="section">## A h2, hr or <span class="more"> marks where the intro cuts off</span>
|
||||
|
||||
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
|
||||
tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
|
||||
quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
|
||||
consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
|
||||
cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
|
||||
proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
|
||||
</code></pre>
|
||||
<h2 id="links-in-the-markdown-to-other-items-in-the-content-tree-will-be-resolved-for-you-">Links in the markdown to other items in the content tree will be resolved for you.</h2>
|
||||
<p>For example a link to <code>../bamboo-cutter/index.md</code> resolves to <a href="/blur-admin/articles/bamboo-cutter/"><code>/articles/bamboo-cutter/</code></a>.</p>
|
||||
<hr>
|
||||
<p>This is where I leave you to your own devices. Join <strong>#wintersmith</strong> on freenode if you have any questions.</p>
|
||||
|
||||
</div>
|
||||
</section>
|
||||
<footer class="wrap">
|
||||
<div class="left">Powered by Angular, Bootsrap, Gulp and more...</div>
|
||||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,705 +0,0 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<meta name="keywords" content="admin,dashboard,template,angular,bootstrap,blur,panel,html,css,javascript">
|
||||
<title>BlurAdmin documentation - Markdown syntax</title>
|
||||
<link rel="alternate" href="http://localhost:8080/feed.xml" type="application/rss+xml" title="Ramblings of an immor(t)al demigod">
|
||||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900italic,900|Anonymous+Pro:400,700,400italic,700italic&subset=latin,greek,greek-ext,vietnamese,cyrillic-ext,latin-ext,cyrillic">
|
||||
<link rel="stylesheet" href="/blur-admin/css/main.css">
|
||||
<link rel="shortcut icon" href="/blur-admin/images/favicon.png">
|
||||
</head>
|
||||
<body>
|
||||
<div class="container">
|
||||
<div class="nav-main">
|
||||
<div class="wrap"><a href="/blur-admin/" class="nav-home"><img src="/blur-admin/images/blur-admin-logo.png" width="36" height="36" class="nav-logo"> <span class="blur-label">Blur</span>Admin</a>
|
||||
<ul class="nav-site nav-site-internal">
|
||||
<li><a href="/blur-admin/">Home</a></li>
|
||||
<li><a href="/blur-admin/articles/red-herring/" class="active">Docs</a></li>
|
||||
</ul><span class="nav-docs-right">Need some help? Let us know! <a href="mailto:help@akveo.com">help@akveo.com</a></span>
|
||||
</div>
|
||||
</div>
|
||||
<section class="content wrap documentationContent">
|
||||
<div class="nav-docs">
|
||||
<div class="nav-docs section">
|
||||
<h3>Second Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/red-herring/">A red herring</a></li>
|
||||
<li><a href="/blur-admin/articles/bamboo-cutter/">Taketori Monogatari</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>First Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/another-test/">Code and stuff!</a></li>
|
||||
<li><a href="/blur-admin/articles/hello-world/">README</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>Third Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/markdown-syntax/" class="active">Markdown syntax</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="inner-content">
|
||||
<h1>Markdown syntax</h1>
|
||||
<div class="subHeader"></div><p>Full markdown syntax taken from John Gruber’s <a href="http://daringfireball.net/projects/markdown/syntax">Daring Fireball</a>.
|
||||
Did you know that 9 out of 10 bloggers prefer to write in markdown?</p>
|
||||
<hr>
|
||||
<h1 id="markdown-syntax">Markdown: Syntax</h1>
|
||||
<ul>
|
||||
<li><a href="#overview">Overview</a><ul>
|
||||
<li><a href="#philosophy">Philosophy</a></li>
|
||||
<li><a href="#html">Inline <span class="caps">HTML</span></a></li>
|
||||
<li><a href="#autoescape">Automatic Escaping for Special Characters</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#block">Block Elements</a><ul>
|
||||
<li><a href="#p">Paragraphs and Line Breaks</a></li>
|
||||
<li><a href="#header">Headers</a></li>
|
||||
<li><a href="#blockquote">Blockquotes</a></li>
|
||||
<li><a href="#list">Lists</a></li>
|
||||
<li><a href="#precode">Code Blocks</a></li>
|
||||
<li><a href="#hr">Horizontal Rules</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#span">Span Elements</a><ul>
|
||||
<li><a href="#link">Links</a></li>
|
||||
<li><a href="#em">Emphasis</a></li>
|
||||
<li><a href="#code">Code</a></li>
|
||||
<li><a href="#img">Images</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#misc">Miscellaneous</a><ul>
|
||||
<li><a href="#backslash">Backslash Escapes</a></li>
|
||||
<li><a href="#autolink">Automatic Links</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>Note:</strong> This document is itself written using Markdown; you
|
||||
can <a href="/projects/markdown/syntax.text">see the source for it by adding ‘.text’ to the <span class="caps">URL</span></a>.</p>
|
||||
<hr>
|
||||
<h2 id="overview">Overview</h2>
|
||||
|
||||
<h3 id="philosophy">Philosophy</h3>
|
||||
|
||||
<p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p>
|
||||
<p>Readability, however, is emphasized above all else. A Markdown-formatted
|
||||
document should be publishable as-is, as plain text, without looking
|
||||
like it’s been marked up with tags or formatting instructions. While
|
||||
Markdown’s syntax has been influenced by several existing text-to-<span class="caps">HTML</span>
|
||||
filters – including <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a>, <a href="http://www.aaronsw.com/2002/atx/">atx</a>, <a href="http://textism.com/tools/textile/">Textile</a>, <a href="http://docutils.sourceforge.net/rst.html">reStructuredText</a>,
|
||||
<a href="http://www.triptico.com/software/grutatxt.html">Grutatext</a>, and <a href="http://ettext.taint.org/doc/">EtText</a> – the single biggest source of
|
||||
inspiration for Markdown’s syntax is the format of plain text email.</p>
|
||||
<p>To this end, Markdown’s syntax is comprised entirely of punctuation
|
||||
characters, which punctuation characters have been carefully chosen so
|
||||
as to look like what they mean. E.g., asterisks around a word actually
|
||||
look like *emphasis*. Markdown lists look like, well, lists. Even
|
||||
blockquotes look like quoted passages of text, assuming you’ve ever
|
||||
used email.</p>
|
||||
<h3 id="html">Inline <span class="caps">HTML</span></h3>
|
||||
|
||||
<p>Markdown’s syntax is intended for one purpose: to be used as a
|
||||
format for <em>writing</em> for the web.</p>
|
||||
<p>Markdown is not a replacement for <span class="caps">HTML</span>, or even close to it. Its
|
||||
syntax is very small, corresponding only to a very small subset of
|
||||
HTML tags. The idea is <em>not</em> to create a syntax that makes it easier
|
||||
to insert <span class="caps">HTML</span> tags. In my opinion, HTML tags are already easy to
|
||||
insert. The idea for Markdown is to make it easy to read, write, and
|
||||
edit prose. HTML is a <em>publishing</em> format; Markdown is a <em>writing</em>
|
||||
format. Thus, Markdown’s formatting syntax only addresses issues that
|
||||
can be conveyed in plain text.</p>
|
||||
<p>For any markup that is not covered by Markdown’s syntax, you simply
|
||||
use <span class="caps">HTML</span> itself. There’s no need to preface it or delimit it to
|
||||
indicate that you’re switching from Markdown to HTML; you just use
|
||||
the tags.</p>
|
||||
<p>The only restrictions are that block-level <span class="caps">HTML</span> elements – e.g. <code><div></code>,
|
||||
<code><table></code>, <code><pre></code>, <code><p></code>, etc. – must be separated from surrounding
|
||||
content by blank lines, and the start and end tags of the block should
|
||||
not be indented with tabs or spaces. Markdown is smart enough not
|
||||
to add extra (unwanted) <code><p></code> tags around <span class="caps">HTML</span> block-level tags.</p>
|
||||
<p>For example, to add an <span class="caps">HTML</span> table to a Markdown article:</p>
|
||||
<pre><code>This is a regular paragraph.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>Foo</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
This is another regular paragraph.
|
||||
</code></pre><p>Note that Markdown formatting syntax is not processed within block-level
|
||||
<span class="caps">HTML</span> tags. E.g., you can’t use Markdown-style <code>*emphasis*</code> inside an
|
||||
<span class="caps">HTML</span> block.</p>
|
||||
<p>Span-level <span class="caps">HTML</span> tags – e.g. <code><span></code>, <code><cite></code>, or <code><del></code> – can be
|
||||
used anywhere in a Markdown paragraph, list item, or header. If you
|
||||
want, you can even use <span class="caps">HTML</span> tags instead of Markdown formatting; e.g. if
|
||||
you’d prefer to use HTML <code><a></code> or <code><img></code> tags instead of Markdown’s
|
||||
link or image syntax, go right ahead.</p>
|
||||
<p>Unlike block-level <span class="caps">HTML</span> tags, Markdown syntax <em>is</em> processed within
|
||||
span-level tags.</p>
|
||||
<h3 id="autoescape">Automatic Escaping for Special Characters</h3>
|
||||
|
||||
<p>In <span class="caps">HTML</span>, there are two characters that demand special treatment: <code><</code>
|
||||
and <code>&</code>. Left angle brackets are used to start tags; ampersands are
|
||||
used to denote <span class="caps">HTML</span> entities. If you want to use them as literal
|
||||
characters, you must escape them as entities, e.g. <code>&lt;</code>, and
|
||||
<code>&amp;</code>.</p>
|
||||
<p>Ampersands in particular are bedeviling for web writers. If you want to
|
||||
write about ‘<span class="caps">AT</span>&T’, you need to write ‘<code>AT&amp;T</code>‘. You even need to
|
||||
escape ampersands within URLs. Thus, if you want to link to:</p>
|
||||
<pre><code>http://images.google.com/images?num=30&q=larry+bird
|
||||
</code></pre><p>you need to encode the <span class="caps">URL</span> as:</p>
|
||||
<pre><code>http://images.google.com/images?num=30&amp;q=larry+bird
|
||||
</code></pre><p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to
|
||||
forget, and is probably the single most common source of <span class="caps">HTML</span> validation
|
||||
errors in otherwise well-marked-up web sites.</p>
|
||||
<p>Markdown allows you to use these characters naturally, taking care of
|
||||
all the necessary escaping for you. If you use an ampersand as part of
|
||||
an <span class="caps">HTML</span> entity, it remains unchanged; otherwise it will be translated
|
||||
into <code>&amp;</code>.</p>
|
||||
<p>So, if you want to include a copyright symbol in your article, you can write:</p>
|
||||
<pre><code>&copy;
|
||||
</code></pre><p>and Markdown will leave it alone. But if you write:</p>
|
||||
<pre><code>AT&T
|
||||
</code></pre><p>Markdown will translate it to:</p>
|
||||
<pre><code>AT&amp;T
|
||||
</code></pre><p>Similarly, because Markdown supports <a href="#html">inline <span class="caps">HTML</span></a>, if you use
|
||||
angle brackets as delimiters for <span class="caps">HTML</span> tags, Markdown will treat them as
|
||||
such. But if you write:</p>
|
||||
<pre><code>4 < 5
|
||||
</code></pre><p>Markdown will translate it to:</p>
|
||||
<pre><code>4 &lt; 5
|
||||
</code></pre><p>However, inside Markdown code spans and blocks, angle brackets and
|
||||
ampersands are <em>always</em> encoded automatically. This makes it easy to use
|
||||
Markdown to write about <span class="caps">HTML</span> code. (As opposed to raw HTML, which is a
|
||||
terrible format for writing about HTML syntax, because every single <code><</code>
|
||||
and <code>&</code> in your example code needs to be escaped.)</p>
|
||||
<hr>
|
||||
<h2 id="block">Block Elements</h2>
|
||||
|
||||
|
||||
<h3 id="p">Paragraphs and Line Breaks</h3>
|
||||
|
||||
<p>A paragraph is simply one or more consecutive lines of text, separated
|
||||
by one or more blank lines. (A blank line is any line that looks like a
|
||||
blank line – a line containing nothing but spaces or tabs is considered
|
||||
blank.) Normal paragraphs should not be indented with spaces or tabs.</p>
|
||||
<p>The implication of the “one or more consecutive lines of text” rule is
|
||||
that Markdown supports “hard-wrapped” text paragraphs. This differs
|
||||
significantly from most other text-to-<span class="caps">HTML</span> formatters (including Movable
|
||||
Type’s “Convert Line Breaks” option) which translate every line break
|
||||
character in a paragraph into a <code><br /></code> tag.</p>
|
||||
<p>When you <em>do</em> want to insert a <code><br /></code> break tag using Markdown, you
|
||||
end a line with two or more spaces, then type return.</p>
|
||||
<p>Yes, this takes a tad more effort to create a <code><br /></code>, but a simplistic
|
||||
“every line break is a <code><br /></code>“ rule wouldn’t work for Markdown.
|
||||
Markdown’s email-style <a href="#blockquote">blockquoting</a> and multi-paragraph <a href="#list">list items</a>
|
||||
work best – and look better – when you format them with hard breaks.</p>
|
||||
<h3 id="header">Headers</h3>
|
||||
|
||||
<p>Markdown supports two styles of headers, <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a> and <a href="http://www.aaronsw.com/2002/atx/">atx</a>.</p>
|
||||
<p>Setext-style headers are “underlined” using equal signs (for first-level
|
||||
headers) and dashes (for second-level headers). For example:</p>
|
||||
<pre><code>This is an H1
|
||||
=============
|
||||
|
||||
This is an H2
|
||||
-------------
|
||||
</code></pre><p>Any number of underlining <code>=</code>‘s or <code>-</code>‘s will work.</p>
|
||||
<p>Atx-style headers use 1-6 hash characters at the start of the line,
|
||||
corresponding to header levels 1-6. For example:</p>
|
||||
<pre><code># This is an H1
|
||||
|
||||
## This is an H2
|
||||
|
||||
###### This is an H6
|
||||
</code></pre><p>Optionally, you may “close” atx-style headers. This is purely
|
||||
cosmetic – you can use this if you think it looks better. The
|
||||
closing hashes don’t even need to match the number of hashes
|
||||
used to open the header. (The number of opening hashes
|
||||
determines the header level.) :</p>
|
||||
<pre><code># This is an H1 #
|
||||
|
||||
## This is an H2 ##
|
||||
|
||||
### This is an H3 ######
|
||||
</code></pre><h3 id="blockquote">Blockquotes</h3>
|
||||
|
||||
<p>Markdown uses email-style <code>></code> characters for blockquoting. If you’re
|
||||
familiar with quoting passages of text in an email message, then you
|
||||
know how to create a blockquote in Markdown. It looks best if you hard
|
||||
wrap the text and put a <code>></code> before every line:</p>
|
||||
<pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
|
||||
> consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
|
||||
> Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
|
||||
>
|
||||
> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
|
||||
> id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre><p>Markdown allows you to be lazy and only put the <code>></code> before the first
|
||||
line of a hard-wrapped paragraph:</p>
|
||||
<pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
|
||||
consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
|
||||
Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
|
||||
|
||||
> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
|
||||
id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre><p>Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
|
||||
adding additional levels of <code>></code>:</p>
|
||||
<pre><code>> This is the first level of quoting.
|
||||
>
|
||||
> > This is nested blockquote.
|
||||
>
|
||||
> Back to the first level.
|
||||
</code></pre><p>Blockquotes can contain other Markdown elements, including headers, lists,
|
||||
and code blocks:</p>
|
||||
<blockquote>
|
||||
<h2 id="this-is-a-header-">This is a header.</h2>
|
||||
<ol>
|
||||
<li>This is the first list item.</li>
|
||||
<li>This is the second list item.</li>
|
||||
</ol>
|
||||
<p>Here’s some example code:</p>
|
||||
<pre><code>return shell_exec("echo $input | $markdown_script");
|
||||
</code></pre></blockquote>
|
||||
<p>Any decent text editor should make email-style quoting easy. For
|
||||
example, with BBEdit, you can make a selection and choose Increase
|
||||
Quote Level from the Text menu.</p>
|
||||
<h3 id="list">Lists</h3>
|
||||
|
||||
<p>Markdown supports ordered (numbered) and unordered (bulleted) lists.</p>
|
||||
<p>Unordered lists use asterisks, pluses, and hyphens – interchangably
|
||||
– as list markers:</p>
|
||||
<pre><code>* Red
|
||||
* Green
|
||||
* Blue
|
||||
</code></pre><p>is equivalent to:</p>
|
||||
<pre><code>+ Red
|
||||
+ Green
|
||||
+ Blue
|
||||
</code></pre><p>and:</p>
|
||||
<pre><code>- Red
|
||||
- Green
|
||||
- Blue
|
||||
</code></pre><p>Ordered lists use numbers followed by periods:</p>
|
||||
<pre><code>1. Bird
|
||||
2. McHale
|
||||
3. Parish
|
||||
</code></pre><p>It’s important to note that the actual numbers you use to mark the
|
||||
list have no effect on the <span class="caps">HTML</span> output Markdown produces. The HTML
|
||||
Markdown produces from the above list is:</p>
|
||||
<pre><code><ol>
|
||||
<li>Bird</li>
|
||||
<li>McHale</li>
|
||||
<li>Parish</li>
|
||||
</ol>
|
||||
</code></pre><p>If you instead wrote the list in Markdown like this:</p>
|
||||
<pre><code>1. Bird
|
||||
1. McHale
|
||||
1. Parish
|
||||
</code></pre><p>or even:</p>
|
||||
<pre><code>3. Bird
|
||||
1. McHale
|
||||
8. Parish
|
||||
</code></pre><p>you’d get the exact same <span class="caps">HTML</span> output. The point is, if you want to,
|
||||
you can use ordinal numbers in your ordered Markdown lists, so that
|
||||
the numbers in your source match the numbers in your published HTML.
|
||||
But if you want to be lazy, you don’t have to.</p>
|
||||
<p>If you do use lazy list numbering, however, you should still start the
|
||||
list with the number 1. At some point in the future, Markdown may support
|
||||
starting ordered lists at an arbitrary number.</p>
|
||||
<p>List markers typically start at the left margin, but may be indented by
|
||||
up to three spaces. List markers must be followed by one or more spaces
|
||||
or a tab.</p>
|
||||
<p>To make lists look nice, you can wrap items with hanging indents:</p>
|
||||
<pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
|
||||
Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
|
||||
viverra nec, fringilla in, laoreet vitae, risus.
|
||||
* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
|
||||
Suspendisse id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre><p>But if you want to be lazy, you don’t have to:</p>
|
||||
<pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
|
||||
Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
|
||||
viverra nec, fringilla in, laoreet vitae, risus.
|
||||
* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
|
||||
Suspendisse id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre><p>If list items are separated by blank lines, Markdown will wrap the
|
||||
items in <code><p></code> tags in the <span class="caps">HTML</span> output. For example, this input:</p>
|
||||
<pre><code>* Bird
|
||||
* Magic
|
||||
</code></pre><p>will turn into:</p>
|
||||
<pre><code><ul>
|
||||
<li>Bird</li>
|
||||
<li>Magic</li>
|
||||
</ul>
|
||||
</code></pre><p>But this:</p>
|
||||
<pre><code>* Bird
|
||||
|
||||
* Magic
|
||||
</code></pre><p>will turn into:</p>
|
||||
<pre><code><ul>
|
||||
<li><p>Bird</p></li>
|
||||
<li><p>Magic</p></li>
|
||||
</ul>
|
||||
</code></pre><p>List items may consist of multiple paragraphs. Each subsequent
|
||||
paragraph in a list item must be indented by either 4 spaces
|
||||
or one tab:</p>
|
||||
<pre><code>1. This is a list item with two paragraphs. Lorem ipsum dolor
|
||||
sit amet, consectetuer adipiscing elit. Aliquam hendrerit
|
||||
mi posuere lectus.
|
||||
|
||||
Vestibulum enim wisi, viverra nec, fringilla in, laoreet
|
||||
vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
|
||||
sit amet velit.
|
||||
|
||||
2. Suspendisse id sem consectetuer libero luctus adipiscing.
|
||||
</code></pre><p>It looks nice if you indent every line of the subsequent
|
||||
paragraphs, but here again, Markdown will allow you to be lazy:</p>
|
||||
<pre><code>* This is a list item with two paragraphs.
|
||||
|
||||
This is the second paragraph in the list item. You're
|
||||
only required to indent the first line. Lorem ipsum dolor
|
||||
sit amet, consectetuer adipiscing elit.
|
||||
|
||||
* Another item in the same list.
|
||||
</code></pre><p>To put a blockquote within a list item, the blockquote’s <code>></code>
|
||||
delimiters need to be indented:</p>
|
||||
<pre><code>* A list item with a blockquote:
|
||||
|
||||
> This is a blockquote
|
||||
> inside a list item.
|
||||
</code></pre><p>To put a code block within a list item, the code block needs
|
||||
to be indented <em>twice</em> – 8 spaces or two tabs:</p>
|
||||
<pre><code>* A list item with a code block:
|
||||
|
||||
<code goes here>
|
||||
</code></pre><p>It’s worth noting that it’s possible to trigger an ordered list by
|
||||
accident, by writing something like this:</p>
|
||||
<pre><code>1986. What a great season.
|
||||
</code></pre><p>In other words, a <em>number-period-space</em> sequence at the beginning of a
|
||||
line. To avoid this, you can backslash-escape the period:</p>
|
||||
<pre><code>1986\. What a great season.
|
||||
</code></pre><h3 id="precode">Code Blocks</h3>
|
||||
|
||||
<p>Pre-formatted code blocks are used for writing about programming or
|
||||
markup source code. Rather than forming normal paragraphs, the lines
|
||||
of a code block are interpreted literally. Markdown wraps a code block
|
||||
in both <code><pre></code> and <code><code></code> tags.</p>
|
||||
<p>To produce a code block in Markdown, simply indent every line of the
|
||||
block by at least 4 spaces or 1 tab. For example, given this input:</p>
|
||||
<pre><code>This is a normal paragraph:
|
||||
|
||||
This is a code block.
|
||||
</code></pre><p>Markdown will generate:</p>
|
||||
<pre><code><p>This is a normal paragraph:</p>
|
||||
|
||||
<pre><code>This is a code block.
|
||||
</code></pre>
|
||||
</code></pre><p>One level of indentation – 4 spaces or 1 tab – is removed from each
|
||||
line of the code block. For example, this:</p>
|
||||
<pre><code>Here is an example of AppleScript:
|
||||
|
||||
tell application "Foo"
|
||||
beep
|
||||
end tell
|
||||
</code></pre><p>will turn into:</p>
|
||||
<pre><code><p>Here is an example of AppleScript:</p>
|
||||
|
||||
<pre><code>tell application "Foo"
|
||||
beep
|
||||
end tell
|
||||
</code></pre>
|
||||
</code></pre><p>A code block continues until it reaches a line that is not indented
|
||||
(or the end of the article).</p>
|
||||
<p>Within a code block, ampersands (<code>&</code>) and angle brackets (<code><</code> and <code>></code>)
|
||||
are automatically converted into <span class="caps">HTML</span> entities. This makes it very
|
||||
easy to include example HTML source code using Markdown – just paste
|
||||
it and indent it, and Markdown will handle the hassle of encoding the
|
||||
ampersands and angle brackets. For example, this:</p>
|
||||
<pre><code> <div class="footer">
|
||||
&copy; 2004 Foo Corporation
|
||||
</div>
|
||||
</code></pre><p>will turn into:</p>
|
||||
<pre><code><pre><code>&lt;div class="footer"&gt;
|
||||
&amp;copy; 2004 Foo Corporation
|
||||
&lt;/div&gt;
|
||||
</code></pre>
|
||||
</code></pre><p>Regular Markdown syntax is not processed within code blocks. E.g.,
|
||||
asterisks are just literal asterisks within a code block. This means
|
||||
it’s also easy to use Markdown to write about Markdown’s own syntax.</p>
|
||||
<h3 id="hr">Horizontal Rules</h3>
|
||||
|
||||
<p>You can produce a horizontal rule tag (<code><hr /></code>) by placing three or
|
||||
more hyphens, asterisks, or underscores on a line by themselves. If you
|
||||
wish, you may use spaces between the hyphens or asterisks. Each of the
|
||||
following lines will produce a horizontal rule:</p>
|
||||
<pre><code>* * *
|
||||
|
||||
***
|
||||
|
||||
*****
|
||||
|
||||
- - -
|
||||
|
||||
---------------------------------------
|
||||
</code></pre><hr>
|
||||
<h2 id="span">Span Elements</h2>
|
||||
|
||||
<h3 id="link">Links</h3>
|
||||
|
||||
<p>Markdown supports two style of links: <em>inline</em> and <em>reference</em>.</p>
|
||||
<p>In both styles, the link text is delimited by [square brackets].</p>
|
||||
<p>To create an inline link, use a set of regular parentheses immediately
|
||||
after the link text’s closing square bracket. Inside the parentheses,
|
||||
put the <span class="caps">URL</span> where you want the link to point, along with an <em>optional</em>
|
||||
title for the link, surrounded in quotes. For example:</p>
|
||||
<pre><code>This is [an example](http://example.com/ "Title") inline link.
|
||||
|
||||
[This link](http://example.net/) has no title attribute.
|
||||
</code></pre><p>Will produce:</p>
|
||||
<pre><code><p>This is <a href="http://example.com/" title="Title">
|
||||
an example</a> inline link.</p>
|
||||
|
||||
<p><a href="http://example.net/">This link</a> has no
|
||||
title attribute.</p>
|
||||
</code></pre><p>If you’re referring to a local resource on the same server, you can
|
||||
use relative paths:</p>
|
||||
<pre><code>See my [About](/about/) page for details.
|
||||
</code></pre><p>Reference-style links use a second set of square brackets, inside
|
||||
which you place a label of your choosing to identify the link:</p>
|
||||
<pre><code>This is [an example][id] reference-style link.
|
||||
</code></pre><p>You can optionally use a space to separate the sets of brackets:</p>
|
||||
<pre><code>This is [an example] [id] reference-style link.
|
||||
</code></pre><p>Then, anywhere in the document, you define your link label like this,
|
||||
on a line by itself:</p>
|
||||
<pre><code>[id]: http://example.com/ "Optional Title Here"
|
||||
</code></pre><p>That is:</p>
|
||||
<ul>
|
||||
<li>Square brackets containing the link identifier (optionally
|
||||
indented from the left margin using up to three spaces);</li>
|
||||
<li>followed by a colon;</li>
|
||||
<li>followed by one or more spaces (or tabs);</li>
|
||||
<li>followed by the <span class="caps">URL</span> for the link;</li>
|
||||
<li>optionally followed by a title attribute for the link, enclosed
|
||||
in double or single quotes, or enclosed in parentheses.</li>
|
||||
</ul>
|
||||
<p>The following three link definitions are equivalent:</p>
|
||||
<p> <a href="http://example.com/" title="Optional Title Here">foo</a>: <a href="http://example.com/">http://example.com/</a> ‘Optional Title Here’</p>
|
||||
<p><strong>Note:</strong> There is a known bug in Markdown.pl 1.0.1 which prevents
|
||||
single quotes from being used to delimit link titles.</p>
|
||||
<p>The link <span class="caps">URL</span> may, optionally, be surrounded by angle brackets:</p>
|
||||
<pre><code>[id]: <http://example.com/> "Optional Title Here"
|
||||
</code></pre><p>You can put the title attribute on the next line and use extra spaces
|
||||
or tabs for padding, which tends to look better with longer URLs:</p>
|
||||
<pre><code>[id]: http://example.com/longish/path/to/resource/here
|
||||
"Optional Title Here"
|
||||
</code></pre><p>Link definitions are only used for creating links during Markdown
|
||||
processing, and are stripped from your document in the <span class="caps">HTML</span> output.</p>
|
||||
<p>Link definition names may consist of letters, numbers, spaces, and
|
||||
punctuation – but they are <em>not</em> case sensitive. E.g. these two links:</p>
|
||||
<p> [link text][a]
|
||||
[link text][A]</p>
|
||||
<p>are equivalent.</p>
|
||||
<p>The <em>implicit link name</em> shortcut allows you to omit the name of the
|
||||
link, in which case the link text itself is used as the name.
|
||||
Just use an empty set of square brackets – e.g., to link the word
|
||||
“Google” to the google.com web site, you could simply write:</p>
|
||||
<p> <a href="http://google.com/">Google</a></p>
|
||||
<p>And then define the link:</p>
|
||||
<p>Because link names may contain spaces, this shortcut even works for
|
||||
multiple words in the link text:</p>
|
||||
<p> Visit <a href="http://daringfireball.net/">Daring Fireball</a> for more information.</p>
|
||||
<p>And then define the link:</p>
|
||||
<p>Link definitions can be placed anywhere in your Markdown document. I
|
||||
tend to put them immediately after each paragraph in which they’re
|
||||
used, but if you want, you can put them all at the end of your
|
||||
document, sort of like footnotes.</p>
|
||||
<p>Here’s an example of reference links in action:</p>
|
||||
<pre><code>I get 10 times more traffic from [Google] [1] than from
|
||||
[Yahoo] [2] or [MSN] [3].
|
||||
|
||||
[1]: http://google.com/ "Google"
|
||||
[2]: http://search.yahoo.com/ "Yahoo Search"
|
||||
[3]: http://search.msn.com/ "MSN Search"
|
||||
</code></pre><p>Using the implicit link name shortcut, you could instead write:</p>
|
||||
<pre><code>I get 10 times more traffic from [Google][] than from
|
||||
[Yahoo][] or [MSN][].
|
||||
|
||||
[google]: http://google.com/ "Google"
|
||||
[yahoo]: http://search.yahoo.com/ "Yahoo Search"
|
||||
[msn]: http://search.msn.com/ "MSN Search"
|
||||
</code></pre><p>Both of the above examples will produce the following <span class="caps">HTML</span> output:</p>
|
||||
<pre><code><p>I get 10 times more traffic from <a href="http://google.com/"
|
||||
title="Google">Google</a> than from
|
||||
<a href="http://search.yahoo.com/" title="Yahoo Search">Yahoo</a>
|
||||
or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</p>
|
||||
</code></pre><p>For comparison, here is the same paragraph written using
|
||||
Markdown’s inline link style:</p>
|
||||
<pre><code>I get 10 times more traffic from [Google](http://google.com/ "Google")
|
||||
than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
|
||||
[MSN](http://search.msn.com/ "MSN Search").
|
||||
</code></pre><p>The point of reference-style links is not that they’re easier to
|
||||
write. The point is that with reference-style links, your document
|
||||
source is vastly more readable. Compare the above examples: using
|
||||
reference-style links, the paragraph itself is only 81 characters
|
||||
long; with inline-style links, it’s 176 characters; and as raw <span class="caps">HTML</span>,
|
||||
it’s 234 characters. In the raw HTML, there’s more markup than there
|
||||
is text.</p>
|
||||
<p>With Markdown’s reference-style links, a source document much more
|
||||
closely resembles the final output, as rendered in a browser. By
|
||||
allowing you to move the markup-related metadata out of the paragraph,
|
||||
you can add links without interrupting the narrative flow of your prose.</p>
|
||||
<h3 id="em">Emphasis</h3>
|
||||
|
||||
<p>Markdown treats asterisks (<code>*</code>) and underscores (<code>_</code>) as indicators of
|
||||
emphasis. Text wrapped with one <code>*</code> or <code>_</code> will be wrapped with an
|
||||
<span class="caps">HTML</span> <code><em></code> tag; double <code>*</code>‘s or <code>_</code>‘s will be wrapped with an <span class="caps">HTML</span>
|
||||
<code><strong></code> tag. E.g., this input:</p>
|
||||
<pre><code>*single asterisks*
|
||||
|
||||
_single underscores_
|
||||
|
||||
**double asterisks**
|
||||
|
||||
__double underscores__
|
||||
</code></pre><p>will produce:</p>
|
||||
<pre><code><em>single asterisks</em>
|
||||
|
||||
<em>single underscores</em>
|
||||
|
||||
<strong>double asterisks</strong>
|
||||
|
||||
<strong>double underscores</strong>
|
||||
</code></pre><p>You can use whichever style you prefer; the lone restriction is that
|
||||
the same character must be used to open and close an emphasis span.</p>
|
||||
<p>Emphasis can be used in the middle of a word:</p>
|
||||
<pre><code>un*frigging*believable
|
||||
</code></pre><p>But if you surround an <code>*</code> or <code>_</code> with spaces, it’ll be treated as a
|
||||
literal asterisk or underscore.</p>
|
||||
<p>To produce a literal asterisk or underscore at a position where it
|
||||
would otherwise be used as an emphasis delimiter, you can backslash
|
||||
escape it:</p>
|
||||
<pre><code>\*this text is surrounded by literal asterisks\*
|
||||
</code></pre><h3 id="code">Code</h3>
|
||||
|
||||
<p>To indicate a span of code, wrap it with backtick quotes (<code>` </code>).
|
||||
Unlike a pre-formatted code block, a code span indicates code within a
|
||||
normal paragraph. For example:</p>
|
||||
<pre><code>Use the `printf()` function.
|
||||
</code></pre><p>will produce:</p>
|
||||
<pre><code><p>Use the <code>printf()</code> function.</p>
|
||||
</code></pre><p>To include a literal backtick character within a code span, you can use
|
||||
multiple backticks as the opening and closing delimiters:</p>
|
||||
<pre><code>``There is a literal backtick (`) here.``
|
||||
</code></pre><p>which will produce this:</p>
|
||||
<pre><code><p><code>There is a literal backtick (`) here.</code></p>
|
||||
</code></pre><p>The backtick delimiters surrounding a code span may include spaces –
|
||||
one after the opening, one before the closing. This allows you to place
|
||||
literal backtick characters at the beginning or end of a code span:</p>
|
||||
<p> A single backtick in a code span: <code>` </code></p>
|
||||
<p> A backtick-delimited string in a code span: <code>`foo` </code></p>
|
||||
<p>will produce:</p>
|
||||
<p>A single backtick in a code span: <code>`</code></p>
|
||||
|
||||
<p>A backtick-delimited string in a code span: <code><code>foo</code></code></p>
|
||||
|
||||
<p>With a code span, ampersands and angle brackets are encoded as <span class="caps">HTML</span>
|
||||
entities automatically, which makes it easy to include example HTML
|
||||
tags. Markdown will turn this:</p>
|
||||
<pre><code>Please don't use any `<blink>` tags.
|
||||
</code></pre><p>into:</p>
|
||||
<pre><code><p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
|
||||
</code></pre><p>You can write this:</p>
|
||||
<pre><code>`&#8212;` is the decimal-encoded equivalent of `&mdash;`.
|
||||
</code></pre><p>to produce:</p>
|
||||
<pre><code><p><code>&amp;#8212;</code> is the decimal-encoded
|
||||
equivalent of <code>&amp;mdash;</code>.</p>
|
||||
</code></pre><h3 id="img">Images</h3>
|
||||
|
||||
<p>Admittedly, it’s fairly difficult to devise a “natural” syntax for
|
||||
placing images into a plain text document format.</p>
|
||||
<p>Markdown uses an image syntax that is intended to resemble the syntax
|
||||
for links, allowing for two styles: <em>inline</em> and <em>reference</em>.</p>
|
||||
<p>Inline image syntax looks like this:</p>
|
||||
<pre><code>
|
||||
|
||||
|
||||
</code></pre><p>That is:</p>
|
||||
<ul>
|
||||
<li>An exclamation mark: <code>!</code>;</li>
|
||||
<li>followed by a set of square brackets, containing the <code>alt</code>
|
||||
attribute text for the image;</li>
|
||||
<li>followed by a set of parentheses, containing the <span class="caps">URL</span> or path to
|
||||
the image, and an optional <code>title</code> attribute enclosed in double
|
||||
or single quotes.</li>
|
||||
</ul>
|
||||
<p>Reference-style image syntax looks like this:</p>
|
||||
<pre><code>![Alt text][id]
|
||||
</code></pre><p>Where “id” is the name of a defined image reference. Image references
|
||||
are defined using syntax identical to link references:</p>
|
||||
<pre><code>[id]: url/to/image "Optional title attribute"
|
||||
</code></pre><p>As of this writing, Markdown has no syntax for specifying the
|
||||
dimensions of an image; if this is important to you, you can simply
|
||||
use regular <span class="caps">HTML</span> <code><img></code> tags.</p>
|
||||
<hr>
|
||||
<h2 id="misc">Miscellaneous</h2>
|
||||
|
||||
<h3 id="autolink">Automatic Links</h3>
|
||||
|
||||
<p>Markdown supports a shortcut style for creating “automatic” links for URLs and email addresses: simply surround the <span class="caps">URL</span> or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:</p>
|
||||
<pre><code><http://example.com/>
|
||||
</code></pre><p>Markdown will turn this into:</p>
|
||||
<pre><code><a href="http://example.com/">http://example.com/</a>
|
||||
</code></pre><p>Automatic links for email addresses work similarly, except that
|
||||
Markdown will also perform a bit of randomized decimal and hex
|
||||
entity-encoding to help obscure your address from address-harvesting
|
||||
spambots. For example, Markdown will turn this:</p>
|
||||
<pre><code><address@example.com>
|
||||
</code></pre><p>into something like this:</p>
|
||||
<pre><code><a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
|
||||
&#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;
|
||||
&#109;">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;
|
||||
&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>
|
||||
</code></pre><p>which will render in a browser as a clickable link to “address@example.com”.</p>
|
||||
<p>(This sort of entity-encoding trick will indeed fool many, if not
|
||||
most, address-harvesting bots, but it definitely won’t fool all of
|
||||
them. It’s better than nothing, but an address published in this way
|
||||
will probably eventually start receiving spam.)</p>
|
||||
<h3 id="backslash">Backslash Escapes</h3>
|
||||
|
||||
<p>Markdown allows you to use backslash escapes to generate literal
|
||||
characters which would otherwise have special meaning in Markdown’s
|
||||
formatting syntax. For example, if you wanted to surround a word
|
||||
with literal asterisks (instead of an <span class="caps">HTML</span> <code><em></code> tag), you can use
|
||||
backslashes before the asterisks, like this:</p>
|
||||
<pre><code>\*literal asterisks\*
|
||||
</code></pre><p>Markdown provides backslash escapes for the following characters:</p>
|
||||
<pre><code>\ backslash
|
||||
` backtick
|
||||
* asterisk
|
||||
_ underscore
|
||||
{} curly braces
|
||||
[] square brackets
|
||||
() parentheses
|
||||
# hash mark
|
||||
</code></pre><ul>
|
||||
<li>plus sign</li>
|
||||
</ul>
|
||||
<ul>
|
||||
<li>minus sign (hyphen)
|
||||
. dot
|
||||
! exclamation mark</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</section>
|
||||
<footer class="wrap">
|
||||
<div class="left">Powered by Angular, Bootsrap, Gulp and more...</div>
|
||||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 320 KiB |
|
|
@ -1,78 +0,0 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<meta name="keywords" content="admin,dashboard,template,angular,bootstrap,blur,panel,html,css,javascript">
|
||||
<title>BlurAdmin documentation - A red herring</title>
|
||||
<link rel="alternate" href="http://localhost:8080/feed.xml" type="application/rss+xml" title="Ramblings of an immor(t)al demigod">
|
||||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900italic,900|Anonymous+Pro:400,700,400italic,700italic&subset=latin,greek,greek-ext,vietnamese,cyrillic-ext,latin-ext,cyrillic">
|
||||
<link rel="stylesheet" href="/blur-admin/css/main.css">
|
||||
<link rel="shortcut icon" href="/blur-admin/images/favicon.png">
|
||||
</head>
|
||||
<body>
|
||||
<div class="container">
|
||||
<div class="nav-main">
|
||||
<div class="wrap"><a href="/blur-admin/" class="nav-home"><img src="/blur-admin/images/blur-admin-logo.png" width="36" height="36" class="nav-logo"> <span class="blur-label">Blur</span>Admin</a>
|
||||
<ul class="nav-site nav-site-internal">
|
||||
<li><a href="/blur-admin/">Home</a></li>
|
||||
<li><a href="/blur-admin/articles/red-herring/" class="active">Docs</a></li>
|
||||
</ul><span class="nav-docs-right">Need some help? Let us know! <a href="mailto:help@akveo.com">help@akveo.com</a></span>
|
||||
</div>
|
||||
</div>
|
||||
<section class="content wrap documentationContent">
|
||||
<div class="nav-docs">
|
||||
<div class="nav-docs section">
|
||||
<h3>Second Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/red-herring/" class="active">A red herring</a></li>
|
||||
<li><a href="/blur-admin/articles/bamboo-cutter/">Taketori Monogatari</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>First Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/another-test/">Code and stuff!</a></li>
|
||||
<li><a href="/blur-admin/articles/hello-world/">README</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="nav-docs section">
|
||||
<h3>Third Group</h3>
|
||||
<ul>
|
||||
<li><a href="/blur-admin/articles/markdown-syntax/">Markdown syntax</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="inner-content">
|
||||
<h1>A red herring</h1>
|
||||
<div class="subHeader"></div><p>A long time ago, when the world was young – someone put some food on their tongue.
|
||||
They tasted the food, and thought it was nice. Most fruit liked it – but banana’s thought twice.</p>
|
||||
<p><span class="more"></span></p>
|
||||
<p>They held a meeting at quarter past eight.
|
||||
Whilst the human’s were getting home late.
|
||||
They decided they didn’t want to be eaten they said:
|
||||
“No way, we’re not going to be beaten”.</p>
|
||||
<p>So time went by, and human’s got old.
|
||||
Banana’s got ready, for their prophets had told.
|
||||
That soon shall come the dawn of war.
|
||||
Where humans will rule the earth no more.</p>
|
||||
<p>The humans knew not of the evil banana’s plans.
|
||||
They made their cars, guitars and aluminum cans.
|
||||
And the banana’s began to take over the east.
|
||||
While humans knew not, and kept having their feast.</p>
|
||||
<p>But time has run out, no more hiding there can be.
|
||||
Or else the banana’s will kill you and me.
|
||||
We must take up arms, and fight to the end.
|
||||
Because, believe it or not, a banana is not a friend.</p>
|
||||
<p><img src="/blur-admin/articles/red-herring/banana.png" alt="a banana"></p>
|
||||
|
||||
</div>
|
||||
</section>
|
||||
<footer class="wrap">
|
||||
<div class="left">Powered by Angular, Bootsrap, Gulp and more...</div>
|
||||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
|
|
@ -90,5 +90,10 @@
|
|||
<div class="right">© 2015–2016 Akveo LLC<br />Documentation licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</div>
|
||||
</footer>
|
||||
</div><a href="https://github.com/akveo/blur-admin"><img style="position: fixed; top: 0; right: 0; border: 0; z-index: 1000;" src="https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"></a>
|
||||
<script>
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q || []).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
|
||||
ga('create', 'UA-61945105-3', 'auto');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Reference in New Issue