Planet Drupal

Syndicate content - aggregated feeds in category Planet Drupal
Updated: 7 min 51 sec ago

BlackMesh: Looking at DrupalCon Amsterdam Sprints, Upcoming sprints for you to attend

Thu, 10/30/2014 - 05:00
span class=submitted-by/spandiv class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encoded p By:br / Tim Erickson, a href=, a href= from a href= / Alina, a href=, a href= / Cathy Theys, a href=, a href= from BlackMesh/p h2 DrupalCon Amsterdam Sprints/h2 p DrupalCon is a great place to enhance your Drupal skills, learn about the latest modules, and improve your theming techniques. Sure, there are sessions, keynotes, vendor displays, and parties... like trivia night!/p p But.. there is also the opportunity to look behind the curtain and see how the software really gets made. And, more importantly, to lend your hand in making it. For six days, three both before and after DrupalCon, there are dedicated sprint opportunities where you can hang out with other Drupalistas testing, summarizing issues, writing documentation, working on patches, or generally contributing to the development of Drupal and the Drupal community./p p We want to share some details about the DrupalCon Amsterdam Sprints (and pictures to reminisce about the good times) and mention some upcoming sprints that you can hopefully attend./p ulli a href=#sponsorsSponsors supporting the sprinters/a/li li a href=#preconPre-con Extended sprints on Saturday and Sunday/a (60 Saturday, 100 Sunday, 180 Monday) /li li a href=#duringDuring the con/a/li li a href=#mentoredFriday Sprint/a (450 people) /li li a href=#postconPost-con Extended sprints on Saturday and Sunday/a (80 Saturday, 60 Sun) /li li a href=#feedbackFeedback about the sprints/a/li li a href=#upcomingUpcoming sprints/a/li /ulh3 id=sponsors Sprint sponsors/h3 ulli a href= Association/a, a href= li a href= (Large Scale Drupal), a href= li a href=, a href= li a href=, a href= li a href= Hernandez/a, a href= li a href=, a href= /ulp Our sponsors helped us have:/p ulli Space: ulli Co-working space Saturday and Sunday before the con. /li li Sprint space at the venue Monday-Thursday. /li li Big sprint space Friday. /li li Co-working space Saturday and Sunday after the con. /li /ul/li li Food and coffee all of the days. /li li Sprint supplies: task cards, stickers, markers, signs, flip charts. /li li Mentor thank you dinner. /li /ulh3 id=precon Pre-con sprints/h3 p During the weekend before DrupalCon 60 people gathered on Saturday and 100 on Sunday at a href= Berlage/a, a fantastic old castle just blocks from the central train station. On most days the Berlage serves as co-working space. For 48 hours it was home to contributors working together on Drupal core, contrib projects, distributions and itself. Our supportive sponsors supplied lunch and coffee on both days while contributors worked on a number of initiatives: Multilingual, Drupal 8 criticals and beta blocking issues, Headless Drupal and REST, porting contrib projects to Drupal 8, Drupal 8 Frontend United, Search,, Behat (Behavior Driven and javascript/frontend testing), Commerce, Panopoly, Rules, Media, Documentation, Migration, Performance, Modernizing Testbot, and more./p p a href= alt=Outside of the Berlage src= width=332 //abr / The outside of the Berlage co-working space (castle) with the Drupal Association / (photo: a href= p a href= alt=Sprinters working inside the Berlage castle src= width=573 //abr / Sprinters sprinting inside the cool looking /imarthinal, franSeva, estoyausente, YesCT, Ryan Weal/ibr / (photo: a href= p We had lots of rooms for groups to gather at the Berlage./p p a href= alt=Field API room at the Berlage sprint. src= width=573 //abr /ipwolanin, dawehner, wimleers, Hydra, swentel/ibr / (photo: a href= p a href= alt=Field API room at the Berlage sprint. src= width=573 //abr /iSutharsan, yched, Berdir/ibr / (photo: a href= p On Monday sprint attendance grew to 180 sprinters. We moved to the conference venue, Amsterdam RAI. Other pre-conference events taking place included trainings, the Community Summit, and the Business Summit. At this particular DrupalCon there was much excitement about the anticipated beta release of Drupal. Many people did a lot of testing to make sure that the beta would be ready./p p a href= alt=Sprinters working together, talking. src= width=573 //abr / Discussing a beta blocker issue they /ilauriii, sihv, Gábor Hojtsy, lanchez/ibr / (photo: a href= /p p a href= alt=Mauzeh, Tobias and the sprint location at the venue. src= width=573 //abr / Lots of people sprinting and testing the beta candidate, with support from experienced core contributors walking around and /itstoeckler, mauzeh/ibr / (photo: a href= /p h3 id=during During the con/h3 p Sprinting continued during the conference, Tuesday through Thursday. And, to prepare for Friday's mentored sprint, the core mentoring team scheduled a series of 8 BOFs (‘Birds of a Feather’ or informal sessions). Preparations included mentor orientation, setting up local environments, and reading, updating, and tagging issues in the Drupal issue queue. Mentoring BoFs were open to all conference participants./p p a href= title=Untitled by stpaultim, on Flickrimg alt=Mentors sitting in a BoF room src= width=573 //abr / Mentor Trainingbr /iYesCT, sqndr, -, -, lazysoundsystem, neoxavier, Mac_Weber, patrickd, roderik, jmolivas, marcvangend, -, realityloop, rteijeiro/ibr / (photo: a href=;stpaultim/a)/p p To promote contribution sprints, mentors volunteered at the mentoring booth in the exhibition hall during all three days of DrupalCon. Conference attendees who visited the booth learned about the Friday sprints. Mentors also recruited additional mentors, and encouraged everyone to get involved in contributing to Drupal./p p a href= title=Untitled by stpaultim, on Flickrimg alt=The mentor booth with lots of colorful signs src= width=573 //abr / The mentor booth with lots of signage, and welcoming /imradcliffe, kgoel/ibr / (photo: a href=;stpaultim /a)/p p At the booth, conference attendees were able to pick up our new a href= role task cards/a and a href= which outlined some of the various ways that people can contribute to Drupal and provided them with a sticker as recognition for the specific roles that they already play./p p a href= alt=picture of the cards and stickers src= //abr /a href= cards/a and a href= / (photo: a href= /p h3 id=mentored Mentored Sprint/h3 p In Amsterdam, 450 people showed up to contribute to Drupal on Friday./p p a href= alt=lots of people at the Friday sprint src= width=573 //abr / (photo: a href= p People gathered in groups to work on issues together./p p a href= alt=A group around a table. src= width=573 //abr /i-, -, -, -, -/ibr / (photo: a href= p For many people the highlight of the week is the large “mentored” sprint on Friday. 180 of the 450 participated in our a href= sprinter workshop/a designed to help Drupal users and developers better understand the community, the issue queues, and contribution. The workshop helped people install the tools they would use as contributors. Another 100 were ready to start work right away with our 50 mentors. Throughout the day people from the first-time sprinter workshop transitioned to contributing with other sprinters and mentors. Sprinters and mentors helped people identify issues that had tasks that aligned with their specific skills and experience./p p a href= title=Untitled by stpaultim, on Flickrimg alt=The dark workshop room with presentation screen, filled with people. src= width=573 //abr / The workshop / (photo: a href=;stpaultim/a)/p p a href= title=Untitled by stpaultim, on Flickrimg alt=Mentors checking in with tables full of sprinters. src= width=573 //abr / Mentors (in orange shirts): irachel_norfolk, roderik/ibr / (photo: a href=;stpaultim/a)/p p a href= title=Untitled by stpaultim, on Flickrimg alt=Mentored Core Sprint room sign, modified with marker to have a list of good and not good novice tasks. src= width=332 //abr / Hand written signs were everywhere!br / (photo: a href=;stpaultim/a)/p p a href= src= //abr / A group picture of some of the /imradcliffe, Aimee Degnan, alimac, kgoel, rteijero, Deciphered, emma.maria, mon_franco, patrickd, 8thom, -, lauriii, marcvangend, ceng, Ryan Weal, YesCT, realityloop, -, lazysoundsystem, roderik, Xano, David Hernández, -, -, -, -/ibr / (photo: a href= p Near the end of the day, over 100 sprinters (both beginners and veterans) gathered to watch the work of first time contributors get committed (added) to Drupal core. Angie Byron (webchick) walked the audience through the process of evaluating, testing, and then committing a patch to Drupal core./p p a href= title=Untitled by Pedro Lozano, on Flickrimg alt=webchick celebrating and showing her screen on the overhead. Contributors clapping. src= width=573 //abr / Live commit by webchickbr /iwebchick, -, -, marcvangend/ibr / (photo: a href= Lozano/a)/p h3 id=postcon Extended sprints on Saturday and Sunday/h3 p On Saturday after DrupalCon 80 dedicated contributors moved back to the Berlage to continue the work on Drupal core. 60 people came to contribute on Sunday. During these final days of extended sprints, Drupal beginners and newcomers had the chance to exercise their newly acquired skills while working together with some of the smartest and most experienced Drupal contributors in the world. The value of the skills exchanges and personal relationships that come from working in this kind of environment is cannot be underestimated. While there is an abundance of activity during Friday’s DrupalCon contribution sprints, the atmosphere during extended sprints is a bit more relaxed. Attending the pre and post-con sprints gives sprinters time to dive deep into issues and tie up loose ends. After a number of hallway and after-session conversations, contributors working on specific Drupal 8 initiatives meet to sketch out ideas, use whiteboards or any means of note-taking to make plans for the future./p p a href= alt=Sprinters in the front end room. src= width=573 //abr /iLoMo, Outi, pfrenssen, lauriii, mortendk, emma.maria, lewisnyman/ibr / (photo: a href=;stpaultim/a)/p p a href= alt=Berlage first room filled with people at all the tables, some high tables. src= width=573 //abr /iAimee Degnan, Schnitzel, dixon, -, Xano, alimac, boris, Gábor Hojtsy, realityloop, YesCT, justafish, eatings, fgm, penyaskito, pcambra, -/ibr / (photo: a href=;stpaultim/a)/p p a href= sprint room at the Berlage. src= width=573 //abr /i-, jthorson, opdavies, drumm, RuthieF, -, -, killes, dasrecht/ibr / (photo: a href=;stpaultim/a)/p h3 id=feedback Feedback about the sprints/h3 ulli a href= for the First Time/a - Blog post by a href= li a href= Rookie to Drupal Core Contributor in One Day/a - Blog post by a href= li a href= Amsterdam, 2014/a - Blog post by a href= li em“Mentoring at a href= sprints is the most rewarding and enjoyable part of the week :) lt;3 a href= a href= - a href= Tweet/a from a href= li em“One hour at the a href= code sprint and I've already submitted my first patch. It is going to be a good week.”/em - a href= Tweet/a from a href= li a href=, I'm George! I'm your mentor!/a - Blog post by Thamas (a href= /li /ulp Please contact me to get your DrupalCon Amsterdam sprint related blog added to the list here./p h3 id=upcoming Upcoming sprints/h3 ulli a href= (a href= details/a November 5 - 10 2014) /li li a href= Sprint Weekend/a January 17, 18 2015 /li li a href=https://latinamerica2015.drupal.orgDrupalCon Latin America in Bogota/a (a href= details/a Feb 8 - 13 2015) /li li lots of camps, check a href= (The drupal event location visualization tool.) /li li a href=http://devdays.drupalcamp.frDrupal Dev Days/a April 2015 /li li DrupalCon North America in a href= Angeles/a (sprint May 9 - 17 2015) /li li DrupalCon Europe in a href= (sprint Sept 19 - 27 2015) /li /ulp Plan your travel for the next event so you can sprint with us too!/p h3 Corrections/h3 p If there are corrections, for example of names of people in the pictures, please let me know. -Cathy, a href=, or a href= contact form/a./p /div/div/divdiv class=field field-name-field-tags field-type-taxonomy-term-reference field-label-hiddendiv class=field-itemsdiv class=field-item evena href=/tags/drupal typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=Drupal/a/divdiv class=field-item odda href=/tags/sprints typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=Sprints/a/divdiv class=field-item evena href=/tags/drupalcon typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=DrupalCon/a/divdiv class=field-item odda href=/tags/drupal-planet typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=Drupal Planet/a/div/div/divdiv class=field field-name-field-blog-images field-type-image field-label-hiddendiv class=field-itemsdiv class=field-item evenimg typeof=foaf:Image src= width=640 height=424 alt=Lots of people at the Friday sprint title=Friday sprint //div/div/div RESTful Discovery - Who knows about your API?

Wed, 10/29/2014 - 23:00
pAs extremely pedantic developers we take documenting our APIs very seriously. It#39;s not rare to see a good patch rejected in code review just because the PHPdocs weren#39;t clear enough, or a code@param/code wasn#39;t declared properly./p pIn fact, I often explain to junior devs that the most important part of a function is its signature, and the PHPdocs. The body of the function is just quot;implementation detailsquot;. How it communicates its meaning to the person reading it is the vital part./p pBut where does this whole pedantic mindset got when we open up our web-services?br I would argue that at least 95% of the developers who expose their web-service simply enable RESTws without any modifications. And here#39;s what a developer implementing your web-service will see when visiting code/node.json/code:/p pa href= reading…/a/p

Mediacurrent: 10 Things I Wish I Knew About Drupal 2 Years Ago

Wed, 10/29/2014 - 21:44
img typeof=foaf:Image src= width=200 height=152 alt=10 things I wish I knew about Drupal 2 years ago title=10 things I wish I knew about Drupal 2 years ago / pThey say that hindsight is 20/20. With the many advances that have happened in the Drupal community recently, we asked our team What is the one thing you wish you knew about Drupal two years ago? /p pI wish I knew about the Headless Drupal initiative so I that I could be ahead of the curve as far as the Javascript technologies that it will require. - a href= target=_blankChris Doherty/a/p

Metal Toad: Seeing Long Term Technology Adoption as Evolution

Wed, 10/29/2014 - 18:31
div pMuch like an evolutionary tree our goal in technology adoption is too continue to move forward and evolve, rather than getting caught in a dead end.  In the natural world, becoming bigger can be good but can lead to extinction events should the environment or food source change.  Right now we are in a technology Jurassic.../p /div ul class=links inlineli class=0 first lasta href= rel=tag title=Seeing Long Term Technology Adoption as EvolutionRead more/a/li /ul

Code Karate: Finding the right brand

Wed, 10/29/2014 - 12:28
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpIf you have been around for awhile you have noticed that our branding has been, we/p/div/div/div

Acquia: Drupal in the Philipines, Own your Own Code More - Luc Bézier

Wed, 10/29/2014 - 12:00
div class=form-item form-type-item labelLanguage /label English /div div class=field field-name-body field-type-text-with-summary field-label-hidden div class=field-items div property=content:encoded class=field-item evenh2 On being an open source developerbr //h2 p Like a lot of people, I did both sides of technology; working on paid, proprietary systems [and open source]. There is a big difference. I can't imagine myself going back to any proprietary system where I have to pay; I can't share the code I am doing with anyone; I have to ask a company about the right tool to use. I love the way that everybody contributes to the same piece of code, trying to make it the best ... and for free! /p/div /div /div span property=dc:title content=Drupal in the Philipines, Own your Own Code amp; More - Luc Bézier class=rdf-meta/span

The Cherry Hill Company: Islandora Camp Colorado - Bringing Islandora and Drupal closer

Tue, 10/28/2014 - 23:40
pFrom October 13 - 16, 2014, I had the opportunity to go to (and the priviledge to present at) Islandora Camp Colorado (a href= These were four fairly intensive days, including a last day workshop looking to the future with Fedora Commons 4.x. We had a one day introduction to Islandora, a day of workshops, and a final day of community presentations on how Libraries (and companies that work with Libraries such as ours) are using Islandora. The future looks quite interesting for the relationship between Fedora Commons and Drupal./p ulliThe new version of Islandora allows you to regenerate derivatives on the fly. You can specify which datastreams are derivatives of (what I am calling) parent datastreams. As a result, the new feature allows you to regenerate a derivative through the UI or possibly via Drush, which something the Colorado Alliance is working to have working with the .../li/ul a href=/ class=views-more-linkRead more »/a frontpage posts: Drupal Camp Ohio

Tue, 10/28/2014 - 21:30
div class=field field-type-datestamp field-field-start7 div class=field-items div class=field-item odd div class=field-label-inline-first Start:nbsp;/div span class=date-display-start2014-11-14 (All day)/spanspan class=date-display-separator - /spanspan class=date-display-end2014-11-15 (All day) America/Chicago/span /div /div /div div class=field field-type-text field-field-event-type div class=field-items div class=field-item odd Drupalcamp or Regional Summit /div /div /div div class=field field-type-userreference field-field-organizers div class=field-labelOrganizers:nbsp;/div div class=field-items div class=field-item odd a href=/user/1557328 title=View user profile.themic8/a /div /div /div div class=field field-type-text field-field-url div class=field-items div class=field-item odd pa href= title= /div /div /div pDrupalCamp Ohio 2014 returns to The Ohio State University's Nationwide and Ohio Farm Bureau 4-H Center, for another two-day camp to build on last year's success, and will include keynote speeches, topical sessions, Beginners Training, Birds of a Feather breakouts, and code / -- a href= title=

Drupal core announcements: This month in Drupal Documentation

Tue, 10/28/2014 - 21:12
pThis is the monthly update from the a href= Working Group (DocWG)/a on what has been going on in Drupal Documentation. Because this is posted in the Core group, comments for this post are disabled, but if you have comments or suggestions, please see the DocWG home page for how to contact us./p h3Drupalcon Documentation Sprint/h3 pA small group of sprinters gathered on the last day of Drupalcon to work on a couple of Documentation issues. During the sprint the a href= guide was being reviewed/a for Drupal 8 and there is still work left to process some of that feedback. Furthermore a start was made a href= the Theming guide for Drupal 8/a (see below for more)./p h3Theming guide for Drupal 8/h3 pa href= theming guide for Drupal 8/a has been written almost from scratch and is beginning to take shape. It already covers such topics as:/p ul liDefining a theme with an .info.yml file/li liTheme folder structure/li liWorking With Twig Templates/li liAdding stylesheets (CSS) to a Drupal 8 theme/li liCreating a Drupal 8 sub-theme/li liUsing Classy as a base theme/li liAdding JavaScript to a Drupal 8 Theme/li /ul pThe theming guide still needs a lot of improvement. So if theming is your thing and you have some spare time this month, then please a href= it/a. Every little improvement is helpful. Note that you can edit documentation pages on directly and that there is no need to leave comments./p h4Credits/h4 pa href= Tirez's theming guide/a, many a href=[8]stackexchange Qamp;A's/a and various blog posts proved invaluable input for writing the guide./p h3Thanks for contributing!/h3 pSince a href= last post from October 1/a about 280 contributors have made some 1100 documentation page revisions, including 10 people that made 15 or more edits. Thank you batigolix, Pierre.Vriens, SERVANT14, Anthony Pero, camorim, sanchiz, tvn, Pere Orga, LoMo, phenaproxima and all the others and keep up the good work!/p h3Changes to documentation on ul liThe a href= of keywords/a in the sidebar of documentation pages in has been improved./li liThe display of the a href= author of documentation pages has been removed/a. This was done because in many cases the wrong original author was being shown. Now only the most recent revision authors are being shown. /li /ul h3Documentation Working Group meetings are open/h3 pThe monthly meeting of the Documentation Working Group is open to anyone who would like to attend. a href= us/a if you want to join the meeting./p h3Documentation Priorities/h3 pThe a href= documentation priorities page/a is always a good place to look to figure out what to work on, and has been updated recently./p pIf you're new to contributing to documentation, these projects may seem a bit overwhelming -- so why not try out a a href= contributor task/a to get started?/p

Drupal Watchdog: Drupal 8 Modules

Tue, 10/28/2014 - 20:08
div class=field field--article-edit-printtype field-type-list-text field-label-hidden field--rss Feature /div div class=field field--article-body field-type-text-long field-label-hidden field--rss pThis article will be more about the patterns you need to use during Drupal 8 development than how to fit the various pieces together. /p pimg src= class=img-responsive img-thumbnail margin-left alt=Implements of Mathematics width=50% align=right /There’s good reason for this approach: fitting the pieces together has plenty of examples, change records, and whatnot – but many pieces of the puzzle are entirely new to Drupal developers. /p h3The Background/h3 pThe first half of this article provides general PHP information which uses Drupal as an example, but is not Drupal specific. The idea behind this is that the knowledge can be reused well (indeed, this was also a design goal for Drupal 8)./p h4Classes, Objects, Interfaces/h4 pIn Drupal 7, span class=geshifiltercode class=php geshifilter-phpstdClass/code/span was used at a lot of places; ergo, classes (like span class=geshifiltercode class=php geshifilter-phpstdClass/code/span) and objects (instances of a class, like node, user, etc.) should be familiar. span class=geshifiltercode class=php geshifilter-phpstdClass/code/span is a class without methods, and the properties are not defined ahead of time. In PHP, it’s valid to set any property on an object, even if it’s not defined on its class. So, span class=geshifiltercode class=php geshifilter-phpstdClass/code/span worked much like an associated array, except that it used arrows instead of brackets. Another important distinction between arrays and objects is passing them to a function: in PHP5, if a function/method gets an object and then changes the object, it will affect the object everywhere – objects are not copied every time, while arrays are. /p /div

Aten Design Group: Modularizing JavaScript

Tue, 10/28/2014 - 19:17
img src= width=1000 height=600 alt= /pI came to Drupal from a JavaScript background and was happy to see a module system in place. Have you ever wished you could write your JavaScript modularly just like your PHP in order to take advantage of testing, better documentation and the a href= One Thing Well/a philosophy? Well I have the solution for you: a href= and a href=http://npmjs.orgNPM/a!/p h2Getting Started/h2 pIn order to take advantage of JavaScript modularity you will need codenode/code and codenpm/code which can be installed together using a href= of these methods/a./p h2Creating a JavaScript Module/h2 pJavaScript modules are similar to the PHP include system in that they allow the developer to separate their code across multiple files. The key difference is that JavaScript uses the syntax coderequire/code to pull the emexported/em part of a JavaScript file into the current file's variable of choice. Let's take a look./p pSimply create a JavaScript file, do whatever you’re trying to do and assign the resulting value (usually a class or object) to codemodule.exports/code./p div class=geshifilterpre class=geshifilter-javascriptspan style=color: #009900; font-style: italic;// src/lib/MyClass.js/span nbsp; module.span style=color: #006600;exports/span = span style=color: #003366; font-weight: bold;function/span MyClassspan style=color: #66cc66;#40;/spanoptsspan style=color: #66cc66;#41;/span span style=color: #66cc66;#123;/spanspan style=color: #66cc66;#125;/span nbsp; MyClass.span style=color: #006600;prototype/span.span style=color: #006600;magic/span = span style=color: #003366; font-weight: bold;function/spanspan style=color: #66cc66;#40;/spanspan style=color: #66cc66;#41;/span span style=color: #66cc66;#123;/span console.span style=color: #006600;log/spanspan style=color: #66cc66;#40;/span‘magic’span style=color: #66cc66;#41;/span; span style=color: #66cc66;#125;/span/pre/div pYou can now use codeMyClass.js/code from other JavaScript files like so:/p div class=geshifilterpre class=geshifilter-javascriptspan style=color: #009900; font-style: italic;// src/index.js/span span style=color: #003366; font-weight: bold;var/span MyClass = requirespan style=color: #66cc66;#40;/span‘.span style=color: #0066FF;/lib//spanMyClass’span style=color: #66cc66;#41;/span; nbsp; span style=color: #003366; font-weight: bold;var/span classy = span style=color: #003366; font-weight: bold;new/span MyClassspan style=color: #66cc66;#40;/spanspan style=color: #66cc66;#41;/span; nbsp; classy.span style=color: #006600;magic/spanspan style=color: #66cc66;#40;/spanspan style=color: #66cc66;#41;/span; span style=color: #009900; font-style: italic;// ‘magic’/span/pre/div h2NPM/h2 pPHP developers may be familiar with a href= NPM is the Composer of the JavaScript world. Both allow you to manage the dependencies of your project./p pBefore creating a custom module it's a great idea to see if it has already been written. a href= is the place to look. When you find a module you’d like to include in your project, retrieve it and add it as a dependency with codenpm/code. For example, to install lodash:/p div class=geshifilterpre class=geshifilter-textnpm install lodash --save/pre/div pThe save flag adds this dependency to the codepackage.json/code file. It might help to think of this as the JavaScript version of codecomposer.json./code All the dependencies for a project can be installed by running codenpm install/code within the directory containing codepackage.json/code or its sub-directories./p pRequiring modules from NPM is done just like local modules but you don’t have to provide the path, just use the module name. coderequire/code will look in the codenode_modules/code folder automatically./p div class=geshifilterpre class=geshifilter-javascriptspan style=color: #003366; font-weight: bold;var/span _ = requirespan style=color: #66cc66;#40;/span‘lodash’span style=color: #66cc66;#41;/span;/pre/div pa href= more about NPM and package.json on the NPM website./a/p h2The Browserify command/h2 pBrowserify reads your JavaScript files and resolves their codemodule.exports/code and coderequire/code's./p pYour main JavaScript file should be a compilation of its dependencies resulting in a useful piece of functionality for your website. To compile your multiple files into one that is browser ready we will use the a href= abbr title=Command Line InterfaceCLI/abbr./p pFirst install it globally with codenpm/code. Globally installed modules can be accessed from anywhere on your machine./p div class=geshifilterpre class=geshifilter-textnpm install -g browserify/pre/div pThen tell Browserify where your main JavaScript file is and redirect the output to where you want your compiled, browser-ready JS to be./p div class=geshifilterpre class=geshifilter-textbrowserify src/index.js gt; build/myModule.js/pre/div pcodebuild/myModule.js/code is now browser ready! Now you can add it to your website./p h2Come see me at BADCamp/h2 pThe above workflow is a great way to maintain custom Drupal modules with a lot of JavaScript. For more detailed information about using this workflow with Drupal — such as global dependencies, handling jQuery, task automation and testing — come a href= out my session at this year’s BADCamp!/a/p

Open Source Training: Node Gallery: The Easiest Drupal Photo Gallery

Tue, 10/28/2014 - 16:32
!-- Start ScreenSteps Content -- div class=LessonContent div class=LessonSummary pWe have several different Drupal photo gallery tutorials on this blog. The most popular are a href= Photo Galleries for Drupal 7/a and a href= Gallery for Drupal 6/a./p pHowever, although Views is powerful, it is too complex for many Drupal users and Node Gallery remains popular. So here's an update that shows how to use Node Gallery in Drupal 7./p pNode Gallery is still the easiest way to build a photo gallery in Drupal. It requires very little set-up and almost no configuration./pimg src= height=1 width=1/

Sooper Drupal Themes: Introducing version 5

Tue, 10/28/2014 - 16:11
div class=field-body pimg src= /br / Welcome to the fifth redesign of!br /img src= //p h2What's new at SooperThemes/h2 pThe fifth major update to is the biggest update ever. It's a completely new site, unlike the previous sites which were built on top of the original (2007!)! /p pThe new site comes with a big shift in focus. With Drupal 7 sites becoming more complex, and the upcoming Drupal 8 introducing new power and flexibility, but also complexity, we work hard to offer tools, services and products that allow everyone to profit form Drupal's flexibility without having to suffer the steep learning curve (alone). In addition to selling Drupal themes with turn-key demo sites we now offer more services:/p ulliCustom built ticket system on, to work alongside e-mail support/li liDesign to Drupal service, for affordable and top quality Drupal themes based on your own design/li liEnterprise Drupal services, including art direction, design, theming, data driven design and consulting./li liNo more one-off theme sales, total focus on club membership and long term support/li /ulpOur new tools are the best part, read on to learn about our major plans to support Drupal for small/medium businesses./p h2Drupal Developers will Love these New Tools:/h2 h3A new Distribution: Drupal CMS Powerstart/h3 pDrupal's awesome architecture is what makes it such an awesome alternative to competing CMS like Wordpress and Joomla, but setting up shop with Drupal is described by many as painful and too complicated. Here, Drupal's power in flexibility is also it's weakness. It takes too much time to install basic features like WYSIWYG with media management: you need to find modules and set up complicated configurations, sometimes needing patches or development versions of modules, external libraries, / To solve this problem, we created a a href= CMS/a Distribution, targeted to small business sites and aiming to make life easier for developers and shops who create small sites./p h3Drupal CMS Powerstart needs beta testers: a href= pDries has mentioned in several keynotes that Distributions are the key to make Drupal more accessible and therefore the Drupal ecosystem more succesful. We too believe distributions are the solution but we don't like how they are currently made and how they are managed by Therefore we have created a new interface: A user-friendly interface to our distribution that lets you pick features, so that you don't get a bulky distro with everything in it, and the kitchen sink./p pCheck out the custom build interface to Drupal CMS Powerstart: /p pa href= CMS Custom Build/a/p h2Twitter Bootstrap Fans will love what we did with Bootstrap 3/h2 pIn order to create a truly responsive distribution, we developed and refined a lot Bootstrap 3 Drupal-integration. Responsive grid control from Views, content organisation with Bootstrap shortcodes: a href= and all our features come with default layouts that regardless of whether you use a Bootstrap theme. /p pDevelopment of Drupal CMS Powerstart is sponsored by and if you want to support future development of this new platform, please help beta testing and/or consider becoming a member of our premium themes club, you can see our premium themed version of CMS Powerstart here: a href= - more a href= themes/a./p !--break-- /div h3 class=field-label Tags /h3 div class=field-tags a href=/category/tags/sooperthemes typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=sooperthemes/a /div div class=field-tags a href=/category/tags/drupal-7 typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=drupal 7/a /div div class=field-tags a href=/category/tags/drupal-8 typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=drupal 8/a /div div class=field-tags a href=/category/tags/distributions typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=distributions/a /div div class=field-tags a href=/tags/cms typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=cms/a /div div class=field-tags a href=/category/tags/planet typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=planet/a /div div class=field-tags a href=/category/tags/drupal-planet typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=drupal planet/a /div div class=field-tags a href=/tags/cms-powerstart typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=cms powerstart/a /div h3 class=field-label Drupal /h3 div class=field-drupal a href=/category/core-compatibility/7x typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=7.x/a /div

ERPAL: Drupal design patterns – do we need them?

Tue, 10/28/2014 - 14:56
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpAfter six years of working with Drupal, I’ve seen many successful Drupal projects. I’ve also felt how hard it is to become an experienced Drupal developer. When I asked myself why some Drupal projects succeed while others don’t, I came to this conclusion: the projects that integrate with Drupal core and the contrib ecosystem – i.e. the ones that use best practice deployment workflows and try to use configuration instead of custom code – keep their flexibility, stay maintainable and avoid niche know-how. This then ensures that the project can be continued even if the team changes. Of course, there are a href= of other non-technical factors that make projects successful/a but we’re focusing here on the technical ones. The problem is that there’s no central repository of best practices: almost all developers or Drupal shops have their own./p pThis brings me to the point of considering some Drupal design patterns. Whereas in object-oriented programming, developers have patterns for their object models to solve specific problems that appear again and again, we haven’t yet established any in Drupal. But if we look at the configuration layer of Drupal as a programming language, we could describe some patterns or best practices that would help others with problems that have already been solved hundreds of times before. This would have the same benefits as design patterns in other programming languages. Solutions for equivalent problems / requirements are always designed in a similar way. For any given workflow we could always use the same rules, so everybody would know where to go to change some behavior. The result would be that modules wouldn’t implement their own logic in code but provide actions, events and conditions, and some default rules. People still wouldn’t find a Drupal image gallery module but they would know how to build one according to some patterns. Of course we’d have a longer dependency chain for some modules, but is this really a problem if we’re depending on standard modules?/p pimg src= width=709 height=337 //p p /p h3When to choose which module – would patterns work for this?/h3 pWith more than 8000 modules available at, new Drupal users may find it hard to get started. What usually happens is that they enable lots of modules to test them; if the module works for their requirements, it remains enabled. If the user is a technical person, maybe even a developer, he/she will most likely use the Drupal API to extend the Drupal / But wouldn't it be great if we had a list of modules that were state of the art for best practices such as using rules for workflows and business logic, ECKs and fields for data structure modelling, views for lists and data queries, restWS and WSclient for communication with other applications, entity view modes in combination with panels for layouting, and features for the deployment. Considering the above, I’ve created the a href= application stack poster/a to collect all our modules – along with their specific use cases –and to share this overview with the community. Shouldn't we always have a Drupal-relevant set of modules in mind when it comes to the modelling process of our Drupal app? This would keep Drupal apps sustainable and flexible./p p /p h3Dos and don’ts/h3 pThere are also some examples of what not to do. In a few projects that had crashed before they came to us to be rebuilt, it became clear that the previous developers had exactly the problems listed above. They had no guide to help them figure out when to use the API and when to choose which module, which further led to code and architectures that nobody but the developer could maintain. After the first release, the projects weren’t extendible, as there was no deployment process established. Wouldn't it help to collect these examples as well, to help people avoid them and get on the right path with Drupal? With a list of positive and negative patterns, we could give users some objective criteria for rating the implementation of their Drupal project./p p /p h3Distributions – start from a higher level/h3 pDistributions built on such best practices as a href= commerce kickstart/a or a href= Platform/a provide a good starting point for new Drupal developers, since they can see how experienced Drupalistas created the distros and which modules they used. Distros can be showcases for Drupal design patterns or a kick-start for vertical use cases like e-commerce sites or business applications./p pIf we want the a href= community to grow/a, we should help others find the right starting point – not just any old one that could lead them off in the wrong direction: while they might see some quick results, if it wasn’t the right approach, they would only realize that after days of work. Once too much time has elapsed, with the money already spent and the deadline looming ever closer, nobody will ever refactor the Drupal application to improve its structure./p pWith Drupal design patterns, we’d be able to offer standard solutions to often-complex problems. What are your thoughts about Drupal design patterns? Would this bring us another step closer to making a href= into a world-leading web application framework/a?/p pimg src= width=709 height=337 //p /div/div/div

Drupalize.Me: Free Halloween Icon Set

Tue, 10/28/2014 - 14:04
div class=field field-name-body field-type-text-with-summary field-label-hidden text-content text-secondarydiv class=field-itemsdiv class=field-item evenpWith Halloween just around the corner, I thought it might be fun to hand out some tasty treats. Don't worry, you're not getting fruit or pennies. It's something much more fun! I designed a custom Halloween icon set, which is free to download and use however you want. With Drupalize.Me's scary good Drupal training, it's fitting that these icons can spook, sweeten, or surprise your next project./p /div/div/divdiv id=comment-wrapper-nid-1895/div

Clemens Tolboom: Which route belongs to which path fragment?

Tue, 10/28/2014 - 13:21
div class=field field-name-field-images field-type-image field-label-hiddendiv class=field-itemsdiv class=field-item evena href=/content/which-route-belongs-which-path-fragmentimg src= width=220 height=156 alt= title=Drupal radial menu tree //a/div/div/divdiv class=field field-name-upload field-type-file field-label-hiddendiv class=field-itemsdiv class=field-item eventable class=table table-striped sticky-enabled theadtrthAttachment/ththSize/th /tr/thead tbody tr class=oddtdspan class=fileimg class=file-icon alt= title=image/svg+xml src=/modules/file/icons/image-x-generic.png / a href= type=image/svg+xml; length=666068 title=drupal-8-menu-tree.svgDrupal menu tree with GraphViz/a/span/tdtd650.46 KB/td /tr tr class=eventdspan class=fileimg class=file-icon alt= title=text/html src=/modules/file/icons/text-html.png / a href= type=text/html; length=221608 title=drupal-menu-tree-d3.htmlDrupal menu tree with d3js/a/span/tdtd216.41 KB/td /tr tr class=oddtdspan class=fileimg class=file-icon alt= title=image/png src=/modules/file/icons/image-x-generic.png / a href= type=image/png; length=56493 title=Drupal-menu-tree.pngDrupal menu tree PNG/a/span/tdtd55.17 KB/td /tr tr class=eventdspan class=fileimg class=file-icon alt= title=text/html src=/modules/file/icons/text-html.png / a href= type=text/html; length=222611 title=drupal-menu-tree-radial-d3.htmlDrupal menu radial tree with d3js/a/span/tdtd217.39 KB/td /tr tr class=oddtdspan class=fileimg class=file-icon alt= title=image/png src=/modules/file/icons/image-x-generic.png / a href= type=image/png; length=226646Drupal-menu-tree-radial.png/a/span/tdtd221.33 KB/td /tr tr class=eventdspan class=fileimg class=file-icon alt= title=image/png src=/modules/file/icons/image-x-generic.png / a href= type=image/png; length=77669 title=Drupal-menu-tree-graphviz.pngDrupal menu tree graphviz/a/span/tdtd75.85 KB/td /tr /tbody /table /div/div/divdiv class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpVisualization some complex part of Drupal is helping understand Drupal better. This is about the menu tree using Graph Viz for a static SVG diagram and D3JS for a dynamic version./p /div/div/div

KnackForge: Ajax Autocomplete Customization for Textfield in Drupal

Tue, 10/28/2014 - 12:23
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encodedpAutocomplete is a feature for textfields in Drupal. It provides a dropdown list of matching options from the server. It is implemented through AJAX. To know how to add an autocomplete form element in Drupal visit a href= pimg alt= src= //pp /p pFor customizing autocomplete we need to override the Drupal system file misc/autocomplete.js. This can be achieved ideally in two ways:/p ulli pReplace the entire autocomplete.js with your customised version/p pre class=lang-cs prettyprint prettyprintedcodefunction MY_MODULE_js_alter(amp;$javascript) { $javascript['misc/autocomplete.js']['data'] = drupal_get_path('module', 'MY_MODULE') . '/js/autocomplete.js'; }/code/pre/li li pOverride with a custom behaviour in theme script.js or module js file, as long as it's added after /misc/autocomplete.js it will override it./p/li/ul/div/div/div

Visitors Voice: “Can our site search be like Google?”

Tue, 10/28/2014 - 07:58
When we discuss site search with clients they often say they want it to work like Google. The problem with this is not that they don#8217;t understand that Google plays in another league when it comes to resources #8211; of course they do. The main problem is that the clients often doesn#8217;t understand the main [#8230;]

Chapter Three: Drupal 8 Administration is Faster, Cheaper and Easier

Mon, 10/27/2014 - 20:53
p dir=ltrspan style=font-size: 13px; line-height: 20.0063037872314px;Drupal 8 is the most fully featured Drupal version ever. Site builders will notice this most immediately when looking at what is available out of the box. Drupal 8 is faster because features that are expected of a modern CMS, like a WYSIWYG editor, are in Core. /spanIt's cheaper because you don't have to pay for custom development to change administration listings since they are Viewsspan style=font-size: 13px; line-height: 20.0063037872314px; And it's better because there are less why does this not work moments including the ability to place the same block in multiple regions. Below are four videos that demonstrate these new Drupal 8 features and a few more./span/pbr / br / p dir=ltrspan style=font-size: 1.385em; font-weight: bold; line-height: 1.538em;Create Custom Administration Experiences/span/p

KnackForge: To check Caps lock is on/off status in jQuery

Mon, 10/27/2014 - 19:49
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encodeddivI'm sure that this script will help you in some of your projects that needs a username and password./div divSometimes when we want access to a secure page that asks for a username and password and we submit the information but we didn't know that the password was submitted in upper case, we get an error./div div /div divSolution: /div div pre class=brush: bash; auto-links: true; collapse: false; first-line: 1; html-script: false; smart-tabs: true; tab-size: 4; toolbar: true; codetagjQuery('#username').keypress(function(e) { var s = String.fromCharCode( e.which ); if ( s.toUpperCase() === s amp;amp; s.toLowerCase() !== s amp;amp; !e.shiftKey ) { jQuery('#capslockdiv').show(); } else { jQuery('#capslockdiv').hide(); } }); jQuery('#password').keypress(function(e) { var s = String.fromCharCode( e.which ); if ( s.toUpperCase() === s amp;amp; s.toLowerCase() !== s amp;amp; !e.shiftKey ) { jQuery('#capslockdiv').show(); } else { jQuery('#capslockdiv').hide(); } }); /pre/div pSample HTML code/p/div/div/div