Sprint Topics for 2018

PLIP: Use Web Components instead of Patterns for Mockup #2253

This PLIP is not accepted and controversially discussed. Goal is to investigate the possibilities to use React and/or Web Components as a replacement for Patternslib and Mockup. Targets Plone 6. See:

• https://github.com/plone/plone-react/issues/59
• https://github.com/plone/Products.CMFPlone/issues/2253

PLIP: Resource registry improvements #1955

This PLIP is not accepted and should be re-evaluated in regard to new Tools based around Webpack and SASS. Targets Plone 6. See:

• https://github.com/plone/Products.CMFPlone/issues/1955
• Many discussions and other issues in CMFPlone

PLIP: New datetime and date widgets #2150

Targets Plone 5.2 Missing: a time picker widget.

• https://github.com/plone/Products.CMFPlone/issues/2150
• https://github.com/Patternslib/Patterns/pull/520
• https://github.com/plone/plone.app.widgets/pull/174
• https://github.com/plone/plone.app.z3cform/pull/73
• https://github.com/plone/mockup/pull/807

Other Possible Mockup/Resource Registry Topics

Targets Plone 5.2

• Mockup tooltips confusion: https://github.com/plone/Products.CMFPlone/issues/1766
• LESS compiler and relative URLs: https://github.com/plone/Products.CMFPlone/issues/1732
• resourceregistry: "develop" mode loads less files, even if "Develop CSS" isn't active https://github.com/plone/Products.CMFPlone/issues/1505
• resourceregistry: https proxying and js errors https://github.com/plone/Products.CMFPlone/issues/1433
• resourceregistry: canceling build process results in broken JS https://github.com/plone/Products.CMFPlone/issues/1432

PLIP: Restructure CMFPlone static resources #1653

Johannes Raggam takes this one... Targets Plone 5.2

https://github.com/plone/Products.CMFPlone/issues/1653

Regarding Webpack integration see:

• https://github.com/collective/collective.lazysizes/pull/53
• https://github.com/simplesconsultoria/sc.recipe.staticresources