Ideally you'd want to create a website which demonstrates your use of different functionality. - Show that you know how to output a HTML page using <?php ?> tags amongst the HTML itself. IMO it shows that you know this is possible. Also show clever little things like crossing between HTML and PHP preprocessing:[quote]<ul> <?php foreach($arr as $e){ ?> <li><?php echo $e; ?></li> <?php } ?> </ul>[/quote] - Demonstrate some AJAX request/response code in Javascript and PHP. - Show that you know how to mitigate threats like XSS. - Demonstrate database connectivity and data retrieval. - Show how to define a final class which inherits from an abstract class which also inherits from an abstract class and implements at least 3 predefined PHP interfaces. - Show how to publish and consume a web service using REST (eg. JSON) and SOAP. - Show how to perform some B2B functionality, likely in conjunction with the above point, with cURL. - Show some regex. - Show buffering. Something I like to do is to turn on buffering at the start of a script, use a single variable which contains everything I'm going to send to the client, then turn off buffering and serialise the object/variable. This is also handy when you want to catch any errors from being reported (especially when you can't turn them off). - Something clever I like to do is post-processing. I do it something like this:[quote]- Turn on buffering - Collect output in variable(s) - Turn off buffering - Output a Content-Length header with the size (strlen) of the variable(s) - Output the variables - Turn buffering back on - Do any post-processing you want to do[/quote]The trick here is that browsers will only keep reading from the socket/stream from the server up until the Content-Length is reached. Turning buffering on again after outputting the header is just a safeguard against accidentally showing something that shouldn't be and any clients (including non-browsers) who want to keep reading after the length is reached. - Demonstrate some obscure low-level stuff like direct HTTP manipulation, socket connectivity, OS calls (try backticks!). You'll be unlikely to use this stuff, but knowing it will probably be advantageous.