anyone here with jade’s experience?
@Ivor Thanks very much for your quick response.
My item was disabled even if was not using any prettyPhoto script. Although, it has a string ’.fn.prettyPhoto’ in it’s ‘init.js’ file, but it was only to check if the customer is using some third-party prettyPhoto plugin or not, the theme itself does NOT have any prettyPhoto script. I’ve submitted the file without any modification, plz recheck it.
Recently i read some tutorials on JADE Templating Engine and i love it’s templating system; means how you can define a template, it’s blocks and related functions (e.g. extend, prepend, append etc.). For me, it could become pretty usefull when developing an HTML template but the issue is .jade files don’t allow traditional HTML to be written in normal way and I don’t really like the new shorthand way of writing HTML. It might be because, it’s new for me thats why I wanna ask is it worth learning this shorthand language? as all I want is the template functionality of this engine.
Great News! I’m in for beta testing
node_modules contains grunt packages and instead of adding project path and start working w/ grunt, customer need to install all the packages that you used in grunt.
Normally is to include only the sass files, package, bower, to pass the file size problem, however if a customer want to work with grunt, that mean he already have some knowledge and can install packages by himself.Cheers
I’m relatively new to this build system concept, might be I’m not picking up what are you trying to say. What I’m saying is, from the above folder structure we can exclude 3 heavy folder (named node_modules, bower_components, test) and then we can zip all remaining files and folders for ThemeForest. What the customer will do? (assuming he knows how to work with built systems), he’ll extract all these files/folders in his development folder and then he’ll run the following commands:
Again, assuming he had installed all required technologies before hand (e.g. node.js, gulp, bower ….)
npm install to install all the listed node modules defined in
package.json, it’ll auto-create the ‘node_modules’ folder with all module files.
bower install to install all the listed packages defined in
bower.json, it’ll auto-create the ‘bower_components’ folder with all front-end dependecies.
3: Finally, he can start working on source files (included in ‘app’ folder) and when he require he can command to build ‘dist’ version, by using
In this way way our .zip file for themeforest will include only few KB’s/MB’s of development + configuration files and it’ll save hundred of MB’s from ‘bower_components’ and ‘node_module’ folders.
I work with grunt, and I include sass files and installation but you must be aware of packages(node_modules) because create long path names ://folder/folder/folder/folder… and you will get a soft reject on that. Cheers
But what’s the point of including ‘node_modules’ directory, when the final customer can install node modules with one command? and it will also increase the .zip file size by many folds.
I was wondering if is it good to put all of our development files (together with dist folder) in .zip file of HTML template here?
As can be seen in screenshot below: (definitely don’t need to include node_modules and bower_components)
As it is far more manageable to work on development files as compared to static .html files which have repetition of many code chunks (header, footer etc) similarly for CSS, instead of one long .css files it is good to split styles in multiple logical files. What is your experice? does any one of you have done it, what was the response from customers and does it cause increas/decrease in support request?
Well, when asked about it’s possibility from Envato help on twitter, they said:
Sometimes, if not too much times has passed. ^PRhttps://twitter.com/envato_help/status/617716024008273920
and when asked about the procedure and time frame:
You would create a ticket in our Help Center and explain the situation when you need the upgrade. Max would be a month. PRhttps://twitter.com/envato_help/status/617721847325405184
Hope it helps somebody else.
I want to buy use some codecanyon script in my commercial WordPress theme, before buying it’s extended license i’ll buy it’s regular license to see if it fulfill all my requirements. If i decides to implement it in my theme, i’ll need to buy an extended license, but can i update my existing regular license of same script to extended license? (by paying additional amount)