Now,
- =foo= -> <code>foo</code> in HTML (same as before)
- ~foo~ -> <kbd>foo</kbd> in HTML (new functionality)
You can still get the below behavior by setting
`org-hugo-use-code-for-kbd` to nil, or setting the
`EXPORT_HUGO_USE_CODE_FOR_KBD` property value in a subtree property
drawer to empty (see example).
- ~foo~ -> <code>foo</code> in HTML (old behavior; before this commit)
Add tests.
Closes https://github.com/kaushalmodi/ox-hugo/issues/53
- Blackfriday automatically renders "--" as en-dash, "---" as em-dash and
so on. So there is no need for Org to replace those with the HTML
special characters in the Markdown itself. This also makes the
Markdown more readable.
- Titles are now sanitized. HTML anyways does not allow bold, italics,
etc markup in the <title> section. Now Markdown markup for the same
are removed from the title variable in front matter.
User can still override this default by using:
#+OPTIONS: ':t
The default smart-quoting by Blackfriday is good enough. As a side the
Markdown files are much more human-readable with the
single and double quote characters used instead of rsquo, lsquo, rdquo
and ldquo.
- Rename org-hugo-publish-subtree to org-hugo-export-subtree-to-md to
fit the standard naming convention.
- Remove org-hugo-convert-region-to-md; does not seem necessary for
Hugo exporter.
@titaniumbones
Now,
- "C-c C-e H H" will work as old "M-x org-hugo-publish-subtree"
- "C-c C-e H A" will work as old "C-u M-x org-hugo-publish-subtree"
- Add org-hugo--quote-string, org-hugo--get-valid-subtree,
org-hugo--get-post-subtree-coordinates
- Add examples to demonstrate how auto menu weight assignment works.
- '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
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 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
Kaushal Modi
Puneeth Chaganti
Matt Price