Raphael Sonabend-Friend

> If I understand correctly, you're after the latter? Yeah, or not really 'every' object but just ones we want to be documented (so if you look at point 1...

> Docs.meta(MyPackage) Thanks for this tip, much neater than in my code above. > name(MyPackage) Assuming you meant `names`, if so this unfortunately doesn't quite work as it includes exported...

Deleted previous comment - pretty messy! Found a solution that doesn't require any additional dependencies, macros, or extra functions. Let me know your thoughts! ```julia using MyPackage documented = map(x...

@sebffischer @be-marc how does this PR fit in with https://github.com/mlr-org/mlr3book/pull/412 ?

I wouldn't stress about this now. We can have Title Page -> Preamble -> Introduction. The quickstart will become the preamble in the printed version and the title page will...

The printed book will definitely need a preamble as well as installation instructions. Once that's made we could then take something shorter for quickstart, but tbh this could end up...

I don't think we should necessarily do this. The tables we currently have already don't provide enough info to be valuable to the user, in your example it would be...

General issue unfortunately. Agreed for online we want it to always be up-to-date but of course this isn't possible for the book. My preference is to pick consistency based on...

Or we could do something similar to the [learner search](https://mlr3extralearners.mlr-org.com/articles/learners/list_learners.html) but for all our dictionaries?

Hi and thanks for your interest in the package, It's quite a lot of work adding new models to this package, especially when they're not already on Python; in fact...