# 2025 Installation instructions

## The problem

* Installations instructions are the first point of contact
* It makes or breaks week 2 of the course
* If installation instructions may not match how people usually work.
* If people see something that looks like what they do, they'll want to engage
* If they see something out of their world, they won't.

Other smaller problems:
- Many people ask "is this thing I am using now OK?" (we used to have a checker script but it wasn't fully reliable)

## The task

* Understand existing install instructions
* Collect list of possible install methods and advantages/disadvantages.
* Decide the recommended options for installing things
* (implementation can be later)

## Git
### Linux
* Package manager installation
### MacOS
* There by default
### Windows
* Must be installed, but there seems ot be one standard way to do it (git web page) - this is used by vscode and all.

## Command line /teerminal
### Linux
* There by default
### MacOS
* There by default
### Windows
* git prompt
* anaconda prompt
* VScode terminal

## Conda

### Linux
### MacOS
### Windows

## Other notes

### Operating-system specific notes

#### Linux
#### MacOS
#### Windows
- How to https://github.com/coderefinery/installation/issues/282

### How to introduce the terminal
We want to introduce learners to the concept of the terminal, while not scaring people away. We should make it clear to learners that terminal is not required, even if we secretly plan on introducing it.

- on day 2 one archaeology exercise needs a terminal
- by day 3 we can show some more terminal (even if not everyone uses it). "First demo" for future days
- On day 4 (reproducible) learners start to do things with the terminal themselves.
- VSCode's teriminal is a good way to introduce it: it avoids having to open some new program and "cd" to the right directory.