[docs] Move docs pages to this repo (#165)

## Summary
Move docs pages to this repo.

- [x] yarn start locally
- [x] CICD preview

TODOs: in separate PRs
- linters
- devbox.json for quick local dev
- quick start readme on how to contribute

## How was it tested?
`yarn install`
`yarn build`
`yarn start`

Author: LucilleH

.github/workflows/deployment.yaml

@@ -0,0 +1,45 @@
+name: docs-deployment
+
+concurrency: deployment
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+
+env:
+  JETPACK_SECRET_KEY: ${{ secrets.JETPACK_SECRET_KEY }}
+
+jobs:
+  deploy-docs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: dorny/paths-filter@v2
+        id: filter
+        with:
+          filters: |
+            docs:
+              - 'docs/**'
+      - uses: bahmutov/npm-install@v1
+        if: steps.filter.outputs.docs == 'true' || github.event.workflow_dispatch
+        with:
+          working-directory: docs/app
+      - name: Mount docs node_modules
+        if: steps.filter.outputs.docs == 'true' || github.event.workflow_dispatch
+        uses: actions/cache@v3
+        with:
+          path: docs/app/node_modules
+          key: docs-node-modules
+      - name: docs build
+        if: steps.filter.outputs.docs == 'true' || github.event.workflow_dispatch
+        run: |
+          yarn install
+          yarn run build
+        working-directory: docs/app
+      - name: Deploy docs to production
+        if: steps.filter.outputs.docs == 'true' || github.event.workflow_dispatch
+        run: |
+          curl https://get.jetpack.io -fsSL | bash -s -- -y
+          jetpack up docs --environment=prod --debug

.github/workflows/previews.yaml

@@ -0,0 +1,49 @@
+name: docs-preview
+
+on:
+  workflow_dispatch:
+  push:
+    branches-ignore:
+      - main
+
+permissions:
+  contents: read
+  pull-requests: read
+
+env:
+  JETPACK_SECRET_KEY: ${{ secrets.JETPACK_SECRET_KEY }}
+
+jobs:
+  deploy-docs-preview:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v3
+        - uses: dorny/paths-filter@v2
+          id: filter
+          with:
+            filters: |
+              docs:
+                - 'docs/**'
+        - uses: bahmutov/npm-install@v1
+          if: steps.filter.outputs.docs == 'true'
+          with:
+            working-directory: docs/app
+        - name: Mount docs node_modules
+          if: steps.filter.outputs.docs == 'true'
+          uses: actions/cache@v3
+          with:
+            path: docs/app/node_modules
+            key: docs-node-modules
+        - name: Docs build
+          if: steps.filter.outputs.docs == 'true'
+          run: |
+            yarn install
+            yarn run build
+          working-directory: docs/app
+        - name: Deploy docs preview
+          if: steps.filter.outputs.docs == 'true'
+          run: |
+            curl https://get.jetpack.io -fsSL | bash -s -- -y
+            jetpack up docs \
+              --ttl 300 --debug \
+              -n jetpack-io-preview-$(echo "${GITHUB_REF_NAME}" | sed "s/[^0-9a-zA-Z]/-/g")

docs/.dockerignore

@@ -0,0 +1,3 @@
+app/build/Release
+app/.docusaurus
+app/node_modules

docs/.gitignore

@@ -0,0 +1,29 @@
+# Dependencies
+app/node_modules/
+
+# Production
+app/build/
+
+# Generated files
+app/.docusaurus/
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+app/.yarn/*
+!app/.yarn/patches
+!app/.yarn/plugins
+!app/.yarn/releases
+!app/.yarn/sdks
+!app/.yarn/versions
+# If we want to start checking in the cache to enable 'zero install':
+# !app/.yarn/cache

docs/Dockerfile

@@ -0,0 +1,6 @@
+# syntax=docker/dockerfile:1 
+FROM nginx:stable-alpine as deploy
+WORKDIR /app
+EXPOSE 80
+COPY ./app/build ./static/devbox/
+COPY ./nginx.conf /etc/nginx/nginx.conf

docs/app/.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

docs/app/README.md

@@ -0,0 +1,41 @@
+# Website
+
+This website is built using [Docusaurus 2](https://docusaurus.io/), a modern static website generator.
+
+### Installation
+
+```
+$ yarn
+```
+
+### Local Development
+
+```
+$ yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+### Build
+
+```
+$ yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+### Deployment
+
+Using SSH:
+
+```
+$ USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```
+$ GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

docs/app/babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

docs/app/docs/cli_reference.md

@@ -0,0 +1,44 @@
+---
+title: CLI Reference
+sidebar_position: 4
+---
+
+## add
+
+Add Nix packages to your devbox project. To see a list of available packages, you can use [Nix Package Search](https://search.nixos.org/packages). Added packages are stored in `devbox.json`
+
+For example the following will add Python 3.10 to your `devbox.json`
+
+```nix
+devbox add python310
+```
+
+You can add multiple packages in a single command:
+
+```nix
+devbox add python310 curl 
+```
+
+## build
+
+Builds your current source directory and devbox configuration as a Docker container. Devbox will create a plan for your container based on your source code, and then apply the packages and stage overrides in your `devbox.json`.
+
+## init
+
+Initializes a devbox project by creating a blank `devbox.json` file in your directory. 
+
+## plan
+
+Shows the current plan that devbox will use to create your shell and build your project. 
+
+This will include any install/build/run commands that devbox has automatically detected, or that you have included in your devbox.json (see [Configuration Guide](../configuration) for more details)
+
+## rm
+
+Removes packages from your devbox.json.
+
+## shell
+
+Starts an isolated nix shell with the packages and configuration in your local `devbox.json`. 
+
+Any packages in your devbox.json that have not been previously installed will be downloaded and installed in your machine, and made available while your shell is running. 

docs/app/docs/configuration.md

@@ -0,0 +1,94 @@
+---
+title: Configuration Guide
+sidebar_position: 5
+---
+
+Your devbox configuration is stored in a `devbox.json` file, located in your project's root directory. This file can be edited directly, or using the [devbox CLI](cli_reference.md).
+
+```json
+{
+    "packages": [],
+    "shell": {
+        "init_hook": "..."
+    },
+    "install_stage": {
+        "command": "..."
+    },
+    "build_stage":{
+        "command":"..."
+    },
+    "start_stage": {
+        "command": "..."
+    }
+}
+```
+
+### Packages
+
+This is a list of Nix packages that should be installed in your Devbox shell and containers. These packages will only be installed and available within your shell, and will have precedence over any packages installed in your local machine. You can search for Nix packages using [Nix Package Search](https://search.nixos.org/packages).
+
+You can add packages to your devbox.json using `devbox add <package_name>`, and remove them using `devbox rm <package_name>`
+
+### Shell
+
+You can configure `devbox shell` to run a custom commands at startup by setting an `init_hook`. This hook runs after any other `~/.*rc` scripts, allowing you to override environment variables or further customize the shell.
+
+This is an example `devbox.json` that customizes the prompt and prints a welcome message:
+
+```json
+{
+    "shell": {
+        "init_hook": "export PS1='📦 devbox> '\necho 'Welcome! See CONTRIBUTING.md for tips on contributing to devbox.'"
+    }
+}
+```
+
+When run, you'll see:
+
+```
+> devbox shell
+Installing nix packages. This may take a while...
+Starting a devbox shell...
+Welcome! See CONTRIBUTING.md for tips on contributing to devbox.
+📦 devbox>
+```
+
+### Stages
+
+Stages are used to configure and run commands at different points of container creation. For languages that support autodetction, Devbox will automatically detect and configure the correct stage commands for your project based on your source code. You can override any of these stages by configuring them in your devbox.json
+
+* The **install stage** will run after your base container has been initialized and your Nix packages are installed. This stage should be used to download and build your application's dependencies
+* The **build stage** runs after the install stage, and should be used to build or bundle your application.
+* The **start stage** will run when your container is started. This stage should include any commands needed to start and run your application.
+
+Each stage takes a single command that will be run when the stage is reached in your container build.
+
+```json
+//Install stage command for a Node Project
+"install_stage": {
+    "command": "yarn install"
+}
+```
+
+### Example: A Rust Devbox
+
+An example of a devbox configuration for a Rust project called `hello_world` might look like the following:
+
+```json
+{
+    "packages": [
+        "rustc"
+        "cargo",
+        "libiconv",
+    ],
+    "install_stage": {
+        "command": "cargo install --path ."
+    },
+    "build_stage":{
+        "command":"cargo build"
+    },
+    "start_stage": {
+        "command": "./target/build/hello_world"
+    }
+}
+```