Planet Drupal

Subscribe to flux Planet Drupal
Drupal.org - aggregated feeds in category Planet Drupal
Mis à jour : il y a 42 min 34 sec

Drupal core announcements: This month in Drupal Core (June 25, 2014)

jeu, 26/06/2014 - 06:19

Note: We've renamed this post series to Drupal Core Updates since, well, you know, they weren't exactly weekly to begin with. (As always, contact xjm if you'd like to help write them!)

What's new with Drupal 8?

We may have been quiet for the past month as we prepared for -- and then recovered from -- DrupalCon Austin, but core development has been sizzling! (And not just because of the Texas climate.)


Photo credit: pdjohnson

DrupalCon Austin sprints

In addition to all the great sessions (videos below), summits, BOFs, and trainings, Austin included six full days of sprints on everything from Drupal 8 release blockers, frontend, and APIs, to D8 contrib initiatives like #d8rules, the Examples D8 port, and D8 Media, to Drupal.org itself. Nearly 500 sprinters and mentors got involved on the main Friday sprint day, and over 100 sprinters participated in the extended sprints before and after the Con.

If you were at the sprints, you might have noticed a few goofy sprinters decked in rabbit ears. :) These indefatigable contributors were working on some of the very last Drupal 8 beta blockers. During Austin, we managed to resolve six of these issues, but more importantly, we identified the path forward in all the beta blockers we didn't fix as well.

Done > Perfect

The past month also showed a shift in the community's outlook: It's time to get Drupal 8 done. We need to stop making large, non-essential changes, because every time we make more work for ourselves, we delay the release of 8.0.0 for hundreds of thousands of people. When we have a choice between doing something quickly and imperfectly, or slowly and perfectly, it's time to pick the quick, imperfect fix. A couple examples:

  • Last month, we discovered that Drupal 8's new support for PHP INTL dates was badly broken. Instead of spending dozens of hours trying to resolve this issue before releasing a beta, we removed the feature. It did not exist in D7, and it can be added back for 8.1.0, or provided by a contributed module.
  • In Drupal 8, comment fields can now be attached to any entity type, instead of just nodes; however, they don't work on entity types with non-numeric ID keys (contact forms are the only example in Drupal 8 core). Instead of holding up the release on making every fieldable entity type commentable, we settled for almost every entity type being commentable -- which is still a big improvement from D7.

Drupal 8.0.0 will not be perfect, but it will be powerful. And we have the chance to make it even better in 8.1.0 six months later. Think about which issues in the core queue might make sense as minor version targets, and help us work on Drupal 8 efficiently.


Photo credit: Michael Schmid. Help us battle Lord Over-Engineering!

Drupal 8 documentation updates on API.drupal.org

Lots of comprehensive API documentation has been added to the API.Drupal.org handbook page over the past month, thanks especially to API documentation maintainer jhodgdon and review efforts from core component maintainers. This overview page (and the detailed documentation linked from it) should provide a much better starting point for learning about Drupal 8. (See below for how you can help document the remaining API topics.) API.drupal.org has also recently added an automatic list of services provided in Drupal 8 core. For updates on Drupal documentation work, see This Month in Drupal Documentation.

Where's Drupal 8 at in terms of release?

Last week, we fixed 9 critical issues and 10 major issues, and opened 4 criticals and 6 majors. That puts us overall at 92 release-blocking critical issues and 595 major issues.

2 beta-blocking issues were fixed last week. There are still 11 of 172 beta blockers that must be resolved before we can release a Drupal 8 beta.

Where can I help? Top criticals to hit this week

Each week, we check with core maintainers and contributors for the "extra critical" criticals that are blocking other work. These issues are often tough problems with a long history. If you're familiar with the problem space of one of these issues and have the time to dig in, help drive it forward by reviewing, improving, and testing its patch, and by making sure the issue's summary is up to date and any API changes are documented with a draft change record.

  • #2238217: [Change record] Introduce a RouteMatch class

    The one reasonably approachable task in this week's top beta blockers is to complete the needed change record documentation for the recently added RouteMatch class. Help by writing a draft change record for the issue, and then update existing change records to also include an issue reference to #2238217 and to use the new API. (See comment #143 on the issue for a start.) Post links to the revision diffs for your change record updates so they can be reviewed by other contributors.

  • #2256521: New plan, Phase 2: Implement menu links as plugins, including static admin links and views, and custom links with menu_link_content entity, all managed via menu_ui module

    This massive (nearly 600 K) improvement to the Drupal 8 menu link API resolves or unblocks numerous critical issues while also supporting performance, DX, and multilingual improvements. The patch is developed from a sandbox:
    git clone --branch 2256521 http://git.drupal.org/sandbox/dereine/2031809.git
    Help this issue by:

    • Providing code additional reviews, since the patch is way too big for any one contributor to review in one sitting.
    • Proactively identifying things in the patch (or from others' reviews) that could be resolved in followup issues, filing those followup issues, and adding the appropriate code @todo and links to the followup issues.
    • Looking through the patch and issue to identify the complete, specific API changes it introduces, and adding these changes to the issue summary.
    • Checking for existing change records that will need to be updated for these API changes, listing the updates that will be needed in the issue summary, and editing the change records to add a reference to #2256521.
    • Drafting a new change record for the change.

    Check with Wim Leers, pwolanin, or dawehner so that you can align your efforts with their work on this patch.

  • #2144263: Decouple entity field storage from configurable fields

    This issue is key to completing the Drupal 8 Entity Field API and is the culmination of work done across DrupalCons Portland, Prague, and Austin. The patch needs test failures resolved, architectural review, and (as above) identification of any needed change record updates. Coordinate with Berdir, plach, or yched to help further with this issue.

  • #1825952: Turn on twig autoescape by default.

    Enabling Twig's built-in autoescaping of HTML-unsafe code will security-harden Drupal 8, and should eventually allow us to reduce complexity and improve perfomance in the theme layer. The patch introduces a SafeMarkup class that can be used to identify sanitized strings for use in templates, and all other strings are automatically escaped. Help with this patch by providing feedback to points raised in recent reviews (see comment #185), helping write thorough API documentation for the SafeMarkup class, or starting a draft change record. Contact xjm to help out with this issue.


Photo credit: Michael Schmid

More ways to help
  • We're closing in on Beta 1!

    Only 11 beta-blocking issues remain, and we will probably be in the single digits by the end of the week. This means now is a good time to start looking at all the beta targets and especially issues with a beta deadline. (See Beta blocker deadline target what? for an explanation of these issue categories.) Keep an eye out for other issues that should have a beta deadline as well.

  • #2148255: [meta] Make better D8 api.d.o landing page, linked to high-level overview topics, and put it in Core api.php files

    Help improve our Drupal 8 API documentation! The menu and routing topic needs review, and we also need first drafts for the REST, Migration, and Ajax documentation topic updates.

  • #1971384: [META] Convert page callbacks to controllers

    We converted all of core to use our new routing system last fall, but eighteen different form and page controllers still need to be cleaned up to conform to our best practices. Currently, almost all of these patches need to be rerolled for PSR-4 and for other core changes. Note, however, that many of these patches have gone through multiple rerolls (mostly by novice contributors) over the course of more than a year, without sufficient review before the patches become stale. So, what these issues need most is 1-2 experienced contributors with an understanding of Drupal 8 architectural concepts who can manage the meta issue and its children, and provide thorough code review when new patches are submitted. If you can help out, start by reviewing those child issues still at "Needs review".

  • #2016679: [Meta] Expand Entity Type interfaces to provide methods

    Drupal 8 core provides numerous entity types, but the full public API for each type is not easily documented or discoverable. To improve the developer experience, each entity type interface is being expanded with relevant methods for the specific entity. Most issues have a submitted patch, and what is most needed is architectural review of the proposed interface methods, including recommending which properties should instead be protected. If you have experience with one of the subsystems that still has an open child issue, or if you have a sound grasp on OO design generally, we could use your help to thoroughly review these patches so that the completed APIs are available for contributed module developers in a beta release.

As always, if you're new to contributing to core, check out Core contribution mentoring hours. Twice per week, you can log into IRC and helpful Drupal core mentors will get you set up with answers to any of your questions, plus provide some useful issues to work on.

You can also help by sponsoring Drupal core development.

Notable Commits

There have been a remarkable 360 commits since our last post in May! Far too much great work has been done across D8 core to summarize it all, but here are a handful of the more "epic" beta-blocking issues that were recently resolved:

  • Issue #2224887 by alexpott, Berdir, Gábor Hojtsy, Jalandhar: Language configuration overrides should have their own storage.
  • Issue #2247991 by xjm, typhonius, donquixote: [May 27] Move all module code to PSR-4.
  • Issue #2183231 by tstoeckler, plach, jessebeach, fago, Berdir, xjm, mauzeh: Make ContentEntityDatabaseStorage generate static database schemas for content entities.
  • Issue #2143291 by plach, alexpott, xjm, effulgentsia, pwolanin, swentel | yched: Clarify handling of field translatability.
  • Issue #2167167 by Berdir: Remove field_info_*().
  • Issue #2238217 by effulgentsia, neclimdul, martin107, tim.plunkett, cweagans, kim.pepper, xjm: Introduce a RouteMatch class.

You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.

Drupal 8 Around the Interwebs

If you didn't make DrupalCon Austin -- or even if you did -- be sure to check out all the Drupal 8 session recordings. Some highlights:

Seen enough videos now? Looking for something to read instead? webchick's ongoing blog series, the Ultimate Guide to Drupal 8, is a great resource for everything you might want to know about D8 improvements.

Drupal 8 in "Real Life"

It's a sprint-filled summer!

Whew! That's a wrap!

Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. Contact xjm if you'd like to help communicate all the interesting happenings in Drupal 8!

Catégories: Elsewhere

Lullabot: CSS Regression Testing with Resemble.js

mer, 25/06/2014 - 22:00

Roughly a year ago Alex Sexton's Smashing Magazine article highlighted a new role emerging amidst the increasing complexity of front-end work in a responsive world: Front End Ops. Since that article was published, there's been an entire conference devoted to the subject, and folks like Chris Rupl have evangelized similar roles and supporting tools to the Drupal community.

Catégories: Elsewhere

Appnovation Technologies: First Thoughts on and 4 Tips for Drupal Development

mer, 25/06/2014 - 17:47
Coming in to Appnovation as a Co-op student, I hadn’t had much exposure to Drupal before. This meant my training not only involved getting to know how the company works, but also how Drupal works. Below are some of the main things I learned during my training in Drupal at Appnovation. var switchTo5x = false;stLight.options({"publisher":"dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683"});
Catégories: Elsewhere

Acquia: Gábor Hojtsy: A Whole New World for Multilingual Sites in Drupal 8

mer, 25/06/2014 - 14:30
Presenter Dossier: Gábor Hojtsy
Catégories: Elsewhere

Code Karate: Creating Drupal Commerce add to cart links

mer, 25/06/2014 - 14:29

I recently ran across a problem of needing multiple Drupal Commerce add to cart buttons on a sing

Catégories: Elsewhere

Gizra.com: Creating a Custom Breakpoint in Bootstrap-Sass

mar, 24/06/2014 - 23:00

Bootstrap is our go to base theme, but what happens when the grid the client asks for has different width, or more break points? Using Bootstrap-Sass creating a custom grid is possible in a manner that can be copied and adjusted from one project to another. As example for this post, and for your future reference you may follow the live demo and repository that changes Bootstrap to work with five breakpoints (tip: use Resizer for easy viewport resize).
Note that example is using Jekyll for simplicity, however the same technique can be used on Drupal.

Continue reading…

Catégories: Elsewhere

Metal Toad: Toadcast 23!

mar, 24/06/2014 - 22:30


Photo Credit: Tyler Ward

In Toadcast 23 we talk with Tom Martin and Dan about Drupalcon 2014, Texas Food, Heat, Sessions from Four Kitchens, Adam Edgerton, Roaches, Austin City Life, Pet Talk, Presentations by Dan, Drupalcon 2015, The Definition of Decimate, Future of Drupal, & Expansion of Drupal Crowd.

Catégories: Elsewhere

Mediacurrent: Migrating The World's Largest Website onto Drupal - Weather.com

mar, 24/06/2014 - 19:39

At Drupalcon, we had the opportunity to share with the community a case study featuring The Weather Channel (TWC), which has one of the most highly visited web sites in the world (www.weather.com). And, it’s certainly among the largest Drupal sites under development.

The approach was to break the engagement into two phases, the first to address editorial concerns and the second to replace legacy systems and take over the front end serving.

Catégories: Elsewhere

Aten Design Group: Getting Started with References in Drupal

mar, 24/06/2014 - 19:25

Slated to be part of Drupal 8 core, Entity Reference is a field type module you should be familiar with now. For experienced Drupal users, the reference field is probably not a new concept. Regardless of your Drupal skill level, I hope to give a practical example of how the Entity Reference module can be utilized and introduce a few other modules that greatly improve its usability.

The Entity Reference module provides a new field type that allows entities (nodes, taxonomy terms, etc.) to create a reference (or connection) to each other. The need for references usually comes from needing to create content with complex data points (or fields). My example is for Aten Records (our company's fake record label). Aten Records needs to catalog all of their artists, albums and tracks. Imagine trying to store every album and track for an artist in a single content type (artist for example). It would be challenging because of the data we need to collect for each album and track. It becomes much easier to imagine three content types (artist, album & track), but we need a way to connect the three content types together. Entity References can help!

In this example I am using Drupal 7 core and the Entity Reference module.

Creating the example

You can also follow along with the screencast if you like.

Create content types
  • Artist
    • Name (title field)
    • Biography (body field)
    • Photo (image field)
    • Albums (Entity Reference referencing the album content type)
  • Album
    • Title (title field)
    • Album Artwork (image field)
    • Year (text field)
    • Tracks (Entity Reference referencing the track content type)
  • Track
    • Title (title field)
    • MP3 (file)
    • Length (text)
    • Writer (text)
Review entity reference field settings
  • Make sure it is pointing to the correct entity type (node in our example)
  • Make sure it can reference the correct content types
  • Make sure it can reference a unlimited number of options
Creating Content

We can now create artists, albums and tracks but the workflow isn't ideal.

Default workflow (cumbersome)
  1. Create all tracks for an album
  2. Create the album (reference the tracks created above)
  3. Create the artist (reference the album created above)

Repeat for each new album (or artist / album)

A more ideal workflow

Using a couple contributed modules, (references dialog and inline entity form), we can greatly improve this workflow.

  1. Create an artist, create albums and tracks directly from the artist edit screen!
References dialog

References dialog launches a new content create form in a modal window on the page where you are currently editing content. I've chosen this for album, so new albums can quickly be created without leaving the artist edit screen.

  1. Enable references dialog
  2. Modify albums field settings on the artist content type
Inline entity form

Inline entity form embeds the form of the referencing entity directly on the page. I've chosen this for tracks so we don't have modals in modals, because we already have an album modal window open at this point.

  1. Enable inline entity form
  2. Modify tracks field settings on the album content type
Displaying referenced content

I will only briefly touch on this topic since it could be a whole other blog post.

  1. Modify the view mode display for artist and album
  2. For each entity referenced field, choose "show rendered node"

The sky is really the limit with how you use references in a project. Imagine a social site with profiles referencing work experience, a soccer club website with teams referencing players, or a hiking website with trails referencing other nearby trails. What other tips do you have for folks just getting started with Entity References? What other modules improve usability of Entity References?

Catégories: Elsewhere

Gábor Hojtsy: How to manage drupal.org issues according to your priorities

mar, 24/06/2014 - 19:05

Drupal.org provides an amazingly flexible issue queue and is the backbone of most community activity around code, community, policies, drupal.org itself and so on. Each issue has a priority value which can be one of Critical, Major, Normal and Minor. Even more interesting is the tagging system we use with some commonly used tags like 'beta blocker' or 'beta target' or 'revisit before release' which add extra priority on top of the single value field. The drupal.org issues however don't lend themselves to supporting working on your priorities. Here are some options and tools I used so far that help solve this issue.

Catégories: Elsewhere

Palantir: DrupalCon Austin: a Recap

mar, 24/06/2014 - 17:49

Anyone even remotely connected to the Drupal community knows how special DrupalCon is. The community, code sprints, co-mingling of ideas, and, of course, coffee. Thousands of people from around the world getting together – in Austin, no less – to share, learn, and have fun. Eleven of us went to Austin this year, and now we've had some quality time to reflect, we wanted to share our thoughts and experiences.

Kelsey Bentham

I had a couple of goals going into DrupalCon I wanted to learn some new things, meet some new people, and eat some Tex-Mex – boy, did I accomplish those goals. I am now even more excited about Drupal 8 than I was when I left, and I was pretty excited about it before. I have also learned a lot about how this community functions and continues to grow.

I have to admit, I was a little apprehensive about going to my first big tech conference; thankfully all my worries were for nought. I met some amazing people, and had some great discussions about what people in the community are doing and how they are doing it. I thank you all for making this a wonderful experience. Just so you know I plan on using all of your knowledge and experience to enhance my own. As for the Tex-Mex, it is something I will never eat again outside of Texas.

Tom Jones

Going into DrupalCon, I was excited for the opportunity to learn and exchange ideas with others in the Drupal community – plus catching up with a few clients. And, yes, indulging in Austin’s local culinary adventures.

Being my first DrupalCon, I was impressed by the veterans welcoming new folks. Drupal is truly an inclusive community, and gratitude is the one contribution we can all make going forward, even if you never commit a line of code.

The highlight of the week, and what made the greatest impression on me was spending time with our clients. We employ an integrated approach on projects, and our clients really become part of the team. Seeing them at DrupalCon was really like catching up with old friends.

We know our clients are great, but having the opportunity to observe them at DrupalCon gave me an entirely new perspective. It was inspiring to see their passion first-hand, and how they are using Drupal to achieve their mission. Whether higher education, publishing or medical, our clients are purpose-driven, and it is incredibly gratifying to “empower and enable” them each and every day.

Ryan Wagner

Having been to many Drupal Camps around the east coast, I was incredibly excited to finally attend my first DrupalCon. Being surrounded by so many other people who had come together to learn, share, and talk about something so positive was an excellent experience. My stated goals at the outset were to meet good people, learn new things, and indulge in some local cuisine; I would say that my goals were met or exceeded in all respects. Addendum: Any dietician would likely lift eyebrows at how enthusiastically I tackled the last goal.

Aside from excess amounts of food, I borrowed from DrupalCon an incredible amount of new knowledge and a fresh appreciation for how many people contribute so much time and effort into the Drupal project. With the help of the mentors, I’m now proud to say that I’ve started down the path of my own (small for now) contributions towards the project, and I’m hopeful to make many more.

Steve Persch

I try to focus my Drupalcon experience around catching up on the latest big ideas in the community, and then getting small concrete progress on those ideas. This year that meant working on pull requests to the the Drupal Media team's Entity Embed module after seeing two core conversations that referenced it. Jeff Eaton's Battle for the Body Field Core Conversation highlighted the need to separate the storing and rendering of transcluded data. Dave Reid and Janez Urevc talked about how Entity Embed would be the module in Drupal 8 to carry that idea forward. You, too, can dive in here: https://github.com/drupal-media/entity_embed

George DeMet

While I didn’t get a chance to attend too many sessions at this DrupalCon, I spent a lot time doing Drupal community work for both the Drupal.org Content Working Group and the Drupal Community Working Group.

The Content Working Group and user experience coach Whitney Hess kicked off user research that will inform a revamp of Drupal.org next year. This is a really exciting project intended to help draw new audiences to Drupal, as well as improve the experience for existing users of the site. Look forward to hearing more in the months between now and DrupalCon Amsterdam.

The Community Working Group is responsible for helping to uphold the Drupal Code of Conduct and maintaining a friendly and welcoming community for the Drupal project. In Austin, we approved a conflict resolution policy designed to put process around conflicts that might arise within the community and cannot be easily resolved by the affected parties.

Erynn Petersen’s keynote which made a strong case for the role of diversity in healthy and productive communities, was one particular highlight of the conference for me. While Drupal has a more diverse community than many others in the tech industry, we still have room for improvement. I’m hopeful that the work that both the Content and Community Working Groups are doing will ultimately help to make the Drupal community a more welcoming place for everyone.

Ken Rickard

I spent my time in the DrupalCon “hallway track” having conversations, introducing people and making connections. There were two things that stood out to me: 1) the folks who have been going to DrupalCon for a long time (this was my 15th) really try to reach out to newcomers, and I think this should be an area of focus. Hat tip to Andrea Soper for leading mentorship sprints designed to onboard new developers. 2) There was a sizable Latin American presence at the conference, the first time I’ve really noticed that. I met people from Columbia, Argentina, Bolivia, Costa Rica, and Mexico; and they are all very excited about DrupalCON Bogota next year, and that enthusiasm is spreading.

I also have two main highlights: 1) Inigo San Gil’s performance at the DEIMS session. He was fabulous, and he really nailed the importance of the project and reinforced why we took it on. 2) After a week of convincing, I did finally ride the mechanical bull.

I also had numerous great conversations with people at the booth, centered around the question “What can we do to help make you successful?” I talked to large and small companies, non-profits, schools, libraries, and hospitals and the topic was the same from each: We’re undertaking something new and we need it to be great. We think Drupal can do that for us, and we need someone who can help us realize its potential.

Shawn Smith

With it being my first DrupalCon, I didn’t quite know what to expect from the show or the community at-large. Granted, I had heard many amazing things about the Drupal community since so many Palantiri are so deeply rooted in it, but first-hand experience is always different, regardless of expectations. What a joy all around! The entire atmosphere was welcoming, interesting, fun, and so much more. The show itself was relaxed yet specific. Often at traditional trade shows, there’s a lot of awkward, fluffy networking that leads nowhere. DrupalCon was different. There were no hard sells. Nothing came off as slimy or smarmy. Just good people, good conversation, and good feelings. If I were to pick a singular experience as a highlight, it’d be Trivia Night. Ken suggested I be a runner, and I’m so glad I accepted that role. Met a lot of nice folks, learned more about Drupal, and had a lot of laughs. Thanks for an amazing first impression!

Chris Zietlow

While I’ve been to many local and regional Drupal Camps, Austin was first time attending a Con. I boarded my plane with the expectation that a DrupalCon is just a Drupal Camp turned to 11. Austin was far beyond my expectations of 11. I was hoping to spend a lot of time in sessions, talking to some of the community elites, and generally absorbing as much knowledge as I could. What I couldn’t begin to image was the scale and amount of awesome of the Drupal community. It was thrilling to experience that in person, rather than via forum posts or IRC.

I’ve read the attendance numbers for previous cons and have even seen the infamous group pictures with thousands of people, but wasn’t expecting to feel as welcomed as I was around every corner. In many other open source communities, it’s easy to become just a number and hide in the background, especially as they grow and scale. While I may have been attendee #533, the entire time I was there I felt like an integral part of Drupal. Come for the community, stay for the code as they say.

This has me even more excited for Drupal 8. I’ve been excited by the new architecture, and technical debt that’s being cleaned up, but now I’m waiting to see where our amazing community can take the newest version of Drupal.

Catégories: Elsewhere

Drupalize.Me: Web Profiler in Drupal 8

mar, 24/06/2014 - 16:00

Profiling your site is extremely useful not only for debugging and performance testing but also for learning about how your site handles requests.

Symfony 2 comes with a bundle (like a Drupal module but for Symfony) called WebProfiler Bundle which collects information about each request made to your application and allows you to visualize it in the browser.

Drupal 8 doesn’t include the Web Profiler bundle in core. However, there already is a contrib module for it. Make sure to install any dependencies before enabling the module.

The module will render a fixed bar at the bottom of each page for users with the View webprofiler toolbar permission. The bar provides a summary of the collected data from the profiler.

Catégories: Elsewhere

Acquia: Why Drupal? First Principles

mar, 24/06/2014 - 14:12

This post will give us some common ground on which I can build my case for Drupal. To get started, we’ll need working definitions of success in business today, the nature of open source software, and a quick explanation of Drupal itself. In subsequent posts, we’ll explore specific concepts and examples of how Drupal enables success because it is open source software at scale – a powerful combination: the empowerment of freedom multiplied by an ecosystem of thousands of service providers, tens of thousands of developers, and millions of sites online.

Catégories: Elsewhere

Pronovix: How to get the community to write your documentation

mar, 24/06/2014 - 10:28

In the Drupal community we excel at sharing code, but we are terrible at sharing documentation. I’ve been trying to rally the Drupal community around a standard for reusable documentation for a few years now. But to get people to collaborate we needed to invent a new tool that makes it easy to create, reuse and share documentation between sites and the Drupal project at large. We have built that tool, it’s called WalkHub.

Catégories: Elsewhere

Drupal Association News: Drupal.org User Research: stakeholder workshop outcomes

mar, 24/06/2014 - 07:23

At DrupalCon Austin 2014, we officially kicked off the reimagination of Drupal.org with a full-day workshop with Drupal Association staff, Working Groups, select board members and advisors, facilitated by our user experience coach Whitney Hess. In the morning, we did the serious business of defining our objectives, target audiences, metrics for success (KPIs), partners and competitors, and then in the afternoon broke out into teams to brainstorm provisional personas, use case scenarios, and a blue-sky set of features. These are the hypotheses that we will now test in our user research.

Here are a few outcomes of the day:

Objectives for the Drupal Association:
  1. Grow Drupal community engagement
  2. Grow adoption of the Drupal project
  3. Make it easier to build Drupal
Objectives for a new Drupal.org:
  1. Be the home of the Drupal community and primary destination for collaboration, education and relevant information and answers
  2. Provide tools to help coordinate community development of Drupal and related projects by removing barriers, retaining resources and more
  3. Demonstrate Drupal’s capabilities and advantages, and promote it as an organizational solution
  4. Encourage and enable people to develop themselves and their careers over time
Metrics for success (in no particular order): ↑ % completion of user profiles ↑ # Drupal sites ↑ # Authenticated user logins (globally) ↓ Average issue lifetime ↑ # site visitors (globally) ↑ Traffic to marketing content ↑ Prospect captures ↑ $ received / product category ↑ $ spend by partners y/y ↑ # contributors ↑ # code contributions / contributor ↑ # doc edits / contributor ↓ time issue has 'needs review' status ↑ # project downloads ↑ self-reported community satisfaction ↓ single-time logins ↑ # vendors in Drupal marketplace ↓ #/% inactive accounts ↓ #/% inactive projects ↓ # former Drupal.org users ↑ Drupal 8 effect ↑ # sites using specific projects

 

Despite how busy everyone is at DrupalCon at sessions and in the hallways, we were also able to conduct 11 user interviews with a wide variety of community members. Our user research continues until mid-July, as we interview developers, designers, site-builders, business decision makers, technical leads, content strategists, sysops, marketing managers, evangelists, students, agency heads and more, learning everything we can about what the Drupal community needs to do its best work and what Drupal.org can provide to make that happen.

We are very excited to share the results of our research with you soon.

Thank you for participating in this process with us,

The Drupal Association Staff

--
Flickr photo by 3oheme

Personal blog tags: drupal.org user research
Catégories: Elsewhere

Modules Unraveled: 111 Backup and Migrate 3.x with Ronan Dowling - Modules Unraveled Podcast

mar, 24/06/2014 - 07:00
Published: Tue, 06/24/14Download this episodeNodeSquirrel
  • Let’s start out by getting a quick overview of what Backup and Migrate is.
  • What are some of the new features in version 3.x?
    • Files
    • New UI
    • Notes about backups
    • Backup to two places at once
    • Elysian Cron
    • Smart delete
    • One list for all backups instead of a list for each schedule
    • Restore from stored backup or upload
    • Ctools exportable
  • What are some of the limitations of the module?
  • How does this work in conjunction with Git?
NodeSquirrel Plug
  • Since your the lead developer of NodeSquirrel, give us the pitch :)
    • modulesunraveled.com/easybackups
Episode Links: Ronan on drupal.orgRonan on TwitterBackup and Migrate ModuleGorton StudiosNodeSquirrelTags: 
Catégories: Elsewhere

Drupal core announcements: Core Sprint: Drupal 8 at the Jersey Shore

mar, 24/06/2014 - 04:25
Start:  2014-07-12 09:00 - 2014-07-13 17:00 America/New_York User group meeting Organizers:  crowdcg pwolanin davidhernandez Event url: 

http://jerseyshoredrupal.github.io

Join members of the NJ Drupal Community at our upcoming sprint: Drupal 8 at the Jersey Shore. The event will be held in Asbury Park, NJ and run all day on Saturday, July 12 and Sunday, July 13.

Join like-minded Drupal contributors for two full days of core and contrib sprinting to further advance Drupal 8. We'll have a list of approachable Drupal 8 critical tasks for participants to work on (thanks to remote help from xjm).

Get a ticket on Eventbrite. Attendees will be provided with breakfast, lunch, and snacks throughout the event. Further details about the event can be found at http://jerseyshoredrupal.github.io.

All attendees should have previously participated in a core sprint and/or have a fully working local environment for developing patches.

We look forward to seeing you at the Jersey Shore!

Catégories: Elsewhere

PreviousNext: The Drupal jack of all trades

mar, 24/06/2014 - 01:08

Last week I was very fortunate to not only attend, but be the keynote speaker for DrupalCamp Singapore! Here are my take aways and keynote slides.

Catégories: Elsewhere

Stanford Web Services Blog: Top 6 things to do while your cache clears on its own

mar, 24/06/2014 - 00:05

Caches are a great tool, they store your website's database and code information in a way that loads much faster. But they DO mean that your changes don't appear right away.

Where are my changes?

One of the things we here at Stanford Web Services get emailed about most frequently is, "Why did my changes disappear when I logged out?" The answer is that the site caches haven't yet been updated, but they will if we wait a little bit (sometimes a few hours or so).

Catégories: Elsewhere

Pages