Sprint to update add-ons to work with P5?

[tkimnguyen]

Continuing the discussion from What ist the best/default implementation for static complex HTML in the content body area:

@hvelarde

@tkimnguyen

Maybe we should organize a sprint for P5 add-on upgrades...

I think that's a fantastic idea; I'm in...

We started this process in Bucharest.

What would be your top add-ons that need to get updated to work with P5?

Does it make sense to try to organize a sprint to push this forward?

[hvelarde]

in our case, at least the following:

• collective.cover
• collective.lazysizes
• collective.nitf
• collective.polls
• sc.contentrules.groupbydate
• sc.contentrules.layout
• sc.contentrules.metadata
• sc.embedder
• sc.photogallery
• sc.social.like

all of them used in projects of the Brazilian government.

[1letter (Jan)]

We often use:

• webcouturier.dropdown
• collective.cover
• collective.plonetruegallery

but i think plone.app.mosaic is the better choice than collective.cover. I have forked webcouturier.dropdownmenu and work on a P5 Version. But i'm not that experienced with the test-machinery, so it takes a time.

What we need is Link to extern/intern Pages in the Leadimage Behavior of plone.app.contenttypes, but this is probably not the right Topic here.

[gil (Gildardo Bautista)]

In a University site we use:

• Products.FacultyStaffDirectory
• eea.facetednavigation
• quintagroup.dropdownmenu

Products.CMFBibliographyAT is another add-on very useful for Universities. I'm not sure if this is working in Plone 5.

[tkimnguyen]

@vangheem and I have been working on FSD to make it work with P5, but we are taking a very minimalist approach (and as part of that, we have a version of archetypes.referencebrowserwidget working with P5 as well). Will take a bit more testing. https://github.com/plone/archetypes.referencebrowserwidget includes the latest fixes already.