Of course, if more than one person knows the password to the same account.
DuffTime wrote:
ok ok plz carry me omg
i was only waiting for you to ask
Temzilla wrote:
Too hot to be icecream.
Luther3000 wrote:
He looks like a hair gel advert on legs
Toshabi wrote:
Icecreamy, with hair as slick and smooth as the ocean waves of Cocobana
That is not possible ;)
DuffTime wrote:
ok ok plz carry me omg
i was only waiting for you to ask
Temzilla wrote:
Too hot to be icecream.
Luther3000 wrote:
He looks like a hair gel advert on legs
Toshabi wrote:
Icecreamy, with hair as slick and smooth as the ocean waves of Cocobana
sure thing. it'd just be safe to credit both.
Thank you jhoijhoi, Keondre, LaCorpse, The_Nameless_Bard, Arcana3, Apfeljack, Hogopogo, eddie199, Xiaowiriamu, and JEFFY40HANDS for the spectacular sigs!

It's one of those things that will take enough work, and will be utilized by so few people, that it may never make it to the top of the list :( There are also some complex issues that arise in terms of locking guides to prevent simultaneous editing.
My recommendation for now is to use a shared Google docs document for the bbcode and just credit both of you at the beginning / end of the guide, but post it under one person's account. Make that person manage all the publishing in exchange for having it listed under their account ;)
My recommendation for now is to use a shared Google docs document for the bbcode and just credit both of you at the beginning / end of the guide, but post it under one person's account. Make that person manage all the publishing in exchange for having it listed under their account ;)
You could also make a new account, share the password with whoever you want to make a guide together with and edit as you please ;)
DuffTime wrote:
ok ok plz carry me omg
i was only waiting for you to ask
Temzilla wrote:
Too hot to be icecream.
Luther3000 wrote:
He looks like a hair gel advert on legs
Toshabi wrote:
Icecreamy, with hair as slick and smooth as the ocean waves of Cocobana
@Matt
You don't really need to lock guides. At best one's changes will be overwritten by the other's. If you do lock guides while editing then it could turn into a potentially bad situation when one of the owners leaves it open. I've used similar systems for managing websites and it's just a pain when someone forgets to close the damn editor.
A good system would be for the users to receive a message when the guide is edited. That way if you're editing the guide and someone else publishes it you'll know immediately. It would also make it much easier for the owners to communicate as they could write a small comment or change-log in each of those messages. It can be easily done manually by the users as well, so as long as you leave a suggestion box at the top of each co-owned guide it should be fine.
You don't really need to lock guides. At best one's changes will be overwritten by the other's. If you do lock guides while editing then it could turn into a potentially bad situation when one of the owners leaves it open. I've used similar systems for managing websites and it's just a pain when someone forgets to close the damn editor.
A good system would be for the users to receive a message when the guide is edited. That way if you're editing the guide and someone else publishes it you'll know immediately. It would also make it much easier for the owners to communicate as they could write a small comment or change-log in each of those messages. It can be easily done manually by the users as well, so as long as you leave a suggestion box at the top of each co-owned guide it should be fine.
You need to log in before commenting.
<Member>