Scratchpad for text snippets to be included somewhere else in the training.
When providing static resources (JS/Less/CSS) for Plone 5 resource registry, use plone.resource based resources instead of Zope browser resources. The latter are cached heavily and you won’t get your changes built with Zope resources.
This means, each bundle gets all their dependencies compiled in, which raise the response payload unnecessarily.
To avoid this, add your resources to existing bundles, like the
The mockup grunt infrastructure is build with a convention over configuration approach in mind.
Bundles have to be named
mockup-bundles-BUNDLENAME, patterns have to be named
The resources are downloaded to your browser, compiled there and re-upload to the Plone server, where they are stored in ZODB as plone.resource <https://pypi.org/project/plone.resource>`_ resources.
mockup’s Grunt infrastructure.
- About this training
- Training Agenda
- Preparing for the training
History of everything, What’s what.
- Development environment
Short explanation of the code tree / main modules: Mockup Patternslib Plone 5
- Developing a Pattern
- A Barebone Pattern
Based on collective.minimalpattern
Adding a bower.json dependency
Testing the Pattern
- Integrating the Pattern
Integration in Plone 5 Integration in Plone 4 Integration in Mockup w/out Plone
The old, require JS-less way
Using other Frameworks in Plone
Angular JS React JS
Comparison to other frameworks
Patternslib and Web Components Patternslib and React Components Patternslib and Angular JS directives Plone and ES 6