So you want to create a really large hero component or call to action with a focus on images to perhaps add some visual interest to the area or break up an otherwise fairly boring sea of flat boxes.
One big challenge will be to get really large images, in the correct (very narrow) aspect ratio, that are art-directed so they don’t cause problems with your text. Once that’s done, now you’re going to need to contend with the large file (and thus download) sizes of that hero image.
Okay, so there are some challenges. Hit the jump to see how I solved it.
A while ago—about the last post on this blog—I decided to start running Trunk. Since 3.6 was a few weeks away at that time and I wanted to know what was going on with Post Formats, I also modified the site to utilize some of the fun new functions.
Then the Post Format upgrades were pulled from trunk. Then I updated all the WordPress sites on my server to 3.5.2. Except the site running trunk updated to the latest trunk version. So now my theme is referencing functions that don’t exist…. and this happens:
I just put this theme up on Github to make it easier for me to push and pull changes. It isn’t that exciting; the core of the theme is about 2 years old and frankly kind of scary. I just started updating it for use with 3.6′s post formats, however.
It’s got a weird name; apparently it was named after an Al Capone henchman. Nitti is the font that IA writer selected for their popular writing apps. It’s monospaced, beautiful, and I want to put it in my code editor. In fact, I’d be happy if pretty much everywhere I did writing had this font.
If anyone is feeling particularly like they’d love to buy me a license, I’d like, at least, the standard and web version of Nitti basic light, Nitti basic light italic, and Nitti basic light bold—six fonts total. Having on hand Nitti regular and Nitti regular italic would be nice to have. Pricing is in euros, so at the moment that doesn’t help.
When you’re writing your own custom comments callback, you’ll likely need to write-in a template tag called comment_reply_link. This template tag takes an array of options, one of which is add_below to direct where the comment reply form should be appended.
When it runs, the value of add_below is appended with a dash and the ID of the current comment. So it’s important that the ID of where you want the comment form to pop under is the same.
I’ve been asked a few times in the past year about opening links in new windows. Just because a tag, property, or attribute is there — even valid — doesn’t mean it’s appropriate to use. For instance, did you know there’s a valid CSS property to make things blink a’la the infamous <blink> tag? Doesn’t mean that’s okay.
Anyway, I wrote a blog post for 10up on the topic in case you want to know what you should be doing.
I’m sure there are plenty of heartwarming stories about how Find my iPhone, the Apple device locator app, has reunited them with their iThingy. I should have one too. My story turns out fine, don’t get me wrong:
Boy loses device at coffee shop. Boy doesn’t realize until days later when he goes to watch Netflix. Boy looks through house. Boy uses Find my iPhone app. Boy locates iPad at coffee shop where it had been rescued and turned in.
But here is where there is supposed to be jubilation, jumping up and down, happy dances, and drinks-all-around. I did none of things. I think I was more excited when a friend caught my obscure Eddie Izzard reference yesterday. Boy leaves coffee shop with shops reasonably glad he found it, but also kind of annoyed.
Am I just not that attached to it? I know now that I don’t deserve it. Maybe I should sell it and buy my parents a proper Mac. It has been useful for testing websites and I enjoy it for things like Netflix and reading newsfeeds. Maybe I’m just annoyed at myself for having lost it in the first place, and not excited because I’m tired?