You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if we should redo this as Gutenberg blocks, to make it more future-proof, and as an opportunity to learn more JS.
On the back end, the CPT could be pre-populated with a template of blocks that collect the various info about the company.
On the front end, the table could be a dynamic block or standalone React app rather than native JS. That's kind of overkill in a way, but it would also be more consistent with the back end, and may be able to share some code with the back end, WordCamp blocks, etc? If we do it as a block, maybe it'd be an opportunity to experiment with a way to write dynamic blocks in JavaScript rather than PHP?
Here's a couple recent projects that could provide a good template for building small interactive apps with Gutenberg's abstraction layer for React, and its components:
I'm wondering if we should redo this as Gutenberg blocks, to make it more future-proof, and as an opportunity to learn more JS.
On the back end, the CPT could be pre-populated with a template of blocks that collect the various info about the company.
On the front end, the table could be a dynamic block or standalone React app rather than native JS. That's kind of overkill in a way, but it would also be more consistent with the back end, and may be able to share some code with the back end, WordCamp blocks, etc? If we do it as a block, maybe it'd be an opportunity to experiment with a way to write dynamic blocks in JavaScript rather than PHP?
What do you think, @vedanshujain and @coreymckrill ?
The text was updated successfully, but these errors were encountered: