Are Collaborative Guides something you would like to see, or participate in?
I think there'd be a few workarounds to develop this feature. Mods and admins can access ANY guide on the site and edit it - the EDIT button (among others) is available for us to use. Of course I've never used that feature except when an author has asked me why their coding had gone out of whack.
So my first workaround would be to have some sort of form that requested share access/collaboration with a guide, and then the guide could be released to the person needing access (so for example, Hopper could request access to one of your guides and then be able to edit it). This would leave the guide on your profile, but perhaps there'd be a way to allow access on her profile too.
The second workaround I could see is similar to how admin can assign a guest guide to someone who makes a profile. It's happened so many times before where someone says "I wasn't signed in when I made a guide" and the guide is just plopped into their account. Couldn't that also happen "multiple times", so a guide is plopped into place across multiple accounts? (obviously it'd need to be coded so the guide isn't duplicated, just assigned to multiple accounts)
Other issues with collaborative guides:
> Who's elo is displayed? Is it averaged out? What if there is 1 writer and 1 coder?
Benefits:
> If multiple authors write the guide, it'll more likely be kept up to date
> More collaboration across the site
> Chance for a "community guide" for champions (to go with the champion information build data!!!)
> Guide exposed on multiple profiles/signatures
> It'd be lots of fun (in the past I've tried to write collaborative guides with many MobaFire users, but they've always failed because we never could really edit it whenever we wanted etc)
> More discussion on guides as multiple authors can reply
Anyway.
So my first workaround would be to have some sort of form that requested share access/collaboration with a guide, and then the guide could be released to the person needing access (so for example, Hopper could request access to one of your guides and then be able to edit it). This would leave the guide on your profile, but perhaps there'd be a way to allow access on her profile too.
The second workaround I could see is similar to how admin can assign a guest guide to someone who makes a profile. It's happened so many times before where someone says "I wasn't signed in when I made a guide" and the guide is just plopped into their account. Couldn't that also happen "multiple times", so a guide is plopped into place across multiple accounts? (obviously it'd need to be coded so the guide isn't duplicated, just assigned to multiple accounts)
Other issues with collaborative guides:
> Who's elo is displayed? Is it averaged out? What if there is 1 writer and 1 coder?
Benefits:
> If multiple authors write the guide, it'll more likely be kept up to date
> More collaboration across the site
> Chance for a "community guide" for champions (to go with the champion information build data!!!)
> Guide exposed on multiple profiles/signatures
> It'd be lots of fun (in the past I've tried to write collaborative guides with many MobaFire users, but they've always failed because we never could really edit it whenever we wanted etc)
> More discussion on guides as multiple authors can reply
Anyway.
That moment when you suddenly remember all those painful hours working with Git/GitHub and its logic can be applied on MobaFire. Not sure whether you guys are familiar (I'd assume the devs are), but I can see something similar with this idea. You take a guide and make it open source, allowing people to clone it (literally make a copy of it to their 'Guides' section), make their own changes/additions and commit them. Then someone can review said changes and decide whether it is an improvement or not.
I am not entirely sure how hard this would be to implement, tough. That said, I am definitely interested in this idea!
I am not entirely sure how hard this would be to implement, tough. That said, I am definitely interested in this idea!
|
That's certainly an interesting approach Re4XN. I'm also unsure of how difficult that would be to implement but it would solve the potential problem of two users editing the same guide at the same time. If the main author has to approve all changes that would be pretty easy. The only problem is that it'd mean the main author would have to be checking in to approve new commits pretty often.
Ultimately it kinda seems like that's not far off the workaround solution that people use right now, which is to make the guide in a googledoc and then send changes to the main author and have them implement them manually. It's something to consider though.
Ultimately it kinda seems like that's not far off the workaround solution that people use right now, which is to make the guide in a googledoc and then send changes to the main author and have them implement them manually. It's something to consider though.
Thanks to Jovy for the sig!
Love the idea of collaborative guides, given how I'm horrible at the code part, whereas my friend isn't. I can see the benefits in places where maybe I know really well how the champ plays up against certian other champs, but my friend knows how it plays up against others. Or even a section on the synergy that the champ might have with another champ that my friend plays, where then he can add a section on how to make that synergy work really well, or even a short snippit on how to play the synergy champ.
tl;dr I would love to have this ability added. As for how to impliment it, I worry that it might be a headache to do, and for the perms of who "owns" the guide. Yikes.
tl;dr I would love to have this ability added. As for how to impliment it, I worry that it might be a headache to do, and for the perms of who "owns" the guide. Yikes.
Thanks to Mozume for the beautiful signature! <3
Re4XN wrote:
That moment when you suddenly remember all those painful hours working with Git/GitHub and its logic can be applied on MobaFire. Not sure whether you guys are familiar (I'd assume the devs are), but I can see something similar with this idea. You take a guide and make it open source, allowing people to clone it (literally make a copy of it to their 'Guides' section), make their own changes/additions and commit them. Then someone can review said changes and decide whether it is an improvement or not.
I am not entirely sure how hard this would be to implement, tough. That said, I am definitely interested in this idea!
I am not entirely sure how hard this would be to implement, tough. That said, I am definitely interested in this idea!
Me as the author of the highest voted Rakan Guide would love such a feature. I already messaged a xayah guide author and a shyvana guide author. The one for shyvana already answered and we are trying a little collaboration with visuals and sectionbanners for example. They put a lot of effort on writing and testing things and I changed some visuals or sorted the sections so the guide doesn't look like a giant mess. It sounds kinda hard but I'm a perfectionist myself and when reading through some guides that have such huge amounts of work and testing their visuals look so confusing and everthing is mixed up!
For such purposes or to work together with other guide authors of the same guide I'd love this feature.
I would've put it like giving the "Co-Workers" of your guide different ranks. For example "Designer", "Co-Author", "Tester", "YouTuber", "Streamer", "Helper" etc.
And as already mentioned a system like wikipedia has. Every other [approved] collaborative person can send a version where he/she edited something and the main author can approve it if it's something good.
But a backup function would be necessary if you accidently approve something bad or someone tries to destroy a good guide with lie and cheat.
PsiGuard wrote:
Ultimately it kinda seems like that's not far off the workaround solution that people use right now, which is to make the guide in a googledoc and then send changes to the main author and have them implement them manually. It's something to consider though.
I guess the difference is that you don't have to use a platform outside of MobaFire. If the user could hit EDIT, make a few changes, then SEND it, the author could review the changes (which would be highlighted or somehow shown to be visible) and APPROVE or DENY. Would be pretty cool :) In fact, it'd be nice to be able to save versions, so you could back up to a previous version if something happened.
jhoijhoi wrote:
(...) APPROVE (...) save versions, so you could back up to a previous version if something happened.
Essentially clone and merge (branches) from Git, the resemblance is uncanny xD
|
|
You need to log in before commenting.
<MOBAFire Mother>
♡ sig unintentional collab with Jovy and me ♡