Drupal dev and design / Music PR / Politically Opinionated / Eater of Chilli / Finds it hard to be serious
@jeni could you use ECA to validate a field like this? Not tried it, but it was the first thing that came to mind....
@jeni no. But I am using it as frontend as well as backend
@jeni hmm I do have an update to do... Thanks
@jeni no d10... Have you used gin? I can't see the option on either gin or claro
@hotsauce It's only cos I'm working on a site that's basically an admin panel - where the frontend uses Gin as well as the backend.. that I noticed.
So now I've either got to learn how to activate that setting or hack the tpl which would be a pain every update.
Very grrr
Am I going mad - how have I only just noticed that admin themes in Drupal don't seem to have favicon settings.
Stoke’s melodic riff-lords CLKWRK unveil new single and video for BURN BRIGHT
Stoke's melodic riff-lords CLKWRK unveil new single and video for BURN BRIGHT Stoke-On-Trent trio CLKWRK have dropped their new single and video entitled Burn Bright. Marking the bands first music release of 2025, the track is a huge statement of the bands potential for the rest of the year. Burn Bright is a song with meaning, the chronicle of love gone bad, where synergy can become toxic.
@mikemccaffrey
The d word - Drecipe.
@mikemccaffrey There's one big difference - that once you've installed it there is no dependence on a third party to update their distribution.
You install it and the codebase is yours to maintain , upgrade and break if you want.
Same with recipes, no upgrade path for the 'recipe', once installed it's yours.
Drupal CMS only makes sense though as a proof of concept, IF other use cases appear and get built. It's got some great stuff, but the principles will either flourish or wither.
CLKWRK announce new single BURN BRIGHT to launch 11th April
CLKWRK announce new single BURN BRIGHT to launch 11th April Hometown single launch show at the Sugarmill Stoke-On-Trent 12th April Stoke-On-Trent natives CLKWRK are just getting started in their 2025 plans. With a raft of new music ready to drop, they are unleashing the first new single alongside a hometown show this month. Burn Bright is the new track, set for release on the 11th April, a sonically massive…
@ekes https://www.nngroup.com/articles/simplicity-vs-choice/
Had this bookmarked for a while (like years).. it's more about the output complexity, but I think a similar story could be told for data capture as well
@ekes like a data store?
@jeni
Aaah. The Brutalist phase.
In terms of Drupal vs CMS docs, most will crossover unless they are specific to the actual recipe functionality in CMS that may or may not be being used.
But there is the issue, core docs for Drupal haven't normally covered contrib projects, but the introduction of recipes changes that paradigm. But again, easy to solve - you have Drupal Docs, CMS specific docs (how to use recipes, XB, etc) and then Recipe docs (hopefully created as they are built).
I agree with this. There is a big difference between "User" and "Developer".
I think this has long been the issue with Drupal adoption, the documentation has always leant towards developers talking to other developers. Just look at any issue queue to see the pattern. A "user" posts an issue, and immediately is lost when told "if you provide a patch...etc". I've seen this more times that I would care to remember.
A USER guide should be just that, how does a USER use it.
@hotsauce holy crapola. That's awful news! Was it just a general downturn in workload?
I just hope they rethink the name "ripple maker". I don't want to make ripples, and I'm not going to announce that I'm small fry compared to others.
It's cheesy, demeaning and I was happy being a D.A. supporter.
@e0ipso but for the record, I seriously would have thrown some money at you while I was following the development of SDC - because I saw how great it was and how I would use it. So, thanks for putting in the work!
@e0ipso The main danger in a model like this is that you will have people try and hold code hostage. Like they will provide something, build user numbers and then say "no pay, no maintenance" - which completely undermines the whole thing.
It would also be up to the developer to have to be firm on a projects goals so they don't end up with a massive codebase they never intended to support. We have all experienced scope creep, probably would be worse if it was financially incentivised :)