Closed adamkucharski closed 4 hours ago
Name | Link |
---|---|
Latest commit | 59f7499a800c57653558455044d6c7b408f48362 |
Latest deploy log | https://app.netlify.com/sites/tourmaline-marshmallow-241b40/deploys/668c3bfb6c1cd4000802190e |
Deploy Preview | https://deploy-preview-295--tourmaline-marshmallow-241b40.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
I did try with package logos, but it meant there's quite a lot of visual elements for user to process (and wouldn't work well on mobile). Instead, thought the library
call hints at these being R packages in a broad way (as reckoned unlikely that a visitor, at least one who works on analysis, would assume that the basic library()
call could do all that plotting).
Although could definitely use some refinement. Perhaps something like below, that introduces package with text?
(Maybe with a tweak to make the normal font text a slightly different shade)
I did try with package logos, but it meant there's quite a lot of visual elements for user to process (and wouldn't work well on mobile). Instead, thought the
library
call hints at these being R packages in a broad way (as reckoned unlikely that a visitor, at least one who works on analysis, would assume that the basiclibrary()
call could do all that plotting).Although could definitely use some refinement. Perhaps something like below, that introduces package with text?
(Maybe with a tweak to make the normal font text a slightly different shade)
I love the new one you're suggesting 🤩 .
My only suggestion would be to highlight the package name and one or two keywords in two different colors. For example, the keyword for epichains could be "transmission chains".
Thanks! I've pushed a new version with different colour for package name – I tried highlighting key words, but struggled to make it consistent. I also added some other packages, as thought nice opportunity to showcase. Preview here:
Will merge on Monday if no major edits – can always refine/iterate further in future versions! One later addition we should consider is mentioning integration with existing packages (e.g. socialmixr, EpiNow2, EpiEstim, incidence2 etc.)
Thanks all. I've updated the alt-text and merged – I didn't edit dimensions as looked like width was aligned with a wider template, so didn't want to inadventenly introduce instabilities.
This is a straight swap of the
render1717079674378.gif
file to display some applied visual examples of Epiverse tools, which will address issue #292. Will also hopefully be more mobile friendly.This is V1, so can be further iterated in future when we have additional examples/packages ready and feedback on most commonly used features.