All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
The ideas of Atomic Design and component based design allow one to create an established structure within which a large scale front end project can be built. The CMS space hasn’t always been the most friendly toward implementing these types of patterns. Whether it’s difficulty in creating a content architecture that models your front end design system within Drupal or the feeling of lack of control over generated markup, it can feel like an uphill battle.
The Paragraphs module gives us the tools to create much more well defined and structured component based architectures upon which modular front end systems can be built. The Paragraphs module, however, comes with no rules. As a site architect and front end developer, you must decide how to implement Paragraphs. There is definitely a lot of room for flexibility in implementation, but there are many best practices that can be followed to allow for a very clean, scalable, and extendable front end design system to be built within Drupal 8.
The goals of this session will be the following:
- Review the basic concepts and benefits of component based design
- Discuss the paragraphs module and how to create an implementation based on a well defined content architecture
- Explore some Drupal best practices that allow for a successful component based design system implementation
It's here! Lightning 2.2.1 provides a migration to the core media system that was introduced in Drupal 8.4.0.
This is a major milestone for us. One of the big advantages of using Lightning over vanilla Drupal or a roll-your-own solution is that as underlying modules evolve, Lightning maintains an update/migration path. This effectively creates a facade in front of media, workflow, and layout functionality. That functionality remains stable no matter what. Of course, this is in addition to the fact that Lightning provides all of that functionality out of the box. (Even though Media is now a part of core, it still doesn't provide the out of the box configuration, experience, and add-ons that Lightning does.)
Core Media migration was #2 in our list of major migrations. It was preceded by a migration from Layout Plugin to the core Layout Discovery module. Next up is Workflow which will involve migrating from Workbench Moderation to core's Workflows and Content Moderation modules.
Special thanks to phenaproxima who is at the intersection of the core, contrib, and Lightning work. To say the migration wouldn't have been possible without him is an understatement.Want to try it out?
Update your existing codebase:composer update acquia/lightning --with-dependencies composer update drupal/core
Then check out our 2.2.0 -> 2.2.1 update instructions.
Or build a fresh codebase:composer create-project acquia/lightning-project MY_PROJECT
Provides a field with quick links that can be added in the content listing for editors to edit the existing translations or add the missing ones.
Professional design is a half of website successful performance. Every text field, a button, and a picture should be placed purposefully.
We keep exploring Drupal contributions, and here’s the selection of free good-looking Drupal themes available for immediate usage. So download any and start working.
This module is to import taxonomy terms with hierarchical tree structure via csv file. Taxonomy terms can be imported with custom fields and in hierarchical tree structure.
tl;dr: Review the plan at the end directly.
Software has a changing nature; Drupal and its extensions are not the exception.
To be useful for a most of the users, those need to be on full releases, not only on the version control system; indeed the problem is not new and there is even a well-known phrase for one of its solutions: release early, release often
Therefore it is important to have a release plan.
Following after some context and reasoning, I propose a couple of practical guidelines on release schedule for contributed drupal extensions that I intend to use: release weekly until stable, then once a month following core shedule.
Software inherently tends to change, there are exceptions like embedded systems or really purpose-specific software.
Even really solid software like GNU core utils project, started on 1992, which provides tools that I consider among the most mature in the software space used daily, has 253 commits and three point releases in the last 12 months.
How much a software change depends on many factors.
I would hypothesize that the most relevant factors are the age of the project, the environment around it, and the amount of people behind it.
In this way, new projects change more than well established projects, and projects around dynamic environments which is also influenced by the amount of people around it, will also change more than the ones in environments with less participants or less technology changes.
Drupal contributed extensions are naturally mainly influenced by drupal core, so let us examine a bit how changing is Drupal core.
It is definitely on a dynamic environment, and I will argue that each major release can be considered a new project, making it really changing.
On the dynamic side, even if web standards changes slowly, and for good reasons, technologies around web tools are still constantly changing.
Drupal core project code history is now 17 years old, which seems like enough time to get into a stable state, especially if you are not yet part of the drupal community.
But the drupal project has a history on rewriting the way its internal works, which has been argued as one of the reasons why drupal can keep up with the changing environment around web technologies.
It may be also a consequence of its amazingly collaborative community.
And because of this rewriting between major versions, at least internally, each major release can be considered a new project, especially with 8.x.x.
A hint about it may be reflected in the fact that major contributors across different drupal core versions are mainly different; only a few one are as active across releases.
In consequence, drupal core is still a highly changing project, and in the same way its extensions inherit part of that changing nature; but a contributed drupal extension is not really only influenced by core.
Given the amazingly high number of written extensions, it is only natural to start depending on other software pieces and make its maintenance more effective.
For instance, currently there are 13432 and 4069, D7 and D8 compatible modules respectively.
In this way, one of the factors that will clearly influence a contributed extension is their dependencies, both inside and outside the drupal, and how changing they are.
Another factor is the amount of people behind it, not only developers, but also users reporting bugs.
For drupal contributed extensions this vary a lot, but it is usually not that big.
For all this, contributed drupal extensions are usually in a changing environment.Commits are not releases: release early, release often
As a contributed module developer myself, I will start by mea culpa.
Sometimes I wrongly assume that when a change is inside git the work is done, but that may be only true for people willing to take the extra effort to get the changes from git, or assume the consecuences of using a development release.
Commits are a developer tool inside the used version control system, but not necessarily something that is visible/usable for all.
As in many occasions, the problem is not new, and I find a pretty good answer for it on "The Cathedral and the Bazaar" chapter 2: Release early, release often.
It mainly propose that to be able to tackle enough bugs to make the software usable, the amount of releases needs to be as fast as the pace of the development, even at the cost of some stability.
I definitely recommend reading it fully for more context, and a lot more inspiring insights for any open source developer.
Granted, the answer is not a recipe, and it makes sense it is that way because it really depends on the project.
On the following lines I will propose an specific release strategy for drupal contributed extensions.
Drupal core already has a release plan, it is really detailed, so please review it if you have not done it yet.
Minor releases are approximately available every six months, but security and bugfix releases for a given minor version branch are available monthly, on third and first Wednesday respectively.
Security releases for drupal contributed extensions are published in coordination with the security team, so there is no need to plan them here, they also happen on Wednesdays.
Making it simple to remember can help maintainers stick to it, so I will also be using Wednesdays as well as the weekday for releases.The plan
I propose the following for each supported major branch in contributed extensions:
- release alpha/beta/rc weekly on Wednesdays, until a stable is ready
- release bugfix releases once stable has been reached in the same schedule than core, i.e. the first Wednesday of the month;
Looking back, it seems obvious and really simple, but if it is not documented somewhere, I will probably forget about it.
Hopefully someone else finds this useful, or even better wants to do the same.
Having a more predictable schedule always help to make better planning decisions.
I will start this week using this two guidelines and release a new version in the modules I maintain and there are pending changes to be released.Auto-notify maintainers
Notifications may help us maintainers to stick to this, but I guess the plan itself was relevant enough keep the focus of this post.
I may be exploring some solutions around it in the future.
 To reproduce statistics you can retrieve the main repository from https://git.savannah.gnu.org/cgit/coreutils.git and then run a couple of commands:
git log --oneline --all --since="1 year ago" | wc -l git log --oneline --all --since="1 year ago" --decorate | grep tag
The Calendar Links module provides calendar paths for the following:
- Google Calendar
- Yahoo! Calendar
Once installed you will need to have your module/theme use the paths or the included render element.Add To Calendar Dropdown
It includes an Add To Calendar Dropdown element. You can use the element by having your module/theme create a render element like this example:
Agiledrop.com Blog: AGILEDROP: Why should agencies partner with companies rather than hire freelancers?
Some users accidentally click the submit button more than once while waiting for their post to be saved. In some cases this may result duplicate postings or duplicate e-commerce orders.
There are few ideas on how to solve duplicate postings but none is perfect. One of the solutions is a bit of jQuery to hide or disable the submit button after it has been clicked and replace it with an informative text such as "Processing..." .
This module provides a default handler for contextual filters which allows the site administrator to set a title or a breadcrumb for a view based on a value defined by a contextual filter of this view.
Drupal Modules: The One Percent: Drupal Modules: The One Percent —Create user permission (video tutorial)
Here is where we seek to bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll consider Create user permission, a module which allows users to create other users without granting all the permissions administer users provides.
Creating a page template for a content type gives you a lot of control over the structure of the page. While Drupal will automatically pick up a node template for a content type, if you use the right naming convention, it will not for a page template. Fortunately it just takes a few lines of code and you can create a page template for any content type you choose.
Appends a global view header that creates a form in the view used to export data to spreadsheets. It requires PHPExcel library.
In my previous post I shared key takeaways from a Birds of a Feather (BoF) session I ran at DrupalCon Vienna last month on what it means to be an Agile agency.
Another BoF session I ran invited conference attendees to share their experiences of managing team members and ensuring technical excellence. We covered each topic in a lot of depth, and at times it felt a bit like a counselling session for new and aspiring tech leads!
Here’s a snapshot of what we discussed:Overcoming resistance to change.
The group debated how best to roll out changes within the tech team, such as changing version control software to git. Tech leads don’t always feel empowered to force through new initiatives, and can get frustrated by developers who either don’t want to change or are unable to see the benefits.
We spoke about the need to introduce change gradually and gain buy in through mechanisms such as team meetings, highlighting the importance of allowing changes to be discussed and concerns to be heard.
It can be helpful to identify evangelists in the team who will promote the change, and can act as support contacts during the period of transition so that no one suffers in silence.Leading change in remote teams.
Change is hard enough when you’re all in the office together – how do you ensure a smooth transition in co-located and distributed teams?
At Deeson, we’ve introduced a quarterly get together in person. We set up the changes the tech chapter plans to make over the next quarter, and assign owners to develop the ideas and facilitate the transition process.
We also run group workshops on the changes made during the last quarter, allowing people to gain hands on experience with a new tool or technique under the supervision of those that specified it and their evangelists. This allows us to identify any problems and concerns before the change is mandated.Dealing with complaints.
It’s natural and healthy to express concerns or frustrations. But what do you do when a team member seems to complain more than most?
As a manager you feel responsible for solving every issue that arises, and of course there are times when the onus will rightly fall on you.
However, in the case of a chronic complainer it can be more effective for you as tech lead to listen to the grievance and empower the person to consider their options and suggest solutions, rather than exhaust yourself trying to solve the issue on their behalf.Transitioning to tech lead.
Often a developer progresses until they one day find themselves leading a tech team, without ever having received any formal leadership or management training. We spoke about the changes you need to make, and how to understand what’s expected of you in your new role.
We cited the book The Manager’s Path by tech lead turned CTO Camille Fournier as an excellent reference. The Lead Developer conference which takes place annually in London is another good resource. Talks are made available online and provide a lot of guidance to those new to the tech leadership position.
Here’s one of our favourites:
Want to work with the largest Acquia Certified team in Europe and one of the top 30 companies contributing to Drupal globally? We’re hiring.
Provides a mechanism to translate all occurrences of the same locale string.
This drupal 8 module converts internal links to ajax requests that return the rendered nodes. All attached JS and CSS of the requested nodes are also added and executed.
Allows Administrators to set permissions for moderation states within the group.