Views has been an amazing tool. I've used it since 4.7.
For me it was the secret sauce in Drupal. Content types + views + basic Drupal user management and page rendering was the best.
At this point I'd so much rather have an API and a JS front end.
In 2017 no one cares that you can create a list with a couple of "view modes" or fields that are a nightmare to "theme". Views is just so difficult to work with. Even Earl has stopped committing.submitted by /u/livelierepeat
I work on a Drupal based platform with a variety of Site builders, front end coders. One issue I've noticed is that they are unaware of the available tools that have been built into the platform, specifically, custom blocks and view blocks.
This got me thinking about the block listing page and how it really doesn't tell you a lot about what will actually show up when you place the block on the page. Has anyone ever built a custom Block listing page? What I'm envisioning is a list of all available blocks, that are then linked to a page that's basically a blank canvas with the block in the center. In a way this is a Drupal take on the Atomic design Pattern.
Of course context specific blocks would need to be provided default arguments in some way.submitted by /u/claytron79
Jacob Rockowitz: Webform 8.x-5.x-beta14: Ajaxifying Webforms and Improving User Submission Management
Webform 8.x-5.x-beta14 has become a significant release because it addresses several important features and milestones listed on the Webform roadmap, including support for multiple drafts, Ajax-enhancing submission forms and the administrative UI.
Before I start to "show-n-telling" you about these cool new features, wanted to announce that I am targeting monthly releases and explain my goals for each release of the Webform module.
Initially,I was reluctant to publically commit to regular releases for software that I am maintaining for free. Turns out my public commitment is a good thing. Targeting regular releases motivates me to organize the Webform's roadmap and issue queue while iteratively working on fixing bugs and adding new features. I’m trying to take an agile approach with maintaining the Webform module that seeks to iteratively implement working features knowing that features and functionality can and should evolve over time.
The Webform for Drupal 8 (formerly known as YAML Form module) is a completely new codebase striving to reach reasonable feature parity with the Webform 7.x-4.x module, which is used by a half million Drupal 7 websites. I've also looked at the Webform ecosystem for Drupal 7 - gradually I’m integrating key Webform add-on modules into the core Webform module for Drupal 8.
Ajaxifying Webform Forms and User Interface
Meet our last intern: Brandon Reid of our Web & Drupal Developer Internship program! One of his first projects as an intern was to research High Tech Website built on Drupal, so without further ado, here are his findings:
For those who aren't familiar with Drupal. Drupal is the #1 platform for web content management among global enterprises, governments, higher education institutions, and NGOs. Drupal is flexible and highly scalable, publishing a single website or shares content in multiple languages across many devices. Technology and business...Read more
Drupal 8 - Console, Setup and Usage in building drupal application
The Drupal CLI. A tool to generate boilerplate code, interact with and debug Drupal.heykarthikwithu Wednesday, 28 June 2017 - 12:05:12 - IST, Asia/Kolkata
Creating a multistep form was not straightforward in Drupal 7, although there were some solutions, like “mforms”,” multistep” and apparent solution by show/hiding fields by “Field Group” module but Drupal Developers have struggled to create MultiStep Form, In this article I’ll try to describe how we can create MultiStop Form in Drupal 8,it’s not hard as much as it was in Drupal 7, Drupal 8 makes it easy for us, stay with me.
GSoC17 : Client Side File Crypto : Week 4
This blog post summarises my fourth week of the coding period of Google Summer of Code with Drupal.Code Review
The week began with iterating over previously committed code based on feedback by Colan. After making the changes and pushing them, I later merged the merge request into the 8.x-1.x-dev branch after Colan’s approval.tameeshb Wed, 06/28/2017 - 09:16 Tags GSoC Google Summer of Code 2017 Drupal Drupal Blog