cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Piotrowski (Sujan) (JIRA)" <>
Subject [jira] [Commented] (CB-13338) How does the build process work?
Date Thu, 28 Sep 2017 11:52:02 GMT


Jan Piotrowski (Sujan) commented on CB-13338:

Thanks for these clarifications, I now much better understand what is going on. 
For example it wasn't clear to me that Gulp and Make are alternatives for the same process.

As I already mentioned on Slack, I am not interested in changing the process - just document
it better so one can get an impression what is going on without having to install everything
just to find out what the build process actually does.

> How does the build process work?
> --------------------------------
>                 Key: CB-13338
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Sub-task
>          Components: cordova-docs
>            Reporter: Jan Piotrowski (Sujan)
> Per and
the build process of the website is handled by `gulp`.
> tells us to install
_Ruby_, _python_, _Node.js_, the _dependencies _for both Ruby and Node, and optionally _Make_.
> From looking at `www` I know the website is _actually_ a Jekyll website.
> This leads to a very confused me and several questions:
> # How does the build process with Make work? Is this documented?
> # What is python required for?
> # What is node.js required for? gulp?
> # What does the gulp thing actually do? The README only mentions serve, watch, build
- but the gulpfile contains _so_ much more.
> # What workflows or processes are "hidden" in the gulpfile that should better be documented?
> # What is the difference between PROD and DEV in this build process?
> # How does the fetching of external docs work?
> # Is there anything about translations in there?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message