Drupal Features Module and Nodequeues

A little thing I’ve noticed with the Drupal 7 [Features module](http://drupal.org/project/features “Features”) and [Nodequeues](http://drupal.org/project/nodequeue “Nodequeue”): the **View** automatically created by a nodequeue doesn’t show up in the “Views” listing when creating a Feature. You have to manually create the View, and then it’ll show up in the listing.

If you haven’t used Features before, they’re a way of collecting your configuration changes into a module that can be applied to an existing site. Since the changes are pushed into code as a module, that means they can be applied to a site without disturbing the database. This way you can apply changes to a site that’s already live and full of content.

Typekit and Drupal

We recently got a [Typekit](http://typekit.com “Typekit”) account at work, so the next step was to see if I could integrate it into some Drupal 7 projects. I was going to include the JavaScript files manually, but fortunately I stumbled upon this module first: [@font-your-face](http://drupal.org/project/fontyourface “Font Your Face”). You’ll need to generate an [API token](http://typekit.com/account/tokens “Typekit API token”) and you’re going to be up and running. If you’re not using Typekit, @font-your-face also supports other font services, like [Font Squirrel](http://www.fontsquirrel.com/ “Font Squirrel”), [Fontdeck](http://fontdeck.com/ “Font Deck”), [Fonts.com](http://www.fonts.com/ “Fonts.com”), [Google Fonts](http://www.google.com/webfonts “Google Fonts”), and [KERNEST](http://kernest.com/ “KERNEST”).

One quick note: If you’ve enabled the @font-your-face module and the Typekit module but you don’t see your Typekit JS being included in the **HEAD** of your html, check that the **sites/default/files/fontyourface/font.css** file is writeable by your server. I’m not sure why that makes a difference—it doesn’t look like that file contains anything, but after making it writeable and disabling/re-enabling the modules the Typekit JS showed up.

Typekit and MAMP

#alttext#

Because I couldn’t find much info on this out on the web: Does [Typekit](http://typekit.com “Typekit”) work with [MAMP](http://www.mamp.info “MAMP”)? **Yes, it does**.

Typekit’s domain settings cover local domain hosts just like actual public domains. You just have to enter your local domain names into the kit settings. For example, if I have a local “dirtystylus” host I just add that to the kit settings and when the kit propagates my fonts will be available for local testing.