[jira] [Commented] (CB-13162) cordova-docs should be built and published automatically on every change
[ https://issues.apache.org/jira/browse/CB-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247443#comment-16247443 ] Jan Piotrowski (Sujan) commented on CB-13162: - Isn't the other issue missing all the information on translation we talked about here? > 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 (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13162) cordova-docs should be built and published automatically on every change
[ https://issues.apache.org/jira/browse/CB-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242635#comment-16242635 ] Audrey So commented on CB-13162: This is a duplicate issue. Closing this one and using --> https://issues.apache.org/jira/browse/CB-13543 Thanks! > 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 (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13162) cordova-docs should be built and published automatically on every change
[ https://issues.apache.org/jira/browse/CB-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122174#comment-16122174 ] 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 (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13162) cordova-docs should be built and published automatically on every change
[ https://issues.apache.org/jira/browse/CB-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16120553#comment-16120553 ] 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 (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13162) cordova-docs should be built and published automatically on every change
[ https://issues.apache.org/jira/browse/CB-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16120549#comment-16120549 ] Jan Piotrowski commented on CB-13162: - > any languages in crowdin that have close-to-100% translation are pulled in > and integrated into the built docs Using the Crowdin Github integration the -docs repo would actually get Pull Requests to an integration branch. There these could be checked and accepted, and merged to the main branch when ... (whatever acceptance criteria is met) and then automatically deployed as your described. I don't know anything about how the docs go from repo to website, but if this was hosted via Github Pages (which is also Jekyll, Netlify is another tool that does this) this would all happen automatically as soon as the changes hit the repo. Hopefully not too hard to replicate that. > 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 (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
