Usecase suggestion: markdown folder import

[joepio]

I was discussing an interesting usecase with @AlexMikhalev about managing personal knowledge, currently stored in markdown files in a system similar to an Obsidian + Github workflow

Wishes:

• Import once (using CLI)
• Maintain relative links in markdown files
• Track incoming / outgoing links (including non atomic resources)
• Export to folders + files structure
• Import media files File management in Atomic-Server (with Commits) #72
• Track links to media objects

[AlexMikhalev]

Question for discussion: import from git (i.e. github/gitlab) are better than import from filesystem = same level of abstraction.

[jonassmedegaard]

I recognize the convenience of using Github/Gitlab APIs, but please don't call those "git".

Supporting "import from git" is something semantically different from "import from $SERVICE API".

[joepio]

Since github, gitlab and others should implement the git SSH protocol, I think this could suffice. It is secure and standardized.

[jonassmedegaard]

for a read-only "dump" of a git repository I agree - not only the git+ssh protocol but also http and https could be supported.