update readme

Author: emrberk

README.md

@@ -2,105 +2,73 @@
 
 This repository hosts the implementation of QuestDB user interface and surrounding tooling.
 
-## Local development setup
+## Prerequisites
 
-In order to start working with this repo, you first need to clone and bootstrap it.
+- **Node.js** >= 18.18.0 (check with `node -v`)
+- **Yarn** 4.1.1+ (check with `yarn -v`)
 
-It is a simple process! Follow these steps:
-
-1. Clone the repository
-2. Bootstrap dependencies
-3. Run command
-4. Hack!
-
-Each step is described in below.
-
-### 1. Clone the repository
-
-There are few ways to clone a repository. Check [Github docs](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) if you need help.
-
-- Clone this repository using SSH:
-
-  ```
-  git clone git@github.com:questdb/ui.git
-  ```
-
-- or HTTPS:
-
-  ```
-  git clone https://github.com/questdb/ui.git
-  ```
-
-- or with [Github CLI](https://cli.github.com/):
-  ```
-  gh repo clone questdb/ui
-  ```
-
-### 2. Bootstrap dependencies
-
-#### `node` and `yarn`
-
-First make sure you have `node` and `yarn` and that their versions are compatible with this project.
-This is a common source of issues, best not to skip this step:
-
-- `node -v` should return a version compatible with what's in [.nvmrc](../.nvmrc)\
-  If it doesn't, you can use [fnm](https://fnm.vercel.app) or [nvm](https://github.com/nvm-sh/nvm) to manage node versions on your machine.\
-  Then run `fnm use` or `nvm use` to set correct version.
-
-- If `yarn -v` returns `command not found`, enable `yarn` by running `corepack enable`.\
-  Follow [official installation guide](https://yarnpkg.com/getting-started/install) if you have trouble.
-
-#### Bootstrap
-
-Simply run `yarn` to bootstrap.
-
-### 3. Run command of a package
-
-Congrats, the setup is done! You're ready to start working on web console.
-
-```
-yarn $script
+If your Node.js version doesn't match, use [fnm](https://fnm.vercel.app) or [nvm](https://github.com/nvm-sh/nvm) to switch versions:
+```bash
+fnm use  # or nvm use
 ```
 
-where `$script` is one of the scripts defined in `package.json` file.
-
-- You can start web console development server with:
-
-```
-yarn start
+If Yarn is not installed, enable it with:
+```bash
+corepack enable
 ```
 
-[localhost:9999](http://localhost:9999) should display the web console.
+## Quick Start
 
-- You can run unit tests using:
+1. Clone the repository:
+   ```bash
+   git clone git@github.com:questdb/ui.git
+   cd ui
+   ```
 
-```
-yarn test:unit
-```
+2. Install dependencies:
+   ```bash
+   yarn
+   ```
 
+3. Start the development server:
+   ```bash
+   yarn start
+   ```
 
-- You can run e2e tests using:
+4. Open [http://localhost:9999](http://localhost:9999) in your browser. Note that for Web Console to work properly, [QuestDB server](https://github.com/questdb/questdb) should be up and running.
 
-```
-yarn test:e2e
-```
+## Available Scripts
 
-Note that you need to run QuestDB server for testing web console.
-There are useful scripts
+- `yarn start` - Start development server (Vite)
+- `yarn build` - Build for production
+- `yarn preview` - Preview production build locally
+- `yarn test:unit` - Run unit tests (Vitest)
+- `yarn test:e2e` - Run end-to-end tests (Cypress)
+- `yarn test:e2e:auth` - Run auth-specific e2e tests
+- `yarn test:e2e:enterprise` - Run enterprise e2e tests
+- `yarn typecheck` - Run TypeScript type checking
+- `yarn lint` - Lint source code (ESLint)
+- `yarn lint:fix` - Fix linting issues automatically
 
-### 4. Hack!
+## Development Notes
 
-The setup is done! 
+### Running E2E Tests
 
-If you need help, here are some useful links:
+E2E tests require a running QuestDB server. The tests connect to `localhost:9000` by default.
 
-- [GitHub issues](https://github.com/questdb/ui/issues), might already have an answer to your question
-- [QuestDB Documentation](https://questdb.com/docs/) includes a lot of useful information
-- [QuestDB Slack Channel](https://slack.questdb.io/) and [QuestDB Community Forum](https://community.questdb.io/): join our helpful community!
+### Working with Context Path
 
+To test with a custom context path:
+```bash
+QDB_HTTP_CONTEXT_WEB_CONSOLE=/context yarn preview
+```
 
 ## Contributing
 
 We always welcome contributions from the community!
 
-Please, read our [local development setup](./docs/local-development-setup.md) document to learn how to get started.
+If you need help, here are some useful links:
+
+- Check [GitHub issues](https://github.com/questdb/ui/issues) for existing discussions
+- Read the [QuestDB Documentation](https://questdb.com/docs/)
+- Join our [Slack Channel](https://slack.questdb.io/) or [Community Forum](https://community.questdb.io/)