Revamp README with updated setup, installation, and module overview

Author: elevinskii

README.md

@@ -1,81 +1,32 @@
-# 991FuchsiaSnake
+# Order Bulk Manager
 
-Welcome to my Adobe I/O Application!
+Speed up order processing with our app that adds new mass actions for invoicing and shipment. Push multiple orders to
+the queue at once and let automated background processing handle the rest — saving time, reducing errors, and keeping
+your operations smooth.
 
-## Setup
+# Installation
 
-- Populate the `.env` file in the project root and fill it as shown [below](#env)
+Module compatible with both Adobe Commerce SaaS and PaaS.
 
-## Local Dev
+## Prerequisites
 
-- `aio app run` to start your local Dev server
-- App will run on `localhost:9080` by default
+- Node.js 20+
+- Adobe I/O CLI
 
-By default the UI will be served locally but actions will be deployed and served from Adobe I/O Runtime. To start a
-local serverless stack and also run your actions locally use the `aio app run --local` option.
+## Adobe Console preparation
 
-## Test & Coverage
+Go to [Adobe Developer Console](https://developer.adobe.com) and create a new project from the "App Builder" template.
+Adding a service "Adobe Commerce as a Cloud Service" is necessary for generating OAuth Server-to-Server credentials.
 
-- Run `aio app test` to run unit tests for ui and actions
-- Run `aio app test --e2e` to run e2e tests
+## Installation
 
-## Deploy & Cleanup
+- Clone the repository
+- Run `npm install` for installing dependencies
 
-- `aio app deploy` to build and deploy all actions on Runtime and static files to CDN
-- `aio app undeploy` to undeploy the app
+## Environment variables
 
-## Config
+- Rename default `env.dist` to `.env` for storing environment variables
 
-### `.env`
+### Adobe Commerce SaaS
 
-You can generate this file using the command `aio app use`. 
 
-```bash
-# This file must **not** be committed to source control
-
-## please provide your Adobe I/O Runtime credentials
-# AIO_RUNTIME_AUTH=
-# AIO_RUNTIME_NAMESPACE=
-```
-
-### `app.config.yaml`
-
-- Main configuration file that defines an application's implementation. 
-- More information on this file, application configuration, and extension configuration 
-  can be found [here](https://developer.adobe.com/app-builder/docs/guides/appbuilder-configuration/#appconfigyaml)
-
-#### Action Dependencies
-
-- You have two options to resolve your actions' dependencies:
-
-  1. **Packaged action file**: Add your action's dependencies to the root
-   `package.json` and install them using `npm install`. Then set the `function`
-   field in `app.config.yaml` to point to the **entry file** of your action
-   folder. We will use `webpack` to package your code and dependencies into a
-   single minified js file. The action will then be deployed as a single file.
-   Use this method if you want to reduce the size of your actions.
-
-  2. **Zipped action folder**: In the folder containing the action code add a
-     `package.json` with the action's dependencies. Then set the `function`
-     field in `app.config.yaml` to point to the **folder** of that action. We will
-     install the required dependencies within that directory and zip the folder
-     before deploying it as a zipped action. Use this method if you want to keep
-     your action's dependencies separated.
-
-## Debugging in VS Code
-
-While running your local server (`aio app run`), both UI and actions can be debugged, to do so open the vscode debugger
-and select the debugging configuration called `WebAndActions`.
-Alternatively, there are also debug configs for only UI and each separate action.
-
-## Typescript support for UI
-
-To use typescript use `.tsx` extension for react components and add a `tsconfig.json` 
-and make sure you have the below config added
-```
- {
-  "compilerOptions": {
-      "jsx": "react"
-    }
-  } 
-```