All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Sprint Date: January 11 & 12, 2018
I knew it was going to be a good few days of sprinting when the first of our team (Vicki Spagnolo) pinged the group in IRC saying she was getting started. You see, this was a virtual sprint and Vicki, being in New Zealand, starts well before the rest of us. The excitement she had going into the sprint was contagious.
Bright and early, we had our first stand-up call on Google Hangouts. We discussed all of the tasks for the next few days and dove right into working on code. A lot of the benefit of a sprint is having others around with focus to review code, so we did a lot of reviews of each other's work. Lots of issues made it from “Needs Review” to “Reviewed and Tested by the Community” (RTBC), and we had several Core committers hanging out to assist us. Special thanks to Gabor Hojtsoy, Lee Rowlands and Jess Myrbo for all their commits over the 2 day sprint.
Some progress stats. We went into the sprint with 3 Core migrate modules that weren't marked as stable. The Migrate API module went stable during the sprint. The Migrate Drupal User Interface module had one blocking issues resolved, leaving a single blocker remaining (UPDATE: this has been resolved, too). Finally, the big one, the Migrate Drupal module itself has only a few limited blockers remaining, all related to i18n/multilingual use cases.
A great benefit of sprinting with a group is that we had people available who can provide guidance and direction on architecture. With the group, we landed on a good plan of action for all the remaining i18n/multilingual issues. We opened the sprint and saw significant progress on the first step in that plan. It isn't RTBC yet, but it should go soon. After which, we have to leverage the building blocks it provides for the remaining i18n/multilingual issues.
Yes, it's down to just a few issues. Once they are wrapped up (and we saw great progress, so I'm hoping soon), all of Migrate Drupal will go stable. I also expect that the Migrate Drupal UI module will go stable at the same time.Summary:
- 5 Critical blockers across the entire Migrate sub-system.
- Migrate API module went stable! Only two more to go.
- 25 issues worked on; all with significant progress seen during the sprint.
- 15 commits, of which 10 were serious improvements in API documentation.
- Remaining release blockers can be found here. Filter issue priority to ‘critical’. Feel free to jump in and help!
A huge thanks to all the sprinter: GaborHojtsy (Gabor Hojtsy), heddn (Lucas Hedding), xjm (Jess Mybro), larowlan (Lee Rowlands), masipila (Markus Sipilä), maxocub (Maxime Turcotte), phenaproxima (Adam Hoenich), quietone (Vicki Spagnolo).
Do you have an ecommerce site that you want to migrate to Drupal 8, but not sure how? We can help! Contact us to discuss your migration with one of our experts, no strings attached.
If you're planning to use Bootstrap on your Drupal 8 site, the first obvious thing to do is download and set up the Bootstrap theme. Then, during the site building process, there will come the point where you need to create a few layouts. These layouts could be used for content types with Display Suite, or for custom pages using Panels.
Implementing layouts using the Bootstrap grid system is simple thanks to the Bootstrap Layouts module.
Bootstrap Layouts is a module that ships a bunch of prebuilt layouts using the grid system in Bootstrap. Best of all, these layouts can be used between Display Suite and Panels, or any module which supports the Layout Discovery module
The layouts are configurable through Drupal's administrative UI. For example, you can adjust the width of a two column layout by choosing grid CSS classes from a multi-select field.
This module provides integration with the crisp.chat live chat service and Drupal 7, so that if a user is logged in their username and email address are passed to crisp.chat. It is based on the OLark module
Panels-based plugin that wraps a Twig / REST JSON-schema-defined library of components.
This code will parse a pattern library (local or through REST endpoints) to generate a list of "content types" in panels that can be drag/dropped into panel variants.
If enabled, the configuration screen is simply an iframe wrapper of a simplified version of the PatternLab schema builder.
When pattern configurations are saved, the template is downloaded locally (to mitigate origin failures and lock in version at time of configuration.)
With this module, you can log in with OneLogin through SAML in Drupal 8. This module is a rebuild of https://github.com/onelogin/drupal-saml/tree/master/onelogin_saml, which is only available in Drupal 7. Because of this, I rebuilded it for Drupal 8.
More information will come at a later stage.
Before having a look at AngularJS’ components, terms and terminologies, let’s make sure everyone is on the same page. If not then you can go through our previous blogs “Introduction to AngularJs” and “…
Two weeks ago the first edition of the Drupal meetup 2018 (also my first ever) took place at our office. Besides discussing Drupal Community activities for 2018 in Switzerland, Amazee Group CTO and Partner, Michael Schmid gave a presentation on «The possible future of React, GraphQL, and Drupal».Vijay Dubb Tue, 01/30/2018 - 10:50
It was great to learn about how Amazee both tackled and created a decoupled Frontend and Backend Drupal site, and inspiring to have met so many great people from the Drupal community.Presentation Recap
Especially for someone like me, who is new to the Drupal world, the presentation gave some significant insight. Here's how it helped me to further develop my understanding of all things Drupal, React and GraphQL.GraphQL and Starwars
The first part was all about GraphQL and Star Wars, well, the Star Wars part was the API used for the demo. Having never used GraphQL much before, I appreciated the brief introduction to GraphQL and how much better it is to the regular rest API. You are welcome learn more about GraphQL from our blog posts.Frontend tools
The second part was about the Frontend tools used: React, Apollo, and Redux. I knew at least 40% of this section already, thus having experience in this area, helped me feel comfortable. By implementing further education into our average working day, Amazee Labs is looking to become one of the leading agencies using React and Drupal.It all comes together
After an introduction as to how both tools work separately, we now got to the most exciting part: understanding how both GraphQL and React work together with Drupal. During this section, I came to learn that there was an open source demo application that had been created by Amazee Labs. This got me excited, as it meant that I could not just use at Amazee Labs but am able to play with it in my own projects. Personally, I think it is pretty awesome when any company open sources everything, as it allows the community to both learn and contribute. Anyways, back to the point: is React and GraphQL with Drupal in a decoupled ecosystem the future? It for sure could be, what I know for sure, is that it is Amazee Labs’ future, and we are very excited about it.
If you would like to play around with the demo application, then feel free to clone the repository. Trust me you won’t be disappointed.
Also, feel free to watch the full presentation, including question and answers below.About the future
There were many suggestions after the presentation. Heres a summary of the most notable discussion points.Upcoming Meetups
A few meetups were arranged for the following dates.
- Tuesday 20th of February at Liip
- Wednesday 21st of March at Attribute
- Wednesday 25th of April at Unic
There was also a discussion regarding meetups in other locations within Switzerland. Car sharing was suggested, to make this a feasible possibility. Fun. Right?
The timing for the next meetup was another suggestion, where the Doors could open at 18:30 and the meetup start at 19:00.Other topics we discussed
- The next Drupal Mountain Camp
- Drupal Switzerland Association
Including new conference topics, collaborations, case studies, and even a suggestion to redesign the current Drupal Switzerland site. After everything considered, I believe that the near future for the Local Drupal Community looks bright.
Thank you to all who participated and attended our meetup.So what’s next?
I would like to nominate Kevin Thull (kthull on Drupal.org) for this year's Aaron Winborn Award.
If you have been to a Drupal camp in the last few years, you may have seen Kevin sprinting...
...Sprinting from session room to session room making sure the speaker hit the big red record button.
Kevin contributes to the Drupal community in a way that is different and unique, he helps record the sessions on video and posts them for free online. If you haven't been to one of these camps, I hope you have taken the opportunity to watch some of the over 500 session recordings that he has posted online for all of us to learn from and advance our careers.
You can find a majority of the videos linked here:
You can find a listing of the camps he has recorded here:
I first met Kevin in 2013 at the first Drupal Camp Fox Valley. A mutual friend asked if they could borrow a video camera as a backup to their session recording setup. Turns out, they didn't need it as Kevin had already started dialing in his system.
He has a great series of blog posts at his personal site documenting his recording kit at http://www.bluedropshop.com/