ci: add GitHub Actions workflow to push README markdown to Notion page

Author: yCodeTech

.github/workflows/push_markdown_to_notion.yml

@@ -0,0 +1,22 @@
+# Push README markdown code to a Notion page when changes are pushed
+# or when the workflow is manually triggered.
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master
+jobs:
+  push_markdown_job:
+    runs-on: ubuntu-latest
+    name: Push Markdown to Notion
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+      - name: Push Markdown to Notion
+        uses: JoshStern/push-md-to-notion@v0.4.0
+        id: push_markdown
+        with:
+          notion-token: ${{ secrets.NOTION_TOKEN }}

README.md

@@ -1,13 +1,20 @@
+---
+notion_page: https://www.notion.so/Coding-Standards-3aafb6c5496580dfacedc234b633c8e4
+title: Coding Standards
+---
+
 # Coding Standards
-This is a little repo to document my coding standards and styles for easy reference.
 
+This is a little repo to document my coding standards and styles for easy reference.
 
 ## Indentation
+
 Tabs
 
 1 Tab = 4 spaces
 
 ## Curly brackets
+
 Start curly brackets on if else blocks and functions should be on the same line as the declaration with a space before the curly bracket.
 
 ```js
@@ -19,6 +26,7 @@ function thing() {
 ```
 
 ## else
+
 `else if` and `else` blocks should be on a new line after the previous closing curly bracket
 
 ```js
@@ -30,8 +38,8 @@ else {
 }
 ```
 
-
 # Git Commits
+
 I use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) with the extra commit types as [described in Angular](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type) and also some from the [Medium article - Conventional Commits: A Better Way ](https://medium.com/neudesic-innovation/conventional-commits-a-better-way-78d6785c2e08).
 
 ## Commit types
@@ -67,32 +75,31 @@ I use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) wit
 ## Abstraction
 
 - Helps focus on the essential elements of an object, and hide less important details or mechanisms.
-- Organises code more efficiently and extracts (*abstracts*) parts of the code into their own functions, methods, etc., using the DOT prinicple.
-  - Allows a program to not worry about the details of *how* an action is performed, but only *what* action is performed.
+- Organises code more efficiently and extracts (_abstracts_) parts of the code into their own functions, methods, etc., using the DOT prinicple.
+  - Allows a program to not worry about the details of _how_ an action is performed, but only _what_ action is performed.
   - A form of separation of concerns.
 - Helps to construct more understandable code and promotes reusability.
 
 ## Inheritance
 
 - Allows an object (child) to extend another object (parent).
-  - The child *inherits* all the properties and methods from the parent.
+  - The child _inherits_ all the properties and methods from the parent.
   - Allows usage of the code from the parent.
   - Enables the child to override methods and properties of the parent with it's own implementation.
 - Promotes reusability and avoids duplication, meaning DRYer code.
 
 ## Polymorphism
 
 - Extends inheritance, by allowing the parent object to become an `abstract` template object.
-  - Defines common methods for the child objects to *inherit* and use.
-  - Defines specific `abstract` methods that the child objects *must* implement.
+  - Defines common methods for the child objects to _inherit_ and use.
+  - Defines specific `abstract` methods that the child objects _must_ implement.
     - Allows child objects of different types to perform the same method but with differing implementations.
 - Promotes reusability and flexibility.
 
 ## Single Responsibility
 
 - Extends on the DOT principle.
-  - A *single* file should define a *single* object.
-  - An object should have only a *single* responsibility - Do One Thing.
-  - An object should have a *single* reason to change.
+  - A _single_ file should define a _single_ object.
+  - An object should have only a _single_ responsibility - Do One Thing.
+  - An object should have a _single_ reason to change.
 - Promotes organisation.
-