or... "Ok, now what?"
Custom post types and custom taxonomies may come with "surprise" archive pages
Also... don't forget these special pages:
WordPress is extremely customizable
*We'll get to this in a bit
This is super important.
"Does anybody know where I left my website?"
"Supos belusi buggerup..."
*My personal opinion is that you should never rely on a thing to backup or restore itself
* I like to use offsite storage like Amazon S3 for media uploads. Then, with proper version control for code files, the only thing left to backup is the database
*No but really, this works in a pinch. And you should be manually checking the automated backups anyways. You are checking your backups, right?
See my Introduction to git and WordPress presentation
git add . && git commit -a -m "first commit"
VVV is a tool built to facilitate development on multiple wordpress websites from one vagrant virtual server
Start here if you're not comfortable with a command line yet
I prefer to use staging for testing changes that were made in a development environment on my own computer, but if you're going with the "another copy of the site" method, this can be an easy way to do it.
This is really not ideal — mistakes can easily leave your website broken or your changes lost. And everybody makes mistakes.
This method is safer and gives a process for undoing mistakes. However it has some drawbacks too... especially if you're using an asset builder like Grunt