Skip to content

Conversation

@topepo
Copy link
Member

@topepo topepo commented Nov 14, 2025

Looking for suggestions on reordering/restructuring.

Spark is aspirational right now (there are some eval: false options currently).

The TODO list:

  • multielvel example data sets
  • get automl working (maybe worth removing right now)
  • expand survival prediction tibbles
  • expand quantile prediction tibbles
  • keras3 updates / new engine?
  • use <details> for long model prints (<cough> C5 <cough>)
  • avoid subsection titles capitalizing the engine name (e.g., "CATBOOST") and text within backticks

@EmilHvitfeldt
Copy link
Member

Is this in relation to tidymodels/parsnip#1293?

Copy link
Member

@EmilHvitfeldt EmilHvitfeldt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this document is so long!!!

Copy link
Member

@hfrick hfrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the hierarchy of mode > model type > engine that you've used. I would combine Emil's suggestion of allowing the TOC to go one level deeper with putting the mode in h2, the model type in h3 (both visible in the TOC), and reusing the element from the parsnip article of hiding everything related to one engine underneath the <details> tag. That should make it easy to navigate to the relevant example quickly and a bit more obviously than via the TOC on the right-hand side.

@topepo topepo marked this pull request as ready for review November 18, 2025 13:49
@topepo
Copy link
Member Author

topepo commented Nov 21, 2025

@hfrick I think that my changes are all done; please re-review when you get a chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants