kit
cat kit | specificity
grayside — Mon, 05/31/2010 - 22:52
When you read through Kit, one of the themes that keeps cropping up is the concept of specific relevance. How do you know when it is a good idea to include a given variable, permission, or other component in your Feature?
The answer boils down to this: Keep your Feature lean and mean. Include only what’s necessary for a good, mission-complete piece of functionality. The primary reason for this rule strikes me as the worthy goal of avoiding a horde of bloated, conflicting Features that will make an ill-configured wreckage of the sites that try to use them.
Behind the fold for further thoughts about what specificity means in a well-built Feature.
cat kit | summarize namespacing
grayside — Sat, 05/22/2010 - 22:03
I decided a few notes would help me grok the Kit Specification. I post them here in case someone else finds them useful.
Shortest Summary
Project Name and Feature Name should be the same. They should have a nice, unique namespace. The human readable version doesn’t need to show the prefix. Views and other individually exported pieces should be prefixed with the not-necessarily-unique part of the Feature name.
