I’ve recently joined a group of developers that is going to set up an ELGG site for a rising political movement in Spain.
We expect to have new developers joining soon, as well as people from all around contributing now and then, and we need to ensure that they do not have a steep learning curve when it comes to contributing to our ELGG project, so I need to work on Spanish documentation (e.g. writting plugins, data models, API). My guess is that most of the work will be translating existing documentation, and ocasionally creating original documentation in English and then translating it.
I don’t want to work downstream in our own wiki, I would really prefer to do the work on the ELGG official wiki to avoid duplication, and reach a wider audience.
So, could someone here let me know what should I (or anyone else in our documentation team, which is still coming together) do to get an account that we can use to write in the ELGG wiki? So far I’ve only been able to find the log-in page, nothing about registering. I also tried using the community account for the wiki, to no avail.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Adrián Chaves Fernández (Gallaecio)@Gallaecio

Adrián Chaves Fernández (Gallaecio) - 0 likes
- Evan Winslow@ewinslow

Evan Winslow - 0 likes
- Adrián Chaves Fernández (Gallaecio)@Gallaecio

Adrián Chaves Fernández (Gallaecio) - 0 likes
You must log in to post replies.Reading http://docs.elgg.org/wiki/Documentation/Guidelines now, maybe I can find what I was looking for.
That's great news! Thanks for getting involved. It will be great to have more translations and docs available and agree on your approach to contributing to the official docs rather than maintaining your own, as you say.
The wiki is deprecated and we are moving everything to learn.elgg.org. To add new docs, you should submit a PR on github against the 1.9 branch. Also, read up about our documentation style, organization, and standards.
If you just want to focus on contributing translations, that of course appreciated as well. But in order to do this for the docs, you should chime in on the relevant github ticket and make your case. The rest of the core team unfortunately has not been interested in translating the docs historically, but I believe they are open to being persuaded.
I see, many thanks!
I will look into the Github ticket (I was already having a look at http://sphinx-doc.org/latest/intl.html).