mdBook VS nomicon

I personally had the frustration that websites generated with [mdBook](https://github.com/rust-lang/mdBook) always displayed me the "Navy" theme. But I prefer the "Ayu" theme, therefore I always set the theme to "Ayu". But doing things per hand is not the way we do stuff around here, so I decided to write a small browser extension that applies the themes for me.

It's mdBook which is made in Rust and popular with Rust content https://rust-lang.github.io/mdBook/

I made a PDF generator for mdbook called mdbook-compress.

This makes me think, maybe I'll start using mdBook. I find it really comfortable to read and it's probably not too complicated to use.

I sync Obsidian with Git and use pandoc for book / ebook generation (or Foam with Visual Code might work too).

Scrivener can synchronise with Git too - albeit indirectly (it sync's with a folder & I use a simple script to keep it up to date)

If you need to organise research you can sync Wiki.js with Git.

However, Gitbook or mdBook might be easier to use for a single book project.

https://www.gitbook.com/

https://rust-lang.github.io/mdBook/

https://foambubble.github.io/foam/

https://js.wiki/

mdBook

+1 for Pandoc. I'll also add mdBook as an alternate for markdown to web version of ebooks (especially for search and themes).

I also don't mind using a Markdown editor + static site generator like mdBook - BookStack is where I'd have gone if I wanted something else

All credit goes to the mdbook people for this! I'm using it to turn Markdown text into HTML, complete with interactive playgrounds and all :-)

You should read The Rustonomicon before you use unsafe since it's essentially the unsafe guidelines and covers much more than I can here

Rust doesn't have similar obscure details? May I interest you with the Rustonomicon?

For more details on this kind of thing, you might be interested in the Rustonomicon, which is the goto guide for the details of writing unsafe Rust code.

The "Rustonomicon" is a book about unsafe code in Rust: https://doc.rust-lang.org/nomicon/

Getting into unsafe Rust is generally more for intermediate to advanced users, but the Rustonomicon has good information on how to do it safely: https://doc.rust-lang.org/nomicon/

The hard part is designing a safe "rusty" interface around such data structures, so it actually becomes practical (and safe) to use them in regular Rust code. The best place to look for is the Rustonomicon book. It documents Rust's safety requirements and unsafe code.

⭐ The Rustonomicon - The Dark Arts of Advanced and Unsafe Rust Programming - repo

Can confirm. Rust has one of these and the code looks similar: https://doc.rust-lang.org/nomicon/

I'll add a (lone?) voice for diving in to the deep end straight away:

https://doc.rust-lang.org/reference/

https://doc.rust-lang.org/nomicon/

Documentation aimed at beginners often assumes a lack of prior programming experience, which is useful if you are (for example) a high-school student learning about pointers and abstraction but IMO not a good use of time for most people posting on Hacker News.

The Rust reference manual is well-written and comprehensive for basic Rust, and the Rustonomicon has often answered my questions about more advanced topics (FFI, concurrency).