Dive into the world of unlimited customization for your Obsidian exports using the Liquid Templating Language! This gives you complete control over how your highlights, notes, frontmatter, filenames and other content are presented.
With Liquid Templating, you can craft personalized templates, shaping your exported content exactly the way you want it. From dynamic page layouts to tailor-made filenames, the possibilities are endless. Learn more at https://shopify.github.io/liquid/
While BookFusion provides an optimal template to start you have full power to customize all aspects including: File Name,Page Template, Highlight Template, Chapter Heading Template, Frontmatter & More. This is all done on the Obsidian configuration page with details provided there.
Tips
- Check the documentation for the Liquid templace language documentation.
- If you are customizing your filename and paths ensure that you use
| sanitize_filename
with each variable that you include in the path. - Ensure you always click Apply on the right after making any changes under the Templates & Customization section. You must click Apply for the changes to take effect.
- Ensure you have sync enabled for your entire library or have selected a few books, tags, bookshelves or series if you see no highlights being synced.
- You have full control to create a rich Frontmatter. See below for a subset of the data that can be included:
bookfusion.book_id: "{{ id }}"
bookfusion.synced_at: "{{ 'now' | date: '%FT%T%:z' }}"
{% if categories -%}
categories: {% for category in categories %}
{{ category| prepend: ' - ' }}
{%- endfor %}
{% endif -%}
{% if series -%}
series: {% for serie in series %}
{{ serie | prepend: ' - ' }}
{%- endfor %}
{% endif -%}
{% if tags -%}
tags: {% for tag in tags %}
{{ tag | replace: ' ', '_' | prepend: ' - ' }}
{%- endfor %}
{% endif -%}
{% if authors -%}
authors: {% for author in authors %}
{{ author | append:']]"'| prepend: '- "[[ ' }}
{%- endfor %}
{% endif -%}
asset: {{ book_url }}
uploaded_date: {{ uploaded_date }}
progress: {{progress}}
Comments
0 comments
Article is closed for comments.