Danielle:
Well, it's been a few weeks since the 1st of the year, so of course most of us are either dreading or hoping for the question: "How are you doing with your New Year's resolution?" Today, I'm excited to report on one of mine!
Dave:
A danger I am constantly battling is becoming too tied to my tools. By tools, I mean the things I use to get work done. It could be Photoshop, CSS, a CMS, pen, paper, anything I use to do my job. Why is this so dangerous? Aren’t tools there to make our lives easier? Well, they are, but we often lock in out toolset too early on projects and it ends up hurting our product in the long run.
Erik:
We had our first Austin Apps sprint last week and got quite a bit done. We had 12 people from Phase2 Technology, LevelTen, Four Kitchens, Mediacurrent and Pantheon all had people at the sprint. Thanks to Four Kitchens for helping us provide a space for the Sprint.
Frank:
Having spent an amazing few days in Austin for the Apps Sprint we came away with some even better news than expected. After a few joint development sessions with the great folks of [Pantheon] we are thrilled to announce that OpenPublic, OpenPublish and OpenAtrium are now available on the Pantheon platform via a one-click install from your Pantheon dashboard.
Josh:
The modern day cut-up man/woman/shop is dead when it comes to a dynamic system. It’s sad because no obituary was written nor news alert on AP/CNN posted, but it’s true. The theory, that a company or individual needs to ‘cut-up’ the design composition into a semi-working website before full development of the backend system is highly unnecessary and inefficient. In a time where budgets are even tighter than they have been in years past and a need for continual push around efficiency in development, eliminating the process of cut-ups before development needs to die quickly.
Patrick:
Just a small but important release, security release for Date (SA-CONTRIB-2012-004), and multiple community patches!
Karen:
Phase2, Level Ten, 4Kitchens, and others come together to improve the Apps and Appserver modules this Friday.
Danielle:
It's been about three months since I joined Phase2 as Community Manager, and I have really appreciated getting to know the needs of the community around Phase2's products and contributed modules. Thank you so much to those of you who have offered your honest -- and at times colorful! -- feedback. Truly, this is how we get better, move forward, and work together. In my last post, I talked about how we planned to respond to the community and about our goal to communicate more about our module contributions and product work. So I'm here to fulfill that promise.
Mike:
One of the most common challenges with multiple-site web architectures is determining the right level of interaction between the sites. In particular, one of the most common requirements is for some kind of content sharing. The problem with "content sharing" is that it is usually given as a pretty vague requirement at first. It's like a home storage problem - you could be talking about building a second floor on your house, putting up a shed in the backyard, or buying a storage bin from IKEA. Here, I'll try to distill some of the issues and get you asking the right questions when you encounter the problem of content sharing across multiple websites within a web architecture.
Mike :
A new method for overriding Features in Drupal is presented that works for all types of Features.
