The Drop Times: Register Early for DrupalCamp NJ 2023
The Drop Times: DrupalCamp NJ: Submit Your Sessions Before Feb 01
Matt Glaman: Trimming whitespace from Drupal form submissions using an HTTP middleware
Leading and trailing whitespaces. The bane of normalized data everywhere. It seems like a constant task that needs to be performed on incoming user data. When working with Laravel, I use the TrimStrings
middleware. Calls PHP's built-in trim
function on all string values for the request query and input values – including JSON! While working on my project WhiskeyDex, I noticed how mobile device keyboards always add trailing whitespace when using the autocomplete functionality. This, in turn, meant user-created data will end up with trailing whitespaces. I started to just quick-fix in the single instance and realized it should be solved once and for all.
Acquia Developer Portal Blog: How to Enable Project Browser on Your Drupal Site
Project Browser makes it easy for site builders to find modules. Once selected, instructions are provided on how to install the modules on your site. This browser lives inside the Drupal site itself, which means you don't need to leave your site in order to look for modules. Plus, it's a much improved experience than trying to page through modules by popularity on Drupal.org.
To get started, we must first composer require the module:
Quilltez: Drupal 10 Create Node Programmatically
Drupal is a content management system that allows you to create and manage website content in an organized way. One of the ways to create content in Drupal is by creating a node programmatically. A node is a fundamental building block of a Drupal website and represents a piece of content such as an article, a page, or a product.
To create a node programmatically in Drupal 10, you will need to use the Drupal's Entity API, specifically the Node class. Here's an example of how you can create a basic node:
leopathu Tue, 01/10/2023 - 16:07 Drupal10 Drupal PlanetTalking Drupal: Talking Drupal #381 - A Modular Web with Sam Bhagwat
This is episode #381 A Modular Web with Sam Bhagwat.
For show notes visit: www.talkingDrupal.com/381
Topics- Gatsby
- Founding Gatsby
- Modular: The Web’s New Architecture
- When did you decide to write the book
- Key tech changes over time
- What is the Modular Web
- Successful architecture
- Is it similar to serverless
- Challenges
- Drupal focused companies and modularity
- Advice on transitioning
- Drupal
- 2023 and Gatsby
- Staying competitive in JS
- Kindle Book
- Modular: The Web’s New Architecture: (And How It’s Changing Online Business)
- gatsby-plugin-drupal-i18next
- Gatsby and Drupal (224, 260)
- The Website Owners Manual by Paul Boag
- tc39
- Gatsby: The reactive site generator (and a live demo tour of how we got here)
Nic Laflin - www.nLighteneddevelopment.com @nicxvan John Picozzi - www.epam.com @johnpicozzi Stephen Cross - www.StephenCross.com @stephencross
MOTW CorrespondentMartin Anderson-Clutz - @mandclu Decoupled Interface Translations Allows a headless application to use Drupal-managed interface translations.
The Drop Times: DrupalCon Pittsburgh 2023: Important Dates to Remember
Gizra.com: ElasticBeanstalk ♥ Drupal
DrupalEasy: DrupalEasy Podcast S14E3 - Leslie Glynn - How to test Project Browser
We talk with Leslie Glynn about the Project Browser initiative with a specific focus on how to check it out and get involved with the project.
URLs mentioned
- Project browser project on drupal.org
- Strategic initiative: Project browser
- Kanban board for getting the top 100 module ready for Project browser
- Leslie's slides from NEDCamp
DrupalEasy News
- Professional module development - 15 weeks, 90 hours, live, online course.
- Drupal Career Online - 12 weeks, 77 hours, live online, beginner-focused course.
Audio transcript
We're using the machine-driven Amazon Transcribe service to provide an audio transcript of this episode.
Subscribe
Subscribe to our podcast on iTunes, Google Play or Miro. Listen to our podcast on Stitcher.
If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.