| 16 | | === During the Hackaton day: 1) we concentrate in translation |
| 17 | | 1. We conform groups of translators by topic of interest. |
| 18 | | 1. Start the traslation work of each page, by opening a ticket, and mention there who is in the translation group. |
| 19 | | 1. Or do this process collectively by using a common pad editor in each group. |
| 20 | | 1. At the same time we have a central pad to bring questions and clearify criteria and conventions, and also a mumble for audio communication during the Hackaton |
| 21 | | 1. |
| 22 | | 1. Create new wiki page with the same name (and path) AND add **.Es** at the end of the name. |
| 23 | | 1. Start the translation in this blank page OR bring all the content of the english version to the new .ES page and translate there. Alternatively, peo |
| 24 | | 1. Translate, review and update the ticket with the progress |
| 25 | | |
| | 16 | === Before the Hackaton day |
| | 17 | 1. We promote the Hackaton with two or three months in advance with the help of graphic design that expresses the relevance of Internationalism and Solidarity as technological transfer. |
| | 18 | 1. We setup the right queries for automatically showing the progress of the translation, during the Hackaton. |
| | 19 | 1. We conform two working groups: Wiki Editors [https://support.mayfirst.org/wiki/WikiFormatting familiar with the WikiFormatting markup language] and Ilustrators who will prepare the ilustrations in spanish of the interfaces, menus, etc. already shown in the english versions. |
| | 20 | |
| | 21 | |
| | 22 | === During the Hackaton day: First, we concentrate in translation |
| | 23 | We conform groups of translators by topic of interest. |
| | 24 | |
| | 25 | ==== For every body |
| | 26 | 1. We have a central pad to bring questions and clearify criteria and conventions, and also a mumble for audio communication during the Hackaton. |
| | 27 | 1. The query system will show in real-time the over all progress during the journey and if we have succeded by reaching the goal at the end. |
| | 28 | |
| | 29 | ==== For each translation working group |
| | 30 | 1. First concentrate on translation, without concern of text formating or images, just text traslation. |
| | 31 | 1. Start the traslation work of each page, by opening a public ticket and mention there which page will be translated and who is in the translation group. And update there when you have finished, or in case you have suspended. Use the ticke to let others know about the work that your group is doing on every page separately. |
| | 32 | 1. Copy the content of each page and paste it in a common pad text editor that the group uses to translate and convene on corrections and improvements |
| | 33 | 1. Once you have finished, create a new wiki page with the same name (and path) AND add **.Es** at the end of the name. |
| | 34 | 1. Copy the text from the pad, directly in the new wiki page and save it. Update the corresponding ticket for this wiki page. There in the ticket, in case you need it, ask for help to Editors and Ilustrators, as to make the page look pretty and to improve it with visual material. |
| | 35 | 1. In case there are no images in spanish, please consider contributing with images if you are able, Editors can help you to publish them correctly. If you are not able, organizers will solve later, just make sure |
| | 36 | |
| | 37 | ==== For Ilustrators and Editors |
| | 38 | 1. By on hold to address questions and support the translation working groups once they have finished |
