diff --git a/docs/_markbind/layouts/devGuide.md b/docs/_markbind/layouts/devGuide.md
index 33c9dc6abd..3fee89f963 100644
--- a/docs/_markbind/layouts/devGuide.md
+++ b/docs/_markbind/layouts/devGuide.md
@@ -16,6 +16,9 @@
* [Server Side Rendering]({{baseUrl}}/devGuide/design/serverSideRendering.html)
* [Writing Components]({{baseUrl}}/devGuide/writingComponents.html)
* [Writing Plugins]({{baseUrl}}/devGuide/writingPlugins.html)
+* GitHub Actions :expanded:
+ * [Overview]({{baseUrl}}/devGuide/githubActions/overview.html)
+ * [markbind-action]({{baseUrl}}/devGuide/githubActions/markbindAction.html)
* [Project management]({{baseUrl}}/devGuide/projectManagement.html)
* Appendices :expanded:
* [Style guides]({{baseUrl}}/devGuide/styleGuides.html)
diff --git a/docs/devGuide/githubActions/markbindAction.md b/docs/devGuide/githubActions/markbindAction.md
new file mode 100644
index 0000000000..f790148d55
--- /dev/null
+++ b/docs/devGuide/githubActions/markbindAction.md
@@ -0,0 +1,50 @@
+{% set title = "GitHub Actions: markbind-action" %}
+{{ title }}
+
+
+ title: "{{ title }}"
+ layout: devGuide.md
+ pageNav: default
+
+
+# {{ title }}
+
+
+
+A GitHub Action that builds and deploys a MarkBind site. It helps users to streamline their workflow by:
+* Making it easier to deploy without having to write their own actions from scratch.
+* Making the workflows consistent and up to date with any changes specific to MarkBind.
+
+The source code is at [MarkBind/markbind-action](https://github.com/MarkBind/markbind-action).
+
+
+**Follow the steps below to get started on modifying the source code.**
+## Setting Up
+1. Fork the [action repository](https://github.com/MarkBind/markbind-action).
+1. Familiarise with the existing workflow syntax/options provided in the repository's [README.md](https://github.com/MarkBind/markbind-action#readme).
+1. Set up a repository that contains a MarkBind site to test the action:
+ 1. Create a repository.
+ 1. Set up MarkBind and run `markbind init` to populate with default content.
+ 1. Push your repository to GitHub.
+ * [Example](https://github.com/MarkBind/init-typical)
+
+## Modifying the action
+1. Create a new branch from master to work on your changes.
+1. Make necessary modifications to the workflow files.
+1. Update the repository's README.md to reflect the changes.
+
+## Testing the action
+1. Include a workflow file in your test repository to test your modified version of the action.
+ * Instead of using `uses: MarkBind/markbind-action@v2` in the workflow file, use `uses: yourGitHubName/markbind-action@yourBranch` to reference the unpublished version of the action that you are currently developing.
+ * e.g. `uses: tlylt/markbind-action@main`
+1. Trigger the action as needed, check and validate the results in the action logs.
+
+You can now submit PRs to improve MarkBind's Github actions! 🎉
+
+## Release Management
+Based on the [Github Actions documentation](https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-release-management-for-actions), we are using tags for release management.
+
+> * Create and validate a release on a release branch (such as `release/v1`) before creating the release tag (for example, `v1.0.2`).
+> * Create a release using semantic versioning. For more information, see "[Creating releases](https://docs.github.com/en/articles/creating-releases)."
+> * Move the major version tag (such as `v1`, `v2`) to point to the Git ref of the current release. For more information, see "[Git basics - tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)."
+> * Introduce a new major version tag (`v2`) for changes that will break existing workflows. For example, changing an action's inputs would be a breaking change.
\ No newline at end of file
diff --git a/docs/devGuide/githubActions/overview.md b/docs/devGuide/githubActions/overview.md
new file mode 100644
index 0000000000..03a2a11639
--- /dev/null
+++ b/docs/devGuide/githubActions/overview.md
@@ -0,0 +1,22 @@
+{% set title = "GitHub Actions: Overview" %}
+{{ title }}
+
+
+ title: "{{ title }}"
+ layout: devGuide.md
+ pageNav: default
+
+
+# {{ title }}
+
+
+
+A GitHub Action can perform a variety of tasks, including automating the build and deployment of a MarkBind site.
+* [MarkBind/markbind-action](https://github.com/MarkBind/markbind-action) is a [published action](https://github.com/marketplace/actions/markbind-action) that builds and deploys your MarkBind site.
+
+
+**Before any development, ensure you have a basic knowledge of GitHub Actions**
+* [Official GitHub Actions documentation](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions)
+ * [Workflow syntax](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
+ * [Creating a composite action](https://docs.github.com/en/actions/creating-actions/creating-a-composite-action)
+ * [Releasing and maintaining actions](https://docs.github.com/en/actions/creating-actions/releasing-and-maintaining-actions)
diff --git a/docs/userGuide/deployingTheSite.md b/docs/userGuide/deployingTheSite.md
index b7a2af1dd5..5f220c9f13 100644
--- a/docs/userGuide/deployingTheSite.md
+++ b/docs/userGuide/deployingTheSite.md
@@ -118,6 +118,27 @@ The sample `deploy.yml` workflow above uses the [default Github Token secret](ht
Once you have created the file, commit and push the file to your repo. Github Actions should start to build and deploy your markbind site. You can verify this by visiting `www.github.com///actions`.
+
+
+MarkBind provides a helper GitHub Action that you can use to simplify your workflow file. A sample workflow file utilizing the action is as follows:
+```yml
+name: Deploy MarkBind Site
+on:
+ push:
+ branches: master
+
+jobs:
+ build_and_deploy:
+ runs-on: ubuntu-latest
+ steps:
+ - name: Build & Deploy MarkBind site
+ uses: MarkBind/markbind-action@v2
+ with:
+ token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+Read the [action documentation](https://github.com/MarkBind/markbind-action#readme) to understand the various configuration options.
+
+
For more information on customizing your workflow file to fit your specific needs, you may refer to the [Github Action Docs](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions).