2. "Optimize CSS" option:
An option for CSS optimization is now added, and this feature allows to join and minify CSS. While handling a complex site with many extensions, the number of CSS file can be PITA for you. This option will reduce the number of CSS files and optimize them in the best way. Now you can have less worries about the IE issue of maximum limit of 31 individual styleSheet per web page.
IMPROVEMENT AND BUG FIXES
There are about 35 bug fixes and improvements for this release. You can read our Changelog in Github for the full details. Here is the summary of some significant improvement and bug fixes that you may need to know.
- Improve performance for development mode | Link
In this version, T3 will only build files with changes, unchanged files will not be re-built, and this will save time and make the development process goes faster.
- Update Less css js to 1.3.3 | Link T3 is now up-to-date with the latest version of Less v1.3.3 and Bootstrap v2.2.2
- Move configuration of Megamenu from file to database | Link
The benefit of this improvement is it helps you to create a quickstart more quickly and easier.
- Duplicated submenu when add a blank column | Link
If you have been working with earlier versions of T3, you must have noticed this annoying bug, its fixed now.
- Correct show/hide configuration in backend for Article page | Link
- Last but not least: we have fixed the jQuery conflict | Link
You should note that this release of T3 Framework cannot work directly with our earlier released T3 templates. The reason for this is that since the version 1.1.0 RC1 of T3, we have made significant changes in both back-end and code:
- Change the prefixes: remove all the JA prefix, from ja-/ja_ to t3-/t3_
This change is applied in Megamenu, template layout/block, Less files and code.
- Rename plugin & template: Plugin: “jat3v3” to “t3” and Template: “ja_t3v3_blank” to “t3_blank"
Why we made such changes? As we have mentioned on the Future of T3 Framework blog post, we are looking for co-authors and co-developers to develop T3 to the whole new level, and the remove of JA prefixes will make T3 Framework become more standardized.
As for our earlier released T3 templates, especially JA Mero, JA Brisk, JA Onepage which were built on T3 1.0.0 RC1, we have plan to update these templates to T3 1.1.0 stable version in the coming weeks.
If you are not familiar with T3 yet, take your time to read through other amazing features in T3 blog series: