Hugo is one option. Liquid and Jekyll may fit the bill too. But there are others. Many others, including a vast majority are open source.
You may want to look into the Write The Docs community.[1] In particular you may want to join the Slack workspace and take a peek in the "docs-as-code" channel.[2] There's a lot of useful, relevant information in there (although, because WtD is using the free Slack workspace, it's not archived like it would be with a paid subscription). I get the sense that you may want to make a decision quickly and just go with it. Before you do I might encourage you to pop in and ask for the community's input. You'll get a range of responses, I'm certain. To enforce certain standards and criteria (such as whether images have dimensions set or not) or want to enforce a particular style guide, you may want to consider building Vale into your pipeline.[3] If you were going an XML route, I would suggest Schematron.[4] If you maintained the docs source in GitHub, you might get additional contributors through pull requests. It looks like it's already there[5]. What's not clear to me is whether the files in the "Documentation" folder in the "linux" repo would be extended (since it's clear this is already a fork that's gone its own way) or whether an additional pCP-only docs repo is desired. And Netlify is popular for hosting, too.[6] [1] https://www.writethedocs.org/ [2] https://www.writethedocs.org/slack/ [3] https://github.com/errata-ai/vale [4] https://en.wikipedia.org/wiki/Schematron [5] https://github.com/piCorePlayer [6] https://www.netlify.com/products/ ------------------------------------------------------------------------ prabbit's Profile: http://forums.slimdevices.com/member.php?userid=11142 View this thread: http://forums.slimdevices.com/showthread.php?t=112712 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
