blogdown

Mara Averick (@dataandme; 56/11): For anyone who hasn’t 👀, the blogdown demo site is a must-visit!
👏 @xieyihui , @apreshill @ProQuesAsker
“A minimal example website using blogdown”
https://t.co/vOpBKNIDfU #rstats #blogdown https://t.co/v8G77elKdc ↪

Alison Hill (@apreshill; 22/4): OK y’all, file paths for data files in #blogdown, https://t.co/65j6866w1g h/t @dataandme and @mmmpork #rstats https://t.co/uZF4n7HghI ↪

Keith Lyons (@520507; 4/1): #cssia18 learning portfolio: Blogdown example https://t.co/P4B3fUW7dK ht @dataandme ↪

Mara Averick (@dataandme; 4/0): @xieyihui @mmmpork @apreshill @kierisi It’s so easy to get sucked down a (fun) rabbit hole though… The blogdown code is incredibly readable, so 🙏 thank you thank you for that! ↪

Yihui Xie (@xieyihui; 3/1): @mmmpork @apreshill @kierisi @dataandme That is totally fine to me. As I said in the blogdown book, there are very legitimate reasons to use rmarkdown::render_site(): https://t.co/MAHaTLyuh9 You don’t have to wrestle with Hugo. Use whatever works for you. ↪

Amber Thomas (@ProQuesAsker; 1/0): Ah this is so great!

I’ve often wondered if it’s more efficient to have a separate GitHub repo per project and have my blogdown site pull in the CSV from that repo (as opposed to keeping the CSVs from lots of different projects all on my site itself). Love seeing these options! https://t.co/543zPSxXwr ↪

Andrew MacDonald (@polesasunder; 0/1): #blogdown question : I’m updating my github repo, and netlify is deploying, but the website won’t show any new posts! has that ever happened to you? #rstats ↪

Miguel Bento (@theporra; 0/0): @londonaesthetik Congrats, and great post. My domain is setup, just working on the blogdown structure and have started writing my first post (also an origin story 😊) ↪

bookdown

Yihui Xie (@xieyihui; 3/1): @mmmpork @apreshill @kierisi @dataandme That is totally fine to me. As I said in the blogdown book, there are very legitimate reasons to use rmarkdown::render_site(): https://t.co/MAHaTLyuh9 You don’t have to wrestle with Hugo. Use whatever works for you. ↪

knitr

Colin Fay (@_ColinFay; 10/4): Ok so I might have found a way to insert neo4J results inside an RMarkdown.
#RStats #Neo4J #knitr https://t.co/sLoL2ORqAy ↪

Jesse Maegan (@kierisi; 9/0): not only did @_omahdi find a small bug in knitr, he opened a GH issue, filed a PR, and learned about reprex()! in his words, “this awesome community and the February challenge encouraged me to share my findings and turn them into a little contribution instead” 🙌🙌🙌 ↪

Colin Fay (@_ColinFay; 1/0): @Chucheria Yep, knitr engines are amazingly customizable (knitr never ceases to amaze me), and you can mimic almost any command line tool, so cypher is doable :) ↪

Colin Fay (@_ColinFay; 0/0): @Chucheria This engine is simply wrapping up the chunk code inside a system call to cypher, with the cypher-shell bin path, user name and password given as knitr options.
I’ll 📦 this up in a few 🙃 ↪

職業、イケメン。Nagi Teramo (@teramonagi; 0/0): rmadkwodnとknitrの違いがわかってない… ↪

xaringan

Alison Hill (@apreshill; 2/0): Sad to miss this- but if I know @old_man_chester some #xaringan slides will surely surface shortly after 🤓 https://t.co/wFp9wQ7QGp ↪

Sylvain Lapoix (@SylvainLapoix; 1/0): @badnetworker You know you can do all that with #Rstats + #ggplot2 + #xaringan right ? #Rtrolling https://t.co/vWAyhzoz4k ↪

Metamathan (@metamathan; 0/0): The TAMU Theme for xaringan https://t.co/WDCkMxfzgx #statistics ↪

yihui.name

Ben Marwick (@benmarwick; 2/0): @jgendrinal @AlexaLFH @rstatsbot1234 This recent pkg by @xieyihui might help with updating your latex: https://t.co/HCzSvII867 ↪

Nicolas Roelandt (@RoelandtN42; 1/0): @emilyhmarkowitz @rstatsbot1234 It is a tiny install of LaTeX. Everything you do with LaTeX, you can do with Tiny text. Using latexmk , it’ll download the necessary packages to compile your document. Check @xieyihui ’s blog for more information. 😊

https://t.co/FNdLwe0LMS ↪

L. Collado-Torres (@fellgernon; 0/0): @lorenzwalthert Looks like you might appreciate this blog post https://t.co/FsVM1skwd7 where I did the opposite: one PR for multiple things 😔 ↪