Mockup stayed a separate project, was accepted for inclusion in the Plone core by the Framework Team in 2013 and is one big part of the upcoming Plone 5.
This documentation should help developers to better understand Mockup, effectively quickstart projects and use Mockup in production.
But wait, despite all of the well sounding hymns to mockup from above, aren’t there more established alternatives?
Well ... yes, there are. Mockup grew up in a world where none of these alternatives were in sight. Now we have at least an upcoming Web Components W3C standards draft with concrete implementations (X-Tags, Polymer) and Angular JS Directives. Both of them could be used instead of Mockup.
And you can, if you want. Since mockup is so encapsulated, you can just switch over and use something else. Or only small parts of Mockup. It’s up to you and your requirements.
I expect Mockup to stay relevant for Plone until Web Components are standardized and stable and ECMAScript 6 is implemented by all Browsers we want to support. That will happen, hopefully, in the near future. Then Mockup could be changed to be a Web Components implementation, which again uses other top notch, well established Frameworks to satisfy the needs of frontend developers.
The Goals of Mockup¶
- Standardize configuration of patterns implemented in js to use HTML data attributes, so they can be developed without running a backend server.
- Use modern AMD approach to declaring dependencies on other js libs.
- Full unit testing of js.
Technologies used with Mockup¶
- Bower (Github, Wikipedia) for package management.
- Yeoman (Github, Wikipedia) for generating pattern scaffolds.
- LESS (Github, Wikipedia) as CSS preprocessor.
- Node JS (Github, Wikipedia) as a requirement for Grunt.
- React JS