Open ns-rse opened 1 year ago
To expand on Neils 'Alternatively' section, its worth pointing out that this is the only .Rmd file in the entire repository. So by removing the embedding on this one page would remove the need to support Rmd at all.
Having the same exact issue with blogdown using both Zotero or just using a bib file
This might be able to be addressed using a Hugo plugin shortcode which has been used to add a recap to the materials which @davidwilby has added. Its for Markdown but there may be an alternative for embedding HTML. See #62 and Hugo | Shortcodes.
The shortcode is, e.g.:
{{% include "/01-getting-started-with-git-and-github/00-typical-workflow.en.md" %}}
added here: https://github.com/RSE-Sheffield/git-github-zero-to-hero/pull/62/files
Had lots of head scratching today as to why a change to
content/setup/gitkraken/_index.en.Rmd
wasn't rendered in the Netlify deploy previews.Eventually figured out that its because this is the source for
content/setup/gitkraken/_index.en.html
and it is the HTML file that is used in building and deployment. The RMarkdown isn't rendered automatically by Hugodown.This is alluded to in the
README.md
which states...To resolve this I attempted to build the
rmarkdown::render()
the.Rmd
in two places.Within
content/setup/gitkraken
Top level of the repository
In both cases the failure is because
/images/gpg_off.png
can not be found. This file resides at/static/images/gpg_off.png
.Changing
_index.en.Rmd
to have the following relative path means thatrmarkdown::render("_index.en.Rmd")
completes successfully and the resulting HTML page has the PNG file embeded within it (i.e. not a link).The
README.md
also mentions the R package hugodown and I played around trying to build withhugodown::build_site()
without success. Not overly familiar withhugodown
though, this is as far as I got...I'm not sure whether this change should be made or not, but I do think the
README.md
would benefit from additional details on this so that others don't get confused should they ever edit this file in the future.Something like...