php[architect] magazine has released their first issue of 2017 with their January edition - Blueprints for Success.

Happy New Year, dear reader! Let’s get ready to take on the challenges of the next 12 months. As always, a new year brings a sense of a “fresh slate” for our personal and professional goals. This month, we’ve collected articles that will help you in planning before you dive into your code editor.

Articles in this month's edition include:

• "Mirror, Mirror on the Wall: Building a New PHP Reflection Library" (by james Titcumb)
• "Writing Better Code with Four Patterns" (by Joseph Maxwell)
• "Capturing an API’s Behavior With Behat" (by Michael Heap)

...and, of course, the columns you know like "Education Station" and "Community Corner". You can find out more about these articles and columns on this page for the issue and pick up a copy of your own.

Padraic Brady has posted part four today detailing his development process for a piece of blogging software with the Zend Framework. This part focuses on the design stage of the application.

In this article we're going to take a stab at setting up a default blog style, using some filler content, and finally capturing the design with a Zend_View template to be consumed by Zend_Layout as a common HTML Layout for the entire future blog.

He uses the Blueprint CSS framework for his projects, a simple system that helps you lay out pages it a bit more sensible fashion without having to worry about the underlying CSS so much. He shows how to integrate the library into his project and gives some sample HTML to style with it. Then, with a little help from the Zend_Layout component, he splits it up into a layout that can be used over the entire website (code included).

From the Zend Developer Zone today, there's the continuation of their "Blueprint for PHP Applications" series, this time focusing on bootstrapping (part 1).

The definition (of bootstrapping) from Wikipedia has more flair to it than I can probably give this article, but nonetheless bootstrapping is an incredibly important part of a PHP web application. It is the ignition, the launch-pad, the booster rockets, and even the safety gear for our trip through PHP Best Practices. Without a well designed bootstrap, our application will never get off the ground.

The general idea behind the bootstrapping is forcing all of the requests to a domain to be funneled through a central script and branching out from there. They talk about how to use Rewrite rules to accomplish this and how to set the setup. He finishes the post off by bringing it back to the layout of the application, pointing out where it fits in.

From the Zend Developer Zone today, there's the continuation of their "Blueprint for PHP Applications" series, this time focusing on bootstrapping (part 1).

The definition (of bootstrapping) from Wikipedia has more flair to it than I can probably give this article, but nonetheless bootstrapping is an incredibly important part of a PHP web application. It is the ignition, the launch-pad, the booster rockets, and even the safety gear for our trip through PHP Best Practices. Without a well designed bootstrap, our application will never get off the ground.

The general idea behind the bootstrapping is forcing all of the requests to a domain to be funneled through a central script and branching out from there. They talk about how to use Rewrite rules to accomplish this and how to set the setup. He finishes the post off by bringing it back to the layout of the application, pointing out where it fits in.

In the latest post on the Sitepoint PHP Blog today, Harry Fuecks has his recommendation for how to help track how people do PHP, as opposed to what they're doing with it.

Here's a question… If someone comes to you and asks "How do I organise myself in PHP?", what do you say? In particular, if they are an experienced programmer in other languages but still learning their way around PHP. The question I'm really asking is what application(s) would you point people at as an example for how to do PHP.

These days I find myself pointing people at Eventum, MySQL's bug tracking application. There are things I personally have "issues" with in the way Eventum is written but those are really just my personal taste.

He talks about what he likes about their system and what benefits it has for potentiial/beginning PHP developers. He also asks for comments on what other PHP applications that developers could be pointed to as an example of good structure, a "blueprint"...

In the latest post on the Sitepoint PHP Blog today, Harry Fuecks has his recommendation for how to help track how people do PHP, as opposed to what they're doing with it.

Here's a question… If someone comes to you and asks "How do I organise myself in PHP?", what do you say? In particular, if they are an experienced programmer in other languages but still learning their way around PHP. The question I'm really asking is what application(s) would you point people at as an example for how to do PHP.

These days I find myself pointing people at Eventum, MySQL's bug tracking application. There are things I personally have "issues" with in the way Eventum is written but those are really just my personal taste.

He talks about what he likes about their system and what benefits it has for potentiial/beginning PHP developers. He also asks for comments on what other PHP applications that developers could be pointed to as an example of good structure, a "blueprint"...