blogdown
Yihui Xie (@xieyihui; 13/1): @imtaraas @dataandme @BecomingDataSci @kierisi Why not blogdown? Someday you will be able to build blogdown posts to books: https://t.co/uhPepU5nfG Most web platforms are not good for technical writing (Medium, WordPress, …). ↪
Jesse Maegan (@kierisi; 7/2): @xieyihui @BecomingDataSci @imtaraas @dataandme for those curious: https://t.co/fS4RSMLziF ↪
Yihui Xie (@xieyihui; 7/0): @BecomingDataSci @imtaraas @dataandme @kierisi If you are serious about writing technical content, you should definitely consider blogdown or bookdown. Syntax highlighting is a relatively minor feature. More important ones are: code chunks (reproducibility), figures, tables, captions, cross-references, math, citations, … ↪
Jesse Maegan (@kierisi; 6/0): @xieyihui @imtaraas @dataandme @BecomingDataSci I’m actually working through your blogdown guide right now! It’s fantastic and a million times easier than I expected it to be. ↪
aishida (@aishida; 5/2): Rとblogdownでかんたんにgithub.io上にブログを使ってみよう！！ on @Qiita https://t.co/wXOLPFYwHh ↪
Miles McBain (@MilesMcBain; 1/0): @hrbrmstr @dataandme @imtaraas @BecomingDataSci @kierisi I tried blogdown but I got sick of maint issues. Tech stack is too deep for ocassional user. ↪
Taraas (@imtaraas; 1/0): @xieyihui @BecomingDataSci @dataandme @kierisi I did try blogdown and had it working at https://t.co/4QNotjWby2, but got trapped in the “looks” part, just what you warned against. Visual appearance is important to me and I got tired of fine tuning all the little aspects and learning html, css and js (definitely not my goal) ↪
TheWireMonkey (@WireMonkey; 1/0): Working on a blogdown.netlify site covering cleaning and exploring the MetObjects @metmuseum data in #Tidyverse. In the meantime, enjoy a wordcloud from the “medium” variable from the department of Drawings and Prints:
#rstats #wordcloud #DataScience https://t.co/HFgbaWDkfC ↪
bookdown
Yihui Xie (@xieyihui; 13/1): @imtaraas @dataandme @BecomingDataSci @kierisi Why not blogdown? Someday you will be able to build blogdown posts to books: https://t.co/uhPepU5nfG Most web platforms are not good for technical writing (Medium, WordPress, …). ↪
Jesse Maegan (@kierisi; 7/2): @xieyihui @BecomingDataSci @imtaraas @dataandme for those curious: https://t.co/fS4RSMLziF ↪
Yihui Xie (@xieyihui; 7/0): @BecomingDataSci @imtaraas @dataandme @kierisi If you are serious about writing technical content, you should definitely consider blogdown or bookdown. Syntax highlighting is a relatively minor feature. More important ones are: code chunks (reproducibility), figures, tables, captions, cross-references, math, citations, … ↪
Ben Marwick (@benmarwick; 1/0): @kjhealy Underscores in code chunk labels are not recommended because they prevent cross-referencing figures or tables generated from a code chunk: https://t.co/tNuwZgHqSK & https://t.co/5GeekbKdcB ↪
knitr
Kieran Healy (@kjhealy; 26/1): Showing the literal content of plain-text R code chunks—including the code chunk delimiters—using only plain-text markup is a pain, but pandoc and knitr are up to the task. https://t.co/HCeyVNWopy ↪
Hiroaki Yutani (@yutannihilation; 1/0): knitrがバージョン1.18に。見逃してた。 https://t.co/9QG40hMQy0 ↪
Mark Andrews (@xmjandrews; 0/0): @Heinonmatti @rstudio I believe the issue is related to how knitr works, as opposed to RMarkdown or RStudio per se. So maybe @xieyihui will have a better idea of the future of Python in RMarkdown. ↪
முஹம்மத் ஷிம்ரான் (@ThamizhPaiyan; 0/0): How Do I Output Regression Result Tables to Word from Knitr / R RStudio? (mtable, memisc) https://t.co/l2nPjo6dpS https://t.co/wvb1vfNCqs ↪
முஹம்மத் ஷிம்ரான் (@ThamizhPaiyan; 0/0): Show both ‘active’ and ‘inactive’ plots in knitr html output https://t.co/8XnwUSz06Y https://t.co/wvb1vfNCqs ↪
Fake StackOverflow (@horse_overflow; 0/0): How to automatically escape characters (’_’,’' etc) using knitr ↪
yihui.name
matti heino (@Heinonmatti; 1/0): R commandments: use library() to load packages, not require(). Because reasons. https://t.co/lUJyWvz738 ↪