[software training] How to teach two intertwined topics best?

Hi, I'm about to start authoring my fifth course (ebook first, then also videos), which covers how to build plugins for a special host application using React.js

The big deal here is the special host application part – i.e. the new API that has been recently released and nobody's covered yet; while React.js is everywhere, by everybody, countless times. Nevertheless, I' ve estimated that it makes sense for me to cover both topics jointly, in the context of that specific developers niche community. In other words, they'd likely buy it.

At first I've thought about a master/slave approach, but it's hard to treat the API as the main topic (as it would make sense) because you can't really use it/develop plugins without React.js, that is hence hard to treat just as an ancillary subject.

Alternatively, I've thought about splitting the book in three parts, e.g. I. React.js, II. the new API, III. 'em both, but it sounds super dull and awfully boring, for me as a writer and the readers alike.

Or splitting not the book, but each chapter in two – one part the API, one part React. I'm afraid it'd require a lot of work to make a number of separate narratives that make sense when sewed together.

What about a project based thing, e.g. 4-5 different plugins (covering different API aspects) of increasing difficulty built using more and more advanced React.js features? I'm not a super fan or project-based stuff myself, but heck, it may work.

To sum up: I have to write about/teach 2 topics, one of which is exclusive and basically the main reason why my audience will buy my work; the other is a tool that they have to master in order to make any use of the shiny new thing. How to go about this best?

Have you ever found yourself in this situation? What did you do? What worked and what didn't? Thanks!