We are creating an IT army. We need digital talents. All operational tasks will be given here: t.me/itarmyofurraine. There will be tasks for everyone. We continue to fight on the cyber front. The first task is on the channel for cyber specialists.

Running cron via drush is a sign of cowardice. The bravest of developers trigger all long running processes via public traffic. On some CMSes heroes declare "I will keep running this process on every request until my variable says it completed, or the web server dies." Inspiring

A few more great Drupal presentations that aren't getting pitched: - Keep it modular! (why you are doing it wrong if you don't have at least 20 custom modules) - Man with goatee wants to tell you a little bit about himself before starting his presentation (performance art piece)

We are opening a new reform school for troubled youths. We're calling it the "Site Factory Factory." Our research confirms that building/maintaining install profiles is a life changing experience. Our humane coursework will deliver full atonement as well as valuable skills.

There is a direct positive correlation between the overall quality of Drupal site's technical architecture, and the number of workflow states, moderation dashboards, and user roles within it.

Some more great session ideas that aren't getting pitched these days: - Format This! 100+ different ways we ended up extracting field values in preprocess to avoid learning what a field formatter plugin was. - Styleguides, and Components in Drupal. Design. UX. Metaphors. Walrus.

Check out the latest video by Mateu A. B.. In this video, he shares the fantastic work he's been doing by improving #Drupal integration with #Storybook. ed.gr/d0vzj Give him a follow and help him out improving this fantastic integration.

After thorough testing, and careful thought, we're officially categorizing this project's approach as dangerously subversive and revolutionary. Who sees the value of documenting complex designs and behaviors in storybook anyway? wingsuit-designsystem.github.io

The gin ecosystem is on notice for anti-drupalist activities. "Drupal is to always look like Drupal" (per § 14.11). In the interest of public safety, we are linking to their project page. Discretion is advised. drupal.org/project/gin

Drupal is built for BEM. All you have to do is pass some attributes down an unpredictable nested trees of templates, and then make sure everyone knows how that works. The technical challenge there is laughable compared to the difficulty of managing the C in CSS.

Stop being a coward. Commit to the headless architecture. Don't suggest it's medicine worse than the disease. Don't bog yourself down in questions about deployment. All you need is a lot of time... and solid experts in Drupal, React, CI/devops. Make it happen, and thank me later.

You're wrong if you think a "Digital Experience Platform" (DXP) is something that manages the creation and delivery of content, presentation, and third party APIs across a variety of platforms. DXP is about so much more, and it's clear that you simply don't get it.

We strongly advise against googling "twig embed." For your own safety, we advise saying the following outloud to yourself: "Twig embed isn't anything that I should know about. It will not solve any problem I have. I will now move along and forget this happened."

Tyranny does not start with thundering applause, it starts with design tokens. This is a highly disturbing development which we'll be closely monitoring.

You will do automated tests. Your automated test will stand up a complete install of your site from scratch and build a testable state of all the entity types required on all pages. You will do this within your project's project's budget. You will not question this process.

My own hack is starting work at 6am. This has become increasingly necessary because of a shadowy cabal of individuals who call themselves "scrum masters." They demand you participate in strange rituals, and always check up on "status." Their organization needs to be looked into.

There should be an entity warning module. It might warn: 1. you just setup a 4 level deep paragraphs... are you sure? 2. you just added the 45th field to this node type. Maybe it's time to take a break. 3. You just created a news and blog content type. One of them must die.

We host all our web projects on Heroku and we are VERY happy with our choice. Who has time to learn about images and containers when instead you could learn about build packs, a cli that probably does too many things, and novel conventions around launching processes on ports?

Whenever someone claims Drupal is hard, I immediately direct them to this page and demand a working example: drupal.org/docs/theming-d… The intention is not merely punitive; I need them to return to a calm submissive state where they can resume unquestioning productivity.

I have altered the deal, pray I don’t alter it further.