This becomes obvious when you turn block caching or anonymous page caching on, because the JS/CSS won’t be included on the page. Here is the code in how to do it correctly.

/**
 * Implements hook_block_info().
 */
function mymodule_block_info() {
  $blocks['testblock'] = array(
    'info' => t('Testing Block'),
  );

  return $blocks;
}

/**
 * Implements hook_block_view().
 */
function mymodule_block_view($delta = '') {
  $block = array();

  switch ($delta) {
    case 'testblock':
      $block['subject'] = t('Testing block');
      $block['content'] = array(
        '#markup' => mymodule_testblock_content(),
        '#attached' => array(
          'css' => array(
            drupal_get_path('module', 'mymodule') . '/css/mymodule.css',
          ),
          'js' => array(
            drupal_get_path('module', 'mymodule') . '/js/mymodule.js',
          ),
        ),
      );
      break;
  }
  return $block;
}

function mymodule_testblock_content() {
  return '<p>This is a testing block!</p>';
}

This code will ultimately call drupal_add_js() and drupal_add_css(), but it is hit even with block caching on. It makes sense when you think about it, because block caching grabs the html generated in ‘#markup’ once, and doesn’t call it again when it is cached.

Here is a great article that goes through another example in how to do this.

Let’s take a closer look at the different approaches in building a website.

Option #1: Static Website

With this option you have full control over every page of the site. But the big disadvantage with this method is that you have to update every page of the site if a common element is updated (like a header or a footer). And if the site grows or more advanced features are added, it will take more time to maintain a static site. Unless you only have a two or three page site, this is usually not the best approach. The client also needs to consider that any basic text changes done to the site will need to be done by the web shop, which will add additional maintenance costs.

Option #2: Custom Programming

Unlike the static website option, this is usually the point where web programmers get involved. They can implement login systems or contact forms. But how well and how easily maintainable the website is, depends by the code produced or used. In other words, you are 100% in the hands of the programmers working on your projects. As you go to option #3 and #4, this becomes less of a factor….because less of the system is created by custom code.

These types of websites usually take more time debugging and tweaking than options #3 an #4, because there is no type of framework system involved specifying how things should be implemented. This problem becomes more obvious when other programmers need to come in and work on the system.

Option #3: Web Framework

This improves on the previous option with a few advantages:

• Access plugins for the framework to more easily add new functionality.
• Makes it easier for other programmers to work with the system, since the framework provides online documentation.
• You can implement a template engine easily to more separate your code from the html (such as Smarty or Twig).
• Allows for full customization of the website system.

The biggest disadvantage with options #2 and #3 is that it requires more dependency on programming than on anyone else (when compared with the 4th option), including designers. Even if you implement a template engine, unless your designers know how to work with it, they will be depending on the programmers to make updates to the template files (but this often depends on the designer).

It is my opinion that it costs most web shops more money to go with this route, since their dependency on programmers becomes the highest priority on most projects. The exception to this is if you need a very large system that requires extensive customizations on every level.

Option #4: CMS System

This option takes most of what works with using a framework system, and adds the following advantages:

• Most CMS systems are designed to implement modules that provide high level features without any programming required. And unlike a lot of the plugins you see with framework systems, these usually also come with an admin interface.
• Instead of depending on programmers to do most of the work for these types of projects, they are only required for very customized functionality. Everything else can be done by none programmers or designers.
• If you use a CMS system that is actively maintained, you can upgrade your websites and automatically inherit the new features and security benefits of the system. With how much and how quickly things are changing on the web, this is a huge advantage, and lowers the cost of the upgrade process (especially when you look at the cost over a period of 6-10 years).
• Out of the box allows non technical people to update their website with some basic training in how to use the system through the admin interface.

The biggest disadvantage of a system like this is that you need to keep up on the updates for the CMS and modules to keep your site secure and you are investing resources with the idea that the CMS is going in the right direction. Hackers like to focus on vulnerabilities in systems that are widely used. But with that said, large gaping security holes in systems like this are less likely than Option #2 where programmers are creating custom code on their own.

You also need to keep in mind that the learning curve with a system like this is often higher than option #3, because you not only have to learn a framework type of system, but also have to learn how use the admin and contributed modules.

Even with small websites, I think going with Drupal or WordPress is the way to go. Both of these systems are evolving and becoming more user friendly, and with Drupal you can create a very advanced website and save 75%-90% of the time it would take to create the same website outside of Drupal.

As a professional Drupal developer working for The Brick Factory, I have grown to love working with Drupal.

A few of the goals Dries has outlined includes the following: to integrate web services, optimize for HTML5, improve configuration management, improve design and usability, and to become mobile and tablet friendly.

Web Services

Web Services are one of the central features for Drupal 8. The goal for Drupal is to use the Representational State Transfer architecture (REST) for its integrated services functionality. Drupal 8 will aim to have the ability to produce data in different formats, such as JSON, XML as well as other formats.

The reason for this is that data for a website can no longer be assumed to mostly be full html pages. These days AJAX combined with communicating via web services is becoming more of a priority. It is good to see Drupal recognize this.

HTML 5

HTML 5 is another major initiative for the next Drupal release. All indications have shown that HTML 5 is a major milestone in the evolution of the internet and is now supported on the latest browsers. Drupal 8 is setting a goal to use HTML 5 as its default doctype.

Configuration Management

This initiative aims to create more control over configuration changes. It allows configurations such as rollbacks, which can return the settings back to a particular time. It also allows the saving of a configuration change, such that changes made to one site, can be automatically applied to another site. To make these types of updates to Drupal, there are a few changes that need to be made to the Drupal core and will result in much more control for Drupal developers.

Design

One of the main goals of Drupal 7 was to improve design and Drupal will aim to push this even further. Ideally the focus here will be to attract designers, which was not achieved in in the past. There will be a new core theme, which will not only be a beautifully designed theme, but it will path the way for an improved theme development process.

Mobile Devices

The previously mentioned initiatives of web services, html5 and design are directly contributing to improving the Drupal mobile experience (including tablets). A mobile initiative has been created to make Drupal the foremost mobile platform. There is a major shift predicted from desktops to tablets and mobile phones, and Drupal aims to be ready for this shift. It will be important that the backend is usable and accessible on mobile devices.

Usability

As with Design, usability was a strong focus for Drupal 7. For Drupal 8, usability will continue to be further emphasized. Formal usability tests are being conducted to see what can be improved. This will make Drupal easier to learn, quicker to perform tasks, easier to remember tasks, reduce errors, easier to recover from errors and overall make Drupal more pleasant to use. Drupal has sometimes been criticized for not being intuitive and quick to learn, so these improvements will be one of the most important of all the initiatives.

Drupal 8 Progress

You are able to keep track of the progress of these initiatives by following the Drupal 8 Initiatives group. This group provides updates and announcements and is the best group to join if you are interested in keeping up to date with Drupal 8 news.

Overview

Drupal 8 promises some exciting changes to bring it in line with some of the latest trends. It will also improve aspects that have put people off by Drupal in the past, especially usability and design.

This article was written by Mitchel Xavier. He is a Drupal Developer in Sydney Australia

This isn’t to say that Drupal is the only system you should use. But when looking at the system objectively, I think there are some advantages and disadvantages in choosing Drupal 7.

Drupal 7 Advantages

• Admin Power: If you have experience creating PHP programming websites from scratch, than you know how much work it can take in programming a website. Drupal 7 takes care of 90% of what most people need in a website and provides the ability in having the website content updated through an easy to use admin interface. In fact, the UI interface from Drupal 6 to Drupal 7 has become much more user friendly. What took 20 hours to implement via a totally custom solution, now takes 30 minutes. This is probably the biggest advantage in using Drupal 7.
• Contributed Modules: When Drupal 7 first came out, most of the major contributed modules were still in beta. However, it finally seems like the modules are in stable releases and more contributed modules are upgraded more frequently now.
• Theme Layer: The default theme layer uses PHPTemplate, but other engines can be used. It provides a flexible way for non programmers to create and modify the design of the site without requiring PHP knowledge (even though some helps).
• Active Community: With this type of system, you want people actively working on the system and modules so that bugs and security flaws are ironed out quickly. With Drupal 7, we’ve seen updates to core come out every 1-2 months since the stable version has launched.
• Custom Programming: Drupal 7 has added many hooks that allows a PHP programmer to tap into the system and contributed modules to modify behavior. This allows for extreme flexibility. In the case where you need to create a custom module from the ground up, the Drupal form API becomes a very useful and secure tool at your disposal.
• Fields: With Drupal 7, fields became widespread across the system. You now can add fields to pretty much everything: nodes, users, comments, custom entities, etc… This allows for easy customization throughout the system and is a very handy feature.

Disadvantages of Drupal 7

• Learning Curve: Once you get familiar with the basic mechanics of the system, it becomes second nature in how to do the most common things via programming. However, getting to that point requires referencing the documentation a lot in the beginning. The curve has steepened with Drupal 7, with the introduction of entities…but in most cases you won’t need to create a custom entity. Also learning how to best use the theme layer can take time in figuring out.
• Security Concerns Just like any other shared code, the risk of someone taking advantage of a security flaw is greater than it is with a totally custom system. You can minimize this risk by keeping the code up to date with security updates. With this said, I have not come across a drupal site that has been kept relatively up to date.
• Updating: Updating the core code is not difficult. But when compared to WordPress, it is a little more time consuming…especially when you do it via FTP. There are ways in speeding up this process. But most people won’t know how to take advantage of these techniques.
• Lack of Documentation: When Drupal 7 first became stable, there was very little as far as completed documentation. This made the learning curve even more difficult. Be prepared to have to do multiple Google searches in finding sample code that helps you along. Hopefully in the next year this will not be an issue.
• Speed: There is a performance hit when using a system like this with all of the moving parts of the system. The cache does help things, but it still is not the fastest system out there. I do see this improving, up through Drupal 8.

Summary

All in all, I believe Drupal 7 is a great option for most websites. It is flexible enough to handle complicated websites with a huge user base and combined with the contributed modules, most things can be handled without needing any PHP programming. The user interface has become much more user friendly since Drupal 6.

This made me think. Not because my programming skill or knowledge was challenged. But because I’m not sure what makes code or a programmer “advanced”. This article is meant to take a look at this from an analytical perspective. I’m less concerned about general labels, and more concerned in how to improve going things going forward.

What makes a PHP programmer advanced?

1. Is it the programming concepts they understand? If so, which concepts do they need to understand in order to be considered advanced?
2. Is it the amount of experience they have or the size of the websites they’ve worked on? If so, how long do they need to have programmed or how large of a website do they need to have worked on to be considered advanced?
3. Is it how fast or efficient they program? If so how fast do they need to be?
4. Or maybe it is dependent on how modular their code is?
5. Does it depend on how much they makes?
6. Does it depend on whether the PHP programmer went to college or not, and which college they went to?
7. Or does it depend on the conferences the programmer has been to?

The point I’m trying to make is that the term “advanced” is a relative term and is subjective to the person using it. A person may define a PHP programmer as advanced if they understand object oriented concepts. Or they may consider a PHP programmer advanced if they make a six figure income. But the fact of the matter is that you can use whatever labels you want, but that doesn’t define your value as a PHP programmer. Outside of general programming knowledge and concepts, there are many other factors to consider when analyzing the value of a PHP programmer. On top of that, the term “advanced” does not always equal “best” or “most valuable”. I wrote an article last year that goes through Analyzing the Value of a PHP Programmer.

What makes PHP code advanced?

Similar to the previous section, I think this question is very subjective…and honestly I think it is irrelevant. You can have the most “advanced” PHP code in the world for a system, but it could also be the most worthless code because it is impractical in most situations. I also think it misses the point.

In any given scenario, the best solution is sometimes a simpler solution than a more advanced implementation. A real world example of this that I’ve experience is the use of object oriented PHP code. In a framework system such as Zend Framework, using object oriented code makes a lot of sense. But for a simple site with only a few pages and one simple form, using objected oriented code may be overkill and take much more time to implement. At one point in my career I had built a custom object oriented framework that I used with all of the custom sites I worked on. This worked okay at the time, but looking back I now realize that I had spent a lot of time that I didn’t need to spend creating a framework system when I could have used countless other systems that were already created. On top of that, there were some websites where I had used this system where it would have been faster to just put together a more simplified solution.

Summary

Instead of throwing around general terms in labeling code or other programmers, let’s come together and figure out ways in improving code together. Practical applications. Questions such as, when does it make sense to use OOP? Or how can we make this code more modular in a site that needs to re-use the code? These are the questions that are worth pursuing. This is how we can help others improve their code (without caring how “advanced” they are) and this is how we can improve our own code and increase our value as a PHP programmer!

This PHP sample code has many advantages over the previous article. Not only that, but for the most part it is easier to implement with more complexed forms where you need more than basic validation.

Requirements

Below are the requirements for the code included in this PHP form tutorial:

• PHP 5
• jQuery
• jQuery Validate Plugin

JavaScript has become standard in browsers, which makes client side form validation user friendly before submitting the form. In fact, in most cases, it is the standard for form validation on the web.

With that said, I do not recommend depending on client side validation for your forms…mainly in defending against hackers and bots. But most people who use your form should have JavaScript enabled.

You can view a demo of the PHP form in action. You will not only see the standard validation (email, phone, and required fields), but we also take it a step further by validating check boxes. If the visitor checks the newsletter option, they must then check two topics before the form can be submitted (in the same way, you can do something like this with radio buttons). If there are errors in the form, and those errors are corrected, they will immediately disappear.

I took an example from the jQuery validation documentation and tweaked it a little bit to fit the form, for this PHP tutorial.

Form HTML Page

Below is the html for the page where the form will sit.

<html>
<head>
<script type="text/javascript" src="js/jquery-1.5.2.min.js"></script>
<script type="text/javascript" src="js/jquery.validate.min.js"></script>
<script type="text/javascript" src="js/additional-methods.min.js"></script>

<style type="text/css">
label { 
	float: left; 
	padding-right:10px;
}
label.error { 
	float: none; 
	color: red; 
	padding-left: .5em; 
	vertical-align: top; 
}
p { 
	clear: both; 
}
.gray { 
	/*color: gray;*/
	display: none;
}
#newsletter_topics label.error {
	display: none;
	padding-left: 0px;
}
</style>


<script type="text/javascript">
$(document).ready(function(){
	// validate signup form on keyup and submit
	$("#signupForm").validate({
		rules: {
			firstname: "required",
			lastname: "required",
			email: {
				required: true,
				email: true
			},
			phone: {
				required: true,
				phoneUS: true
			},
			agree: "required",
			'topic[]': {
				required: "#newsletter:checked",
				minlength: 2
			}
		},
		messages: {
			firstname: "Please enter your firstname.",
			lastname: "Please enter your lastname.",
			email: "Please enter a valid email address.",
			phone: "Please specify a valid phone number.",
			agree: "Please accept our policy."
		}
	});
	
	//code to hide topic selection, disable for demo
	var newsletter = $("#newsletter");
	
	// newsletter topics are optional, hide at first
	var inital = newsletter.is(":checked");
	var topics = $("#newsletter_topics")[inital ? "removeClass" : "addClass"]("gray");
	var topicInputs = topics.find("input").attr("disabled", !inital);
	
	// show when newsletter is checked
	newsletter.click(function() {
		topics[this.checked ? "removeClass" : "addClass"]("gray");
		topicInputs.attr("disabled", !this.checked);
	});
});
</script> 

</head>
<body>

<form id="signupForm" method="POST" action="processform.php"> 
	<fieldset> 
		<legend>Signup Form</legend> 
		<p> 
			<label for="firstname">*Firstname:</label> 
			<input id="firstname" name="firstname" /> 
		</p> 
		<p> 
			<label for="lastname">*Lastname:</label> 
			<input id="lastname" name="lastname" /> 
		</p> 
		<p> 
			<label for="email">*Email:</label> 
			<input id="email" name="email" /> 
		</p> 
		<p> 
			<label for="phone">*Phone Number:</label> 
			<input id="phone" name="phone" /> 
		</p> 
		
		<p>[ENTER POLICY HERE]</p>
		<p> 
			<label for="agree">*Do you agree to our policy?</label> 
			<input type="checkbox" class="checkbox" id="agree" name="agree" /> 
		</p>
		
		<p> 
			<label for="newsletter">Would you like to receive our newsletter?</label> 
			<input type="checkbox" class="checkbox" id="newsletter" name="newsletter" /> 
		</p> 
		<fieldset id="newsletter_topics"> 
			<legend>Topics (select at least two) - note: would be hidden when newsletter isn't selected, but is visible here for the demo</legend> 
			<label for="topic_marketflash"> 
				<input type="checkbox" id="topic_marketflash" value="marketflash" name="topic[]" /> 
				Marketflash
			</label> 
			<label for="topic_fuzz"> 
				<input type="checkbox" id="topic_fuzz" value="fuzz" name="topic[]" /> 
				Latest fuzz
			</label> 
			<label for="topic_digester"> 
				<input type="checkbox" id="topic_digester" value="digester" name="topic[]" /> 
				Mailing list digester
			</label> 
			<label for="topic[]" class="error"><br /><br />Please select at least two topics you'd like to receive.</label> 
		</fieldset> 
		<p> 
			<input class="submit" type="submit" value="Submit"/> 
		</p> 
	</fieldset> 
</form> 

</body>
</html>

One thing you will notice is that there is no PHP code on this page. You will also notice that jQuery is used heavily. In the head tag we define which fields are required and the error messages to display if the field is not entered correctly. This is the largest improvement over the last form example, since the client side error handling is immediate and it displays the errors without posting the form. There was no client side validation in the previous PHP form article.

If you are not familiar in working with jQuery, I highly recommend going through some basic jQuery examples. The bundled code I provide at the end of this PHP tutorial includes the jQuery files necessary in making this example work.

PHP: Process the Form

Since jQuery is JavaScript, if the visitor has JavaScript disabled, the validation on this page will not work and the form will be posted. With this in mind, we still need to do server side validation. I took the code that was used in the previous tutorial, and improved it for this example.

<?php 
/*
 * BEGIN CONFIG
 */

// The page you want the user to be redirected if there are no errors.
$thankYouPage = 'thanks.html';

// Define which values we are to accept from the form. If you add additional 
// fields to the form, make sure to add the form name values here.
$allowedFields = array(
	'firstname', 
	'lastname',
	'email',
	'phone',
	'agree',
	'newsletter',
	'topic',
);

// Specify the required form fields. The key is the field name and the value 
// is the error message to display.
$requiredFields = array(
	'firstname' => 'First name is required.', 
	'lastname' => 'Last name is required.',
	'email' => 'Email address is required.',
	'phone' => 'Phone number is required.',
	'agree' => 'You must agree with our policy.',
);

// Note: Since we are requiring two topics to be checked if they want to receive 
// our newsletter, we need to implement custom code.

/*
 * END CONFIG
 */


/*
 * Since we are doing javascript error checking on the form before the form gets submitted, 
 * the server side check is only a backup if the user has javascript disabled. Since this 
 * is unlikely, we are displaying the server side errors on a separate page of the form.
 * 
 * The more practical purpose of server side checking (in this case) is to prevent hackers from exploiting 
 * your PHP processing code.
 */


/*
 * BEGIN FORM VALIDATION
 */

$errors = array();

// We need to loop through the required variables to make sure they were posted with the form.
foreach($requiredFields as $fieldname => $errorMsg)
{
	if(empty($_POST[$fieldname]))
	{
		$errors[] = $errorMsg;
	}
}

// Loop through the $_POST array, to create the PHP variables from our form.
foreach($_POST AS $key => $value)
{
    // Is this an allowed field? This is a security measure.
    if(in_array($key, $allowedFields))
    {
        ${$key} = $value;
    }
}

// Code to validate the newsletter topic checkboxes
if(!empty($_POST['newsletter']))
{
	// They checked the newsletter checkbox...make sure they 
	// checked at least two topics.
	if(count($_POST['topic']) < 2)
	{
		$errors[] = "In order to receive our newsletter, you must check at least two topics.";
	}
}

/*
 * END FORM VALIDATION
 */


// Were there any errors?
if(count($errors) > 0)
{
    $errorString .= '<ul>';
    foreach($errors as $error)
    {
        $errorString .= "<li>$error</li>";
    }
    $errorString .= '</ul>';
 
    // display the errors on the page
    ?>
    <html>
    <head>
    <title>Error Processing Form</title>
    </head>
    <body>
    <h2>Error Processing Form</h2>
    <p>There was an error processing the form.</p>
    <?php echo $errorString; ?>
    <p><a href="index.php">Go Back to the Form</a></p>
    </body>
    </html>
    <?php 
}
else
{
    // At this point you can send out an email or do whatever you want
    // with the data...
 
    // each allowed form field name is now a php variable that you can access
 
    // display the thank you page
    header("Location: $thankYouPage");
}
?>

A configuration area was added to the beginning of the file. Notice that in this code, if there is are no errors processing the form, we display the errors on this page instead of the previous form. This does several things:

1. Since the majority of people will have JavaScript enabled, the server side form validation is only meant as a backup and to prevent hackers from trying to exploit the form. So displaying errors on a blank page should suffice in this case. With that said, there may be times were going back to the form and pre-populating the fields makes sense.

2. This simplifies things. We don’t have to use PHP on the form html page at all.

I also do not use the short tag version of calling PHP for compatibility.

You can download all of the PHP Form Code, which includes the required JavaScript files.

Linux Terminal

Previously, I used the terminal through SSH when I needed to. But these times were limited to basic functionality. Recently I became more familiar in working with MySQL over the command line and creating PHP shell scripts. The advantages of running PHP through the shell are that you can use a program like Screen to run a PHP daemon script. This allows the PHP script to run infinitely, which is useful in some applications when you want to check for updates every xx seconds or minutes (in a sense, it is an upgrade in using cron jobs). You also are no longer limited to the PHP memory config or time limits that are set by the php.ini file, so you have more freedom. I was able to put this to use when creating Slurp140, among several other projects.

SVN Repository

I’ve always heard of SVN, but I hadn’t used it very much prior to moving to Helena, MT. You can look at revision history, export previous revisions, see who did what revision and when, among many other useful features. For managers, they can see exactly the new code a programmer wrote in emails that are sent when the code is committed to the repository….instead of having to figure out what they did. In fact, it seems that every medium to large size company I have worked for in the last 2.5 years uses this system.

More recently I started using Git in Drupal contributions.

Drupal

I’ve been aware of Drupal for a long time, but it wasn’t until 2009 when I started using the system quite often. In fact, I’ve grown to love Drupal. It has a huge community with modules that cover most everything that you need. In fact, unless you need a very custom solution, there usually is a module that exists for what you are looking for.

I was able to create many custom modules for projects that needed custom interfaces. I was pleasantly surprised by how well thought out their module system is laid out, and how easy it is to tap into Drupal core functionality.

More recently I started working with Drupal 7. I found this version a little more difficult to pickup than Drupal 6, but it is more powerful.

WordPress

Most of my experience with WordPress has been through this site, but I also worked on several projects that used this system. I don’t like it as much as Drupal, but for a simple blog….Wordpress is hard to beat.

CiviCRM

This technically is a module for Drupal (and Joomla), but it is such a huge system that it is worth mentioning. Unfortunately, I don’t agree with how some elements have been put together for this system….but it has a ton of features and I’ve seen it used with millions of contacts for projects that I’ve worked on. It was good to get some experience with CRM a system.

Mailing Lists

I’ve worked with mailing list systems in the past, but over the last year I’ve worked with many more. Lyris, Mail Chimp, and Constant Contact…just to name a few. All of them have different API’s that are very different from each other. I personally find Mail Chimp to be the easiest to use out of all of them, and Lyris to be the most difficult (but it does have a lot more features).

Going Forward

I feel very good with the diversity in different systems I’ve learned how to use. I’ve become a better programmer because of it. But I do feel like I can improve on my command line knowledge.

Knowing what I know now five years ago, I probably would have spent more time understanding how servers work on a basic level, and how to edit code and work with a database using only the command line. With that said, I don’t think that knowing these things makes you a great programmer. In my experiences, reliability and organization are a lot more valuable to the PHP programmer!

If you want to write a guest post on a specific PHP or project management related topic, please contact me.

WordPress is a popular publishing platform that was primarily used for blogging purposes. Part of the widespread popularity of WordPress was due to the ease of use and quick setup. Users didn’t have to have a background in website programming in order to create and install an online platform to share their thoughts with the world. The downside to this popular platform in the beginning was the limited template designs and plugins that were available. The user could post blog entries or write articles, but were unable to customize the look and add other features to their WordPress site very easily.

Compared to other scripting languages, learning PHP is fairly easy, which makes getting down and dirty with with WordPress even easier. Over time, web designers and website programmers began using custom PHP programming in conjunction with WordPress to build websites. This allowed designers to use a readymade platform while having the ability to customize the look of their website, without PHP programming knowledge. This technique made it fast and profitable to build a website that was completely customizable according to the client’s preferences, without having to hand code everything. Another thing that is nice about using WordPress as a content management system is the availability of plugins. Plugins are like miniature programs that can be easily added to a website to enhance its use or functionality. For example, there are plenty of readymade plugins that can do just about anything from posting the current date and time, to allowing your site visitors to sign up for a newsletter. These can be installed quickly and most of them are simple to customize.

Not only is PHP hosting required for building a site with WordPress, but it is a good idea because it gives you access to other systems that also use PHP and MySQL. PHP has a great open source community that provides plenty of support to help with technical issues or other custom programming projects. All of the plug and play extras, such as forums and chat rooms are a piece of cake to install.

Chris Roane’s Perspective

I agree that WordPress is a powerful platform for building simple websites, like a blog. However, in the last few years, I’ve determined that Drupal is a more programmer friendly option when you really need to do a lot of customizations or implement advanced features. The module system in Drupal is much more integrated, and you can more easily modify deeper aspects of Drupal than you can in WordPress.

With that said, WordPress is more easily picked up by none PHP programmers (mainly due to the complexity of the Drupal API). Also, the admin interface for WordPress is more user friendly than Drupal, but now that is debatable since Drupal 7 launched (early last month). Both systems have active and large communities that provide tons of open source code to customize your website through plugins and modules. There are other options, but I would put Drupal and WordPress at the top of my go to list for the best PHP CMS systems out there.

About Carrie:

This article is contributed by Carrie Donalds, a senior writer for WebHostingSearch.com. She has been writing since her school days–from academic writing to blogging. Aside from writing, Carrie is also into creating home-cooked meals.

What is your favorite PHP content management system, and why?

When I think of leadership, I typically think of someone leading a group of people through a project or a task. But when you look at a good leader, their ability not only lies in how they manage others….but also how they manage their own time and productivity. An excellent PHP programmer is not only intelligent, but they also have a good understanding in how to make a project successful and refuse to make any promises or commitments that are not realistic.

Whatever you do, you are responsible for leading your own life. This includes at work and at home…even if you are not in what is considered a “leadership position”. How you interact with people, what you do with your time, how you handle problems, etc…all deal with choices that you make every day. You are the master/commander/chief/president of your own life.

Let’s take a look at how this principle relates to the web programming industry. We have a PHP programmer who works at a company we will call Cool Ass Websites. A project comes in that they want a cost estimate on. Management sends the information to the programmer and asks for a time estimate.

Now a programmer with good leadership skills will first determine if they can create an accurate time estimate based on the provided specification (see my Website Specification How To Guide). If they cannot, the programmer will request more information. If they can accurately determine a time estimate for the project, the next question they will ask themselves is if they can get the project done in the specified time line (if this was included), based on what is currently on their plate. They will not promise to complete a project in a time line that does not fit in with their work load….without either adjusting the current work load or pushing back deadlines.

Not only that, but the time estimates this programmer provides for their time is fairly accurate. In most cases they are able to get the project done in less time than they anticipate, which makes project cost estimates and project time lines go smoothly.

If you have any upper management experience in this industry, you realize that what this programmer is doing is not different than what a good project manager or team leader would be doing for multiple people. It shows signs of initiative and responsibility…traits that we all can learn.

This type of PHP programmer is valuable because they do not need someone constantly babysitting them. They can be trusted and people can depend on them confidently. If you are a manager, these are the people you want to manage because they will make you look good.

If you are in a programming related field, show people that when things get tough, you are the last one they should consider firing!

Also, if you are looking to expand your leadership role in the programming field, look into what an online Information Technology degree has to offer.

I received a shirt from Crazy Like That. I came across this site a while ago, and I liked the “geek” humor that is on these shirts. It is funny to see how much people know about the geek world, in how they respond to these shirts.

They sent me the Binary Geek T-Shirt. The quality is great, and the lettering is crisp. If you want a good quality, geek humor t-shirt….you need to take a look at their site.

They also did an email interview of me, which I really enjoyed. Check out the interview on their site. If you want to see a different side of me that is not shown very much on this website, take a ponder at the article.

Things have been very busy over the last month….but fear not! I have not forgot about this site or given up on it. I plan on getting back to a more regular writing schedule soon. On an interesting note, even through my writing silence, I have been bringing in more traffic through search engines. So stay tuned!