Jan Piotrowski commented on CB-13162:

Oh, I was assuming the docs were actually some form of Jekyll from what I saw.

I am with you on the explore part (but will actually wait until the move of 
issues to Github is complete because this will make it so much easier to 
iterate quickly).

> 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