This reverts commit 654dba0838.
That commit wasn't the cleanest way to make the HTML valid. Actually
the HTML will never be valid because of the div hack.. I guess we just
live with it till Hugo/Blackfriday adds support for wrapping Markdown
elements in div tags.
Fixes https://github.com/kaushalmodi/ox-hugo/issues/141
Regular page weight setting is same as before:
Manual:
#+hugo_weight: 100
Auto:
#+hugo_weight: auto
Taxonomy weight setting:
Manual:
#+hugo_weight: :tags 100 :categories 100 :series 100
Auto:
#+hugo_weight: :tags auto :categories auto :series auto
Regular page weight and Taxonomy weights together:
#+hugo_weight: 50 :tags 100 :categories 100 :series 100
or if *not* specifying the page weight in the very beginning, use the
:page keyword:
#+hugo_weight: :tags 100 :categories 100 :page 50 :series 100
https://github.com/kaushalmodi/ox-hugo/issues/139
Remove the requirement to suffix such keys with "{}". This is an
improvement over the previous commit
d0a60c5104.
---
The syntax for specifying nested map values custom front-matter is:
Using property drawer (in subtrees):
:EXPORT_HUGO_CUSTOM_FRONT_MATTER: :PARENT_KEY '((KEY1 . VAL1) (KEY2 . VAL2) (KEY3 . VAL3) ..)
Using keyword:
#+hugo_custom_front_matter: :PARENT_KEY '((KEY1 . VAL1) (KEY2 . VAL2) (KEY3 . VAL3) ..)
Note that the elements in the list *have to be* dotted-pairs
like (KEY1 . VAL1). That is what tells ox-hugo that this is a nested
map.
Only 1 level of nested keys is supported.
The syntax for specifying nested map values custom front-matter is:
Using property drawer (in subtrees):
:EXPORT_HUGO_CUSTOM_FRONT_MATTER: :PARENT_KEY{} '((KEY1 . VAL1) (KEY2 . VAL2) (KEY3 . VAL3) ..)
Using keyword:
#+hugo_custom_front_matter: :PARENT_KEY{} '((KEY1 . VAL1) (KEY2 . VAL2) (KEY3 . VAL3) ..)
The "{}" at the end of the key name is what tells ox-hugo that this is
a nested map.
Only 1 level of nested keys is supported.
Fixes https://github.com/kaushalmodi/ox-hugo/issues/139.
This fixes the earlier generated invalid HTML.
---
Details:
Earlier, a figure with #+name:
#+name: fig__unicorn
[[/images/org-mode-unicorn-logo.png][file:/images/org-mode-unicorn-logo.png]]
would export as:
<a id="org55ede7e"></a>
{{< figure src="/images/org-mode-unicorn-logo.png" link="/images/org-mode-unicorn-logo.png" >}}
In HTML, that would look like:
<p><a id="org55ede7e"></a>
<figure>
<a href="http://localhost:5555/images/org-mode-unicorn-logo.png">
<img src="http://localhost:5555/images/org-mode-unicorn-logo.png" />
</a>
</figure>
</p>
This resulted in invalid HTML as per the HTML5 validator.. because
figure is a block level element, and it cannot be put inside the p
tag.
The fix was to insert a blank line after the a tag so that it would be
in its own <p> element, and the following figure element would live
outside that.
With the fix in this commit,
#+name: fig__unicorn
[[/images/org-mode-unicorn-logo.png][file:/images/org-mode-unicorn-logo.png]]
now exports as:
<a id="org55ede7e"></a>
{{< figure src="/images/org-mode-unicorn-logo.png" link="/images/org-mode-unicorn-logo.png" >}}
In HTML, that now looks like:
<p><a id="org55ede7e"></a></p>
<figure>
<a href="http://localhost:5555/images/org-mode-unicorn-logo.png">
<img src="http://localhost:5555/images/org-mode-unicorn-logo.png" />
</a>
</figure>
.. which now is valid HTML.
If an attachment path contains "/static/", that attachment is copied
to the site's static/ dir *even in page bundles*.
This allows one to have links to files in the static/ dir as well as
within the bundle dir, in the case of page bundles.
If an attachment path is:
/foo/<BUNDLE_NAME>/bar/baz.png
That attachment is copied to:
<HUGO_BASE_DIR>/content/<SECTION>/<BUNDLE_NAME>/bar/baz.png
i.e. the attachment path *after* "/<BUNDLE_NAME>/" is retained.
Use plist-put and plist-get instead of passing the description value
via a global variable.
To my surprise, the plist-put and plist-get works across functions!
Kaushal Modi
