SEO Expert Blog

This is a Views summary style plugin. It allows you to embed the results of a View with each argument in the argument summary. You may use a different display; for example, you might build an archive View with a Year+Month argument, that lists the four most popular nodes for each month in the summary, but that lists nodes in date order when you click through to the argument. Usage: Set the "argument summary" style -- to "Peek Summary" Configure the style -- choose a display plugin, set paging Example peek_summary output The same View, with an argument (not peek_summary output) Caveats: You should limit the number of arguments displayed per page (in the argument summary). A View is executed for each argument that is rendered. You should use Views' caching, at least for the display you use for peek_summary. The peek_summary display must have the same arguments as the argument summary display--they may or may not be the same actual display.

---

Yesterday afternoon we made a new Alpha release of Pay for Drupal available. What is Pay you might ask? At it's core Pay is a modular API for accepting, processing and tracking payments. If you want to be able to accept payments on your Drupal site for simple transactions with out "Add to cart" or complicated checkout procedures then Pay is for you! To learn more about Pay, take a look at our blog post last week and check out the project page. As part of the Pay API we provide a set of base classes which can be extended to provide payment forms or payment methods and gateways. Out of the box we're currently shipping with support for Authorize.Net and PayFlowPro payment gateways. While at DrupalCon Copenhagen I began adding support for PayPal Website Payments Pro and Standard. While still under development some of this work is now available for testing in the latest alpha.read more

---

Quicktabs, the Drupal module that allows you to create blocks of tabbed content such as views, blocks and nodes, and which I co-maintain with Csuthy Balint (Pasqualle on drupal.org), received a couple of significant changes recently. One of the changes, allowing Quicktabs blocks to be exported just like you export Views and other CTools exportables, had been submitted as a patch by Young Hahn of Development Seed a shamefully long time ago and I had procrastinated about certain aspects of it. But building client websites at Work [at] Play, the dev team has been making huge efforts to keep everything in code, and it became increasingly clear to me that Quicktabs' lack of exportability was a Bad Thing; my fellow developers were surely casting sidelong, disapproving glances at me as its author, wondering what on earth the problem was. Yay - Quicktabs are now exportable! So I have created the 6.x-3.x branch of the module in order to accommodate this change.read more

---

It's hard sometimes to find certain module if you're using a bunch of modules. This module helps you to find the module faster.

---

Have you ever wonder how many Drupal websites are there? What about Drupal modules and themes? Ever wanted to know how has Drupal evolved since it was created? Find out all you ever wanted to know about Drupal, but were afraid to ask. Take a look at this fast overview of basic facts about Drupal, print out a card and use it as a handy resource to promote the awesome features of this powerful CMS. You can even download a version for t-shirt and become the coolest geek on your next meetup or Drupalcamp. Questions covered:read more

---

This module is an in-line editor used to edit the body field of specific content types and blocks using Mozilla's Mozile editor. In essence, this editor should work on all browsers, but it's best used with Mozilla Firefox. Please consider donating to further the development of this module. Maintainer: Waleed Qadi from O-Minds. O-Minds can be contacted for Drupal services via the contact form on our website.

---

This is the question I got at many events where I presented about localize.drupal.org. We've just rolled out support for suggestion exports for translators about a month ago to make quality control and management easier, but that does not help people much who are just looking to download what's available. I've also announced about three months ago that translation downloads were becoming stable and continually generated in a nice pace. However, the usability of those downloads left a lot to be desired. When looking at project pages on the site, you were shown a bland list of links to major Drupal versions the project was compatible with which all led to a long list of filenames on an FTP browser frontend. Also, some files being months old looked shocking given I've told you the downloads are now stable and up to date.read more

---

This module provides Moodle SCORM (http://www.moodle.org) integration for Drupal using CCK functionality. It depends on the CCK and the FileField module. This first version focuses on displaying SCORM contents and logging events for each user. Analysis of all logged events will be part of a later release. The module enables the user to upload a SCORM compatible Zip file during node creation process. The user can decide if the SCORM content should be opened in a new window or if it should be embedded (width and height parameters are available). The module is developed during the project “E-Learning 2.0 in craftsmanship trainings” funded by the Federal Ministry for Education and Research (http://www.bmbf.de/) and the European Social Fund (http://www.esf.de/). Project maintainer is the German Center for Aerospace (http://www.dlr.de/). The module is developed by Servit Open Source Solutions (www.servit.ch) and is adjusted by the project team (http://q-online.de/kontakt). The module is a part of the community portal which is currently in development. Further documentation will be published soon. Module maintainers are: University of Duisburg-Essen – Chair of educational media (http://www.mediendidaktik.de) Servit Open Source Solutions (www.servit.ch)

---

Since a few months I try to have a closer look at Drupal 7. After the release of Alpha 6 I decided to start a clients project based on Drupal 7. Two weeks ago we discovered a more or less strange problem. In Drupal 7, as far as I knew, the profiles module will disappear or integrated in the new field api.  So I thought it would be a good idea to create the user fields as "fields" not as "profile fields". That worked perfect. It was possible to see the fields in the user edit dialog and in the user profile. It was also possible to access the fields via the views module. But ... what is with the registration dialog? Read more

---

I get fed up with scrolling down the modules admin page looking for the right module to enable/disable. This module injects a tiny javascript into the page head that adds a drop down to local menus. This then allows a quick jump to sections in the page. read more

---

The next major addition to Translation Management will be the addition of a reporting tool. This reporting tool will answer questions like these: How are translations progressing? Who's the French translator, responsible for the delays? Which urgent documents are still not translated? Are all marketing documents for product X translated? How much work did we send to translation service Y in June? To answer these questions, and more, we're setting up a Translation Analytics tool, which would work very similarly to the famous Google tool for Website Analytics. The idea is that you can define special taxonomy for documents, like urgency, budget code, project, etc. The Translation Analytics will identify these fields and create database entries for them. You will be able to drill down through the translation statistics and create reports that give you the information you're looking for.read more

---

Moshe Weitzman talks about the new Page rendering flow and hook_page_alter() functionality in Drupal 7, which allows a more control over what appears on each page load. This will enable one-off customizations to the page loads in a much easier way. He talks about how Drupal 7 themes can now implement alter hooks, and how the page render arrays use the same approach as forms and nodes. Weitzman suggest that if you're new to the concept of render arrays to check out either the Pro Drupal Development book or some of the other training resources such as a workshop or other training videos.read more

---

Provides a shortcode API and basic shortcodes through Drupal filters. Initial works based on the Wordpress Shortcode API but I rewrote it for Drupal and solved the nested tag problem. Now you can nest tags (same tags too) no need special recursion handling. All tags are themeable and new tags can be provided by other modules.

---

This module's audience is developers who require machine names for taxonomy vocabularies, including views support. This module allows existing (and new) installations to continue using the Drupal 6 taxonomy API while gaining the benefits of vocabulary machine names. As such, it should play nice with any taxonomy related modules (such as those that provide import / export features, etc...) Background Taxonomies are a bit of an issue to deal with in Drupal, specifically in terms of using them in install profile or update hooks, team development, and deployment through environments. There are a few modules out there which try to get around this issue. However, they are limited in a number of ways. Currently there are 3 methods I can see in trying to solve this. This module goes with #3. Use existing modules (such as features_extras or exportables). This provides taxonomy (among other) machine name support, however, it can require multi-module dependencies, and typically require additional calls while programming. As well, there is typically no views support to remove "vid"s from view exports. read more

---

TagsDrupal PlanetIt’s by sharing knowledge with others that the Drupal community continues to grow and flourish. In that spirit, DrupalCon Chicago will be offering pre-conference training courses and workshops to attendees interested in gaining additional hands-on knowledge on a variety of topics related to Web and Drupal development. We are looking for talented, professional trainers who can share their knowledge at pre-conference training courses and workshops. These courses will take place on March 7, 2011, before the main conference begins and will be held in the classroom facilities of the University of Chicago’s Gleacher Center, located steps from the conference venue. We are looking for sessions and workshops that touch on all aspects of Web development, from Drupal site-building, module development, user experience design, and beyond. read more

---

This is a howto for wrapping a div around a few of your view fields (and not others). This is useful, for instance, for being able to group all one's content so that it floats left but does not float around an image. EDIT: This technique is a good intro to views templates, however, an easier way exists, mentioned below in the comments by Sr. or Sra. Anonymous. Thank you! Just use two "Global:Custom" fields, one before and one after, the fields you wish to enclose, and the fields between the two "Global:Custom" fields will be wrapped in a div. That said, this post is still useful for learning about views templating. Carry on. First, create a template for your view. Create a template file in your theme directory with the same name as the views and paste the code from the level of specificity that you desire. For more information, read this introduction to views template files. Here is the code from the stock Row Style Output:read more

---

Earlier this year I delivered a series of talks and workshops on how to use "advanced" modules to create Drupal layouts without ever having to crack open a PHP file. The slides from my CMS Expo talk "Advanced Design for Drupal" were uploaded to SlideShare. Now, for the first time ever, the notes from this talk (which became a three-week workshop) are available for sale.read more

---

Chuck Norris ordered a Big Mac at Burger King, and got one. Module Description Minimal feature set: creates a block with random Chuck Norris "facts". Could be used to display in admin UI to prevent admins from falling asleep while administering boring Drupal sites. Soliciting Ideas We are pretty sure Chuck Norris deserves a dedicated module and have some ideas about what the module functionality should be. However, Chuck Norris is too much for a single brain to comprehend, therefore we ask the community to contribute ideas for the Chuck Norris module. cheers.

---

John Albin Wilkins (aka JohnAlbin) talks about some of the new extensions to the theming system that are new in Drupal 7 including render elements, hook_page_alter(), show, hide, theme_get_suggestions(), and improvements to theme_links(). He also talks about the theme administration page overhaul, how it's now a lot easier to create "mega-menus" dropdown panels when hovering over the primary navigation, as well as another presentation that Palantir gave on previewing Drupal 7.read more

---

Flag Lists is in the early stages of development and should not be installed unless you're helping to work on it. Please help! Flag lists allows a user to create personal flags that only he can use. For example, on a site with a content type "cars" you could make one list called "Favorite front-wheel drive cars" and another for rear or 4-wheel drive. Requires Flag version 2 and the patch here #750578: Patch creates hook_flag_delete() and uses db_rewrite_sql on flag_get_flags() but this all may change.

---

Reinvigorate is a simple, real-time web analytics + heatmaps solution that measures your influence on the web. This module provides an easy to use interface to adding reinvigorate tracking to your Drupal site. Read more at their website. Maintained and developed by: devkinetic. Setup See the README.txt

---

A module that allows you to display your location nodes in the Layar Augmented Reality App. It's a Views based module that uses a style and filter plug-in to create the Layar compatible JSON from your nodes. Create your views and then create a "Layar" node and select the views you want to include in your Layer, View the the node and your Points of Interest URL is displayed. Which you can then use on the Layar website as the server for your Layer.

---

If you read my previous post about converting Subversion repositories to git, you’ll know that to do a proper Subversion-to-Git transformation on a batch of repositories is going to take some time (what with all that command line typing). I had 142 legacy project Subversion repositories lying around I wanted converted to Git and, since I’m lazy, I pulled on my bash boots and wrote me a script to do the work! With the git-svn-migrate scripts I wrote, you can batch convert all of your Subversion repositories in just 3 steps. And I’ve GPLed them and put them on GitHub if you’d like to collaborate and improve them; see the git-svn-migrate project page. git-svn-migrate: a reverse glue factory read more

---

Menu customization in various ways

---

Richard Jones of iKos gave a presentation on simplifying and streamlining the development of Drupal sites. His team observed that they were creating the same basic sites over and over again. To this end, rather than starting from scratch each and every time, the team created basic sites to start from and rapidly built out the basic site for a client in several weeks. This allows the client to start entering data early in the process - which means come theming time, you are working against real client data. This is a plus when you are trying to achieve the results your client is seeking. In the iKos model, design comes last and is somewhat subject to the functionality that has been developed. iKos set the the goal to reduce Drupal development time by 80% - to radically reduced the repeated effort that the company engaged project after project. They created a model of a site "startpoint" that begins each new client effort. read more

---

The steps for programmatically creating a node are: Create a PHP object representing the node data Save the object using the node_save() function While the mechanics are simple, there is an important responsibility involved. The Drupal work flow does data validation before calling the node_save() function; node_save() does no validation. By calling node_save() directly your code takes the responsibility for providing valid data. Drupal 7 Changes A quick note for those of you familiar with Drupal 6. You'll notice two changes in Drupal 7: Body Field Is No Longer Special In Drupal 6 the body field was special. Specifically, it had a different data structure than other fields and it always existed, even if it wasn't used. With Drupal 7 the body field is a standard field provided by core and is truly optional. Language Language specification is required for the node and some fields. Basic Node Creation The following code assumes an unchanged Drupal 7 Standard installation and will create a Drupal 7 article node. read more

---

I was the first woman at any DrupalCON, the only woman in Antwerp. Until the brouhaha over the keynote, I never really thought about why I went there in the first place. But the decision to travel there was triggered by a tiny and important event, so I'd like to share it. I had been communicating back and forth with Matt Westgate about some e-commerce functionality. At the end of one of his emails, he tacked on the following: PS - You headed to Belgium? This question wasn't a part of an outreach initiative to involve women in open source. I doubt he questioned that my interest might be affected by my gender. It was simply, "we're having an interesting conversation that would be even easier to have in person". Before I read that email, the thought of traveling to DrupalCON hadn't crossed my mind. But my response to that simple question was to make it happen! And thus my life was changed. But five years later in San Francisco, when the number of women in attendance had risen from 1 to 300, I was settling into a BoF session when I was presented with another innocuous question: This is a technical BoF. Are you sure this is where you intended to be? This question was not intentionally harmful. It was an offer of help, in a tone of "hey, do you need some help finding your way to a session you might enjoy more?". But this "help" was based on the unconfirmed likelihood that I might not belong in a technical session. If I was new, I might have doubted my own aptitude and diminished my participation. This post is not about lambasting the BoF guy or calling out the similar encounters we encounter every day, such as asking if I'm on the documentation team, a designer, or just there with my partner. This happens regularly and quite cordially, usually perpetrated by someone who you wouldn't call 'sexist'. But good or bad, tiny exchanges make up our community as a whole, and have a much broader impact. What if Matt, without any derogatory judgment, questioned my interest in showing up in Antwerp? What if he hadn't bothered to ask? Five years later, would I be contributing to Drupal, running a company that employs other Drupal contributors, and helping to support the local Drupal community? More importantly, what if more people reach out to others in similar ways? How many others would there be out there doing more good for Drupal? Setting aside the topic of what is/isn't "offensive", how do we focus on being more inspirational, and asking questions instead of making assumptions? Drupalchix

---

Tue, Aug 31, 2010 by Alla Sometimes it is really hard to show only the needed nodes in the needed order using views only. Here are some examples when you need to give a Content Manager (CM) some control over the nodes that will be displayed by the view: - you need to promote on the front page some content Item (for ex., some new Game) and want the CM to be able to change it through the UI any time he pleased - you need to show the newest Games in the block (sorted by some date), but you need to give the CM ability to override this list and show a couple of Games of their choice at the top of the list (following by rest of the newest Games sorted by a date) - you need to show a list of Items of some Type, but to make sure that some of the Items (from some "black list") will never be included into this list. The Nodequeue and Views modules will be a very useful combination here.

---

I've now been working professionally in Drupal for a year and have learned a lot about it; I have some patches into contrib but I've not really done much with core other than some simpletests I was too shy to commit at Drupalcon and some comments trying to help people out on d.o. Prior to my stint as Drupal programmer I was a hardcore Ruby on Rails developer for about 4 years. Over the last two years in particular I've learned a lot about frameworks and I'd like to share an observation about which framework feels right to me for which situations and why.

---

Like any Drupal themer, I've done my share of grumbling about the frequently ridiculous level of nested divs with dozens of classes. I'd heard some people mention a module called Semantic Views, but I never really understood what it was for until I found this video. If you don't understand what the big deal is either, take the four minutes to watch. It's a total "ah-ha!" moment. I'm happy to say that I just used Semantic Views for the first time on a client site, and it's just as awesome as everyone says. It saved me a ton of work and let me get exactly the markup I wanted, even while working around Chuck's nested views.

---

Drupal 7 introduces a number of new apis and with those comes new jargon. Untangling that could be daunting. I'll try to briefly sketch what is what and relate it to terminology outside of the Drupal world. This post is a work in progress, I am regularly revising the text from feedback. Note Revised paragraph order and wording, clarified wording of definitions, added references, corrected glitches Entities Bundles Fields Field Instances read more

---

Emma Jane Hobgin (aka emmajane) gives an overview of her DrupalCon San Francisco presentation on PHP for Designers. She talks about the importance of pattern recognition and forensic coding, some helpful modules such as Devel Themer as well as some of the basics of Drupal theming with tpl.php files and preprocess functions within the template.php. For more information, be sure to check out her PHP for Designers presentation.read more

---

The Views Dynamic Fields module provides a filter for use with Views module. This filter allows the user to pick and choose which fields to display for a rendered instance of a view for that user. This provides a customized view instance for each user. read more

---

When I first realized that I needed a version control system, the best system at the time was CVS. (No, really.) Subversion was nearing 1.0, so I waited for its release and then used it everywhere. Well, that was 2003. Time for a change. This past year, it became obvious that there were many Git users within the Drupal community, so Drupal has decided to move to Git. Since then I've started learning and researching the best ways to convert all my development to a Git-based workflow. So far… it rocks. read more

---

Are you writing and using environmentally friendly software? Have you ever thought of the impact on the environment for the software you've written? Working in front of a computer it can be easy to overlook the impact on the environment due to what were creating. It's not like drinking a beverage out of a styrofoam cup (they don't break down). But, there is an impact. As Internet usage grows in leaps and bounds we need to start taking a closer look at that impact and doing something about it. Why Performance Is Green Why did Facebook start using Hip-Hop? According to their blog, With HipHop we've reduced the CPU usage on our Web servers on average by about fifty percent, depending on the page. Less CPU means fewer servers, which means less overhead. When we have less servers we use less power, we need less space in buildings, less servers need to be built for our tasks and our overall footprint is smaller. Think about it like this. We buy energy efficient appliances, we talk about turning lights off when we aren't using them, we look at energy efficient cars, and we think about being environmentally conscious. So, why not extend this to what powers our websites. read more

---

It is that phase of my life! I'm just turning 30 in a month, working with Drupal for 7 years and just had my third Acquia anniversary a week ago. Time to look back and evaluate how things went, all the good and bad things; even better if the wisdom can be shared with others. This was part of my thinking when I submitted the session titled "Come for the software, stay for the community" for Drupalcon Copenhagen. I was interested to distill and share how Drupal came to be as unstoppable as it is, what core values lie behind it, so someone coming fresh can understand and integrate with these. When Dries Buytaert started Drupal he made a few key decisions which launched the project and kept being governing principles ever since. First of all he decided to make it free and open source, and release it under the GPL. The choice of one single license helps you use all the Drupal components together without the requirement to consult lawyers. Also, the choice of GPL in particular ensures that derivative works are distributed in the open as well.read more

---

Ryan did a session on the new version of the D7 Commerce Module. He was the original writer of the Ubercart package - a main stay of ecommerce sites in Drupal 6. His self deprecating humour at the beginning of the session was charming as Ubercart was his first segue into many aspects of Drupal and it has become the defacto leader of the pack for Drupal ecommerce sites. His new offering is looking very slick, making use of fields in core for example, and while Ryan tells us it isn't quite ready for primetime (he's still building out features) it looked pretty good. Video from this session is below in seven sections. The original first video was only 4 seconds long. read more

---

I've been promising benchmarks for the Display Suite module after every presentation I gave so far. It took me a while to get a good setup but now it's here. I've used the demo site as a start, so there are a lot of modules enabled for this test. Views, panels, fivestar, heartbeat, comment, taxonomy, location, gmap, imagecache are the most important ones since they all integrate with the ecosphere of Display Suite modules. I added a new content type called 'benchmark' and added 14 CCK fields to it: 4 textfields, 4 textareas, 2 images, 2 filefields, 1 node reference and 1 user reference. It also has a title, body, 2 taxonomy fields, a fivestar widget and a couple of comments. Depending on the test, the complete set of modules integrating with Display suite are enabled or disabled. These include ds, ds_ui, cd, hds, nd, nd_cck, nd_search, nd_fivestar, nd_location, nd_switch_bm, ucd, ud and vd. You gotta love small project names right ? <!--break--> Desktop The first test was ran on my Fedora Core 13 desktop - Intel Core Quad, 2 GHz, 2MB RAM with php 5.2.13 and eAccelerator - ab sending 100 requests with 5 concurrent users on a single node and page caching disabled.read more

---

aCoffee theme is the one-or-two-columns Free Drupal theme with a fixed width. There are some icons for Twitter, RSS and a forum and a favicon. Rich green and warm brown colors create an impression of comfort. This theme is perfectly suitable for a blog, websites of cafe and web-cafe-guides with news, reviews and comments. Features: Columns: 1 or 2. 12 regions. Cross-Browser tested: Firefox 3, Internet Explorer 7 and 8, Opera 9.5+, Google Chrome and Safari 3 and 4. Width: Fixed, 970 px. Color: green, brown. Valid XHTML and CSS.

---

Translating interface strings is always a painful process. Actually, it's difficult to achieve in many content management systems, not just in Drupal. Unlike node contents, interface strings can come from many different places. They can be part of Drupal core, from modules, themes or dynamically generated by the site's admin. The hard part is locating these interface strings which appear to site visitors and translating them. To visitors, it doesn't really matter where the strings come from. All user-facing strings must be translated, for the entire page to appear in the right language. Choosing Strings With The Localization Client Module The localization client allows searching for untranslated strings easily. For site admins, the most important feature is the ability to spot strings as they are used on public pages. Once installed and enabled, the Localization Client opens a panel at the bottom of public pages. These pages are viewable to admins only and not to site visitors. read more

---

Media: Comedy Central is an Embedded Media Field for comedycentral.com videos. It should support videos from any comedycentral subsite (e.g. http://www.thedailyshow.com/)

---

Media: TED is an Embedded Media Field provider for ted.com It accepts both the default TED embed code and the Wordpress.com shortcode (e.g. [ted id=319] )

---

The Ban and Unpublish module makes it easier to clean up after registered spammers and other problem users by implementing a bulk operation that appears at Home > Administer > User management > Users. read more

---

There are a couple of coupon modules that I found and tried for Ubercart 2.x. However, I found that they are either too fancy, or hard to understand. Normally, a coupon (as advised by Ubercart) are relying on line items, here I take a different approach. In this module I treat a coupon as a product node with a negative price. This gives several good things: Since a coupon is a node (because products are nodes), you can have a themable page for a coupon, so you can print it out Stock can be used to check if the coupon is (un)available The coupon is attached directly to the order, so you don't need to mess around with the line items - the sum that goes to Paypal is already discounted (somehow with the line items the order lifecycle was quite obscure to me) The other coupon modules that I've tried and didn't adopt are: Coupon System UC Discounts I'm looking forward to Drupal 7 and Drupal Commerce module, so if anyone is interested to take over the development of this module, you're more than welcome!

---

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: Be considerate Be respectful When we disagree, we consult others. When we are unsure, we ask for help. Step down considerately. read more

---

The Menu Node Action module creates an action that can be configured to add a link to the node in a menu. read more

---

“Eau” is a new fluid-width theme in development. For the moment this is a placeholder to reserve the name.

---

Comment and Share with friends.

---

Allow Gallery Assist to load and show flickr images.

---

Overview Views Flag Refresh allows site administrators to configure which views are refreshed automatically via AJAX when certain flags are selected. This is useful when you have a view that filters by flagged content and you want the view to be refreshed automatically when content is flagged or unflagged elsewhere on the page. The Views Flag Refresh module also allows administrators to select widgets that alter the display of the view while it is being refreshed. Some examples are displaying a throbber image or textual message alerting the user a refresh action is being taken. By implementing the API, developers can add additional widgets with ease. Configuration Views Flag Refresh is configured entirely through the Views interface. After installing the module, additional settings will be available to the Use AJAX option in each display's Basic Settings tab. Related projects Views: Provides a flexible method for Drupal site designers to control how lists and tables of content are presented. Flag: A flexible flagging system that is completely customizable by the administrator. Maintainer Views Flag Refresh is developed and maintained by Chris Pliakas. read more

---

Betting system is a set of modules that can transform your Drupal site into betting shop. It's mainly designed for course betting. For better extensibility is created with more modules. It also defines own hooks. The core of the Betting system adds the following: allows administrators to define basic parts for betting brings two new content types: Abonents and Games. Without abonents it is not possible to create games. Abonents are players (teams) that attend a game (for example Manchester United in the English Premier League, or Roger Federer in tennis). users can bet on games, but only if they have points each Abonent and Game have to be in a sport (which are defined by the Taxonomy module) administrators can set many options (like eventualities) in the Settings of the Betting System Betting system also contains other smaller modules for functionality extension. Betting system relation allows the creation of relationships between games (like a half in a soccer game) Betting system flexible eventualities allows administrators to create special kinds of games, that do not have attending of Abonets and administrator can type own eventuality of result. read more

---

One Hour Translation Module provides one click professional Human translation to your content. Backed by more than 8,000 and serving over 50 languages, with the One Hour Translation open source human translation module your content can be translated to any language with one click. The One Hour Translation's translation module handles all aspects of your content including titles and other information used by CCK. With the module you can have your text translated by humans in near real time eliminating the manual handling process of the translation. No more sending the content via email and waiting for days to get the results. Using the module, the text is automatically sent for translation and posted back in the local version of your blog. On Average, a standard, 500 words English post is posted in the Spanish or other main language in a matter of hours from the time the original post was published. Service highlights: Professional Human translation in near real time Over 50 languages served to date 24/7 service and support at no additional cost Flat price per word independent of languages and time of day Super fast service at no additional cost Increased exposure to new audience Immediate SEO value at low cost Increased income from advertisement read more

---

Stream is the default theme for the NodeStream profile. Stream uses the Precision base theme which is a theme designed for use with Panels Everywhere.

---

This project is a wrapper for all the core features that is distributed with the NodeStream profile. Although these features aren't meant to be used outside of NodeStream, the goal is to be Kit compliant so features independently can be turned on and off. For bug tracking, please refer to the NodeStream profile issue queue.

---

The PM adv module extends the Privatemsg core module. What exactly makes Privatemsg advanced? Please read the FAQ in the documentation. Additional modules This module also contains the module Privatemsg advanced views. The PM adv views module extends the Privatemsg core module with extra views functionality. Dependencies The PM adv module: Privatemsg The PM adv views module: Privatemsg, Views If used version 2 of the Privatemsg core module must be enabled its submodule Block user messages. Cooperation The PM adv module cooperates with the modules Author Pane Conclusion From the date on which the Privatemsg module realizes the functionalities of PM adv and PM adv views, is not necessarily this project.

---

Antonelli is a fluid width subtheme for Bartik, the default core theme for Drupal 7. By default Bartik is fixed width - Antonelli changes the layout to fluid (percentage based) with fixed width sidebars. Antonelli does not change any styles in Bartik - it only changes the layout from fixed to fluid. A fluid with option was proposed during the development of Bartik, however the request for this option came too late in the Drupal 7 cycle. Due to the lateness of the proposal it was decided to place a fluid width subtheme in contrib until Drupal 8 when we can again discuss the inclusion of a fluid width option. The original issue is here: #846542: Bartik fluid width subtheme The name is in reference to Jean Bartiks work colleague kathleen Antonelli.

---

A cloudy day mobile theme is based on the A Cloudy Day theme. Optimized for iPhone, designed and developed by Carette Donny and co-maintained by Rajan Mayekar. Features: Support for logo, slogan, mission, primary links, secondary link, search, user pictures,... Regions: Content, Footer

---

Precision is a base theme build for Panels Everywhere. It's based on the exact same principles as the 960 grid system, but with a more fine grained grid and some minor feature additions. The theme is also shipped with some Panels layouts and style plugins making it possible to leverage the grid system from the Panels interface. More information is coming soon.

---

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? read more

---

The beautiful Modernist theme is a minimal theme focused on great typography. It is designed by Rodrigo Galindez and based on the design ideas of Jan Tschichold, Josef Müller-Brockmann, Dieter Rams, and other modernists. Beautifully built yet transparent, it was designed with a focus on optimal typography in order to better showcase your content: text, images and video. Features Fixed width. Two columns. Includes CSS3 enhancements. Works in all current browsers. Credits Designed by Rodrigo Galindez. Drupal port by Ralf Stamm (Ralf).

---

Magazeen lite is based on WordPress' Magazeen theme plus the addition of a slideshow.

---

This is a port of the Twenty Ten theme from WordPress 3

---

In 2009 Appnovation Technologies was asked to design and develop a Drupal based community and e-commerce website called Cargoh. The driving idea behind the site is to create a “social marketplace” for independent artists from all over the world to be able to showcase and sell their products and services. It features community tools such as forums, an internal messaging system and events section. Cargoh.com was founded by Paul and Cariann Burger when they noticed the lack of avenues for independent artists, designers and musicians to get their work to the world. They realized that some of the most talented people in the world were making them coffee in the morning at the local coffee shop. They set out to change that by creating a super accessible, highly affordable and unbelievably feature rich venue for artists, designers and musicians to sell the things they create. Above that, they wanted to create the world's best online shopping mall for all the uniquely independent products in the world. So from those two missions, Cargoh.com was born. The world's most exciting social marketplace for independent creatives! read more

---

Founded in 1991, The Cara Program is a Chicago-based non-profit that empowers men and women affected by homelessness and poverty with the skills, confidence and resources to secure and sustain quality jobs and achieve long-term success. Since their founding, they have placed more than 2,500 individuals into full-time, rewarding positions with leading Chicago area companies such as ABM Lakeside, The Hilton Hotels, JP Morgan Chase, Sodexho, and more. The Cara Program sought a redesign of their static website, one that engaged visitors by quickly delivering key information that was clear and concise, and could be easily maintained by Cara staff. Being a non-profit website, they also needed a way to accept donations, recruit volunteers, allow visitors to join their mailing list, and recruit sponsors and employment partners. In addition to being able to simply accept donations, they wanted to eventually “empower” donors to use social media and/or other outlets to spread the word, champion their cause and help others donate or otherwise support. The ability to share some content also needed to be a feature on The Cara Program "child" program websites: Clean Slate, Quad Communities and Career Pathways. Duo Consulting was chosen to implement their goals and Drupal was the platform chosen. read more

---

Features CSS and XHTML Valid (XHTML 1.0 Strict) Usable and accessible 12 block regions Stylings for all core modules: nodes, forums, blocks, poll, books, profiles, etc. Cross-browser IE >= 6 FF >= 2, Safari > =3, Opera >= 4, Chrome read more

---

Start:  2010-10-02 08:00 - 09:00 UTC Drupalcamp or Regional Summit Organizers:  Mediacurrent Drupalcamp Atlanta 2010 (www.drupalcampatlanta.com) is now open for registration, and will be held on Saturday, October 2nd from 8am – 5pm at the Georgia Tech Research Institute. Our mission and purpose is twofold: (1.) we want to educate people about Drupal and (2.) further evangelize Drupal within our geographic region. The 2nd annual Drupalcamp Atlanta is an attendee driven, completely volunteer initiative modeled after the open, participatory nature of barcamps. We are offering four tracks this year: (1.) Drupal for Beginners (2.) Design, Theming, and Usability (3.) Development and Performance and (4.) Drupal for Business and Services. If you are new to Drupal we definitely want you to come – in fact, during registration we have carved out space and time for a “Drupal Installfest” before the sessions start. This year’s venue at Georgia Tech will be spectacular. The main auditorium offers stadium-style keynote seating, power outlets in every other seat, and a reliable wifi set-up. The schedule will involve high-quality breakout sessions, an attention-grabbing keynote from a to-be-determined speaker, a coder’s lounge, sponsor booths, and an executive boardroom for special Birds of Feather (BoF) type gatherings. Want more? OK, when we are done we are going to have a party from 6-9pm at a nearby, soon-to-be announced restaurant where the networking and good times will be sure to follow. Amazingly, this year’s event will cost a modest $25 for an all-day conference badge and will include breakfast, lunch, and snacks. For an extra $25 ($50 total), you can become an individual sponsor and we will provide you with an official t-shirt and recognition on the DCA website. Many thanks to the 13+ organizations who have already signed on to become a sponsor – sponsorship opportunities are still available. How can you help? We need more volunteers, particularly those who would be willing to loan us video equipment, take pictures, or shoot footage of sessions– contact us and we will get in touch. Next, we need presenters to submit sessions. After being inspired by kick-ass Drupalcamp sites like Los Angeles and Colorado we added a voting component and commenting feature this year to allow potential speakers more attendee input leading up to the camp. The ability to submit sessions is now open and will close on September 10th at MidnightEST. Let me state the obvious, but the earlier you get your session submitted the more opportunity for votes and feedback. Finally, here is the best piece of advice I can give you – REGISTER NOW. Due to venue constraints, we are capping attendance at 225. Last year’s event sold-out two months in advance, so do not risk getting shut-out. Follow Drupalcamp Atlanta on Twitter @Drupalcamp_ATL www.drupalcampatlanta.com triDUG

---

One of the big goals of the drupal.org redesign is to make it easier for end users to find the right modules for the site they're trying to build. With over 5,000 contributed modules, many of them providing similar functionality, it can be extremely difficult to choose. One method is to try to assess the "health" of the module, by how actively it's maintained, used, supported, etc. One approach to gauging health is posted at Project ratings and reviews for drupal.org redesign. While that proposal deals with subjective factors, this post addresses objective facts about a module that can be computed and displayed for all projects hosted on drupal.org. While no single metric can tell you what module to use, and some knowledge will be required to make the best use of this data, it's important to make these statistics more readily available on drupal.org to empower users to make better decisions. The redesign prototype for project pages includes the introduction of a sparkline showing the "Activity" for each project. The details of this activity chart weren't specified at a technical level during the design phase, but the spirit of the design is that they wanted more ways to visualize the health of a project. As we're implementing the redesign, we've been empowered to provide as many charts containing specific data we think will best help end users make sense of what's going on with a project. Read on for our specific proposal, including what metrics to compute, and some ideas on how those are going to be visualized on the new drupal.org Specific metrics There are literally dozens and dozens of metrics that could be captured and displayed. We've already got support for the usage of any given project and we're working on support for download statistics. Beyond those, we believe the following are important to assess the overall health of a project at a glance: Issue activity: Each project category (bug, feature request, etc.) -- number open vs. number fixed/closed Number of issue reporters (unique users filing new issues in a defined time period) Number of issue participants (unique users filing issues or comments in defined time period) Total number of issue comments posted over a week (ideally with a separate total for the number of comments by any of the project maintainers, both of which can be graphed on the same sparkling). Release activity: Number of releases in each time period We're proposing to normalize all metrics to a weekly granularity. This would both simplify the storage (so we're not trying to store daily metrics) and the UI (since it'd be best if all the charts used the same granularity to make it easy to compare them). Additionally, the following metrics could be useful, but we might not have time to implement them for the initial launch of the redesign: Commit activity (This would be great, but it's not worth our time to add this for CVS with the Git migration imminent). Number of lines added/removed Number of commits Total number of tests and percentage of tests that pass Total lines of code vs. lines of comment Average length of time that issues are open Number of unique users submitting patches reviewing patches We're trying to strike a balance between what's relatively easy and sane to compute, implement and display visually, and things that will help users find the best project for their particular needs. Given that, if you have suggestions for other metrics we should be considering, please comment below! Enter the project_metrics module We looked at a lot of Drupal charting modules (see below), but basically none of them handle the storage for you. So, no matter how we end up displaying this data, we need somewhere to compute and store it. Enter the project_metrics module. This would be a new sub-module included directly in the Project project. While the project_usage module is really only relevant to sites that are using Project to manage releases of Drupal code to track update_status usage, the project_metrics module could be useful for just about anyone running the Project suite. It would be responsible for computing the metrics and storing them. To compute, the idea is we'd write a series of drush commands that would be run periodically to do all the heavy lifting to compute the right statistics for a given week. These commands would insert records into the project_metrics module's DB tables. Then, project_metrics would provide various ways to access and display the data (see below). The basic architecture of the module is that it would invoke a hook to allow other modules to advertise what metrics they want to provide. The project_metrics module would then be responsible for invoking the appropriate functions in the other modules at the right frequency and storing the results. So, project_metrics itself wouldn't know how to query the issue database tables looking for statistics. That'd still be the responsibility of the project_issue module. However, project_issue wouldn't have to worry about invoking itself via cron, wouldn't have to manage its own tables to store the historical data, etc. Front-end display So how would all this data be visible on drupal.org? The key metrics would be exposed via sparklines on the project page itself. Depending on how many metrics we end up with, we might need to add a tab off project pages (or use JS to show/hide the full list of metrics) so that it's possible to drill down and find as many statistics as we provide, without overwhelming the user with all of that data directly on the default project pages. My vision is that there's an easy way to see 5 - 10 sparklines, each with datapoints at 1 week granularity, all vertically stacked so the weeks line up. That way, you can see how the different metrics correlate. So long as the scale of the horizontal axis is the same on all graphs (so they line up and are easy to compare), we can use a different scale for the vertical axis for each sparkline so that they all make the most visual sense (e.g. the number of releases in a week is probably going to be 0-4 most of the time, whereas the number of issue comments or lines of code added/removed could be in the hundreds or thousands). With the charts stacked so the weeks line up, you could easily see for example that one week the "number of lines of code added/removed" sparkline goes nuts, and the "number of open bugs" chart started climbing soon thereafter. ;) There are some metrics and statistics specifically about the issue queues that are already on drupal.org, they're just mostly hidden. For example, you can view statistics about the Drupal core issue queue. This page will probably get some much-needed attention (it hasn't been touched in years). Although none of the UI parts of this proposal are set in stone, it's likely that we'll update these per-project issue statistics pages to include more of the issue-related metrics discussed above. The idea is that we'd put the current week's raw data in the tables near the top of the page, and then provide sparklines below to see how those values have changed over the weeks of the last year. Additionally, we're going to expose some of these metrics to Solr to make it possible to filter and sort projects by various metrics. We've already done this with the project usage data (for example, this is the default sort order when you browse module projects on drupal.org). So, in addition to being able to sort by "Most installed" (and hopefully soon, "Most downloaded"), you might also be able to sort by "Most active issue queue", "Smallest % of open bugs", "Most commit activity", etc. However, when it comes to visualizing the data that the project_metrics module would be providing, we've investigated a few possible ways to generate the necessary charts: Sparkline-aware views display plugin We could expose all of the project_metrics data to views, create views for whatever we care about, and write a Views display plugin that knows how to render our results as a sparkline. This could potentially be done as part of the Views charts project, or as its own new "Views sparkline" contribution. Either way, we'd hope to make use of the Sparkline module. The Views display plugin would simply be glue to take the data from the results of the query that Views ran and format that data in a way that the Sparkline module expects to be able to generate the sparkline itself. Charts API We could potentially use the Charts API to handle our charting needs. We'd still probably drive the queries via Views and have a display plugin to render the results via the Charts API. So, this is more an alternative to the Sparkline module itself -- either way we'd probably be exporting the project_metrics data to Views and writing a display plugin. Quant We looked at the Quant module, but it doesn't really seem like it gets us very far. It can do really complicated queries to try to figure out the historical data for you, but that's going to probably kill the d.o database server. It doesn't do any storage for you. And, we'd have to write some code to expose our data to Quant. At that point, we might as well just expose it to Views since that seems a lot more flexible and powerful. Implementation roadmap From now until around August 20th, we're just going to gather feedback on this proposal. To prevent the discussion from getting fragmented, please add comments directly on this post. Starting around August 23rd, we're going to begin implementing the project_metrics module, and any changes to the rest of the Project suite, to make it possible to compute all these statistics. We expect all the backend work to take approximately two weeks. Starting around September 7th, we're going to evaluate the front-end options and pick one to roll out on drupal.org. We're aiming to get these metrics visible on project pages and in the ApacheSolr index on the live drupal.org independent of the launch of the redesign theme (which is called "bluecheese"), unless it involves significant work in the existing drupal.org theme ("bluebeach"). Background reading Interested readers can check out the following threads for more on this juicy topic: Project Quality Metrics on Drupal.org (meta document) Automate gathering of quality metrics Project module's hidden project metrics Drupal.org redesign implementers

---

It's time for another update from DrupalCon Copenhagen! This time around we have updated information on the core developer summit, the unconference, and the code sprint. Official Program First of all, we are happy to announce that the final version of the program is now available on the site. The few remaining slots in the schedule will be used for sponsor sessions and lightning talks. We'll try to keep schedule changes to a minimum, but if we do have to shuffle a few sessions around, this is the page to watch. Also, we'll make the entire program available as a PDF if you would rather keep it on your laptop or print a copy to keep in your pocket during the conference. Now that the program has been finished, you can start planning your DrupalCon Copenhagen. Go to the session schedule and add all your favorite sessions to your personal schedule. You can see a list of your chosen sessions by going to your user profile and clicking the "My schedule" link. Core Developer Summit If you're in Copenhagen on Sunday, August 22nd, and interested in helping improve Drupal core, you should participate in the Core Developer Summit. The summit will provide opportunities both for people to discuss changes to Drupal code and processes as well as people interested to move Drupal 7 closer to release. The summit will start wit three shorts sessions by Dries Buytaert, Sam Boyer, and Jen Simmons. After the kick-off sessions, the summit will break up into two groups, with plenty of space to be fruitful and get stuff done. All ideas are welcome! read more

---

Mod. Corolla by Thomas Moseler, Jeff Burnz View screenshot: ► Sky ► Sea ► Beach ► Garden ► Sunset ► City ► Lava Features Extensive stylings for all core modules: blocks, nodes, forums, books, profiles, etc. Drop-down menu with unlimited number of submenus 7 predefined color schemes 1-, 2- or 3-column layout with flexible width Configurable layout width Configurable position of each sidebar Configurable base font size Regions: content, content top, content bottom, sidebar first, sidebar second, highlight Supported standard theme features: logo, site name, site slogan, primary links, secondary links, user pictures in comments, user pictures in nodes, favicon Can be used as a full-fledged admin theme, also inside overlay read more

---

Download Drupal 6.19 Download Drupal 5.23 Drupal 6.18 and 5.23, maintenance releases which fix security vulnerabilities are now available for download. Drupal 6.19 also fixes other small issues reported through the bug tracking system. 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. read more

---

This post is part of a series to inform the Drupal community about the drupal.org redesign project, and the work the Drupal Association is funding to help get the redesign completed. If you would like to contribute to the redesign as a volunteer, see the community initiatives redesign page. If you'd like to contribute to the redesign financially, see the Drupal Association memberships and donations pages. read more

---

With Drupal 7 down to 30 critical bugs, and Drupalcon Copenhagen just around the corner, it's only a matter of time before Drupal 7.0 ships. We want to make sure our Drupal 7 documentation is in great shape for this fantastic new release, and the Documentation Team could really use YOUR help getting there! read more

---

Waves is a spin-off theme of the web design used at the University of Antwerp. The theme features are three-column layout and is fully XHTML 1.0 strict and CSS 2.1 compliant. Features Customizable logo, favicon Proper embedding of primary and secondary links

---

Use this starter theme to make a sub theme for a runvsc based theme.

---

The given theme is made for a city portal of a Brest in Belarus and laid out in free using. Features Three columns design with 10 regions for blocks Cross-browser tested in IE6/7, Opera, Safari, and Firefox Possibility of citing of comments The theme is made by LTD company Internet marketing. It is laid out for all intermediary http://www.seonet.by/

---

PulpMX.com was launched in early 2009 as a place for well-known motocross columnist Steve Matthes to post his musings about the sport and its history. Originally conceived of as a modest site, it was built in early 2009 using a stock theme with a handful of custom images, the FCKeditor and IMCE modules to provide a built-in visual editor, and little else. Over time it had grown organically as needs developed: CCK, Filefield, and SWF Tools for posting audio interviews in a built-in player, for example. In early 2010 PulpMX also took on discussion forums from a site that was no longer able to host them, so an existing phpBB installation was also imported. The site was developing a growing following and it was becoming obvious that it needed an overhaul to better reflect the character of the site, and provide more cohesive and initiative navigation among the quickly expanding areas of the site. Says Steve: Originally I had gotten Tooth and Nail to design me a basic site for blogs and photos, what they gave me was way better than I had thought I needed. The traffic and the new media things that I was doing (podcasts, slide shows and a live internet show) demanded that I get something new and fresh. I was now big-time I suppose. read more

---

Fever is a multi-purpose magazine style theme. It is the second Drupal theme developed by Antsin.com and released under the GPL. Same author for BlogBuzzI & BlogBuzzII. Fever Drupal theme suits perfectly for news, sports, gaming, entertainment, etc. It is three columns, fix width theme. Two flexible sidebars can be switched on/off. Fourteen block regions, including a large Showcase block that allows you to display a rotating headline beautifully. Five content bottom regions can be structured more interesting way. Stylish white color tune combines with orange color links and buttons, it gives your site a clean, professional look and feel. Fever theme also has a unique blog style with neat comments layout that support avatar. Fever theme has successfully passed XTHML + CSS W3C standard check. See it yourself for detailed features & demo on Fever. Fever also available as Feverultra which including Advanced Forum theme. Standard Features: 100% CSS driven 2 level droplist navigation menu read more

---

Get ready to meet and learn from the top Drupal developers, designers and architects from around the world. Save €31 and get your DrupalCon Copenhagen ticket now at the current price of €279, because on August 16th at 8am CEST the ticket price will go up to €310 + VAT. Go to the DrupalCon Copenhagen site to buy your ticket for the conference. Your ticket includes: 94 sessions spread out over 3 days Ad hoc BOF (birds of a feather) sessions Access to the Core Developer Summit and the post-conference code and documentation sprint Access to the ChX Coders Lounge where you can hang out and code all night Access to FooBar, the official bar of DrupalCon Copenhagen …and, last but not least, a chance to meet your fellow Drupalers read more

---

A Vitamin Plus is a new Drupal Template by Themes Drupal. It is based on my previous template called A Vitamin. This new template inherits the same layout but with a different CSS. Moreover it is available in two color variants: A Vitamin Plus+ A Vitamin Plus+ Orange read more

---

In mid-2009, TopNotchThemes started building Fusion, a theme system that would pave new ground for Drupal themes. Along with this new technology, we started dreaming of our ideal website where products could be deployed automatically, customers had access to a much more friendly account area, and of course a brand new look and feel for this new line of themes. Our current Drupal 5 website at TopNotchThemes.com (to remain active until remaining themes are ported to Fusion) is showing its age and does not have the control we need in order to be able to adapt content and features as our visitors demand. Launched this spring, FusionDrupalThemes.com is not only a showcase for our products, but a wonderful showcase of community and commercial synergy. It integrates Ubercart, Organic Groups, and the Project module suite to create a feature rich platform for selling code-based products. read more

---

Tumblike is a theme inspired by the elegant simplicity that is portrayed by many blogs on tumblr. This theme is very simple in design and form and really only intended to be used for a blog. Theme developed by Thomas Lattimore. This theme is still in mid development. Though functional and ready for testing, it should not be used on production sites. Enjoy.

---

Based on Pandion.IM, this theme is meant to display products or business information. It'll integrate nicely with the carousel & gallery modules. ALARM: Not for production use...yet. Built on Drupal & Love. Built for You.

---

Based on Directi.com, this is a minimalist business theme featuring custom layouts for the front, inner & blog pages. It's named in honour of Sidney Bristow, a double agent for the CIA who tirelessly and unselfishly fought to make this world a better place. ALARM: Not for production use...yet. Built on Drupal & Love. Built for You.

---

The Deutsche Aids-Hilfe (DAH) is the leading German non-governmental organization that deals with the concerns of people living with HIV/AIDS and helps raise awareness of effective HIV prevention techniques. As the governing body for more than 120 local AIDS service organizations, it supports this work at many different levels. The DAH website, aidshilfe.de, is one of the organization’s main communication channels. It offers information on HIV and other sexual transmitted infections and covers the field of counseling for private matters. The website also provides contact information for local self-help-centers, a broad selection of free information material, workshops, community features, etc. Work on the aidshilfe.de project was supported by many partners. Christoph Schüßler designed the website, which was implemented in Drupal by Berlin-based Werk21. The new aidshilfe.de is a step forward toward a future-proof system that features an attractive new design, interactive features, user-friendly community functionality and great usability. read more

---

runvsc is a tight, mean pre-processing base theme; all of the logic / markup is built from within the template.php. You need to also download STARTVSC to use this base theme ! Startvsc is the starter theme for runvsc. Download this starter theme and place it in your theme folder (as a sibling) with runvsc. You can then copy this subtheme to use as your starting point for making your individual custom theme! Click here to download startvsc from the project page. runvsc themes features include: Native 960 grid system -> configurable with simple integer variables in the template.php A theme "abstraction layer" -> I hunted down all the places where major items are declared and exposed them so you can find them! Useful functions -> such as a "div" generation function! All elements are processed through "runvsc_build_div_markup" so all output is reliable - no hanging h*.title elements! Preprocessing makes your theme 3 times faster -> the tpl files are simply print $variable statement. No pesky if - colon statements! read more

---

TicketCake.com is an event ticketing and promotion start-up that recently launched using Drupal as its framework. The website features an innovative design by White Label Graphics which balances functionality and simplicity. Because Drupal has many ways to display dynamic content, finding the right way to implement a design can be a problem in itself. To overcome this obstacle, the Ticket Cake team focused a significant amount of time creating wireframes for the project. Drupal’s unique ability to display content in various ways made the process of developing wireframes a constant back and forth. With each iteration, the team updated price quotes, layouts, and site flow. “Throughout the construction of the wireframes, we always looked to a keep it simple philosophy that ended up being vital,” said Joe Henriod, head of the Ticket Cake business development team. “Measure twice, cut once.” read more

---

This theme is a demo platform for the CSS Template module (http://drupal.org/project/css_template).

---

Smokers is an advanced theme developed by Dr. Radut for Smokers Association to be ideal for a wide range of sites, been optimized for e-commerce with Ubercart. It contains the same kinds of features you'll find in our other professional Drupal themes. The theme validates XHTML 1.0 Strict / CSS 2, and it is cross-browser compatible; works perfect in Firefox, IE 6, IE 7, IE8, Safari, Opera and Google Chrome. Live demo at: Smokers Association. read more

---

All your Drupal XHTML belong to us. A base theme for HTML5. This theme is not ready for use!!!!!!!!!!!!!! It's a total rough mess. Why is it here then? So that the group working on it can share code and process. DO NOT USE THIS THEME. DO NOT JUDGE THIS THEME! We know it's not anything yet. Are you sad because you want some HTML5 awesomeness, and there's nothing finished to download yet? Well, the awesome stuff is over here: http://drupal.org/project/issues/html5_base Yummy, yummy discussions about how best to mark things up. Also, there's super yummy in the IRC channel #drupal-html5. Sometimes there is a whole mess of smart Drupalers discussing HTML5. Join us! Really, you. Anyone can join in. Don't be shy! Read the manifesto: http://groups.drupal.org/node/82664 People currently working on this: canaryMason / Mason Wendell / http://drupal.org/user/65865 mxgfx / Patrick Macom / http://drupal.org/user/195972 jensimmons / Jen Simmons / http://drupal.org/user/140882 theresaanna / Theresa Summa / http://drupal.org/user/215660 timplunkett / Tim Plunkett / http://drupal.org/user/241634 (and if your name should be here, ping one of the maintainers.) read more

---

This is a basic theme intended for sites that want to get away from the column feel, yet want to have a fluid look. This approach uses fixed-width content area to help ensure readability, while blocks "float" against it. (Hence the name.) #D7CX — I pledge that this theme will have a full Drupal 7 release on the day that Drupal 7 is released. #D7AX — I pledge to make this theme as accessible as it can be. If you find any flaws, please submit an issue. Help me fix them if you can. Features Blocks float against the content. The wider the page, the more blocks will bump up to fill in across the top. Alternative layout styles apply on smaller resolution screens. Caveats Stable but subject to change. Alpha versions will be tested to work against alpha releases of Drupal 7, focusing on the use case of blocks in the right sidebar. Until Drupal 7 has a stable release, or at least a release candidate, things could change radically to keep up with the changes. read more

---

A table-less, CSS driven, 2-coloumn, fixed 1024 size, centered theme that aims clearly designed sites. Originally written for an address repository in Germany, now contributed to the community. Customizable color schemes. Enjoy! Features - Clear and bright theme - Site Name, Site Slogan, Site Logo, Site Mission - Customizable colors - custom.css for extensions that survive updates - Plain code region for insertion of tracking scripts ie. - No fixed primary menu - 12 regions - Will work gracefully degrade for stone aged IE6 Sorry for the release delay - we're still on it

---

Grandiflora is a boutique florist based in Sydney, Australia. Although you might not have heard of them before, you've probably seen their work in the pages of Vogue, Harpers Bazaar and many other fashion magazines. They've also created the floral design for many celebrity weddings and events in the Australia's premier harbour city. Recently Grandiflora were interested in updating their identity and marketing (including their website), so they tasked the team at House of Laudanum to create a custom online shopping experience to sell their products online. The previous website was a custom CMS written in Perl and while it did have some e-commerce facilities, it required updating to be a more integrated shopping solution. Why was Drupal chosen for the project? Although WordPress was considered early on in the decision making process, the team chose Drupal mainly because of the Ubercart module and some other contributed modules which laid the foundation for the integrated payment solution required for the project. read more

---

After reviewing 240 sessions submitted for the conference, the track chairs, the Copenhagen team and the Drupal Association are proud to present the DrupalCon Copenhagen program. The total of 94 sessions is made up of 83 regular sessions, 6 platinum sponsor sessions, 3 keynotes and 2 rounds of lightning talks. The session selection accounts for many factors including attendee votes, addressing the breadth of interests of DrupalCon attendees, and providing a balanced and compelling program. For example, some sessions were picked because they were essential for introducing new developers to Drupal, other sessions were selected because they present important local Drupal business cases, etc. If you proposed a session that didn't make it into the program, please consider presenting it at the Unconference on August 23rd or run it as a Birds of a Feather session. We will be adding more information about these options to the website in the coming weeks. You can either see the sessions selected for each track below, or take a look at the program overview. Please bear in mind that this is not the final program and that sessions are likely to be moved around as we refine it. read more

---

At the Drupal Association retreat in San Francisco, the general assembly set the completion of the drupal.org redesign as its number one priority for 2010. The assembly agreed to fund five contracts to help eliminate obstacles that had prevented the community from completing the redesign. Five key roles were identified: Architect, Solr developer, Project module developer, and an infrastructure developer. The association also elected to upgrade Drupal.org code repository from CVS to Git to help maintain Drupal.org as the hub of Drupal development. Hiring process: Job descriptions were developed in conjunction with both the redesign volunteers and the Drupal.org project managers, Kieran Lal, Chris Strahl, and Lisa Rex. The job descriptions were then posted to groups.drupal.org for 3 weeks. Approximately 35 applications were received and a dozen interviews were conducted by the project management team. The contracts were negotiated with Drupal Association Interim General Manager Jacob Redding, to whom the project team reports directly. Contractors work day-to-day with the project management team. The association will pay for the contract work using the funds raised through memberships, advertising, partnerships, affiliates, and DrupalCon sponsorships. read more

---

The Drupal Association has been working to figure out the most effective ways it can help local user groups organize Drupal camps. We quickly realized that there was a lack of data about how past and present Drupal camps were currently being organized. With that in mind, we created an online survey for DrupalCamp organizers that would help everyone understand how Drupal camps currently worked. Over the course of about 7 weeks, we collected a total of 51 responses, with 6 duplicates and unusable, making our sample size 45 Drupal camps. In a previous article posted on the Drupal Event Organization Drupal group, I posted the results from the first 31 responses. Since that article was published (and because of it), we had an additional 14 responses, making the data that much more valuable. Overall, the 45 camps that completed the survey had over 6,200 participants, a combined budget of almost $250,000, and were organized by over 400 volunteers. The resulting data is extremely valuable to both the Drupal Association and Drupal user groups around the world. The Drupal Association now has an idea of how camps are currently being organized and can make informed decisions about how to help future organizers. Local user groups can use this data to help plan future events. In particular, the average cost-per-particpant and participants-per-volunteers data (highlighted below) should be considered when planning future camps. read more

---

Start:  2010-08-07 09:00 - 2010-08-08 15:30 America/Los_Angeles Organizers:  Chris Charlton mike stewart jromine christefano rainbreaw nbluto thund3rbox DrupalShark snelson Registration is now open for DrupalCamp LA 2010. Mark your calendars for Saturday & Sunday, August 7-8th, 2010. Attendance is free. The camp will be taking place in the same great venue from last year - UC Irvine in the city of Irvine, California. The campus has housing available if you wish to rent rooms to stay overnight. If you registered last year then your account is already setup and you just need to login and edit your profile to mark what days you plan to attend. Free to attend. Parking costs about $8-12 per day. Lunch is not provided but you can bring your own or buy a food pass from the cafeteria on campus (which people liked last year). Nighttime private camp party on Saturday 7PM-MIDNIGHT sponsored by MediaTemple. SPONSORS Warner Music Group Media Temple Achieve Internet Volacci Tropo Stauffer New Media Development Monstrositee Commerce Guys WHAT PEOPLE LEARN EACH YEAR AT DrupalCamp LA Drupal 6 & 7 Drupal Basics Business with Drupal Administering & Maintaining Drupal Building with Drupal Drush PHP & SQL Designing & Developing for Drupal Drupal Themes & Modules Contributing back to Drupal, and more! http://2010.drupalcampla.com ADDITIONAL SPONSORS & CONTRIBUTORS The Henry Samueli School of Engineering University of California Irvine Acquia Intrinsic Web Designs SunRain Productions Cherry Hill Co Development Seed Sage Tree Solutions New site design provided by SoCal's premier Drupal agency This By Them, creators of the 2009 site. http://2010.drupalcampla.com WE NEED YOUR HELP! By sponsoring our camp you get exposure and praise from our community mixed with networking possibilities during the entire camp. Due to budget cuts recently experienced by state schools in California, however, UC Irvine's costs have gone up, meaning our costs for the camp have also risen. We are charged with the task of raising upwards of $10,000 this year in order to fund the event our community has come to expect. Please consider sponsoring. Contact an organizer today. Sponsor get their names/logo/link on our camp site, camp signs, maps & pamphlets, videos, our tweets - anything we can think of. If you want to make your presence known in the SoCal Drupal community then you want in on this. Visit http://2010.drupalcampla.com/sponsorship for more details. RAFFLE PRIZES Each day a dozen winners will be announced and each will get to choose a Drupal related prizes. Book publishers currently sponsoring the camp prizes are O'Reilly, Apress, and Packt Publishing. Two special winners will win full 1-month passes to Lynda.com on behalf of Drupal author & community leader Chris Charlton, author of Drupal: Creating and Editing Custom Themes online video training. Creators of the jQuery & Drupal plug-ins for Adobe Dreamweaver & Eclipse IDE, XTND.US are providing two awesome "CSS Ninja" shirts, check out the shirts below or at: http://www.zazzle.com/css_ninja_style_class_tshirt-235091799113607617) DrupalCamp LA APPAREL At the camp we will be selling awesome new t-shirts for only $10! That's 50% off the online price. Our 2009 camp shirt is also (still) available and you can order yours before the camp! This is the shirt being raffled off by XTND.US. You can order your own online. Get more info about DrupalCamp LA http://2010.drupalcampla.com Sponsorship information available at http://2010.drupalcampla.com/sponsorship Drupalcamp or Regional Summit Ventura Drupal

---

Our fifth Drupal 7 alpha version was released a little over a month ago. Today, we're proud to announce the release of the sixth (and hopefully final) alpha version of Drupal 7.x for your further testing and feedback. The first alpha announcement provided a comprehensive list of improvements made since Drupal 6.x, so in this announcement we'll concentrate on how you can help ensure that Drupal 7 is released as soon as possible and is as rock solid as the previous Drupal releases that you've grown to love! This release includes many critical bug fixes, a nearly working upgrade path, and a new default core theme: Bartik! Please see the release notes for more details. When will alpha become beta? We have identified several "beta blocking" issues, and itemized these at the Drupal core community initiatives page. On or about August 1, 2010 (or when the upgrade path is working, whichever comes first) we will create a new official Drupal 7 release. If this list is fixed, it will be a beta release. Otherwise, it will be another alpha release. It's expected we will have a few beta versions and at least one release candidate before Drupal 7.0 is finalized. We can potentially reach beta within the next month by focusing on this short-list of issues! Please help! read more

---

Want to help migrate drupal to git? Great! This page overviews the different parts of the migration process, with a focus on making it easy for you to jump in wherever you'd like. See the Migration Roadmap for a more in-depth overview of what the migration entails. Phase 2 of the migration has a lot of work to do, and it's spread all over the place. Being so spread out makes it hard for folks to know where to jump in and help. So instead, we've come up with these three loose avenues for participation - "Developing, Documenting, and Deciding." If you'd like to help, you should read through the stuff below and then ping sdboyer over email, twitter, or irc, saying, "I'd like to help with Development/Documenting/Deciding!" He'll get you squared away. Develop If you're a code monkey, we can definitely put you to work. There's modules to develop, a migration path to test, test sites to debug, and server settings to tinker with. The modules are the lowest-hanging fruit, and these are ones that really need love right now: Version Control API Version Control Git Backend Version Control / Project integration Getting the latest branches of these modules finished and working is an absolute must for the migration. The 2.x branch of vc api is what this whole system will be based on, and we're trying to finish it up. There's LOTS of other dev work to be done, too, including work on the migration path, experimenting with server setups, and work on the packaging script. Document It's been soundly agreed upon that documentation is just as essential as code for the success of this migration. Of course, 'documentation' covers a wide range. Here's the general picture of what we want to accomplish: Create a 1:1 analogue of the CVS Handbook. There's a prototype, and an issue to discuss it. Create a 'Git Instructions' module, analogous to the CVS Instructions module. Develop an "open source training curriculum" that will prepare new drupallers/git users for using git to contribute to and work on Drupal projects. (will provide a link here to that discussion once it's kicked off) Decide Want to be heard, but not do any work? This is for you! (kidding :P) There are a lot of things about the way d.o works, and the way we work with d.o, that are being decided by this migration - for example, we need to decide how commit statistics should work, and on how we'll replace $Id$ tags Some of these are decisions that can be taken now, while others we'll only realize as we run across them well doing other work. In both cases, though, we need to sort them out as a community for the migration to proceed. So if you're too strapped for time to offer anything but your voice, that's ok - just make sure you follow the migration gremlin, as crucial decisions are primarily be announced there. Drupal.org Git Migration Team

---

We are proud to announce the keynote speakers at DrupalCon Copenhagen 2010: Rasmus Lerdorf (topic to be crowdsourced), Jeremy Keith (Design of HTML5) and Dries Buytaert (State of Drupal). The State of Drupal Dries Buytaert, Drupal Project Lead Tuesday, August 24th Dries Buytaert will discuss where Drupal is and where it is going. In particular, he’ll discuss the final preparations for the release of Drupal 7, the Drupal.org redesign, and the plans for Drupal 8. Dries Buytaert is passionate about the web, open source, and photography. He is the original creator and project lead of Drupal, an open source social publishing system. He is co-founder and chief technology officer of Acquia, a venture-backed software company that offers products and services for Drupal. Dries is also working on Mollom, a service that helps you identify content quality and that stops website spam. Topic to be decided by you Rasmus Lerdorf, PHP Project Founder Wednesday, August 25th Tell Rasmus which topic you would like him to focus on by leaving a comment on the DrupalCon Copenhagen site. Rasmus Lerdorf is known for creating the PHP project in 1995 and he has contributed to a number of other open source projects over the years. Rasmus was most recently an infrastructure architect at Yahoo! for over 7 years before joining WePay in 2010. He was born in Greenland, grew up in Denmark and Canada and has a Systems Design engineering degree from the University of Waterloo. You can follow @rasmus on Twitter. The Design of HTML5 Jeremy Keith, Author of HTML5 For Web Designers Thursday, August 26th Everyone's talking about the benefits of HTML5 for Web applications but the specification also introduces an extra layer of semantic richness to our Web documents. These additions aren't wishful thinking for some far-flung future: you can start using them today. That's because the design principles driving HTML5 are steeped in pragmatism. Find out how important good design principles are to any project, whether it's a website, a content management system, or the very language that underpins the World Wide Web. Jeremy Keith is an Irish web developer living in Brighton, England where he works with the Web consultancy firm Clearleft. He wrote the books DOM Scripting, Bulletproof Ajax, and most recently, HTML5 For Web Designers. His latest project is Huffduffer, a service for creating podcasts of found sounds. When he’s not making websites, Jeremy plays bouzouki in the band Salter Cane. read more

---

What is COD? COD stands for Conference Organizing Distribution and the goal of the project is to facilitate coordination of and participation in conferences via the conference website. COD can improve the efficiency of setting up a powerful website for both Drupal and non-Drupal conferences and events and provide value to non-developers and developers alike. Work on COD documentation has started at http://groups.drupal.org/node/79003 . If you like, you can vote for the DrupalCon Copenhagen session about COD. COD existed as a group of modules for Drupal 5 and the Drupal 6 version is a rewrite with similar goals. While COD draws on patterns used by other Drupal event websites, DrupalCamp Colorado 2010 was the first event to specifically use the Drupal 6 version of COD, and volunteers from that event contributed a great deal back to the project, specifically to the COD Support project which has been the main development focus thus far. Key modules used in COD are the Signup module for managing lists of attendees, Ubercart for accepting payment for registration, and the UC_Signup module for simplifying the process of registering for an account on the site, entering attendee profile information, and paying registration fees. The short term development goals for COD include developing a proper fully packaged Drupal distribution for COD that includes the COD_Support and other required modules for the project in order to facilitate easier installation and collaboration in the issue queue, so that we can improve COD as a community. The chart below lists features that COD currently provides and could provide in the future, the level of configuration required to use those features, and the level of documentation available for each feature. These features are organized by general user role on the site (not necessarily a Drupal user role in the technical sense). For each role, a "user dashboard" is suggested, with the goal of making it easy for users to access information and perform tasks relevant to them. ND = Needs documentation. Most of COD ND, though having a COD-specific document that points users to the documentation for the underlying modules will be appropriate in many cases. Below this chart is a list of miscellaneous tasks and their related Drupal.org issues, where applicable. "Needs more roadmap!" The destination, briefly: "Fully featured, easy to use." Yes, it's true that this document is more of an overview than a traditional roadmap. Right now, COD has several useful features, and is somewhat easy to use for site builders and developers who are familiar with Drupal. The overall goal for COD is to make it very easy for non-developers to build a fully-featured event management website. Therefore, the immediate direction for COD should be to add and improve the key features listed below in ways that make COD powerful and easy to use. A critical short-term goal is to make COD and the COD_Support modules available as a fully packaged Drupal.org installation profile. How can I get involved? You can get in involved by: Working on "Getting Started with COD" documentation. Right now, folks can install COD but it might not be clear what they can do to set it up and start using it. Documenting the basic setup steps for the features in the chart below would be extremely valuable to helping folks who are new to COD get it set up. Identifying a feature below and opening an issue in the queue of cod_support or a dependency module to discuss how the feature should be implemented, and ideally provide a patch. Using COD and providing feedback :) Download distribution here. Key COD features, based on user role Attendee Use-case Setup required Documentation? Notes View basic event information (what, when, where, etc), official hash tag Basic content creation ND Signup and pay Add user profile fields if paying, remove signup.module form field ND or work for removing signup.module default form field on sites where registration is free Provide contact/profile information Fill out core profile fields ND View Session proposals Provided by cod_session ND Submit sessions Provided by cod_session ND Vote on sessions Provided by cod_session ND Based on Flag. Submit session & conference surveys online Not currently provided. Requires configuring Webform. ND Create a personalized session schedule Provided by cod_session ND Based on Flag Check in quickly and easily Some View building required. Better default views could be provided ND Connect with other attendees through profiles and forms Enable forum module, configure profile fields ND * Potential dashboard: o official announcements o sessions, forum posts with tags I subscribe to * As the event draws closer easily change homepage from sessions to announcements and include BOFs, Food, maps front and center Checkin Administrator Use-case Setup required Documentation? Notes Turn attendee data into badges Attendee views could use a CSV export ND Find attendee records by email, name, username Adding custom fields to attendee admin view. Could use better defaults ND See who has paid UC_Signup has Views integration that connects signups to orders, but could provide a better default admin view. UC_signup could store the signup ID in the order ND Easily mark attendees as checked in, have an accurate count of how many people attended Signup allows admins to mark users as checked in or not checked in. Could use an ajax toggle link for faster processing. Signup.module provides a count of who is attending ND Session Organizer Use-case Setup required Documentation? Notes See submitted sessions, votes Provided by COD_Session. Needs a view for accepted nodes ND See number planning on attending Provided by Signup module. Could be made more visible and placed in a dashboard. ND See self-described skill levels of people who plan on attending . Core profile field configuration ND Schedule sessions Requires configuring room and timeslot fields and then placing them into a view. This could be streamlined further. ND View session surveys Full configuration of webform. ND Mail users by session acceptance status Could be added using Views Bulk Operations and additional view exports. ND Mail users by proposed sessions last year, not yet this year Could be provided by VBO ND. * Potential Dashboard: o sessions proposed o most popular sessions by comments o most popular sessions by votes o recent session review submissions Event Sponsor Use-case Setup required Documentation? Notes See sponsor benefits Submit content ND Sign up, pay for sponsorship We could facilitate this process better * ND Profile sponsor info (Logo, blurb) Partially provided by cod_sponsor ND Get coupons to sign up other people in company UC_Signup + UC product kits for sponsorship + event attendees is one solution but coupons are not currently provided but could be with a UC discount module. ND Sponsor Admin Use-case Setup required Documentation? Notes Receive sponsorship info Sponsor content type exists, but we could make it easier for sponsors to enter info directly and admins to approve it ND Easily create coupons for sponsor benefits Not currently provided but could be provided with a UC discount module ND Attendee relations/Event organizer Use-case Setup required Documentation? Notes Add profile fields Add core profile fields ND . Send e-mails based on variety of factors (below) Partially provided by Signup and UC ND o profile fields o order status o previous event attendance and current event status Misc Tasks Make into an actual packaged distribution for easier installation + setup Move from Context to Panels Re-export features from DrupalCamp Colorado 2010 site, compare changes (and commit back to the project) UC_Signup/Signup improvements * better locking of signups Better default theme than Garland (For admins and attendees) Store SID (Signup ID) in the UC order Better support for free events (don't use signup template form, add option to sign up on user registration form) Assorted Ways to make things especially awesome: Schedule Clearly label session tracks and skill level Sessions Embedding videos after the event, making it easy to browse videos Selling access to the embedded videos Subscribe to sessions submission to a particular tag/track? Session surveys via sms (twilio) Provide responses to questions like "Next sessions" via sms Checkin Automate checkin process Other Provide rich(er) profiles and easy tools to navigate profiles and contact people for pre-event networking Enable working groups to create and manage their own discussion area for pre-conference and post-conference discussion (i.e. OG) Profile pages with links to relevant content (sponsor affiliation, presentations proposed by the individual, presentations where the person is a speaker) Dashboard and reporting tools (probably a bunch of views) -- What kind of reporting do folks need? Ability to hire/advertise availability for services show attendee origin maps, distance traveled Make it easier to switch between modes of the event and prioritize different information on the site: -- 1 Button to end session submission, enable session voting (by changing user permissions) -- Make it easier to offer earlybird pricing Conference Organizing Distribution

---

On August 23rd, the day before the main conference kicks off, you'll be able to attend training sessions facilitated by leading Drupal experts. These sessions will take place at the main conference venue. The training sessions will cover: Performance and Scalability Drupal Powered E-Commerce Module development Security: process, code and hands-on training It is possible to attend the training sessions even if you're not going to the main conference. If that's the case, simply buy a ticket for the training session you'd like to attend. If you buy a ticket for a training session together with a ticket for the conference, we will subtract €30 from the price of your conference ticket (making it €249 + VAT). The discount will be applied automatically during checkout. Check out the training page for more information on the training sessions. read more

---

ThinkDrop Consulting and the non-profit organization MACILE are collaborating on a pilot program to introduce open-source technology and Drupal to children living in less-advantaged communities, helping them overcome the hurdles that prevent them from openly accessing and sharing information.  In July, we will travel to Itabo, Dominican Republic to teach a two-week class to 6th-12th graders and educators on Internet Technology, Open Source, and Drupal. In addition to educating both students and teachers on Internet technology and Drupal, we will be documenting the process using OpenAtrium and releasing our curriculum under Creative Commons licensing. Our goal is to create a consistent curriculum to teach kids around the world who may have not ever even used a computer. Donate Today! We are seeking $8,000 in funding through Kickstarter, an innovative website that allows users to fund creative endeavors. The funds we are seeking will pay for full-time coding and project development, travel and housing expenses in the Dominican Republic, and additional computers for educators and students. As we will be working in less advantaged communities, maintaining access to consistent electricity and the internet will be a challenge, so a portion of our time will be spent developing a model approach to this problem. Although we have set our funding goal at $8,000, we hope to exceed it. Any additional funds we receive will be used to continue expanding the Internet Technology programs of COSOLA and MACILE.  read more

---

A couple of days ago, we announced the track chairs and published the final descriptions of the six tracks at DrupalCon Copenhagen. To make sure that everyone has had a chance to submit a session targeted at a specific track, we have decided to move the session deadline back a week. The revised schedule is as follows: The final deadline for session submissions is July 4th. Voting will take place from July 5th until July 11th. The initial schedule will be published on July 18th. We have enjoyed seeing all the sessions submitted so far, but it has become apparent that the lack of detailed track descriptions has made it difficult to categorize some sessions. Hopefully, the track descriptions will make it easier for you to target your session at a specific audience. Please consider the following track descriptions when submitting a session proposal: Introducing DrupalChaired by Boris DoesborgFor users and developers new to Drupal. Theming, Design & UsabilityChaired by Roy ScholtenFor people who focus on usability, user experience, and design. Code & DevelopmentChaired by Gábor HojtsyFor people interested in Drupal's architecture and the future of its codebase. Configuration, Set-Up & PerformanceChaired by Florian LoretanFor people who want to spend less time coding and more time working on the content of their sites. Drupal for BusinessChaired by Jakub SuchýFor people who using Drupal as a tool for running their business. Providing Professional Drupal ServicesChaired by Thomas BarregrenFor people who provide Drupal-related professional services. We can't wait to receive your session proposals! read more

---

Start:  2010-06-24 08:00 - 17:00 America/Indianapolis User group meeting After months of planning it is official: On Thursday, June 24th, Drupalers from across the country are gathering together at the Arlington Central Library Google Map Here for a full day of DRUPAL LIBRARYCAMP. We strategically planned the event right before the American Library Association's Annual Conference in DC. Event site here This has allowed people from very far away to join us for a smaller sized Drupal event before they dive into the whirlwind of activity with the ALA. We chose to follow an UNconference model where we all show up, make a list of what every one wants to either learn about OR speak about then break off into ad-hoc groups; each seeking the group that meets the individual's needs. A WIDE range of people are coming to the LibraryCamp; some with years of Library experience, years of Drupal experience, or both. This is going to be a RICH time of sharing and learning for sure! We're all looking VERY forward to meeting each other and sharing our knowledge and skills as we seek to leverage the awesome power of Drupal for Libraries! Libraries

---

The issue of renaming Organic groups (OG) to Group was raised in several places, but it's probably a good idea to have it in a central place which is accessible to many. There are very good reasons for renaming the module, but just as good to not renaming it. Following the suggested Drupal Code of Conduct (#DCOC): When we are unsure, we ask for help I have created a Poll for us to vote. Let's write the comments in this discussion. Please go over the above links -- people have already written their thoughts, and they are worth reading. Oh, and the choices are only OG or Group... :) Contributed Module Ideas

---

You may already have heard of Packt, the fast-growing publisher of hardcopy and digital books on specific technologies, due to the large number of Drupal books it has published over the years. However, you may not be aware that they recently relaunched their website, www.PacktPub.com, using Drupal as its framework. Packt Publishing is a modern, unique publishing company with a focus on producing cutting-edge books for communities of developers, administrators, and newbies alike. Packt has so far published over 15 Drupal books and remains committed to producing practical solution-based books for Drupal developers, along with the best available online bookstore. The new website, which took 12 months from design to launch, was developed with UK-based Bluetel Solutions. The new version not only adds to the existing functionality of Packt’s original website, but now also offers a new, enhanced customer experience with an advanced design. read more

---

Recently, I've been working with the Drupal Association in determining the most effective ways that the association can help user groups organize local Drupal camps. One of the first thing we realized was that we didn't have any hard data on how camps were actually organized. We decided to create a survey for camp organizers to collect some data. The resulting survey has been available for about a month, and we've collected 31 responses. Not all surveys were completed, so not all of the responses total 31. If you're a DrupalCamp organizer and haven't completed the survey yet, please do so! Here's a rundown of the results to date: 8 were one-day camps 20 were two-day camps 3 were three-day camps 12 countries were represented Canada, Czech Republic, France, Germany, Ireland, Italy, New Zealand, Nicaragua, Romainia, Spain, United Kingdome, and the United States. It is not a big surprise that most camps were multi-day camps. I was surprised by the three-day camps. We didn't collect information about what took place each day, I'd be curious to know if the three-day camps were comprised of three days of sessions or something else (code sprint? coding for a cause?) Average attendance was 135 attendees, range was 45-375. 11 camps had less than 100 attendees 16 camps had between 100 and 200 attendees 3 camps has over 200 attendees Largest camp was DrupalCamp Spain 2010 with 375 attendees. The total combined number of attendees of all reported camps was 4,044. Average budget was $5,429.50 Largest budget was $31,319 (DrupalCamp Spain 2010)! 11 camps had a budget of less than $2,500 8 camps had a budget of between $2,500 and $7,500 0 camps had a budget of between $7,500 and $10,000 5 camps had a budget of over $10,000 The average cost per participant was $33.93 (low was $5.00, high was $90.91) The total combined budget of all reported camps was $130,308 (all amounts in USD) With the total number of attendees of 4,419, the reporting camps were collectively larger than DrupalCon SF 2010! For all camps, the average cost per participant was $29.49, roughly 10% of what a ticket to DrupalCon SF 2010 cost. Clearly, camps offer an amazing cost-effective opportunity for new and existing Drupalistas. 12 camps charged an admission fee ranging from $5 to $43 3 camps had their admission fee provide less than 25% of their total income 6 camps had their admission fee provide 25% and 50% of their total income 3 camps had their admission fee provide more than 50% of their total income 13 camps charged an admission fee to recover some costs of the camp 8 camps charged an admission fee to get a more accurate count of attendees 6 camps charged an admission fee to appear more professional 1 camp charged and admission fee because they wanted active developers, not newbies (multiple answers were allowed) As one of the organizers of Florida DrupalCamp, we debated charging a small admission fee. Our main reason for ultimately deciding to charge $6 was that we felt it was important to have an accurate count of attendees for planning purposes. Obviously, being able to recover some of the costs of the camp was helpful as well, but there appears to be no negative repercussions from charging a small admission fee. 13 camps reported a profit 0 camps reported an loss Average profit was $1,620.46 Largest profit was $8,000 6 camps had a profit of less than $1,000 7 camps had a profit of more than $1,000 While we didn't ask explicity what camps did with any operating profit, conversations I've had with other camp organizers indicate that most profit is saved to be used as seed money for a future camp. 8 camps paid for expenses out of pocket 14 camps had sponsors pay for expenses directly 9 camps paid for expenses out of a user group or camp account 4 camps had a 3rd party manage income and expenses 1 camp created a legal organization specifically for the event 5 camps partnered with a 501(c)3 organization 6 camps partnered with another type of organization 19 camps utilized no legal organization at all 1 camp purchased event insurance from their venue 2 camps purchased event insurance from an agent/carrier Providing a financial and legal mechanism for camps is one way that the association has indicated that it might be interested in helping camps. Less than half of the camps utilized a legal entity or a dedicated account to handle finances. Surprisingly, only 3 camps purchased any kind of event insurance. Granted, some venues include event insurance as part of the rental fee, but this is something that should be considered for all camps - especially larger ones. 7 camps purchased t-shirts to give away to participants 5 camps purchased t-shirts to sell to participants 19 camps provided morning drinks/snacks 20 camps provided lunch 15 camps provided afternoon drinks/snacks 8 camps provided evening drinks/snacks 4 camps rented additional equipment (chairs, projectors, PA systems, venues, internet services) Other items paid for by camps included: notebooks, fliers, posters, bags, badges, patches, lanyards, banners, raffle tickets, sign holders. In addition, it is assumed that at some camps, sponsors provided some of these items. 10 camps had 10 or less volunteers 13 camps had between 10 and 20 volunteers 1 camp had more than 20 volunteers The average participants per volunteer was 15.8 (low was 4, high was 61.67) Larger camps tended to have a participant-to-volunteer ratio of between 10 and 15, while smaller camps were a bit lower. Three camps had participant-to-volunteer ratios over over 30, which skewed the average (and probably made for some very tired volunteers!) 2 camps organized their camp sessions a low degree ("unconference style") 9 camps organized their camp sessions to a medium degree ("seeded the camp") 13 camps organized their camp sessions to a high degree ("all sessions pre-planned") Clearly, the majority of the camps were more conference-like than unconference-like. Conference-like camps add an additional layer of complexity, resulting in the need for additional volunteers (both organizers and speakers), but probably results in better attendance (more people might be willing to attend if they know what to expect) and a wider variety of Drupalistas (especially if there are different levels and topics of sessions). Another possible benefit might be an increase in the number of sponsors - if they see an organized program, they might be more willing to participate. The last question of the survey was for camp organizers to add any additional comments they thought might be helpful. Here's a sample: "We organized on a Google Wave, letting everyone who was interested join the conversation. We picked a good venue (Temple U, where one organizer works) who also donated the food and took care of a lot. We used a pretty basic site which we built in a one evening open sprint for the previous camp, and updated its theme with a new design. Overall, people step in and do what's needed and we don't do a whole lot of organizing and have no real power structure or people seeking power in the process. On the other hand, we always have our camps on a weekday because we are more professionals than hobbyists, and they've always managed to be smooth and professional." "We held in the camp in a very small village in the West of Ireland. It was held in a beautiful venue - the Burren College of Art which was about a mile from Ballyvaughan village. The idea behind this was that in a small and lovely location, it would be very easy for socialise during the weekend - and so it proved. We found this was as helpful as the pre-planned sessions themselves and people loved having the camp in a place that had a unique character in itself. We also found that staff and management of the Burren College of Art (who gave the use of their venue for free) were also very enthusiastic and helpful as it was an unusual (to them) conference to host." "Focused on track on beginners - soup-to-nuts intro to basics of Drupal core, how to install modules, some basic CCK & Views." "We did a mini, regional Drupalcon for drupal 'professionals' - no newbie track." "Having a focus on developers allowed us to get a lot of high-quality sessions, even with guest speakers from outside the Drupal world (php, mysql). The drawback was less sessions targeted at beginners (even though no restriction was imposed)." "We got it organised, with 45 people signed up, within 2 weeks. Only marketing was through twitter." "We partnered with local university for space, WiFi, most venue infrastructure." "We had a great party the night before and planned sessions. Unconference-style, but with good people ready to give talks." Drupal Association

---

As our community grows, it is imperative that we preserve the what got us here. Namely, we keep Drupal a fun, welcoming, challenging, and fair place to play. IMO, we need to proactively state our shared ideals with respect to conduct. Think of this as coding standards for people :) Our friends at Ubuntu have blazed a brilliant trail in this area. They use our CMS, and I propose that we use their Code of Conduct. Adopt the Ubuntu Code of Conduct. Make very light edits to the UCOC just to swap the word Ubuntu with Drupal and and remove reference to conflict resolution process. See my proposal below. I propose to avoid bikeshedding and avoid further edits for now. Write a handbook page where we adopt the DCOC. Add prominent links to this document from drupal.org, groups.drupal.org, etc. Add a user profile checkbox where users can optionally affirm their support for the Drupal Code of Conduct. There are no repercussions to checking or not checking this box. Its just a grassroots way to show that many members of drupal.org believe on our own Code. Post the news on drupal.org front page Build upon the DCOC with a conflict resolution policy. Again, Ubuntu has a really strong model. Have a look at it. Such a policy will really help groups.drupal.org and IRC administrators as they deal with the inevitable trolls in our world. If this sounds too formal for Drupal, I sort of agree with you. But in the end, we want Drupal to be big and successful and a force for positive change in the world. Without a code of conduct, we impair this goal. We need to shout from the rooftops about who we are and how we operate. We need to recruit like-minded people. And we need to clearly deal with trolls who throw roadblocks toward our goals. This is bridge building, in classic Drupal tradition. The DCOC finally documents the unwritten guidelines that have been so instrumental in the healthy/happy development and growth of Drupal to-date. It's a numerical fact that we're growing beyond the scale at which we can rely on informal standards and individual personalities to guard the spirit of the community. Lets discuss the many details here. I hope to synthesize all feedback and make a recommendation after a couple of weeks. Lets christen this the webchick model of community decision making. We are following her brilliant lead in pushing the community to modernize its version control platform. Feel free to blog and microblog (use #DCOC keyword) about this in order to get the best minds talking here. CAPS indicate changes from the Ubuntu Code of Conduct Be considerate. Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should take those consequences into account when making decisions. DRUPAL has millions of users and thousands of contributors. Even if it's not obvious at the time, our contributions to DRUPAL will impact the work of others. For example, changes to code, infrastructure, policy, documentation, and translations during a release may negatively impact others' work. Be respectful. The DRUPAL community and its members treat one another with respect. Everyone can make a valuable contribution to DRUPAL. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the DRUPAL community to be respectful when dealing with other contributors as well as with people outside the DRUPAL project and with users of DRUPAL. Be collaborative. Collaboration is central to DRUPAL and to the larger free software community. This collaboration involves individuals working with others in teams within DRUPAL, teams working with each other within DRUPAL, and individuals and teams within DRUPAL working with other projects outside. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream projects and others in the free software community to coordinate our technical, advocacy, documentation, and other work. Our work should be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress. When we disagree, we consult others. OMIT THIS SECTION UNTIL WE HAVE CONFLICT RESOLUTION PROCESS When we are unsure, we ask for help. Nobody knows everything, and nobody is expected to be perfect in the DRUPAL community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked questions should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum. Step down considerately. Members of every project come and go and DRUPAL is no different. When somebody leaves or disengages from the project, in whole or in part, we ask that they do so in a way that minimises disruption to the project. This means they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. Drupal.org policies

---

We are continuing to work to make DrupalCon Copenhagen as awesome as possible, but we wanted to take some time to give you an update on what we have been working on lately: As you may have noticed, the deadline for submitting a session has been moved back to June 27th. Voting on the sessions opens on June 28th and closes on July 8th. We will notify all speakers and post the full schedule on July 18th. The votes for the different sessions will be used by the track chairs to inform their decision of which sessions get selected. If your session isn't selected for one of the main conference tracks, please consider doing it as a Birds of a Feather (BOF) session instead. We will post more information about how to announce your BOF sessions as we get closer to the conference. If you are not attending one of the training sessions on August 23rd, we would love to see you at the Unconference. This will be a perfect opportunity to connect with the local open source community and to discuss issues outside of the Drupal-sphere. The Unconference will be run BarCamp-style and it will be free to attend, but please register in advance to help us determine how much coffee we need to brew. read more

---

PitBulls.org is a community and information site centered around the American Pit Bull Terrier, usually referred to as Pit Bulls. Pit Bulls get a lot of coverage in the media, usually negative, because there is rampant fear of the breed. They are also often the target of Breed Specific Legislation (BSL). PitBulls.org aims to share another perspective, those of passionate Pit Bull owners. The main mission of the site is to convey that Pit Bulls make great family pets, to get the word out that a dog is only a reflection how it is treated and raised, and to provide a central hub where owners can connect and share their pictures and stories. The site was conceived and developed by PropDrop Web Development and Marketing. PropDrop not only does client work, but also performs web niche analysis and develops in-house web properties based on that research in order to gain market share in a wide variety of areas. PitBulls.org is one of these properties. It also doesn't hurt that we are dog lovers and own a Pit Bull/Lab mix named Bauer, so we are our own audience in some sense. PropDrop uses Drupal exclusively for its in-house projects, because we can create a community and information site with some advanced features in under 2 weeks, with everything optimized for search with little effort. It also gives us the opportunity to expand a site's feature set in the future without interfering with current functionality, taking a site in directions that might not be possible with other content management systems. read more

---

Technorati and Ingboo have partnered together to provide an all new kind of subscription experience for Technorati content, including tagged posts. Look for a blue Ingboo icon for a full range of subscription options. Feeds are also available for: Hottest Blogosphere Posts Latest Original Articles from Technorati The Technorati Blog We also have channel feeds, writer feeds, and editorial tag feeds, which can be found on their respective pages.

---

There's a mistake I've made which a few others have made too. The mistake is rushing into your new Drupal site and populating your menu ...gotdrupal.com

---

Devel release on the day that Drupal is released. A suite of modules containing fun for both ...drupal.org

---

Dries Buytaert relates a synopsis of his life with Drupal. From its inception during Buytaert's "typical geek" undergraduate days in ...mitworld.mit.edu

---

Like many other content management systems, Drupal is built on PHP . With PHP , you can dig in and make it do whatever you want. Likewise, you can ...gotdrupal.com

---

Is Drupal a CMS? Or is Drupal an Application Framework? Yes! This is a brief introduction to Drupal. UPDATE: This video won 6 Telly Awards.youtube.com

---

movielibrary.lynda.com In this lynda.com video podcast, learn to customize page themes in Drupal. Drupal is a free, open-source content management ...youtube.com

---

Introduction to Drupal Try our new player Mdailymotion.com

---

Google Tech Talks October, 8 2007 ABSTRACT Geoff Butterfield, Senior Technical Producer at The George Lucas Educational Foundation, and Angie ...youtube.com

---

Google Tech Talks October, 8 2007 ABSTRACT Geoff Butterfield, Senior Technical Producer at The George Lucas Educational Foundation, and Angie ...video.google.com

---

What is Drupal and what can you do with it? In this video I hope to show the basics by building a website in minutes using Drupal. To see more ...youtube.com

---