Some updates have been made on this fork - https://github.com/dylviz/githubbooks, I am no longer maintaining repo this in favor of hosting content on GitHub directly
yarn add github-books
#or
npm install github-books
This library helps you make a book from .mdx and .md files on GitHub. mdxbook has nothing to do with user interfaces and is independent of any JavaScript framework.
We take a table of contents that is written in Markdown and parse it to a JSON format that helps you use GitHub as a headless CMS. In less technical terms, we help you give your reader a good experience whether they read your content directly on GitHub or on your own custom platform.
A major selling point is that we are compatible with existing GitBooks. We hope this configuration can become a standard and everything will be interoperable. Like EPUB for the Markdown era.
We take a file that has a markdown table of contents. Notice that we support both relative paths and full GitHub URLs. You can use content from other people's repositories by simply adding the URL.
# Title of Book
* [Study 1](study-guide.md)
* [Study 2](https://github.com/MatthewCaseres/mdExperiments/blob/main/study-guide.md)This file renders in a nice way on GitHub, and you can use GitHub to read the contents even without building your own web application.
You can generate a configuration file and save the JSON to a file.
var { summaryToUrlTree } = require("github-books");
var fs = require('fs');
(async () => {
const config = await summaryToUrlTree({
url: "https://github.com/MatthewCaseres/mdExperiments/blob/main/config.md",
localPath: "/Users/matthewcaseres/Documents/GitHub/mdExperiments/config.md",
});
fs.writeFileSync('config.json', JSON.stringify(config))
})()Here are some observations about the generated object:
- Nodes contain a
ghUrlwith the location of the file on GitHub, as well as arawUrlthat contains the location of a URL serving the raw text content of the Markdown. - A
pathproperty exists for all files with links that are relative paths. This allows for local development workflows when authoring contents.
{
"type": "root",
"children": [
{
"type": "file",
"route": "MatthewCaseres/mdExperiments/study-guide.md",
"title": "Study 1",
"path": "/Users/matthewcaseres/Documents/GitHub/mdExperiments/study-guide.md",
"rawUrl": "https://raw.githubusercontent.com/MatthewCaseres/mdExperiments/main/study-guide.md",
"ghUrl": "https://github.com/MatthewCaseres/mdExperiments/blob/main/study-guide.md",
"treePath": [0]
},
{
"type": "file",
"route": "MatthewCaseres/mdExperiments/study-guide.md",
"title": "Study 2",
"ghUrl": "https://github.com/MatthewCaseres/mdExperiments/blob/main/study-guide.md",
"rawUrl": "https://raw.githubusercontent.com/MatthewCaseres/mdExperiments/main/study-guide.md",
"treePath": [1]
}
],
"title": "Title of Book",
"treePath": []
}Users can write custom functions. The user is given the AST for the markdown file in mdast, and the front matter in frontMatter. Modifications can be made for each node of type file on the basis of it's abstract syntax tree.
The unified ecosystem is basically about turning text into JSON (abstract syntax trees to be precise). If you want to see what an Abstract Syntax Tree for your markdown document looks like you can go to the AST explorer. Mess around with this.
Run the code below to see that we can grab information from inside the markdown files and make modifications to the generated configuration. The logs actually repeat, because our configuration has two list items that point to the same location.
Remember to run yarn add unist-util-visit. This is a utility built by the unified.js people, whose work allows us to do all that we are doing. Having a good idea of the unified ecosystem will really help you when working with Markdown, check them out at https://unifiedjs.com/.
var {summaryToUrlTree} = require('github-books');
var fs = require('fs');
var visit = require('unist-util-visit');
(async () => {
const docsTree = await summaryToUrlTree({
url: "https://github.com/MatthewCaseres/mdExperiments/blob/main/config.md",
userFunction: (node, {mdast, frontMatter}) => {
// You could collect information about headings and add it to the tree
visit(mdast, 'heading', (mdNode) => {
console.log('Heading Node', mdNode)
})
//Or use the frontMatter
console.log('frontMatter', frontMatter)
//But instead we just laugh
node.lol = "lol"
}
})
console.log("docsTree", docsTree)
})()Use the rawUrl field from tree nodes to fetch text data and use GitHub as a headless CMS. You can do this however you want, but we have a template for Next.js. You can press the "Use this template button" at the repo - https://github.com/Open-EdTech/github-books-template, or you can use create-next-app.
#Experiencing issues with npx currently, use yarn
yarn create next-app gh-books-template -e https://github.com/Open-EdTech/github-books-template
Make sure the dependencies are installed if not using the Next.js CLI.
npm run dev
# or
yarn dev
You should see the application on port 3000,
The blue button takes you to the book -
There is a file bookConfig.ts that generates the configuration files using an IIFE. At the bottom of the file you can see that we write bookConfig.json using the configuration file at https://github.com/basarat/typescript-book/blob/master/SUMMARY.md.
To add a new book we just need to write another tree to bookConfig.json. In some cases you want to host other people's stuff but there is no configuration file in their repository since they aren't using GitBook. Do not despair, you can write your own configuration file in your own repository that contains links to their repository.
In this configuration file we link to the AWS documentation on getting started with AWS - https://github.com/MatthewCaseres/aws-docs-configs/blob/main/configs/amazon-s3-getting-started-guide.md. Let's add the tree to our array of configuration trees.
#Update the configuration file
(async () => {
const tsTree = await summaryToUrlTree({
url: "https://github.com/basarat/typescript-book/blob/master/SUMMARY.md"
})
const awsTree = await summaryToUrlTree({
url: "https://github.com/MatthewCaseres/aws-docs-configs/blob/main/configs/amazon-s3-getting-started-guide.md"
})
fs.writeFileSync('bookConfig.json', JSON.stringify([awsTree, tsTree]))
})();Generate a new configuration file using yarn book or npm run book. The array of trees now contains two trees in bookConfig.json. Visit the route at http://localhost:3000/awsdocs/amazon-s3-getting-started-guide/doc_source/GetStartedWithS3.md to see your book. To know the route I just go into the generated bookConfig.json and grab the first route property on the first tree.
You can see our platform on openedtech.io if you want to see how we customize our markdown to be interactive.
The software is not perfect, but I try to be clear about what it is and how I use it on my own website.
I think there is a lot of potential and a long road ahead. Ultimately I think we need some sort of standard for books in a markdown/GitHub era of content.