Skip to Content

Drupal

Drupal core announcements: These two weeks in Drupal Core

Planet Drupal - 15 May 2014 - 3:30pm
What's new with Drupal 8?

The past two weeks saw the Drupal community rally together to support each other and recognize the hard work involved in making Drupal awesome, starting with the launch of the Drupal Core Gittip Team and the news that Alex Pott had been hired by Chapter Three to work on Drupal 8 development full-time. It also saw some great performance improvements in Drupal 8 and a handful of Developer Experience improvements.

Drupal Core Gittip Team

On Friday, May 2nd, Cathy Theys (YesCT) and Alex Pott (alexpott) launched the Drupal Core Gittip Team, a new funding effort to allow companies and individuals to support the people who are regularly contributing their own time, without compensation, to Drupal Core development. (See their announcement and Team FAQ for more information.) A weekly contribution to the Core Gittip team is a great way for individuals and companies (and you!) to both help Drupal 8 and improve the long-term sustainability of Drupal Core development.

Sponsored Drupal 8 development

On Tuesday May 6th, Alex Pott announced that Chapter Three had hired him to work on Drupal 8 full-time, and that he would be using his Gittip income to support the rest of the Drupal Core Gittip team. This came a year and thirty-five days after he became a Drupal co-maintainer and nine months after he asked for the community's help to continue to support his Drupal 8 development work.

In response to Alex's announcement, Dries blogged about the investment case for employing a Drupal core contributor and Jennifer Hodgdon responded with the case for a small Drupal shop contributing to Drupal.

Contrib fundraising initiatives

Nick Veenhof announced that the Search API team were able to meet (and exceed!) their goal to fund the porting of Search API to Drupal 8 along with the next sprint date.

And, Wolfgang Ziegler (fago) announced the #d8rules initiative, an effort to get the Rules module ported to Drupal 8.

Where's Drupal 8 at in terms of release?

Last week, we fixed 13 critical issues and 16 major issues, and opened 11 criticals and 12 majors. That puts us overall at 115 release-blocking critical issues and 545 major issues.

4 beta-blocking issues were fixed last week. There are still 20 of 163 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.

More ways to help

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 on Gittip.

Notable Commits

The best of git log --since "2014-04-30" --pretty=oneline (147 commits in total):

There were a number of commits that improved performance directly and indirectly:

  • Issue #2099131 by jessebeach, Wim Leers, catch, Berdir, benjifisher, martin107, andypost: Use #pr_render pattern for entity render caching.
    This slight change to the render pipeline allows Drupal to cache the render array, in addition to the resulting HTML. Preliminary tests showed that, from a warm cache, this change makes full page loads between 15 and 25% faster. Woohoo!
  • Issue #2226761 by Wim Leers: Change all default settings and config to fast/safe production value.
    This changes the default settings for new sites so that HTML and Twig caching, CSS and JavaScript aggregation are all turned on, and Twig debugging and Twig auto-reloading is turned off.
    It also introduced an example.settings.local.php with examples of how to toggle these settings on development sites.
  • Issue #2257709 by znerol, Wim Leers: Remove the interdependence between the internal page cache and management of the Cache-Control header for external caches.
    This commit is part of an ongoing effort to modernize the page caching mechanisms in core. This change makes the Symfony Response object responsible for setting the Cache-Control HTTP header.
  • Issue #2228261 by beejeebus, kim.pepper, alexpott, Wim Leers | catch: Add a local, PhpStorage-based cache backend.
    This will make it possible to cache data on the filesystem when it makes sense to do so.
  • Issue #2241249 by Wim Leers: First step in making search results pages cacheable: add the associated SearchPage's cache tag.

To improve the developer experience (DX):

  • Issue #2079797 by ParisLiakos, Xano, amateescu, tim.plunkett: Provide a trait for $this->t() and this->formatPlural().
    Previously, any class that containing at least one translatable string needed to define a t() function that called \Drupal::translation()->translate(...) in order for the string extractor to determine what needed to be translated.
    This patch reduces the boilerplate code to a single line: use StringTranslationTrait; through the use of a PHP Trait. Classes with this trait can still call $this->t() to make strings translatable.
    Reducing boilerplate code for the win!
  • Issue #2241633 by sun: Simplify site-specific service overrides.
    You can now override a service in your module by simply adding a services.yml file.
  • Issue #2257835 by tim.plunkett, sun, Jalandhar: Move form submission logic out of FormBuilder int a new class.

And...

  • Issue #2039163 by Reinmar, Wim Leers: Update CKEditor library to 4.4.
    Did you know that the CKEditor Widgets feature introduced in CKEditor 4.3 was specifically developed for Drupal 8 as a way to make accessible, easy-to-use templates in body content?
    This patch updated CKEditor from 4.2 to 4.4, adding this feature and unblocking a couple of other ones.
  • Issue #2116363 by Berdir, jessebeach | fago: Unified repository of field definitions (cache + API)>
    This milestone Entity Field API commit concludes work begun at DrupalCon Prague and unblocks the removal of legacy D7 field API code.

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

Here are a selection of the best blog posts about Drupal 8 in the past few weeks:

Drupal 8 in "Real Life"

There are a whole bunch of camps and sprints happening this coming weekend (May 16, 17th and 18th)!

  • Drupal Open Days 2014 in Dublin, Ireland on May 16th and 17th, with a session on building Multilingual sites in D8.
  • DrupalCamp Wrocław in Wrocław, Poland on May 16th, 17th and 18th has sessions on CKEditor in Drupal 8, Drupal 8 on mobile platforms, and a session on what to look for today so as not to get left behind when Drupal 8 is released.
  • DrupalCamp Spain 2014 in Valencia, Spain on May 16th, 17th and 18th with a Drupal Core Criticals sprint and sessions about CMI, Sessions in D8, Commerce in D8 and a couple of talks on Migrate in D8.
  • MoldCamp 2014 in Chisinau, Moldova on May 17th and 18th, featuring sessions on Guzzle and what to expect in Drupal 8.
  • Drupal Camp Alpe-Adria in Portoroz, Slovenia on May 17th and 18th, with sessions on the D8 Entity API, Rules in D8 and CMI; and with D8 sprints.
  • TC Drupal Spring Sprint in Minneapolis, MN on May 17th, featuring a documentation sprint!
  • Albany Drupal Sprint Day in Albany, NY on May 18th.

Also coming up are:

  • DrupalCamp Helsinki on May 23rd and 24th in Helsinki, Finland, featuring sessions on Symfony, Media Management in Drupal 7 and 8, D8 JavaScript, D8 Routing and Menus, D8 Theming and multiple sessions on Twig. And, to top it all off, there will be code sprints.
  • DrupalCamp Soleil 2014 in Montpellier in the south of France on May 24th and 25th, featuring an non-non-conference on Drupal 8.
  • A Drupal 8 Code Sprint in Leuven, Belgium on May 25th.
  • DrupalCamp Yorkshire 2014 in Leeds, West Yorkshire, England on May 31st and June 1st.

Don't forget that DrupalCon Austin is quickly approaching! The extended sprints start on May 31st and run until June 8th. If you plan to participate in any way (remotely or in-person), please sign up ahead of time so we can plan for your attendance!

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!

Categories: Drupal

Drupal Association News: Happy Global Accessibility Awareness Day

Planet Drupal - 15 May 2014 - 1:11pm

Today is Global Accessibility Awareness Day, and people and companies from all around the globe are participating. I had the privilege of giving a speech this morning on how Drupal is one of the best content management systems for accessibility. It’s always inspiring to see the Drupal community’s commitment to accessibility.

What is accessibility?

Accessibility is about making a product, device or service as widely available as possible. With websites this means providing greater accommodation, generally through a web browser, to a wider diversity of humanity. Web accessibility works to support the whole population, not just those who have perfect vision and are easily able to use a keyboard and mouse. Scalable text, semantics like headings, and even mobile responsive capabilities all fall under the umbrella of accessibility.

Why is Drupal great for accessibility?

The Drupal community has chosen to address accessibility at the source. In Drupal 8 we are adding meaning through new semantic HTML5 elements in a way that is easy and gives screen reader users much needed context. This structure also applies to Drupal 8’s out-of-the-box mobile capabilities, giving screen reader users the ability to navigate and even administer their site through their phone.

Additionally, Drupal’s multilingual functionality is fantastic. Because of the community’s early commitment to internationalization, it’s easy to have more than one language at a time enabled on a website, and Drupal’s internationalization structure has made it easier to build in accessibility for multiple languages at once.

Drupal 8, builds on the accessibility work done in previous releases. We’re incorporating aural alerts, better tab ordering, forced alt text, and more to make it even easier for individuals with disabilities.  With Views being incorporated into Core, Views UI has been made more accessible, as has the table output which is now used throughout the admin interface.

How can I help?

Drupal’s accessibility is great, but just because your website is built with it doesn’t mean it is accessible. It is always useful to engage with people who have disabilities, and use automated testing tools, educate yourself on the issue and have an expert provide an audit of your site. Seek feedback from users with different abilities, and really listen thoughtfully to what they have to say. Together, we can make a difference!

Categories: Drupal

Drupal core announcements: Drupal 8 alpha 12 on May 21

Planet Drupal - 15 May 2014 - 11:30am

The next alpha for Drupal 8 will be alpha 12! Here is the schedule for the alpha release.

May 18-20, 2014 Only critical and major patches committed May 21, 2014 Drupal 8.0-alpha12 released. Emergency commits only. May 22-25, 2014 Disruptive patch window
Categories: Drupal

Cheppers blog: Bundlerize your SASSy themes!

Planet Drupal - 15 May 2014 - 7:08am

Nowadays many web-frontend developer use Compass framework to easily manage the CSS side of the currently developed project. We at Cheppers use Compass to compile the SASS files in our custom theme projects. If you do too, and you ever ran into an ugly circular gem file dependency problem, you definitely should use Bundler.

Categories: Drupal

Drupal core announcements: Accessibility Issues That Affect Administrators (Part 2 of D8 A11y Update)

Planet Drupal - 14 May 2014 - 2:02pm

In Part 1, I mentioned Authoring Tool Accessibility Guidelines (ATAG) although most of the analysis here will be geared to achieving Web Content Accessibility Guidelines (WCAG) 2.0 AA. Drupal is both about web content and the process of authoring that content and ATAG 2.0 is about both. For the most part we’ve looked at seeing that the admin side of Drupal is as accessible as the public facing components. The interface also has a strong role in producing better, more accessible content. Being able to force alt text for images is a part of this, but it is just the beginning.

Many of the elements mentioned in Part 1 will also be present on the admin side. For instance, we’ve adopted similar approaches to both Bartik & the default admin theme Seven when it comes to ARIA & HTML5.

Administering any CMS, you are ultimately navigating web forms to manage the content. We’ve done lots of little things to clean up the accessibility of the admin side from silencing the “*” for screen readers to adding missing titles. There are lots of places where LABELS were used for markup rather than as a semantic relationship, and we’ve fixed most of those now (see 1811216, 2044521, 1932068 & 882666). We’ve also enlarged the font size for things like the table sorting link so it is easier for people who have mobility challenges to find and use.

We also cleaned up the accessibility contextual links (849926 & 1905340). Removed blank table headers, fixed up file uploads so that screen readers get some notifications and made sure that parents didn't show up if there were no child elements present. dealing with parents. Lots of little items like this have been cleaned up throughout the interface, but since the understanding about web accessibility has grown so much Drupal 8 contributors it is a lot less than it used to be. Accessibility is talked about by much more than the accessibility team.

These forms ultimately encourage content authors to follow best practice in the creation of their content, including web forms. By using Drupal properly and following the examples in Core it will be much easier for everyone to create accessible content by default, an important part of ATAG 2.0 AA compliance. A simple example of this is that we expanded the allowed filters in Drupal 8 to encourage users to use HTML headings in the default Filtered HTML text format.

On the admin side we made internationalization more accessible by improving the String Translation UI and ensuring that the original language is set semantically. We have also allowed the ability to synchronize alt and titles text for multi-lingual images. Most of the other accessibility challenges with multi-lingual sites are then just taken care of when the content is presented to the users. A great illustration of ATAG 2.0.

As with the public facing links, we have continued to ensure that the “purpose of each link can be determined from the link text alone” and have done so both in the Forums as well as with the main Add content links.

We increased the maximum allowed text size for alt and title strings to be 1024 characters allowing for more complex descriptions of images. Although not in Core yet, through CKEditor it is possible to add longdesc links for other images.

jQuery UI’s modal dialogs are used all over in the admin side and are a great example of the Proudly Invented Elsewhere concept, as is the adoption of CKEditor. Serious work went into choosing which WYSIWYG editor went into Drupal 8 and accessibility was a big component of the decision. With that we get a lot of accessibility gains as IBM and others have worked to improve CKEditor’s accessibility over the years. With Drupal we have improved our own configuration pages so that it can be administered with people using assistive technologies. We will also get benefits from accessibility enhancements made to CKEditor, like the Language of Parts improvements which are scheduled for a 4.3 release.

Views. The most powerful module in Drupal 6 and 7 got brought into Core. With that it got cleaned up a great deal, particularly for it’s accessibility. Now it is even easier for administrators with disabilities to use this incredibly powerful query engine. There were a bunch of basic improvements like:

None of these will affect the output of Views, but there were also improvements to the output as well. The mini-pagers in views needed a header and additional context to understand the purpose of the previous/next links. This brings it up with the accessibility levels for pagers in the rest of Drupal Core.

The tables are also significantly improved as there is now proper id/header semantics included by default. This makes it easier for users to know where they are on large data tables. To keep up with data tables in HTML5 we have had to add captions and descriptions and removed the summary element for tables. Having this ability to control the captions and descriptions of tables is a really strong advantage for Drupal.

Another nice element is that many core admin listing pages are being migrated over to Views, so that this semantic presentation is available for many of the lists that are required critical for Drupal 8.

Plug: I will be presenting about the Drupal Accessibility Advantage at 7am ET (May 15th) as part of Inclusive Design 24. There will be 24 such videos, one for every hour of Global Accessibility Awareness Day. These videos should be available in the future for those who miss tomorrow's presentation.

Categories: Drupal

Propeople Blog: 23 Acquia Certified Drupal Developers (and Counting)

Planet Drupal - 14 May 2014 - 1:10pm

Every day at Propeople, I get to interact and work with a top-notch team of Drupal experts. And even though those of us at Propeople, as well as our clients, can vouch for the high caliber of our team, it never hurts to have some solid facts that show the awesome talent that we’re lucky enough to have on our team. This includes receiving awards, taking on some of the largest Drupal projects in the world, and, now, the Acquia Certification Program - a new program created by Acquia to validate the skills and knowledge of Drupal developers.

Acquia just launched the certification at the beginning of April, and already Propeople counts 23 of our developers among those that have successfully gone through the Acquia certification exam! That's right...23 developers! We couldn't be more proud, and we’re excited to see that number keep growing as more members of our technical team are able to take the certification exam.

So far, Propeople Drupal developers from across our offices in the US, Denmark, Ukraine, Moldova, and Bulgaria have become certified through the program.

As an Acquia Enterprise Partner, Propeople is proud to be an early adopter of Acquia’s Certification Program. With the Drupal community and marketplace continuing to grow, having such a measure of knowledge and expertise is a benefit to us, and to our clients. Top businesses and organizations that are currently using (or looking to use) Drupal seek out the best Drupal talent in the industry - and Acquia’s Certification Program provides us with some hard evidence that Propeople’s Drupal specialists are some of the best in the world.

To learn more about how Propeople’s qualified team can help you make your next Drupal project a success, make sure check out what services we offer and reach out to us.

 

 

Tags: DrupalAcquiaDevelopersCertificationCheck this option to include this post in Planet Drupal aggregator: planetTopics: Tech & Development
Categories: Drupal

Forum One: Relaunching GlobalChange.gov

Planet Drupal - 14 May 2014 - 12:42pm

Last Tuesday, 240 of the country’s top climate scientists and experts released the third National Climate Assessment (NCA). The report details the current and best understanding of how climate change is already impacting Americans’ health and livelihoods in every region of the country. The takeaway from the report is that if you live in the United States, you’re either already dealing with climate change, or it is coming soon to your neighborhood.

When Forum One began working with the U.S. Global Change Research Program (GCRP) last year on a new design for globalchange.gov, we knew we had a big job, but we didn’t know we’d have such a big audience.

Our goal in redesigning globalchange.gov was to help GCRP bring context and transparency to global change research within the federal government. The release of the new NCA is an opportunity to draw attention to the issue of global change - and to showcase the wide range of related Federal information. As an example, our Browse section includes reports and datasets from the Global Change Information System (GCIS), a federal portal which houses climate change research drawn from thirteen federal agencies and organizations who study climate. In the long-term, we want to make it easy to trace the connections between the individual pieces of research that constitute “what we know” about climate change. 

Though our project team had lofty goals, we faced a lot of common website design challenges. One of GCRP’s organizational goals is to make their science accessible. If the scientific findings aren’t explained clearly, then the chances of anyone actually doing anything about it are slim. However, the site also has to work for scientists sharing their research, and policymakers and planners who want to understand how climate change will affect their communities. We needed a design that would help all of GCRP’s audiences find the information they need to make smart climate decisions. John Schneider, one of our senior user-experience designers, designed the overall information architecture that created unique paths through the site for each of GCRP’s key audiences.

One of our team’s first ideas was the Understand section of the site, which helps those new to climate change understand the “big picture” story of what’s happening, what it means, and how we know. The Explore section gives visitors a direct path to aggregation pages for the regions and topics that provide details and context to the overall NCA findings. The Browse section, as mentioned above, is the portal into the GCIS and all the climate data and research you could ever want. Through the Follow section, users can subscribe to GCRP news or social feeds, and the Engage section provides info on public events or other opportunities to get involved with the assessment process itself.

For visual design, we turned to our long-term partners at Antistatic Design to create the “slick” look & feel that beautifully showcases the stark reality of climate change on your desktop, mobile, or tablet device. Finally, our site search allows users to quickly find content within the overall website or just within the NCA report module itself, developed by the firm Habitat Seven and NOAA’s Cooperative Institute for Climate & Satellites.

Between interesting design challenges and working with the brilliant and engaged staff over at GCRP, we had plenty to focus on beyond any attention from 1600 Pennsylvania Ave.

Once we started to hear and see the attention on the recent IPCC report release, the whole project took on a new urgency. We were confident in the quality of our design, but at that point we knew that we needed to be equally confident in our hosting infrastructure. Suddenly it was clear that there was a lot of attention on the climate issue, and a hunger for new scientific research. We got wind of some traffic numbers from the IPCC report website, which we used to extrapolate a baseline expectation for our launch. We deployed a content delivery network (CloudFlare), and a page caching solution (Varnish). We conducted load testing and refined our hosting setup until we were confident that we could handle anything short of a highly-orchestrated DDOS attack. We also implemented FISMA compliance measures to ensure that the site and data was secure and only authorized users from GCRP and the development team were able to access administrative functions on the site.

On launch day, we knew pretty quickly that we were going to hit our targets. The site went online just after 8am, and by noon we had seen over 50,000 visitors. Over the next 48 hours, over a quarter-million people would browse the site or read the report. Dozens of reporters covered the White House stakeholders event – where our site received quite the hurrah from Presidential advisor John Podesta – and morning shows across the country were invited to send their meteorologists to interview the President. Throughout the day, our site held up as the numbers kept climbing and climbing. At least one person on Twitter seemed impressed:


There may not have been a lot of good news for the country in the latest NCA report, but we loved working with GCRP and our other partners on the new globalchange.gov. At Forum One, we spend a lot of time geeking out on the latest coding trick or UX trend, but what motivates us more than anything is helping our clients make progress on issues that matter, and this is a big one.

The message of the Third NCA is that climate isn’t a problem for tomorrow, but for today. Like climate change itself, changing the political consensus can be a staggeringly slow and incremental process, but once in a while, something new at the right moment can trigger rapid, cascading change. That’s what we need on the issue of climate change, and we hope that the redesigned globalchange.gov helps the American people understand why.

When Forum One began working with the U.S. Global Change Research Program (GCRP) last year on a new design for globalchange.gov, we knew we had a big job, but we didn’t know we’d have such a big audience.

 

Categories: Drupal

Drupal Association News: Add the Drupal Project to your professional experience on LinkedIn

Planet Drupal - 14 May 2014 - 12:38pm

For many in the Drupal community, working on the Project can become like a full-time job. Maintaining modules, patching bugs, organizing camps and responding to issues in the issue queue can be a lot of work, and now, you can get professional recognition on LinkedIn for your efforts.

There is now a company page for the Drupal Project available to anyone who wants to cite their work with Drupal as professional experience on LinkedIn. This is a great opportunity to get recognition from employers and colleagues for your hard work, and to signal to future employers that you’re a Drupal expert and/or contributor.

You can find the LinkedIn page here. To add it to your work experience, treat it like you would any other company: edit your profile, and when you type in Drupal Project under “Experience,” it should pop up.

Let us know if you have any questions or feedback. Thank you for all your hard work on the Drupal project.

Categories: Drupal

Chapter Three: The future of the internet is as stake

Planet Drupal - 14 May 2014 - 12:31pm

America’s online freedoms are under attack. FCC Chairman Wheeler wants to give Internet service providers like Comcast and Verizon the power to block access to the Web unless content providers pay an extra fee. The Internet pipeline will be divided into different streams of varying quality, and sites will be required to pay premiums based on the performance of their users connections.

Net neutrality or bust

The demise of net neutrality will give big companies with lots of money premium access to digital networks and make it difficult for independent communities to thrive. The Web’s openness makes it possible for open source projects with meager funding, like Drupal, to compete against wealthy, established brands such as Adobe. If Drupal.org had to pay premiums for Internet access, it may have never been feasible to exist alongside companies with enourmous budgets.

Chairman Wheeler’s so-called “fast lane” proposal for Internet traffic will give Internet service providers unprecedented power to control our access to culture and politics. The magnitude of this issue has driven me to spend the past few weeks scouring the news, signing petitions and telling everyone I know about the situation.

Taking to the streets

I even went as far as trying to mastermind a political demonstration in downtown San Francisco to tell our senators that net neutrality is important and to demand the FCC to keep it that way. The event was essentially a flop, but technically, I pulled it off. At the very least, I got to speak with a representative from Senator Feinstein’s office who came down to chat with me in the plaza.

Organizing the demonstration was an excellent learning experience, regardless the outcome. It pushed me out of my comfort zone while giving me a richer perspective on the issue and democracy in general. It also made me think about better ways to influence change by leveraging my strengths instead of naively rush into the unknown.

My manic, sleep deprived dreams of political manifesto were, if anything, a cry for help. It was a plea for the nation to band together and tell our representatives that keeping the Web open is important. We must demand that our representatives urge the FCC to uphold net neutrality or lose the promise of a connected world.

Only YOU can save net neutrality

Take action now and sign this petition to the FCC telling them that net neutrality is vital to the web’s future. Internet access is now a fundamental part of our society and it is necessary for a vibrant, healthy economy. We are increasingly dependent on the Web to distribute information, exchange ideas, and create new tools. Senator Al Franken is right about the net neutrality debate being the civil rights issue of our time. We can’t let huge media monopolies take control of such an influential tool.

We at Chapter Three have taken a stand on the issue by signing the Declaration of Internet independence. Encourage your employers to support freedom online by doing the same. Check out this list of resources from the FreePress organization to discover even more ways to help.

Can you think of any more ways to reach out? What have you already done to protect the integrity of the Web and what tactics do you find most effective? I believe we can live in the world of our dreams but not without fighting for it first.

Categories: Drupal

DrupalCon Austin News: So you're going to DrupalCon Austin. Now What?

Planet Drupal - 14 May 2014 - 7:30am

You've got your tickets to DrupalCon Austin. What happens next? This fun and helpful infographic maps out the next steps for you. From reserving a space to sleep to selecting your schedule and keeping up with all the latest news, this infographic comes complete with links to help you plan out your DrupalCon Austin adventure.

Categories: Drupal

Mediacurrent: Energize Your Web Project at Drupalcon

Planet Drupal - 14 May 2014 - 5:22am

Here at Mediacurrent, we’re counting down the days until Drupalcon Austin. This year, we’re proud to be a Platinum sponsor, and we’re bringing our A-game with over a dozen teammates, The Weather Channel Case Study, Power Sessions, Office Hours, an After-party (with LingoTek), and a ton of other activities. If you’re attending Drupalcon Austin this year, here are 5 reasons to pay Mediacurrent a visit:

Categories: Drupal

Acquia: Ultimate Guide to Drupal 8: Episode 2 - Mobile Improvements

Planet Drupal - 14 May 2014 - 4:58am

Welcome to the second instalment of an 8-part blog series we're calling "The Ultimate Guide to Drupal 8." Whether you're a site builder, module or theme developer, or simply an end-user of a Drupal website, Drupal 8 has tons in store for you! This blog series will attempt to enumerate the major changes in Drupal 8. Successive posts will gradually get more technical, so feel free to skip to later parts (once they're published) if you're more on the geeky side.

Categories: Drupal

Code Karate: Drupal 7 Commerce Stripe Module

Planet Drupal - 14 May 2014 - 4:37am

The Commerce Stripe module integrates Stripe with the Drupal Commerce checkout and payment system.

Categories: Drupal

Modules Unraveled: 107 The Community Summit at DrupalCon Austin with Addison Berry and Mortendk - Modules Unraveled Podcast

Planet Drupal - 14 May 2014 - 1:41am
Published: Wed, 05/14/14Download this episodeTrack
  • What exactly is the Community Summit?
  • When is it? Monday, June 2 - the day before the conference itself starts
  • How did it go in Prague?
  • Is there anything that will be new or different in Austin?
Episode Links: Community Summit in AustinSubmit Your Desired ProjectDrupalCon Social EventsMorten on TwitterMorten on Drupal.orgMorten’s BlogHire Morten for Theming StuffAddison on TwitterDrupalize.meAddison’s BlogDareConf 2014GruntTags: 
Categories: Drupal

Modules Unraveled: 107 The Community Summit at DrupalCon Austin with Addison Berry and Mortendk - Modules Unraveled Podcast

Planet Drupal - 14 May 2014 - 1:41am
Published: Wed, 05/14/14Track
  • What exactly is the Community Summit?
  • When is it? Monday, June 2 - the day before the conference itself starts
  • How did it go in Prague?
  • Is there anything that will be new or different in Austin?
Episode Links: Community Summit in AustinSubmit Your Desired ProjectDrupalCon Social EventsMorten on TwitterMorten on Drupal.orgMorten’s BlogHire Morten for Theming StuffAddison on TwitterDrupalize.meAddison’s BlogDareConf 2014GruntTags: 
Categories: Drupal
Syndicate content


Google+
about seo