I am cross-posting this message from the r-studio community and am posting here because the question is more about Hugo than Rmarkdown.
My office is doing something interesting with bookdown, and I want to consult the community here to make sure everything is doable.
We are currently working on a wikipedia-like document in that we want to ultimately create a website that people can view and edit. A collaborative living document.
We started off writing in bookdown because it has great defaults for publishing html pages and it is easy to get someone up and running. Thanks to everyone who works at bookdown for making a really revolutionary system.
However ultimately, we don’t want someone to have to get set up on our shared dropbox folder (we don’t use git… yet) to make edits. We want a wikipedia-style interface where you can click on something and then edit that page.
On the other hand, i am in no way a web developer, and dont want to try and maintain a non-static website.
Bookdown has great github integration. At least for gitbook output, you can link directly to the git repo you are hosted with and people can make edits from there. Then I saw this web IDE from gitlab and I think this is exactly what I want. Here is my proposed workflow, I would appreciate comment on if people think it is feasible.
- Upload everything we have from dropbox to gitlab
- Use Hugo to create a static website that borrows a lot of design elements from gitlab
Set up netlify with our gitlab repo and enable continuous integration. This way, whenever someone merges a PR, the website updates automatically.
- On every page of the website, ensure that there is a link to the appropriate Rmarkdown document on gitlab.
- Ensure that when they click on this link, Gitlab’s web IDE opens and the user can use this interface, never having to download Rstudio (however great Rstudio is). Hopefully this interface is responsive and intuitive, but I can’t vouch for it yet.
- Enable me, my boss, and a few others to have automatic pushes, and act as maintainers for outsiders who want to make edits.
I’m pretty good with coding, and open to learning new things. I am under the impression this workflow has the right balance of learning new things and a well-supported, simple system.
My ultimate question is whether I should go with the mediawiki ecosystem instead. They provide collaboration out of the box, especially if you use a hosting service. However I explored the options and it seems there are a few issues.
Primarily, there No local editing. Unless we have a private wiki, we would have to make it open to the public. Even if it is private, the idea of not having a local repository of plain-text markup files scares me. It means that it is difficult to take our content to a new format. Overall, the mediawiki ecosystem seems designed for people with PHP knowledge and who are okay managing a server. I highly doubt that we will ever be remotely large enough for something this heavy duty.
On the other hand, built-in collaborative editing seems fantastic, as does tight integration for cross referencing.
I would be curious to see what the people at Hugo think about this dilemma. All thoughts are welcome.