English:
Hello
Not fluent in English, so this is a translation from Google Translate in
Spanish my original note (below)
I think it can be solved elegantly using a template and categories
We can create a template called Status, you simply assign certain categories
page.
For example:
{{Status | Draft | RGB-es}}
Inserts the entry into the category page "Draft", and subcategory page "Draft
by RGB-es"
When the page is revised, we can change the template for
{{Status | Review | Pescetti}}
Insert the entry into the category page "Review", subcategory page "Review by
Pescetti"
Finally, when the page has been approved for publication, simply remove the
entry {{Status | NNNN | YYYY}} of it.
The entries in the category and subcategory pages automatically disappear.
If you think it, I can create the template structure, and you only have to
decide which categories will be required. Modifying the template {{Status}} we
can add new categories as needed.
regards
Español:
Hola
No domino el inglés, así que esto es una traducción de Google Traductor de mi
nota original en español (más abajo)
Creo que se puede solucionar de forma elegante utilizando una plantilla y
categorías
Podemos crear una plantilla llamada Status, que sencillamente asigne a la
página determinadas categorías.
Por ejemplo:
{{Status|Draft|RGB-es}}
Inserta la entrada en la página de categoría "Draft", y en la página de
subcategoría "Draft by RBG-es"
Cuando la página sea revisada, podemos cambiar la plantilla por
{{Status|Review|Pescetti}}
Insertará la entrada en la página de categoría "Review", y en la página de
subcategoría "Review by Pescetti"
Finalmente, cuando la página haya sido aprobada para su publicación,
sencillamente eliminamos la entrada {{Status|NNNN|AAAA}} de la misma. Las
entradas en las páginas de categoría y subcategoría desaparecen automáticamente.
Si os parece bien, puedo crear la estructura de plantillas, y tan sólo teneis
que decidir las categorías que serán necesarias. Modificando la plantilla
{{Status}} podemos agregar nuevas categorías, según necesidad.
Saludos
Salva
-----Mensaje original-----
De: RGB ES [mailto:rgb.m...@gmail.com]
Enviado el: lunes, 25 de febrero de 2013 0:17
Para: doc@openoffice.apache.org
Asunto: Re: [Discuss]Call for volunteers [Was: Re: Starting to build the user
guide]
2013/2/24 Andrea Pescetti <pesce...@apache.org>
> On 20/02/2013 RGB ES wrote:
>
>> 2013/2/19 Rob Weir
>>
>>> Maybe this already exists, and it already exists, but it might help to
>>> have a series of page tags for things like:
>>> 1) This page is being drafted by XXX and is not ready for review yet
>>> 2) This page has been drafted and is ready for editing
>>> 3) This page is currently being edited by XXX
>>> 4) This page is done editing and is ready for technical review
>>> 5) This page is being reviewed by XXX for technical contents
>>> 6) This page is ready for final review/approval
>>> 7) This page is approved for publication
>>> Or is this overkill? ...
>>>
>>
>> Maybe just a bit overkill... :)
>> What about a "status page" on the wiki?
>>
>
> I agree that a simple status page may be enough for the time being. Then
> we are free to add more complexity as needed, and it's good that all
> technology is already there.
>
I finally started a "status" page:
http://wiki.openoffice.org/wiki/Documentation/UserGuide/Status
It lists all the existing pages and several of the needed ones.
I know many users checked the pages I wrote (many thanks!) but I have not
had the time to look at the history of the pages to acknowledge all of them
on this status page, sorry.
Any idea how to improve the readability of this status page?
Regards
Ricardo
>
> Regards,
> Andrea.
>
