<p><div><div><div><div data-show-faces="false" data-height="21" data-width="100" data-layout="button_count" data-send="true" data-href="https://www.r-bloggers.com/r-blogdown-setup-in-github-2/"></div></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="https://talesofr.wordpress.com/2018/02/26/r-blogdown-setup-in-github-2/"> R – Tales of R</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<div>
<ul>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#an-updated-tutorial-to-set-up-a-blogdown-blog" target="_blank">An updated tutorial to set up a <span>blogdown</span> blog   </a>
<ul>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#git-github-repos" target="_blank">Git &amp; GitHub repos</a></li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#rstudio-and-blogdown-setup" target="_blank">RStudio and <span>blogdown</span> setup</a></li>
</ul>
</li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#customising-paths-and-styles" target="_blank">Customising paths and styles</a>
<ul>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#modify-config.toml-file" target="_blank">Modify <span>config.toml</span> file</a></li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#custom-css" target="_blank">Custom css</a></li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#custom-javascript" target="_blank">Custom javascript</a></li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#site-build-with-blogdown" target="_blank">Site build with <span>blogdown</span></a></li>
</ul>
</li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#deploying-the-site" target="_blank">Deploying the site</a>
<ul>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#updating-the-local-git-repository" target="_blank">Updating the local <span>git </span>repository</a></li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#pushing-to-github" target="_blank">Pushing to GitHub</a></li>
</ul>
</li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#add-r-code" target="_blank">Add R code</a></li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#a-new-post-in-blogdown" target="_blank">A new post in <span>blogdown</span></a>
<ul>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#deploying-the-site-with-the-new-post" target="_blank">Deploying the site with the new post</a></li>
</ul>
</li>
<li><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#this-.rmd-source-code" target="_blank">This <span>.Rmd</span> source code</a></li>
</ul>
</div>
<div>
<h1>An updated tutorial to set up a <span>blogdown</span> blog</h1>
<p>You can also check this post, written in <a rel="nofollow" href="https://twitter.com/hashtag/blogdown" target="_blank">#blogdown</a>, here: <a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/" target="_blank">r-blogdown-setup-in-github-2</a>.</p>
<p>This is an updated blog post from the previous version: <a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2017/08/r-blogdown-setup-in-gihub/" target="_blank">R Blogdown Setup in GiHub</a>.</p>
<p>Inspired by this great blog, by Elio Campitelli: <a rel="nofollow" href="https://eliocamp.github.io/codigo-r/" target="_blank">eliocamp.github.io/codigo-r</a> and his settings on the hugo-tranquilpeak theme, by <a rel="nofollow" href="https://github.com/LouisBarranqueiro" target="_blank">Louis Barranqueiro</a> &amp; <a rel="nofollow" href="https://github.com/kakawait" target="_blank">Thibaud Leprêtre</a>.</p>
<p>As the changes I made imply many modifications in paths, directories (some very subtle), they invalidate much of my previous tutorial. The changes I basically made are:</p>
<ul>
<li>I still use Github pages for hosting. However, I changed the rendering folder from <code>master</code> to <code>docs</code>.</li>
<li>Made some other fixes to the <code>config.toml</code> file.</li>
</ul>
<p>The steps I followed are detailed here:</p>
<div>
<h2>Git &amp; GitHub repos</h2>
<ul>
<li> Set up a GitHub account, following for example <a rel="nofollow" href="https://www.wikihow.com/Create-an-Account-on-GitHub" target="_blank">this</a>.</li>
<li> Set up a new <a rel="nofollow" href="https://github.com/" target="_blank">GitHub</a> repo with a name of your choice (in my case <span>talesofr</span>). See <a rel="nofollow" href="https://help.github.com/articles/create-a-repo/" target="_blank">this </a> and <a rel="nofollow" href="https://tclavelle.github.io/blog/blogdown_github/" target="_blank">this</a>.</li>
<li> Activate GitHub pages. For this, you must go to the <span>/settings</span> section of your repo and find the epigraph “GitHub Pages”. In the dropdown menu, select:   <span>master branch /docs folder</span> and save.</li>
</ul>
<div><img alt="Activating GitHub pages" src="https://i1.wp.com/aurora-mareviv.github.io/talesofr/images/tuto/tuto5.2.png?w=456&ssl=1" data-recalc-dims="1">
<p>Activating GitHub pages</p>
</div>
<ul>
<li>Create a <code>git</code> local repo in your machine:
<ul>
<li>Create manually a new directory called like your repository, e.g. <span>talesofr</span>.</li>
<li>Run in the terminal (Windows users have to install <a rel="nofollow" href="https://git-scm.com/downloads" target="_blank"><code>git</code></a> first):</li>
</ul>
<pre><code><span>cd</span> /Git/talesofr <span># your path may be different</span>
git init <span># initiates repo in the directory</span>
git remote add origin <a rel="nofollow" href="https://github.com/%5BUSERNAME%5D/talesofr" target="_blank">https://github.com/[USERNAME]/talesofr</a> <span># connects git local repo to remote Github repo</span>
git pull origin master <span># in case you have LICENSE and Readme.md files in the GitHub repo, they're downloaded to your machine</span></code></pre>
</li>
<li>You can add a <em>.gitignore</em> text file to the root directory of your repo. This tells <code>git</code> what files <em>not to add</em> to the repo, even if they are into the folder. One example of <em>.gitignore</em> file is <a rel="nofollow" href="https://github.com/aurora-mareviv/talesofr/blob/master/.gitignore" target="_blank">this</a>.</li>
<li>For now, your repo is ready. We will now focus in creating &amp; customising our Blogdown.</li>
</ul>
</div>
<div>
<h2>RStudio and <span>blogdown</span> setup</h2>
<ul>
<li>We will open RStudio (my Version is 1.1.419).
<ul>
<li>First, you may need to install Blogdown in R:</li>
</ul>
<pre><code>install.packages(<span>&quot;blogdown&quot;</span>)</code></pre>
<ul>
<li>In RStudio, select the <em>Menu > File > New Project</em> following the lower half of these <a rel="nofollow" href="https://bookdown.org/yihui/blogdown/rstudio-ide.html" target="_blank">instructions</a>. The wizard for setting up a Hugo Blogdown project should be available in your RStudio version.</li>
</ul>
</li>
</ul>
<div><img alt="Creating new Project" src="https://i1.wp.com/aurora-mareviv.github.io/talesofr/images/tuto/tuto1.png?w=456&ssl=1" data-recalc-dims="1">
<p>Creating new Project</p>
</div>
<div><img alt="Selecting Hugo Blogdown format" src="https://i2.wp.com/aurora-mareviv.github.io/talesofr/images/tuto/tuto2.png?w=456&ssl=1" data-recalc-dims="1">
<p>Selecting Hugo Blogdown format</p>
</div>
<div><img alt="Selecting Hugo Blogdown theme" src="https://i0.wp.com/aurora-mareviv.github.io/talesofr/images/tuto/tuto3.2.png?w=456&ssl=1" data-recalc-dims="1">
<p>Selecting Hugo Blogdown theme</p>
</div>
<div><img alt="A config.toml file appears" src="https://i2.wp.com/aurora-mareviv.github.io/talesofr/images/tuto/tuto4a.2.png?w=456&ssl=1" data-recalc-dims="1">
<p>A <strong>config.toml</strong> file appears</p>
</div>
<hr>
</div>
</div>
<div>
<h1>Customising paths and styles</h1>
<p>Before we <span>build</span> and <span>serve</span> our site, we need to tweak a couple of things in advance, if we want to smoothly deploy our blog into GitHub pages.</p>
<div>
<h2>Modify <span>config.toml</span> file</h2>
<p>To integrate with GiHub pages, there are the essential modifications at the top of our <em>config.toml</em> file:</p>
<ul>
<li>We need to set up the base URL to the “root” of the web page (<a rel="nofollow" href="https://%5Busername%5D.github.io/%5BREPO_NAME%5D" target="_blank">https://[USERNAME].github.io/[REPO_NAME]</a> in this case).</li>
<li>By default, the web page is published in the <code>/public</code> folder. We need it to be published in the <code>/docs</code> folder of the repository (we must create it if it doesn’t exist yet), to match the structure of the GitHub <span>docs</span> branch (we’ll see what that means):</li>
</ul>
<pre><code>baseURL = <span>&quot;<a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/" target="_blank">https://aurora-mareviv.github.io/talesofr/</a>&quot;</span>
publishDir = <span>&quot;docs&quot;</span></code></pre>
<ul>
<li>Other useful global settings:</li>
</ul>
<pre><code>draft: false <span># if set to true, changes will not be published</span>
ignoreFiles = [<span>&quot;\\.Rmd$&quot;</span>, <span>&quot;\\.Rmarkdown$&quot;</span>, <span>&quot;_files$&quot;</span>, <span>&quot;_cache$&quot;</span>]
enableEmoji = true
<span>...</span></code></pre>
<div>
<h4>Images &amp; styling paths</h4>
<p>We can revisit the <em>config.toml</em> file to make changes to the default settings.</p>
<p>The file for the logo that appears in the corner must be placed in the <code>/docs/logo.png</code> path. To modify it in the <em>config.toml</em>:</p>
<pre><code>picture = <span>&quot;logo.png&quot;</span> <span># the path to the logo</span></code></pre>
<p>The cover (background) image must be located in <code>/themes/hugo-tranquilpeak-theme/static/images</code>. To modify it in the <em>config.toml</em>:</p>
<pre><code>coverImage = <span>&quot;myimage.jpg&quot;</span></code></pre>
<p>We want some custom css and js. We need to locate them in <code>/static/css/my-style.css</code> and in <code>/static/js/myjs.js</code> respectively.</p>
<pre><code>  <span># Custom CSS. Put here your custom CSS files. They are loaded after the theme CSS;</span>
  <span># they have to be referred from static root. Example</span>
   [[params.customCSS]]
     href = <span>&quot;css/my-style.css&quot;</span>

  <span># Custom JS. Put here your custom JS files. They are loaded after the theme JS;</span>
  <span># they have to be referred from static root. Example</span>
   [[params.customJS]]
     src = <span>&quot;js/myjs.js&quot;</span></code></pre>
</div>
</div>
<div>
<h2>Custom css</h2>
<p>Now, we can add arbitrary classes to our <em>css</em> file! (see above).</p>
<p>Since I started writing in Bootstrap, I love it a lot. Since this theme already has bootstrap classes, I brought some others I didn’t find in the theme (they’re <a rel="nofollow" href="https://github.com/kakawait/hugo-tranquilpeak-theme/blob/master/docs/user.md" target="_blank">available</a> for <em>.md</em> files, but currently not for <em>.Rmd</em>)</p>
<div></div>
<div></div>
<p>Here is an example of a custom <em>css</em> file that can be copied to the file <code>/static/css/my-style.css</code>:</p>
<pre><code>/* @import url(<span>'<a rel="nofollow" href="https://maxcdn.bootstrapcdn.com/bootswatch/3.3.7/cosmo/bootstrap.min.css" target="_blank">https://maxcdn.bootstrapcdn.com/bootswatch/3.3.7/cosmo/bootstrap.min.css</a>'</span>); may conflict with default theme!*/
@import url(<span>'<a rel="nofollow" href="https://fonts.googleapis.com/icon?family=Material+Icons" target="_blank">https://fonts.googleapis.com/icon?family=Material+Icons</a>'</span>); /*google icons*/
@import url(<span>'<a rel="nofollow" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css" target="_blank">https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css</a>'</span>); /*font awesome icons*/

.input-lg {
  font-size: 30px;
}
.input {
  font-size: 20px;
}
.font-sm {
    font-size: 0.7em;
}
.texttt {
  font-family: monospace;
}
.alert {
padding: 15px;
margin-bottom: 20px;
border: 1px solid transparent;
border-radius: 4px;
}
.alert-success {
color: <span>#3c763d;</span>
background-color: <span>#dff0d8;</span>
border-color: <span>#d6e9c6;</span>
}
.alert-danger,
.alert-error {
  color: <span>#b94a48;</span>
  background-color: <span>#f2dede;</span>
  border-color: <span>#eed3d7;</span>
}
.alert-info {
  color: <span>#3a87ad;</span>
  background-color: <span>#d9edf7;</span>
  border-color: <span>#bce8f1;</span>
}
.alert-gray {
  background-color: <span>#f2f3f2;</span>
  border-color: <span>#f2f3f2;</span>
}

/*style <span>for</span> printing*/
@media <span>print</span> {
    .noPrint {
       display:none;
   }
    }

/*link formatting*/
a:link {
    color: <span>#478ca7;</span>
    text-decoration: none;
} 
a:visited {
    color: <span>#478ca7;</span>
    text-decoration: none;
}
a:hover {
    color: <span>#82b5c9;</span>
    text-decoration: none;
}</code></pre>
<p>An example of the <span>alert-danger</span> class:</p>
<pre><code><div><span>class</span>=&quot;<span>well</span> <span>alert</span> <span>alert</span>-<span>danger</span> <span>text</span>-<span>center</span>&quot;>
<span></span> <span>alert</span>-<span>danger</span>
</div></code></pre>
<p>Also, we have <a rel="nofollow" href="http://fontawesome.io/icons/" target="_blank">font-awesome</a> icons!</p>
<div>
<h4>Update! Hugo shortcodes in <em>.Rmd</em> !</h4>
<p>Searching through blogdown/issues in GitHub, I found this good trick by Yihui:<br>
You can add Hugo shortcodes if you wrap them with the function <code>htmltools:HTML</code></p>
<pre><code>htmltools::HTML(<span>&quot;{{&lt; hl-text danger >}}
this is a highlighted danger text
{{&lt; /hl-text >}}&quot;</span>)</code></pre>
</div>
</div>
<div>
<h2>Custom javascript</h2>
<p>We can also add really cool functions to enhance our post! (see the blogdown version of this post)</p>
<div></div>
<p>Here is the code of the button:</p>
<pre><code><div><span>class</span>=&quot;<span>button</span> <span>well</span> <span>alert</span> <span>alert</span>-<span>danger</span> <span>text</span>-<span>center</span>&quot; <span>id</span>=&quot;<span>myButton</span>&quot; <span>onclick</span>=&quot;<span>alertColor</span>()&quot;>
<span> <span></span><span>alert</span>-<span>danger</span> </span>
</div></code></pre>
<p>And <a rel="nofollow" href="https://github.com/aurora-mareviv/aurora-mareviv.github.io/blob/master/static/js/myjs.js" target="_blank">here</a> is the javascript function that you can copy into <code>/static/js/myjs.js</code>:</p>
<pre><code><span>function <span>alertColor</span><span>()</span> </span>{
  var result = <span>&quot;<span></span> alert-info&quot;</span>;
  document.getElementById(<span>&quot;toInfo&quot;</span>).innerHTML = result; 
  document.getElementById(<span>&quot;myButton&quot;</span>).style.backgroundColor = <span>&quot;#d9edf7&quot;</span>;
  document.getElementById(<span>&quot;myButton&quot;</span>).style.color = <span>&quot;#3a87ad&quot;</span>;
  document.getElementById(<span>&quot;myButton&quot;</span>).style.borderColor = <span>&quot;#bce8f1&quot;</span>;
}</code></pre>
</div>
<div>
<div>
<div>
<div></div>
</div>
</div>
</div>
<div>
<h2>Site build with <span>blogdown</span></h2>
<p>Once we have ready our theme, we can add some content, modifying or deleting the various examples we will find in <code>/content/post</code>.</p>
<p>We need to make use of Blogdown &amp; Hugo to compile our <em>.Rmd</em> file and create our <em>html</em> post:</p>
<pre><code>blogdown::build_site()
blogdown::serve_site()</code></pre>
<p>In the viewer, at the right side of the IDE you can examine the resulting <em>html</em> and see if something didn’t go OK.</p>
</div>
</div>
<div>
<h1>Deploying the site</h1>
<div>
<h2>Updating the local <span>git </span>repository</h2>
<p>This can be done with simple git commands:</p>
<pre><code><span>cd</span> /Git/[REPO_NAME] <span># your path to the repo may be different</span>
git add . <span># indexes all files that wil be added to the local repo</span>
git commit -m <span>&quot;Starting my Hugo blog&quot;</span> <span># adds all files to the local repo, with a commit message</span></code></pre>
</div>
<div>
<h2>Pushing to GitHub</h2>
<pre><code>git push origin master <span># we push the changes from the local git repo to the remote repo (GitHub repo)</span></code></pre>
<p>Just go to the page <span><a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr" target="_blank">https://[USERNAME].github.io/[REPO_NAME]</a></span> and enjoy your blog!</p>
<hr>
</div>
</div>
<div>
<h1>Add R code</h1>
<p>Works just the same as in Rmarkdown. R code is compiled into an <em>html</em> and published as static web content in few steps. Welcome to the era of reproducible blogging!</p>
<p>The figure <a rel="nofollow" href="https://aurora-mareviv.github.io/talesofr/2018/02/r-blogdown-setup-in-github-2/#fig:diamond" target="_blank">1</a> uses the <code>ggplot2</code> library:</p>
<pre><code><span>library</span>(ggplot2)
ggplot(diamonds, aes(x=carat, y=price, color=clarity)) + geom_point()</code></pre>
<div><span></span><img alt="diamonds plot with ggplot2." src="https://i0.wp.com/aurora-mareviv.github.io/talesofr/post/2018-02-25-r-rmarkdown2_files/figure-html/diamond-1.png?w=450&ssl=1" data-recalc-dims="1">
<p>Figure 1: diamonds plot with ggplot2.</p>
</div>
<hr>
</div>
<div>
<h1>A new post in <span>blogdown</span></h1>
<p>I know there is a procedure to create a new post using the interface in RStudio (<strong>via the “Addins” button in RStudio IDE</strong>) but this one will also work:</p>
<p>I copied a blank <em>.Rmd</em> file into the folder <code>/content/post</code>. I gave it a different name than the other post, with the date and some explanatory text (I called it “<em>2017-08-22-new-post.Rmd</em>”).</p>
<p>Then, I added an appropriate YAML heading (similar to the one in the previous post, but changing dates and times). Beware, as the YAML header indent-sensitive:</p>
<pre><code>---
title: <span>&quot;New Post in Blogdown&quot;</span>
author: <span>&quot;1&quot;</span>
date: <span>2017</span>-<span>08</span>-22T23:<span>41</span>:<span>14</span>-<span>05</span>:<span>00</span>
draft: false
categories: [<span>&quot;R&quot;</span>]
tags: [<span>&quot;R Markdown&quot;</span>, <span>&quot;blogdown&quot;</span>, <span>&quot;#rstats&quot;</span>]
thumbnailImagePosition: left
thumbnailImage: ./images/logo.png
metaAlignment: center
disable_comments: true
output:
  blogdown::html_page:
    toc: false
    fig_width: <span>8</span>
    css: <span>&quot;/css/my-style.css&quot;</span>
--- </code></pre>
<p>Finally I added some content to the Rmarkdown and saved the changes.</p>
<p>We need to make use of Blogdown &amp; Hugo to compile our <em>.Rmd</em> file and create our <em>html</em> post:</p>
<pre><code>blogdown::build_site()
blogdown::serve_site()</code></pre>
<p>In the viewer, at the right side of the IDE you can examine the resulting <em>html</em> and see if something didn’t go OK.</p>
<div>
<h3>Deploying the site with the new post</h3>
<div>
<h4>Updating the local <span>git </span>repository</h4>
<p>This can be done with simple git commands:</p>
<pre><code><span>cd</span> /Git/[USERNAME].github.io <span># your path to the repo may be different</span>
git add . <span># indexes all files that wil be added to the local repo</span>
git commit -m <span>&quot;Adding a new post&quot;</span> <span># adds all files to the local repo, with a commit message</span></code></pre>
</div>
<div>
<h4>Pushing to GitHub</h4>
<pre><code>git push origin master <span># we push the changes from the local git repo to the remote repo (GitHub repo)</span></code></pre>
<p>You can rinse and repeat this procedure for the rest of the posts.</p>
<hr>
</div>
</div>
</div>
<div>
<h1>This <span>.Rmd</span> source code</h1>
<p>You can download it from <a rel="nofollow" href="https://github.com/aurora-mareviv/talesofr/blob/master/content/post/2018-02-25-r-rmarkdown2.Rmd" target="_blank">here</a></p>
<p> </p>
</div>
<div>
<div><img src="https://i1.wp.com/aurora-mareviv.github.io/talesofr/images/hexbins2.png?w=456&ssl=1" data-recalc-dims="1"></div>
</div>
	<p>
<div>
<div>To <strong>leave a comment</strong> for the author, please follow the link and comment on their blog: <strong><a href="https://talesofr.wordpress.com/2018/02/26/r-blogdown-setup-in-github-2/"> R – Tales of R</a></strong>.</div>
<hr>
<a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers.com</a> offers <strong><a rel="nofollow" href="https://feedburner.google.com/fb/a/mailverify?uri=RBloggers">daily e-mail updates</a></strong> about <a rel="nofollow" href="https://www.r-project.org/" title="The R Project for Statistical Computing">R</a> news and <a rel="nofollow" href="https://www.r-bloggers.com/search/tutorial" title="R tutorials">tutorials</a> on topics such as: <a rel="nofollow" href="https://www.r-bloggers.com/search/data%20science" title="Data science">Data science</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Big%20Data" title="Big Data">Big Data, <a rel="nofollow" href="https://www.r-users.com/" title="R jobs">R jobs</a>, visualization (<a rel="nofollow" href="https://www.r-bloggers.com/search/ggplot2" title="ggplot and ggplot2 tutorials">ggplot2</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/boxplot" title="Boxplots using lattice and ggplot2 tutorials">Boxplots</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/map" title="Maps and gis">maps</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/animation" title="Animation in R">animation</a>), programming (<a rel="nofollow" href="https://www.r-bloggers.com/search/RStudio" title="RStudio IDE for R">RStudio</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/sweave" title="Sweave and literate programming">Sweave</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/LaTeX" title="LaTeX in R">LaTeX</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/SQL" title="SQL and databases">SQL</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/eclipse" title="Eclipse IDE for R">Eclipse</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/git" title="git and github, Version Control System">git</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/hadoop" title="Large data in R using Hadoop">hadoop</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/Web+Scraping" title="Web Scraping of google, facebook, yahoo, twitter and more using R">Web Scraping</a>) statistics (<a rel="nofollow" href="https://www.r-bloggers.com/search/regression" title="Regressions and ANOVA analysis tutorials">regression</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/PCA" title="principal component analysis tutorial">PCA</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/time+series" title="Time series">time series</a>, <a rel="nofollow" href="https://www.r-bloggers.com/search/trading" title="finance trading">trading</a>) and more...
<img width="1" alt="" src="http://feeds.feedburner.com/~r/RBloggers/~4/HAzxdC109mE" height="1"></a></div>