It's difficult to review this PR given the formatting issues; we'll need to set up Prettier or something so everyone is on the same page... my advice is to pull it down and format it to the app-wide standards.
A lot of the code here is simply splitting hairs; minor changes needed to connect the dots.
Not much is actually changed here, though:
/data now has two subdirectories: /components and /page
Pretty straight forward, but page data can parse down to each component. This approach is fine, too, because the tree isn't very deep.
The next problem to solve is all of the hardcoded imports for each component. We will need to bundle all of our assets with Webpack somehow, so we can simply specify the path as a key in our data... then the components will simply accept data.
It's difficult to review this PR given the formatting issues; we'll need to set up Prettier or something so everyone is on the same page... my advice is to pull it down and format it to the app-wide standards.
A lot of the code here is simply splitting hairs; minor changes needed to connect the dots.
Not much is actually changed here, though:
/datanow has two subdirectories:/componentsand/pageThe next problem to solve is all of the hardcoded imports for each component. We will need to bundle all of our assets with Webpack somehow, so we can simply specify the path as a key in our data... then the components will simply accept data.