For instance, it would be nice if the data in the left column, 'Beauty Tips', could be different for each page. There are several ways to solve this, but for know I will choose the simplest.

He takes a few steps to make adding the content simple:

• Adding markers for the title and left menu to the template
• Change the OutputHandler class to make it less static
• use setData() to title the page
• user setData() to add left column content
• Use mark() and endmark() to section off a part of the template.

He's provided a demo and made the source code available for download.

A lot of the content on reviewsBy.us and other sites we make using symfony have dynamic content. We try to have our page titles reflect the content by prepending the name of the specific restaurant, document or menu item before the site name.

Their path to the prize is a method, prependTitle that's included in a class (myActions.class.php) and used via it's reference in the application's app.yml file.

I thought of something that would be both, easy to implement and easy to use. What I finally came up with is tightly coupled to my new url system that I'm using, so make sure to check it out in case you've missed it.

The basic idea of the system is that the URL of the page (made up partly of the title) would be the unique identifier for the page. For example, "[page 12]" would be expanded out to "/pages/12:my-title". Felix takes this idea and runs with it, showing how to implement it in a CakePHP project inside of a Model and a Component. The sample usage code is, of course, also included in the post.

In the second, Felix demonstrates how, with some simple if logic, you can simulate dependencies. His examples include a simple if to check for the return of "true" from various functions and an inline example of an svn export and FTP.

Now, on to what we need from you - we'd prefer the information to be as concise as possible. Cut and paste of a full listing isn't the way to go here. We'd prefer the summary of the position with a link to more details.

Here's the key info we'd like:

• Company Name
• Position title
• Position location
• Summary description of the position
• A link to more information on it (on Monster, Hotjobs, your site, etc.)

To submit your job information, send it along to jobs@phpdeveloper.org and we'll get it posted and include the phrase "JOB POSTING" somewhere in the subject line. Since this will start off as a weekly thing, you'll need to wait until Friday to see the information show up.