Set up parceljs

Author: reakaleek

.github/actions/bootstrap/action.yml

@@ -30,4 +30,11 @@ runs:
         echo "Version Number: ${REPO_VERSION}"
         echo "REPO_VERSION=${REPO_VERSION}" >> $GITHUB_ENV
         echo "full-version=${REPO_VERSION}" >> $GITHUB_OUTPUT
-        echo "major-version=$(echo ${REPO_VERSION} | cut -d"." -f1)" >> $GITHUB_OUTPUT
+        echo "major-version=$(echo ${REPO_VERSION} | cut -d"." -f1)" >> $GITHUB_OUTPUT
+        
+    - uses: actions/setup-node@v4
+      with:
+        cache: npm
+        cache-dependency-path: src/Elastic.Markdown/package-lock.json
+        node-version-file: .nvmrc
+      

.nvmrc

@@ -0,0 +1 @@
+22.13.1

README.md

@@ -137,6 +137,25 @@ To test performance it's best to build the binary and run outside of docker:
 For reference here's the `markitpy-doc` docset (50k markdown files) currently takes `14s` vs `several minutes` compared to
 existing surveyed tools
 
+# Local Development
+
+## Preqrequisites
+
+- [.NET 9.0 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/9.0)
+- [Node.js 22.13.1 (LTS)](https://nodejs.org/en/blog/release/v22.13.1)
+
+## Live Reload Markdown files in the `docs` folder:
+```shell
+dotnet run --project src/docs-builder -- serve
+```
+
+## Automatically rebuild changes to `src/Elastic.Markdown/Assets` JS and CSS files:
+```shell
+cd src/Elastic.Markdown
+npm ci
+npm run watch
+```
+
 # Release Process
 
 This section outlines the process for releasing a new version of this project.

src/Elastic.Markdown/.gitignore

@@ -0,0 +1,6 @@
+.parcel-cache/
+node_modules/
+_static/main.js
+_static/main.js.map
+_static/styles.css
+_static/styles.css.map