[adamschwartz]

Gatsby is pretty powerful but also quite complicated and has a fair amount of issues to deal with.

For example it was pretty unergonomic to set up support for deploying to a `pathPrefix` [1] while retaining the ability to develop locally [2].

Nevertheless, we were able to make it work and have been relatively happy with Gatsby overall.

Absolutely! The docs are dual MIT and Apache licensed [3] so have at it. One note: we have not yet completely teased apart the so-called “engine” from our particularly implementation itself. This is something we’re planning to do, in part because we need to to support our other docs sites. You may find it easier to work with once we’ve done that. That being said, you can also just fork the repo, change the content and branding, and things should mostly “just work”. Of course if you run into issues along the way, we’d be glad to have contributions back to the project itself. Good luck!

[1]: https://git.io/JUJsy

[2]: https://github.com/gatsbyjs/gatsby/issues/16040

[3]: https://github.com/cloudflare/workers-docs-engine