Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Enable conversion for the whole vault (into new secondary vault) #1

Open
phibr0 opened this issue Nov 18, 2020 · 7 comments
Labels
enhancement New feature or request

Comments

@phibr0
Copy link

phibr0 commented Nov 18, 2020

I think the title says it all! A Feature which enables the user to "export" the whole vault with mdlinks instead of the default wikilinks. By doing that the user will be able to use something like github pages to host their knowledge-base.

@agathauy
Copy link
Owner

Ohhhh that indeed an interesting use case! I'm interested in exporting stuff to Github pages as well. Would update on Discord when I get around doing this :D

I think the next thing I would do first is the per page implementation. And then that one 👍

@agathauy agathauy added feature request enhancement New feature or request and removed feature request labels Nov 19, 2020
@phibr0
Copy link
Author

phibr0 commented Nov 19, 2020

hm.. i just found out that the plugin doesnt add the folder in front of the mdlink..
That means it still wouldn't work with other software like Github Pages. Would it be possible to get that information too? I mean obsidian has it, i just dont know if a plugin can get access to it..

If all notes are in the root directory it works, but i use multiple sub-directories

@agathauy
Copy link
Owner

@phibr0 it doesn't? It does on mine... Would you mind sending an example text?

@agathauy
Copy link
Owner

agathauy commented Nov 20, 2020

Ah got what you're saying. What setting is it in Obsidian that allows you to just use a "filename" on a Wikilink without a path? I use relative file paths for example, and before, absolute paths. I use sub-vaults as well.

I think it's with "Shortest path available" right? But I just can't seem to trigger it right now for some reason. A folder path still appends to my links.

@phibr0
Copy link
Author

phibr0 commented Nov 20, 2020

What i mean is that for example i have this vault:
root.md in the root vault folder and
/sub/sub.md so another md file in a subdirectory

If i want to have a mdlink in the root file shouldnt the link be something like [](./sub/sub.md)?

@agathauy
Copy link
Owner

agathauy commented Nov 20, 2020

@phibr0 Hmm Obsidian does load relative files like [](sub/sub.md) still doesn't it? Although tbh it wasn't an issue with Github Wiki, Gitlab Wiki, Zettlr, VS Code Preview and Pandoc. So I think this is ok.

For Obsidian, it appears to only change the file paths if for example sub.md accesses root.md like [](../root.md)

Personally right now I think I shouldn't handle this yet since vault configurations for paths tend to be different for different people. Especially since some changed the settings after already using an existing setting (Obsidian doesn't change already existing absolute paths to relative paths for example). Might be best for us to manually change this via Replace All for now with a code editor e.g. VS Code, or other replace all scripts manually instead of devving a more intricate solution.

@phibr0
Copy link
Author

phibr0 commented Nov 20, 2020

Will it then work with GH Pages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants