@datajoely Often I find that books of this sort exist to (1) acquaint the reader with the tool and (2) learn how to integrate it with other topics. The documentation is excellent and continues to improve, so the focus of such a book would not be to simply reproduce the docs. Rather a book that covers the design philosophy of the tool itself, and pipeline design patterns that are consistent with the tool. Recommended practices for using Kedro, and practices that 'could' be done but are not a good idea. Considerations of how to adopt and integrate the tool into an organization. Maybe digging into some special topics (e.g. Bayesian workflow, causal workflow, geoprocessing, containerization/Docker, etc) of how to use Kedro. Overall, to integrate different topics around the topic of Kedro. Anyway, I have not thought about it a lot but that's just what came to mind just now.