pandoc
obsidian-export
Our great sponsors
pandoc | obsidian-export | |
---|---|---|
417 | 22 | |
32,051 | 914 | |
- | - | |
9.8 | 7.7 | |
2 days ago | 4 days ago | |
Haskell | Rust | |
GNU General Public License v2.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pandoc
-
📓 Versionner et builder l'eBook de son Entretien Annuel d'Evaluation sur Git(Hub)
pandoc toolchain pour builder une version confortable/imprimable en phase de travail (ePub, pdf, docx, html)
-
Launch HN: Onedoc (YC W24) – A better way to create PDFs
Congrats on the launch, I guess, but there are so many free options that I can't think of a situation where paying $0.25 per document would be justified...? Just to name a few:
Back in the days, I used to use XSL-FO [0] and it was okay. It was not very precise but it rarely if ever broke, and was perfectly integrated with an XML/XSLT solution. Yeah, this was a long time ago.
Last month I used html-to-pdfmake [1] and it's also not very precise and more fragile, but very efficient and fast.
Yet another approach would be to pro grammatically generate .rtf files (for example) and use Pandoc [2] to produce PDFs (I have not tried this in production but don't see why it wouldn't work).
[0] https://en.wikipedia.org/wiki/XSL_Formatting_Objects
-
Ask HN: Looking for lightweight personal blogging platform
Others have mentioned static site generators. I like Hakyll [1] because it can tightly integrate with Pandoc [2] and allows you to develop custom solutions if your needs ever grow.
[1]: https://jaspervdj.be/hakyll/
[2]: https://pandoc.org/
-
Show HN: CLI for generating beautiful PDF for offline reading
Have you compared it with a conversion by pandoc (https://pandoc.org/)?
-
Pandoc
I have used it to kickstart a blogging project that I wish to come back to soon. The Lua inter-op for custom readers, writers and filters is great but I wish there was more editor integration and even perhaps an official IDE/editor with built-in debugging features (probably something already do-able with Emacs but I haven't checked). The only blocker for my project is no support for "ChunkedDoc" for Lua filters [1] which forces me to write more code and a complicated Makefile.
- I don't always use LaTeX, but when I do, I compile to HTML (2013)
-
Running Quarto Markdown in Docker
Until recently, I'd been using pandoc but, having taken the time to look around Quarto, it's a hell of a lot more powerful.
- ArXiv now offers papers in HTML format
-
A doctoral dissertation build system
On the technically advanced end of the spectrum you'll find John MacFarlane [1], professor of philosophy at Berkeley and creator of pandoc [2]. Some people are just amazing.
obsidian-export
-
MdBook – Create book from Markdown files. Like Gitbook but implemented in Rust
Found: https://github.com/zoni/obsidian-export but hope this can be part of a single solution.
-
Using Github to write my notes has helped me retain knowledge immensely.
I use this obsidian-export CLI program to convert prior to pushing to my repo and it's been working pretty well. This gives me a read-only version of my notes that is accessible from devices I don't have obsidian on (work laptop, for example).
-
Personal knowledge base: Any tool/software suggestions?
If you limit your use of third party plugins, you can always use https://github.com/zoni/obsidian-export for this as well. I originally built it for exactly this use case (but now also use it as a crucial step in my pipeline to publish content to my own website)
-
A free + simple + good looking alternative to Obsidian Publish!
It came from here! https://github.com/zoni/obsidian-export
-
A Quick Way to Share Your Obsidian PKM
If you add in obsidian-export as a build step (disclaimer: I'm the author), there is no need for people to change their Obsidian settings. Obsidian-export turns WikiLinks into regular Markdown links (and it flattens embedded notes) :)
Worth noting I maintain a project which does exactly this: https://github.com/zoni/obsidian-export
-
D&D template?
I have similar folders to [Oudwin](https://www.reddit.com/user/Oudwin/)... - dm - _inbox - assets - checklist - communications - research-reference - elements - sessions Additionally, I have had reasonable success using [obsidian-export](https://github.com/zoni/obsidian-export) to export my Obsidian vault to CommonMark. From there you have more options. I then build html pages using [mdbook](https://rust-lang.github.io/mdBook/) to control the information that is revealed to players. I am playing with using [MkDocs](https://www.mkdocs.org/) to see if it offers more control/flexibility. Regardless, the /elements folder contains all the lore chunks of the world including information I keep on the PCs. The /communications and /sessions folders can contain info with links to /elements that are revealed as needed. I make heavy use of transclusion ![[CoolThingFormAnotherFolder]] to keep it a bit more elegant and some custom styles are needed to make it how it look how I wish.
-
New User - Should I stay with pure markdown or use Obsidian extra commands/syntax?
Shameless plug: obsidian-export. It will convert [[WikiLinks]] and ![[Embeds]] to plain Markdown (among a few other things) so you'll always have a way to go back if Obsidian doesn't work out the way you hoped.
-
What Settings to Use to Make Notes Created in Obsidian the Most Universally Compatible
So really you can't get what you want at all. You could try an external tool like this to export your notes to commonmark which is more widely supported. Ultimately if you are changing the path to files outside of obsidian (meaning they won't be automatically updated) you will break links. So maybe your best bet is to use wikilinks + an export tool.
-
I followed the steps in this blog and cloned my resulting repo. Now I can use Obsidian as my website CMS and text editor!
If that's something you would miss, you could hook obsidian-export into a build pipeline to convert Obsidian-flavored markdown to regular Markdown (CommonMark, really).
What are some alternatives?
obsidian-pandoc - Pandoc document export plugin for Obsidian (https://obsidian.md)
Obsidian-MD-To-PDF - A command line python script to convert Obsidian md files to a pdf
pandoc-highlighting-extensions - Extensions to Pandoc syntax highlighting
OSCP-Notes-Template - A template Obsidian Vault for storing your OSCP revision notes
Hugo - The world’s fastest framework for building websites.
Zettlr - Your One-Stop Publication Workbench
dendron - The personal knowledge management (PKM) tool that grows as you do!
obsidian-html - :file_cabinet: A simple tool to convert an Obsidian vault into a static directory of HTML files.
foam - A personal knowledge management and sharing system for VSCode
kramdown - kramdown is a fast, pure Ruby Markdown superset converter, using a strict syntax definition and supporting several common extensions.
wavedrom - :ocean: Digital timing diagram rendering engine