This is a first step towards having the UI of ARDAC being driven from Strapi CMS.
It depends on a working/populated Strapi backend, which isn't available yet, so a local install / DB ingest is needed -- for testing/reviewing this, it'd be best to work in an interactive peer session. There's also a lot of structural things that are up in the air, and probably some loose ends in terms of the overall code status.
One specific thing to check is that the package.json isn't pulling in unused modules at this point.
This is a first step towards having the UI of ARDAC being driven from Strapi CMS.
It depends on a working/populated Strapi backend, which isn't available yet, so a local install / DB ingest is needed -- for testing/reviewing this, it'd be best to work in an interactive peer session. There's also a lot of structural things that are up in the air, and probably some loose ends in terms of the overall code status.
One specific thing to check is that the
package.jsonisn't pulling in unused modules at this point.