[Pelican] Importing Pelican article files into Obsidian Notes

[egberts]

I wish to build a "Import from Pelican" for this wonderful Obsidian Importer (without making a standalone plug-in for this Pelican import)

Pelican too also uses Markdown for all their article files.

But Pelican also had "file properties" embedded at the beginning of each file, typically looking like:

title:  An Example Title
date: 2020-10-13 11:00
modified: 
status: published
tags: example
category: HOWTO
summary: An example file demonstrating file properties already embedded in itself.
slug: pelican-example-file.md
lang: en
private: False

This article details the demonstration of Pelican 
properties having already in beginning of each 
Markdown file with no header/footer markers to 
be (rudderlessly) guided by.

Note: Notice that there are no header/footer demarcations (ie., --- or === or `````).

What aspect of Obsidian Importer is closest to this desired action:

• Converting file content having [\w\s]:\s*[\w]* into Obsidian file properties
• Stop adding Obsidian file properties once a blank line has been encountered
• Importing remaining file content as a 'Note'.

[kepano]

This is possibly duplicate of #23. I was not familiar with Pelican but since it's a static site generator I think it makes more sense to consider what file format it uses: Markdown with a metadata syntax derived from MultiMarkdown:

• https://fletcher.github.io/MultiMarkdown-5/metadata.html
• https://python-markdown.github.io/extensions/meta_data/

Perhaps there could be a MultiMarkdown to Obsidian Flavored Markdown converter/importer. However, I think this kind of conversion is better for a tool like Pandoc which can convert between many Markdown variants.

[egberts]

Pandoc? I do not see any form of metamarkdown importer in Obsidian:

https://github.com/obsidianmd/obsidian-importer/tree/master/src/formats

Unless you are alluding to some kind of intermediate conversion step going from my Pelican metamarkdown thru Pandoc into what Obsidian-desired format before doing the Obsidian importer?

Remember, there are many useful Pelican metatags that can be imported into Obsidian. So, that incorppration of these metadata would be lost if the intermediate conversion step is straight into a simple Obsidian Markdown file, right?