Two different articles from GovTech Today caught my eye, and that's tough to do since I get a couple hundred emails a day! Filling out a paper form and faxing it to a company or government office is still a thing! It's bad for business, deteriorates trust, and we're so beyond that. Here's how to join the 2020's...

Do you rely on your phone? Like, really rely on it like its a new body part? Many of us do. So what happens when one day you notice the charger is not charging it? eGads! It has 4% to live! Check here.

Some web developers are hackers (we mean that in the nicest way). They hand-code the website to meet the custom need. We applaud that; more power to them. But we're integrators and we like it when several standard, well-supported components can be artfully combined to solve the problem. Here's a great example.

Have you been reading an article on a website and after a rather clever, profound, or newsworthy sentence, you see a link to "Tweet this?" If so, you may have run into a clicktotweet link. Would you like to do this yourself? We walk through the steps for you.

If you belong to trade associations, chambers of commerce, technical groups, etc., you should tell your website visitors. Why? How? Well, let me tell you.

We found some of our menus missing. What's worse: they were missing on some of our client's websites. The culprit?Microsoft! Internet Explorer version 10 interprets some HTML and Javascript differently than its previous versions and for that matter differently than any other browser (what else is new?) including some code necessary to display the menu systems of some of our clients. This news would have been devastating to other web developers who code pages by hand or use older technology, but we use DotNetNuke. It didn't eliminate the problem, but it certainly minimized it.

A client whose site exhibited the symptoms of the Microsoft problem asked why DNN didn't protect her from it. I was able to sing DNN's praises to her ...

I'm presenting along with several other business today. Here are my slides.

Like a lot of small businesses, Sprocket Websites sometimes suffers from the “Shoemaker’s kids have no shoes” syndrome. We spend a great deal of time working on our customer’s websites. From building new sites, to updating existing sites with new looks or functionality, to creating and posting new content and social media updates. It keeps us busy to say the least and sometimes we go a while working in the business before we can get back to working on the business a bit. Well a new module update spawned a whole bunch of work for me on our own website.

At 11:00pm last night I was notified that one of my servers was having a problem. I run a couple of site monitoring tools and Simon was the one that picked up the problem first. I got online and started a remote desktop session to the server and it connected, which normally when one of my servers isn’t running properly a RDC will fail. However, it connected and presented me with the “I’ve just had an unexpected reboot problem screen” and wanted me to tell it what happened. Well at this point I had no idea and thought about the irony of that particular screen as I filled in “unknown” into the restart reason box.