Resources on Web, Mobile, SEO, Outsourcing and more.

When we launched our business/technical blog system under this domain/url, it was done with WordPress version 2.7 and later we upgraded it to 2.9 (Carmen McRae release) last year. Now WordPress announced its version 3, with major revisions.  WordPress community announced that 1217 bugs were fixed (which means our present blog system has 1217 bugs) which is not a small number. It has 4 digits.

WordPress 3

Next week, we will be upgrading to the new WP 3.0 and we when have started planning now few things come to my mind.

• The first thing would be Database backup.
• The only major task involved in WP upgrades is theme and plug-in compatibility checking. We may need to change our present theme and sacrifice some plug-is if they do not work with the new version. The directory of plug-ins for 3.0 is yet to be displayed, we are waiting for that.
• We are preparing a list of plug-ins, I have asked team to give up some of the plug-ins like ‘Listen Now’, i do not see any use in it. We will also remove the video comment plug-in even if it is compatible with 3.0.
• WordPress has detailed guide for version upgrades, simply following up http://codex.wordpress.org/Upgrading_WordPress helped us before.
• Finally we will check the site for validations, in a previous blog we discussed this too. 4 site design validations you should do before you deliver

Now why would we want to upgrade while the present 2.9 is working fine. Not just for the terrible figure 1217, But I like the following list of features which I see in WP3.

1. Create multiple blogs/sites with single control panel. This would be a boon for company like us, who run more than 4 business sites and blogs. But we need to find how easy it would be.
2. Contextual help in the same page. You get what is what within that section. I am sure this will help our customers who use WordPress or any blogging/CMS for the first time.
3. Custom Menu management: We so far used third party plug-ins for Menu based navigations. Some plug-ins works well with some WordPress versions, and some are not. This is the graceful feature which I welcome.
4. Support for short URLs: We need to check is the short URLs are automatically created or we need to use a service like bit.ly

Before we recommend the upgrade to our customers, we want to try and practice it in our system first. Can’t wait!

WordPress control panel has Auto upgrade at : http://blog.macronimous.com/wp-admin/update-core.php , we will try it and post it soon.

Not all the web clients are tech or web savvies. Many times you should pave them their success path online. Here are few a list of 4 important things which you should let your client know, if they trust your web development skills.

1. Flash: When they ask for a fully flashed website, let them know the adversity it might make. By doing this you are helping them to establish the right online presence. Unless your client is Coca cola or Burger King ( I mean,  :-), an establish brand), they will really want to establish better Visibility to the Search Engines.

2. SEO – If a client just wants a website, let them know what SEO is and how it is going to help them. Make the site SEO friendly within the design scope (Eg. Image tags, XHTML validations, designing without tables, etc). Most of the clients will not say NO to make their site ready for SEO.

3. CMS – Ask how frequently they want to change the content, and if they do, let them do know how to do it themselves with a CMS. You may also need to let them know the advantages of fresh content. I believe instead of providing them a static site of 20 pages, you can introduce them Joomla and how to use it, for some additional but onetime investments.

4. Advantages of Opensource - Do they need a CMS or Ecommerce, You can justify why you charge less. Let them know that you can cut cost by using WordPress or Magento and still make their site professional. By doing this you are introducing standards – if your client goes to some other developers, it would not be difficult for them to take up the work.

I recommend you to keep a short write up (with some references) or articles on the above mentioned (you may keep that under your client section of your website) and ask the client to refer them. It also helps them to understand that you know what you tell them.

Many of our customers who look for Ecommerce solutions find Opensource solutions to build it cost effectively and they like what we recommended, Cubecart!There are reasons:1. Easy to customize (skin based), and this keeps the cost low.
2. You can bring great look and feel with skins, you can make the site like complete custom design. No footsteps of Cubecart would be visible.
3. PHP programmers likes it. – Clean code structure, easy to manage. Our PHP programmers have a great feel about it.
4. Designers like it. Clean XHTML interface and CSS driven.
5. SEO guys like it. Search Engine Friendly URLs, Custom URLs, Meta Tags, Robots.txt & PHP Session Killer etc
6. Good support from Cubecart team apart from forum support (Like http://www.cubecartforums.org/)
7. Low cost, $180 only.
8. Good number of alternate payment solutions, Shipping modules (http://www.cubecart.com/modules)
9. Web2.0 interface, But I am yet to see any Mashups.We strongly recommend and teach the importance of SEO for customers who wants us to build Ecommerce sites, as any online business should consider SEO as their primary marketing channel – Not just news paper ads, for long term business through online. Cubecart is one good choice to build SEO friendly Ecommerce sites that supports online marketing.

Organizing of content is done better way using drop down menus. But coding them could be a heck of a task. Thanks to some of the finest plug-ins that cater to the drop down menus needs for WordPress, we can use them in our websites or blogs for easy drop down navigation. These plug-in can also be customized manually for better presentation.
 
Discussed below are four drop down plug-ins, for sites enabled with WordPress.
 
1. Suckerfish WordPress Plug-in: It can be downloaded from here. Suckerfish has already existing drop down design, but the same can also be customized using the CSS generator, which very well suits this plug-in. The site clearly explains the procedure to install the plug-in onto your website.
 
2. Zack Designs: A three level drop down menu has been developed by Zack Designs, for WordPress. This looks to be really promising and efficient as well. You can download it from here. But one thing is that this would be a strict no-no for people who are not well conversant with CSS, especially if you are attempting to make changes to the existing design that the plug-in provides.
 
3. Gouden Douche plug-in: Depending upon the page list, the drop down menu is created in your website, by this plug-in. It has about 3 versions of the plug-in and is still in the beta version. All the 3 versions have specific requirements, with the latest one still having few bugs in it; still it is definitely worth a look and a try, in case you are able to fix the glitches. With the beta version that has come out, it sure looks to be a promising WordPress drop down plug-in.
 
4. TransMenu: A very swift and animated drop down menu, TransMenu is easy to install at the same time makes drop downs more attractive as well. With options to include pages and sub pages inside, the drop down is definitely a very good idea for starters. The site also gives detailed information about how to go about installing the plug-in.
 
It would be good to try them out first in any blog if the features are compatible with your requirements and try applying them in your WordPress enabled sites.

Hackers like WordPress sites and your blogs too. With some precautious steps you could avoid your WordPress driven website being hacked.

WordPress codex has a detailed article on Hardening wordpress, and hence hardening your site. In fact its a guide to help you to find and prevent your PC vulnerabilities, Server Vulnerabilities, WordPress package issues, Your network issues, Database, Files etc.

Go on here to read further to learn to secure your site.

In a survey, by the Information Architecture Institute, 47.6% of people says “My CMS is not flexible enough to accommodate my design”, as a key issue they face with many Opensource CMSs available in the market. This made me to think about the truth behind this. What prevents them from making a great design for their CMS driven site? Is it the CMS they’ve chosen or they customization skills they lack?

When we offer consulting for Opensource CMS selection, it is not an easy job always. Building websites with the CMS our clients like and to make it work with our own custom design might become a nightmare if we aren’t considering and planning the UI design in advance.

We have customers who supply design for their web sites (as Photoshop source files – if they know Photoshop) since they have good sense of designing and they know how their site should look like. We can happily accept it and build HTML/XHTML and CSS based Static pages without any issues or provide a Custom written CMS easily. The real challenge starts when they want to make their site CMS enabled with an Opensource CMS framework such as Joomla, WordPress or Drupal.

Most of the opensource CMS applications strictly adopt some design standards, and they give clear instructions for UI designing. Your design will not work well with the CMS, if it does not obey their design rules. The primary reason for these strict rules is to help with the CMS applications for design-content separation and for easy user interface maintenance. You can easily change the design without changing the programming sections and vice versa. But can you easily fit your custom design which is created as your mind wishes to an Opensource CMS application? Most of the good CMS applications does not allow you to create an unique site with your own custom design, custom graphics and custom XHTML.

Simply configuring a Opensource CMS application along with a template design (meant for that CMS application) may ease your job, But it will not give your client an user interface, which is unique for them. It will look like one another site made with that particular CMS. I have seen several Ecommerce sites with similar structures; I can easily identify them as “made with osCommerce without added efforts”.

So, how do we deal with this situation?

Take the case of WordPress. If you start designing a site without keeping WordPress in mind, and wanted to enable WordPress CMS at later stage, I am sure you need much experience in XHTML coding  you may have to give up WordPress in order to keep your look and feel remain unchanged.

Few months earlier, we did an Ecommerce web site design with Cubecart; with the help of Programmers and good HTML scripter, we were able to make the user interface which is very unique and no template look. Yes, good PHP and HTML programmers will have to give hands to change the way the application works and to fit your custom design with the CMS. If you need a decent design which does not offer you a standard template based site look, you need an experienced team’s support to make it possible.

Cost is one key factor why people like to use opensource applications and in most of the cases we almost get a free solution. Installing Drupal or Joomla with a pre-existing design, will only help you to offer a cheaper solution, But to give a unique look and feel to your site, you must be ready to invest in application customization too. Your CMS theme or template will need your programmer’s support to provide coherent CMS driven website, which is exclusive for the customer.

Opensource CMS applications are excellent tools for professional web solutions. No objections!. Opensource CMS applications will not cut the cost of custom development completely and making a design which has an exclusive and aesthetic look to your customer will need the time/cost of your developers and designers.  Don’t leave the CMS application to decide your site user interface by cutting the customization efforts.