ci: automate docusaurus github pages deployment

spencerlepine · Mar 30, 2024 · 0d0974e · 0d0974e
1 parent ea44ed2
commit 0d0974e
Show file tree

Hide file tree

Showing 5 changed files with 10 additions and 10 deletions.
diff --git a/.github/workflows/calibreapp-image-optimizer.yml b/.github/workflows/calibreapp-image-optimizer.yml
@@ -13,6 +13,7 @@ jobs:
     # Only run on Pull Requests within the same repository, and not from forks.
     if: github.event.pull_request.head.repo.full_name == github.repository
     name: calibreapp/image-actions
+    permissions: write-all
     runs-on: ubuntu-latest
     steps:
       - name: Checkout Repo

diff --git a/.github/workflows/github-pages-deploy.yml b/.github/workflows/github-pages-deploy.yml
@@ -28,12 +28,12 @@ jobs:
         run: yarn build
       # 👆 Build steps
       - name: Setup Pages
-        uses: actions/configure-pages@v
+        uses: actions/configure-pages@v4
       - name: Upload artifact
-        uses: actions/upload-pages-artifact@v4
+        uses: actions/upload-pages-artifact@v3
         with:
           # 👇 Specify build output path
           path: build
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v4
+        uses: actions/deploy-pages@v4
diff --git a/...uilding-a-readme-crawler-with-node-js/building-a-readme-crawler-with-node-js.md b/...uilding-a-readme-crawler-with-node-js/building-a-readme-crawler-with-node-js.md
@@ -12,7 +12,7 @@ Building a README Crawler with Node.js
 
 An Overview of the Node.js README Web Crawler project and how I created it.
 
-A recent project of mine was this Node.js [web crawler](https://spencerlepine.com/blog/building-a-web-crawler-with-node.js). Working on that led to this idea for another crawler. I wanted a way to navigate through GitHub and search for obvious typos. I had this idea after stumbling across silly typos on numerous portfolio pages. Perhaps I could help fix these errors and ensure these portfolio/sites are more presentable.
+A recent project of mine was this Node.js [web crawler](https://github.com/spencerlepine/readme-crawler). Working on that led to this idea for another crawler. I wanted a way to navigate through GitHub and search for obvious typos. I had this idea after stumbling across silly typos on numerous portfolio pages. Perhaps I could help fix these errors and ensure these portfolio/sites are more presentable.
 
 If you’re interest in the final product, you can find the package [here](https://www.npmjs.com/package/readme-crawler), as well as the [GitHub Repo](https://github.com/spencerlepine/readme-crawler).
 
@@ -143,7 +143,7 @@ run() {
 ```
 
 
-This project is also available on [npm](www.npmjs.com/package/readme-crawler). Install the package and try it yourself!
+This project is also available on [npm](https://www.npmjs.com/package/readme-crawler). Install the package and try it yourself!
 
 ```js
 import ReadMeCrawler from 'readme-crawler';

diff --git a/...-end-engineer-interview/preparing-for-my-amazon-front-end-engineer-interview.md b/...-end-engineer-interview/preparing-for-my-amazon-front-end-engineer-interview.md
@@ -12,7 +12,7 @@ After my recent interviews with Amazon for the Front End Engineer role, I though
 
 TL;DR - practice LeetCode, practice vanilla JS, always verbalize your thought process, prepare stories to share in the STAR framework, and be confident (or fake it).
 
-If you are interested in general advice for landing your first role in tech, I wrote another article about that: [How I Became a Software Engineer at 20 With No CS Degree](TODO)
+If you are interested in general advice for landing your first role in tech, I wrote another article about that: [How I Became a Software Engineer at 20 With No CS Degree](https://sppencerlepine.com/blog-TODO)
 
 For the Amazon FEE interviews, you can find a lot of material online, since thousands of people are applying to these roles. In this article I will share the resources that helped me and give advice on what to study.
 
@@ -68,8 +68,8 @@ I will not go into detail about the specific problems I was given. You should fi
 All of this is biased to my experience, and you should look beyond just this article. Every new day you study, every hour you invest more time, your skills will sharpen. Focus on what you can control.
 
 I hope you got  some value from the article. If you are interested in reading more about my job searching and landing my first role as a software engineer, checkout out these articles:
- - [How I Became a Software Engineer at 20 With No CS Degree](TODO)
- - [My Coding Bootcamp Experience at Hack Reactor](TODO)   
+ - [How I Became a Software Engineer at 20 With No CS Degree](https://sppencerlepine.com/blog-TODO)
+ - [My Coding Bootcamp Experience at Hack Reactor](https://sppencerlepine.com/blog-TODO)   
 
 Follow my journey and connected with me here:
 - LinkedIn: [/in/spencer-lepine](https://www.linkedin.com/in/spencer-lepine/)

diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -16,13 +16,12 @@ const config = {
   url: 'https://spencer.github.io',
   // Set the /<baseUrl>/ pathname under which your site is served
   // For GitHub pages deployment, it is often '/<projectName>/'
-  baseUrl: '/blog',
+  baseUrl: '/blog/',
 
   // GitHub pages deployment config.
   // If you aren't using GitHub pages, you don't need these.
   organizationName: 'spencerlepine', // Usually your GitHub org/user name.
   projectName: 'blog', // Usually your repo name.
-  trailingSlash: false,
 
   onBrokenLinks: 'throw',
   onBrokenMarkdownLinks: 'warn',