WPIntell

Source evidence

Custom Module admin.js

Snowball · support · 2017-06-26T21:11:00+00:00

Snowball plugin evidence original source source API
complaintsentiment
mediumseverity
0.86relevance
6replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

8 / 37 rows with source links

21.6% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
msteel unresolved
Since your admin.js files have been minimized how do you suggest incorporating admin.js into a custom module? The default gulp task will concat and minify all of the module admin.js scripts. While adding the new module, you can run gulp to watch for and run this task. Check out gulpfile.js for more details. Thanks for the quick response. I’m not seeing gulpfile.js in the plugin. Do you mean get it from git? Ah yes, you should grab it from GitHub for all the dev files: https://github.com/thomaspark/snowball OK, I’ll see if I have time to download and get it going. I’m finding some issues with adding a custom module that you may want to know in order to (in my eyes) improve the process. Our office has to keep uploads ignored so we don’t want to add code to the uploads folder. Also by using the basedir it doesn’t lend itself to multisite use. Perhaps adding a filter for the custom modules location? Also adding more instructions on gulp (that it is needed and how to use it) would be helpful. Thanks for the suggestions. Will beef up the FAQ with details about the GitHub repo and gulp. As far as location of custom modules, making it customizable is ideal, but curious where you’d save them? /my-theme/snowball/modules could work. And/or if you filter the location (or array of locations) then people could put it where it best suits them (i.e. a plugin rather than a theme)

Comments

6 shown
thomaspark 2017-06-26T22:18:00+00:00

The default gulp task will concat and minify all of the module admin.js scripts. While adding the new module, you can run gulp to watch for and run this task. Check out gulpfile.js for more details.

msteel 2017-06-27T13:01:00+00:00

Thanks for the quick response. I’m not seeing gulpfile.js in the plugin. Do you mean get it from git?

thomaspark 2017-06-27T15:11:00+00:00

Ah yes, you should grab it from GitHub for all the dev files: https://github.com/thomaspark/snowball

msteel 2017-06-27T15:18:00+00:00

OK, I’ll see if I have time to download and get it going. I’m finding some issues with adding a custom module that you may want to know in order to (in my eyes) improve the process. Our office has to keep uploads ignored so we don’t want to add code to the uploads folder. Also by using the basedir it doesn’t lend itself to multisite use. Perhaps adding a filter for the custom modules location? Also adding more instructions on gulp (that it is needed and how to use it) would be helpful.

thomaspark 2017-06-27T17:25:00+00:00

Thanks for the suggestions. Will beef up the FAQ with details about the GitHub repo and gulp. As far as location of custom modules, making it customizable is ideal, but curious where you’d save them?

msteel 2017-06-27T17:50:00+00:00

/my-theme/snowball/modules could work. And/or if you filter the location (or array of locations) then people could put it where it best suits them (i.e. a plugin rather than a theme)