Markdown To Website


7.13 Sharing HTML output on the web

One appealing aspect of rendering R Markdown to HTML files is that it is very easy to host these files on the Internet and share them just as one shares any other website. This section briefly summarizes numerous options for sharing the HTML documents that you have created.

7.13.1 R-specific services

RStudio offers a number of services for publishing various types of content created in R Markdown to the Internet. These services make it particularly easy to publish content by using the RStudio IDE or the rsconnect package (Allaire 2019).

  • RPubs enables free hosting of static single-file R Markdown content. It is easy to publish via the Publish button in the RStudio IDE or the rsconnect::rpubsUpload() function. Please see the “Getting Started” page ( for more details.

  • allows for hosting dynamic content that requires a server to run R. For example, one can host interactive R Markdown documents that include Shiny components.12 is an analog to RPubs for Shiny applications. Apps and interactive R Markdown documents can be published using the push-button in the RStudio IDE or the rsconnect::deployApp() function. See the user guide ( for more details.

  • offers free hosting specifically for books written with the bookdown package. You may easily publish static output files of your book using the bookdown::publish_book() function.

  • RStudio Connect is an enterprise product that organizations may run on their own servers. It can host a wide variety of content created in R (such as R Markdown documents, Shiny apps, and APIs) in a secured environment with document-level access controls, viewership history, and more. Content can be published to RStudio Connect using manual upload, the rsconnect package, or with GIT-based deployment.

7.13.2 Static website services

Markdown Editor is Markdown text editor online which helps user to test and view Markdown online. Website to IP Address. Using Markdown formatting, websites, documents, images and videos can be inserted into almost any location. Common examples include content blocks and hint text on fields. In the words of its creator (John Gruber), 'The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked. Convert Markdown to HTML Paste or type your markdown and see it rendered as HTML. Download or copy the resulting HTML.

In a few words, a simple static website is composed of any number of HTML files (typically containing an index.html, which is the homepage), JavaScript, CSS files, and additional content such as images. This collection of files can be hosted as-is on a web server and rendered in a web browser.

When R Markdown is rendered to the HTML output format, the result may be treated as a static website. Websites can range in complexity from a single, standalone HTML file (which is what we get when we use the default self_contained: true option), a set of files, or a sophisticated project like a website based on blogdown (which relies upon a static website generator). For more details, see Section 2.1 on Static Sites of the blogdown book (Xie, Hill, and Thomas 2017).

As a result, in addition to R-specific services, you may host your HTML document on many freely available static website hosting services. Commonly used options in the R community are:

Markdown table to html
  • GitHub Pages makes it particularly easy to publish Markdown and HTML content straight from a GitHub repository. You may specify whether to host content from either the main branch’s root, a docs/ directory on the main branch, or a specific gh-pages branch. Publishing new content can be as simple as pushing new HTML files to your repository via GIT.

  • GitLab Pages offers similar functionality to GitHub Pages for GitLab repositories. GitLab deploys content stores in the public/ directory of a repository. To build and publish content, you must provide a YAML file, .gitlab-ci.yml with instructions, but GitLab provides many helpful templates. For an example of hosting rendered HTML content, please see

  • Netlify is a platform to build and deploy static website content. It is a popular choice for web content created by the blogdown and pkgdown packages, but it can host all kinds of HTML files. There are many different publishing options including drag-and-drop, command line, or automated publishing from GitHub and GitLab repositories. Additionally, Netlify offers many helpful features such as website previews in pull requests. See the Netlify documentation ( or the RStudio webinar “Sharing on Short Notice” for more details.

This tutorial provides an introduction to creating websites using R, R Markdown and GitHub pages.

Updates were made on November 6, 2020 to simplify the personal website example as some extraneous pieces of information there were giving people problems. See new example website for my cats, John and Pete!

The current version was updated and presented at the R Ladies NYC Meetup on February 15, 2018.

This tutorial was originally presented at the Memorial Sloan Kettering Cancer Center Department of Epidemiology and Biostatistics R User Group meeting on January 23, 2018.

Types of websites

The main types of websites you may want to create include:

  1. Personal websites
  2. Package websites
  3. Project websites
  4. Blogs

R Markdown website basics

The minimum requirements for an R Markdown website are:

Markdown To Websites

  • index.Rmd: contains the content for the website homepage
  • _site.yml: contains metadata for the website

A basic example of a _site.yml file for a website with two pages:

And a basic index.Rmd to create the Home page:

You can find an overview of R Markdown website basics here.


This tutorial will focus on hosting websites through GitHub pages. Hosting websites on GitHub pages is free.

If you don’t have a GitHub account already, sign up for one at with username YOUR_GH_NAME. I’ll be referring to this username, YOUR_GH_NAME, as “your GitHub username” throughout this tutorial.

There are other free sites for website hosting, and another popular choice is Netlify.

Personal websites

Let’s say that I wanted to build a website for my cats.

There are two main steps for creating a personal website that will be hosted on GitHub:

  1. GitHub setup
  2. Local setup

GitHub setup

  1. Create a GitHub repository (“repo”) named, where YOUR_GH_NAME is your GitHub username.
  2. Initialize it with a README
    • For the GitHub inexperienced: this can ease the process of cloning the repo by initializing the remote repo with a master branch

Local setup

  1. Clone this remote repository to a local directory with the same name,
  2. Add an R Project to this directory
  3. Create a _site.yml and index.Rmd file in your new directory

Why do I need an R Project?

The R Project is useful because RStudio will recognize your project as a website, and provide appropriate build tools.

Note: After creating the R Project and initial files, you may need to close the project and reopen it before R will recognize it as a website and show the appropriate build tools.

Create content

Edit the _site.yml file to change the metadata, layout, and theme of your website. Preview Jekyll themes here and play around with different options. Themes are easy to change even after you have added content.

For example, the _site.yml for my cats’ personal website looks like this:

Choose a default theme from for easy implementation.

Edit and create .Rmd files that contain your website content, which will produce the html pages of your website when you knit them.

For example, the index.Rmd file for my cats’ personal website homepage looks like this:

In this example the image files are stored in a subdirectory of named “files”.

Once you have your content written and the layout setup, on the Build tab in RStudio, select “Build Website”:

Now your local directory contains all of the files needed for your website:

And here’s what the resulting website looks like, hi kitties!

Deploy website

Basic approach:

  • Select “Upload files” from the main page of your GitHub repo:
  • And simply drag or select the files from the local repository:

Advanced approach (recommended):

  • use Git from the shell, from a Git client, or from within RStudio (another great reason to use an R Project!)
  • But this is not a Git/GitHub tutorial. If you want to learn more about Git/GitHub, which I encourage you to do, here’s a great resource to get you started:

Custom domains

The default is for your site to be hosted at, but you can add a custom domain name as well. There are two steps:

  1. In your GitHub repository, go to Settings > GitHub pages. Type your domain name in the box under Custom domain and hit Save.
  1. Add a CNAME file to your GitHub repsitory

It will appear like this in your repository:

And inside the file you will simply have your domain name:

Package websites

An example from the website for my package ezfun:

Use Hadley Wickham’s great package pkgdown to easily build a website from your package that is hosted on GitHub. Details of pkgdown can be found on the pkgdown website, which was also created using pkgdown.

This assumes you already have an R package with a local directory and a GitHub repository.

From within your package directory run:

  • This will add a folder called docs to the local directory for your package

  • Upload/push these changes to the GitHub repository for your package

  • In the GitHub repository for your package go to Settings > GitHub pages. Select “master branch/docs folder” as the source and hit Save

  • The page will be added as to your personal website as

    • The Home page of the site will be pulled from the README file on your package repository
    • The Reference page of the site lists the included functions with their description
    • Each function can be clicked through to see the help page, if any
    • Would also build pages for any available vignettes

And you’re done, it’s that easy.

Project websites

You can create a website for a non-package repository as well. For example, I have a page on my website linking to the repository in which this tutorial is stored.

Local setup

From within the local directory of the project of interest:

  1. Create a _site.yml and index.Rmd file in your new directory
  2. Edit these files to create content and manage layout, as before for personal websites

GitHub setup

  • Upload/push these new files to the GitHub repository for your project

  • Enable GitHub pages for the repository by going to Settings > GitHub Pages, where you’ll select the “master branch” folder and hit Save


R Markdown websites are simple to create and deploy, but can become cumbersome if you make frequent updates or additions to the website, as in the case of a blog. Luckily, the R package blogdown exists just for this purpose. blogdown is an R package that allows you to create static websites, which means that the deployed version of the website only consists of JavaScript, HTML, CSS, and images. Luckily the blogdown package makes it so that you don’t have to know any of those things to create a beautiful website for your blog, powered by Hugo.

For a complete resource on using the blogdown website, checkout this short blogdown book.

I don’t have a personal blog, so let’s look at the website I built to feature the events and blog of the R-Ladies NYC organization as an example.


The first three steps are similar to those from creating a basic R Markdown website:

  1. Create a GitHub repository named, where YOUR_GH_NAME is your GitHub username, initialized with a README file
  2. Clone the GitHub repo to a local directory with the same name
  3. Add an R Project to the local directoroy

Next we get started with blogdown.

  1. Install blogdown and Hugo
  1. Choose a theme and find the link to the theme’s GitHub repository. In this case themes aren’t quite as easy to change as with basic R Markdown websites, so choose carefully.

  2. Within your project session, generate a new site. The option theme_example = TRUE will obtain the files for an example site that you can then customize for your needs. Below “user/repo” refers to the GitHub username and GitHub repository for your selected theme.

This will generate all of the file structure for your new blog.

After this is complete, you should quit and then reopen the project. Upon reopening, RStudio will recognize the project as a website.

Customizing the appearance

Make changes to the config.toml file (equivalent to the _site.yml from basic R Markdown websites) to change the layout and appearance of your website. The available features of the config.toml file will differ depending on your theme, and most theme examples come with a well annotated config.toml that you can use as a template.

Once you have customized your website features, click on the RStudio addin “Serve Site” to preview the site locally.

Writing a new blog post

There are several ways to create a new post for your site, but the easiest is using the RStudio addin “New Post”:

Markdown To Website Free

This opens a pop-up where you can enter the meta-data for a new post:

Vuze update mac. In addition to setting the Title, Author and Date of the post, you can additionally create categories, which will organize your posts in folders, and can add tags to posts, which can make them searchable within your site’s content. Be aware that the functioning of these features will vary by theme. Dates can be in the future to allow future release of a post.

Notice at the bottom that you can select whether to use a regular markdown (.md) or R markdown (.Rmd) file. .Rmd files will have to be rendered before generating html pages so it is best practice to limit their use to cases where R code is included.

A file name and slug will automatically be generated based on the other metadata. The slug is a URL friendly title of your post.


A blogdown site is a bit more cumbersome both to build and to host on GitHub as compared to a regular R Markdown website, and as compared to what I described above.

Problem 1: Because it is a static site, upon building, the files needed to generate the site online are automatically created in a separate subdirectory called public within your local directory. However this will cause problems with GitHub hosting since the files to host need to be in the local directory

My solution:

  1. Maintain separate directories for the source files (I named this directory “source”) and for the static files (the directory that will be generated on build. The “source” folder is where your R project and config.toml files will live.
  1. In your config.toml use the option publishDir = to customize blogdown to publish to the folder, rather than to the default local location

Problem 2: GitHub defaults to using Jekyll with website content, and this needs to be disabled since blogdown sites are built with Hugo

To get around this, you need to include an empty file named .nojekyll in your GitHub repo, prior to publishing.

Markdown Link To Website

Additional resources

A compiled list of the additional resources/links presented throughout this tutorial:

  • an overview of R Markdown website basics
  • an introduction to Git/GitHub
  • Hadley Wickham’s pkgdown website
  • Yihui Xie’s blogdown book
  • Hugo themes for use with your blogdown website