> For the complete documentation index, see [llms.txt](https://codecall.gitbook.io/code-call/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codecall.gitbook.io/code-call/engineers-docs/quick-start.md).

# Quick Start

Welcome to Code Call! Here's a quick and easy guide to get you started as a competitive developer and create your first submission

### 1. Account Setup

First, visit [app.codecall.xyz](https://codecall.gitbook.io/code-call/engineers-docs/www.codecall.xyz) and click connect with GitHub in the top right corner to login with your account directly and have a wallet automatically generated for you, you should see your github name at the top once you logged in:

<figure><img src="/files/KGpPGx09D6UBrVFPnBhP" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/kA3mrFLkvHpdbjOkJtcs" alt=""><figcaption></figcaption></figure>

### 2.Enter your first project

Navigate to the projects page and look for "Live" projects or alternatively navigate to the junior projects to practice:

<figure><img src="/files/lTKSaUvjoR58xlbVrGoL" alt=""><figcaption></figcaption></figure>

```html
> 📝 Don't want to miss any of our project announcements??
> Make sure to follow us on Twitter and join our Discord server!
> Sign up on our mailing list
```

Clicking on a project will open its details page, with important information such as:

* [Prize pool ](/code-call/engineers-docs/payouts.md)development reward breakdowns.
* Start and end dates.
* Scope and development tasks.
* Scoring.
* Link to the GitHub repository (if the competition is live).
* Language.
* How To Guide.

TODO: Add Photo Here of project screen

Every contest also comes with details that will help you understand:

* The codebase
* Scope
* Compatibilities
* How to get the codebase up and running

New projects are added regularly. \
When you find a project that fits your skills, click on the "participate" button to join it:

TODO: ADD PICTURE OF PARTICIPATE BUTTON IN COMPETITIONS SCREEN

### 3. Submit your first task

Once you've completed your first task navigate to the project page, and click on the "submit" button:

TODO: PHOTO OF SUBMIT BUTTON IN PROJECT SCREEN

To submit your task, you'll be asked to insert:

* Title - a <250 character descriptive title of your submission.
* Contribution Type - The type of contribution you are submitting: Feature, Optimization, Bug Fix Read [How to Evaluate Contribution Type](/code-call/engineers-docs/how-to-evaluate-contribution-type.md) for a full explanation.
* Description - a detailed description of your contribution:\
  **Bug**: Document the effects of the bug and how to reproduce it as well as your fix.\
  **Feature**: Describe the feature you are implementing and how it aligns with the project tasks.\
  **Optimization**: Describe which part of the code you are optimizing and the effect of it optimization.

Learn more on [How To Present Your Contributions](/code-call/engineers-docs/how-to-present-your-contributions.md) on the dedicated guide.

### 4. Awaiting reviewer Results

**After the project ends, reviewers will evaluate each submission carefully to determine its validity and overall quality.**

**reviewers is done in two steps:**

* [**reviewers** ](/code-call/reviewer-docs/the-reviewing-process.md)- a period where all [eligible reviewers](/code-call/reviewer-docs/reviewing-eligibility.md) can evaluate others' submissions.
* [Finalization](/code-call/businesses/assessment-process.md) - a period where a lead reviewer, reviews the submissions approved by his fellow colleagues and present a document to the business for review.

Learn more about [the reviewer process](/code-call/reviewer-docs/the-reviewing-process.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://codecall.gitbook.io/code-call/engineers-docs/quick-start.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.