diff options
author | Volpeon <git@volpeon.ink> | 2022-06-11 16:26:47 +0200 |
---|---|---|
committer | Volpeon <git@volpeon.ink> | 2022-06-11 16:26:47 +0200 |
commit | 604dcfe244ab8f6913db9dec3de5796ad32f43f5 (patch) | |
tree | fc56d5965f3e263937efd3d42196afe1359299cb /content/notebook | |
parent | Re-implemented design via iro-design (diff) | |
download | volpeon.ink-604dcfe244ab8f6913db9dec3de5796ad32f43f5.tar.gz volpeon.ink-604dcfe244ab8f6913db9dec3de5796ad32f43f5.tar.bz2 volpeon.ink-604dcfe244ab8f6913db9dec3de5796ad32f43f5.zip |
Removed private section, various improvements
Diffstat (limited to 'content/notebook')
-rw-r--r-- | content/notebook/index.md | 6 | ||||
-rw-r--r-- | content/notebook/scrap/design-test.md | 315 | ||||
-rw-r--r-- | content/notebook/scrap/index.md | 6 |
3 files changed, 327 insertions, 0 deletions
diff --git a/content/notebook/index.md b/content/notebook/index.md new file mode 100644 index 0000000..8d58834 --- /dev/null +++ b/content/notebook/index.md | |||
@@ -0,0 +1,6 @@ | |||
1 | --- | ||
2 | title: Notebook | ||
3 | position: 3 | ||
4 | list_limit: 4 | ||
5 | feed: true | ||
6 | --- | ||
diff --git a/content/notebook/scrap/design-test.md b/content/notebook/scrap/design-test.md new file mode 100644 index 0000000..2367513 --- /dev/null +++ b/content/notebook/scrap/design-test.md | |||
@@ -0,0 +1,315 @@ | |||
1 | --- | ||
2 | title: Design Test | ||
3 | --- | ||
4 | |||
5 | - [Overview](#overview) | ||
6 | - [Philosophy](#philosophy) | ||
7 | - [Block Elements](#block-elements) | ||
8 | - [Paragraphs and Line Breaks](#paragraphs-and-line-breaks) | ||
9 | - [Headers](#headers) | ||
10 | - [Blockquotes](#blockquotes) | ||
11 | - [Lists](#lists) | ||
12 | - [Code Blocks](#code-blocks) | ||
13 | - [Span Elements](#span-elements) | ||
14 | - [Links](#links) | ||
15 | - [Emphasis](#emphasis) | ||
16 | - [Code](#code) | ||
17 | |||
18 | ---- | ||
19 | |||
20 | ## Overview | ||
21 | |||
22 | ### Philosophy | ||
23 | |||
24 | Markdown is intended to be as easy-to-read and easy-to-write as is feasible. | ||
25 | |||
26 | Readability, however, is emphasized above all else. A Markdown-formatted | ||
27 | document should be publishable as-is, as plain text, without looking | ||
28 | like it's been marked up with tags or formatting instructions. While | ||
29 | Markdown's syntax has been influenced by several existing text-to-HTML | ||
30 | filters -- including [Setext](http://docutils.sourceforge.net/mirror/setext.html), [atx](http://www.aaronsw.com/2002/atx/), [Textile](http://textism.com/tools/textile/), [reStructuredText](http://docutils.sourceforge.net/rst.html), | ||
31 | [Grutatext](http://www.triptico.com/software/grutatxt.html), and [EtText](http://ettext.taint.org/doc/) -- the single biggest source of | ||
32 | inspiration for Markdown's syntax is the format of plain text email. | ||
33 | |||
34 | ## Block Elements | ||
35 | |||
36 | ### Paragraphs and Line Breaks | ||
37 | |||
38 | A paragraph is simply one or more consecutive lines of text, separated | ||
39 | by one or more blank lines. (A blank line is any line that looks like a | ||
40 | blank line -- a line containing nothing but spaces or tabs is considered | ||
41 | blank.) Normal paragraphs should not be indented with spaces or tabs. | ||
42 | |||
43 | The implication of the "one or more consecutive lines of text" rule is | ||
44 | that Markdown supports "hard-wrapped" text paragraphs. This differs | ||
45 | significantly from most other text-to-HTML formatters (including Movable | ||
46 | Type's "Convert Line Breaks" option) which translate every line break | ||
47 | character in a paragraph into a `<br />` tag. | ||
48 | |||
49 | When you *do* want to insert a `<br />` break tag using Markdown, you | ||
50 | end a line with two or more spaces, then type return. | ||
51 | |||
52 | ### Headers | ||
53 | |||
54 | Markdown supports two styles of headers, [Setext] [1] and [atx] [2]. | ||
55 | |||
56 | Optionally, you may "close" atx-style headers. This is purely | ||
57 | cosmetic -- you can use this if you think it looks better. The | ||
58 | closing hashes don't even need to match the number of hashes | ||
59 | used to open the header. (The number of opening hashes | ||
60 | determines the header level.) | ||
61 | |||
62 | |||
63 | ### Blockquotes | ||
64 | |||
65 | Markdown uses email-style `>` characters for blockquoting. If you're | ||
66 | familiar with quoting passages of text in an email message, then you | ||
67 | know how to create a blockquote in Markdown. It looks best if you hard | ||
68 | wrap the text and put a `>` before every line: | ||
69 | |||
70 | > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet, | ||
71 | > consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus. | ||
72 | > Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus. | ||
73 | > | ||
74 | > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse | ||
75 | > id sem consectetuer libero luctus adipiscing. | ||
76 | |||
77 | Markdown allows you to be lazy and only put the `>` before the first | ||
78 | line of a hard-wrapped paragraph: | ||
79 | |||
80 | > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet, | ||
81 | consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus. | ||
82 | Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus. | ||
83 | |||
84 | > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse | ||
85 | id sem consectetuer libero luctus adipiscing. | ||
86 | |||
87 | Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by | ||
88 | adding additional levels of `>`: | ||
89 | |||
90 | > This is the first level of quoting. | ||
91 | > | ||
92 | > > This is nested blockquote. | ||
93 | > | ||
94 | > Back to the first level. | ||
95 | |||
96 | Blockquotes can contain other Markdown elements, including headers, lists, | ||
97 | and code blocks: | ||
98 | |||
99 | > ## This is a header. | ||
100 | > | ||
101 | > 1. This is the first list item. | ||
102 | > 2. This is the second list item. | ||
103 | > | ||
104 | > Here's some example code: | ||
105 | > | ||
106 | > return shell_exec("echo $input | $markdown_script"); | ||
107 | |||
108 | Any decent text editor should make email-style quoting easy. For | ||
109 | example, with BBEdit, you can make a selection and choose Increase | ||
110 | Quote Level from the Text menu. | ||
111 | |||
112 | |||
113 | ### Lists | ||
114 | |||
115 | Markdown supports ordered (numbered) and unordered (bulleted) lists. | ||
116 | |||
117 | Unordered lists use asterisks, pluses, and hyphens -- interchangably | ||
118 | -- as list markers: | ||
119 | |||
120 | * Red | ||
121 | * Green | ||
122 | * Blue | ||
123 | |||
124 | is equivalent to: | ||
125 | |||
126 | + Red | ||
127 | + Green | ||
128 | + Blue | ||
129 | |||
130 | and: | ||
131 | |||
132 | - Red | ||
133 | - Green | ||
134 | - Blue | ||
135 | |||
136 | Ordered lists use numbers followed by periods: | ||
137 | |||
138 | 1. Bird | ||
139 | 2. McHale | ||
140 | 3. Parish | ||
141 | |||
142 | It's important to note that the actual numbers you use to mark the | ||
143 | list have no effect on the HTML output Markdown produces. The HTML | ||
144 | Markdown produces from the above list is: | ||
145 | |||
146 | If you instead wrote the list in Markdown like this: | ||
147 | |||
148 | 1. Bird | ||
149 | 1. McHale | ||
150 | 1. Parish | ||
151 | |||
152 | or even: | ||
153 | |||
154 | 3. Bird | ||
155 | 1. McHale | ||
156 | 8. Parish | ||
157 | |||
158 | you'd get the exact same HTML output. The point is, if you want to, | ||
159 | you can use ordinal numbers in your ordered Markdown lists, so that | ||
160 | the numbers in your source match the numbers in your published HTML. | ||
161 | But if you want to be lazy, you don't have to. | ||
162 | |||
163 | To make lists look nice, you can wrap items with hanging indents: | ||
164 | |||
165 | * Lorem ipsum dolor sit amet, consectetuer adipiscing elit. | ||
166 | Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi, | ||
167 | viverra nec, fringilla in, laoreet vitae, risus. | ||
168 | * Donec sit amet nisl. Aliquam semper ipsum sit amet velit. | ||
169 | Suspendisse id sem consectetuer libero luctus adipiscing. | ||
170 | |||
171 | But if you want to be lazy, you don't have to: | ||
172 | |||
173 | * Lorem ipsum dolor sit amet, consectetuer adipiscing elit. | ||
174 | Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi, | ||
175 | viverra nec, fringilla in, laoreet vitae, risus. | ||
176 | * Donec sit amet nisl. Aliquam semper ipsum sit amet velit. | ||
177 | Suspendisse id sem consectetuer libero luctus adipiscing. | ||
178 | |||
179 | List items may consist of multiple paragraphs. Each subsequent | ||
180 | paragraph in a list item must be indented by either 4 spaces | ||
181 | or one tab: | ||
182 | |||
183 | 1. This is a list item with two paragraphs. Lorem ipsum dolor | ||
184 | sit amet, consectetuer adipiscing elit. Aliquam hendrerit | ||
185 | mi posuere lectus. | ||
186 | |||
187 | Vestibulum enim wisi, viverra nec, fringilla in, laoreet | ||
188 | vitae, risus. Donec sit amet nisl. Aliquam semper ipsum | ||
189 | sit amet velit. | ||
190 | |||
191 | 2. Suspendisse id sem consectetuer libero luctus adipiscing. | ||
192 | |||
193 | It looks nice if you indent every line of the subsequent | ||
194 | paragraphs, but here again, Markdown will allow you to be | ||
195 | lazy: | ||
196 | |||
197 | * This is a list item with two paragraphs. | ||
198 | |||
199 | This is the second paragraph in the list item. You're | ||
200 | only required to indent the first line. Lorem ipsum dolor | ||
201 | sit amet, consectetuer adipiscing elit. | ||
202 | |||
203 | * Another item in the same list. | ||
204 | |||
205 | To put a blockquote within a list item, the blockquote's `>` | ||
206 | delimiters need to be indented: | ||
207 | |||
208 | * A list item with a blockquote: | ||
209 | |||
210 | > This is a blockquote | ||
211 | > inside a list item. | ||
212 | |||
213 | To put a code block within a list item, the code block needs | ||
214 | to be indented *twice* -- 8 spaces or two tabs: | ||
215 | |||
216 | * A list item with a code block: | ||
217 | |||
218 | <code goes here> | ||
219 | |||
220 | ### Code Blocks | ||
221 | |||
222 | Pre-formatted code blocks are used for writing about programming or | ||
223 | markup source code. Rather than forming normal paragraphs, the lines | ||
224 | of a code block are interpreted literally. Markdown wraps a code block | ||
225 | in both `<pre>` and `<code>` tags. | ||
226 | |||
227 | To produce a code block in Markdown, simply indent every line of the | ||
228 | block by at least 4 spaces or 1 tab. | ||
229 | |||
230 | This is a normal paragraph: | ||
231 | |||
232 | This is a code block. | ||
233 | |||
234 | Here is an example of AppleScript: | ||
235 | |||
236 | tell application "Foo" | ||
237 | beep | ||
238 | end tell | ||
239 | |||
240 | A code block continues until it reaches a line that is not indented | ||
241 | (or the end of the article). | ||
242 | |||
243 | Within a code block, ampersands (`&`) and angle brackets (`<` and `>`) | ||
244 | are automatically converted into HTML entities. This makes it very | ||
245 | easy to include example HTML source code using Markdown -- just paste | ||
246 | it and indent it, and Markdown will handle the hassle of encoding the | ||
247 | ampersands and angle brackets. For example, this: | ||
248 | |||
249 | <div class="footer"> | ||
250 | © 2004 Foo Corporation | ||
251 | </div> | ||
252 | |||
253 | Regular Markdown syntax is not processed within code blocks. E.g., | ||
254 | asterisks are just literal asterisks within a code block. This means | ||
255 | it's also easy to use Markdown to write about Markdown's own syntax. | ||
256 | |||
257 | ``` | ||
258 | tell application "Foo" | ||
259 | beep | ||
260 | end tell | ||
261 | ``` | ||
262 | |||
263 | ## Span Elements | ||
264 | |||
265 | ### Links | ||
266 | |||
267 | Markdown supports two style of links: *inline* and *reference*. | ||
268 | |||
269 | In both styles, the link text is delimited by [square brackets]. | ||
270 | |||
271 | To create an inline link, use a set of regular parentheses immediately | ||
272 | after the link text's closing square bracket. Inside the parentheses, | ||
273 | put the URL where you want the link to point, along with an *optional* | ||
274 | title for the link, surrounded in quotes. For example: | ||
275 | |||
276 | This is [an example](http://example.com/) inline link. | ||
277 | |||
278 | [This link](http://example.net/) has no title attribute. | ||
279 | |||
280 | ### Emphasis | ||
281 | |||
282 | Markdown treats asterisks (`*`) and underscores (`_`) as indicators of | ||
283 | emphasis. Text wrapped with one `*` or `_` will be wrapped with an | ||
284 | HTML `<em>` tag; double `*`'s or `_`'s will be wrapped with an HTML | ||
285 | `<strong>` tag. E.g., this input: | ||
286 | |||
287 | *single asterisks* | ||
288 | |||
289 | _single underscores_ | ||
290 | |||
291 | **double asterisks** | ||
292 | |||
293 | __double underscores__ | ||
294 | |||
295 | ### Code | ||
296 | |||
297 | To indicate a span of code, wrap it with backtick quotes (`` ` ``). | ||
298 | Unlike a pre-formatted code block, a code span indicates code within a | ||
299 | normal paragraph. For example: | ||
300 | |||
301 | Use the `printf()` function. | ||
302 | |||
303 | --- | ||
304 | |||
305 | # Headline 1 | ||
306 | |||
307 | ## Headline 2 | ||
308 | |||
309 | ### Headline 3 | ||
310 | |||
311 | #### Headline 4 | ||
312 | |||
313 | ##### Headline 5 | ||
314 | |||
315 | ###### Headline 6 | ||
diff --git a/content/notebook/scrap/index.md b/content/notebook/scrap/index.md new file mode 100644 index 0000000..4cc3c2e --- /dev/null +++ b/content/notebook/scrap/index.md | |||
@@ -0,0 +1,6 @@ | |||
1 | --- | ||
2 | title: Scrap | ||
3 | position: 100 | ||
4 | list_read_indicators: true | ||
5 | feed: true | ||
6 | --- | ||