vault backup: 2022-12-11 21:50:17

README.md

@@ -1,2 +1,12 @@
 # linked-blog-md
 Markdown files for the linked-blog-starter repository
+
+talk about how to set this up here
+
+blog posts to write:
+- Obsidian publish alternative (steps using github actions and obsidian git extension)
+- How to extend this blog post
+
+
+notes to write:
+- how does this work

get-project-id-account-id-and-token-vercel.md

@@ -0,0 +1,9 @@
+---
+title: "How to get Project/Account ID and Token from Vercel"
+---
+1. Go to your Project settings, you'll want to copy the project id (Project Settings > General > Project Id). Save this for later.
+![[vercel-project-id.png]]
+2. Then go your account id ([Personal Account Settings](https://vercel.com/account) > General > Your ID). Save this for later as well.
+![[vercel-account-id.png]]
+3. Finally, generate a token under ([Personal Account Settings](https://vercel.com/account) > Tokens > Create). Finally save the value of the token for the next step.
+![[vercel-create-token.png]]

publish/README.md

@@ -29,6 +29,6 @@ Deploy the example using [Vercel](https://vercel.com?utm_source=github&utm_mediu
 
 # Notes
 - `linked-blog-starter` uses [Tailwind CSS](https://tailwindcss.com) [(v3.0)](https://tailwindcss.com/blog/tailwindcss-v3).
-- Markdown files are statically generated
+- Markdown files are [[statically-generated|statically generated]]
-- Html is generated using [generated GitHub flavoured markdown](https://github.com/sindresorhus/github-markdown-css)
+- Markdown is styled using [generated GitHub flavoured markdown](https://github.com/sindresorhus/github-markdown-css)
 

publish/connect-obsidian-vault-with-github.md

@@ -0,0 +1,8 @@
+---
+title: "How to setup your Github repository with Obsidian"
+---
+1. Clone the repository or "Download As Zip"
+![[clone-or-download-github.png]]
+2. Unzip the downloaded folder, then open the folder as a vault in Obsidian
+3. Install the [Obsidian Git](https://github.com/denolehov/obsidian-git) community plugin
+4. 

publish/customize-linked-blog-starter.md

@@ -0,0 +1,3 @@
+- Look at Fleeting Notes website for a more comprehensive example of what this blog can be made to become.
+- Linked Preview
+- 

publish/deploy-obsidian-notes-with-linked-blog-starter-and-github-actions.md

@@ -0,0 +1,20 @@
+By the end of this tutorial, you'll have a github repository that will automatically publish notes to your custom website everytime you upload new notes to the `publish` folder.
+
+## Step-by-step instructions to setup your blog
+
+1. Fork the repository [linked-blog-starter-md](https://github.com/matthewwong525/linked-blog-starter-md) repository. This repository is where the publishing occurs
+![[fork-linked-blog-starter-md.png]]
+2. Create a [Vercel](https://vercel.com/dashboard) account then go to your dashboard then (Add New... > Project)
+3. Import the repository you just forked
+4. In the "Configure Project" settings (before you deploy), **set the "Framework Preset" to Next.JS** . Then click the "Deploy" button.
+![[configure-project-vercel.png]]
+5. After clicking the Deploy button, you'll see that the deploy failed. That's as expected.
+6. OPTIONAL: Go to your [dashboard](https://vercel.com/dashboard), then click on the project you created and disconnect the git repository (Settings > Git > Disconnect)
+![[disconnect-repo-vercel.png]]
+7. Then, [[get-project-id-account-id-and-token-vercel|get the account id, project id and token from vercel]]
+8. Now with the account id, project id, and token, go back to your forked repository and update Github secrets (Settings > Secrets > Actions). Add the following secrets: `VERCEL_ORG_ID`, `VERCEL_PROJECT_ID`, `VERCEL_TOKEN`
+![[github-secrets-vercel.png]]
+9. Finally, click "Actions", and enable the workflow
+![[enable-actions-github.png]]
+10. Now whenever any notes are uploaded to the `publish` directory of the repository, they are automatically published online! You can find the domain in Vercel under `Projects`.
+11. See [[connect-obsidian-vault-with-github]]

publish/install-linked-blog-starter.md

@@ -0,0 +1,4 @@
+1. Clone this repo by running `git clone https://github.com/matthewwong525/linked-blog-starter`
+2. `cd linked-blog-starter`
+3. `npm install`
+4. `npm run dev`

publish/notes/install-linked-blog-starter.md

@@ -1,4 +0,0 @@
-1.  Clone this repo by running `git clone https://github.com/matthewwong525/linked-blog-starter`
-2.  `cd linked-blog-starter`
-3.  `npm install`
-4.  `npm run dev`

publish/posts/convert-obsidian-notes-to-common-markdown.md

@@ -1 +0,0 @@
-Placeholer

publish/posts/deploy-obsidian-notes-with-linked-blog-starter-and-github-actions.md

@@ -1 +0,0 @@
-Placeholder

publish/statically-generated.md

@@ -0,0 +1,3 @@
+> With Static Generation, tools like Next.js try to render that page mostly like it would in the browser but at compile time. This gives us the ability to serve the entire content on first load. The scripts still hydrate the page during this process, but ideally with fewer changes or no changes at all.
+
+https://www.freecodecamp.org/news/static-site-generation-with-nextjs/#:~:text=With%20Static%20Generation%2C%20tools%20like,or%20no%20changes%20at%20all.