diff --git a/README.md b/README.md
index 0883fcfa36f9..6b875507015c 100644
--- a/README.md
+++ b/README.md
@@ -101,18 +101,28 @@ Before running or contribute to this project, you need to have the setup of the
npm run build
```
+
+
## Packages
-| Package name | Docs | Version |
-| :------------- | :------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------- |
-| `Appstore` | [](packages/appstore/README.md) | - |
-| `Bot` | [](packages/bot/README.md) | - |
-| `Components` | [](packages/components/README.md) | - |
-| `Core` | [](packages/core/README.md) | - |
-| `P2P` | [](packages/p2p/README.md) | [](https://www.npmjs.com/package/@deriv/p2p) |
-| `Shared` | [](packages/shared/README.md) | - |
-| `Trader` | [](packages/trader/README.md) | - |
-| `Translations` | [](packages/translations/README.md) | - |
+| Package name | Docs | Version |
+| :------------- | :------------------------------------------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------- |
+| `Account` | - | - |
+| `Appstore` | [](packages/appstore/README.md) | - |
+| `Bot-skeleton` | [](packages/bot-skeleton/README.md) | - |
+| `Bot-web-ui` | [](packages/bot-web-ui/README.md) | - |
+| `Cashier` | [](packages/cashier/README.md) | - |
+| `Cfd` | [](packages/cfd/README.md) | - |
+| `Components` | [](packages/components/README.md) | - |
+| `Core` | [](packages/core/README.md) | - |
+| `Indicators` | [](packages/indicators/README.md) | - |
+| `P2P` | [](packages/p2p/README.md) | [](https://www.npmjs.com/package/@deriv/p2p) |
+| `Publisher` | [](packages/publisher/README.md) | - |
+| `Shared` | [](packages/shared/README.md) | - |
+| `Trader` | [](packages/trader/README.md) | - |
+| `Translations` | [](packages/translations/README.md) | - |
+
+
## Working With This Repo
@@ -134,9 +144,11 @@ All packages must contain the following scripts to perform the stated actions:
[comment]: <> (| ❌ | `deploy:clean` | Runs `build` script, clears `gh-pages` branch, then pushes the output to GH Pages. |)
[comment]: <> (| ❌ | `deploy:folder` | Runs `build` script, then pushes the output to the specified folder in GH Pages. |)
-**Please follow the README of each package you intend to work with on how to get set up and their custom scripts.** However, the above scripts can be run from the root directory in the following manner.
+**Note: Please follow the README of each package you intend to work with on how to get set up and their custom scripts.** However, the above scripts can be run from the root directory in the following manner.
+
+
-### Package names
+## Package names
Each package is named with the `@deriv/` prefix, however for the scripts above, you do not need to add the `@deriv/` prefix as the scripts already prefix the 1st argument of the script with `@deriv/`. **However**, if you do use the `lerna` CLI directly, then you will need to use the full package name including the `@deriv/` prefix.
@@ -144,7 +156,7 @@ You can find the names of packages by first navigating to the `packages` folder.
### Usage
-#### Configuring Hosts file
+### Configuring Hosts file
In order to run our solution for the first time, you need to configure your `hosts` file:
@@ -153,7 +165,7 @@ In order to run our solution for the first time, you need to configure your `hos
3. Add a new entry pointing to `127.0.0.1 localhost.binary.sx`.
4. Save the file and proceed to the next step.
-#### Starting a Development Server
+### Starting a Development Server
If you wish to work on Core, simply run `npm run serve core`.
@@ -163,7 +175,9 @@ But for working on any of the other packages (such as Trader, Bot, P2P), perform
2. Run `npm run serve {package name}` in the first one. e.g.: `npm run serve translations`, `npm run serve bot`, etc.
3. Then run `npm run serve core` in the second one.
-#### How to Clean Packages
+
+
+### How to Clean Packages
If you intend to remove `node_modules` folder(s) from the projects, please run `npm run clean` from the root of the project.
@@ -172,7 +186,13 @@ You can read more on the various lerna commands (and the [`clean` command](https
**Note**: In case of facing permission denied error, please simply run `sudo chown -R $(whoami) .` from the root of the project.
-#### Examples of Script Usage
+### How to clear cache
+
+`npm cache clean -f`
+
+
+
+### Examples of Script Usage
If a script supports the "Package param", you can supply a `{package name}` for it to run the script in. At the moment, only 1 package name can be given to a script, if you wish to run in multiple, please use the `lerna` command that's used under the hood as per its docs.
@@ -190,7 +210,9 @@ npm run test:stylelint trader
[comment]: <> (❌ Below command will not work as the script `deploy:clean` does not support "Package param" \(refer to the table in [Working With This Repo]\(#working-with-this-repo\)\): `bash npm run deploy:clean bot`)
-#### Release
+
+
+## Release
There are 2 types of release:
@@ -207,6 +229,8 @@ There is a 4th type of release: releasing npm registry packages (currently `@der
2. Ensure you have a new (bumped) version of publishable packages (currently `@deriv/p2p`).
3. Run `npm run publish:p2p`. The command publishes all bumped packages. However, right now the name includes the word `p2p` to signal the WIP status and that P2P is the only published package under this repo.
+
+
## PR Guidelines
1. Use the `developer 1|developer 2/task_name` format for PR titles. (e.g.: `dev1|dev2/fixed_emoji_issue`, `dev1/added_superfast_jellyfish`)
@@ -214,6 +238,8 @@ There is a 4th type of release: releasing npm registry packages (currently `@der
2. Use the appropriate package labels available on the repo to indicate which packages your PR modifies.
3. Use Draft PRs if you don't mean to request for reviews yet. [Read more here.](https://github.blog/2019-02-14-introducing-draft-pull-requests/)
+
+
## Test link deployment
There are two types of test link deployment preview:
@@ -230,6 +256,8 @@ If preferable to use manual deployment, you can use [gh-pages](https://pages.git
- You can clean (remove `br_` folders and clear root\) your `gh-pages` branch and deploy to root in a single command with `npm run deploy:clean`
- You can deploy to a folder in your `gh-pages` branch in order to separate from root app deployment and other folder deployments with: `npm run deploy:folder br_test_folder` (folder name must be prefixed with `br_`))
+
+
## FAQ
1. How do I **install** an npm package in one of our packages?
@@ -260,3 +288,8 @@ If preferable to use manual deployment, you can use [gh-pages](https://pages.git
1. First run `npx lerna exec -- npm rebuild node-sass` and try building your packages again.
2. If that doesn't work, try `npm cache clean --force`, followed by `npm run clean`, and then `npm run bootstrap`.
3. And finally, if that doesn't work then you can read deeper into this [StackOverflow post](https://stackoverflow.com/questions/37986800).
+
+6. How can I regenerate `package-lock.json` file?
+
+ We have added `bootstrap:dev` to scripts. If you are updating or adding a package and you want to regenerate `package-lock.json` file, you should run this command
+ `npm run bootstrap:dev`
diff --git a/docs/JavaScript/README.md b/docs/JavaScript/README.md
index c43616328e33..1b0f67262711 100644
--- a/docs/JavaScript/README.md
+++ b/docs/JavaScript/README.md
@@ -137,6 +137,16 @@ React.useEffect(...);
- Use `{condition && ...}` syntax to conditionally render an element.
- Use ``; just use ``.
- Always name your components before default exporting them, for example:
diff --git a/docs/Modules/README.md b/docs/Modules/README.md
index 8cba0304f483..c507a6a65cf0 100644
--- a/docs/Modules/README.md
+++ b/docs/Modules/README.md
@@ -4,3 +4,6 @@ In order to create and add a new package to this project/repo, please follow the
1. Make sure your new package name is prefixed with `@deriv/`.
2. Make sure the Webpack config has `IS_RELEASE` flag, as well as conditional source-maps based on "if IS_RELEASE".
+3. To link the new package with the previous packages that we already have, you need to run `npm run bootstrap:dev` to link it with the others.
+4. Make sure your webpack configs are working as expected.
+5. You need to install the newly created package inside core package or other packages that need access to its store, components, etc.
diff --git a/docs/README.md b/docs/README.md
index 4fe9afff52e3..d58193f97007 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -22,6 +22,7 @@ There are 2 types of dependencies:
- `@deriv/bot-skeleton`
- `@deriv/bot-web-ui`
- `@deriv/cashier`
+ - `@deriv/cfd`
- `@deriv/p2p`
- `@deriv/trader`