Downloading and installing libraries for every new site is a PITA.
So I've spent an hour today with trial and error to find out how libraries can be installed with composer.
Results: there are three things to do in composer.json
https://css-tricks.com/snippets/jquery/simple-auto-playing-slideshow/
https://symfony.com/doc/current/frontend/encore/server-data.html
Videos. Responsive pseudo-streaming. MP4 with H264 and WEBM with VP9.
recommended bitrates per resolution:
I thought I would quickly setup a little stock tracker and portfolio tracker app using the easy to use and free Yahoo Finance API or Google Finance API, but oh boy, it's not a free internet anymore!
I guess the free data subscription models didn't work out, because both services have been discontinued. Open Bloomberg is history as well.
So after some research I made a shortlist of API providing free market finance data:
I regularly scan the web for more Drupal modules that add functionality that I might need.
This is my most recent crop. I include it here so that I don't forget it, and I add what I hope the module will achieve
for all sites
stumbled upon this unbelievable writeup of all things Jquery and Javascript in a Drupal context:
https://www.therussianlullaby.com/blog/guide-how-to-integrate-javascript-in-drupal-8-9
Great reference document, I saved this to a Word document and also put the URL here so I find it easily again.
there's a part 2 to my dream to be a Drupal dev - the previous installment was about creating patches, but the new recommended way of contributing code to Drupal is to create an issue fork and create a merge request.
As usual, documentation on Drupal.org for doing that is poor, and I spent hours to figure out how to get it done.
here are my steps:
*this supposes you have access to Drupal.org as well as Drupal GIT
Open an issue and describe what you want to do
Click "request push access"
HAR HAR HAR
Ummmmmm
Okay, let's start with correcting bugs by adding some null checks... don't say it's not real coding... please ... there... I asked you kindly not to say it... please. TT
Login to Drupal.org, login to Drupal GIT
Go to the project page, such as https://www.drupal.org/project/webform_validation
useful if you want to hack core or a module, but want to keep updatability and composer integrity.
use Winmerge
file paths in the .patch file are relative from the root directory of the installed package that is being patched
store patch in some high directory, I use /projectname/patches
add the patch under "extras, patches" in composer.json
run composer update
Very strange, patches hosted on Drupal.org can be applied by composer with no problems, but a patch from a local directory on my Windows system failed.
I used Winmerge to produce a patchfile, included it in composer.json and the result was always "could not apply patch"
composer -v update
produced the result "patch is not a recognized internal or external command"
