- 'name' is a separate 'identifier'-like Menu property. So use ":menu"
to get the menu entry 'name' (not to be confused with the menu 'name'
property!)
- Allow white space in menu entry 'name' (Example:
https://discourse.gohugo.io/t/working-with-multiple-menus-and-iterating-over-the-whole-set/7503)
- Refactor: menu-name(-str) -> menu-entry(-str) to prevent confusing
that with the menu name property.
- Remove 'children' from the list of settable Menu properties. As its
datatype is "Menu" and not "string" (from docs), I don't see that as
something a user would set. I believe, a user setting a menu parent
will mirror that menu entry as a child automatically in that parent
entry.
- Allow inheritance of HUGO_FRONT_MATTER_FORMAT property too.
- Add examples of white space use in ":menu" and ":name" for TOML and
YAML front matter
Now menu front matter data is specified as follows:
* Menu Alist Meta Data
:PROPERTIES:
:EXPORT_FILE_NAME: menu-alist-meta-data
:EXPORT_DATE: 2017-07-18
:EXPORT_HUGO_MENU: :name main :weight 80 :parent posts :identifier foo1
:END:
The option is set by the HUGO_CODE_FENCE property.
- If set to t (default), Markdown code fence is used.
- Else Hugo `highlight' shortcode is used.
Add examples.
This function replaces 2 older interactive functions:
org-hugo-export-current-subtree and org-hugo-walk-headlines
M-x org-hugo-publish-subtree will "do the right thing" when publishing
the current subtree.
C-u M-x org-hugo-publish-subtree will publish all the subtrees in the
document; but now the older limitation of posts to be level-1 headings
is removed.
This function tries to be intelligent; it will export only the current
or one of the parent subtrees that first is seen to contain the
EXPORT_FILE_NAME property. It does not simply export "the current"
subtree.
Also examples added to show how to exclude or comment out posts.
- Case where parenethesized text has leading/trailing spaces adjoining
the parentheses characters.
Earlier 'sluggifying' "Foo ( Bar ) Baz" resulted in 3 hyphens in the
slug string ("foo---bar---baz"). After this commit, those extra spaces
are removed in the slug generation process and so only 2 hyphens (as
expected) would be in the slug ("foo--bar--baz").
Also improve the doc-string of org-hugo--slug function.
* ox-hugo.el (org-hugo-link): Update the type=="file" case in the
final t case of the cond. Now the file:// prefix is not added if
the raw-path begins with "/images/" (or "/HUGO_STATIC_IMAGES/").
Cleanup:
- Move raw-path to the first let form in org-hugo-link; no need to get
that value multiple times in the fn.
- Get value of :hugo-static-images from info
- Replace occurrences of:
(if (not foo) bar
baz)
with
(if foo
baz
bar)
- Misc code consistency edits
For the general use of Hugo to publish blog posts, we do not need to
publish TOC at the beginning of each post.
If a user wants, there are ways to insert the TOC using Hugo.
- Date needs to be of the format "2017-07-06T14:59:45-04:00", not
"2017-07-06T14:59:45-0400" (Note the missing colon in time zone in
the latter).
- No need to wrap values in double quotes that will never contain
spaces.. mimics the default "hugo new posts/foo.md" behavior.
Found the earlier name confusing as the value actually represents the
base directory for the Hugo site development. The posts are actually
exported to a content/ subdir under that.
.. by wrapping (org-export-data (plist-get info :date) info) in org-string-nw-p
- Also fix the date specification in property drawer in small1.org
example.
Also fix the case of "isCJKLanguage" front matter variable.. though, I
believe, hugo does not care about the case there.
Add a test file prop-drawer-parsing.org
* .dir-local.el: Consider sentences to end in double spaces, to match
the Emacs-Lisp string/comment coding style in Emacs source.
* ox-hugo.el: Make the file pass checkdoc, enable lexical binding, and
ensure that it compiles with zero errors/warnings.
* ox-blackfriday.el: Make the file pass checkdoc, enable lexical
binding, and ensure that it compiles with zero errors/warnings. Add
GNU GPL license. Replace "Github Flavored Markdown" references to
"Blackfriday Markdown".
(org-blackfriday-format-toc): Add INFO argument
(org-blackfriday-inner-template): Use above. Needed to fix free
variable warning for info. In lexical binding, the info variable
cannot be global; it has to be passed as an argument. So the
mapconcat implementation had to be broken down into a loop.
---
Consistency edits:
BLACKFRIDAY -> Blackfriday
hugo -> Hugo (in strings and comments)
Hugo Flavored Markdown -> Hugo-compatible Markdown
(Front Matter goes more in-line with Hugo lingo and static site
generators in general.)
metadata -> front-matter (in variable/function symbols)
metadata -> front matter (in strings and comments)
org-mode -> Org mode (in strings and comments)
org -> Org (in strings and comments)
- Remove extra spaces between (var value) in let forms.
- Comment out let-bound variables that were never used.
- add org-hugo-walk-headlines
- exports each 1st-level headline to a hugo entry.
- primitive with no error testing or finer controls
- should definitely be improved!!
Kaushal Modi
Matt Price