Coyote Blog

For reasons I do not fully understand because I really must not fully grasp how CSS works, the white background of the site loads last.  Some of you found the site hard to read because there was a small bit of code, really ancient site meter sort of code from 15 years ago, that was broken and slowing the white background from loading.  I think it is fixed.  Thanks to the readers who let me know.

With the help of several readers, I did a revamp on some of my site code that I think substantially fixed performance on mobile devices -- in particular, the large right hand margin that made the site really small is gone.  The site scales well to most of the devices I have tried, and as a bonus I learned enough about putting mobile code in CSS that the font for the main post section (not the margins) should increase automatically now on small, high density screens.

My company has over 20 URL's for various recreation facilities we manage.  I do all the design and maintenance of these myself, generally using a shared core design with some color and content changes.  Since this is just a side job for me, I often put it off and unfortunately things get dated fast.

For a while now I have been wanting to experiment with a content management system to ease the maintenance of multiple web sites.  So over the past couple of weeks, I have played around with various CMS's.  I was intrigued for a while by ExpressionEngine, but the fact it was not public domain (ie it charges per site licenses that would be prohibitive for me) finally killed the deal.  I also looked at Joomla and Drupal. 

Eventually, I settled on what many will consider an odd choice:  WordPress.  Yeah, I know, its a blogging engine.  I know quite well, because I am in the process of converting both my blogs from Typepad to WordPress.  I chose WordPress for a few reasons:

• I understand the blogging paradigm, and so I have a good sense for how the content will be handled, and the limitations.
• I am, having messed around with my blogs, comfortable with the WordPress templating system.  Though certainly more limited than ExpressionEngine, it does what I need to do. I am moderately facile in CSS and PHP, the two real requirements to make a good template.
• Most of my sites are simple.  The only two API's I really need to plug in to are Google Maps and Flickr, and I have tested and am comfortable with the available WordPress plugins for these.
• I want to begin, carefully, to let some of my employees be able to add and edit some content (e.g. changing store hours).  I think the wordpress interface is pretty accessible to some folks who may be new to online content and gives me the amount of control I need as an editor.  For a noob content contributor, WordPress is far more accessible than other CMS's.
• With a static site, I have an advantage over a blog in that I can turn on full site caching to speed up the site (via WP-super-cache).  I also added an SEO plugin to make my permalinks and pages more SEO friendly, something I don't care that much about on my blog.

I think that the first site came out pretty well, and I don't think its obvious that it is built on a blogging engine (site here, for our Arizona snow play area).  The biggest internal debate I had was whether to go with fixed or variable widths.  I actually went the opposite way of most modern programmers, moving from variable to fixed rather than vice versa.  Most of my customers, as shown by my server logs, have slow and dated computers and monitors, so I think fixed width makes sense. 

Yeah, I know that no one will ever consider me a l33t h4x0r for using WordPress, or even for using a CMS at all, but I was absolutely thrilled how fast the second site is going up now that I have built all the templates and functions I need.  More reports to come  (and hopefully this site will soon be on WordPress, but I am not holding my breath.  Still having trouble with brinking over the permalinks so they all work right).

The Town of South Attleboro, MA sent out wildly threatening past due letters for folks with balances as low as 1-cent  (thereby investing at least 42 cents to get one back).  In response to charges that this was stupid, City Collector Debora Marcoccio responded:

A computer automatically printed the letters for any account with a balance remaining, and they were not reviewed by staff before being sent out, Marcoccio said.

"It would be fiscally irresponsible for me to have staff weed through the bills and pull out any below a certain amount," Marcoccio said. " And what would that amount be?"

What, are we living in the 19th century with clerks in a musty room preparing bills by hand?  This fix probably requires one whole entire line of program code in the billing system to fix.  I could probably teach myself to code whatever language the payroll system is written in (my guess is COBOL, which, god help me, I already know) in less time than this woman has spent fielding complaints and media inquiries.  Compare this to what TJIC has to do just to get the mail out.

And don't you love people who don't even have enough spine to make a simple decision about the cutoff for minimum bill size.  I have found this is one of those things the government is really, really bad at -- making decisions under uncertainty  (which covers about all decisions, except routine ones embodied in SOP).  Government has no incentives, in general, for productivity, or production, or customer satisfaction.  The only time government employees get feedback at all is when they get negative feedback from having someone yell at them for making a decision that some higher-up didn't like..  So if a decision is not justifiable either by past precedent/SOP or explicitly by the rules, it is not made.

By the way, I had a personal programming milestone last night.  I finally built a website without using a WYSIWIG editor that formatted the way I wanted it to all in CSS without a single table.  I predict that now that I have finally gotten a decent handle on CSS, which mainly consists of learning all the workarounds for when it doesn't work as you would expect, that someone is about to introduce a whole new system for formatting web pages.

A Judge has ruled that the Kaleidescape movie server (basically a big box that rips and stores DVDs on hard disk) did not violate its licensing agreement with the DVD-CCA:

Kaleidescape argued, first and foremost, that nothing in the DVD-CCA
licensing agreement prohibits the development of products that allow
users to copy their DVDs.

Indeed, that's exactly what Judge Leslie C. Nichols ruled today in
the non-jury trial at the Downtown Superior Court of Santa Clara in San
Jose, Calif. There was no breach of contract.

That seems to be good news for those of us who like the server concept and would like to make copies of our DVDs for our own (fair) use.  However, the judge seems to have sidestepped the copyright and fair use issues, such that this ruling probably will turn out to be pretty narrow and not constitute a useful precedent.

Because of this ruling, the Judge did not have to get into copyright
issues, so the Kaleidescape ruling has no copyright implications. It is
not a statement on the legality of ripping DVDs.

There was the possibility that copyright issues could have come into
play. The DVD-CCA submitted to the Court a particular document, the
"CSS General Specifications," that it asserted was part of the
licensing agreement.

The CSS General Specifications document includes wording about
thwarting the "unauthorized copying" of DVD's. The issue of what
constitutes an unauthorized copy could have come up, but Judge Nichols
ruled that the document in fact is not part of the DVD-CCA licensing
agreement.