Comment by George Spake on "Ask anything to Zurb Foundation"

One of the stated goals of v7 is to be "accessible in every framework." I have high hopes that this will be the case and 6.4 is a big step toward making that possible. In the meantime, though, it can still be tricky to architect a front-end codebase around, say, Foundation and React without two different repos, two different builds, etc... which can get confusing pretty quickly. Given the amount of overlap in tooling, dependencies, and structure, I would love to see a harmonious single project codebase that would allow me to build out Foundation and React (or any other js framework without having go to great lengths to glue them together. Any thoughts on what that might look like or how I should organize projects for use with React?

Hi @gpspake, This is exactly the challenge we're working on with the planned Foundation 7 JavaScript architecture. Without going into too great a detail as it's still early days and may change, our approach is to encapsulate state and "ui logic" in a core component, and then provide simple clean interfaces for implementation in different frameworks.

Essentially the idea is to make the 'glue' piece much thinner, making it much easier to support integrations in every JS Framework, and keeping the internal logic consistent without requiring folks to rebuild it.

Our early proof of concept has implementations both in vanilla JavaScript and React, and we're optimistic we can get the interface well enough defined that building these out for every framework will be quick. Exactly how that ends up playing out into project structure is still TBD. If you (or anyone else reading this) is interested in getting involved in making this a reality, hit me up by email at kball (at) zurb.com

Search Hashnode