Improve dev onboarding and docs

CONTRIBUTING.md

@@ -14,14 +14,29 @@ git clone https://github.com/pyscript/pyscript.git
 pip install --upgrade pip
 ```
 
-Make a virtualenv and activate it:
+Create a local enviroment with your enviroment manager of choice.
+
+### Virtualenv
+
+In case you choose Virtualenv, make a virtualenv and activate it using the following commands:
 
 ```shell
 python -m venv .venv
 source .venv/bin/activate
 ```
 
-Install your local enviroment dependencies
+### Conda
+
+In case you choose to use conda, use the following commands:
+
+```shell
+conda create -n pyscript-cli python
+conda activate pyscript-cli
+```
+
+### Installation
+
+Now that you have your environment set up and activated, install your local enviroment dependencies
 
 ```shell
 pip install -e ".[dev]"
@@ -39,6 +54,37 @@ After setting up your developer enviroment, you can run the tests with the follo
 pytest .
 ```
 
+# Running CLI Commands
+
+Once the installation process is done, the `pyscript` CLI is avaible to be used once the environment has been
+activated. Simply run `pyscript` with the appropriate command. For instance, to see the list of commands:
+
+```shell
+>> pyscript --help
+
+ Usage: pyscript [OPTIONS] COMMAND [ARGS]...
+
+ Command Line Interface for PyScript.
+
+╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ --version          Show project version and exit.                                                                                                                    │
+│ --help             Show this message and exit.                                                                                                                       │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+╭─ Commands ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
+│ create  Create a new pyscript project with the passed in name, creating a new directory in the current directory. Alternatively, use `--wrap` so as to embed a       │
+│         python file instead.                                                                                                                                         │
+│ run     Creates a local server to run the app on the path and port specified.                                                                                        │
+╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
+```
+
+or, to run a pyscript app:
+
+```shell
+>> pyscript run
+Serving from /pyscript-example at port 8000. To stop, press Ctrl+C.
+127.0.0.1 - - [30/Apr/2025 17:01:03] "GET / HTTP/1.1" 200 -
+```
+
 ## Documentation
 
 ### Install the documentation dependencies
@@ -77,3 +123,60 @@ e.g.:
 ```shell
 make -C docs html
 ```
+
+
+## Creating a New Release
+
+To create a new release of pyscript-cli, follow these steps:
+
+1. Update the version number in `src/pyscript/version`
+
+2. Update CHANGELOG.md with the changes since the last release
+
+3. Create a new git tag matching the version number:
+   ```shell
+   git tag X.Y.Z
+   ```
+
+4. Push the tag to GitHub:
+   ```shell
+   git push origin X.Y.Z
+   ```
+
+5. The GitHub Actions workflow will automatically:
+   - Verify the tag matches the version in `src/pyscript/version`
+   - Run tests
+   - Build and publish the package to PyPI
+   - Create a GitHub release
+
+6. Verify the new version is available on PyPI: https://pypi.org/project/pyscript-cli/
+
+Note: Make sure all tests pass locally before creating a new release. The release workflow will fail if there are any test failures or version mismatches.
+
+Note 2: The version number in `src/pyscript/version` and the tag pushed to git (`X.Y.Z` in the example above) MUST MATCH! If they don't match the, the
+action to create and publish the release won't start.
+
+
+### How the Release Process Works
+
+The release process is automated through GitHub Actions workflows. Here's what happens behind the scenes:
+
+1. When a new tag is pushed, it triggers the release workflow
+2. The workflow first checks that:
+   - The tag name matches the version in `src/pyscript/version`
+   - All tests pass successfully
+
+3. If checks pass, the workflow:
+   - Builds the Python package using setuptools
+   - Creates source and wheel distributions
+   - Uploads the distributions to PyPI using twine
+   - Creates a GitHub release with the tag name
+
+4. The version check is performed by the `check_tag_version()` function in setup.py, which:
+   - Reads the version from `src/pyscript/version`
+   - Compares it to the git tag that triggered the workflow
+   - Fails if they don't match exactly
+
+5. The PyPI upload uses credentials stored as GitHub repository secrets
+
+This automated process ensures consistent and reliable releases while preventing common issues like version mismatches or failed tests from being published.