Question about hashing passwords with PBKDF2
The example seemed to show what I needed to do as far as hashing and
  salting my passwords, but I was concerned with using a colon to create
  a split between the iterations, salt, and password.
  
  Wouldn't that just give clues to someone who would try to hack my
  database as to how I was hashing my passwords?


The security only has to come from the algorithm and the key used, keeping the algorithm or its parameters secret should not be necceasary. That is the principle of Kerckhoff, on of the pillars of modern cryptography. 
This means in consequence, that since you are using an algorithm considered secure, it is no problem to show the public parameters to an attacker.


  Also, I am open to hearing others thoughts on which algorithm I should
  be using because there is a lot of information out there and it seems
  like there is nothing conclusive as to which one is the best.


PBKDF2 is fine, but it is not as resilient to attacks with specialised hardware as other schemes. SCrypt is the most well established such algorithm. Another scheme worth mentioning is Argon2. It is the recent winner of the academic Password hashing competition, but due tp its newness it is not as widely used (and implemented) as SCrypt.