Translating Official Documentation to Spanish

@ayalaluquez, @map0logo and me have been participating in the South American Jupyter Workshop this weekend, and started a working group to begin translating the official Jupyter documentation to Spanish.

The first thing we noticed is that there's no spanish docs at all in the documentation library: https://jupyter.readthedocs.io/. So we decided to start from the beginning and work on the "Jupyter Notebook Quickstart" section. We translated all subsections:

tryjupyter.rst running.rst install.rst contents.rst migrating.rst install-kernel.rst glossary.rst

There's still some work to be done, particularly with checking internal references and rst formatting (didn't try to build the docs with sphynx yet), but we think translation is mostly completed.

We have forked https://github.com/jupyter/jupyter to https://github.com/camporeale/jupyter/ to temporarily work on this, and commited all translated files as {original}.es-ES.rst.

The only reference to the translation work we've found was this issue created last year on the jupyterhub repo.

We tried to follow some of the recommendations and definitions there, and the translation conventions on The Carpentries repo.

As I said before, the forked repo is just a temporary measure, because we're not sure what procedure we should follow to make the new docs publicly available in the official page in readthedocs.

So, there are a few questions we would like to ask:

• What would be the way to commit these files? Should we work on a forked repository and send pull requests for the new files? Create a specific repository for spanish documentation and upload there?

• How are the docs on readthedocs.org generated? We assume that there's an automated workflow with hooks from Github, so this would be very closely related to the previous question. On the other hand, there should be a decision on the URL for the docs, maybe using a path like https://jupyter.readthedocs.io/es/latest?

• Do you have any ideas/preferences regarding to work on next? We've been thinking that the most important thing would be to translate the documentation more related to new/inexperienced users, as they're the ones that would probably benefit the most to have docs in their native language (we believe that more advanced users have probably had more exposure to english documentation). But there is a lot of work to be done, we could continue translating the "Architecture" or "Installation, Configuration, and Usage" sections. But other suggestions are welcomed.

There's one last thing we talked about but did not worked on: application menus localization. We think that would probably have a also a huge impact for beginners, but it's something that we probably should talk about on another issue / discussion.

@fperez @willingc @damianavila @Ruv7 @choldgraf