Page MenuHomePhabricator

Move development build assets into a 'dev' folder
Open, Needs TriagePublic

Description

The Gulp.js build assets are currently generated and placed inside the src/wikipedia.org/ folder along with the uncompiled source files. This makes it difficult to distinguish which assets are produced by the Gulp build and which are manually edited.

To more cleanly see this distinction, we should place all the build assets into a separate, top-level dev folder that mimics the folder structure of the src folder.

The following files should be moved into the new folder:

  • Compiled handlebars files index.html
  • Compiled PostCSS files assets/postcss/
  • Compiled translation files assets/l10n/
  • Compiled images (the sprite file) & logo images should be copied over

This move will involve several changes to the Gulp build process. First to output the files into a new directory, and second to compress and minify those files from the new directory into production.

Event Timeline

Change 701524 had a related patch set uploaded (by Ishan Saini; author: Ishan Saini):

[wikimedia/portals@master] Move build assets into a top level 'dev' folder

https://gerrit.wikimedia.org/r/701524

Change 701524 abandoned by Ishan Saini:

[wikimedia/portals@master] Move build assets into a top level 'dev' folder

Reason:

Issues with .gitignore. Adding fresh patch.

https://gerrit.wikimedia.org/r/701524

Change 701557 had a related patch set uploaded (by Ishan Saini; author: Ishan Saini):

[wikimedia/portals@master] Move build assets into the top level 'dev' folder

https://gerrit.wikimedia.org/r/701557

@Tsiruot: Per emails from Sep18 and Oct20 and https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup , I am resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!). Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task. Please claim this task again when you plan to work on it (via Add Action...Assign / Claim in the dropdown menu) - it would be welcome. Thanks for your understanding!