All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Before/After Field Formatter will provide a field formatter for image fields so that the images uploaded for an image field would be rendered as a Before and After Images.
Installation and Configuration
1. Download and Enable the module similar to other Drupal modules
2. Visit any Image fields in Display settings, you will be able to find the Before/After Field Formatter, Select this one and you would be able to select image styles and another config.
Drupal Developer Days Lisbon was valuable, nicely organized, and full of energy. Two Axelerant team members attended to contribute a workshop and a session on two key topics, and they wanted to share key highlights with you, to thank the volunteers, and to encourage more developers from around the world to make it in 2019.
Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.Announcements Last chance to vote in the Drupal Association board election
Elections for the Drupal Association board end on July 13th, 2018 at 5pm Pacific (in just over an hour at the time this is posted). There are nine candidates from 7 countries across six continents representing a wide variety of perspectives from the Drupal community. Anyone user who has been active in the last year and registered before the elections began is welcome to cast a ballot.
We encourage you to vote today and help guide the future of the Drupal Association.Reminder: Drupal Europe is coming up soon
Drupal Europe is coming up in less than 60 days! Drupal Europe will be the largest gathering of the Drupal community in Europe and is a reimagining of this important community event as both technical conference and family reunion. The Drupal Association engineering team will be attending to connect with the community, provide updates on Drupal.org, and listen to some of the incredible speakers who will be in attendance.
Join the community in Darmstadt, Germany from September 10-14, 2018. Make sure to register, book your travel, and secure accommodation: http://drupaleurope.org/Project maintainers: Change your git remote configuration
Git authentication methods for Drupal.org hosted projects are changing as we approach upgrading our developer tooling stack. In particular we will be:
Deprecating password authentication for git
Deprecating the git remote format <username>@git.drupal.org/project/<yourproject>.git in favor of firstname.lastname@example.org:project/<yourproject>.git
We have updated the version control instructions for Drupal.org projects, and put a message in the git daemon for any user who makes a push using the deprecated format.
For more information, please review: https://drupal.org/gitauthDrupal.org Updates Ecommerce industry page launched
Since last year, one of our ongoing initiatives has been to develop more content on Drupal.org focused on specific industries. Drupal is an incredible powerful tool for building ambitious digital experiences, but it's flexibility can sometimes be overwhelming. These industry specific pages help Drupal evaluators discover how Drupal can be tailored for their specific needs, and highlight successful case studies of Drupal in the wild.
For every new Drupal project that a developer or site-builder undertakes, time is spent evaluating distributions, modules, and themes to find integrations that will accelerate launching the project.
To improve the user experience for users evaluating modules on Drupal.org, we've implemented a new lightbox-style display for project screenshots.
Here's an example of a screenshot from the Token project:Granted more maintainers the ability to give contribution credit
Since the introduction of contribution credits at the end of 2015, they've become an important part of the way the Drupal community recognizes individual and organizational contributions to the project. The Drupal Association Engineering team regularly reviews the contribution credit system to make small tweaks and adjustments to make the experience even better.
For our most recent update, Drupal.org now grants all project maintainers with the 'maintain issues' permission the ability to grant contribution credit, instead of just those users with 'Write to Version Control' permissions. This means that a much wider group of maintainers can now participate in granting credit.Showing maintainer photos on top level Docs guides
Documentation is critically important to the Drupal project To make it easier for potential contributors to find out who they should reach out to for issues that affect the top levels of documentation, we've added maintainer information to the top level documentation guides.Email confirmation when creating an organization node
To help more organizations that work with Drupal join our community, we now send an email confirmation to any user who creates an organization profile with information about becoming listed as a service provider, details about the contribution credit system, and information about becoming a Drupal Association member or supporting partner.
We encourage everyone in the Drupal community to ask your clients to create a Drupal.org organization profile. Bringing end-users into the contribution journey will be a key part of Drupal's long term health and success.Contributing to the Open Demographics Initiative
One of our goals on the Drupal Association engineering team is to adopt the Open Demographics Initiative in our user registration process. As part of our effort to work towards that goal, we have contributed a machine readable version of the demographic questions and and answers to the ODI project.
We're hopeful that can be reviewed and committed soon, and be used as the basis for an ODI Drupal module.Security Improvements Added PSA and SAs to the /news feed
One of the most important services the Drupal Association provides for the project is DrupalCI, the suite of tools used to test all of Drupal's code. These tools are very powerful, but also expensive to maintain, and something we have to monitor carefully. In June, we spent some time automating disk space management for the DrupalCI dispatcher, to help reduce the maintenance cost of keeping it running smoothly.
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who make it possible for us to work on these projects. In particular we want to thank:
- OPIN - Renewing Signature Supporting Partner
- Srijan - Renewing Signature Supporting Partner
- Lullabot - Renewing Premium Supporting Partner
- Aten - Renewing Premium Supporting Partner
- Phase2 - Renewing Premium Supporting Partner
- WebEnertia - *NEW* Premium Supporting Partner
- Pantheon - Renewing Premium Hosting Supporter
- Datadog - Renewing Premium Technology Supporter
- Promet Source - Renewing Classic Supporting Partner
- Evolving Web - Renewing Classic Supporting Partner
- ImageX - Renewing Classic Supporting Partner
- Adapt - Renewing Classic Supporting Partner
- Green Geeks - Renewing Hosting Supporter
- Microserve - Renewing Classic Supporting Partner
- ThinkShout - Renewing Classic Supporting Partner
- Amazee Labs - Renewing Classic Supporting Partner
- Four Kitchens - Renewing Classic Supporting Partner
- Access - Renewing Classic Supporting Partner
- Appnovation - Renewing Classic Supporting Partner
- Studio Present - Renewing Classic Supporting Partner
- undpaul - Renewing Classic Supporting Partner
- Position2 - Renewing Classic Supporting Partner
- Blend Interactive - Renewing Classic Supporting Partner
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.
As you may have figured out by now, Drupal is a great platform for 3rd party integrations. Whether it’s eSignatures with Hellosign, more sophisticated search with Solr, or a host of other options, Drupal works best when it’s not trying to reinvent every wheel and is instead used to leverage existing business tools by tying them all together into a robust and useful package. Today, we’re going to take a look at a new set of integration modules that Ashday has just contributed back to the Drupal community: Omeda, Omeda Subscriptions and Omeda Customers.
Take this survey to help us make Drupal the best platform for content editors and managers to use everyday.
Help us modernize the admin UI of Drupal.
Do you use Drupal? Before working at Palantir, I used Drupal only once: to help a legacy client with their Drupal 6 website. They had a support contract with my company, so if they had an issue or question I would do my best to help them, even though the original team who built the site had moved on to other jobs, and even though my company focused on WordPress sites.
I remember scrutinizing every menu item of the admin section, trying to familiarize myself with the platform while careful not to misclick and mess up something on the client’s site. Some of the terms I could understand—users, taxonomy—but some were new or vague, and not very clear to their meaning such as nodes, views, and blocks. While I was able to help the client at the time, I felt Drupal was too obtuse of a platform for me.Redesign planned for Drupal
Now that I’m at Palantir, and knowing Drupal is a bigger part of my job, I’m still struck by how user unfriendly the platform can be out-of-the box, especially to a non-developer. While add-on modules like Workbench and Content Moderation can mitigate some of this complexity, installing and configuring those requires specialized knowledge. From talking to current clients, I know that I’m not the only one who feels intimidated by Drupal’s default administrative interface.
The Drupal community is also aware of the high learning curve to Drupal, and is in the process of modernizing the look and feel of the admin experience to make it more intuitive. Given how big the changes are, it’s the perfect time to include the people who work with Drupal every day to make sure Drupal is a system everyone feels comfortable using.
Therefore, I am working with fellow Palantir web strategist Michelle Jackson, Drupal front-end designer Cristina Chumillas, co-founder and front-end lead at Evolving Web Suzanne Dergacheva, project manager Antonella Severo, design consultant Roy Scholten, folks from the Drupal Association and other interested volunteers to conduct research on popular content management systems and web platforms such as Drupal, WordPress, Squarespace, and Joomla in order to learn how best to update Drupal.Here’s where you come in
We want to make Drupal the best platform for content editors and managers to use everyday. Therefore, if your job involves updating the company blog, swapping out images, tagging content to group related information, or some other way you interact with your website, we want to hear from you.
We put together a quick, 5-10 minute survey that asks about your general familiarity with Drupal. For example, we want to know common tasks you perform on the platform as well as frustrating pain points. This way we can target our redesign efforts to make Drupal work better for you.
In addition to the opportunity to shape the future of Drupal, at the end of the survey you’ll have the opportunity to enter into a drawing for two great prizes: 1 full conference ticket to the (new) DrupalCon Content Marketing track at DrupalCon Seattle 2019 - $695 value (flight and hotel not included), or 1 two-day, online Drupal 8 training session from fellow Drupal agency Evolving Web.Take the Survey So what happens next?
This survey is step one of our research efforts. After reviewing the common tasks, we’ll ask folks who had provided their email address if they are willing to participate in card sort exercises to determine the best label for grouping common tasks together. Next we’ll design solutions to address the biggest pain points and ask participants to validate our assumptions through usability tests.
Looking at the long term, we are interested in comparing Drupal with other popular systems such as WordPress and Squarespace. We plan to reach out to people who use those platforms to find out what they find easy or difficult about them, which may inform the direction of the Drupal redesign. No matter which direction our research takes, we want to ensure we’re building a product with you, the content editor, in mind.More ways to help
It shouldn’t take specialized knowledge to update and maintain a website on Drupal. With your help, we can make Drupal a more approachable platform for content editors. I can’t wait to hear from you!Community Drupal People
This module is simply a bundle of many modules that integrate the various BYU web components into a paragraph. So far, it includes paragraphs for the BYU hero banners, BYU cards, BYU feature cards, and BYU calendars.
This blog has been re-posted and edited with permission from Dries Buytaert's blog. Please leave your comments on the original post.
If you've ever watched a Drupal Camp video to learn a new Drupal skill, technique or hack, you most likely have Kevin Thull to thank. To date, Kevin has traveled to more than 30 Drupal Camps, recorded more than 1,000 presentations, and has shared them all on YouTube for thousands of people to watch. By recording and posting hundreds of Drupal Camp presentations online, Kevin has has spread knowledge, awareness and a broader understanding of the Drupal project.
I recently attended a conference in Chicago, Kevin's hometown. I had the chance to meet with him, and to learn more about the evolution of his Drupal contributions. I was struck by his story, and decided to write it up on my blog, as I believe it could inspire others around the world.
Kevin began recording sessions during the first community events he helped organize: DrupalCamp Fox Valley in 2013 and MidCamp in 2014. At first, recording and publishing Drupal Camp sessions was an arduous process; Kevin had to oversee dozens of laptops, converters, splitters, camcorders, and trips to Fedex.
After these initial attempts, Kevin sought a different approach for recording sessions. He ended up developing a recording kit, which is a bundle of the equipment and technology needed to record a presentation. After researching various options, he discovered a lightweight, low cost and foolproof solution. Kevin continued to improve this process after he tweeted that if you sponsored his travel, he would record Drupal Camp sessions. It's no surprise that numerous camps took Kevin up on his offer. With more road experience, Kevin has consolidated the recording kits to include just a screen recorder, audio recorder and corresponding cables. With this approach, the kit records a compressed mp4 file that can be uploaded directly to YouTube. In fact, Kevin often finishes uploading all presentation videos to YouTube before the camp is over!
This is one of Kevin Thull's recording kits used to record hundreds of Drupal presentations around the world. Each kit runs at about $450 on Amazon.
Most recently, Kevin has been buying and building more recording kits thanks to financial contributions from various Drupal Camps. He has started to send recording kits and documentation around the world for local camp organizers to use. Not only has Kevin recorded hundreds of sessions himself, he is now sharing his expertise and teaching others how to record and share sessions.
What is exciting about Kevin's contribution is that it reinforces what originally attracted him to Drupal. Kevin ultimately chose to work with Drupal after watching online video tutorials and listening to podcasts created by the community. Today, a majority of people prefer to learn development through video tutorials. I can only imagine how many people have joined and started to contribute to Drupal after they have watched one of the many videos that Kevin has helped to publish.
Kevin's story is a great example of how everyone in the Drupal community has something to contribute, and how contributing back to the Drupal project is not exclusive to code.
This year, the Drupal community celebrated Kevin by honoring him with the 2018 Aaron Winborn Award. The Aaron Winborn award is presented annually to an individual who demonstrates personal integrity, kindness, and above-and-beyond commitment to the Drupal community. It's named after a long-time Drupal contributor Aaron Winborn, who lost his battle with Amyotrophic lateral sclerosis (ALS) in early 2015. Congratulations Kevin, and thank you for your incredible contribution to the Drupal community!
I'm currently serving as one of two community elected At-Large Directors on the board of the Drupal Association. The D.A. supports Drupal in a variety of ways, including maintaining drupal.org, running DrupalCon, and marketing Drupal to foster its adoption and community growth. If you use Drupal at all, you benefit from the work of the Association staff, and I couldn't be prouder of the work they're doing. The team really is incredible, and it's been a pleasure to get to know them more this past year.
Serving on the board has also given me the opportunity to get to know the other board members, including the At-Large Director elected before me, Shyamala Rajaram. She has focused on helping the D.A. board and staff consider how to foster adoption and growth around the world, including in her home country of India where she is a Drupal agency leader and community organizer. Not only has she brought a unique perspective to these conversations at the board level, but she contributes with a humble, generous spirit that has led and served us well. Thank you, Shyamala!
Her term on the board is expiring, and the Drupal community is currently engaged in electing her replacement from a very qualified list of candidates. The D.A. is a key part of the Drupal ecosystem, and each member of the board has the ability to influence how it uses its websites, events, and marketing programs to support the project and foster its growth. Its influence is often indirect, but it is no doubt consequential.
Today is the last day to do vote! Anyone who has used their drupal.org user account in the last year is eligible, and I encourage you to vote. Once you've reviewed the candidates, click the bright green "Vote now!" button in the top right hand of the election homepage. You can rank your choices in order of priority (1st, 2nd, 3rd, etc.), but you can also just pick one person as your 1st choice if that's all the time you have.
If you do vote, thanks for your contribution!
The STRAW module creates a form field widget to allow seeing the full heirarchy of a taxonomy term reference field as well as being able to create new ones dynamically.
One of the reasons why I’ve chosen to run for a position on the Drupal Association Board of Directors is because I’ve noticed that small-to-medium-sized agencies would like to contribute more to Drupal’s strategic direction. These businesses have played a huge role in building Drupal’s code, community and success over the years, and I believe they’re also a key component of its long-term sustainability. Companies with 25 or fewer people registered on Drupal.org make up the majority of those listed in Drupal’s Marketplace. It’s not a comprehensive survey, but it suggests that smaller agencies are the backbone of the community.
I’m an owner and co-founder of an 11-year-old agency that employs just over a dozen team members. We have a diverse client stable that includes non-profits, government departments, universities and businesses of varying sizes. Their project budgets range from $5,000 to $500,000, so it’s important to us—and many others like us—that Drupal continues being able to offer powerful and complex functionality for a wide price range.
I’ve heard the conversations about how Drupal 8 has made it more challenging to work with a smaller team and more expensive to build sites and applications. I’ve seen its relatively sluggish adoption statistics. I’ve watched with interest as Backdrop works on advancing a Drupal fork that doesn’t leave the needs of the smaller agencies behind. I sense that we’re at a watershed moment when these businesses need a strong voice at the table.
Small shops have unique strengths to offer clients: they’re often flexible, speedy, local and personal, with strong customer support. One way the Drupal Association could give a boost to these agencies would be by developing more guidelines and models for Drupal Business Summits. Aimed at helping prospective end-users decide whether Drupal could help meet their needs, these events have the potential to drive Drupal’s growth in new regions. Smaller agencies, often located in places with under-tapped markets, are perfectly positioned to lead the charge.
Getting elected to the Drupal Association Board of Directors would give me the opportunity to share my experience and expertise as a small-business owner. I invite you to make your own voice heard as well, by voting in this important election. (Voting ends today: July 13, 2018).+ more awesome articles by Evolving Web
Affiliates Connect Ebay is the Plugin to the Affiliates Connect Module. It provides the functionality to integrate the Product Advertising API of the Ebay so that the products from the Ebay can be imported to Drupal.
The LeadSquared Integration module is a basic CRM integration to Drupal form.Uses
It helps integrate Drupal form with LeadSquared CRM to capture lead. Mainly focuses on Drupal form i.e leads are captured during :
- Form Submit
- After Publishing/Payment/Update of content
There is a new Birdman in the town! An idea that has gripped the biggest institutions in the market. A technology, that enthusiasts believe, could change the world. "A truly extraordinary invention that does really mundane things", as told by Paul Brody, E&Y Global blockchain leader. Some see it go much further than the effect on "big stock trades". Further into cracking down on music piracy, child labor and a lot of other things around the world. Yes, I'm definitely talkng about Blockchain Technology. The idea that Drupal and Blockchain can work together to create a secure decentralized architecture is quite fascinating
Web Content Accessibility Guidelines (WCAG 2.1) extends WCAG 2.0 and is intended as an interim until WCAG 3.0 is released. The new guidelines were needed due to advancements in technology and to fix some gaps and shortcomings in the earlier guidelines. Some of the new guidelines cover touch/mobile devices, speech control, and cognitive disability support.
This module allows site builders to add CSS through the admin dashboard.
This year’s Drupal Dev Days took place in sunny (well, for the most part) Lisbon, Portugal. Over 400 people attended this year’s Dev Days, and I was one of them. I am fairly new to Drupal, and this was my first conference dedicated to Drupal. This was a week-long event, something that was unusual to me as I am used to attending one or two-day events.Vijay Dubb Fri, 07/13/2018 - 14:26 Day one
Day one was all about Contribution at ISCTE. Let’s just say my first day didn’t get off to a great start. It took me over 30 minutes to find the entrance to the University, where the event was taking place, and I wasn’t the only one.
It also didn’t help that it was raining, but luckily I had my umbrella (being British I never leave the house without it). Once I found the place, I realised I’d left my adapter at home, so I headed out to get one. Luckily, there was a shop nearby. Along with my purchase, I headed back to help with contributing to some of the Drupal innanatives.
There, I met Ruben Teijeiro, who introduced me to several people and how to get started. I really wanted to contribute to the Frontend space, especially to the new admin UI. Setting up wasn’t the easiest (which I expected), as I use Windows for all my development. There I also met Christophe Jossart, a long time contributor to Drupal, who tried to help me with setting up the site on my machine, but to no avail.
By the end of the day with the help of installing WSL on my machine, I had managed to install the site, get it up and running, only then to be served with several errors, by which time I had called it a day. It might sound like all doom and gloom, but I made a lot of progress made throughout the day.Day two Friction
The first keynote session of the week was given by Bojan Zivanovic. He spoke about the evolution of Drupal (version 7 to 8) and how Drupal has made several changes to Core using modern practices, making it a much better framework.
One interesting part was the adaption of Drupal 8, which was a plus (40%), and the loss of Drupal 7 sites (11%), however, by putting them together Drupal actually lost over 35,000 sites in the last year. There were several reasons as to why this could be the case, including time spent installing Drupal and setting up the development environment, especially for those on Windows (like me :sigh:). It all relies on the community to help and improve what is already there, to make it easier for both new and current users.
“Sometimes our Drupal websites end up looking like this.” - Bojan Zivanovic (in reference to the above image).
Another session I attended was a comparison of the top GDPR modules and how you can make your Drupal site GDPR compliant.
The talk covered many aspects - from rights of the user to form checking and security. It was apparent that there are several modules that help do this, so having a short list of the best ones made it easier. It also became apparent that to become compliant, you require more than one module.
One thing that came out of this session, which I totally agree with, was that site security was often neglected in the past but is now at the forefront of all sites.
This session, given by Chandeep Khosa, was the last one I attended and was the highlight of the day for me. Adding features to the Drupal like Admin Toolbar, like a theme module to make it look nice, or even add help text, may sound rudimentary, but how many actually do so and make use of it? (No, really?) Most content editors are not used to the Drupal admin like developers are, so it was nice to hear what we can do to make it easier for them.
One specific module I found very interesting was the tour module, which provides guided tours of the site interface via tooltips, something available in core today. I didn’t even know this existed. One thing I took away from this was that if you don’t need it, hide it, why show something to users that don’t get used?
Part 2 of my Drupal Dev Days Lisbon 2018 Recap will follow soon. Thanks for reading.
Module allow quick and easy insert CSS/JS code and files to Drupal. Library Select allow you create a field in your content type and Editor can easy select predefined CSS/JS Code.
This module borrow some code of module Asset Injector