One of our OSTraining members asked us how to configure webforms with conditions and we prepared for you this tutorial to show you how you can do just that.
For this tutorial, you will need the following Drupal modules:
Once you downloaded the, please go to modules are make sure you have enabled them.
You should have the following module options ticked:
- Chaos tools
- Form builder
- Form builder Webform UI
- Options element
- Views UI.
Under Structure > Content types, you will see that you now have the 'Webform' content type. Review the default settings of this content type. I personally removed the "Published By" but this is my own personal preference.
Now that we have everything installed, let's start building our webform.
Go to Content > Add Content and select the Webform. We need to give this form a title and for ease of access I am also going to assign it a menu link.
Now, using the form builder GUI, you can easily drag and drop the configuration elements that we need for this webform.
I have created a feedback form that will be asking for Name, Email and to rate a service.
We want to set up a condition, which will then trigger a feedback textarea if 'Not Happy' option is selected. We want this textarea to display on the same page, so we will not use a page break for this form element.
As we now have configured our webform, let's make sure it works. While 'Very Happy' is set, you do not see the feedback textarea field:
If, however, you select 'Not happy option', to record a feedback from the user, then right away its corresponding textarea field will show up.
As you have now learned in this tutorials, using conditionals in Dripal, you can add many complex responses to your webforms, add some cool features to them and collect all the information you need.
Still have questions? Please submit them in the comments below.
A tutorial to show how you can use data volume restore for MySQL on Drupal Docker stacks to dramatically improve import performance with notes on how to integrate this with your development and continuous integration workflow. Continue reading…
We are excited to announce that the first three industry pages are now live on Drupal.org, highlighting the power of Drupal solutions in higher education, government and media/publishing. The pages are designed to quickly inform and inspire technical evaluators and connect them to service providers and technology vendors who can help them move further through their Drupal adoption journey.
The Drupal Association is incredibly proud to showcase the Drupal community’s innovation, creativity, and ability to solve end users’ challenging problems. More importantly, these pages are a resource that Drupal businesses can point to as they convince potential clients that Drupal is the right choice for them. We know this is a needed resource not only because Drupal agencies have asked for this, but because our user research was resoundingly positive. One government digital director said “I wish this was around when I was pitching my state CIO on Drupal”.
This launch is the first phase for this initiative. We will learn and iterate to keep improving the pages and we will expand the industries to include pages like healthcare, finance, ecommerce, and more.The Research We Used
Building the industry pages was a community effort. Drupal Association staff framed the concept and then reached out to end-users of Drupal in these industries, service providers who've built solutions for these markets, and the community at large. We listened to all of you who shared your thoughts in the original blog post about this initiative.
We conducted user research, interviewing decision makers and influencers at end user organizations to make sure the pages resonated strongly with them. We talked to organizations like Weather.com, Burda Media, State of North Carolina, Georgia Technology Authority, Duke University, Cornell University - and more!
We also talked to people at agencies who pitch Drupal solutions all day long such as Acquia, Ashday, Blackmesh, Digital Echidna, FFW, Forum One, ImageX Media, Kwall, Lingotek, Lullabot, Palantir.net, Pantheon, and Phase2.
We will continue to take feedback from our global community. Our goal is to keep iterating on these industry pages as we learn more.About The Pages
The industry pages are part of the About Drupal section and they are promoted from the Drupal.org front page. The homepage of Drupal.org receives about 350,000 visits a month, and about 50% of those visitors are new to Drupal.org The front page is primarily technical evaluators coming to learn more about Drupal and we see this as they click on our evaluator resources like About Drupal, TryDrupal, and Case Studies.
Based on user research, we know that before someone comes to the industry pages, they likely know that Drupal is an open source community-built CMS and their organization is leaning towards an open source solution. However, we did make sure the pages do not assume the visitor already knows what Drupal is, because some will find the page through search.
Another key feature is geo-targeting. Currently, we serve localized content for the Americas, EMEA, and AP/Australia/New Zealand regions. This allows us to showcase case studies that will resonate to visitors based on their location. For example, on the Americas page, we highlight the Department of Energy - a U.S federal agency. In EMEA, we highlight City of London - a UK city, and in AP/Australia/New Zealand we highlight the State Revenue Office of Victoria, Australia - a federal agency. We took this approach because business owners at digital agencies from each region said that having localized brand names and case studies helps them convince their potential clients that Drupal is a viable option for them.The Story We Are Telling
The story that the pages tell to visitors is:
Drupal is the open source CMS of choice for this industry. Just look at the strong adoption rate, industry brand names, and their success stories.
Build amazing Drupal solutions to solve problems related to your industry.
Solutions are made up of Drupal and third party software and hosting solutions. Plus, you can use industry-specific distributions to accelerate your build.
Because of Drupal’s extensibility and our robust ecosystem of third-party technology integrations, modules, Drupal hosting, and distributions, you can tailor a solution to solve your unique problems or create new opportunities. Check out some featured industry-specific vendors.
Read case studies to learn how big names in your industry achieved business gains with a Drupal solution.
These solutions were built by people at well-respected Drupal agencies who are top contributors to Drupal.
If you want to talk to someone about creating a Drupal solution, fill out the form and all three will contact you.
Want to meet your peers? Attend the industry summit at DrupalCon Baltimore.
For the Americas region we have secured partners for Drupal evaluators to reach out to discuss their industry needs. However, we have not yet secured agency and vendor sponsors for these pages. It takes a lot of work to line up those relationships and tee-up the content and we wanted to launch sooner than later so we could start learning how to optimize the pages. So for now, we've selected initial case study content for these regions, and we are promoting a link to the marketplace to show agencies who have industry experience in these regions. Over time, we will open up the opportunity for agencies to sponsor the pages similar to our approach in the Americas region.Thank you to our sponsors
Contribution comes in three forms: Time, Talent, and Treasure. Many people shared their time and talent to help us create these pages for the community. We could not have built something of value without them. And, there were several companies who contributed treasure as well by investing financially to sponsor these pages. Those companies are: Acquia, Ashday, Blackmesh, Digital Echidna, FFW, Forum One, ImageX Media, Kwall, Lingotek, Lullabot, Palantir.net, Pantheon, and Phase2.
Because the industry pages give premier visibility and sponsorship is so limited, we wanted to be as fair as possible when opening up this sponsorship opportunity. As we say amongst staff, we want to “sell with a soul”. We decided to only sell these sponsorship opportunities to those who are top contributors. We looked at companies’ code contribution levels and how long they supported the Drupal Association financially and came up with an internal ranking system. Only those above a certain threshold were invited to sponsor.
This means that not only are these sponsors contributing time, talent, and treasure to this specific initiative, but they are long time contributors to the Project, helping Drupal thrive over time. It’s important to the Association that we highlight and reward good Drupal citizenship. When good Drupal citizens are doing well, we all do well. When successful, businesses can hire more Drupal talent and sponsor their contributions back to the Project. They can fund more camps and DrupalCon so we can unite and accelerate the Project in person, and they can fund Drupal.org hosting and engineers so the community can build the Project together online. We are thankful for our sponsors' generous giving and proud to work with them on this initiative.We've created value together
We see this initiative as a great demonstration of serving our mission - “to unite the community to help them build and promote the software”. We united members from all facets of the community: end-users, service providers, and the community at large. The pages promote the software by showing that Drupal is a winning choice for evaluators in these key industries.
This project is a reflection of Drupal’s amazing spirit and culture of respecting diverse opinions, collaboration, and striving to do the best. Thank you to everyone involved in this project for working so well together, listening to each other’s different ideas, and finding ways to incorporate them so together we can build something amazing.
Read more »
Florida Drupalcamp 2017 is less than a week away, February 17-19, in vibrant Orlando. Not only is the camp schedule packed with great sessions and trainings, but there's also a contribution sprint that both helps Drupal 8 core maintainers, and gives you a chance to contribute and learn about Drupal 8.
To join the sprint, you should already be familiar with Drupal... and that's it! You don't need to be an expert. You don't need to be a coder. You don't even need to know much about Drupal 8, although a little knowledge helps. This particular sprint is a great fit for:
- anyone with some Drupal knowledge who is interested in contributing for the first time
- on-and-off contributors
- project managers (you will be great at this!)
- anyone interested in learning more about how Drupal core gets made
- anyone concerned about Drupal 8 bugs!
- anyone interested in helping maintainers (or even becoming maintainers someday themselves)
I'm not teasing with that last one, either. This sprint can be rewarding for anyone from a newbie contributor to a core committer. (If you are skeptical about that, join this beginner camp session from Drupal 8's frontend committer, Cottser: One Step at a Time: Lessons Learned from Drupal Newbie to Core Committer.)
If you can't make it to Florida, you can also host the same kind of sprint at your local Drupal camp. Read on for what this sprint is all about, and why it matters for Drupal 8.Getting our priorities in order
In Drupal core, we define the issue priority of core bugs based on how many users are affected and how severe the problem is, and many contributors respond accordingly to prioritize what is fixed first. Over time, we've refined what specific kinds of bugs are critical, major, or normal priority.
Before we released Drupal 8.0.0 in November 2015, we fixed all the critical bugs we could identify, so that Drupal was safe and production-ready for most users. Our intense focus on fixing those release-blocking issues for such a significant overhaul of Drupal meant that many issues that were not as critical took second place, even though some were still quite problematic. In the past year, now that Drupal 8 has stable releases, we have been able to shift focus to fixing more of the remaining major bugs (as well as adding new features).
Still, there are only so many hours in the day, and many people who've spent time with Drupal before will know how long it can take to find the right bug report! This is where issue triage comes in. The first step to fixing the most important bugs is simply making sure the bug reports are up to date and actionable.Major triage in 2016
During 2016, with the help of subsystem maintainers and a couple small groups of sprinters, we assessed the status of over 200 major bugs. Of the major bugs we triaged, only about half were confirmed as major priority. Roughly one in three were downgraded to normal priority, and one in twenty turned out to be critical priority. The remainder were no longer relevant.
Within the past year, the community also fixed over 250 additional major bugs... but more than 200 new ones were filed at the same time. So, while the triaged issues significantly reduce the size of the major issue queue, there is still much more work to be done to catch up. Core maintainers need your help to close the gap.How you can help
Finding (and fixing) the bugs that are most important is a group effort. We use a two-phase process:
- Contributors verify the current status of the major issues, make sure they are up to date, and close issues that are no longer relevant.
- Core committers and subsystem maintainers collaborate to assess the verified issues.
Phase 1 is where you come in! This flowchart illustrates the workflow we use at major issue triage sprints:
(You can also read the detailed instructions in the major triage meta issue.)
This process can take awhile, but it is great for "unsticking" issues. Plus, once you have triaged an issue as valid, core committers will follow up on it to confirm its priority and make sure you are credited for your triage contribution to the issue on Drupal.org once the bug is fixed.
Once the current state of these bug reports is verified, Drupal 8 core committers and subsystem maintainers will prioritize them, deciding which are indeed major, which are just normal bugs, and even which ones are critical issues in disguise.DrupalCamp NJ 2017
The next stop on the major triage international tour is Orlando! Come to the Florida DrupalCamp contribution sprints to join the experience. The main sprint day is Sunday, February 19. Start the weekend off with a training on Friday, attend some fabulous sessions on Saturday, and then come sprint on Sunday -- or, do what DrupalCamp veterans do and hang out sprinting for the whole camp. nerdstein and the amazing YesCT will be right there with you to help you sprint (probably along with other mentors as well). Also be sure to thank ultimike and other camp organizers for hosting the sprint.Or, organize your own sprint!
Do you have an upcoming local Drupal camp or regional summit? Are your superpowers more for organizing events than testing bugs? Consider hosting a Drupal 8 major issue triage sprint at your event.
To host the sprint, it works best to have a few sprint leads who are either experienced mentors or know Drupal 8, or who have attended another of our Drupal 8 major triage sprints themselves. (Past major triage sprints have been at DrupalCons Los Angeles, Barcelona, Mumbai, and New Orleans, as well as at this year's DrupalCamp New Jersey.)
If you are interested in hosting a core major triage sprint, contact me on Drupal.org. I can help you decide if the sprint is a good fit for your event and share ideas.
Let's shine the lights on some bugs!xjm Tue, 02/14/2017 - 22:35
Here is where we bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll look at Focal Point, a module which allows you to set how images are cropped on a node by node basis.
Neil Drumm (drumm) and I have been working lately on the API module (used to build API documnentation sites like https://api.drupal.org and others). We've made a 7.x-2.x branch of the project, which works quite differently from the 7.x-1.x branch. The major changes are that it uses a different (and external) parsing library for parsing PHP files, and it uses Composer to manage its external library dependencies.
We have a bunch of automated tests for the module, which all pass, and I've successfully used it to parse the latest 8.x and 7.x Drupal Core code. But there are several other users of the API module out there (for instance, the Drush project), and we've changed the public API of the module (functions have moved, changed names, been removed, etc.).
So before we make a full 7.x-2.0 release of the API module (and drop support for the 7.x-1.x branch), I would like to invite users of the API module to test out the 2.x branch on their sites, and create issues in the API project if they encounter any problems. The public API can still be changed at this point, up until we have a new release, so now would be a good time to test.
If you want to test... some links:
- API project: https://www.drupal.org/project/api (download the 7.x-2.x-dev release or use Git)
- Documentation: https://www.drupal.org/docs/7/modules/api-module/create-your-own-api-7x-... -- includes instructions on how to update from a 7.x-1.x site)
Looking forward to hearing about the results of your testing!
It’s always useful to discuss the latest social sharing trends or best practices when designing a signup form. But whether your work includes designing the next pixel perfect icon library or solving the latest user interface problem, sometimes it’s also a good idea to take a step back and appreciate why we started doing ‘this’ in the first place.
Yesterday, after publishing a blog post about Nasdaq's Drupal 8 distribution for investor relations websites, I realized I don't talk enough about "Drupal distributions" on my blog. The ability for anyone to take Drupal and build their own distribution is not only a powerful model, but something that is relatively unique to Drupal. To the best of my knowledge, Drupal is still the only content management system that actively encourages its community to build and share distributions.
A Drupal distribution packages a set of contributed and custom modules together with Drupal core to optimize Drupal for a specific use case or industry. For example, Open Social is a free Drupal distribution for creating private social networks. Open Social was developed by GoalGorilla, a digital agency from the Netherlands. The United Nations is currently migrating many of their own social platforms to Open Social.
Another example is Lightning, a distribution developed and maintained by Acquia. While Open Social targets a specific use case, Lightning provides a framework or starting point for any Drupal 8 project that requires more advanced layout, media, workflow and preview capabilities.
For more than 10 years, I've believed that Drupal distributions are one of Drupal's biggest opportunities. As I wrote back in 2006: Distributions allow us to create ready-made downloadable packages with their own focus and vision. This will enable Drupal to reach out to both new and different markets..
To capture this opportunity we needed to (1) make distributions less costly to build and maintain and (2) make distributions more commercially interesting.Making distributions easier to build
Over the last 12 years we have evolved the underlying technology of Drupal distributions, making them even easier to build and maintain. We began working on distribution capabilities in 2004, when the CivicSpace Drupal 4.6 distribution was created to support Howard Dean's presidential campaign. Since then, every major Drupal release has advanced Drupal's distribution building capabilities.
The release of Drupal 5 marked a big milestone for distributions as we introduced a web-based installer and support for "installation profiles", which was the foundational technology used to create Drupal distributions. We continued to make improvements to installation profiles during the Drupal 6 release. It was these improvements that resulted in an explosion of great Drupal distributions such as OpenAtrium (an intranet distribution), OpenPublish (a distribution for online publishers), Ubercart (a commerce distribution) and Pressflow (a distribution with performance and scalability improvements).
Around the release of Drupal 7, we added distribution support to Drupal.org. This made it possible to build, host and collaborate on distributions directly on Drupal.org. Drupal 7 inspired another wave of great distributions: Commerce Kickstart (a commerce distribution), Panopoly (a generic site building distribution), Opigno LMS (a distribution for learning management services), and more! Today, Drupal.org lists over 1,000 distributions.
Most recently we've made another giant leap forward with Drupal 8. There are at least 3 important changes in Drupal 8 that make building and maintaining distributions much easier:
- Drupal 8 has vastly improved dependency management for modules, themes and libraries thanks to support for Composer.
- Drupal 8 ships with a new configuration management system that makes it much easier to share configurations.
- We moved a dozen of the most commonly used modules into Drupal 8 core (e.g. Views, WYSIWYG, etc), which means that maintaining a distribution requires less compatibility and testing work. It also enables an easier upgrade path.
Open Restaurant is a great example of a Drupal 8 distribution that has taken advantage of these new improvements. The Open Restaurant distribution has everything you need to build a restaurant website and uses Composer when installing the distribution.
More improvements are already in the works for future versions of Drupal. One particularly exciting development is the concept of "inheriting" distributions, which allows Drupal distributions to build upon each other. For example, Acquia Lightning could "inherit" the standard core profile – adding layout, media and workflow capabilities to Drupal core, and Open Social could inherit Lightning - adding social capabilities on top of Lightning. In this model, Open Social delegates the work of maintaining Layout, Media, and Workflow to the maintainers of Lightning. It's not too hard to see how this could radically simplify the maintenance of distributions.
The less effort it takes to build and maintain a distribution, the more distributions will emerge. The more distributions that emerge, the better Drupal can compete with a wide range of turnkey solutions in addition to new markets. Over the course of twelve years we have improved the underlying technology for building distributions, and we will continue to do so for years to come.Making distributions commercially interesting
In 2010, after having built a couple of distributions at Acquia, I used to joke that distributions are the "most expensive lead generation tool for professional services work". This is because monetizing a distribution is hard. Fortunately, we have made progress on making distributions more commercially viable.
At Acquia, our Drupal Gardens product taught us a lot about how to monetize a single Drupal distribution through a SaaS model. We discontinued Drupal Gardens but turned what we learned from operating Drupal Gardens into Acquia Cloud Site Factory. Instead of hosting a single Drupal distribution (i.e. Drupal Gardens), we can now host any number of Drupal distributions on Acquia Cloud Site Factory.
This is why Nasdaq's offering is so interesting; it offers a powerful example of how organizations can leverage the distribution "as-a-service" model. Nasdaq has built a custom Drupal 8 distribution and offers it as-a-service to their customers. When Nasdaq makes money from their Drupal distribution they can continue to invest in both their distribution and Drupal for many years to come.
In other words, distributions have evolved from an expensive lead generation tool to something you can offer as a service at a large scale. Since 2006 we have known that hosted service models are more compelling but unfortunately at the time the technology wasn't there. Today, we have the tools that make it easier to deploy and manage large constellations of websites. This also includes providing a 24x7 help desk, SLA-based support, hosting, upgrades, theming services and go-to-market strategies. All of these improvements are making distributions more commercially viable.
If you want to add Google's reCaptcha (https://www.google.com/recaptcha/intro/index.html) to your Drupal 7 forms programmatically you need to follow these two steps:
1) Install and enable captcha (https://www.drupal.org/project/captcha) and recaptcha (https://www.drupal.org/project/recaptcha) modules. The best ...
This week: Brightcove Video Connect Module // Drupal 8 has more and more features available practically every day. Alongside module migrations and new projects, the Drupal community’s latest major release also offers new ways of solving common problems. Some functionality has moved to Drupal core and new modules have taken up the torch along the way. In this series, the Acquia Developer Center is profiling useful solutions--modules, themes, distros, and more--available for Drupal 8.Tags: acquia drupal planetbrightcovevideo
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.Drupal.org updates Recognizing more types of contribution in the Drupal.org Marketplace
We were very pleased to announce an expansion of the issue credit system into a broader contribution credit system which recognizes more than just code contributions for the purposes of ranking organizations in the marketplace.
We now calculate the following 4 types of contribution into overall contribution credit:
- Issue credits — helping build the Drupal software happens in the issue queues. Issue credits remain the primary factor in ranking, and continue to be shown prominently. Issue credits on more widely used projects, like Drupal Core, will also receive greater weight in the ranking. Learn how to help in the issue queue
- Drupal 8 case studies — success stories show how Drupal is used across industries and the world, helping effectively introduce Drupal to more people. Learn how to write a case study
- Drupal Association Supporter Programs and Organization Membership — our partners and members help us build and maintain Drupal.org. Learn about supporter programs and organization membership
- Projects supported — the work to maintain a project sometimes happens outside of issues. Project maintainers can credit organizations which help provide time and sponsorship. Learn more about crediting project contributions
In a previous blog post on Drupal.org, we talked about our increasing focus on the adoption journey and our plans to create industry specific landing pages on Drupal.org. In January we did extensive user research with people in media and publishing, higher education, and government, which will be the first industries we promote. We're hoping to launch these pages very soon, so keep an eye on the home page.Preparing for community elections for the Drupal Association board
The elections process for the community seats on the Drupal Association board kicks off with self-nominations in February each year. This means that we dedicated some time in January to making small refinements and improvements to the nomination process. In particular we've added more in-context educational materials about the board to the self-nomination form, including a video by executive director Megan Sanicki. We've also refined our candidate questions to help candidates express their unique qualifications.
If you're interested in bringing your perspective to the Drupal Association board, please nominate yourself.Membership history messaging
To make it easier for members to understand their membership history, we've added new messaging to the membership join and renew pages. Users who go to join or renew their Drupal Association membership will now see a message indicating their current membership expiration date, their last contribution amount, a link to contribute again, and their auto-renewal status.Migration of Drupal Association content to Drupal.org
In January we also migrated the majority of content from assoc.drupal.org to a new section on Drupal.org itself. This effort is part of our larger content restructure initiative. By moving Drupal Association content into Drupal.org we hope to increase discoverability of information about the DA, and create a tighter integration between Drupal Association news and the front-page news feed.DrupalCI Checkstyle results now available on the DrupalCI dispatcher
Thanks to community member mile23, DrupalCI now supports automated code style testing. To see checkstyle results for any test on Drupal.org, click on the test result bubble and then click the 'view results' link to view the detailed test results on DrupalCI's jenkins dispatcher.
We're still gathering input and feedback for this initial release of the checkstyle feature, as we decide how to integrate the checkstyle results more tightly with Drupal.org. If you have feedback or suggestions please leave your comments in this issue: #1299710: [meta] Automate the coding-standards part of patch review.Updated testing environments
DrupalCI supports testing code against a matrix of php and database versions. In January we updated the php environments that DrupalCI supports, so that you can test against the minimum supported versions or the latest point releases. Our 5.X containers have been upgraded to the latest version for each minor release (5.3.29, 5.4.45, 5.5.38, 5.6.29). The singular PHP 7 environment that we were using was following the 7.0.x branch of php7. This has now been expanded into four php 7 environments, 7.0 (7.0.14), 7.1 (7.1.0), 7.0.x, and 7.1.x.
The dev versions of php are primarily intended for Core to sense upstream changes to php before they become released, as our comprehensive test suite often finds unanticipated bugs in php7. Additionally some missing features in the php7 containers were added, specifically apcu.Local testing improvements
DrupalCI has always supported local testing, in order to allow developers to test changes on their own machines. This is helpful for several reasons: it allows people to test on their own machines before triggering one of the DrupalCI test bots, it lets users troubleshoot failing tests, and it helps to eliminate the 'works on my machine' problem where code appears to work in a local environment, but fails on the test bots.
To make local testing even easier, DrupalCI now automatically generates a vagrant environment for local testing. To use this functionality simply clone the drupalci_testrunner.git repo and then run $ vagrant up from within the directory. Furthermore, DrupalCI can download a build.yml file from a dispatcher.drupalci.org url to replicate any test that has been run on Drupal.org. More information about this will be added to the DrupalCI documentation soon.Adding test priority
DrupalCI runs thousands of tests of the Drupal codebase for core and contrib modules every month. These tests include commit and patch testing for the active development which may be occurring at any time day or night, as well as the hundreds of daily regression tests run for both core and contrib projects. To help make testing more responsive, we've added a notion of testing priority. When there is a queue of waiting tests, Drupal 8 core patch tests will take priority; followed by D8 branch tests; followed by D8 contrib tests; followed by Drupal 7 patch, branch, and contrib tests.Community Initiatives Project Applications Revamp
Our primary community initiative priority for the first quarter of the new year is the Project Application Revamp. There are four phases to the revamp: 1) preserving security advisory coverage signals about projects, 2) transitioning security advisory coverage to an opt-in process, 3) opening the gates to allow any user to promote a project to full and create releases, 4) building new tools to incentivize code review and provide code quality signals on project pages. One of the changes we made as part of phase 1 was to adjust the way recommended releases are highlighted on Drupal.org project pages.Contrib Documentation Migration
Project maintainers are now able to create documentation guides on their projects using the new documentation content types. Maintainers can then migrate their old documentation content into these new guides, or create new documentation pages. For more information about this process, please consult our guide to contrib documentation.Help port Dreditor features to Drupal.org
Are you a Drupal.org power user who relies on Dreditor? Markcarver is currently leading the charge to port Dreditor features to Drupal.org, and invites anyone interested in contributing to join him in #dreditor on freenode IRC or the Dreditor GitHub.
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects.
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.
The Drupal Console has become a great command-line tool for managing Drupal 8 sites. In our Drupal 8 Module Development Trainings, we use it to automatically generate boilerplate code, so our trainees can get a quick start! Even though Drupal Console has been out for just one year, it already has over four hundred thousand downloads.read more
Hasselt University Professor Frank Neven asked me to come and talk a bit about my experience in open source, and how it helped me. It helped me during my studies, in my career and even in life :)Slides: http://wimleers.com/talk-oss-career/Location: Hasselt UniversityDate: Feb 14 2017 - 15:30
MidCamp is looking for folks just like you to speak to our Drupal audience! Experienced speakers are always welcome, but MidCamp is also a great place to start for first-time speakers. We currently have 69 submitted sessions and are looking for more. Please see our session tracks page to see what kind of talks we are looking for. Subject matter can be Drupal, PHP in general, related technologies, soft skills, testing, tools, workflow, etc.
Sessions submission will close Saturday, February 18th, 2017, so don't delay!Find out more at:
- Submit your Session
- Session FAQs
- Session Topics
- Speaker Terms and Conditions
- View the list of Submitted Sessions
Tickets and Individual Sponsorships are available on the site for MidCamp 2017. Click here to get yours!Schedule of Events
- Thursday, March 30th, 2017 - Training and Sprints
- Friday, March 31st, 2017 - Sessions and Social
- Saturday, April 1st, 2017 - Sessions and Social
- Sunday, April 2nd, 2017 - Sprints
Are you or your company interested in becoming a sponsor for the 2017 event? Sponsoring MidCamp is a great way to promote your company, organization, or product and to show your support for Drupal and the Midwest Drupal community. It also is a great opportunity to connect with potential customers and recruit talent.Find out more at:
- Visit http://www.midcamp.org
- Like Midcamp on Facebook
- Follow @midwestcamp on twitter
- Watch MidCamp on Youtube
"The time is coming," the walrus said, "to talk of many things…"
Nasdaq CIO and vice president Brad Peterson at the Acquia Engage conference showing the Drupal logo on Nasdaq's MarketSite billboard in Times Square NYC.
Last October, I shared the news that Nasdaq Corporate Solutions has selected Acquia and Drupal 8 for its next generation Investor Relations and Newsroom Website Platforms. 3,000 of the largest companies in the world, such as Apple, Amazon, Costco, ExxonMobil and Tesla are currently eligible to use Drupal 8 for their investor relations websites.
How does Nasdaq's investor relations website platform work?
First, Nasdaq developed a "Drupal 8 distribution" that is optimized for creating investor relations sites. They started with Drupal 8 and extended it with both contributed and custom modules, documentation, and a default Drupal configuration. The result is a version of Drupal that provides Nasdaq's clients with an investor relations website out-of-the-box.
Next, Nasdaq decided to offer this distribution "as-a-service" to all of their publicly listed clients through Acquia Cloud Site Factory. By offering it "as-a-service", Nasdaq's customers don't have to worry about installing, hosting, upgrading or maintaining their investor relations site. Nasdaq's new IR website platform also ensures top performance, scalability and meets the needs of strict security and compliance standards. Having all of these features available out-of-the-box enables Nasdaq's clients to focus on providing their stakeholders with critical news and information.
Offering Drupal as a web service is not a new idea. In fact, I have been talking about hosted service models for distributions since 2007. It's a powerful model, and Nasdaq's Drupal 8 distribution as-a-service is creating a win-win-win-win. It's good for Nasdaq's clients, good for Nasdaq, good for Drupal, and in this case, good for Acquia.
It's good for Nasdaq's customers because it provides them with a platform that incorporates the best of both worlds; it gives them the maintainability, reliability, security and scalability that comes with a cloud offering, while still providing the innovation and freedom that comes from using Open Source.
It is great for Nasdaq because it establishes a business model that leverages Open Source. It's good for Drupal because it encourages Nasdaq to invest back into Drupal and their Drupal distribution. And it's obviously good for Acquia as well, because we get to sell our Acquia Site Factory Platform.
If you don't believe me, take Nasdaq's word for it. In the video below, which features Stacie Swanstrom, executive vice president and head of Nasdaq Corporate Solutions, you can see how Nasdaq pitches the value of this offering to their customers. Swanstrom explains that with Drupal 8, Nasdaq's IR Website Platform brings "clients the advantages of open source technology, including the ability to accelerate product enhancements compared to proprietary platforms".