-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix pkgdown configuration for reference #499
Comments
@Robinlovelace Friendly reminder 😸 |
Thanks for the reminder. PRs welcome, away at a conference this week but will aim to get on it this week unless someone else gets there first. Definitely is a need to update the docs tho... |
👋 @Robinlovelace I've had a look and an efficient fix of the configuration requires knowledge about the package since your current reference configuration has grouping (which is awesome for users!)
I guess some of the pkgdown docs https://pkgdown.r-lib.org/reference/build_reference.html#topic-matching |
@Robinlovelace friendly reminder 😸 (some topic expertise is needed, I can't do a quick PR) |
Thanks for the nudge @maelle, it is on the todo list, just a busy period. Will get on it soon for new release but cannot guarantee it will happen by end of year. |
Ok, thank you, I won't bug you again until next year then. A suboptimal but doable workaround would be to delete all the reference grouping from the pkgdown configuration for now (so the website can get updated), and then re-adding it when you have time to include all topics. Good luck with your current projects! |
* Add family types to data * Add missing seealso bits, close #499
thank you!! |
Some topics are missing from the configuration file.
Note that for topics you do not want to include in the index you can create an "internal" section https://pkgdown.r-lib.org/reference/build_reference.html?q=internal#missing-topics
To check all topics are listed, after editing the configuration file you can run
pkgdown::check_pkgdown()
.The text was updated successfully, but these errors were encountered: