Case Study: YourPublicMedia.org

Yourpublicmedia.org is a curated news and arts portal built by the Connecticut Public Broadcasting Network (CPBN) that is dedicated to promoting high quality, local/regional content that is created by non-profit organizations from around Connecticut including: Connecticut Public Broadcasting (CPTV/WNPR) and a number of community partners including the Connecticut Historical Society, the CT Mirror (an independent, Knight-funded news organization), the New Haven Independent (a hyper-local news site), and Fairfield University. We are continuously working to secure additional content partners.

The idea that this site would consist of a curated experience was a very important one to us during the concept and design phase - the two national entities that we (CPBN) are associated with are PBS and NPR; two brands that have a long history and reputation for providing such content curation. We didn't want to simply turn this into a river-of-news-type site, and we recognized that neither our internal staff's capacity, nor the capacity of the non-profit groups we would be working with, would be able to add any meaningful value on this front with the for-profit local news agencies already working hard in this area, and auto-aggregated services like news.google.com providing incredibly useful resources to people looking for up-to-the-minute (breaking news) information.

Instead, we chose to leverage the longer-form coverage and focus on more in depth analysis that we consider a core competency, rather than the sort of coverage typically achieved within the breaking-news context.

Henrik Danielsson (TwoD)

He may not be known to everyone yet. Henrik Danielsson (TwoD) suddenly appeared out of nowhere approximately 18 months ago and started to post a couple of pretty solid patches to Wysiwyg module's queue. In case you do not know the Wysiwyg module yet: It allows you to integrate any kind of client-side content editor (WYSIWYG) with Drupal by building a communication layer between Drupal forms and the actual editor(s). Thus, working on the project requires a solid knowledge and highly advanced expertise of Drupal's Form API, Filter API, JavaScript, and lastly every individual editor library.

Redesign Update: Sprint 2 and 3

The Drupal.org redesign team has made significant progress in the two sprints since our last update. Since beginning work with the contractor team, we have completed over 50 issues related to the Drupal redesign. We’ve also created a volume of documentation and posts related to our community initiatives and the redesign implementers group. We also presented a panel session, held BOF and sprinted at Drupalcon Copenhagen.

If you’re interested in looking at the work that we’ve done, it is all visible in the issue queue tagged with “drupal.org redesign”. You can also view our progress on http://redesign.drupal.org [user:drupal, pass:drupal]. Finally, you can also check out a video showcasing some of our progress.

Isaac Sukin

Hi, I'm Isaac Sukin, and I'm posting here because I hope that the story of how I got involved with Drupal can encourage others to get involved as well.

Drupal.org Profile: http://drupal.org/user/201425 (IceCreamYou)
CertifiedToRock: http://certifiedtorock.com/u/201425
Personal blog: http://www.isaacsukin.com/blog
Other blog: http://www.mediacurrent.com/user/blog/isaac%20sukin
Twitter: http://twitter.com/IceCreamYou

About me

Our new Drupal Code of Conduct

As our community grows, it is imperative that we preserve the things that got us here; namely, keeping Drupal a fun, welcoming, challenging, and fair place to play. The new Drupal Code of Conduct (DCOC) states our shared ideals with respect to conduct. Think of this as coding standards for people. It is an expression of our ideals, not a rulebook. It is a way to communicate our existing values to the entire community.

Our friends at Ubuntu have blazed a brilliant trail in this area. They use Drupal as their CMS, and in turn we have embraced their Code of Conduct. This code of conduct is essentially identical to that used by Ubuntu, except that the name of the project has been changed, and the conflict resolution process has been removed since we don't have one.

The DCOC has been under discussion for several months on groups.drupal.org and discussed further at Drupalcon Conpenhagen. Folks who are interested in talking more about the DCOC should do so in the Drupal.org Policies group.

The short version:

  1. Be considerate
  2. Be respectful
  3. When we disagree, we consult others.
  4. When we are unsure, we ask for help.
  5. Step down considerately.

Case Study: StyleWorks Premium Photoshop Styles

StyleWorks - Premium Photoshop Styles
This past March, I decided it was time to put my skills as a Drupal developer to use and launch a new online business. I knew early on that I wanted this business to be product-based, and after several weeks of playing with different ideas, I settled on selling premium Photoshop layer styles. It was the perfect opportunity to combine my love of photography and Photoshop with my passion for web development and Drupal.

Several months of product development later, StyleWorks was born. The site runs on Drupal 6, and integrates with FastSpring for e-commerce capabilities.

Designing the site: To Zen or not to Zen?

After iterating through several hundred designs in Photoshop, I finally had the look I wanted to go with, and it was time to make it come alive in Drupal. But first, a key decision had to be made: Start from scratch, or go with Zen?

Pages

Subscribe with RSS Subscribe to Drupal.org RSS