Redaxscript 2.1.0

Date Submitted: May 20 2014 09:13 pm
Posted By: The Redaxscript development team

Codebase refactoring



Our goals for this milestone have been attained and even exceeded. We focused on the problem of deprecated constants while refactoring and introduced a registry singleton to allow working with dependency injection. Furthermore, an autoloader now handles loading of classes as needed and a fresh bootstrap.php was introduced to replace startup.php one day. After spending hours of work with PHPUnit we are proud to announce a test coverage of 98 percent for the OOP codebase.





In addition Redaxscript now is represented in Coveralls and Scrutinizer CI.




Documentation is king



Based on Apigen an external API documentation for the OOP codebase is available under api.redaxscript.com and will be frequently updated on each release.



We put great effort into our website to improve your experience. See the overhauled FAQ section in a fresh look and with more questions. Trouble understanding how modules work should be a thing of the past, each description was extended with installation and usage tabs including multiple examples.




Flat template style



We followed the work in 2.0.0 and continued to flatten the admin and default templates. A couple of UI elements like accordion, dialog and tab have experienced a colour revision. Most partials were extended with inline comments and divided into more files to improve readability.





Last but not least, the Scratch template got a fresh typography and was again greatly simplified in order to facilitate the development of templates.




Vendor prefixes



Time to get rid of outdated vendor prefixes by parsing CSS files with the Postprocessor named Autoprefixer, a mind blowing tool based on the popular caniuse.com database to determine needed browser support. We are following a last 2 versions strategy like Goggle does, except for Internet Explorer where we will support the last 3 versions. It was a liberating moment to realise that we saved around 500 rules CSS in our templates.




Native form validation



Our form validation now uses the native checkValidity() method and gives specific error messages to highlight required fields. Third party libraries like jQuery, QUnit and Zepto were raised to the latest version.




Fresh modules



Once you have installed the new Disqus module, all native comments are replaced where they were enabled. Enjoy the social engagement and traffic to your website as well as improving your SEO.





Furthermore, a new Github module was written to display project milestones and issues on our website. Due to the limited time window for refactoring, we made the decision to discontinue our SEO tube module and therefore removed related download.



Again, there is much more to explore. Read full changelog

Post A Comment

Name:
Comment:
Human Verifier:
(enter the 4 blue numbers you see above)
 
Error! Invalid human verify code
Thank you for your comment. After we have reviewed your comment (to make sure it is not spam) it will be posted below.

veery-contrast