You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.1 Links to other pages in website: These currently render as qmd links, e.g. link to Support systems and processes at bottom of this page: https://recognition.ukrn-openresearch.ac.uk/guide-09-planning.html. IN PDF this is rendered as file:///C:/Users/bm907633/Downloads/guide-06-support.qmd. These links should render as html links, i.e. https://recognition.ukrn-openresearch.ac.uk/guide-06-support.html. This means that where pages are included in the PDF the links will go not to the relevant part of the PDF but to the web page. I think this is the best solution if you can apply a rule that will implement it
1.5 Page numbers: Page numbers should appear on all pages after title page. only seem to appear on the first page of a GitHub page, I think because of the copyright and licensing text in the footers.
1.6 Header font: Check all headers are in Roboto font. Level 1, 2 and 3 headers do not appear to be Roboto
1.7 Link to PDF: To display above left-hand side navigation bar. Use pink PDF graphic.
3.5 Page numbers: To display on all pages after p. 1
Presentation
4.1 Icons for page PDF downloads in guide and case studies: Where there are page PDFs there is a larger pink icon at top to the right of the title, then under Other Links ‘This page as PDF’. See e.g. https://recognition.ukrn-openresearch.ac.uk/guide-02-leadership.html. My feeling is that we should avoid displaying links for the same thing in 2 separate styles on one page, so we could remove the Other Links link.
4.2 PDF icon colour: Pink or would aqua fit better? Can’t decide. Perhaps see what aqua looks like.
Collated implementation guide PDF
Individual guide page PDFs
Case study PDFs
Presentation