• Part 1
• Part 2
• Part 3
• Part 4

Define The Problem

In the past, I’ve done some freelance Web Development and Web Design for different clients. One question I’ve always had to ask myself is:

How will the user be updating this website?

That question is usually preempted by a question to the client:

Do you have any HTML experience?

I can count (on one hand) the number of times that I’ve heard a yes to this question. To be quite honest, I don’t even know why I ask it anymore. Hardly any of my clients  ever had HTML experience and even if they did, I doubt they’d want to go through the hassle. So this poses the very interesting question How do you pick a CMS (content management system) for a web project?

What Not To Do – Pure HTML is wrong for many reasons

Over the years, I’ve had much experience in this area (what not to do). Gone are the days when people simply wanted a web presence. Those days, things were simple. You fire up your copy of Frontpage (oh how we’ve learned from then) and designed a website for a client and stick it onto an FTP server, and viola; you’re done. Worst case scenario, they call you up seven (7) months later and say they’ve changed their phone number and need you to make an update.

That might have been fine back then, but right now clients expect a lot more for their money. In this day and age when everyone is worried about SEO ranking and the phrase Content Is King has been coined, no one wants to have to call you up (and God forbid; pay you) to make regular updates to their website. It is expected that you provide some sort method of updating their site.

With that said, providing a purely HTML solution is not user friendly and it can be down right dangerous. Do you really want to give your users full access to the HTML files that comprise the website? What if they break something in the layout while editing in Microsoft Word, ugh!. Who would be to blame? You would.

In the past I’ve guarded against this by using the PHP include strategy. The website would be primarily PHP with a folder called “content” sitting there with various HTML files. From there, I would pull any dynamic content that would be needed for the site: Page titles, tag lines, content blocks, etc, using standard PHP includes. This way my layout would stay (relatively) intact and the user would have access to change what they were allowed to change. The problem with this method is that they required some sort of HTML knowledge to modify the content files. They also required knowledge of FTP software and servers. Not to mention, that adding a pages or sections still needed heavy interaction from myself. Needless to say, I’ve grown from then.

Joomla! – It looked like a good idea at first

Early in my college days, I stumbled across Mambo and subsequently Joomla!, it’s current fork. It did so much for you, it had to be good, right? After installing Joomla for a client, I realized what the problem was. It just did too much. There were too many configurations, and simple things were just too hard. Also, last I remember, one of the main navigational structures was generated using and ugly and rigid table structure. Yes, I know it’s been changed by now, but that was part of my initial frustration.

It just felt too heavy for a normal website. No matter how much I restricted the user (by groups – editors as opposed to admins I think) I still got complaints about how complicated the backend interface it was. Added to that fact, the templates (and I stress) at that time were very cookie-cutter. It got to the point where I could eyeball a website built in Joomla.

Since then (over 3 years ago) I haven’t given Joomla a second look. It’s just one of those things that rubs you the wrong way once, and you never look back. Judging by the version numbers, I’m forced to assume that not much has changed. But that’s just an ignorant assumption with no basis, so please don’t hold it against me.

More To Come

I really had no idea this was going to be as long as it turned out. But sometimes I start ranting and never end. Hense, there shall be a part two where I talk about my dive into WordPress.

All user input is encouranged; ThanX

• Reader Input: Picking A CMS – Part 3
• Content Management Systems
• Spell Out a Detailed Contract
• Nail in The Coffin – Mamboserver.com Hacked
• Reader Input: Picking A CMS – Part 2

So I go through the process and I’m not totally disappointed. There were the normal problems we have with all upgrades and some new ones:

• Theme Issues: This only happened on one of my blogs. Heck, it’s an old theme, so that’s to be expected. The widgets didn’t quite work right, but it was fixable.
• Plugin Issues: Of course there will be those. Some plugins haven’t been updated yet, some just required me to update them. And with the new plugin update feature, it was quite easy to fix these problems. Then, there are some plugins I just had to totally disable, but upgrades for these are coming out everyday. I’m down to one old plugin that hasn’t been updated yet.
• Admin Changes: They decided to redesign the way the administrative section looks and operates. They moved around some stuff in Write section to make it cleaner. But by far, the worst thing they did is switch to a fixed width format; ugh. But nothing that couldn’t be fixed with a quick plugin (Remove Max Width).
• Image Stuff: There is a multi-image Flash uploader and some new gallery features, but I’m not a big picture guy, so

Should Have Waited for Service Pack 1

Everything looks all nice and slick, but after a few days I began to regret my choice. The way images have been inserted is rather different: You need to click media button, the click Gallery, then click and image, then click Insert Into Post. Once you’ve done that, the media window closes. Some people are pissed by this new change since it makes inserting multiple images a pain in the ass. That stupid media window isn’t exactly light on resources.

Now this is when it does work. There are three (3) blogs that I manage and for some ridiculous reason, the Insert Into Post button does me the great pleasure of clearing the media window, hence I can’t insert any of my images. I’ve Googled this issue and some people point to problematic plugins and such. The funny thing is, I event went the step of deactivating all plugins on the blog, with no success. So WordPress 2.5, what gives? Using Firebug I’ve been able to catch the error that happens:

uncaught exception: Permission denied to get property Window.send_to_editor

I guess I was too eager. Hopefully, someone is rapidly working on 2.5.1.

• Yay! WordPress 2.5. Almost Perfect
• WordPress 2.5+ Upload Image Error – Finally Fixed!
• Top 10 CSS Image Galleries – DIY
• I Hate Internet Explorer With A Passion
• How To Make PayPerPost and Google Adsense Play Nice – MightyAdsense Plugin Hack

I has finally occurred to me that I should have gotten my own domain name a long time ago. Really, I don’t know what I was waiting for, but it was about time. Since my focus is Web 2.0, WebDevelopment2.com was an obvious choice. I’ve already written about moving wordpress to a different domain, so moving to this domain was walk in the park. I loaded up PhpMyAdmin and exported my database. Pulled up Notepad++ and did a search and replace for my old URL to the new one. Saved the file, zipped it back up, and uploaded it to the server. Since I usually deal with large databases, I didn’t even bother trying to load into PhpMyAdmin. Bigdump is now my favorite database importer for MySQL.

Finally, I loaded up the .htaccess file on the old domain name and slapped in a RewriteRule with a 301 redirect to WebDevelopment2.com. And Viola, here we have WordPress blog perfectly redirected, without losing a single inbound link. Sure, the Page Rank on the domain name is 0 (for now), but with a name like Web Development, it won’t be for long.

New Focus

I must admit, that when I started this blog I was only vaguely interested in web development and web design. My interests usually hop about like that. I started this blog when AJAX hit the scene. It was the next hottest thing and the birth of Web 2.0. However, coding AJAX, although not difficult, was tedious. And we all know, I don’t like tedium.

Lately, things have gotten a bit more serious, with respect to my interests in web development. But, I’m no less lazy. As a result, my focus (and hence the focus of this blog) is going to shift slightly. Many of you will not notice, but those of you who have been paying attention will see that something has changed. I’ve come to learn the beauty of web development frameworks, such as CakePHP for PHP (duh), Protoype and JQuery for Javascript and AJAX, and even Blueprint for CSS. Don’t worry, if you haven’t heard of any of these, you soon will. Being as lazy as I am, the DRY (Do not Repeat Yourself)Â principle naturally has you gravitating towards frameworks. If someone else; not just someone else, but an entire team of people, work on product for months and even years, I tend to think that they’ve done a better job than I ever code.

This is the new focus of my blog and I hope I don’t lose any of you guys and can bring greater quality and relevance to the things you read here.

• Moving WordPress To A Different Domain
• Your Choice of Web Development Framework Doesn’t Matter
• Comment Relish Plugin + High CPU Usage – Fixed The Right Way
• Do We Not Understand What Bias Means?
• Here’s a Quick Way to Use Multiple Local Roots With WAMP

• How To Make PayPerPost and Google Adsense Play Nice – MightyAdsense Plugin Hack
• Got My New PC
• WordPress 2.5 – The Vista of Blog Platforms
• Comment Relish Plugin + High CPU Usage – Fixed The Right Way
• Reward Your Regular Readers – Skip The Ads

I cannot over stress the importance of number seven (7) and eight (8):

• Everyone suggests researching webhosting companies, but for your first year, just use a web host that can get the job done. I use Dreamhost, and it’s fine except for the 20,000+ visit days …

• If you’re serious about your site, get your own domain name that somewhat relates to your topic (obviously cleverdude.com doesn’t relate to finances). Jim recommends GoDaddy.com, but …

A good domain name is essential to any website. Take your time when picking one. The same goes for a host. I would definitely go with reviews for this. Resist the urge to go with advertising or price solely. I made that mistake and I’m currently riding out my contract so, hopefully, I’ll be able to move with little problems. Just because a web host is advertised in your favorite magazine doesn’t mean that it’s the better deal.

If you’re a blogger, this is a definite read. If you’re a web designer, scan through the list and extract those that apply.
Source: 50 Tips for New Personal Finance Bloggers [Clear Dude]

• Should A Business Use Free Web Hosting?
• What Has Your Domain Been Up To
• Major Hosting Issues
• Weebly Editor – Web 2.0 WYSIWYG Editor
• AJAX – Things To Keep In Mind

This is what happened. I developed a new a interest lately. As a result, I was looking for a blog that I could use as a reference. All my searches returned this one blog. The name of the blog was specific to the actual topic. I went on the blog and to my dismay, I saw post after post which looked like emails from a mailing list. The funniest thing is that the Google Groups mailing list from which he was sponging his information was one that I had recently subscribed to. I actually found a pos, which was me asking a question to the group.
This is what I assume he did. He went into the Blogger configuration and set up the Blog by Email option. And he used the same email address that he used to sign up to the group. So, every time a message is sent to the group it is forwarded to his email address and ends up on his blog.

Now of course this guy has Google Adsense up on his blog and it trying to rake in some income. Hey, what can I say? I must commend his efforts, but this is just rediculous. What I further don’t understand is that he has this site up at Blogger, which is owned by Google. It’s been up for almost two months now, and I don’t understand why it hasn’t been canned. It even ranks highly in the Google Searches. Wow. A splog on Blogger (hosted by Google), rips information straight from Google Groups and ranks highly for its topic in Google Search.

I think Google has fallen off their game a lil’ bit. What do you guys think? Where do I go to to report splogs, somebody help me.

• CakePHP – One RSS Feed To Rule Them All
• Getting Paid to Blog
• Clever Dude – 50 Tips for New Personal Finance Bloggers That Web Designers Can Learn From
• 8 Reasons HTML Emails Hurt Marketing
• New HTML Group Reinventing HTML

The MightyAdsense Plugin has many useful options. You can store up to 10 different sets of ads for various locations on your blog. You can insert them into your template by calling one simple function instead of having to paste entire code snippets for the ads. Since all your code for the ads are stored in WordPress, it makes changing the format of an ad a breeze.

But here’s where the magic comes in. You can chose certain ads to be automatically inserted into posts and pages. One your homepage, category list, etc; where you list many different posts on one page, you can chose to insert specific ads into certain ads on the page. Namely the first, second, and third posts. This is the set up I have for my first post:

The second post I leave blank, but have the following on the third:

Now this is what I have on every page/post:

PayPerPost Says No Ads

PayPerPost has recently modified their Terms of Service:

Inline Ads and Links. There are to be no third party links, ads or other detractors located within the sponsored post.

Now this has seriously thrown a kink into my normal blogging activity. I guess I could change the tight of ad or change the placement of the ad. But over time I’ve come to realize that this in post block ad is the highest paying ad on my site. It makes sense, since the ad is directly related to the post it is in. MightyAdsense currently has no option to manually exclude certain posts from having ads. So it’s all or nothing, Google Adsense or PayPerPost. Why can’t we have the best of both worlds? Well now you can!

Solution: MightyAdsense Hack – Automatically Exclude Certain Categories

Now, as you can tell, I’m a big fan of the whole automatic thing, but it does take a little bit homework.

1. Ensure that all PayPerPost posts are in a particular category.
   My posts are always in the category: Sponsored Posts.
2. Find the Category ID
   Go to the Manage menu in your WordPress administrator menu, click Categories, then find the ID in the, um…well, ID column.
3. Administer the MightyAdsense Hack
   Open up the MightyAdsense plugin in a text editor. We’re looking in the area of line 373 (ver. 4.1. Yours might vary) for the following function:

   function mightyadsense_generateads($content)

   This function starts with the code to insert the ads into a single post:

   if (is_single())

   . So, again we’re looking around line 385:

   //reach the right assignment.
   $adsstr=getAds($p,$content);
   //exit the loop
   $p=1000;
   $mai=1000;

   This is what actually ads the ad code. Around the above code we add the following:

   if (!in_category(9))    // PayPerPost Hack
   {
   $adsstr=getAds($p,$content);
   //exit the loop
   $p=1000;
   $mai=1000;
   }

   Now, I think you can follow me here. My Sponsored Post category id is 9. So we’re saying “insert this ad everywhere except in posts with category ID 9″.

Now obviously, there are some disadvantages to this. You need to edit the code for each different blog you own. What would be ideal is if you could add some option to the plugin where you user could select the category they wish to exclude. But, I’m not a WordPress plugin creator and I did this on my lunch hour.

This way we keep ads out of certain posts and keep PayPerPost happy and still have ads in the rest of our posts. I hope this helps the masses out there.

• Reward Your Regular Readers – Skip The Ads
• PayPerPost’s Answer To The Google PageRank Issue – Real Rank
• FeedBurner + Google search cache = Instant Blog Back Up
• Yay! WordPress 2.5. Almost Perfect
• WordPress 2.5 – The Vista of Blog Platforms

Widgets are, however, a bit awkward to design. A lot of plugins these days come with widgets built in, but there are those that don’t. For these, it’s a bit of a pain to use.

For this purpose we have the King Text + PHP Widget Plugin. This plugin enables you to define empty plugins that you can paste text, HTML, or even PHP into.

I’ve converted all of my blogs (except this one ) to use Widgets. It takes a bit of time to set up, at first, but the flexibility they offer you is just great.

• WordPress 2.5 – The Vista of Blog Platforms
• Yay! WordPress 2.5. Almost Perfect
• Round Corners With jQuery and CSS
• See How Easily You Can Increase Page Load Time 10 Fold With jQuery
• Moving WordPress To A Different Domain

Then I noticed that not only posts were gone, but some settings reverted back to their original values. Upon closer inspection, I realized that certain entries in certain tables in the database were deleted. Hmmph, who knows what the problem was. So I figure that it should be a simple enough task to get a backup from my web host. I was wrong about that, very wrong.

Now let me first state that I was also wrong in not maintaining my own database backups. There is absolutely no excuse for this, so I take full blame for my problem. If I had a database back up, I wouldn’t have been in the situation that I’m in right now. Anyway, moving on. After over 4 days of moving back and forth with tech support, they were able to supply me with their earliest backup, which was dated the day after my database meltdown. So I was screwed, or was I?

There were two tools which saved my butt. First, FeedBurner. With FeedBurner, I was able to recover the titles and content for all of my posts, but simply going back to my feed. To accomplish this, I used Google Reader.

I had one other small problem: The links of my posts are not dependent on the date, by default, but on the category. This is where Google’s caching feature comes in handy. I used the post titles and searched for the web page in Google, by using the site: feature. This did two things: it gave me the link of my post, so I could see what was the main category. I could also view a cached version of the page to see any other relevant information.

So, something to note. FeedBurner + Google search cache = Instant Blog Back Up.

• How To Make PayPerPost and Google Adsense Play Nice – MightyAdsense Plugin Hack
• JavaScript Only Links, Why? Someone Tell Me Why, Please
• Automate MySQL Database Backup With WebCron – No Cron Jobs? No Problem – Part 2
• Why My WordPress 2.7 Install “Failed”
• BloggerWave – Get Paid To Blog

Lava finally made the big step and “moved into her own place“. Moving domains is always such a hassle, but there are a few things that make the process a little bit easier. I was the Administrator during this move and I must say it was a little bit involved, but I think I got it done.

The Domain

The domain was purchase at 1and1.com. Why not NetSolutions, Yahoo, GoDaddy? Because they all have great promotional deals but then it’s upward of $8 to renew every year. 1and1 has a nice flat rate of $5.99 every year.

The host remained the same, since this particular hosts allows up to 10 domains pointing to it. All the files are simply dumped in a different sub folder. I both love and hate the idea of one consolidated host. It’s easier to manage: one login one set of administration and maintenance, cheaper than several different hosts. But if one sight goes down, they all go down. If a hacker gets into one, he damn well gets into all of them. The load on all of the sites is still very small and way under the allotted bandwidth limit. Most of them are blogs using WordPress and we all know what a small physical footprint WordPress leaves behind. If any one site seems to out grow things little family what it turns 18 or something, it will definitely be kicked out of the nest onto it’s on hosting package.

Copy Files

Now this should be the simple part. You copy everything into the folder that is going to house your new blog. There are a few minor changes that you might need to make. Depending on your previous setup you may need to edit the .htaccess file and change the RewriteBase option. But I do think that WordPress will configure it for you when you set up your permalink stuff.

One change that is necessary is editing your wp_config.php file. If you’re changing databases, you need to make the changes here. If you’re not changing databases you still need to make the changes to the table prefix. I forgot to mention that we still need to keep the old database active (details to come later).

Database Migration

Moving the blog involved a little bit of work. There were two stages during this process. There was installing WordPress and there was importing old data. Now frankly, I know I made some mistakes, but all in all, things went smoothly.

It’s funny how moving databases on the same host was actually more difficult. Well, I made it more difficult I guess. My limited shared host has a limit on the number of database you can have. So, to counter that I’ve decided to use a database to its fullest capacity before I create a new one. So different blogs will share the same database but use different table prefixes for identification. It’s a nice plan and it does work, but it makes imports a bit difficult.

Now because I still wanted the old blog up (reasons to come later) I couldn’t simply go into WordPress and change the URL. Come on now, that would make things too easy. So I exported the database. I could not do a straight import because I needed to change the table names so that there would be two copies of each table with each having a different prefix. For example, I’m copying all the wp_ tables to wp2_. Sounds easy in theory, but it was a bit involved.

This is the process I ended up going through. I unzipped the exported DB file. Opened the file in a text editor. Now the uncompressed file was about 14 MB. I used Notepad++ to open it, and even with my new hardware it took a while. I then did a search and replace: wp_ to wp2_. This is so that when the script runs it will import into the newly specified table names. After the completed process I would have one bunch of tables wp_ and another wp2_ with the same structure and the same data. If anyone has a smoother method of doing this, I’m all ears. But I did a quick Google search for Copy MySQL Table and apart from console instructions (No shell access, cheap host) I came up short and it was 1:00 AM and I wanted to get to sleep.

So, the file was edited, I zipped it back up in GZip format with 7Zip and went to the host’s phpMyAdmin site and tried to do an import. Only to realize they don’t have the file import field. This was a bit of a pain. I would have had to copy and paste the data into the little form so that it would run the SQL commands. There was one problem with that though, the uncompressed file was 14 MB and there was no way that the browser could handle that without locking up. So importing that large database was another story: Importing Large MySQL Databases – When phpMyAdmin Let’s You Down – Get BigDump.

Database Configuration

No, we’re not installing a new version of WordPress. You can do that later, after everything is settled, if a new version has come out and you want to upgrade. Or do it before, just not now. Now that your database has been imported properly, you need to make one minor change. Funny enough, this isn’t a change that I’ve seen documented anywhere else though. But it was necessary for me, who knows maybe I did something wrong. I needed to edit the database wp_options table and edit the option_value for the entries where the option_name is siteurl and host. I needed to change these to match the new domain. The first time I left out this step, every time I tried to do anything it just forwarded me back to the old blog. That’s it. I tried editing them from within WordPress, but that didn’t seem to work either.

After that you’re good for the new database. You might need to update some links within your posts, but the next step will simply make this a preference. The only problem we have is that your ranking is going to suffer because you’re starting from scratch. If you have a good relationship with the people that have given you links, you may beg them to update some links or their blogroll. This would help you dramatically in rankings, but again it’s not a necessity.

Preserving Old Links

This is where the magic happens. People hate switching domains because, it’s a hassle, you lose your rankings for search engines and Technorati, etc, and most of all you lose all your inbound links and your visitors are left in the dark. Well, I can’t help you with the first parts, but that last part is a breeze.

There are two methods. The easy one and the easier one. The only thing is that your permalink structure needs to be identical, so don’t try to get fancy and switch them up just because it’s a new domain name.

For the easy one, we edit the .htaccess file and one line:

RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

You add this somewhere after the line: RewriteEngine On

That’s about it really. What this does is that, whenever someone tries to access a link from the old site, it will forward them to the same URL on the new site. The excellent thing is that it will also forward search engines. It’s that great? That’s what the code 301 means. Eventually, they will actually update their database to reflect your new URL. This also keeps your from getting penalized for duplicate content by the search engines. There is only one minor issue with this and it’s just a cosmetic one: the old URL is still left in the browser window. Who cares right? Well I do. There is a workaround, which involves some template changes in your new blog. Basically it says if you have been forwarded by from the old URL, then reload the URL with that of the new one. Pay attention now, this isn’t the same thing. This is done in the browser and refreshes the screen. It’s not really a refresh since it is done before anything else is sent. This, to me is a bit clunky.

The easier one: This is the simplest method that I’ve seen. You can’t really get simpler than this. But it involves leave the old blog active, sort of. Funny enough, it’s called the Moving Your Blog Plugin. You install this on your OLD blog, activate it, go to the options, and enter the URL of the NEW blog (no trailing slashes) and that’s it dude.

Now if you’re like me and you’re on a host with limited database space, then you might want to do a little bit of house keeping. What I’ve done is deactivated all the old plugins, delete all posts and comments, and all files that I’ve ever uploaded (including unused themes – I went back to the classic). Now you’re saying that I’m defeating the purpose by deleting the posts, but actually the plugin doesn’t need the posts. I’m not sure exactly what it needs, but deleting posts and comments didn’t seem to harm it. That’s where most of the space is taken up anyway. I also went through the database and DROPped tables that were created for plugins that I’ve deactivated.

After that, you should have everything working perfectly.

• New Domain: WebDevelopment2.com, New Focus: Frameworks, CakePHP, Javascript, Web 2.0
• FeedBurner + Google search cache = Instant Blog Back Up
• WordPress 2.5+ Upload Image Error – Finally Fixed!
• Here’s a Quick Way to Use Multiple Local Roots With WAMP
• Comment Relish Plugin + High CPU Usage – Fixed The Right Way

• New Domain: WebDevelopment2.com, New Focus: Frameworks, CakePHP, Javascript, Web 2.0
• FeedBurner + Google search cache = Instant Blog Back Up
• Finally Graduating – I’m Done
• Fixing the Back Button and Enabling Bookmarking for AJAX Apps
• Finals Week – Sorry Folks

Now comes another problem. Rather a solution that causes a problem. Most people fixed this resolution issue by slapping on a fixed layout. Now fixed layouts have their pros and cons. The pros are, you know exactly how it will look every time. You know where every thing will be on the website. One major con, I experienced at a friend’s house. He had just gotten a brand new 21″ flat panel monitor and everything looked so crisp. After a couple hours of playing, Wolfenstein: Enemy Territory we were just browsing the Internet and I just asked him to check out my latest post at the time. When he did I was horrified. My beautiful fixed width 787 pixel layout, which looks just brilliant on my 17″ at home, still looked brilliant here, but it was so bloody small. I mean the thing was tiny and scrolling took forever. Yeah, we would have had to scroll a lot on a smaller monitor but since we have this huge one, why should we. There was just so much wasted screen space it annoyed me. You could almost fit a whole other site right next to mine.

When I went home, I said goodbye to the fixed width layout and picked up a fluid one. And I must say, I’m kind of in love with this one. Whether 800 pixels or much higher, everything just stretches out to fill the screen. Sometimes you scroll, some times you don’t. So first off, I’d like to apologize for all my visitors with large fancy monitors, I did not know what you were going through. The other issue is that blogs are less affected by this screen resolution thing for two reasons. First of all, blogs are meant to be read. Therefore the less vertical eye movement the user has to do easier it is on his eyes. A blog is less about graphically and structural presentation and more about reading the text. I’m not saying blogs should be ugly, I’m just saying you don’t need to hook the visitor with too many pretty pictures to get their attention. The second reason is that, a lot of blogs don’t even get visited anymore. With the advent of RSS feeds a lot of people don’t even know what the home page of the blog looks like. RSS feeders just feed straight text and it fills it out however your reader is configured to.

Now because the fluid layout is so great, you know there’s going to be a catch right? The main issue, for me anyways, is getting it to have a minimum width. I mean, there is a point where you just don’t want your website getting any smaller. After all, the main reason we’re using this fluid layout is so that things get expanded. Enter the problem of CSS and the min-width property. This is an entirely different post all on its own, so I’ll leave it as that.

Anyways, tell me how you guys like the new layout. Love it, hate it, I wanna know.

• Websites on Wide Screen – How The Other Half Lives
• Yay! WordPress 2.5. Almost Perfect
• I Think I Owe IE 6 An Apology, Nah.
• Dclick Ads – Another Quick Start Up Advertising Site
• Joomla Template Tip: Optional Modules

Check it out:

Save Money.

• 5 Steps to Simple SEO
• Poll Results – What Do You Look for in a PHP Framework?
• Chitika Ads
• New Domain: WebDevelopment2.com, New Focus: Frameworks, CakePHP, Javascript, Web 2.0
• Blog Revival

Tony writes:

Its as though one loses their status as a “real” blogger the instant you put up Google Adwords, or start selling ad space — as though the purity of your writings takes on a different cast because, well, you’ve got to pay the bills.

As Tony mentions, ads on a website are one thing but PayPerPost is totally different. Having contextual ads makes perfect sense and I actually do use them sometimes. When I read a blog it’s because I actually care about what’s going on there, I’m into the topic. So I would be more inclined to look into ads that were about a topic that interests me.

I say go ahead bloggers. Enjoy, you’ve worked hard.

• PayPerPost’s Answer To The Google PageRank Issue – Real Rank
• Splogs (Spam Blogs) From Mailing Lists – This One’s New To Me
• How To Make PayPerPost and Google Adsense Play Nice – MightyAdsense Plugin Hack
• Clever Dude – 50 Tips for New Personal Finance Bloggers That Web Designers Can Learn From
• AJAX – Things To Keep In Mind