Clients

Traditionally, websites have used HTTP (HyperText Transfer Protocol) by default and only used HTTPS (HTTP Secure, or HTTP over TLS, or HTTP over SSL) when they were processing particularly sensitive data like credit card information.  I’ll look at why this was the case and why we should start using HTTPS for all website traffic.

While this post is particularly pertinent to those people and organizations that operate their own websites, e.g., Troutreach Technologies' clients and potential clients, the information should be useful to all Internet users. 

As much as we try to make the operation and maintenance of our websites intuitive, there is a need to document how a site has been constructed and why certain decisions have been made.  We used the Drupal contributed module Site Notes to meet this need on Drupal Version 5 and 6 websites.  Let's look at an easy to use, and perhaps more flexible way to meet these needs in Drupal 7 and the future.

In earlier blog postings I've talked about using Mollom's services to mitigate spam that originates through a website's Contact page. In this post I'll show effective it can be.

As more and more website visitors move to portable devices, e.g., smartphones and tablets, the screen sizes and proportions become more varied.  We must make our websites more friendly to these different displays.

We hate spam!  And, we're sure that our clients do also.  Therefore, we routinely incorporate a couple of features in our websites that have been proven to dramatically reduce, if not eliminate completely, spam submissions through our contact pages and webforms.

We also love our legitimate site visitors and we don't want to waste their time, and possibly antagonize them, with intrusive antispam techniques like unnecessary CAPTCHAs when they want to send us a message.