For a long time ago, I believed "anchors" were the way to go. I used the Smarty templating engine in those days. Do yourself a favor, and skip that phase. You see... soon you'll find you'll need some basic control structures in your pages. A little loop here, a small conditional there. Before you know it, you'll be implementing your own little programming language just to parse those anchors.
That's when it begins to dawn that PHP is actually a mighty fine templating language. This is the approach many frameworks these days have taken. I'd recommend taking a look at Zend Framework's Zend_View. They do a nifty little thing where they use output buffering to catch the result of a PHP page being included. This allows them interesting stuff like assigning data to an object and retrieving it using $this-> in the template.
What it boils down to is what you want to do in your pages... seperation of concerns, that is, splitting your 'presentation' from your business logic, is pretty much always a good idea. And if you restrict yourself to presentation logic, it naturally follows that your pages will contain only the PHP you really need. As mentioned above.. a while loop, a few If's. That should be it.
See also: MVC pattern