Skip to content
This repository has been archived by the owner on May 31, 2020. It is now read-only.

Path to spanish docs contribution? #670

Open
sebassdc opened this issue Oct 8, 2017 · 4 comments
Open

Path to spanish docs contribution? #670

sebassdc opened this issue Oct 8, 2017 · 4 comments

Comments

@sebassdc
Copy link

sebassdc commented Oct 8, 2017

I'll like to help translating the batavia docs. I will copy the actual docs to translate them line to line. What folder structure would you recommend me to put the spanish doc? I mean, on what path.

@freakboy3742
Copy link
Member

@sebassdc Good question! We haven't started looking at translations for individual projects - to date, our translation efforts have been focussed on the main website.

A great way to contribute would be to sort out what exactly we need to do to translate Sphinx documentation. A good starting point will be this document. You're in new territory here, so any recommendation you make will probably be accepted!

@sebassdc
Copy link
Author

sebassdc commented Oct 9, 2017

Do you like the sphinx way? I would recomend another service like gitbook, its all markdown wich is more easy for everyone. I can help with the migration and the internationalitation. What do you think @freakboy3742 ?

@freakboy3742
Copy link
Member

Yes, we're going to keep Sphinx for docs. I don't agree markdown is better for long-form documentation - it lacks many features for multiple-page documents. It's also the standard for Python projects generally.

@sebassdc
Copy link
Author

sebassdc commented Oct 9, 2017

Ok, I will investigate sphinx Internationalization and help with that. But check the gitbook link and how the multi-page stuff is managed. Its very simple. I mean markdown its standard on many areas. It would be easiest to have more people with markdown knowledge

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants