As part of the process towards building my bus, I put a significant amount of energy into figuring out how to best handle media while on the road.
A while back, I made a post about conditional widget plugins. After reviewing several, I concluded that the best options were Display Widgets and the commercial Widget Ninja. Well, since then I have discovered another option that wasn’t reviewed in the original post and it has, by far, eclipsed every possible plugin from the original post.
In the world of development, the choice of editors is usually a very personal decision. Some people are minimalists, and some prefer full-fledged IDEs. Some people insist on advanced syntax highlighting, and some prefer good, old-fashioned black on white (or white on black). Not to mention the restrictions that a users’ operating system place on the choice.
If you’ve ever spent any real time working with WordPress, there’s a fairly good chance you’ve run across a strange file in the root (or topmost) directory. Whereas the vast majority of the files comprising the WordPress hierarchy consist of a filename and an extension, such as the crucial
wp-config.php, one single file seem a bit out of place. That file is the aptly-named
.htaccess file. So just what is the .htaccess file?
Well, I’m going to start by saying that I’ve failed to make my 30-day mark. Somehow I managed to miss a day without even realizing I did it.
I feel it’s important to note that accessibility is a subject that hits particularly close to home for me. No, I don’t personally have a severe disability, but both my son and his mother do.
Now that I’ve had a little time to decompress from WordCamp San Francisco, it’s time to actually think through the events of the weekend and record my thoughts.