Sorry for the delayed response. I'd forgotten there was a question in there. Yes, we're using our headless CMS to create a model of data that exports it as JSON through an API. We can then parse it to make sure it matches what the framework is expecting. We can create relationships inside the CMS that show which content should be included in which courses. That's the theory, anyway.