Newsfeeds

Best Practices for PAX - Defining Goals - by Jake Parmley

Gamasutra.com Blogs - 11 April 2016 - 11:03pm
Red Fox Insights, with the help of 18 game studios and publishers from around the world, has devised a set of Best Practices for PAX, including defining meaningful goals.
Categories: Game Theory & Design

Generations of Horror Game Design - by Josh Bycer

Gamasutra.com Blogs - 11 April 2016 - 11:03pm
The horror genre has changed over the years, and today's post looks at where it's at now and what we can learn from the first generation.
Categories: Game Theory & Design

Graveyard of Thieves Post Dev Blog I - by Vivek Ramkumar

Gamasutra.com Blogs - 11 April 2016 - 10:47pm
A brief introduction about me and my game Graveyard of Thieves.
Categories: Game Theory & Design

Panzoom Images

New Drupal Modules - 11 April 2016 - 9:04pm

Panzoom Images provides a new image field formatter to render the image using
the Panzoom jQuery library (http://timmywil.github.io/jquery.panzoom/).

Categories: Drupal

Jim Birch: Drupal Podcast Guide

Planet Drupal - 11 April 2016 - 7:52pm

Updated: April 11th, 2016.  While I read a lot, as much as I can about Drupal and Web Development, I feel like I learn even more when I listen. So, while driving to work, or while working out on the treadmill, I listen as much as I can to the great folks below that dedicate their time every week to discussing, training, interviewing, and spreading their knowledge.

Here is a big list of Podcasts about Drupal that you can subscribe and listen to at your convenience.

Acquia Podcasts

Acquia's Open Source Evangelist, Jeffrey "jam" McGuire, gives quick interviews of Drupal community members from conferences and events all around the world.  But looking deeper into Acquia's site, you may also stumble upon jam's Drupal Camp in which Mr. McGuire curates great sessions and presentations from previous camps and cons; Power of PHP which is a PHP focused, more technical collection of talks; and a podcast about Drupal 8.

Commercial Progression's Hooked on Drupal

From Michigan, this podcast features discussion from Commercial Progression's Drupal developers about community events, and development techniques.

Read more

Categories: Drupal

Drupal.org blog: A new design system for Drupal.org

Planet Drupal - 11 April 2016 - 6:17pm

As mentioned in our previous post, one of the initiatives we are working on this year is building a new visual system for Drupal.org.

It has been 7 years since Mark Boulton worked on a design plan for Drupal.org. Since then the web has come a long way. So has Drupal. Drupal.org needs a modern design, and the Product team at the Drupal Association has been working steadfastly on a plan to make that happen.

Building on insights from our user research and content strategy work, we have begun laying out a foundation for the future design system for the site.

Goal

Update Drupal.org to reflect the flexibility, modernity, and community of Drupal itself.

Design Principles

Before we started work on the design for Drupal.org we needed to iron out our process and the principles we wanted to keep in mind throughout our work.

To that end, tvn and I holed up for a weekend design retreat, which resulted in tons of post-it notes about what Drupal.org design looks like, what it should look like, and what we can learn from others -- to develop the design principles that will move Drupal.org forward.

Working on design principles for http://t.co/H0d2MHDCaS with @DyanneNova pic.twitter.com/XVZ0bgPlTe

— tvn (@tvnweb) July 25, 2015

After much deliberation, condensing, rewriting, and discussion with the wider Engineering and Communication teams, these are the principles we found to be our best guiding mantras:

Start with user needs.
We only design for real people. We verify their needs and let that information be our guide when designing anything.

Keep it simple. Focus.
We do less, but better. We focus on the areas we can have the most impact. Our designs are simple and clean, and our messages are clear. We strive for brevity and avoid clutter.

Be consistent. Re-use.
Our designs should be part of a consistent, cohesive system. We don’t introduce new patterns if we can re-use or improve any of the existing ones.

Be accessible.
Our designs should be usable by anyone, on any device or screen size, on a high speed connection or a slow network, by people with different native languages, and regardless of their accessibility needs.

Be relevant. Try new things.
Our designs are relevant and fresh. We keep up with the latest trends and are not afraid to try something new.

Iterate quickly.
We do small and quick iterations, continuously improving the experience. We experiment and test out different approaches.

Use Data.
We use data to support and drive our decisions. This includes analytics, data from testing and experiments, data gleaned through user research methods including interviews, surveys, and so on.

Work openly. Be honest.
Our designs are honest and authentic, and our intentions are transparent. We call things what they are. We respect our community values. We communicate openly and often.

Engage and empower.
We design experiences that unite our users and empower them to collaborate and do great things, because they can.

Be friendly.
We create friendly and welcoming environments. We want our users to feel welcome and supported.

Design Vision

Once we had our design principles in place we needed to move from those abstract guidelines to actual design plans for the website.

After DrupalCon Barcelona, we set aside time for another design retreat. This time tvn lost her voice on day 2, so miming and typing became a fun part of the workflow.

Our first step was to create a mood board of inspirational user interfaces to give us a beginning design language and a starting point for discussion.

Then we began our work with style tiles. I created four first drafts, informed by our mood board. One was softer, with varying shades of blue. At the other extreme was a largely monochrome design, with only tiny hints of the Drupal blue. After a few rounds of reviews and revisions we came up with the following visual system, which we feel matches our goals and gives a general idea of the mood, colors, and visuals we plan to move towards.

The general mood here was inspired by the idea of builders and makers working together to build something larger. We combine blueprint textures, single-width line icons, and an open typeface to make Drupal.org feel like the home to a continually improving framework.

We’ve kept the Drupal blue, and tweaked our green to bring it to a cooler shade. We’ve added darker tones for every color to give us more opportunity for high contrast.

The end goal is to make Drupal.org a useful space for contributors and users alike with a consistent quality of design throughout the site.

To that end, we’ve started work on a pattern library which will categorize all of the different design patterns used on Drupal.org. As we build out new patterns for new features they will be added to the library as well. The styles will be automatically inherited from the theme, which will make maintenance of the library as simple as adding relevant content to a page.

Iterative Approach

To support our current prioritization we knew we would need to use a very iterative process for launching design updates. Our strategy is to make design updates as we can when a new feature is prioritized. As each area of the site is functionally improved, it receives visual improvements as well. You’ve seen some of these updates already in the Drupal 8 launch and in the smaller updates to Drupal.org since last November.



With the Drupal 8 launch came a re-styled header for Drupal.org.

Release pages also received a small update to the download area, with clearer calls to action.

Shortly after that, we held a membership drive with a banner and a front page region highlighting community members. And just a few weeks ago we set up a new banner for promoting community elections to the Board, which can also be used for any important announcements going forward.

Next Steps

Our next big project is Documentation. We’ve been toiling away on these features for months now as part of our overall content restructure work. After the first pass of wireframes and design mockups, we collected input from documentation users via usability testing held remotely and in person at the Drupal Association office in Portland, Oregon, and at DrupalCamp London. Based on all the feedback, we've done a few revisions on our initial ideas and designs. We've spoken with a wide range of community members, from newcomers to masters, and their input was invaluable for arriving at a design that really works for the user.

You can see some of the new patterns we’ve begun work on in this mockup, such as the documentation section header and tags. We also have a pattern for related content which isn’t visible in the image. In our usability testing, we found that wayfinders were incredibly important to the experience of documentation, so we spent considerable time on improving the breadcrumbs and menu navigational patterns before arriving at what you see above.

How to get involved

There are a number of ways to get involved in improving Drupal.org. You can read more about general volunteering here.

If you’re interested in joining our usability testing sessions held both remotely and in person at major Drupal events, please fill out this form and we’ll reach out to you when the next session is being planned.

To post an issue about design on Drupal.org, use the project issue queue at Drupal.org Design. This issue queue will replace the Bluecheese theme queue going forward as a central place to report issues or inconsistencies with Drupal.org design. Meta discussions of design on Drupal.org are also welcome in the queue.

If you’d like to participate in quick design discussions about Drupal.org and be available to give feedback on upcoming design decisions, join us on Slack at channel #drupalorg-design.

As we incrementally roll out new features, you’ll see Drupal.org move ever closer to our updated visual system. Thanks for coming along for the ride!

Categories: Drupal

Layout Builder

New Drupal Modules - 11 April 2016 - 2:02pm
Categories: Drupal

DrupalCon News: Training Spotlight: Frontend and User Experience

Planet Drupal - 11 April 2016 - 2:01pm

Frontenders rejoice! We have made extra room in our training line-up to include lots of frontend and UX topics. Begin your week at DrupalCon with a training course and get a head start on hot topics such as accessibility, site performance, design strategy and more.

Categories: Drupal

Kayak

New Drupal Modules - 11 April 2016 - 1:58pm

Drupal 8 provides a complex framework of classes and interfaces that can easily overwhelm new developers. While tutorials cover some of these for certain scenarios, a lot of the low-level tools provided by Drupal Core can remain hidden because no straight-forward examples of their use exist.

Kayak will provide a web frontend to quickly navigate through the Drupal code base and gain a bird's-eye perspective. It will visualize hierarchies and dependencies and explain when and where to use each class or interface.

Categories: Drupal

Doug Vann: Drupal Promotes An Ownership Society, but does Drupal 8 threaten that?

Planet Drupal - 11 April 2016 - 12:30pm

Those who know me at all likely know that I have a few catch-phrases I use when trying to explain the impact that Drupal has had on the market for organizations and individuals needing quality web sites.

DRUPAL PROMOTES AN OWNERSHIP SOCIETY

is a phrase that I have used for years and years. When I say that I seek to convey the fact that many organizations and individuals are choosing to rely less on outside vendors and more on internal talent to get things done. I have come to this conclusion simply by observation. As I became more and more in demand I found that many organizations wanted me to come in and empower THEIR STAFF to do the work that needed done. In some cases they already had a site that a vendor built but they wanted to improve it. Others had no site and wanted to build the thing form scratch and learn how to use Drupal along the way. Either way, these clients were going ALL IN for Drupal and decided that Drupal was a tool to have IN THEIR OWN tool belt to use whenever they need it.

Who are these organizations choosing to OWN the Drupal process and rely less on vendors? They are Universities, Governments [Fed, State, Local, etc,] Tech companies, Media companies,  Marketing companies, Agencies, etc. They see others, sometimes competitors, leveraging Drupal and they want the same power, but without the price tag. They know that Drupal is Open Source, meaning free, so they check it out and get so far until they decide they need a push. The come to the point where they need a formal engagement by a knowledgable trainer who can walk with them through a tailored learning experience that addresses the kinds of projects that they will be building. They don't want package {A} or {B} or {C} to choose from. They want to own a personal Drupal training experience to equip them to build their personal web experience.

And that is exactly what I give them!

So.... How's that going for you? 

I've kept in touch with these clients & I see many of them attending and participating in Drupal events. I watch them launch site after site. Some of them wind up hiring in some Drupal talent to augment the staff. When that Drupal talent arrives, the other staff are already well oriented to the ways of the Drupal! [Hmm. perhaps a new catch phrase!?] 

Let’s not forget too that many of these organizations have cancelled their expensive licenses for proprietary CMSs and are now enjoying a more agile and productive process of increasing their web-appeal.

AND ALONG CAME DRUPAL 8

I've criss-crossed the country teaching Site Building, Theming, Module Development. People have been amazed at what you can do with Drupal core, some Contribute modules and NO CODE! But the fact is that you are highly likely to need code eventually. If you truly want to create the website EXACTLY to specs, then a little hook here and a little hook there and a theme-variable or 3 or 4 will get you considerably closer to those specs. One custom module with 1 to 4 hooks along with a dozen lines in your template.php and a few extra print commands in a few TPL files will make significant changes to your site. I have taught people how to do this for years and they LOVE THE POWER.

Now I look out at the landscape of Drupal 8 and I am trying to imagine going back to those same clients and telling them to forget it ALL and learn OOP, Symfony2, PSR, and Twig. Is it possible? sure it is! Can I do it all in one week? Not at all likely. Drupal 8 is a game-changer primarily because it threw out most of the rules and started over. So what is an accomplished Drupal trainer and consultant to do? Well. I have discussed this with some of my clients. Some are choosing to ignore Drupal 8 until more contrib modules come of-age. Some are thinking they will ride out their volume of D7 sites until D9 is a topic and the idea of D7 end-of-life is a concern. NONE are overly anxious to start over and jump into a world where most of what they learned before no longer applies.

And yes.... I do tell them that BACKDROP CMS is a viable solution to get tomorrow's features built on a platform that they already know and enjoy and are skilled at.

So you tell me. Have you observed organizations and individuals taking an ownership position of Drupal and relying less on vendors? Do you agree that that approach is more difficult for “many” organizations due to the degree of code rewrite that D8 experienced?

I gotta be honest... When someone asks me D7 or D8? I ask them, do you or your organization plan on OWNING the site or do you want to rely on vendors? Along with that I will ask, do you have some young Comp-Sci cats in your org who can be delighted by the near-MVC-like rewrite of Drupal?

Insert the usual caveat here...
I believe in D8 and its power to bring Drupal to whole new levels of appeal to bigger markets. I also believe that smaller markets have already been and will continue to be "put-off" by the volume of changes that do not necessarily add value to the ways in which these smaller markets utilize this powerful tool.

Alrighty... SHIELDS UP! Sock it to me, PLEASE, in the comments below! :-) 

Drupal Planet

View the discussion thread.

Categories: Drupal

Blizzard shutters popular private WoW server with threat of legal action

Social/Online Games - Gamasutra - 11 April 2016 - 11:44am

Over the weekend one of the largest private "vanilla" World of Warcraft servers, Nostalrius, was shut down after Blizzard threatened to take its operators to court over copyright infringement. ...

Categories: Game Theory & Design

Red Crackle: Configuring Drupal With Elasticsearch For Facet Search Functionality

Planet Drupal - 11 April 2016 - 11:00am
This article integrates Drupal with Elasticsearch to introduce Facet search functionality. You will be taken through the step-by-step procedure through a series of screenshots. By the end of this article, you will be able to select and display items on a page based on specific search criteria.
Categories: Drupal

Pantheon Blog: Modern Command Line Tools for Drupal Modules with Drush and Drupal Console

Planet Drupal - 11 April 2016 - 9:55am
Having a command line interface to the functionality provided by Drupal modules has been a highly valuable and widely-used feature that has been used for many years. Today, there are over 500 Drupal modules that provide Drush commands, and the number keeps growing.  On top of this, some modules have started to use Drupal Console to implement their command line tools. Drupal Console provides an object-oriented interface and a host of utility functions provided by the Symfony Console libraries.
Categories: Drupal

Drupal Association News: Honoring DrupalCon Volunteers

Planet Drupal - 11 April 2016 - 9:22am

Hello, Drupal world! We are thrilled to be able to give you an inside peek at what goes into planning DrupalCons. Throughout 2016, we’ll share a series of posts, and a few webcasts, to show some behind-the-scenes aspects of DrupalCon. In honor of National Volunteer Week, this month's DrupalCon post highlights how an army of amazing, dedicated volunteers is behind every DrupalCon.

If you’ve ever attended a DrupalCon, you probably remember the Drupal Association standing onstage and saying that this event ‘couldn’t happen without our amazing volunteers.’ We normally have a round of applause for the volunteers at each particular Con, but that still doesn't fully convey how much of the Con is lead by some fantastic community members. In this blog we want to help quantify how much time and energy these volunteers give to help create a memorable and enriching Con for you.

Before you even know there is a Con happening in any city, volunteers are already on board helping to make it happen. Once the city has been decided and finalized by the Drupal Association, we loop in a small group of community leaders in the secret city to come together and help us make a splash when we announce the next year’s Con location.

Besfore the Con has even been announced, these 4-6 volunteers work to put together a document that guides our designer in the logo creation and branding of the still-secret event. The community gives input during the design process of the logo, sticker and splash page that goes live after the announcement. The announcement is another way that the volunteers make an impact by dreaming up an awesome way to tell you about how awesome their city is and why you should come to DrupalCon the next year.

Once we have publically announced a location, the Drupal Association reaches out to more volunteers to build the Program Team. This team includes various groups of volunteers who make a huge impact on your DrupalCon experience. Here is a quick rundown of how committed these volunteers are and how their contribution shapes the Con.

  • Track Team - with two to three volunteers per track, this is the team that sets the tone of what content you will be hearing in sessions. They begin thinking about this at least 5 months before the Con and meet weekly to move the session content forward. Between writing track descriptions, reaching out to speakers to curate sessions, reading every single session submission, helping build the schedule and later acting as coaches for their speakers, this team signs up for a long and heavy time commitment and the fruits of their labor results in amazing sessions. In New Orleans we have 130 hand-selected sessions thanks to this dedicated team. Additional Selection Committees - we also call on the help and expertise of various other community volunteers in selecting more things related to DrupalCon. For the incredible training course proposals that we get, we have a team dedicated to selecting the 15 that should be offered. We also have a team tasked with the duty of reading each grant and scholarship application and making the difficult decisions about who is given an award to come to the DrupalCon.
  • Summit Leads - each Summit is led by a small team who works to develop a full day of engaging and educational content that will allow attendees to get the most out of the Con by adding this Monday ticket event to their trip. Our Summit Leads begin working 4 months before the Con to line-up panel guest speakers, organize multiple round table topic leaders, create the flow of the day as well as emcee their event. If you’ve ever attended a Summit, we hope that you appreciate the time and energy that these Leads have committed to making your day great.
  • Sprint Leads - this team of leads works year-round to help create sprints that are welcoming and engaging and DrupalCons are no different. Beginning planning a few months in advance of the Con, this team takes on 9 days of sprint coordination (all those extended sprints on the weekends before and after the Con, Monday Contribution Sprints, Sprint Lounge during the week and Friday Sprint Day). They also have a booth in the Exhibit Hall where you can learn about sprinting, contributing and how you can get involved. They also work to lead an amazing group of additional volunteer Sprint Mentors who help make these sprints a learning experience for many newer contributors.
  • Sprint Mentors - this group of sometimes up to 75 is mainly recognizable in their bright colored Con shirts on Fridays - helping to make sure new contributors are set-up to learn how to give back to Drupal. These mentors come from around the world and attend a training on being mentors to hundreds of DrupalCon attendees and truly dedicate their time and energy to the community with this role.
  • Community Leaders - after helping plan the big reveal of their city, the community leaders stay throughout the months before the Con to make sure that the Con gets an injection of the host city into the fun-filled week. If you’ve ever found a blog about local restaurants or learned about a popular app in a new country, the local community leads are more than likely to thank as the work to provide helpful content that makes your time in their city the best ever.
  • Prenote Performers - now an institution at DrupalCon, the Prenote has become a staple of Con content. The known suspects as well as local participants put in countless hours of time to craft a script, original songs and multiple antics that share the story of Drupal while making us laugh -- kicking the Con off right.

Apart from the Program Team, there are still many more volunteers who give time and knowledge to making DrupalCon special. Below are some of the many ways that volunteers are involved with shaping the Con:

  • Speakers - although the speakers get a free ticket to the Con, we consider them volunteers because in choosing to speak at DrupalCon they are providing us with an incredible session that takes a lot of time and energy to create. Many hours go into a single presentation before you hear it at the Con, and with over 150 speakers at DrupalCon New Orleans, we are thankful to have so many talented volunteers sharing their experience with our Drupalistas.
  • On-site Volunteers - the days before the Con involve over 50 volunteers who help us prepare for the barrage of Drupalers who arrive to enjoy a week of all things Drupal. From organizing over 3,000 t-shirts to stuffing that tote bag you get with multiple sponsor goodies, this power-team of volunteers are like a machine and deserve a huge round of applause for hard work. Once those tasks are complete, we have many volunteers who also help at the registration desk, counting session room attendance, and checking in with sponsors. There is literally of sea of volunteers at all times making sure DrupalCon is going smoothly.
  • Recurring Con Volunteers - some volunteers take on an element of the Con and just own it. Group photos and photography shots come from an amazing photography team composed of new volunteer photographers and some that have been taking photos at Drupal events for years. Our social media team is on point year-round to make sure that you’re always getting the most up-to-date info about the next Con. These volunteers have become almost permanent extensions of our Drupal Association team. We're grateful to work with our recurring volunteers because not only do they rock at what they do, but gosh, they're fun!
  • The Community Working Group - with the Code of Conduct in effect at every Con, this group might go unnoticed but plays a huge role in making DrupalCon welcoming and inclusive for all attendees. Available to mediate and work through incidents, this group is an important part of making a Con a Con.

As you can see, when we say this couldn’t happen without the volunteers, we MEAN IT.

I consider myself very lucky to primarily work with volunteers around the world who are so passionate and invested in creating a DrupalCon for you. I spend a lot of time on Zoom calls and in Slack channels with many of these volunteers. During working hours, on weekends, and at the event itself, these volunteers put a lot of themselves into these Cons and I sometimes step back and appreciate how incredible the Drupal community is.

I do my best to thank these volunteers often, reminding myself that each and everyone of them has a life and other priorities and that they are choosing to make DrupalCon important, but as it is National Volunteer Week, I would like to take a moment to list the DrupalCon New Orleans volunteers below and specifically say THANK YOU for all of your hard work - it is valued and appreciated not only by the team at the Drupal Association but by the community as well.

Program Volunteers

Pamela Barone, Donna Benjamin, Pedro Cambra, Michael Cannon, Ian Carrico, Karyn Cassio, Stuart Clark, Matt Davis, Jess Dearie, Shawn DeArmond, Jeff Diecks, Mauricio Dinarte, Robert Douglass, Larry Garfield, Rob Gill, Becca Goodman, Paul Grotevant, Adam Hill, Lucas Hedding, David Hwang, Paul Johnson, Sherri Johnson, Adam Juran, Alex Laughnan, Dan Linn, Greg Lund-Chaix, Alina Mackenzie, Kathryn McClintock, Jeffrey McGuire, Ashok Modi, Diana Montalion, Mike Nielson, Steve Parks, Jon Peck, Joel Pittet, Koen Platteeuw, Tim Plunkett, Ryan Price, Justin Rhodes, Jason Savino, Michael Schmid, Sabrina Schmidt, Eric Schmidt, Eric Sembrat, Seth Silesky, Lauren Smith, Nikki Stevens, Joe Stewart, Ashleigh Thevenet, Cathy Theys, Campbell Vertesi, Shannon Vettes, Jason Want, Heather White, Jason Yee

Sprint Mentors

Alina Mackenzie (alimac), Adam Smeets (asmeets), Ravindra Singh (RavindraSingh), Cathy Theys (YesCT), Gobinath Mallaiyan (gobinathm), David Valdez (gnuget), Aman Kanoria (amankanoria), Joël Pittet (joelpittet), John Cook (John Cook), Chris McCafferty (cilefen), David Hernandez (davidhernandez), manmohan bisht (manmohandream), Mike Keran (mikeker), Ashwini Kumar (ashwinikumar), Eleanor Wai (eleanor_wai), Mauricio Dinarte (dinarcon), Prabhu Narayanpethkar (prabhurajn654), Maninder Singh (Maninders), Maninder Singh (Maninders), Lucas Hedding (heddn), Hitesh Jain (hitesh-jain), Steve Purkiss (stevepurkiss), Anto Jose (antojose), Piyuesh Kumar (piyuesh23), Saket Kumar (saki007ster), Manauwar Alam (manauwarsheikh), Les Lim (Les Lim), Ajit Shinde (AjitS), Marc Drummond (mdrummond), Nikki Stevens (drnikki), Neetu Morwani (neetu morwani), Prashant Goel (prashantgoel), Tim Erickson (stpaultim), Daniel Carvalhinho (dscl), Lalit Nirban (lalit3007), Joaz Rivera (m3chas), Junaid Masoodi (junaidmasoodi), Christian Manalansan (cmanalansan), Blake Hall (blakehall), Abhishek Anand (abhishek-anand), Amber Matz (Amber Himes Matz), Darryl Norris (darol100) David Needham (davidneedham), Kristin Bradham (kristink2), Diana VanRooy (thenyouDi), Marc Isaacson (vegantriathlete), Carlos Ospina (camoa), Patrick Storey (Patrick Storey), William Hetherington (willwh), Ravish Gupta (ravyg), Valery Lourie (valthebald) Seth Silesky (sethsilesky), Stuart Clark (Deciphered), Barbara Errickson (barbarae), Cristina Chumillas (ckrina)

Speakers

Hussain Abbas, Mary Albert, John Albin Wilkins, Kelly Albrecht, Greg Anderson, Geoff Appleby, Ronald Ashri, Ryan Aslett, Morten Birch, Kristina Bjoran, Abe Brewster, Jesse Browne, Amitai Burstein, Angie Byron, Ian Carrico, Leigh Carver, Karyn Cassio, Marji Cermak, Matt Cheney, Gus Childs, Chaz Chumley, Courtney Clark, Casey Cobb, Ashish Dalvi, Matt Davis, Aimee Degnan, George Demet, Alex Dergachev, Suzanne Dergacheva, Nikhil Deshpande, Frederic Dewinne, Jeff Diecks, Daniel Dreier, Marc Drummond, Jeff Eaton, Stephanie El-Hajj, Adam Englander, Brad Erickson, Lauri Eskola, Edward Faulkner, Mark Ferree, John Ferris, Jessi Fischer, Fabian Franz, Pieter Frenssen, Larry Garfield, Yuriy Gerasimov, Aditya Ghan, Mike Gifford, Matt Glaman, Micah Godbolt, Drew Gorton, Nicolas Grekas, Rudy Grigar, Jody Hamilton, Mike Herchel, David Hernandez, Michael Hess, Jason Hibbets, Amber Himes Matz, Mikkel Høgh, Gábor Hojtsy, Chris Hoult, David Hwang, Marcus Iannozzi, Allie Jones, Adam Juran, Adam Kapp, John Kary, John Kennedy, Greg Knaddison, Randall Knutson, Josh Koenig, Charles Kreitzberg, Michelle Krejci, Kat Kuhl, Ashwini Kumar, Saket Kumar, Piyuesh Kumar, Wim Leers, Brian Lewis, Les Lim, Dan Linn, Clay Marshall, Tom Martin, Sophie Matson, Jeffrey McGuire, Catharine McNally, Oscar Merida, Steven Merrill, Brett Meyer, Michael Miles, Josh Miller, Tim Millwood, Igor Minar, Gaurav Mishra, Jesus Molivas, John Money, Jess Mybro, David Needham, Narayan Newton, Dani Nordin, Darryl Norris, Ron Northcutt, Dick Olsson, John Ouellet, Jason Pamentalm, Jon Peck, Steve Persch, Piyush Poddar, Kristen Pol, Fabien Potencier, Alex Pott, Taco Potze, Ellie Power, Luke Probasco, Ilan Rabinovitch, Scott Reeves, Dave Reid, Adrian Rollett, Chris Rooney, Chris Russo, Susan Rust, Terrence Ryan, Peter Sawczynec, Dave Sawyer, Michael Schmid, Roy Scholton, Michael Sherron, Joe Shindelar, Sebastian Siemssen, Michael Silverman, Preston So, David Spira, Anne Stefanyk, Nikki Stevens, Karen Stevenson, Nick Stielau, Matt Stratton, David Strauss, Ryan Szrama, Patrick Teglia, Chris Teitzel, Dave Terry, Kyle Theobald, Ashleigh Thevenet, Bjorn Thomson, Travis Tidwell, Matthew Tift, Howard Tizzo, Vanessa Turke, Tatiana Ugrimova, Chris Urban, Kristof Van Tomme, Jeff Walpole, Ryan Weaver, Daniel Wehner, Moshe Weitzman, Lynn Winter, Peter Wolanin, Chris Wright, Bojan Živanović, Helena Zubkow

Image credit goes to the following photographers:
DrupalCon Asia Volunteer Selfie : Michael Cannon
Education Summit Meeting : Paul Johnson
Zoom Screenshot Photo : David Hwang
DrupalCon Los Angeles Sprint Mentors: Jared Smith

Categories: Drupal

Drupal @ Penn State: Lower the Drupal 8 development barrier to entry by using the Drupal Console to generate boiler plate code.

Planet Drupal - 11 April 2016 - 9:06am

I admit that I haven't really looked at Drupal 8 too much yet. There is a variety of reasons why I haven't and I surely don't want this to turn into a forum listing the pros and cons of D8. We can leave that for another post. 

Categories: Drupal

Comments Entity

New Drupal Modules - 11 April 2016 - 7:05am

Drupal core comment module is great for commenting on nodes.

This module provides fieldable comments for any entity even comments itself. Entity Comments integrates with views and rules.

Installation

Simply enable the module and go to "admin/structure/comments_entity" and enable Entity Comments on any entity.

Categories: Drupal

The Sego Blog: Drupal 8 Module Development Resources

Planet Drupal - 11 April 2016 - 6:54am
04/11/2016Drupal 8 Module Development Resources

This past weekend we were honored to co-host the Drupal Global Training day at DoSomething.org in NYC. This training was focused on Drupal 8 module development. We have been training on the ins and out of Drupal 8 module development for over a year now but this time we changed the format, considerably. I think for the better! 

Using the Role Notices module, developed by Ted Bowman, we put together an exercise that walks you through building the functionality it exposes step by step. We also built a list of resources chock full of links pertaining to various tools and docs for getting your chops up with D8 development. 

All this work is open source and available at this link. I am really hoping that this content can serve as a valuable resource for folks looking to learn the proper flow of developing a Drupal 8 module.

There are so many exciting concepts and programming patterns to explore in D8, we hope you continue to join us during this jounrney. 

Mega thanks to everyone that helped make this happen! 

Categories: Drupal

Acquia Developer Center Blog: The Faichi Story: From Unknown Drupal Shop to Top 10 in 6 months

Planet Drupal - 11 April 2016 - 6:21am

It all started at DrupalCon Barcelona, when Shailesh Gogate, VP at Faichi Solutions, met Johanna Boel Bergmann, the Account Manager, Drupal Businesses at the Drupal Association.

Johanna had never heard of Faichi; she had never seen it in the Drupal.org Marketplace. This even though our company has been working with big enterprise clients for the past five years, as well as contributing to Drupal.org.

That was an eye­-opener for Shailesh. When he returned to India, he shared his findings with Faichi’s engineers and senior management. They took the feedback very seriously. They decided to create a plan to show their presence: not only in the Drupal Marketplace, but to the whole Drupal community.

Tags: acquia drupal planet
Categories: Drupal

Chapter Three: Javascript testing comes to Drupal 8

Planet Drupal - 11 April 2016 - 4:47am

With the arrival of Drupal 8.1.0 finally you can test javascript interactions on Drupal.org. This is culmination of years of work by many developers to improve the testing API and infrastructure. Without the improvements delivered by Drupal 8 it'd be hard to leverage Mink, PhantomJS and PHPUnit to run our tests, and without the new DrupalCI infrastructure we'd have nowhere to run the tests.



Categories: Drupal

Pages

Subscribe to As If Productions aggregator