The workshop portion of the Drupal Career Starter Program wrapped up in mid-December, just in time for participants to catch their breath and enjoy the holidays before embarking on the second phase of the DCSP. 15 of the 18 students are currently beginning internships with organizations around the United States in an effort to further their education and training to the point where they can begin careers in Drupal.
Conception and Funding
Anello Consulting (parent company of DrupalEasy) conceived, designed, and implemented the DCSP as a way to help Brevard County, Florida (home of NASA's Kennedy Space Center) retain some of the over 7,000 skilled workers who lost their jobs as part of the retirement of the Space Shuttle program. Brevard Workforce funded the program and has been a fantastic supporter and champion of it.
"Well paying jobs are available now, and growing fast in areas of ICT that may not be familiar to the general population, nor have formal certifications," said Lisa Rice, president of Brevard Workforce. "The data on the growth of Drupal, and the tremendous opportunity for those people who learn the software and gain experience convinced us we have to step outside the box a bit so we can offer our workforce, fast turnaround programs that provide well-paying options quickly" (See the complete Brevard Workforce news release).
Anello Consulting is proud to announce the start of the first session of our Drupal Career Starter Program (DCSP). This Drupal training and internship program is designed to teach the basics of Drupal, including a strong foundation on community involvement and practical experience.
The DCSP kicks off on October 4 on Florida’s Space Coast to give laid-off IT-savvy Space Shuttle workers an opportunity at new careers. Brevard Workforce, the local workforce development board funded by the state of Florida, is using federal grant funds to provide scholarships, and potentially paid internships, for the 19 carefully selected participants. The goal is to keep these skilled workers in the area while expanding their skills from the shrinking aerospace industry to self-guided, opportunity-rich careers in Drupal.
I've been heads-down for the past 4+ months working with Bonnier in an effort to migrate FieldAndStream.com and OutdoorLife.com to Drupal 5. I'm proud to say that earlier this week, both sites went live! In case you're not familiar with Bonnier, they're also the parent company of Popular Science, a well-known Drupal site.
As a contractor to the development team, I took part in adding new and expanding existing features to the sites. The previous incarnation of both sites was based on a proprietary content management system that had reached its limits.
The two sites have virtually the same feature set, but each one has their own custom theme and vocabularies (and not just in the Drupal-ese meaning of the word!) Therefore, most of the work we did had to be written in a generic enough way to work in both places.
It is often desirable to add a node count to the title of a view to help users gauge how many nodes have been returned - especially when using exposed filters.
In Views 1.x, this is a fairly simple process using the "hook_views_pre_view(&$view, &$items)" function (documentation).
Let's say you have a view that displays titles and authors all content of type "story" on your site in table format. Furthermore, you've exposed the "Node: Author Name" field as an exposed filter for the view:
Collecting and using user profile information has always been a popular aspect of the Drupal module scene. The Profile module (part of Drupal core) has always been a relatively straight-forward way of collecting additional profile data about users, but its lack of default Views and CCK integration has been problematic for most users.
Saving user data as nodes has been possible using a variety of methods for quite a while, but it seems that with Drupal 6.x, things are coalescing around the Content Profile module. This allows you to set a particular CCK content type as a user profile (the module actually creates a default "profile" content type automatically for you) - thus gaining all the advantages of CCK and Views (and their associated universe of modules) when dealing with user profile data. This is extremely powerful and lets you do all sorts of wacky things with your user's profile data (don't be evil).
This article talks about the (relatively easy) process of getting the Content Profile module configured for a Drupal 6.x site. Then, I'll go through the process of making one of the profile fields available to Views and a template file for use when displaying a node. This might be useful if one of the Content Profile fields you're collecting is a short biography of the user that you want displayed within any nodes the user has authored. Then, your standard node view can look like this: