{"id":3420,"date":"2008-09-20T06:43:17","date_gmt":"2008-09-20T11:43:17","guid":{"rendered":"http:\/\/localhost\/wordpress\/?p=3420"},"modified":"2008-09-20T06:43:17","modified_gmt":"2008-09-20T11:43:17","slug":"web-application-developers-can-learn-a-bit-from-wordpress","status":"publish","type":"post","link":"http:\/\/10.10.2.102\/creevacom\/index.php\/2008\/09\/20\/web-application-developers-can-learn-a-bit-from-wordpress\/","title":{"rendered":"Web Application Developers Can Learn A Bit From WordPress"},"content":{"rendered":"

\"\"<\/p>\n

Picture from here<\/a><\/p>\n

Just the other day I wrote about cloud computing versus SaS terminology. A web application isn’t necessarily a cloud computing or SaS platform. It can be one or the other, it can be both, it can be neither. Now that, that is out of the way let’s move on to the meat.<\/p>\n

I think that all web application developers would do well to look at WordPress and the product they offer as key points for their own designs. Obviously, I use WordPress as a blog<\/a>, I also use it as a CMS, a middleware application system, a database, a word processor and other uses. WordPress is extensible far beyond the original blog software it was designed to be.<\/p>\n

The reason that WordPress is so transformative is the ability to use a fairly easy (well not for me but I suck at PHP and programming in general) API that the users can use to extend and transform the core product. This is done through the use of plugins. In theory, the expandability of WordPress would allow it to transform into any functional web application you can imagine. I’m not saying this should be done, however. WordPress plugins a lot of times just add band-aids to a product to extend it further than the core company can imagine or support.<\/p>\n

Think of your ticket support system. Most of these are moving to a web-based interface. Easy to manage, no software to install on users’ computers, easily updated since you only have to update the core server – it’s a no-brainer to move everything you can over to a web-based centrally managed focus for a company.<\/p>\n

Why can’t you extend it though?<\/p>\n

Most of web application companies MAY ALLOW YOU to go as far as putting your company logo in the interface. Allowing you to brand a product to some extent is not the same as extending the product. I don’t want color changes. I don’t want a simple image swap. I want feature sets to be implemented without waiting 18 months to have it done. If you have a robust CRM application, in this modern time wouldn’t you want a spot to add a LinkedIn Profile section? This would be as easy as allowing customers custom fields that they can rename on the back end. What about adding an image? This would be a bit more difficult than a simple custom field, but still possibly doable. How about however a full blow plugin that looks up the LinkedIn<\/a> contact info?<\/p>\n

This is all hypothetical, but let’s say this is how the plugin would work in a generic CRM system.<\/p>\n

1. Users logged into the CRM would associate their own – or a corporation profile with Linkedin<\/p>\n

2. User plugins in the new contacts e-mail address<\/p>\n

3. User is prompted with “Would You Like to Request Connection on Linkedin?”<\/p>\n

4. If the user states yes the plugin would go into a state of “Waiting for Remote User to Confirm”<\/p>\n

5. At this point the user could add in all the information they normally would in the CRM database<\/p>\n

6. Later the user would receive a confirmation (or decline) of linking up on LinkedIn<\/p>\n

7. If they receive a confirmation they could then pull in the information to the CRM application.<\/p>\n

8. Then the CRM application would have connections and how they relate to each other in their database, home pages, Resumes, etc. – all from a couple of clicks.<\/p>\n

That is a scenario that would appeal to sales personnel. Let’s look at something more urbane, a library look-up system. A library lookup system is something very simple and single task. It works well and returns (normally) the following information:<\/p>\n