move demo files to demo

.gitignore

@@ -128,3 +128,4 @@ dmypy.json
 _output/
 cockle_wasm_env/
 cockle-config.json
+demo/dist

README.md

@@ -50,11 +50,12 @@ jupyter lite build
 
 If you would like to deploy a JupyterLite site with the terminal extension, you will need to configure your server to add the `Cross-Origin-Embedder-Policy` and `Cross-Origin-Opener-Policy` headers.
 
-As an example, this repository deploys the JupyterLite terminal to [Vercel](https://vercel.com), using the following files:
+As an example, this repository deploys the JupyterLite terminal to [Vercel](https://vercel.com), using the following files in the `demo` folder:
 
 - `vercel.json`: configure the COOP / COEP server headers
 - `requirements-deploy.txt`: dependencies for the JupyterLite deployment
 - `deploy.sh`: script to deploy to Vercel, using micromamba to have full control on the Python versions and isolate the build in a virtual environment
+- the `contents` directory contains a couple of demo files to try some commands such as `grep`, `echo` and `lua`
 
 For more information, have a look at the JupyterLite documentation: https://jupyterlite.readthedocs.io/
 

deploy.sh → demo/deploy.sh

@@ -22,4 +22,4 @@ python -m pip install -r requirements-deploy.txt
 
 # build the JupyterLite site
 jupyter lite --version
-jupyter lite build --contents demo/contents --output-dir dist
+jupyter lite build --contents contents --output-dir dist

requirements-deploy.txt → demo/requirements-deploy.txt

@@ -1,4 +1,4 @@
 jupyterlab~=4.2.5
 jupyterlite-core
 jupyterlite-pyodide-kernel
-.
+..