I have a very large production e-commerce project running on v5 and am looking at v6 to see if it is worth upgrading. From playing with a few of the Plugins such as top-bar, sticky, tabs, forms, abide and others, there seems to be a number of changes in class names and data attributes that will require a significant amount of code changes to my v5 project which is using this syntax both in the php code templates but also as part of the dynamic user content which is contained in many database tables and columns.
Is there documentation somewhere of the known syntax changes, ideally on a plugin by plugin basis, so I can scope how much of an effort this is going to be? A list of plugins no longer used (such as Alert) and what it is replaced with (think Callout)?
Is there a graceful way to upgrade without rewriting the v5 code? Some type of backwards compatibility? If not what about future versions of Foundation? It can be very expensive to rewrite applications to support an upgrade, especially 3rd-party code (like a custom e-commerce module that uses Foundation 5 plug-ins) subcontracted out, where we do not want to incur the risk and expense of tampering with it.
I like the functionality of what I've seen in v6 but am finding I can't get some of the Plugins to work as expected (Sticky, Abide, Tabs linking for starters) and have not been able to get support so far for the issues I am running into. Ideally there would be backwards compatibility (at least for a reasonable period of time) to allow an upgrade without the risk and cost it will require for large projects.