Not so much a matter of being converted, as finding the proper tool for the job. I used to have this argument all the time with users when I was a systems architect. A user will read something about something, and want to design a system around it. Usually, it wasn't an appropiate use for that particular something. I also had the opposite problem when I would specify a specific language or piece of equipment for an application because it was (better, faster, cheaper - pick any two), and would have to deal with people who wanted to do it the way they always did it.
If I was still working professionally in IT, I would have no problems with converting HTML pages to PHP. No reason not to do so now, especially since I am effectively dealing with the same problems - cost of maintenaince, flexability, and expansion.
I have to hit Amazon and get a couple of primers on PHP and probably within a couple of weeks, I'll be able to solve problems on here, too
Frank