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.
Kaushal Modi