Custom Field Hacks For WordPress
Custom fields are a great little thing. They allow you to easily customize your blog with only a little bit of code. Below is a succinct explanation on how to do it, courtesy wprecipes.com
Open your single.php file (You can also modify your index.php file) and paste the following code anywhere within the loop:
$customField = get_post_custom_values("mood"); if (isset($customField[0])) { echo "Mood: ".$customField[0];Save the file. Now when you’ll write a new post, just create a custom field named mood and type your current mood as a value.
WordPress Popularity
I recently read an article over on writerspace.net, entitled WordPress.com Nearing Popularity Landmark The article speaks to a simple numbers game relative to wordpress’ popularity on the web. Fascinating enough, it is predicted that wordpress will top 10 million blogs by the end of the year.
As a developer, I would just like to add a few more reasons why wordpress is the dominating force in the blogosphere.
Pings and track backs
From wikipedia:
Track backs are used primarily to facilitate communication between blogs; if a blogger writes a new entry commenting on, or referring to, an entry found at another blog, and both blogging tools support the TrackBack protocol, then the commenting blogger can notify the other blog with a “TrackBack ping“; the receiving blog will typically display summaries of, and links to, all the commenting entries below the original entry. This allows for conversations spanning several blogs that readers can easily follow.
Compared to other blogging software out there, wordpress is the superior product to handle ping and trackbacks. Superior to expression engine, blogger and movable type. Why are ping and track backs so important? Exposure. the TrackBack protocol, as simple as it is, helps to give your article the depth and breath that it would not normally see if it were up to you or your community to forward on your blog topic.
Development Community
With wordpress leading the charge in the blogosphere as the number one platform to publish blogs, the development community has come with them. Need a plugin to manage your ads? Need a plugin to increase your SEO? Need a plugin to create sitemaps? All those are accomplished with a few clicks and a download. With such a large userbase and supporting development community, chances are that someone out there has had the same need as you and there is a solution available.
All this is not to say that the alternative platforms are not wonderful engines to create your blog, not by any means. However, if asked, I personally would reccomend using wordpress.
A Fight To The Finish
I am currently employed full time as Lead Designer at a shop that is an exclusive vendor (or at least tries to be) of Microsoft products. “If Microsoft can produce it, we’ll buy it.” Personally, .NET is of little interest to me. I prefer to code inside of PHP. I can forsee that I will have certain biases for PHP, I admit that. But what is frustrating for me is all the hate from my co-workers.
Having the title of designer at work makes it hard enough to put up a fight for PHP at work, but when I attempt to add in a few thoughts here and there about a theoretical code procedure, I am shot down; FAST! Forget the fact that .NET is an application framework and PHP is a language. Forget the fact that PHP is open source, and .NET is not. And forget the fact that because of that, its like comparing apples to oranges. The fact of the matter is that PHP is just as viable of a coding language as .NET is a framework.
I wont argue that .NET is a highly flexible framework, building both website and standalone applications. I wont argue that PHP is primarily, if not exclusively, focused on websites. But what I will argue is that PHP is not vastly inferior to .NET because of one reason, pre-compiled code.
.NET pre-compiles its code before it is published out to a live server. PHP is not. For this one simple fact, every .NET developer I work with say that .NET is superior. But why? Why would I want to republish entire sites because of a simple code change? Why would I want to add an additional step to the process, when I can simply add/remove a function, move that page up to the server, and be done with it?
To me, and I might be the naive one here, I prefer the simplicity of this process. Time and time again, I have seen my fellow coworkers wait and wait for a website to compile and be published to a server. Which, might be a small preference in the grand scheme of things, but I just want to be done with it.
So to my co-workers I say Ni!
Ni!
Ni!
Sure you can make other arguments about the dominance of .NET to PHP, and I will listen. With deaf ears I will listen. Phooey on you for thinking that .NET is so much greater of a product than PHP. –With the advent of PHP5, your arguments for superiority grow thin (OOP support hint hint, nudge nudge).
Rest assured that one day, you will be hearing your fellow developers ask “you want this in PHP or .NET? there is really no difference”.