Currently this renders in inline math mode

$$math$$

While this renders in display mode

$$
math
$$

They should both render in display mode to match obsidian.

The code is getting complicated enough that unit tests would be a big help. This also helps to avoid cluttering the default ./notes used in the template.

Currently oth requires relative links in [[wikilinks]], forcing people to change obsidian's default settings, and fix their markdown is bad though. so I should improve my pageResolver so it handles normal obsidian vaults

Obsidian tabs in code blocks enter a tab character by default, and tab characters look ugly in the rendered html

There might be a highlightjs option for this, if there isn't we'll have to .replace("\t", " ") somewhere, preferably only in code blocks

Not sure if real issue. When publishing (with a notes directory containing all my .md files), the html files are generated in the notes directory, causing the site to report "file not found" at root, yet contains an entry in the folder notes/ in the url. Also, I have wikilinks of the form [[Link]], which supposedly work, yet I can't get them to actually link to each other in the site.

If I did something wrong, let me know. Thanks!

EDIT: you can view my site as a repo on my profile, it's public.

Currently I have

htmlVFile.dirname = sourceVFile.dirname.replace(/notes/, "out");

This is unsafe as the full dirname may be my-notes/notes in which case we'd get my-out/notes which is wrong!

All the fixes I could think of were rather complicated, I'd like something that takes my-notes/notes/subdir to out/subdir preferably in one line, but extracting it into a helper is fine too (like I did with depth)

Titles are set from filenames by default, meaning Index.md automatically has title "Index". We can fix this by adding optional frontmatter to files (obsidian already supports frontmatter so this is fine)

It would be nice to import css from existing obsidian themes, Ideally I could compile the css into only what's used clientside (perhaps a bundler can do this for me) so I don't waste space on irrelevant UI styles.

I might need to write some custom code to handle the /* @settings */ comment directive in obsidian themes.

We could prefetch pages using link prefetching that are wikilinked to from a note, this would make browsing smoother. especially since obsidian notes are often small, atomic objects where we have to do lots of navigation.

Link hovering would also be cool, but that requires clientside javascript, which I'd like to avoid for as long as possible

Wishlist for things I could statically catch

• [ ] Report dangling [[wikilinks]] before they 404 in prod (blocked)
• [ ] Warn about long math (won't display on small screens) (not sure if this is possible without browser emulation)
• [ ] Warn about spelling/grammer mistakes (a unified plugin should exist, gotta make sure it isn't annoying tho)
• [x] Warn about using $$math$$ since obsidian handles it differently (see #13)