_s2 = md` ### Step 2: Open the code in Glitch Okay, now you have your own repo - how do you run this code and add your own changes? Glitch to the rescue! For this workshop, we will be using [Glitch](https://glitch.com/) to code and make our changes. Glitch is a website where you can share your own web projects with other people, and remix other people's projects. However, normally you will be doing this on your own computer. Setting up git/running code our your own computer can get messy and complicated, so we decided to use Glitch to abstract that all away. In the future, we’ll help you get your computer setup so you won’t have to always use Glitch! To get started, click this button: ${html`

`} Now, in a new tab, an empty Glitch project has opened up, and looks like this: ${picWithSubtitle(assests.glitch_new, 'Your first (empty) Glitch project!')}
Now, let's open up a terminal so that way we can get our code into this Glitch project! #### What is a terminal? The "terminal" (console, command line, bash, shell, etc.) is a tool you use to more efficiently interact with code, scripts, and your computer. Don't worry if you've never used a terminal before - we'll walk you through it! To open up the terminal (called "console" in Glitch), go to the top left options -> Advanced Options -> Open Console. In a new tab, the "console" will open like: ${picWithSubtitle(assests.glitch_terminal, 'The "terminal" in Glitch!')}
Now, in this terminal, you are inside a **directory**, or, a folder. Inside this directory is just other files (could be .txt files, .pdf, whatever) and other directories. In a terminal, to see what files are inside your current directory, run the command \`ls\` (stands for "list contents") like so: ${Terminal(['ls', '!outputnode_modules package.json README.md server.js shrinkwrap.yaml'], glitchStyle)}
These are the "contents" of the directory! \`node_modules\` is a directory, \`package.json\`, \`README.md\`, \`server.js\`, and \`shrinkwrap.yaml\` are all files! You can ignore all of these, these have nothing to do with our graffiti wall. Before we do anything with git, you have to tell git who you are! Run these commands below, replacing with your own name and email address (use the same email that you used to sign up for GitHub)! ${Terminal(`git config --global user.email "you@example.com" git config --global user.name "Your Name"`.split('\n'), glitchStyle)}
Now, we want to **clone** your forked repo - meaning we want to get your code from GitHub into this directory. To do that, you will run: ${Terminal([`git clone https://github.com/${_username}/graffiti-wall.git`],glitchStyle)}
You'll get some output like: ${ Terminal( `Cloning into 'graffiti-wall'... remote: Enumerating objects: 35, done. remote: Total 35 (delta 0), reused 0 (delta 0), pack-reused 35 Unpacking objects: 100% (35/35), done. Checking connectivity... done.`.split('\n').map(s=>`!output${s}`) ,glitchStyle) }
Now, if you \`ls\` again, you'll see a new directory called \`graffiti-wall\` has been created - thats your repo, thats where your code is! ${Terminal([ 'ls', '!outputgraffiti-wall node_modules package.json README.md server.js shrinkwrap.yaml' ] ,glitchStyle)}
Now, before we go back to the nicer looking part of glitch, run the \`refresh\` command so glitch knows you just added some files: ${Terminal(['refresh', '!outputrestarting...'],glitchStyle)} `