[WikiToLearn Editors] [WikiToLearn] Staging for editors

[Luca Toma]

I think this are two thing.

I like the Russell idea but is not an alternative.

My idea is allow editors to do whatever they want (like moving things and
this kind of stuff) without breaking the production site.

For example try different way to organize the content before touching the
production.

This kind of things can be usefull to minimize the time with broken pages
and links when you want to re-organize something.

Toma Luca
Il 20 mar 2016 10:45 AM, "Cristian Baldi" <bld.cris.96 at gmail.com> ha
scritto:

> I really like Russell idea. Could be implemented with a simple extensions
> that adds the username prefix before the title?
>
> On Sun, Mar 20, 2016, 04:54 Russell Greene <russellgreene8 at gmail.com>
> wrote:
>
>> This seems like a great idea, but what would be much more powerful and
>> better for editors is a "draft" feature.
>>
>> The idea would be that you can create a page, and instead of publishing
>> it, it goes under the user page as a draft (or something similar). They can
>> later decide to move it onto the production, or delete it. The trick would
>> be making sure only the right people can see it (not sure about how to do
>> this part)
>>
>> I'm not sure about how to go about a implementation of this, but it seems
>> like a better fix.
>>
>> Just my two cents 😊.
>>
>> -Russell
>>
>> On Fri, Mar 18, 2016, 04:23 M Bona <matteo9496 at gmail.com> wrote:
>>
>>> With the editors, at the sprint, we discussed the idea of having
>>> something similar to what you are talking about. So, for us it would be a
>>> great thing!
>>>
>>> Il venerdì 18 marzo 2016, Luca Toma <toma.luca95 at gmail.com> ha scritto:
>>>
>>>> The idea is: have a spare copy of production site to make tests about
>>>> managing content, try new templates and all this kind of stuff.
>>>>
>>>> Like tuttorotto.org or wikitolearn.vodka for tech stuff but for
>>>> editing stuff
>>>>
>>>> Toma Luca
>>>>
>>>> 2016-03-18 9:53 GMT+01:00 Sofia Liguori <s.liguori4 at campus.unimib.it>:
>>>>
>>>>> I didn't get the point... what are you suggesting? A box with the most
>>>>> important conventions and templates?
>>>>>
>>>>> 2016-03-17 21:58 GMT+01:00 Luca Toma <toma.luca95 at gmail.com>:
>>>>>
>>>>>> Automatic reset can be dangerous if a work is longer than short
>>>>>> amount of time or you forgot about automatic reset.
>>>>>>
>>>>>> I think we can build something with email from mantainers or a
>>>>>> telegram bot command center
>>>>>>
>>>>>> Toma Luca
>>>>>> Il 16 mar 2016 21:43, "Riccardo Iaconelli" <riccardo at kde.org> ha
>>>>>> scritto:
>>>>>>
>>>>>>> On Wednesday, March 16, 2016 09:12:43 PM Luca Toma wrote:
>>>>>>> > Hi!
>>>>>>> > What do you think about mantaining some kind of staging env for
>>>>>>> editing
>>>>>>> > stuff?
>>>>>>> >
>>>>>>> > For example templates, all kind of content stuff.
>>>>>>> >
>>>>>>> > The idea is create a sandbox for editors to avoid tuttorotto stuff
>>>>>>> on
>>>>>>> > production site.
>>>>>>> >
>>>>>>> > This instance will be managed as a production env (rollout, backup
>>>>>>> and
>>>>>>> > stuff like that).
>>>>>>> >
>>>>>>> > Can be usefull?
>>>>>>> >
>>>>>>> > If it is we can plain to boot it up with all new server stuff.
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> that makes lots of sense, but can you elaborate a little more on the
>>>>>>> data
>>>>>>> management? Would it be used only for ephemeral development (i.e.
>>>>>>> reset every
>>>>>>> 24 hours), or...?
>>>>>>>
>>>>>>> Bye,
>>>>>>> -Riccardo
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> WikiToLearn mailing list
>>>>>> WikiToLearn at kde.org
>>>>>> https://mail.kde.org/mailman/listinfo/wikitolearn
>>>>>>
>>>>>>
>>>>>
>>>> _______________________________________________
>>> WikiToLearn mailing list
>>> WikiToLearn at kde.org
>>> https://mail.kde.org/mailman/listinfo/wikitolearn
>>>
>> _______________________________________________
>> WikiToLearn mailing list
>> WikiToLearn at kde.org
>> https://mail.kde.org/mailman/listinfo/wikitolearn
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/w2l-editors/attachments/20160320/b38f64a6/attachment-0001.html>