Efront has been around for quite some time (almost 12 years, actually!). During this time, we’ve witnessed the rise (and, occasionally, fall) of many great technologies, libraries and trends, several of which we had embraced ourselves. Time has come for some change though.
B. We’ve embraced Bootstrap 3, the popular UI framework for the web. It has a sleak, lightweight and fresh design and includes an awesome collection of widgets and animations. Equally important though is its mobile-first approach, which ensures that efrontPRO runs smoothly on all mobile devices.
C. With the power of jQuery and Bootstrap, we were able to make use of the latest and greatest UI libraries available. The editor, the content/courses/branches tree, the uploader and the autocomplete box are some examples of redesigned widgets.
D. Finally, eFrontPRO comes with out-of-the-box support for delivering static assets (css, js) using a CDN, enhancing client-side performance and lowering network usage for the server.
A. Up until now, internationalization was implemented using PHP’s defines, a strategy that suited the project well in the early days but has revealed its shortcomings as the project grew bigger. eFrontPRO offers a new internationalization framework based on GNU gettext. What does this practically mean? Improved run-time performance, easier translations, ability to use all the tools available for translating in gettext, graceful fallback to english for untranslated literals. It also meant that we were able to ditch unused language tags and group similiar tags together, resulting in ~25% less terms.
B. The implementation of efrontPRO follows a more mature and standards-based MVC approach, taking advantage of PHP namespaces. This allowsfor clean, easily tested and reusable code, while at the same time maintaining a considerably smaller footprint.