From 2563afe44a8423707fc50d304cf7fee72f7a5537 Mon Sep 17 00:00:00 2001
From: jackyzha0 <j.zhao2k19@gmail.com>
Date: Mon, 19 Jul 2021 22:02:16 +0000
Subject: [PATCH] doc bump

---
 content/notes/hosting.md |    7 +++++--
 1 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/content/notes/hosting.md b/content/notes/hosting.md
index db42aa1..7a5973c 100644
--- a/content/notes/hosting.md
+++ b/content/notes/hosting.md
@@ -1,8 +1,7 @@
 ---
-title: "Deploying to GitHub Pages"
+title: "Deploying Quartz to the Web"
 ---
 
-
 ## GitHub Pages
 Quartz is designed to be effortless to deploy. If you forked and cloned Quartz directly from the repository, everything should already be good to go! You can head to `<YOUR-GITHUB-USERNAME.github.io/quartz` to see it live.
 
@@ -74,6 +73,10 @@
 3. Wait 30 minutes to an hour for the network changes to kick in.
 4. Done!
 
+## External Hosting
+Don't want to use GitHub Pages? Hugo builds everything for you! Everything is a packaged set of static files ready to deploy in `/public`. You can then upload this folder to a cloud provider to deploy. Alternatively, most providers also give users the option to link a GitHub repository and a folder to deploy. When doing this, ensure you select `/public` folder under the `master` branch.
+
+---
 
 Now that your Quartz is live, let's figure out how to make Quartz really *yours*!
 

--
Gitblit v1.10.0