From 0d0974e932c6eda5828d960b4fe7d1c87f0eb5b1 Mon Sep 17 00:00:00 2001 From: Spencer Lepine <60903378+spencerlepine@users.noreply.github.com> Date: Fri, 29 Mar 2024 21:37:54 -0700 Subject: [PATCH] ci: automate docusaurus github pages deployment --- .github/workflows/calibreapp-image-optimizer.yml | 1 + .github/workflows/github-pages-deploy.yml | 6 +++--- .../building-a-readme-crawler-with-node-js.md | 4 ++-- .../preparing-for-my-amazon-front-end-engineer-interview.md | 6 +++--- docusaurus.config.js | 3 +-- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/.github/workflows/calibreapp-image-optimizer.yml b/.github/workflows/calibreapp-image-optimizer.yml index 78aab96..38bc2db 100644 --- 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 index 3148b43..7574013 100644 --- 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 \ No newline at end of file + uses: actions/deploy-pages@v4 diff --git a/blog/building-a-readme-crawler-with-node-js/building-a-readme-crawler-with-node-js.md b/blog/building-a-readme-crawler-with-node-js/building-a-readme-crawler-with-node-js.md index 993dddc..f6e8815 100644 --- a/blog/building-a-readme-crawler-with-node-js/building-a-readme-crawler-with-node-js.md +++ b/blog/building-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/blog/preparing-for-my-amazon-front-end-engineer-interview/preparing-for-my-amazon-front-end-engineer-interview.md b/blog/preparing-for-my-amazon-front-end-engineer-interview/preparing-for-my-amazon-front-end-engineer-interview.md index 4fcefe6..b3675d5 100644 --- a/blog/preparing-for-my-amazon-front-end-engineer-interview/preparing-for-my-amazon-front-end-engineer-interview.md +++ b/blog/preparing-for-my-amazon-front-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 index 1736839..8e08114 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -16,13 +16,12 @@ const config = { url: 'https://spencer.github.io', // Set the // pathname under which your site is served // For GitHub pages deployment, it is often '//' - 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',