By 2020, 85% of all enterprise interaction will be via bots.
AI-powered bots can make frictionless customer experiences, and drive more conversions. But how are you getting your chatbots to deliver the right answers? Are you stuck recreating all your content in a format that bots can use? That's definitely needless duplication of work, and the slower way, so your competitors could beat you to market.
Feeds and Migrate were two primary contrib modules used for data import since early versions of Drupal. Quick comparison of two modules: Feeds module has great friendly UI that allows site builders configure and import data, Migrate is built for developers with power to perform complex backend data processing but UI for this module was less than ideal.
In D8 migrate module is in core to support one-click upgrades from earlier Drupal versions – great news. In the hallway of Baltimore DrupalCon maintainers of Feeds and Migrate started conversation about using migrate engine to power Feeds UI – seems to be a win-win solution for everyone – developers, site builders, content managers, end users.
In the beginning, there was a conference called Decoupled Dev Days. It had a web site that was React but not actually decoupled at all. Then the next year, it became Decoupled Drupal Days and was still a static site. But this time, it was made with Gatsby. And as the days passed, and the content became more unmanageable, the need for a better CMS was needed. So Drupal was added and the site instantly became decoupled and easy to manage.
No.. Not really.
There were hoops to jump through, build problems, entity reference access issues and image conundrums.
Unexpected complications will always arise and having explicit goals, positive dynamics, budget, timing, team with balance of skills, access to the information, the right channels to communicate, useful and constant feedback in a collaborative space will grant the ingredients to succeed.
Taking the time to get the essential pieces in place from the start will guarantee the success of a Project; as well as the team´s satisfaction because they are creating something wonderful and meaningful together.
3 T´s are Key factors in the longevity of the relationship with our client.
When a client comes to you, don’t start a project, start a relationship. The goal isn’t to solve individual problems, but have an ongoing conversation to assess client needs and find the best solutions.
Supporting Drupal sites requires attention to not only technical needs but also human. The number one most important element of a support program is to make your clients feel comfortable and taken care of. That requires a team of people who can all bring their own expertise and unique skills.
Watch the session video here.
Are you a stakeholder? Do you work for an agency as a designer, engineer, or product manager? Are you a citizen wondering how your government’s website can serve you better?
There’s been a lot of ink spilled about how the RFP process is broken, particularly when it comes to technology projects. This session isn’t going to litigate various viewpoints on that front, because RFPs are not going anywhere anytime soon — especially when it comes to nonprofit, higher ed, and public sector projects.
Ignore the naysayers! Your RFP can be brilliant!
Volunteering is cool, nobody questions that, but we are all pragmatic humans and thus need motivation. In this session I will share with you reflections derived from my experience of contribution to open source. Mostly it has been Drupal (6 years) and just recently initiated Gentoo Linux (6 months). During these 6 years I grew as a contributor to the status of a co-maintainer of Webform 8.x module.
