maxence-l / notenote.link Goto Github PK

Could you please add the feature to embed other MarkDown files using ![[]] syntax just like in Obsidian?

There seems to be a problem with files with Chinese Filenames.
I have my notes in the _notes folder, however only the files with all English filenames are rendered in the website, as shown below.

(The meaning of the note is not important)

(Here it's Okay)

(Inside the link -> all blank)

Thank you in advance for this fantastic theme and your answers

Hey!
I'm currently trying to merge this template with another template, and I couldn't figure out how the sidenote function is operating. I saw some conditionals in the content.html in the _include forlder, but couldn't figure out the solution on my own, could you elaborate a bit on how they work?
Thanks in advance!

when I create a markdown and go to him from the menu list,

his path in my browser is "folder/my_markdown", but my markdown is located in "folder/folder2/folder3/my_markdown".

how to fix that?

Could you please add an option for Sliding Window Mode (Andy Matuschak's Notes Style).

Even if only a single view on the right would be perfect.

Or anything like Obsidian's templates.

I really don't understand how to work with Jekyll, so If anyone know how can I add a light/dark button to change the CSS, I will appreciate it !

Can't we use github pages instead of Netlify? I was just wondering if we really have to use Netlify. I am a noob in all of this, I just want to publish a part of my notes from Obsidian. :)

please, how to remove a requirement of Frontmatter and metadata in markdowns?

I have a very lot markdowns, but links to them required
`---

---`
block in top. In my site they not showing without that Frontmatter.

I want to know if it's possible to "cross-sync" with an already existing Obsidian git vault, or if I need to always use copy-pasting or some "windows magic" like physical link for note we want to share.

These are specific to a machine and a temporary.

I recommend deleting all .DS_Store files and adding .DS_Store to .gitignore

Expected behaviour: wikilinks point to filename and not title of the note. Like it works on the tag page.

Even better: If we could write wikilinks to the filenames (as is how it works in Obsidian) but the anchor text displayed is taken from the YAML frontmatter title.

I have a naming convention for my files where I use only lowercase letters and might prepend them with for example "q." for quotes. However, I do not necessarily want to display this "q." in front of the title of the note.

Hello!
First of all, thank you so much for this repo, it really is a wonderful resource, and it fills a huge void imho.
I don't know if the Issues is the right place for this, but could you explain the seasons' function in the front matter? I tried playing around with it, but couldn't figure out what they were for, but I am curious.

Thanks!

Stunning work, @Maxence-L! 👏

I'd like to get this up and running, ideally using Hyde. Can you recommend which parts would be necessary to change to get at least a very similar feel, i.e. fixed left sidebar, same colour scheme, and fonts?

Or do you reckon it might be feasible to make this a subpage of a main website built with another theme (like Hyde)?

In the readme, you mention that you're thinking about having the ability to apply different themes. So, maybe this is already on your mind?

Any help would be much appreciated.

i dont like how the default light theme looks, how do i use dark themes, do i have to modify css manually?
i use github pages btw

The README says that transclusion for wikilinks is available, but the standard obsidian syntax ![[note]] doesn't work - it just provides a link to the page, with an exclamation point in from of it. So does [[!note]], ![[note#heading]], and ![[note#heading|alt]]. What's the proper syntax?

With ruby update, the FFI seems to be broken.
To work, I do this :

gem install ffi -f
bundle update
bundle add webrick
bundle && bundle exec jekyll serve

I dunno if it's possible to pull request this, so I leave it here for future reference.