The Tech Talks at Acquia Engage have always been among the most popular sessions, so I’m excited to announce that for Acquia’s upcoming Engage 2016 conference (Nov 1-3 in Boston) we’ve more than doubled the number of Tech Talks.
The purpose of software testing is to reduce issues to a minimal level and to carve out optimal quality for a product. When it comes to bugs and defects, there are different schools of thought, but quality is always the main focus.
Jozef Toth talks about the Drupal 8 CWI - I got the chance to follow up on my conversation with Dave Hall and Dick Olsson about the Drupal 8 Content Workflow Initiative (Podcast: Drupal 8 Content Workflow Initiative - Part 1). This post includes the video and full transcript of our conversation, as well as links to many of the people and topics we touched on!
Conversations about delivering business needs with digital tools, or "How to get Drupal into the conversation without talking technology."
The Workbench module suite is a key component to most Drupal 7 web sites. Providing revision management, personal editorial workspaces, and editorial access groups, the module suite provides a unified solution to common problems. Workbench was so popular in Drupal 7 that Acquia helped move it to Drupal 8 as part of the Module Acceleration Program. And now, Workbench Moderation is in Drupal 8.2 core as Content Moderation.
I got the chance to talk with Dave Hall and Dick Olsson from Pfizer at DrupalCon New Orleans about the Drupal 8 Content Workflow Initiative. This post includes the video and full transcript of our conversation, as well as links to many of the people and topics we touched on!
This is Part 4 of an interview with Will Eisner, Senior Director, Product at Acquia.
Understanding Object-Oriented Programming (OOP) has become really critical in Drupal 8. OOP adds benefits such as code reuse and encapsulation, allowing users to build better maintainable and structured code. This does come at a cost for the developer, who must make him or herself familiar with how this is done in PHP: namespaces, PSR-standards and general OOP concepts may all be new if you were previously using Drupal 7.
There are many different approaches to progressively decoupling Drupal, all with different pros and cons. This webinar will cover the different compelling approaches and some use cases of each, including:
Now that we've covered debugging Drupal 8 in PhpStorm using local web-based approaches, let's move on to command line debugging.
As Drupal is increasingly widely used as a back end for application ecosystems, developers of wildly diverse backgrounds are now retrieving and manipulating data from Drupal in unprecedented ways. With Drupal 8 and core REST support articulating an API-first vision for the decoupled future, Drupal is eminently well-prepared to back a bevy of applications with divergent approaches. There's just one problem: non-Drupal developers don't know Drupal.
That's where Waterwheel comes in. Waterwheel is an emerging ecosystem of software development kits (SDKs) built by the Drupal community which ease and accelerate development of applications in other technologies. If you will momentarily forgive the flawed metaphor, Waterwheel helps non-PHP and non-Drupal developers "speak" Drupal.
Lots of people think that template engines like Twig cannot be interactively debugged. I heard this several times as an argument against template engine, and for using legacy php processing like phptemplate (standard in Drupal 7).
Well, it’s not entirely true.
Progressive decoupling, a concept outlined last year in Dries Buytaert’s first post about decoupled Drupal, is a compelling approach to building Drupal's front end where content editors, site assemblers, and front-end developers maintain contiguous experiences. For content editors and site assemblers, progressive decoupling allows for contextualized interfaces, content workflow, site preview, and other features to remain usable and integrated with Drupal as a whole.