test blog code blocks

.ghost.json

@@ -0,0 +1,10 @@
+{
+  "development": {
+    "apiUrl": "https://sdv.ghost.io",
+    "contentApiKey": "68a3f60d2555e5dff8a5df9e11"
+  },
+  "production": {
+    "apiUrl": "https://sdv.ghost.io",
+    "contentApiKey": "68a3f60d2555e5dff8a5df9e11"
+  }
+}

.github/workflows/build_publish.yml

@@ -1,9 +1,14 @@
-name: Update Website
+name: Build and Deploy SDV Blog
 
 on:
   push:
     branches:
-      main
+      - ghost-blog
+      - main
+  repository_dispatch:
+    branches:
+      - ghost-blog
+      - main
 jobs:
   build:
     runs-on: ubuntu-latest
@@ -13,3 +18,8 @@ jobs:
         with:
           access-token: ${{ secrets.BLOG_TOKEN }}
           deploy-branch: gh-pages
+          gatsby-args: --prefix-paths
+
+        env: 
+          SITEURL: ${{ secrets.SITEURL }}
+          SITEPATH: ${{ secrets.SITEPATH }}

README.md

@@ -1,3 +1,46 @@
-# web-dev
+# SDV Blog
 
-*https://sdv.dev/web-dev/*
+*https://sdv.dev/web-dev/*
+
+# Installing
+
+Then install dependencies
+
+```bash
+yarn
+```
+
+ 
+
+# Running
+
+Start the development server. You now have a Gatsby site pulling content from headless Ghost.
+
+```bash
+gatsby develop
+```
+
+# Deploying to Github Pages
+
+```bash
+npm run deploy
+```
+ 
+
+# Optimising
+
+You can disable the default Ghost Handlebars Theme front-end by enabling the `Make this site private` flag within your Ghost settings. This enables password protection in front of the Ghost install and sets `<meta name="robots" content="noindex" />` so your Gatsby front-end becomes the source of truth for SEO.
+
+&nbsp;
+
+# Extra options
+
+```bash
+# Run a production build, locally
+gatsby build
+
+# Serve a production build, locally
+gatsby serve
+```
+
+Gatsby `develop` uses the `development` config in `.ghost.json` - while Gatsby `build` uses the `production` config.