If you don't know that technology, learn it and build a few things with that technology.
If you already know the technology, then you're in good hands.
When you initially learn a new technology, it's not really possible to know what are the must to knows, nice to knows, and no needs to know. In fact, if you were to create a course, without really spending time thinking about this, you will end up creating a course that looks like this:
Once you've created all these modules where you're teaching all these concepts, you will then think what assignments should I add next? That's wrong thinking. You should never do this.
Instead, take time to reflect back and really determine which concepts in the documentations are must to knows, nice to knows, and no need to knows. For any key projects/assignments you've built using technology, whatever you repeatedly used are most likely in the 'must to know' sections. Things that you found helpful but which you did not use for several projects/assignments you've built, just ignore for now. You can add 'nice to knows' later but for now, focus relentlessly only on the must to know concepts.
With now a lens of being able to tell which are must to knows, nice to knows, and no need to knows, you will see that the concepts you need to teach are more looking like this:
Note the grey circled ones are the "nice to knows". The red ones are the "no need to knows". Based on my experience, typically 80-90% of all concepts presented in any technology documentation belong to the nice to knows and no need to knows. This one practice alone will make your curriculum 3-10 times more effective than other courses, where the author failed to distinguish between these three buckets.