Twitter integration and URL shortener I would love to have intergration with Twitter and possibly Facebook, but Twitter is a must. Right now, I post to Twitter manually and use bit.ly as a url shortener. I like bit.ly because it gives you stats on how many clicks and what not, so you can see how effective your links are, referrals and pages it is posted on etc. I would love to have something automatic and integrated like arstechnica Twitter - Ars Technica and their arst.ch shortener domain. Is this something within the scope of the CMS that you would be willing to do?
The upcoming Contentteller 2.1 series have already Twitter integration. The current development version is using TinyURL to make urls shortener but I will look into bit.ly.
Many things that were originally part of the 2.1 series are already available in 2.0.3 and 2.0.4. The most significant differences between the Contentteller 2.0.x and 2.1.x series are template and database changes. There are features that can't be backported to 2.0.x because of required database changes. One of those features is the ability to choose a theme for a particular news story. For example, if you have a Linux news story you could choose now a Linux based template set just for that one story. Another feature you won't see in 2.0.x are animated side boxes because of the required template modifications. The Contentteller 2.0.x series will be still supported after the launch of 2.1. The current proposed end of the life for 2.0.x is 1st November 2011 (Pro) and 1st November 2013 (Business).
I wasn't really wanting intergration with tinyurl or bit.ly. I would like to have that functionality built into the cms along the lines of the Arstechnica's (I'm assuming homebrewed) arst.ch shortening site. so I could have a site Esselbach Storyteller CMS PHP Content Management and a 2ndary url bl.ah. That 2nd domain could just point straight back at the main domain so that it handles the shortening. So http://bl.ah/agdg would point back to http://www.blahblahblah.com/agdg and point to the main story. That is the way I could see doing it, or just have a script that runs at the secondary site to handle it all. And to have functionality similar to bit.ly that keeps tracks of clicks etc would just be icing on the cake.
