It all started with the 2014 Zidandca Sprint.
It was the first time I met Ramon Navarro Bosch. Side note: since then, I’ve done a lot of open source work with Ramon. I even joined one of his startups.
The mockup project
- Backbone js
- LESS CSS
(ReactJS was just getting started and we had a few things written in it as well)
What we were asked to solve:
- integrate mockup within plone
- add/remove js/css resources
- customize resources through the web
- build js/css files through the web
From those constraints and the current state of things, we came up with the Plone Resource registry.
Basically, what is does is:
- allow registering “resources” and “bundles”
- a bundle is a build which combines files and uses RequireJS to resolve resource dependencies
- also supports compiling LESS CSS
- support building resources on the command line from configured customizations/registrations
Well, it didn’t work out well. For the most part, the implementation isn’t perfect and either people didn’t like it or didn’t understand it. Ramon and I spent a insane amounts of time working out the issues, documenting and training people on it.
Summary of the problems:
- RequireJS, LESSC, Backbone: now plone is stuck for a while on it
- Buggy and difficult to understand when problems occurred
- Difficult to change development paradigms when people are used to traditional frontend development
One good thing about it is that it encouraged the community into learning and exploring different approaches to integrating frontend development with Plone.