Migrate branding and posts

.github/workflows/deploy.yml

@@ -0,0 +1,50 @@
+name: Deploy to GitHub Pages
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+jobs:
+  build:
+    name: Build Docusaurus
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: npm ci
+      - name: Build website
+        run: npm run build
+
+      - name: Upload Build Artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: build
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+
+    # Grant GITHUB_TOKEN the permissions required to make a Pages deployment
+    permissions:
+      pages: write # to deploy to Pages
+      id-token: write # to verify the deployment originates from an appropriate source
+
+    # Deploy to the github-pages environment
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4
+
+

.github/workflows/deploy.yml~

@@ -0,0 +1,51 @@
+name: Deploy to GitHub Pages
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master
+jobs:
+  build:
+    name: Build Docusaurus
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: yarn
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+      - name: Build website
+        run: yarn build
+
+      - name: Upload Build Artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: build
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+
+    # Grant GITHUB_TOKEN the permissions required to make a Pages deployment
+    permissions:
+      pages: write # to deploy to Pages
+      id-token: write # to verify the deployment originates from an appropriate source
+
+    # Deploy to the github-pages environment
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4
+
+

.github/workflows/test-deploy.yml

@@ -0,0 +1,28 @@
+name: Test deployment
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master
+    # Review gh actions docs if you want to further define triggers, paths, etc
+    # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on
+
+jobs:
+  test-deploy:
+    name: Test deployment
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: npm ci
+      - name: Test build website
+        run: npm run build
+
+

.github/workflows/test-deploy.yml~

@@ -0,0 +1,28 @@
+name: Test deployment
+
+on:
+  pull_request:
+    branches:
+      - main
+    # Review gh actions docs if you want to further define triggers, paths, etc
+    # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on
+
+jobs:
+  test-deploy:
+    name: Test deployment
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: yarn
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+      - name: Test build website
+        run: yarn build
+
+

blog/2020-01-04-announcing.md

@@ -0,0 +1,27 @@
+---
+slug: announcing
+title: Announcing Reason Bangalore
+authors: [prometheansacrifice]
+---
+
+Hey,
+
+
+Finally, Bengaluru finally gets it's own Reason/OCaml community. And
+hopefully, the meetup serves as an excuse to meet, exchange ideas,
+and hack on all things Reason/OCaml. 
+
+<!--more-->
+
+Reason Bangalore is an inclusive, beginner friendly and motivated
+individuals, looking to help each with Reason/OCaml. It is important
+that we're respectful of each other.
+
+We hope Reason Bangalore provides a great platform to discuss type
+safety, ecosystem shortcomings, tooling, proposed solutions, FP
+influenced software practises (UI, reproducible builds, abstractions
+etc) and all things FP that can help us practise writing robust
+software. At the same time, we need to be mindful of newcomers and
+ensures everyone feels welcome :)
+
+Cheers!

blog/2020-01-19-meetup-1.md

@@ -0,0 +1,21 @@
+---
+slug: meetup-1
+title: Meetup 1 - Prologue MDX Blog Post
+authors: [prometheansacrifice]
+---
+
+Thank you everyone for the great response to the first ever
+Reason/OCaml meetup in Bangalore. Here's what we have planned:
+
+<!--more-->
+
+The first meetup is aimed at being an introductory one. We have
+encourages all the speakers to feel free to explain the whys and hows
+of Reason.
+
+Quickly summarised, talks range from explaining the rationale behind
+picking up Reason/OCaml for a given set of problems to completely
+serveless setup of GraphQL and ReasonML. We also plan to discuss how
+Reason, with it's static types, can help manage large SPA code bases.
+
+Stay tuned!

blog/2024-04-29-ann-next-meetup.md

@@ -0,0 +1,7 @@
+---
+slug: ann-next-meetup
+title: "Meetup Announcement: Live coding a web server with OCaml"
+authors: [prometheansacrifice]
+---
+
+As planned, we're meeting again virtually this Sunday, May 5th. It's a super casual online meet where we live code a web server in OCaml and help each other learn OCaml.

blog/2024-04-29-intro-to-fp-with-ocaml.md

@@ -0,0 +1,7 @@
+---
+slug: intro-to-fp-with-ocaml
+title: Introduction to Functional Programming with OCaml
+authors: [prometheansacrifice]
+---
+
+In our latest meeting, familiar faces returned, showing sustained interest since our group's inception. Attendees, experienced in OCaml or eager to learn, dedicated their Sunday afternoon to engage with us. We agreed to meet weekly online to write OCaml together, enhancing our community ties. Discussions also covered potential venues in Bangalore for in-person gatherings. Our focus was on functional programming, specifically OCaml. For a deeper dive into the topics discussed, visit [Manas Jayanth's Slides](https://slides.manas-jayanth.com/org/reason-bangalore-introduction-to-functional-programming/). Join us next time as we continue exploring and building our community through collaboration and coding.

blog/2024-05-05-meetup-2-and-ann-next-meetup.md

@@ -0,0 +1,30 @@
+---
+slug: meetup-2-and-ann-next-meetup
+title: "Meetup 2: Live coding a web server with OCaml and what's next"
+authors: [prometheansacrifice]
+---
+
+We wrote a Dream web server with a hello world route - ie. you `curl` and get the string `“hello, world”` from the `“/“` endpoint. We started from scratch, empty directory even, and worked our way up. We intend to continue this series, so if you like to catch we what we have so far, here’s what we did so far.

We,
+
+1. Created a `package.json` to install a local compiler and build system ( Dune ). 
+2. Initialised a project with `dune init proj reason_ocaml_dev`. 
+3. Ran the hello world setup by Dune for us with the `dune exec` command.
+4. Installed `ocaml-lsp-server`, `ocamlformat` and `reason` syntax extension
+5. Referred to https://github.com/ManasJayanth/fullstack-reason-react-demo and wrote the first Dream route (I had never written one before). Made mistakes, saw type errors in action, fixed and for the hello world Dream web server to work.
+
+We have two talk proposals for next meetup, either,
+
+1. @shaktimaan introduce us to some more Dream fundamentals and  help us understand @ocaml_orgs website.
+2. Kaushik Hatti will show us getting started with Ocsigen so we can compare notes/experience.
+
+So, we’re meeting up (online) again this Sunday. At 2pm IST. 

+
+## Code
+
+You can find the code we wrote so far on our [Github org](https://github.com/ReasonIndia/dream-web-server-sessions). You can reach out me on X at [@ManasJayanth](https://twitter.com/ManasJayanth) if you have any trouble.
+
+## Stay in touch with us

+
+Twitter: https://twitter.com/ReasonBangalore
+
+Discord: https://discord.com/invite/RamP7SCKcU

blog/authors.yml

@@ -1,17 +1,5 @@
-endi:
-  name: Endilie Yacop Sucipto
-  title: Maintainer of Docusaurus
-  url: https://github.com/endiliey
-  image_url: https://github.com/endiliey.png
-
-yangshun:
-  name: Yangshun Tay
-  title: Front End Engineer @ Facebook
-  url: https://github.com/yangshun
-  image_url: https://github.com/yangshun.png
-
-slorber:
-  name: Sébastien Lorber
-  title: Docusaurus maintainer
-  url: https://sebastienlorber.com
-  image_url: https://github.com/slorber.png
+prometheansacrifice:
+  name: Manas Jayanth
+  title: Managing Partner at Dining Philosophers, LLP.
+  url: https://github.com/ManasJayanth
+  image_url: https://github.com/ManasJayanth.png