Use gh‑pages branch

.github/workflows/publish.yml

@@ -0,0 +1,28 @@
+name: Build and Deploy to GitHub Pages
+on:
+  push:
+    branches:
+    - master
+jobs:
+  build-and-deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout 🛎️
+        uses: actions/checkout@v2
+        with:
+          persist-credentials: false
+
+      - name: Setup Node
+        uses: actions/setup-node@v1
+        with:
+          node-version: '14.x'
+
+      - name: Install and Build 🔧
+        run: |
+          npm install
+          npm run build
+      - name: Deploy 🚀
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          publish_dir: ./out

.gitignore

@@ -1,3 +1,6 @@
+# Output directory
+/out
+
 # Logs
 logs
 *.log

README.md

@@ -6,14 +6,14 @@ A repository template for ECMAScript proposals.
 
 Please ensure the following:
   1. You have read the [process document](https://tc39.github.io/process-document/)
-  1. You have reviewed the [existing proposals](https://github.com/tc39/proposals/)
+  1. You have reviewed the [existing proposals](https://github.com/tc39/proposals)
   1. You are aware that your proposal requires being a member of TC39, or locating a TC39 delegate to "champion" your proposal
 
 ## Create your proposal repo
 
 Follow these steps:
   1.  Click the green ["use this template"](https://github.com/tc39/template-for-proposals/generate) button in the repo header. (Note: Do not fork this repo in GitHub's web interface, as that will later prevent transfer into the TC39 organization)
-  1.  Go to your repo settings “Options” page, under “GitHub Pages”, and set the source to the **master branch** (and click Save, if it does not autosave this setting)
+  1.  Go to your repo settings “Options” page, under “GitHub Pages”, and set the source to the **`gh-pages` branch** (and click Save, if it does not autosave this setting)
       1. check "Enforce HTTPS"
       1. On "Options", under "Features", Ensure "Issues" is checked, and disable "Wiki", and "Projects" (unless you intend to use Projects)
       1. Under "Merge button", check "automatically delete head branches"
@@ -56,5 +56,5 @@ Follow these steps:
   1. Make your changes to `spec.emu` (ecmarkup uses HTML syntax, but is not HTML, so I strongly suggest not naming it ".html")
   1. Any commit that makes meaningful changes to the spec, should run `npm run build` and commit the resulting output.
   1. Whenever you update `ecmarkup`, run `npm run build` and commit any changes that come from that dependency.
-  
-  [explainer]: https://github.com/tc39/how-we-work/blob/master/explainer.md
+
+[explainer]: https://github.com/tc39/how-we-work/blob/master/explainer.md