search

alfredbaudisch / pardall_markdown

Reactive publishing framework, filesystem-based with support for Markdown, nested hierarchies, and instant content rebuilding. Written in Elixir.
Apache License 2.0
115 stars 7 forks source link

Added compatibility with Joplin Markdown notes #39

Closed alfredbaudisch closed 3 years ago

alfredbaudisch commented 3 years ago

Added support for Markdown files exported from Joplin Notes (closes #15)

Introduced a breaking change with the previous version, where the configuration for the static assets now require a path, instead of a folder name, thus the property static_assets_folder_name has been replaced with:

  # The path that contains static assets,
  # those files won't be parsed.
  static_assets_path: "/home/documents/content/static",

Added three configurations for that:

  # Markdown files can contain a top section with metadata/attributes related
  # to the file. Is the metadata required?
  is_markdown_metadata_required: true,

  # Are posts set as draft (unpublished) by default? If true, posts will appear
  # in the content trees only when they have the attribute `published: true`
  # (which sets `Post.is_published == true`). Draft posts can be retrieved
  # only by calling their slug directly with `Repository.get_by_slug/1`
  is_content_draft_by_default: true,

  # Added for compatibility with Markdown files from Joplin.
  # When `true`, the parser will consider the first line of text to be
  # the post title. Even when as `true`, the title can still be overridden
  # by the metadata. Set to `false` in most cases, unless
  # you are exporting notes from Joplin.
  should_try_split_content_title_from_first_line: false,