Profile cover photo
Profile photo
David Lanier
353 followers
353 followers
About
David's posts

Post has shared content
This looks great. Especially the support for hooks.
PhpStorm 7 Early Access Program started with PHP 5.5 support, Drupal integration, Smart Step Into, Extract Interface refactoring, Built-in SSH terminal & more

Packing up the kitchen takes a while. I have about half of it left, and will finish it up today. After that, I think we're fully ready to load the moving truck.

In a week, Janet and I will hit the road, Portland-bound, with nearly all of our worldly possessions. Exciting times!

Post has attachment
A few snapshots from Arches National Park.
PhotoPhotoPhotoPhotoPhoto
Arches National Park, April 2013
7 Photos - View album

Post has shared content
Let's stop Daylight Savings (waste of) time. We all have better things to occupy our attention and time shifts.

Post has attachment
Skied approximately 3 miles up Coal Basin Road, near Redstone.
Photo
Photo
February 25, 2013
2 Photos - View album

I'm pretty sure this has been discussed elsewhere, but I thought I'd ask here too. I'm architecting a Drupal 7 site. It will have several content types and custom entities, quite a few views, probably a lot of panels pages, and probably some rules. Pretty normal site building stuff, but a lot of it.

I'd like to store all of this in code, mainly for my own peace of mind. The features module is the obvious choice for this. Here is my question: would it be better to have one "site" feature that includes everything (content types, fields, entities, views, panels, rules), or would it be better to break it up into separate features?

I'm leaning toward using a single feature, mainly because all of the parts are interrelated, so this would be quicker. I wouldn't have to go through the mental process of distinguishing piece from piece. My perspective right now is that the pieces that are being put together really do function more as a whole than as separate sections.

If using splitting into separate features, do you have certain strategies to know how to distinguish features? One approach might be 1: Content Storage (content types, entities, fields), 2: Display (views and panels), and 3: Logic (Rules). My experience with using many separate features on a single site is that it kind of turns into a headache, because it's so easy to end up with circular dependencies, and one feature is never truly independent of the others.

So the general rule that is materializing so far for me is: "Only use a separate feature if it exists independently, or if it has a clear one-way dependency."

I'll appreciate any additional thoughts you might have.

Post has attachment
It's official, we're putting our Carbondale townhome on the market. If you know of anyone who is interested in moving to the Roaring Fork Valley of Colorado, be sure to have them check out http://www.carbondaletownhome.com/. (I can't believe that domain was available!)

Post has attachment
http://youtu.be/rBDXRsw2UPo Janet and I drove near Kebler Pass and took the photos used in this video a week ago Saturday.

Post has attachment

Post has attachment
PhotoPhotoPhotoPhotoPhoto
Fall Foliage near Kebler Pass, September 2012
6 Photos - View album
Wait while more posts are being loaded