This is a list of ideas I had given to an acquaintance who runs a web2.0 consulting startup (the site tells everyone how to make their site successful in the present web2.0 scenario). He also sells a fairly good CMS of his own written in PHP and MySQL. Unfortunately he did not feel like implementing any of these at that time, so I'm putting them up here so that if any of you folks own a CMS or are planning to start a hip new web2.0 site, maybe these things could help. He did mention that a couple of ideas were pretty good, but they were not implementable right now.
I'm putting down both sides here:
He felt that #1 , #2 and #4 were irrelevant or impractical (which I thoroughly disagree with, naturally
), #3 was OK and #5 was good.
Somehow, he just didn't get the idea of "mashup" and so, he said #6 was irrelevant.
I think, if done properly, and that's not soooo big an IF, all six can produce tangible benefits, if nothing else, sufficient hits to recover hosting fees.
Here they are:
Free QuickSearch for Mozilla Firefox plugins.
People are turning to Firefox on a large scale due to all the negative publicity received by Internet Explorer 7 and Vista. They now want an *easy* way of finding plugins, themes and extensions. See my page at http://2stepsback.co.nr/Firefox/
You could offer a free site analytics engine for any site, based on custom code written using the GData / Alexa / Urchin etc.
So, you could offer the service free to track and display information about subscribers' websites, maybe
plotting a few graphs of traffic, requests, specific pages etc.
modules for your CMS - like Online Workflow graphs for your CMS to be used as a Collaborative editing tool.
See Zoho Virtual Office and MS Office Live - I'm not hinting that you take up something as ambitious as a
complete online collaboration tool, but just a module for simple folks to remember and manage workflows or process flows or even idea flows.
If you already have a CMS, moving all the data from PHPNuke, PostNuke, PHP-BB to your CMS are really important applications as they remove the entry barrier of the loss of existing data your potential customers may face -
The rationale: Everyone first starts out with a free forum or CMS software, then finds the bugs and patches too complicated and then wants to move to a supported version. Then, finding that moving to another CMS means losing a lot of data, they get a freelancer to do the job.
If you put a module into your CMS, you've opened entry points for several users of PHPNuke, PHP-BB etc. to convert to your CMS.
A small Firefox plugin and a small Internet Explorer Add-on to send a user's current URL to your server (or a nice domain name like surf-memory.com or surfistory.com ) and then make some or all of it available to be shared or automatically posted to multiple social bookmarking sites.
There can be a nice trail graph than you could generate using GD, or a simple set of breadcrumbs text links for those on low-speed or dial-up connections
Porting the MySQL backend of your CMS to PostgreSQL, Oracle.
I've been going around a lot of sites concerning VOIP integration, SMS integration and EPABX-on-PC ( eg.
Asterisk), for my latest local project. I can confidently state that if your CMS gets an SMS/MMS/VOIP interface, it should stand out as a unique selling point for your CMS. This market is new and hot. Not many around here (India) are into this. There is Skype/Gizmo for traditional VOIP and there is Truphone for MOIP.
IMO, this will give your CMS a huge marketing advantage over others.