Remodeling Four Kitchens: A look inside our new brand
With the additions of Advomatic and Manatí, we’ve had an exciting few years at Four Kitchens. While we’ve remained fundamentally the same organization, we’ve also been evolving into something new. It’s time for our brand to catch up.Learn more
A more modern, sustainable approach to higher ed websites with YaleSites
A higher ed website is a product, not a project. Learn about Yale’s sustainable approach to digital development and how your team can do the same.Learn more
News and insights from the Web Chefs
Filter by topic
Filter by type
David Strauss elected as a permanent member of the Drupal Association
Congratulations to David Strauss, Four Kitchens co-founder and Drupal scalability guru, who was elected yesterday as a Permanent Member of the Drupal Association. David's goals as a member focus largely on improvements to infrastructure, community-building, and reaching out to other open-source projects. Details can be found in his application: What are the primary goals you would like to work on? I would like to advance the infrastructure for development and sprints by working with the community to drive development and deployment of next-generation (read: not CVS) tools, both for issue tracking and version control. I would like to participate in discussions surrounding the membership software for Drupal Association membership, including CiviCRM (the current tool) and alternatives. I would like to work with major free culture and free software organizations to establish partnerships.
No-brainer shared branch storage on your workstation
For me, my projects are code-based and, hence, mostly a collection of version-controlled branches. So, my "Projects" directory contains a smattering of branches organized into multi-level directory structures. In my last post, I noted that shared branch storage is the key to fast branching, good offline access, and efficient disk usage. I even covered a quick way to get it rolling for Drupal branches. But it's one thing to know how and another to know "best practices," so I'll share how I do things.
Enforcing branch commit atomicity (or, why the git staging area is bad)
With CVS, one of the only repository-wide atomic operations is tagging a local checkout. And not all that long ago, Subversion introduced mainstream users of free, open-source version control systems to full-scale atomicity. Or, at least the ability to be atomic.
Creating common branch ancestry is a hard problem
One of the key features of distributed version control systems (DVCS) is support for divergent development (branching) and then merging. Most DVCS tools, including Bazaar, include rather elegant support for such workflows by embedding metadata about common ancestry into branches. In this post, I'll be focusing on Bazaar.
Distributed version control provides a streamlined alternative to vendor branches
Anyone who's worked with a sufficiently large project eventually ends up establishing vendor branches to track and merge upstream releases. Maintaining these branches is time-consuming, redundant work because everyone who needs a vendor branch of a project needs approximately the same thing.
Dynamically attribute content in Drupal using the Author Taxonomy module
Attributing a story, image, or blog post to more than one person can pose a problem on many web platforms. In the print publishing world, it's simply a matter of adding another name to the byline or tacking "Additional reporting by Sue" to the end of a piece. (Nowhere does the poor designer or typesetter get credit for laying out the page!)
Making the web a better place to teach, learn, and advocate starts here...
When you subscribe to our newsletter!