Brazen Careerist: A Career-Focused Social Network for Young Professionals

Brazen Careerist is a premier Generation Y career-based social network. Our goal is to help shift job seeker's and the recruiter's approaches to focus on social strengths and ideas instead of just experience. We have been using Drupal for almost two years to help us scale and add social features rapidly. Using it as a platform has been crucial to our success and will continue to be in the foreseeable future.

Most recently, we gave our users new and powerful ways to participate in idea-based conversations. We also rolled out innovative integrations with external social-networking sites and revolutionary ways to display your online resume. We'd like to showcase some of these new features to the Drupal community, and hopefully get some more great ideas from you guys! redesign implementation update, and sprint March 19th

The redesign continues to progress. This is great news and a morale boost for everyone involved.

Since our front page post on February 3...

Drupal 6.16 and 5.22 released

Drupal 6.16 and 5.22, maintenance releases which fix issues reported through the bug tracking system, as well as security vulnerabilities, are now available for download. Drupal 6.16 also fixes other smaller issues.

Upgrading your existing Drupal 5 and 6 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 6.x release series, consult the Drupal 6.0 release announcement, more information on the 5.x releases can be found in the Drupal 5.0 release announcement. Drupal 5 will no longer be maintained when Drupal 7 is released. Upgrading to Drupal 6 is recommended.

New Drupal Book - Drupal 6 Attachment Views

Drupal 6 Attachment Views, by me, J. Ayen Green, is my second title from Packt Publishing. It is aimed at Drupal web site developers who want to build more functionality and interaction into their views, but aren’t ready quite yet to take on panels. As a reader of, you can receive a 15% discount (see below) and benefit the Drupal Association!

I wrote this to be a fun, informative, hands-on learning guide. It uses actual case study that was developed in parallel with the book’s writing. This guide presents purposeful and interactive examples that build on each other. Clear, concise instructions and practical examples help you to learn quickly to use this exciting feature of views.

Case Study: Augusta Chronicle

The Augusta Chronicle, the flagship newspaper of Morris Publishing Group, recently relaunched its website on the outstanding Drupal framework.

Morris first began using Drupal in 2005 with the launch of, a blog-centric community website coupled with a free daily newspaper. In 2006 it adopted Drupal for both news and blogs at, the website of the Savannah Morning News. Both newspapers won Digital Edge awards for innovation in user participation.

Since then, the digital media arm of Morris Communications, Morris DigitalWorks, has developed a robust digital newspaper platform built on Drupal 6, to eventually power all 13 of its daily newspapers. Morris also uses Drupal for its radio stations and, a national specialty site for women.

Reader Participation

Morris has made a commitment to make their online platform a dynamic arena for reader participation and contributions. Readers are encouraged to comment on stories and blogs, and, on some papers, are encouraged to create their own blogs on the site. Journalists are expected to post news online immediately and to interact with the public, and they need to be able to do it without learning HTML or tools such as FTP. These requirements made Drupal a natural choice.

Drupal 7 status update and release plan

Drupal 7 is moving along nicely, and is becoming increasingly stable. We just released a second alpha release, fixing a number of critical bugs, following our initial alpha release in January. Alpha releases are to give Drupalistas something to download and test, so they can report and help fix bugs.

When will we switch to betas? We will switch to betas when the upgrade path from Drupal 6 to Drupal 7 is working. Once we hit beta, we will become increasingly strict about accepting any more changes and we'll also commit to making HEAD to HEAD upgrades work.

Finally, we'll start rolling release candidates once the number of critical bugs is zero (or close to zero). To help us focus on critical bugs, we're working on adding a 'major' severity level to our ticketing system, making the options 'critical', 'major', 'normal' and 'minor'. 'Major' bugs would be really bad, but not necessarily block a release. For example, bugs that don't prevent Drupal from working, or that only affect a fraction of the Drupal population would be prioritized for fixing in follow-up releases. Critical bugs are those that badly break Drupal, or that are a major regression compared to Drupal 6.


Subscribe with RSS Subscribe to RSS