-
Notifications
You must be signed in to change notification settings - Fork 7
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
add figure to title page? #73
Comments
@iantaylor-NOAA thanks for the suggestion. Once hake is over I will look. I think that it won't be too hard to add to the template, users would just need to save the figure a certain name and then I will look if a figure is available and bring it in. |
That solution sounds perfect. Thank you. |
@iantaylor-NOAA thanks for the suggestion. You can now include a figure on the title page as long as you include it as figure_title.png in your directory that stores all of the .Rmd files. Part of #73 ... still need to add instructions on the readme or somewhere else regarding how to do this because the functionality is quite hidden.
@iantaylor-NOAA feel free to reopen this issue if the instructions on the README do not work for you. You won't have to change any of your .Rmd files. Just reinstall {sa4ss}, change the saved name of your figure and place it in the proper directory, and compile via |
Worked perfectly, thank you @kellijohnson-NOAA! |
Two low priority additions to this issue:
|
Problem
Before {sa4ss} PFMC assessment reports typically had an image of the species being assessed on the title page which looked nice and also helped when quickly switching among multiple reports.
I added a figure using the following approach:
https://github.com/pfmc-assessments/petrale/blob/main/documents/00title.Rmd
but that caused the figure to also appear in the citation and in between the ToC and the Exec Summary (see screenshot of first two pages below).
Proposal
Develop a method to add a figure to the title page (or document an existing approach).
This is obviously a low priority.
The text was updated successfully, but these errors were encountered: