With around 767 submissions from around the globe DrupalCon New Orleans must have set a new record for an all time high for session submissions at any conference. We can only imagine the plight of track chairs who helped select final ~150 sessions, given the numbers we are absolutely thrilled to announce that three of our talks (Including one in higher ed summit) have been accepted for Drupalcon New Orleans.
Here is a brief of talks at Drupalcon New Orleans May, 2016.
Saket and Piyuesh will talk about Service Workers on D8 and the promise of offline web. The topic is a build up from series of BoF at Drupalcon Asia where service workers was discussed passionately and pragmatically. It’s not just frontend, necessary backend infrastructure (route caching, url config) needs to be present for service workers to be a reality, hence Saket and Piyuesh ( our frontend and backend leads ) decided to team up on this. You can read more about the tentative agenda at the session synopsis and here are rumours of what to expect in the demo:
Config for urls for offline first approach
Config for urls for network first approach & fallback to serviceworker cache
Static resource caching via service workers
Since D8 has placeholders, it would be wise to cache the response of placeholders & render them using service-workers. Background sync can be used to keep pulling in fresh data for the placeholders.
Saket is back with a session on the utopia of using Drupal 8 as a backend for multiple front end frameworks; this time it’s through Polymer. Webcomponents have had the frontend community wanting, what’s not to desire? Reusable components, shadow DOM, templating and much more all native to the browser. Though webcomponents paints a beautiful feature, Polymer from Google delivers it as a polyfill for the restless. In this talk Saket will talk about what Drupal 8 frontend programming might look like and glitches we might need to resolve for a smooth future.
Drupal Campus Ambassador Program - A community Initiative:
A wildcard entry into Dries’s keynote and Holly’s closing-note at Drupalcon Asia, DCAP made its humble beginnings in one of India’s regional events, where business folks were trying to find answers to Drupal talent problems. In spirit of Drupal community’s do-ocracy some of the community members figured a WIN-WIN solution for the problem, that is to take Drupal to colleges and evangelise it professionally. There have been numerous college workshops but DCAP is different in ways that it provides longevity and support to college students and that is exactly what Rakhi will be sharing at Higher-ed summit -- a bit of the history, successes so far and brave new world Drupal will foray into through DCAP. Catch Rakhi in action on May 9 at DrupalCon New Orleans.aurelia.bhoy Mon, 03/21/2016 - 13:39
Last Friday, I gave the first in a series of front-end web development talks here in Taipei. There were 11 attendees as we discussed in length how to structure a site’s styles with CSS components and Drupal 8 naming conventions.
How quick do pages on your site load? How quick should they load? How do you make pages load quicker?
Why should you care?
The speed of pages loading on websites is often overlooked in web projects, and can be a major difference between two sites that otherwise look the same. Let's start with why you should care -- or rather, when you should care.PerformanceDrupal PlanetProfilingInfinite ScrollUser Experience
After lot of research, finally got the way to render blocks in twig files.
Basically there are two type of renders.
- When there is an existing instance of the block in the layout. The the block can be rendered in twig using preprocess as $block = Block::load('mediablock'); $variables['social_links'] = \Drupal::entityTypeManager() ->getViewBuilder('block') ->view($block);
- There is no instance or configurations for the block. Then in the preprocessor we need to create the instance, build the block and then render it $block_manager = \Drupal::service('plugin.manager.block'); $config = ; $plugin_block = $block_manager->createInstance('farmjournal_social_sharing', $config); $render = $plugin_block->build…
The TWG coding standards committee is announcing two coding standards changes for final discussion. These appear to have reached a point close enough to consensus for final completion. The new process for proposing and ratifying changes is documented on the coding standards project page.
The two issues being proposed are:
- Allow camelCase also for local variables / parameters (please not that this particular issue still has some dissention but we think that the community spotlight could help draw it to a final conclusion)
- Should we require a blank line after <?php?
As a follow up on the preceding set of issues now concluded:
- Please relax requirement for @file when using OO Class or Interface per file: 'ERROR | Missing file doc comment' was ratified and is currently RTBC now just waiting for documentation updates
- [policy, then patch] Consistent .install file layout has been rejected as a coding standards change but is moving on as an update for Drupal core
These proposals will be re-evaluated during the next coding standards meeting currently scheduled for March . At that point the discussion may be extended, or the policy may be dismissed or ratified and moved to the ‘update documentation’ step.
Since 2011, Drupal core has had a scheduled monthly bugfix release window, and since 2012, this window has specifically been on the first Wednesday of the month. We are considering extending this window so that a bugfix release is scheduled to come out during a specific week, but not necessarily on Wednesday or any particular day. This is to provide more leeway for release managers to prepare releases across timezones.
Coordinated security releases would still occur during the fixed window on the third Wednesday of the month. The bugfix release windows would still be scheduled every month around the first Wednesday, but might occur anywhere from Tuesday to Friday.
Please let us know by April 1 on the core policy discussion issue if you have any concerns with this proposed change. Otherwise, we may plan to have the release window begin at midnight UTC on Wednesday April 6 (Tuesday evening in the western hemisphere) and extend until the release is created (anywhere from that time through the end of the week). Thanks!
Below you will find the module updates that catched my attention last month:1. Security Kit
Searching on fields in Views is made possible by adding an exposed filter for the relevant field. You can search on multiple fields by adding multiple exposed filters. But what if you want to have one single search box searching multiple fields? This is a very common requirement.
Fortunately, you don’t need to download any additional modules, or do any view alter magic in code. All you need is the power of combined filters.
We made it to the end of another busy work week! Welcome back to Episode 4 of The Mediacurrent Friday 5.
This week, Drupal Developer Ryan Gibson spends 5 Minutes on Configuring Your Drupal Site. With the release of Drupal 8, there are tons of new features to be excited about. One of them being configuration management, or how changes are tracked and controlled in Drupal.
Watch the video below to learn more about how to handle configuration management in Drupal 7 and 8.
Drupal tutorial videos from Mustardseed Media Inc.
CiviCRM Blog: CiviCRM Entity - Working with CiviCRM Contacts on Drupal Node Edit Forms Using Inline Entity Form
It's becoming a common request from our clients to find user-friendly ways to integrate CiviCRM data with the rest of their Drupal website functionality. Oftentimes content creators without direct user access to CiviCRM need to do simple things, such as create, update, and delete contacts in simple, specific ways.Example Use Case
A hypothetical organization advertises various community service projects that they organize and coordinate. Each service project can have it's own page, created by adding a Project content type to display a description, images, videos, slideshows or other information for each project. You'll probably use a View to show multiple Project listings on a page. All that is standard Drupal site building content and functionality. No problem.
But what if the organization wants to display to the user the Project Coordinator(s), which they also want to store in CiviCRM as contact(s)? Their Drupal website content creators need to be able to select, create, and update CiviCRM contacts for the coordinator on the Project node edit form in a simple, user friendly way. The website content creators are not given access to the CiviCRM back end. The organization wants the form to be styled like the rest of the Drupal site and be fully responsive.Challenge
You have CiviCRM data that you need to use with Drupal's standard field and node display and theme structure. What to do?The Solution
CiviCRM Entity to the rescue!
CiviCRM Entity is a Drupal module which exposes many CiviCRM entities as true Drupal entities. That means that almost any module that can use Drupal entities can also access and manipulate CiviCRM data, Drupal style. This includes many commonly used modules such as Views, Rules, Search API, Entityqueue, and many more.
You can use a standard Drupal Entity Reference field and integrate nearly 30 different CiviCRM entities in the standard Drupal way, into any of your node or entity infrastructures. Contacts, Addresses, Emails, Phone numbers, Events, Contributions, Memberships, Activities, and many more CiviCRM entities can be referenced in a consistent manner.System Requirements
Drupal 7 and CiviCRM 4.4 or higher
Install the following Drupal modules and their dependencies:
- CiviCRM Entity
- Entity Reference
- Inline Entity Form
- CiviCRM Entity Inline
- Display Suite
- Display Suite sub-module Display Suite Forms
After following the instructions content creators will be able to select, create, update, or delete CiviCRM contacts with ease and assign them as Project Coordinator(s) for the Project nodes! These content creators need not ever see the CiviCRM backend. You can follow the same procedure for CiviCRM Events, and nearly 30 other entities. Cool, yeah?
Have fun with your own specific implementations!Who are We?
Skvare is a leader in Drupal and CiviCRM integration and project lead for CiviCRM Entity. Contact us to get questions answered and for consultations to make the most of your Drupal and CiviCRM installation.
ArchitectureCiviCRMDrupalInterface and designv4.7v4.6v4.5v4.4
It’s a big day for DrupalCon New Orleans attendees: sessions, training opportunities, and scholarships and grants have been finalized! We’re pleased to announce the lineup of learning, sharing, and networking opportunities for DrupalCon North America attendees this May.
Before the launch of Drupal 8, we started a Kickstarter project.
Our goal was to help as many people as possible to use Drupal 8.
Our strategy was to give everyone free access to the very best Drupal 8 training by releasing free videos.
Today, I'm delighted to say we are succeeding.
If you’re planning on attending DrupalCon New Orleans, better buy your tickets now: prices go up at the stroke of midnight on Friday, March 18.
ImageX is proud to announce our continued support of the Drupal community with our participation at DrupalCon 2016 in New Orleans. ImageX will be a Gold sponsor of the event and can be found at Booth #207. We will also be one of the three key sponsors at the Higher Education Summit on Monday, May 9th.