nimibook is a port of mdbook to Nim, powered by nimib. Nimibook allows to create a nice looking book from nim code and markdown, making sure that nim code is running correctly and being able to incorporate code outputs in the final book. An example book is nimibook documentation.

mdBook is a command line tool and Rust crate to create books using Markdown (as by the CommonMark specification) files. It's very similar to Gitbook, which is a command line tool (and Node.js library) for building beautiful books using GitHub/Git and Markdown (or AsciiDoc).

nimib is a Nim library to convert your Nim code and its outputs to html documents. The html output can be easily customized thanks to nim-mustache, and this is what allows it to use it to build nimibook. nimib documents are normal nim files which use nimib library to produce an output document.

One particular advantage of nimib is that it can incorporate interactive content taking advantage of nim's js backend. For the basic examples see nimib interactivity doc.

The Markdown dialect supported by both nimib and nimibook is the subset of Github Flavored Markdown provided by nim-markdown. For a quick reference of supported syntax see this cheatsheet (created with nimib).

Nimibook as it is provides the basic functionality needed to create a book with markdown and nimib sources. It still has some features missing from mdbook (see this issue). Contributions are welcome and we will provide guidance and code reviews. You can join a Nimib Speaking Hours session if you want some live discussions on whether or not a feature fits or you want pointers on how to help out.

To follow up on recent changes check the changelog.md.

• scinim/getting-started: Getting started with Nim for Scientific Computing
• moigagoo/norm: A Nim ORM for SQLite and Postgres
• moigagoo/karkas: Layout helpers and syntactic sugar for Karax
• PhilippMDoerner/Snorlogue: A plugin for the prologue web-framework that provides a set of simple CRUD routes to administrate your database
• PhilippMDoerner/mapster: A simple way to generate mapping functions at compile-time without having to write them yourself
• dsrw/enu: A Logo-like 3D environment, implemented in Nim
• can-lehmann/owlkettle: A declarative user interface framework based on GTK 4

You are welcome to open a PR and add your site using nimibook here.

• table of contents in a collapsible sidebar
• five themes (Light, Rust, Coal, Navy, Ayu)
• buttons to next/previous pages
• build multiple files in parallel
• (optional) latex content with katex
• (optional) link to github repo
• (optional) link to track analytics with plausible analytics

To install Nimibook: nimble install nimibook

Nimibook does not (yet) provides an executable to manage your book, but it provides the basic building blocks to write your own.

1. example nbook.nim: in a folder of your choice create a nbook.nim file with the following content:

import nimibook

var book = initBookWithToc:
  entry("Preface", "preface.md", numbered = false)
  entry("Introduction", "intro.md")
  section("Chapter 1", "chapter1/index.nim"):
    entry("Content", "content.nim")
    draft("Nothing yet")
    section("Sub chapter", "no_ext"):
      entry("and some more content", "more.md")

nimibookCli(book)

2. write a TOC: modify nbook.nim to specify the planned Table of Content (TOC) for your book.

3. nbook init: running nim r nbook init (or compile nbook and run nbook init) will set up the book with:

• a nimib.toml that contains the default configuration for the book
• a book folder that contains sources for all chapters mentioned in the TOC. Note that .nim files already contain default nimib content to be used in nimibook.
• a docs folder that contains static assets for the book and that will contain the built book

4. nbook build: run nim r nbook build to build the book. Open any .html file in docs folder to navigate your book.

5. create your content and enjoy!: now you are ready to start creating content in your sources and publish your book.

See nimibook documentation for more details.

You are more than welcome to contribute!

• We usually have some open issues of stuff we need to fix or we would like to do.
• You have an overview of the code base in src/readme.md
• The CI is setup to run tests and publish a document PR preview (click on details on the Netlify preview task once it's green), so that we can all check the changes directly from the PR.
• You should also test and build the book locally, there are nimble tasks to help with that (run nimble tasks for the list).
• If the feature can be tested with a unit test, make sure to add one.
• Once you make a change, remember to document your changes in the appropriate place in the docs.
• If you add a module, remember to update the code guide.
• bump the version (usually a patch increment) so that we can immediately tag and release your contribution.
• Make sure that the title of your PR is clear and edit the initial message with a few short sentences that will be added to the changelog once we release.

This website is tracking analytics with plausible.io, a lightweight and open-source website analytics tool with no cookies and fully compliant with GDPR, CCPA and PECR. Analytics for this website are publicly available here. You can opt out from analytics tracking with standard ad-blocking or typing localStorage.plausible_ignore=true in browser console.