Some people hate it and some love it. I belong to the second category. If you, as a webmaster, don't like it, simply do not enable theme support for post formats. I think that post formats bring incredible possibilities to website presentation.
Basic requirements: WP 3.1, theme support, knowledge of CSS and WP filters, imagination, and creativity.
I have to admitt that things were rather slow when it comes to new posts on our site in 2010. However, there were many developments behind the scenes. Moving our website to the "cloud vps" was one, and it was very time consuming.
We plan for year 2011 to have more technical info about WP, especially about new features of WP versions including 3.0 and above. You can finally expect reviews of excellent plugins and themes by Dev4Press. That's the plan and we will try stick to it.
FWSS website is now hosted on VPS.NET's cloud vps. Due to some technical obstacles the website was unavailable for couple of days ( my sincere apology ).
The server consists of 1 node only ( I'll be adding nodes soon ). OS: CentOS 5.5/64, CPU: 0.6GHz, RAM: 376MB, Storage: 10GB, Bandwidth: 250GB. As you can see this is a very minimalistic configuration, however, hosting 5 WordPress websites in 2 domains it still performs better than one WordPress website in shared hosting environment.
In near future the server will have at least 4 nodes hosting 13 websites in 7 domains.
Setting featured image for post/page could be very time consuming, especially when your media library holds hundreds of pictures. Very often we select the same thumbnail for posts in particular category. Wouldn't be much easier to have a thumbnail being set automatically when we choose a category while creating or updating posts/pages? I could not find in wordpress.org repository any plugins doing exactly what I wanted and decided to write my own. It started as a plugin just for myself. Exactly 12 lines of code. Then I decided to share it with others. And here it is - FPW Category Thumbnails. Click on a link above this post to see the plugin in WordPress repository.
This article is aimed at WordPress core developers as its topic is of less interest to a regular user. Pages versus posts. Which are more important? Which deserve more respect?
In Using Google Font API article I've presented one method of incorporating specific fonts into your website. The Google's method will free you from any legal problems related to hosting unlicenced fonts, however, there are couple of drawbacks. Fonts have to be downloaded from Google's servers and that takes time. Secondly, there are only 14 fonts available as of today.
How about hosting your own fonts?
For many years web developers had to rely on fonts being available on viewers' machines. Not any more - thanks to Google Font API.
I'll present just one simple example of this method. For a list of available fonts go to Google Font Directory. For a complete documentation visit Google Font API.
WordPress 3.0 is finally released. We did automatic upgrade, with no accidents, to all our websites, and all works well. It is important to know that the new version's memory requirements changed, therefore, do not perform the upgrade before increasing PHP memory_limit to 64M as 32M is not longer enough, especially when 5 or more plugins are installed.