docs: Start adding some

Signed-off-by: Colin Walters <[email protected]>

Author: cgwalters

.github/workflows/docs.yml

@@ -0,0 +1,43 @@
+name: Docs
+
+on:
+  push:
+    branches: ["main"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+      - name: Setup Pages
+        uses: actions/configure-pages@v3
+      - name: Build with Jekyll
+        uses: actions/jekyll-build-pages@v1
+        with:
+          source: ./docs
+          destination: ./_site
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v1
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v1

docs/index.md

@@ -0,0 +1,14 @@
+---
+nav_order: 1
+---
+
+# Rationale
+
+The bootc project starts from a basic premise: Docker/OCI style containers
+are successful, what if we supported putting a Linux kernel binary inside
+one too, and created client tooling (like `docker`/`podman`) that understood
+how to use container images for in-place transactional (default stateful)
+operating system upgrades.
+
+With `bootc`, bootable operating systems can be created and deployed using all the same
+familiar tools and techniques one uses for *application* container images.