> For the complete documentation index, see [llms.txt](https://uci.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uci.sunbird.org/use/developer/development-environment/frontend-setup-admin-console.md).

# Frontend Setup (Admin Console)

### Your machine should have yarn or npm.

#### Note: Preferable versions

```
Version:
    node 12
    npm 6 
```

### Check the node and npm version by running the following commands.

```
    node -v
    npm -v
```

### Installation Steps:

#### 1. Fork it

You can get your own fork/copy of Frontend by using the Fork button.

#### 2. Clone it

You need to clone (download) it to a local machine using git clone <https://github.com/samagra-comms/uci-admin.git>

Once you have cloned the uci-admin repository in GitHub, move to that folder first using the change directory command.

This will change directory to a folder

```
 cd uci-admin
```

Move to this folder for all other commands.

#### 3. Set it up

Run the following commands to see that your local copy has a reference to your forked remote repository in GitHub

```
git remote -v
```

By running the above command, you can see that the local copy has a reference to the forked remote repository in GitHub.

```
origin    https://github.com/samagra-comms/uci-admin.git (fetch)
origin    https://github.com/samagra-comms/uci-admin.git (push)
```

#### 4. Run it

#### Install dependencies

```
npm install
```

#### 5. Build

```
ng build –prod
```

Build @dist

#### Run frontend application in dev environment

```
ng serve
```

Browse - <http://localhost:4000>

Run standalone module in dev environment


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://uci.sunbird.org/use/developer/development-environment/frontend-setup-admin-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
