rails_markdown_templates 1.0.0 → 1.0.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +9 -4
- data/lib/rails_markdown_templates/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 7db5971722bda0fd05c0f21bea0f11dd03129cdf
|
|
4
|
+
data.tar.gz: bf94607a28f7b2ce017954640e04502881e5c1b8
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 9f2c65a700b914015d61545798f5db12275faee4f4617fe1638e351bd3fedbfec5b354d0a53851cd4ae212c4e575bbd2b0d3d0e48603e50d6242a27aa4258eb0
|
|
7
|
+
data.tar.gz: 20c7e849a878d0c819cc1d989a020b66c87b1d8a6fb8078d4f2faba1f7008486f50b900a86a4e7a00bb22302ea4af4becd5efda8fd5aa895800e6a91597f42e2
|
data/README.md
CHANGED
|
@@ -62,9 +62,9 @@ author: Bob Dylan
|
|
|
62
62
|
Here is part of the document; a very meaningful part.
|
|
63
63
|
```
|
|
64
64
|
|
|
65
|
-
The `metadata_tags_key` and `
|
|
65
|
+
The `metadata_tags_key` and `metadata_tags_json` attributes define the names
|
|
66
66
|
of the content blocks into which metadata will be placed. Metadata can be
|
|
67
|
-
retrieved in Rails views using yield calls; for example:
|
|
67
|
+
retrieved in Rails views using `yield` calls; for example:
|
|
68
68
|
|
|
69
69
|
```html
|
|
70
70
|
<head>
|
|
@@ -78,8 +78,13 @@ retrieved in Rails views using yield calls; for example:
|
|
|
78
78
|
</head>
|
|
79
79
|
```
|
|
80
80
|
|
|
81
|
-
|
|
82
|
-
the original YAML
|
|
81
|
+
The call to `yield` the `:metadata_tags` content block will output HTML
|
|
82
|
+
`<meta />` tags: one for each metadata item present in the original YAML
|
|
83
|
+
metadata block.
|
|
84
|
+
|
|
85
|
+
The call to `yield` the `:metadata_json` content block will output the
|
|
86
|
+
metdata as JSON. This will typically be useful as a mechanism by which
|
|
87
|
+
metadata may be made available to JavaScript.
|
|
83
88
|
|
|
84
89
|
> There is a restriction, however: you cannot `yield` the metadata content
|
|
85
90
|
> block from within the markdown template in which the metadata is defined.
|