This article provides instruction on using tools and a process that will help create and share content online.

Reading time: 18 min read

Excerpts from the article

GitBook Version 2 was released a few months ago and if you navigate to ‘gitbook.com’ you’ll be working in Version 2, which is not a static site generator. You can still access Version 1 by navigating to ‘legacy.gitbook.com’. Because Version 2 is not a static site generator, it can’t be hosted elsewhere.

The legacy GitBook defined an editor, a command line interface, and a toolchain for creating and publishing content. The product of these tools was a set of markdown and HTML that could be served anywhere. I like that flexibility because I like to take advantage of GitHub.io and configure my GitHub.com repo to be served from GitHub.io.

So I left Medium for some obvious reasons. Don’t get me wrong! I loved (and maybe still love) Medium, but with no more custom domains and going in a direction I don’t prefer, I created my own sites on Github.
Well github now in the hands of...

This script works. Have to edit to remove frontmatter, change file name, ensure title comes up in post.

We can bulk upload to github repo also. But then only files listed in summary.md will be built into gitbook. If we figure out a way to list all posts in summary.md, then our medium --> gitbook migration is sorted.

Located usecase similar to that of ours. These guys wanted more students to contribute tutorials and mediawiki wasnt working so well for them. so they migrated to gitpages. Find their discussion on migrating mediawiki content to gitpages below:Avogadro Discussion – 17 Oct 14

The only other option I can think of is to create a gh-pages branch in the avogadro git repo, as these automatically get rendered and served on github. That being said, I think your approach is better. The web dev aspect should be pretty...