CMS Myth is rapidly becoming one of my favorite CMS-related blogs. Â Yesterday, this comic appeared in Google Reader and I experienced a momentary pang ofÂ embarrassment. Â “Oh no!” I thought “I’ve become that guy, blathering on about pasting from MS Word“. Â Actually, it’s even worse; one of ourÂ demo projects is called Quantum. Â Coincidence? Â Probably. Â But this comic struck awfully close to home.
My first impulse was to laugh it off. Â Jeff is correct, CMS demos should be taken with a grain of salt. Â During demos I know precisely what looks good and what to avoidÂ clicking. Â It’s demo magic… just enjoy the show. Â However, the more I pondered this, the more I began to dwell on the process involved in creating this demo magic.
Podcasts have almost completely replaced music and radio for me. Â Anytime I’m physically occupied, but mentally bored (biking, driving, jogging) these things become a source of learning, stories or stupid entertainment. Â Here is a list of the podcasts I enjoy:
Mike Baumeister posted a simple, but very BIG question to Twitter:
There are lots of things developers and designers can do to make the CMS experience better for content authors. Hell, Iâ€™ve written many pages of recommendations for the WYSIWYG editor alone. By contrast, there are also implementation decisions that become downright hostile to content authors.
I recently had a project where I wanted my web site content to utilize short URLs. Â These short URL’s would be easier to utilize on Twitter where the message is limited to 140 characters. Â At this stage link shortening is old news and I could use one of the many available linkÂ shorteningÂ services (Bit.ly, Goo.gl) to generate these links. Â However, I dislike the idea of encouraging visitors to tweet a Bit.ly link, as opposed to my own links.
Using database ID’s to create short links
To address this my original idea was to simply rely on the auto-incremented row ID’s for each item in the database. Â For the database table, this looks something like this:
For anyone investigating Responsive Design it’s natural to ask what percentage of web browsers support this design technique. Â However, the real question you’re asking is “what percentage of web browsers support CSS3 media queries?”. Â CSS3 media queries are the primary technology involved in responsive design. Â If you’re simply looking for a quick answer, here it is:
Responsive design is supported by 70-80% of today’s web devices
However, the complete answer is a lot more nuanced than this. Â The number above examines all web-related traffic. Â However, responsive design is often used to target mobile devices. Â Those statistics look a lot different. Â Furthermore, there are techniques for addressing browsers & devices that do not support responsive design.
I don’t think I’ll get too many arguments if I make this statement:
Content Management Systems (CMS) are a vital tool for creating and maintaining a modern web site.
However, CMS’s vary in price from free to $100k+ and there are widely differing opinions about what a CMS should cost. Â I’m probably not going to change any minds on this and I’m not terribly interested in trying. Â However, I would like to better frame this conversation.
The Telerik Evangelism team has recently been experimenting with new techniques for staying connected and in-sync. Â One of these techniques was to utilize video-conferencing for our bi-weekly meetings. Â Sadly, I’ve not discovered any video-conferencing solutions thatÂ accommodates a team of our size (15 people). Â Below I’ve summarized my experiences thus far:
Over this past weekend I decided to retire my old goondocks.com blog. Â This domain name is a reference to The Goonies which is a movie I remember fondly from the 80’s. Â I picked up this domain many years ago and held on to it. Â When I discovered Sitefinity 3.0 I used it to experiment and share my lessons & experiences.
After joining Telerik, Â I launched sitefinitywatch.com and never again touched goondocks.com. Â Consequently, this blog has stagnated and become a dumping ground for spammers. Â There are now thousands of blog comments that contain nothing but spam:
I wanted to import my old blog posts andÂ legitimateÂ comments to this blog. Â If you scroll down below you’ll see I’m using Disqus to manage my comments on this blog. Â Consequently, I needed to find a way to filter the SPAM from these comments, export the comments from Sitefinity 3.x and then import these comments into Disqus.
The Holidays are upon us and 2011 is nearly gone.Â This past year has been extremely busy and significant for Sitefinity.Â Before we move into 2012 I want to reflect on 2011.Â This post is strictly my personal opinion and, consequently, is being published to my personal blog.
Iâ€™m publishing this for Sitefinity customers who might be interested in a Telerik insidersâ€™ perspective on this past year.Â Hopefully this provides some context and a glimpse into whatâ€™s coming in 2012.
Yesterday Amazon’s Jeff BezosÂ announcedÂ their new Kindle Fire tablet. Â This tablet is a full color, touch-enabled device that is capable of apps, games, books, movies or web browsing. Â To put it bluntly, it’s like an iPad…except it’s $199.
However, it’s the web browser component of this device that caught my attention.