<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 8, 2022, at 1:16 PM, Jef Driesen wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 8/02/2022 21:54, Dirk Hohndel via subsurface wrote:<br class=""><blockquote type="cite" class="">I haven't spent any time at all on the GitHub wiki setup to know how easily we could curate this and more importantly how easily one can create useful deep links to specific answers that could be posted into email / the forum. I understand very well how to manage submissions to the <a href="http://GitHub.io" class="">GitHub.io</a> <<a href="http://GitHub.io" class="">http://GitHub.io</a>> page through PRs.<br class="">I need to spend time to understand how that would work with the wiki. Because the very last thing I need on earth is another time sucking task.<br class="">I'd still likely be leaning towards just a set of markdown pages on the <a href="http://GitHub.io" class="">GitHub.io</a> <<a href="http://GitHub.io" class="">http://GitHub.io</a>> site instead of a wiki - but that's mainly because I haven't done the work to investigate how that would really work.<br class=""></blockquote><br class="">That's exactly what github wikis are: a collection of markdown files managed in a git repository. If you login to your account, you should see a link to clone the wiki locally. Should be something like:<br class=""><br class=""><a href="https://github.com/subsurface/subsurface.wiki.git" class="">https://github.com/subsurface/subsurface.wiki.git</a><br class=""></div></div></blockquote><div><br class=""></div>That is fascinating. I have to create that first page for this to work - but I played with it in your wiki and that does seem like a reasonable compromise. If we assume that we don't want to deal with translations, this is maybe an easier way to go.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">As far as I know, there is no interface for PRs, but you can always publish it as a normal repo in the project, and then manually push to the wiki repo to publish changes. It might even be possible to automate that last part with a github action?<br class=""></div></div></blockquote></div><br class=""><div class="">Yeah - but likely that would get us back to the place that we're in with the <a href="http://GitHub.io" class="">GitHub.io</a> page. Because fundamentally - either I allow people to edit the wiki (so I give people like Jason edit rights to the wiki) - or I do this via the PR interface and then I might as well build <a href="http://GitHub.io" class="">GitHub.io</a> pages. There really wouldn't be any difference.</div><div class=""><br class=""></div><div class="">So I'll have to take a look at how easy it would be to have a group of users whom I give write access to the wiki. And I'll use you and Jason as <span style="color: rgba(0, 0, 0, 0.85); font-family: ".SF NS"; font-size: 13px;" class="">guinea pigs for this</span> - just to give this a try :)</div><div class=""><br class=""></div><div class="">Thanks for pushing in this direction. Because the easier I make this, the more likely I'll be to get strong help.</div><div class=""><br class=""></div><div class="">/D</div></body></html>