
If this sounds overwhelming, don’t worry. And how to use MAMP in the future with other sites you’d like to test.



When I first started coding, one of the things I struggled with most was figuring out my “set up.” I wanted to know how exactly programmers get their code online: Where do they write it? How do they transition between building a site and making it live? Where do all the files live? Where do you make edits if you want to change a file that’s already online? I didn’t know at the time, but my question was really: “How should I set up my coding environment?”
