After a couple more hours of playing with this...

> On Feb 8, 2022, at 2:26 PM, Dirk Hohndel  wrote:
>> 
>> 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:
>> 
>> https://github.com/subsurface/subsurface.wiki.git 
>> <https://github.com/subsurface/subsurface.wiki.git>
> 
> 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.

Well, maybe not. The options are "anyone can edit a wiki page" (sorry, been 
there, done that, HECK NO), or "the same group of users that can edit the wiki 
also have push access to the repo" (sorry, that's an idiotic equivalency). So 
I'm afraid the access control for wikis on GitHub is just not at the level that 
I'd need to be comfortable with this.

> 
>> 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?
> 
> Yeah - but likely that would get us back to the place that we're in with the 
> GitHub.io <http://github.io/> 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 GitHub.io 
> <http://github.io/> pages. There really wouldn't be any difference.
> 
> 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 guinea 
> pigs for this - just to give this a try :)

Since this didn't work, I'll play with other ways to get close to this.

Maybe the simple answer is not to have the complex "accordion" style FAQ but 
instead do far simpler pages that feel much more like a wiki and that are 
easier to edit for casual contributors - but with decent access controls... 
which brings me back to needing to figure out an easier way to create a PR for 
the GitHub.io pages.

Sometimes it feels like I'm running in circles :)

/D
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to