Filip Maj commented on CB-13162:

These are really good suggestions. I am not sure how viable the docs in their 
current form can exist as Jekyll pages, since they require some pre-processing 
to generate tables of contents and link documents within the repo, but it is 
worth checking out.

We should most definitely explore the translation experience a bit more - none 
of the PMC members have gone through this flow so I think there is very little 
empathy and understanding for that flow at this point. Spending some time on 
that would make this an easier experience for our translators, which sounds 
like, is sorely needed.

> cordova-docs should be built and published automatically on every change
> ------------------------------------------------------------------------
>                 Key: CB-13162
>                 URL: https://issues.apache.org/jira/browse/CB-13162
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: cordova-docs
>            Reporter: Filip Maj
>              Labels: backlog
> I would like to see the docs have better automation.
> My ideal situation (and I don't think this is outside the realm of 
> possibility) is that, on every change to cordova-docs:
> * the sources in crowdin are automatically updated (the crowdin GitHub 
> integration does all of this work for us)
> * the cordova-docs get automatically built into a publish-ready state
> * any languages in crowdin that have close-to-100% translation are pulled in 
> and integrated into the built docs
> * the built + translation-integrated docs are finally pushed/published so 
> that docs.cordova.io is updated automatically.
> We should also document this in the README if we ever get around to this 
> issue :)

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to