Templates Overrides. should they stay or should they go ♪♫

[sauzher]

To collect suggestion on which override we must keep (and make it works in plone 51/52) or rewrite relying on plone 52 templates or just take the default new ones.

• collective.contentleadimage.browser.folder_leadimage_view.pt
  superseeded by the standard plone5 behavior but may be we have to port some customization there

• plone.app.event.browser.event_view.pt

• plone.app.event.portlets.portlet_calendar.pt

• plone.app.layout.viewlets.document_byline.pt
  as discussed today... may be the standard plone51/52 is already WCAG 2.0/2.1 AA compliant

• plone.app.layout.viewlets.logo-orig.pt

• plone.app.layout.viewlets.path_bar-orig.pt

• plone.app.layout.viewlets.path_bar.pt
  (there are two files to give posterity - us today - some insight about what has been customized?)

• plone.app.layout.viewlets.personal_bar.pt

• plone.app.layout.viewlets.searchbox-orig.pt

• plone.app.layout.viewlets.skip_links.pt

• plone.batching.batchnavigation.pt

• plone.outputfilters.browser.captioned_image.pt

• plone.portlet.collection.collection.pt

• Products.CMFPlone.browser.syndication.templates.RSS.pt

• Products.TinyMCE.skins.tinymce.plugins.plonebrowser.editor_plugin.js

• Products.TinyMCE.skins.tinymce.plugins.plonebrowser.js.plonebrowser.js

• Products.TinyMCE.skins.tinymce.plugins.plonebrowser.plonebrowser.htm.pt
  TinyMCE now is in the core. It now uses mockup patterns to browse plone items and these customizations are very likely to be broken in plone52.