Removed legacy --config in readme and updated developing folder for learn

Author: NorOldBurden

README.md

@@ -109,16 +109,34 @@ The following blockchain libraries (generated by Telescope) are available via np
 
 ## Quickstart
 
-Follow the instructions below to generate a new Typescript package that you can publish to npm.
+Follow the instructions below to generate a new Typescript package that you can publish to npm. You can also follow the video: https://youtu.be/iQf6p65fbdY
 
-First, install `telescope` and `create-cosmos-app`
+First, install `telescope` 
+```sh
+npm install -g @cosmology/telescope
+```
 
+then install either
+
+`create-interchain-app`
 ```sh
-npm install -g @cosmology/telescope create-cosmos-app
+npm install -g create-interchain-app
+```
+Or
+`create-cosmos-app`
+```sh
+npm install -g create-cosmos-app
 ```
 
 ### Generate
 
+Use the [`create-interchain-app`](https://github.com/hyperweb-io/create-interchain-app/) command to create a new package from the `telescope` boilerplate.
+
+```sh
+cia --boilerplate telescope
+
+or 
+
 Use the [`create-cosmos-app`](https://github.com/hyperweb-io/create-cosmos-app/) command to create a new package from the `telescope` boilerplate.
 
 ```sh
@@ -127,87 +145,23 @@ cca --boilerplate telescope
 
 Then, you'll navigate into `./your-project/packages/telescope` package for the next steps.
 
-You can also use `telescope generate` command to generate package according to the prompt or terminal command params such as:
-`telescope generate --access public --userfullname testname --useremail [email protected] --module-desc test --username salkfl --license MIT --module-name test --chain-name cosmos --use-npm-scoped`
-
-The available options are:
-`--userfullname` `--useremail` `--module-desc` `--username` `--module-name` `--chain-name` `--access` `--use-npm-scoped` `--license`
-
 If some required options are missing, it will prompt to ask for the info.
 
-To be noted, `--use-npm-scoped` only works when `--access` is `public`
+For detailed cli `generate` commands, please check our docs and learn directories.
 
-### Download protos with CLI
+### Download protos 
 
 The old ` telescope install ` command has been deprecated
 
-You can use our CLI to download protos by using `download` command.
+You can use our script to download protos by using `download-protos`command in the boilerplate.
 
 ```sh
-telescope download
+yarn download-protos
 ```
 
 You should now see some repos cloned in `./git-modules` and proto files generated in `./protos`. These are the proto files downloaded according to your config.
 
-Examples:
-
-```sh
-# Telescope will do the download according to .json file of --config
-# Telescope will put proto into location specified by --out
-telescope download --config ./protod.config.json --out ./git-modules
-```
-
-```sh
-# Telescope download from target repo according to --git-repo
-# in format of (i.e. <owner>/<repository> or <owner>/<repository>/<branch>)
-# <branch> can be empty, it will use main as default
-# Also --targets is required to specify the targets to download
-# in format like cosmos/auth/v1beta1/auth.proto
-telescope download --git-repo target-repo --targets target-proto
-```
-
-```sh
-# ssh arg is optional, default is false
-telescope download --config ./protod.config.json --out ./git-modules --ssh true
-```
-
-
-```js
-// .protod.config.json example
-//
-// `repos` are the repository it's going to clone
-// in format of (i.e. { "owner": <owner>, "repo": <repo> } or { "owner": <owner>, "repo": <repo>, "branch": <branch> })
-// <branch> can be empty, it will use main as default
-//
-// `protoDirMapping` is the directory of repo specified if the proto is not under repo's root directory ./protos
-// in format of (i.e. <owner>/<repository> or <owner>/<repository>/<branch>)
-// <branch> can be empty, it will use main as default
-//
-// `outDir` is where the output proto will be put
-//
-// `targets` are the target proto to download
-// `targets` can be patterns like:
-// "cosmos/bank/v1beta1/tx.proto",
-// "cosmos/gov/**/*.proto",
-// "cosmos/authz/**/*.proto",
-{
-  "repos": [
-    { "owner": "cosmos", "repo": "cosmos-sdk" },
-    ...
-  ],
-  "protoDirMapping": {
-    "gogo/protobuf/master": ".",
-    ...
-  },
-  "outDir": "protos",
-  "ssh": true,
-  "tempRepoDir": "git-modules",
-  "targets": [
-    "cosmos/auth/v1beta1/auth.proto",
-    ...
-  ]
-}
-```
+For detailed cli `download` commands, please check our docs and learn directories.
 
 ### Transpile
 
@@ -217,56 +171,6 @@ To create the Typescript files for your chain, run the `yarn codegen` command in
 yarn codegen
 ```
 
-### Transpile with CLI
-
-Less recommended, but you can also use our CLI for transpilation. To create the Typescript files with the `cli`, run the `transpile` command.
-
-```sh
-telescope transpile
-```
-
-You should now see some `.ts` files generated in `./src`. These are the real source files used in your application.
-
-Examples:
-
-```sh
-# Telescope takes chain1 folder as input,
-# and generate files in 'gen/src' folder.
-telescope transpile --protoDirs ../../__fixtures__/chain1 --outPath gen/src
-```
-
-```sh
-# Telescope takes chain1 folder as input,
-# and generate files in 'gen/src' folder using default telescope options.
-telescope transpile --protoDirs ../../__fixtures__/chain1 --outPath gen/src --useDefaults
-```
-
-```sh
-# Telescope takes chain1 folder(from args) and chain2 folder(from config) as input,
-# and generate files in 'gen/src'(defined in the config file, will override outPath in args) folder using a config file.
-# Note: --config will override --useDefaults.
-telescope transpile --protoDirs ../../__fixtures__/chain1 --config .telescope.json
-```
-
-```sh
-# Telescope takes more than one config. The config afterward will override those in front. In this case values in .telescope-ext.json will override those in .telescope.json.
-telescope transpile --config .telescope.json --config .telescope-ext.json
-```
-
-```js
-//.telescope.json
-{
-  "protoDirs": [
-    "../../fixtures/chain2"
-  ],
-  "outPath": "gen/src",
-  "options": {
-    // telescope options
-    ...
-  }
-}
-```
-
 ### Build
 
 Finally, run `install` and `build` to generate the JS and types for publishing your module to npm.