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.
This commit reorganizes the former internal function
org-hugo--transform-org-tags into smaller functions and a new
defcustom org-hugo-tag-processing-functions. See its doc-string for
details.
This change is only internal, and the tag processing logic is exact
same as before (If this commit broke something for you, file a bug
report!).
This defcustom now allows users to add their own processing to the
tags e.g. prevent certain tag names (not the posts tagged with those!)
from getting exported, as requested in
https://github.com/kaushalmodi/ox-hugo/issues/142.
This commit now allows doing that using a small snippet like below:
(defun org-hugo--tag-processing-fn-remove-tags-maybe (tags-list info)
"Remove user-specified tags/categories.
See `org-hugo-tag-processing-functions' for more info."
;; Use tag/category string (including @ prefix) exactly as used in Org file.
(let ((tags-categories-to-be-removed '("DONE"))) ;"my_tag" "@my_cat"
(cl-remove-if (lambda (tag_or_cat)
(member tag_or_cat tags-categories-to-be-removed))
tags-list)))
(add-to-list 'org-hugo-tag-processing-functions
#'org-hugo--tag-processing-fn-remove-tags-maybe)
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.
Kaushal Modi
