All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Violinist.io is a new service that is continuously trying to update your composer dependencies. When a new update is found, a pull request is created on the github repo for the project in question, for example your Drupal site. If you have a good testing setup, this will trigger your tests, and hopefully pass. Now, if you have continuous deployment set up, you can basically merge and deploy updates while sitting in a coffee shop on your phone. Which is now something I have done several times!
I am planning to write a longer blog post about a more complete continuous deployment setup, but just wanted to share a couple of quick fun animated gifs about how Violinist.io works
A couple of weeks ago a new version of Drupal console came out. After it was tagged on Github, an update was available through composer. Since Violinist picked this up, it opened up a new pull request on all of my projects that depend on this. That looks something like this:
I captured this animation because I was fascinated about the short time window between the release and the pull request. As you can see in the animation, it was only around 10 minutes! Now all left for me was to see that the tests passed, read through the changelog (including links to all commits) and merge in the update. Minutes after it was automatically deployed to the production server. About as easy as it gets!
But it's not only other Github hosted projects, or generic php packages that gets updated. For a typical Drupal project I also depend on modules from Drupal.org, and I download these modules with composer. Violinist.io supports those as well. Here is one example (from this very site you are reading) where a new pull request with a full changelog was posted only 8 minutes after it was released on Drupal.org.
Since admin_toolbar is a module I use on many projects, I now could just navigate from pull request to pull request, and update all of my sites within minutes, while still on my phone. A real time saver!
Full disclosure: As you probably understand from the enthusiastic description, I am also the creator of the service. It is completely free for open source projects, and up to one private project. Feel free to reach out if you have any questions or comments! To finish it off, here is an animated gif about enthusiasm.
Thank you to the 1,670 people who joined us at DrupalCon Vienna!
So many volunteers! So many sandwiches! We had a wonderful time in Vienna and can't wait to see you all for DrupalCon Europe 2019.
Until then - we hope to see you in Nashville 2018.
David Rogers, Senior Front End Engineer at Pendo.io, joins Mike Anello to discuss from a Drupal-specific standpoint. They discuss the road to the Drupal community selecting React for use in Drupal core, when a typical Drupal developer should start thinking about React, and what the best first steps are for learning it.Interview
- Drupal looking to adopt React.
- Proposal to use React for building Drupal’s administrative UIs.
- Medium post on the original React license.
- Official Documentation.
- How to Learn React - A Five Step Plan blog post from Lullabot.
- Learn React.js in 8 minutes.
- Codeschool Try React course.
- Mastering Drupal Development Workflows with Pantheon - begins February 27, 2018.
- MyDropWizard.com - Long-term-support services for Drupal 6, 7, and 8 sites.
- WebEnabled.com - devPanel.
If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.
This is part two of our series processing the results of the Amazee Agile Agency Survey. In Part 1, I provided an overview of initial observations from survey results. Here, in Part 2 I would like to focus on process insights.Josef Dabernig Mon, 11/27/2017 - 10:11
In Part 1, we identified Scrum as the most important process for Drupal agencies. Kanban was stated as “somewhat in use” for the most part and also had various agencies stating it as “mostly in use”.
We also asked about “Other important processes?”. From the results, respondents mentioned “Critique, automated testing, collaborative sketching”, such as GitLab workflow, DSDM, Holacracy, Extreme Programming (XP), and Agency Agile.
When asked about how strictly the process would be implemented, the top rated option by 36.7% (on a scale from 1-5) was a “4”, which indicates these agency processes are followed rather strictly. Following this is a “3”, which indicates a balance between strict adherence and many adaptations, and a “2”, which refers to rather many adaptations. Fewer agencies still indicated an even split between either very strictly follow processes and implementing many adaptations to processes.
When asked for which adaptations were applied to their processes, agencies mentioned the following:
- Custom dashboards
- Backlog organization of “in scope” versus “out of scope”
- As scrum is all about inspect and adapt, the result will always look differently
- Scrum gets adapted to different customer needs or other stakeholders in the company asking for it
- Often clients expect fixed price offers with a fixed scope and fixed deadline, results is trying to be agile within those borders
- The best process is invisible and will feel natural once you found the best way, process needs to match individuals needs
From our experience at Amazee, I’d say we tend towards a “4” where we try to follow Scrum strictly but we also don’t want to overdo it. As mentioned in the comments, Scrum is really about the team taking ownership of the process, which requires flexibility. We constantly try to adapt our processes where we feel it helps fulfill our mission to deliver great software to our clients.
How do you structure your processes and what works best for you? Feel free to leave us a comment below. If you are interested in an Agile or Scrum training for yourself or your company, contact us.
Stay tuned for next post where we’ll look at teams: sizes, location, and team assignments.
The Content cancel button module provides a cancel button on node forms.
* Install as you would normally install a contributed Drupal module. Visit:
for further information.
Number to Format aims at creating a formatter for numbers, which prints inputted numbers as words.
It uses The PEAR Numbers_Words package. (https://github.com/pear/Numbers_Words)
For now, it works only as a currency formatter specifically.
This is the field formatter:
And these are the possible settings:
Drupal module that extends functionality of commerce 2.0 tax types.
Adds a new tax type plugin called "Custom Plus" as well as a new checkout pane plugin called "Payment Info Plus".
The Custom Plus tax type plugin allows for added options to limit by city and by county in this new tax type.
The Payment Info Plus checkout pane plugin
Read more »
This module provides a Word encoder for the Drupal 8 Serialization API. This
enables the DOCX format to be used for data output (and potentially input,
eventually). For example:
- Views can output DOCX data via a 'Word Export' display in a View.
- Module developers can leverage DOCX as a format when using the
The Leading Zeros Field Formatter extends the Integer Formatter to add leading zeros to integer fields. Settings for Thousand marker and Prefix / Suffix can also be configured. This may be useful for printing product ids, serial numbers or similar that need to conform to a certain pattern in display.Requirements
This module requires no additional contrib modules, just the core field module, and an integer field.
Provides a field formatter for syntax highlighted code output. It is designed to be simple and not rely on any third-party library (best feature: no third-party dependency to GeShi filter etc.). The syntax highlighting is made by PHP's in-built highlight_string(); function.
Sends a simple notification eMail to the site administrator, if an new comment has been created on the website. Also the eMail sending will be logged and can be checked at /admin/reports/dblog.
The eMail contains the link to un-approved comments and the approved comments on the website. This module does not have any user interface and own configuration options. It is designed to be simple and fit into small business purpose.
If you need more functionality: This module's codebase is minimal and you can use it as an example for your own module.
The Check DNS module simply prevents user registration with invalid email domain on user registration form.
This module enables an additional processor where you may add a prefix or suffix to the facet result item.
This prefix/suffix can be set per facet with the following two options:
This module gathers and reports on user/admin feedback for all pages.
You will need to create a Qualtrics account to make use of this module.