mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #24131
[Bug 1259650] Re: Ability to turn js files into minimised versions for production sites
I think minification itself is sort of overrated. It does improve
performance, but not by a whole lot, like 5%.
So if it's easy to do, sure, we may as well (as long as we also include
an option to de-minify for dev purposes).
Something else we could do that might improve performance more, would be
to reduce the total number of file requests needed for each page, by
concatenating some of the CSS stylesheets together. Likewise for
Javascript files.
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1259650
Title:
Ability to turn js files into minimised versions for production sites
Status in Mahara ePortfolio:
Confirmed
Bug description:
Currently in mahara most css and javascript files are not
compressed/minimised - this is great if you are editing them as a
designer / programmer but means it is slower for sites to load.
It would be good if there could be a system that miniaturizes css / js files for production sites,
ie when $cfg->productionmode = true
I'm not sure how this will work - possibly an admin page with options
on what to minimise (that can also be accessed via commandline for
deployment scripts to access if needed) in conjunction with a
mod_rewrite rule so that the correct files are accessed.
Or maybe some other way of doing it - it would be good to find out
what others do for this kind of thing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1259650/+subscriptions
References