From 0c98be96ebbd624ad21b85da4844218e04d5324a Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.uk>
Date: Fri, 30 May 2025 16:19:41 +0100
Subject: [PATCH] Remove the feeds module

---
 composer.json                                 |    1 -
 composer.lock                                 |  312 +--
 ..._form_display.node.daily_email.default.yml |    9 +-
 ..._view_display.node.daily_email.default.yml |    2 -
 ...tity_view_display.node.daily_email.rss.yml |    2 -
 ...y_view_display.node.daily_email.teaser.yml |    2 -
 .../core.entity_view_mode.feeds_feed.full.yml |   13 -
 config/sync/core.extension.yml                |    1 -
 config/sync/feeds.feed_type.daily_emails.yml  |   69 -
 config/sync/feeds.settings.yml                |    3 -
 ...ield.field.node.daily_email.feeds_item.yml |   23 -
 config/sync/field.storage.node.feeds_item.yml |   20 -
 .../system.action.feeds_feed_clear_action.yml |   13 -
 ...system.action.feeds_feed_delete_action.yml |   13 -
 ...system.action.feeds_feed_import_action.yml |   13 -
 config/sync/views.view.feeds_feed.yml         |  737 -----
 ....90c85284-7ca8-4074-9178-97ff8384fe76.json |   73 -
 content/meta/index.json                       | 2463 ++++++-----------
 ....0001428e-621c-49ca-83d3-4323ea446f48.json |    9 -
 ....001f3ebb-79dc-43ad-a363-6dc668d06a0c.json |    9 -
 ....00497277-4b40-4d36-a473-8d8e1a187c18.json |    9 -
 ....00d62e94-80d1-4792-bdea-88a064f6bf65.json |    9 -
 ....0100be71-79ef-44ea-922e-e75fcc26ae16.json |    9 -
 ....01230324-62b5-442b-80e4-09268a31819b.json |    9 -
 ....01893784-8f45-4466-8586-17df23e7e4b5.json |    9 -
 ....018bf894-2d3e-4130-b0bd-43450ef5753a.json |    9 -
 ....01f3b831-e981-471f-aef9-076b054e3495.json |    9 -
 ....0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json |    3 +-
 ....021e00c1-b813-4edd-8064-71285bc3647d.json |    9 -
 ....0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json |    9 -
 ....024f2c81-68af-4eef-bea5-1b1d43bd1b39.json |    9 -
 ....025f0dde-748b-44f4-93e2-4e0602d30104.json |    9 -
 ....02777730-3fe8-4eba-8a16-e847042b7351.json |    9 -
 ....02bd7b93-43c7-453f-8af9-0be875b27f82.json |    9 -
 ....02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json |    9 -
 ....0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json |    9 -
 ....0316dfcf-b709-47e1-9622-9355b5ece6d9.json |    9 -
 ....0318e249-a9a8-476f-9bd4-432544369917.json |    9 -
 ....033f0b46-69f9-4ea0-9706-d930e67dd5d8.json |    9 -
 ....036a8839-c5f9-4206-a979-201e9dac1557.json |    9 -
 ....037796b8-42d8-4ea4-abec-f8c8de0d97e8.json |    9 -
 ....03bbb03d-5963-477a-a904-19e2c1f1a581.json |    9 -
 ....03c0a713-f32d-445b-9397-add68fbf2fe5.json |    9 -
 ....042e4d0c-f835-47dd-8075-745df0a7f8f2.json |    9 -
 ....04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json |    9 -
 ....050525d7-3275-486e-8f0e-9548aa81a156.json |    9 -
 ....050a5113-59bc-461e-ac78-420e16055303.json |    9 -
 ....05232b81-d945-4112-99bf-d1adb2552428.json |    9 -
 ....0610a25f-884a-48b6-8be0-e969749d316a.json |    9 -
 ....062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json |    9 -
 ....066297b1-ab00-4769-afe1-d3831ed2a654.json |    9 -
 ....06b8d0b3-318a-4a06-902c-f42ce169774b.json |    9 -
 ....079f2e09-0827-458e-91d3-6dd5b8b80c56.json |    9 -
 ....08209d64-40fa-4771-9415-c23e962a5028.json |    9 -
 ....0843614b-645e-4d55-9e70-f960d504cadb.json |    9 -
 ....09073a81-2a1b-4200-905b-98b43152fe37.json |    9 -
 ....09097ac1-03ea-456c-a1bd-49bdc2bb9499.json |    9 -
 ....098d8367-a714-4e16-97b5-44f42a2a1cc2.json |    9 -
 ....09d6a39f-ac99-44fc-b660-4f976132d813.json |    9 -
 ....09dff532-7bc4-4949-bfdf-7c4a6e59097a.json |    9 -
 ....09f421c4-eff1-4b5c-a692-45dfbd837758.json |    9 -
 ....0a04ac23-4d64-40e8-8e94-ead3cab7129d.json |    9 -
 ....0a2a3238-42ea-46de-8140-94e74f381916.json |    9 -
 ....0a3bf034-7203-45c2-aae5-74f9211929fa.json |    9 -
 ....0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json |    9 -
 ....0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json |    9 -
 ....0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json |    9 -
 ....0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json |    9 -
 ....0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json |    9 -
 ....0c1ee324-e522-440a-85bf-e91847091ec9.json |    9 -
 ....0c899647-4916-4ad6-bde0-5ae1f397cc13.json |    9 -
 ....0cc877ae-0361-456e-be2c-73c322fe1780.json |    9 -
 ....0ce2a823-c7ad-475b-9cca-29e1b1702e77.json |    9 -
 ....0cedee86-a2d2-4325-a662-a7399be15d44.json |    9 -
 ....0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json |    9 -
 ....0d707bca-be14-4504-b500-9e44abebab44.json |    9 -
 ....0da14ab3-af09-42cf-9813-877a7a66cf87.json |    9 -
 ....0db2d25b-3e50-4f36-abe1-f84b938c21db.json |    9 -
 ....0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json |    9 -
 ....0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json |    9 -
 ....0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json |    9 -
 ....0e1fbc03-a045-4ca4-8925-69e39b67d893.json |    3 +-
 ....0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json |    9 -
 ....0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json |    9 -
 ....0f349fae-6a04-42b4-979f-ed8428e97a2b.json |    9 -
 ....0f64feba-0a96-41e4-b8e3-10358e4c86c6.json |    9 -
 ....0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json |    9 -
 ....0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json |    9 -
 ....1007a975-f818-4568-8560-9532e96c4577.json |    9 -
 ....10105b0a-c18f-4b77-8ac9-bec3250e37b7.json |    9 -
 ....10b3608a-50f6-4178-9ae2-d07f353a9c23.json |    9 -
 ....10d399d8-6247-48ef-a1b2-d777ecca827d.json |    9 -
 ....112ace31-6c57-405a-8c91-a2a19364fa20.json |    9 -
 ....113e4367-2915-402c-887f-f7dafdb28c86.json |    9 -
 ....11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json |    9 -
 ....123f0530-1218-4db1-b8ce-aecf38d8ec41.json |    9 -
 ....1254f835-445d-4a54-a831-2fc179b3d15c.json |    9 -
 ....12950855-9231-4731-9ccc-e8bc9f61e170.json |    9 -
 ....12b405e6-2827-4279-b85a-7f06475a69a4.json |    9 -
 ....12fb6cce-1f55-4359-b189-700c8ba16935.json |    9 -
 ....13312da0-7cf4-4825-ac6e-eb35c673e63e.json |    9 -
 ....13aced92-5b3d-407d-b242-fb8187a78dd7.json |    9 -
 ....13c70679-77d6-404e-9b4d-ca214713e315.json |    9 -
 ....13e1b1ea-a0df-43b2-8f1b-e8340bb62df8.json |    9 -
 ....140628f4-5b97-4b01-8a55-ca68cf49c635.json |    9 -
 ....141f3c86-ae34-430f-9cba-d1278047fe0d.json |    9 -
 ....1420a8f0-0482-4fa6-86ec-876d84c27255.json |    9 -
 ....1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json |    9 -
 ....15237599-15e7-496b-a7e0-c02fddae26f8.json |    9 -
 ....1550e619-abd2-4efe-b941-fd4e42507d51.json |    9 -
 ....1579b5cf-889e-4a7b-98a7-59918359def9.json |    3 +-
 ....1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json |    9 -
 ....162509c1-9ef9-4647-9ae5-843e6b214cce.json |    9 -
 ....166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json |    9 -
 ....168c59ab-cadd-4dfc-8c72-de82d6578885.json |    9 -
 ....16dc23db-86e4-4c5d-b479-3f92828dae12.json |    9 -
 ....16ed92b5-de67-44e4-b11a-7474081a00d2.json |    9 -
 ....172b603f-fddb-46cc-ac9e-0cd90a339c77.json |    9 -
 ....178c6bab-7e28-413a-9055-24fac0de0d0a.json |    9 -
 ....179c3eed-b723-4f44-b9d4-398b90b916e7.json |    9 -
 ....17a436ab-84f0-4c0a-9305-b04a9e1883ee.json |    9 -
 ....18cac962-eefd-4506-8efd-cd584f027369.json |    9 -
 ....190e33fc-0d42-49fd-8f4d-1cfd174b988a.json |    9 -
 ....192c6112-5287-46c9-9fed-5260db08a41c.json |    9 -
 ....19376fcb-fc7a-4b4a-9fea-6865e423519e.json |    9 -
 ....19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json |    9 -
 ....19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json |    9 -
 ....1a024983-b73b-4b2c-a350-db9152de27a9.json |    9 -
 ....1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json |    9 -
 ....1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json |    9 -
 ....1bac9c8b-18bd-4f09-a8ae-867c43798762.json |    9 -
 ....1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json |    9 -
 ....1c357f25-ed1e-406f-9899-ec9017548800.json |    9 -
 ....1c57b2eb-1206-4833-afb0-a65ec3f432a0.json |    9 -
 ....1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json |    9 -
 ....1d61b9ee-e6de-4db6-8782-68eba42d357a.json |    9 -
 ....1d8c474a-de0c-417c-bc05-179eef2e9bfb.json |    9 -
 ....1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json |    9 -
 ....1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json |    9 -
 ....1e59e156-0e2c-4f6d-a828-030d1322fde6.json |    9 -
 ....1f3f5a8f-412f-4da1-8e7a-4303962079d1.json |    9 -
 ....1f9686d7-f067-4253-88a6-639125a625a6.json |    9 -
 ....1f99779d-11cb-4679-9a0e-fce1be58f6b7.json |    9 -
 ....1fd87ecf-4269-4874-859e-d49c238694bf.json |    9 -
 ....20010c04-2f30-4772-9041-6f7e836158f8.json |    9 -
 ....207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json |    9 -
 ....2142e27d-5c96-4c16-9650-dc47b2b85888.json |    9 -
 ....216f7a7d-663b-42a6-b430-3817a1180dbd.json |    9 -
 ....217616ab-32cb-4c7f-b51c-7da3974de4e2.json |    9 -
 ....21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json |    9 -
 ....21f3f75a-e37f-44b6-81f5-337cc11e5eac.json |    9 -
 ....2234ff18-11e6-4689-9316-cae9fb3f0579.json |    9 -
 ....225110fb-82d3-4056-a394-0612d80e37ec.json |    9 -
 ....2258201f-7beb-4b2a-8a52-ea31c09de73f.json |    9 -
 ....22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json |    9 -
 ....22e50919-7f11-45ed-881e-31482670f416.json |    9 -
 ....22f6723d-c781-4548-a2cf-3b642e91b4ad.json |    3 +-
 ....235bcd7b-1bdb-4616-99bb-ecd321f449a0.json |    9 -
 ....23bff06b-34e8-4f9a-ae67-4405393c874c.json |    9 -
 ....2492a986-0932-437a-a7b4-414dbebb4a2a.json |    9 -
 ....251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json |    9 -
 ....25294346-8919-49c4-affa-d87616ed3df5.json |    9 -
 ....2530ef2e-0df9-4364-8e08-5d872cd9621e.json |    9 -
 ....25833838-38b9-414d-bca6-de0bf5c2ac28.json |    9 -
 ....26335c09-8a6a-461d-85c7-f0dbe37bb890.json |    9 -
 ....266918e6-af3d-48f8-89d4-657ff2214626.json |    9 -
 ....26e4ff33-b5fd-47b4-926e-fc5b78677c88.json |    9 -
 ....26f6be13-6309-441d-977f-eb84684b8a2f.json |    9 -
 ....27159a73-e3ac-4fa9-b18c-2f70157e31d7.json |    9 -
 ....274408ed-379c-4eaf-914d-7f5599f513d3.json |    9 -
 ....278813c0-1c8b-4558-bf13-3c2f03acaeb6.json |    9 -
 ....27926937-f426-490f-ac0a-454d9d2def37.json |    9 -
 ....283e9379-f264-4191-8bbd-2cd8393c395b.json |    9 -
 ....2885a415-17fb-4374-8070-0be55407af6c.json |    9 -
 ....290e62f9-ffc1-4420-91f7-decda6410276.json |    9 -
 ....294ea660-e93e-4596-ad81-5a53d2ba2555.json |    9 -
 ....2959438c-8c12-49c7-84a2-d9ea9bf338e6.json |    9 -
 ....298d7816-0b4a-449e-a78d-fcf973f24bf0.json |    3 +-
 ....29a700d5-082c-4f6b-bafd-f4c4e1486624.json |    9 -
 ....29ab0d54-5f71-4615-b391-164735cada18.json |    9 -
 ....2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json |    9 -
 ....2a816ad4-7e24-4082-83c3-b93490294170.json |    9 -
 ....2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json |    3 +-
 ....2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json |    9 -
 ....2aed4449-60c0-45a6-884d-73eee930eed8.json |    9 -
 ....2b55b7dd-2287-462d-a951-62603ce334bd.json |    9 -
 ....2b747510-63ea-489c-88de-af7995d94d45.json |    9 -
 ....2be6f96b-eecb-4205-9ca9-b364196535ab.json |    9 -
 ....2bf48b4d-12c8-43be-9f95-c4c54fe34712.json |    9 -
 ....2c022817-6bf1-4a2f-809e-8895c72a0e03.json |    9 -
 ....2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json |    9 -
 ....2c83980a-deb6-4e52-95a8-a87155cc3e2a.json |    9 -
 ....2cd07893-c184-4369-bbeb-45c2e9e055a7.json |    9 -
 ....2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json |    9 -
 ....2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json |    9 -
 ....2d0b16d8-0781-411e-a06b-f62bf9a9c253.json |    9 -
 ....2d89873f-8f15-4e92-9f72-1a83855d3d82.json |    9 -
 ....2da2e369-297c-46bd-83e5-8fd16d4c85c1.json |    9 -
 ....2e4827a4-0d9c-458c-86eb-d6b40f18d608.json |    9 -
 ....2eadbc08-32b4-4485-9cfd-087223e7040b.json |    9 -
 ....2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json |    9 -
 ....2f257fd0-6e5d-4690-9f01-3435e3578798.json |    9 -
 ....2f503fac-0d18-436b-a5d1-64263c5fc616.json |    9 -
 ....2f576a37-bd5a-4894-9340-1e69775c8b68.json |    9 -
 ....2facc6b4-52da-4fc5-b957-e29d06f19ae8.json |    9 -
 ....2fed4dad-d36f-47f1-9671-07dc97cfb50c.json |    9 -
 ....301495eb-5851-4dce-9625-779ebb8d7b2b.json |    9 -
 ....31026a42-b854-4517-b2d0-790036cfe6ad.json |    9 -
 ....312fd370-dae0-41b9-977f-282fc553e701.json |    9 -
 ....3179746f-a523-4f4d-8bef-44d0c117cb43.json |    9 -
 ....32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json |    9 -
 ....323bc6bc-069b-497b-9f64-d64c21bdba79.json |    9 -
 ....32591463-ab8b-4210-84ca-419bb69439c4.json |    9 -
 ....3373d8dc-7c1d-477f-8628-f3029228b9c4.json |    9 -
 ....33bea7ca-ccf4-4865-bc17-314ce54b6988.json |    9 -
 ....3422a295-b8a9-43a0-9a03-a54d77e52513.json |    9 -
 ....34be6fed-cd1a-4796-adb8-577340a359b4.json |    9 -
 ....34e3bc00-ec41-4e3a-986d-af500b03fc5c.json |    9 -
 ....357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json |    9 -
 ....358edef5-5436-46ca-a90c-4d691ea7c281.json |    9 -
 ....362530ad-9f84-49c4-a8cb-bea45c77c474.json |    9 -
 ....3681f8cd-22d5-4c2c-b03f-a751bc39753d.json |    9 -
 ....369e9679-fef1-4678-aab9-7edcb39f5533.json |    9 -
 ....36d7f751-faeb-48a4-9fb3-fc8248bb515c.json |    9 -
 ....38522a11-5473-4584-a8f0-c9097a843c9b.json |    9 -
 ....38535020-c00e-4720-8534-73346ff7cb0d.json |    3 +-
 ....38988766-4898-4aec-a987-c189ae1ea6c6.json |    9 -
 ....391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json |    9 -
 ....3933cd74-d4f5-4129-b3a1-71d573c5bf85.json |    9 -
 ....394246dc-42f8-4fbd-987c-7b62c47b9f06.json |    9 -
 ....39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json |    9 -
 ....39db6489-2e23-4cb3-a0be-a4e78a2e9142.json |    9 -
 ....3a13004e-2245-425f-8080-0b98e161bcb0.json |    9 -
 ....3b090ba6-775a-44a1-bc43-c6807380fb59.json |    9 -
 ....3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json |    9 -
 ....3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json |    9 -
 ....3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json |    9 -
 ....3cb7e223-af31-471e-acef-d3d069852841.json |    9 -
 ....3d777436-a3ab-4465-b3c2-63d7eb28b50d.json |    9 -
 ....3e810095-a24b-4f0b-a62b-e39003df099e.json |    9 -
 ....3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json |    9 -
 ....400a0b92-7c40-43b0-883d-5f199fb5471f.json |    9 -
 ....40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json |    9 -
 ....40f5b812-3bf8-47e5-bc39-57d9ae8db404.json |    9 -
 ....41754bbf-ade6-41a3-97f6-90f101c65265.json |    9 -
 ....4177af82-b6e3-4200-9fb8-d66f47611742.json |    9 -
 ....41b8a70d-5df8-45f5-956a-c30b2f3e06de.json |    9 -
 ....42741272-127f-46fb-b058-172301e5edd1.json |    9 -
 ....42744e61-acab-44e4-bd60-576a30cf7b60.json |    9 -
 ....42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json |    9 -
 ....42904e0f-f6d7-496e-8bce-72bd1e669e99.json |    9 -
 ....4297cfc8-623f-4d32-b353-5a441c2c632f.json |    9 -
 ....42e9e133-51d4-4a91-b132-413eece2278c.json |    9 -
 ....439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json |    9 -
 ....43c6257e-4064-422d-8075-5ec55861c177.json |    9 -
 ....43df816f-7fee-4e8a-b396-9a84b2214e7b.json |    9 -
 ....43f35613-9c2f-46e9-b581-8253823fb7d8.json |    9 -
 ....44dcbb55-20f6-4737-9557-d6301fca587d.json |    9 -
 ....44e71b80-61a3-4376-83aa-3b975401942b.json |    9 -
 ....4528246c-53df-4a2b-aba1-e72a45dc542d.json |    9 -
 ....45636e82-61b1-4298-a28c-34f139b9a559.json |    3 +-
 ....4619464a-a90c-4ce6-854d-9decfb58c603.json |    9 -
 ....461af26d-2006-48e4-9aec-6eb2db31d4ef.json |    9 -
 ....4640cfe1-e531-48ab-8fb3-42655a77d667.json |    9 -
 ....465add9b-a2c7-48f1-84de-966fbbd20c27.json |    9 -
 ....46604509-5226-42af-ba63-41eeaed19074.json |    9 -
 ....467e5ad9-cca4-4700-8727-3356e81182aa.json |    9 -
 ....46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json |    9 -
 ....46b8861e-c2e4-49ef-8b79-fb14effaef6a.json |    9 -
 ....46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json |    9 -
 ....47578912-129e-4ee2-9392-a5e04f4592b4.json |    9 -
 ....47749b6f-e118-4fe5-b13d-11fe1189d77d.json |    9 -
 ....48384c9b-ce41-4356-8364-6ce566eac315.json |    9 -
 ....484a7001-9bbd-43fd-b99f-08c6370723d1.json |    9 -
 ....494f1c44-47b9-48be-9240-5a9df560fdaf.json |    9 -
 ....495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json |    9 -
 ....49a59848-0bef-4184-b9d2-5bf539c6e14c.json |    9 -
 ....49ef1a05-b415-4537-b2c7-285827e27463.json |    9 -
 ....49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json |    9 -
 ....49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json |    9 -
 ....4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json |    9 -
 ....4a2000eb-92b5-4a41-8f80-6fa1a6849855.json |    9 -
 ....4ae8b0fe-2248-4e67-b68a-816c8539528a.json |    9 -
 ....4aec9154-e02d-48cd-84e3-26de40c4d4f3.json |    9 -
 ....4af20d94-cb48-4351-a0a6-7f6a0387d105.json |    9 -
 ....4b0999e1-0348-478a-af35-1487adb15b7a.json |    9 -
 ....4b7e6128-69d3-4511-a3ca-cfba25c6e002.json |    9 -
 ....4c0b0072-4046-48aa-b481-84515c265ca0.json |    9 -
 ....4c1497cc-4638-40fc-b045-f342c4d3e5b3.json |    9 -
 ....4c3faf72-fafe-4559-a496-7a0e1ddbc948.json |    9 -
 ....4c9fd2d9-307a-43a1-8993-d422261eabd7.json |    3 +-
 ....4cdddd8a-3291-4d3f-81c9-e639f527f647.json |    9 -
 ....4d1139c2-0183-4670-af08-003694dec455.json |    9 -
 ....4d20a016-5fcf-45a6-946d-9fabe2319230.json |    9 -
 ....4d270194-23a5-445f-8b66-5ee347054400.json |    9 -
 ....4d65036f-7cf3-4ec5-be30-d20f684b820a.json |    9 -
 ....4d6d623b-afb2-4628-b716-2e6c3adac5cb.json |    9 -
 ....4de8ccc0-035a-46b9-870d-6df54238eb65.json |    9 -
 ....4df98b71-9bff-4c1d-9636-5074e31a7ace.json |    9 -
 ....4e0d5cba-13d4-497e-a320-d1236df4dce2.json |    9 -
 ....4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json |    9 -
 ....4e66101d-e2bf-4eab-904d-67c15d0466b8.json |    9 -
 ....4f2f14d0-f991-4f10-b516-20e744c08fce.json |    9 -
 ....4f6883d1-6421-4350-8ca5-7bfc57da20e9.json |    9 -
 ....4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json |    9 -
 ....5017b3a0-ce88-4884-bace-c0550e729ab5.json |    9 -
 ....5060344a-0047-40ab-8fdb-a297518478fb.json |    9 -
 ....50f6b3f3-e483-41b0-a44a-465109c160b7.json |    9 -
 ....516e5193-61d3-4f2b-885b-4e0c5e81c775.json |    9 -
 ....52049b70-5092-41ea-a749-5fde0d95b39e.json |    9 -
 ....526f1b74-c255-4dd3-ba7a-5d529545d01d.json |    9 -
 ....52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json |    9 -
 ....530d3f61-3f2c-4cb5-acc7-560d4608367f.json |    9 -
 ....5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json |    9 -
 ....53a00f10-a301-4294-ad39-916b9bc2ecd7.json |    9 -
 ....53ad5789-5fd6-41e8-b748-ce9e0bff280b.json |    9 -
 ....53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json |    9 -
 ....53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json |    9 -
 ....54108c84-c648-4c91-92c6-816711878a4f.json |    9 -
 ....54a30090-50dd-4534-af69-bc7120297bf9.json |    9 -
 ....5563fb1b-a5a1-4372-84b9-b0be87acc501.json |    9 -
 ....557b60f7-1f31-40ec-b0c8-285df7a73dd9.json |    9 -
 ....5652a68a-720a-4954-adfa-38b8e2890b8d.json |    9 -
 ....56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json |    9 -
 ....56df3f74-7cd2-4229-98b7-a593d435ad70.json |    9 -
 ....56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json |    9 -
 ....5715449a-bcad-41cd-bdb7-252d43b3ebcf.json |    9 -
 ....572f5e16-12f6-4470-a07c-06baf52c26e5.json |    9 -
 ....57f28cf3-4474-4668-8222-c430cbe9b88b.json |    9 -
 ....57f698eb-511f-4cfb-95b0-a752efab60ea.json |    9 -
 ....5920cf0f-3b24-488f-8534-53239f441f5b.json |    9 -
 ....593bdaf4-b28c-4938-b1da-03052baef361.json |    9 -
 ....597567b2-4065-4bea-890f-b8faef33f8c6.json |    9 -
 ....59ae3523-9dc9-4b61-8387-aaeb708385e6.json |    9 -
 ....59cd5b64-d1c8-4249-ab41-2106e25df543.json |    9 -
 ....59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json |    9 -
 ....5a811f7d-30af-40bd-a691-0f181f125541.json |    9 -
 ....5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe.json |    9 -
 ....5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json |    9 -
 ....5af463dd-91dc-45a4-a0bc-58212e30d402.json |    9 -
 ....5b0c25b0-761b-437b-8be3-af045c9e00bc.json |    9 -
 ....5bc7bc61-6e00-45ed-800d-e324a3ee1196.json |    9 -
 ....5c50152f-4832-4ccc-9751-31c5caeb7cc3.json |    9 -
 ....5c687659-3110-4757-b25f-ab28a7190da5.json |    9 -
 ....5c793601-f8ea-470d-8c64-3e669226e651.json |    9 -
 ....5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json |    9 -
 ....5cc109fc-0d43-4d3d-9523-b60e9b27198d.json |    9 -
 ....5d894fb5-1253-4f7e-a6ad-429618eeefef.json |    9 -
 ....5da0ef0c-154d-445e-8632-02cd3b280785.json |    9 -
 ....5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json |    9 -
 ....5df88778-175b-486a-88fb-aba781cb3b05.json |    9 -
 ....5e37f5e3-8ada-4d61-925d-5033258e441f.json |    9 -
 ....5e44dd96-8baf-47dd-9aba-79887e8c3835.json |    9 -
 ....5e643127-50de-44fa-bd1f-70f69c72ee9f.json |    9 -
 ....5e8f1843-5372-46c1-bb61-0ff493ca22ae.json |    9 -
 ....5ec8d076-631f-428e-aaf3-44fef2b83bac.json |    9 -
 ....6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json |    9 -
 ....60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json |    9 -
 ....60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json |    9 -
 ....60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json |    9 -
 ....6118c41e-e92e-4865-9f1c-64dd19e2bc40.json |    9 -
 ....6118e44d-7b4b-465e-9e7d-d2268a2e2505.json |    9 -
 ....614ba8ae-b911-4705-95f8-aafe213e00f3.json |    9 -
 ....614cb089-7e70-46ab-9f5f-dd08b529f3d0.json |    9 -
 ....624faf57-efdb-444b-85b7-fbb680ed2b73.json |    9 -
 ....62684ebe-62d0-4999-b4c3-c768e371caac.json |    9 -
 ....62d91e86-a22e-4ef9-851d-bd2b02c411a9.json |    9 -
 ....63c8df59-28ad-49c9-a605-028d5730d2b6.json |    9 -
 ....63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json |    9 -
 ....6433f0ed-d000-473b-8412-c61c8e39a80e.json |    9 -
 ....6480661e-12de-42e9-aa02-d4f37b23942d.json |    9 -
 ....64f12aa1-bb09-4c30-902f-0e94ffb936cb.json |    9 -
 ....65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json |    9 -
 ....66485e91-b88c-4a7c-8472-e593b8496e82.json |    9 -
 ....667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json |    9 -
 ....675fbf45-ad63-4685-9f22-e67e17764d9a.json |    9 -
 ....681c802d-45a6-409e-8dd1-3499184f7616.json |    9 -
 ....6842a257-a488-48aa-bb63-5663fe8e9f6a.json |    9 -
 ....68735c24-e65b-47f6-9c23-e1be5123f6a6.json |    9 -
 ....68c7948f-c44c-46e2-878f-432616c7e365.json |    9 -
 ....6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json |    9 -
 ....6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json |    9 -
 ....6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json |    9 -
 ....6c69f289-ca43-4731-9729-0341250e0591.json |    9 -
 ....6c7900af-a3e4-4402-937d-9eeda843398f.json |    9 -
 ....6cc053d6-5012-4cc7-81e8-43768a0886be.json |    9 -
 ....6ccfb609-6371-462c-b91c-4aa22d23d248.json |    9 -
 ....6cecf88f-e9d9-4954-b64e-00246781b591.json |    9 -
 ....6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json |    9 -
 ....6d13ed35-7c06-41c2-afe7-847072a84d7a.json |    9 -
 ....6d87c24a-6453-48fd-9921-cede6b1b0001.json |    9 -
 ....6e3be613-f4eb-4a14-87cd-398b0161eeda.json |    9 -
 ....6eeb79ee-eae2-41ea-ab7e-56f216daf636.json |    9 -
 ....6fb0a429-0264-4308-9436-f1115d5b108b.json |    9 -
 ....6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json |    9 -
 ....7039fa97-b91e-42c4-b974-c75ab08e4d51.json |    9 -
 ....7064860b-42de-47c3-b5ac-3560d941fe0f.json |    9 -
 ....70c71a01-1c5a-4b25-8706-d02a4284662e.json |    9 -
 ....711d2246-a181-4fe5-900d-c6e4fee3c29d.json |    9 -
 ....71802d07-348e-45af-9fed-f4f8232b9142.json |    9 -
 ....71882aa6-8635-4242-ad8c-3676d9640060.json |    9 -
 ....71e7e05f-a075-432a-bda3-db66b0e733cc.json |    9 -
 ....720b01a3-3f38-46cd-8263-112571d62c60.json |    9 -
 ....7210b16f-71c2-44c4-9dc1-4264b243c618.json |    9 -
 ....7281f569-60d5-45bd-8f3c-b01762098f77.json |    9 -
 ....72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json |    9 -
 ....72ee8411-6b32-45e5-96e1-2b749601a0ae.json |    9 -
 ....731a0026-d287-452b-96d7-aeaa3f4bec48.json |    9 -
 ....733458ea-e46c-49ed-8e8f-de95148cf0bc.json |    9 -
 ....739826e2-62a6-4726-8294-5359016f8d24.json |    9 -
 ....73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json |    9 -
 ....73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json |    9 -
 ....74447b1a-33da-45b7-aa4b-a35e2afb6803.json |    9 -
 ....74b360bb-61b3-4ed4-8942-1c21bdf630ef.json |    9 -
 ....7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json |    9 -
 ....753da3d5-1cc0-40df-8afa-101986188a96.json |    9 -
 ....75787d98-31be-4b33-a434-15d5a43c07af.json |    9 -
 ....7586b569-6528-43ba-b0a4-a55de9faafb3.json |    9 -
 ....759bb289-07cd-4103-bc90-107b7f13978d.json |    9 -
 ....75e0f02d-1c15-4877-8443-724ddfaf45f6.json |    9 -
 ....7678ac40-dfe5-43bd-98cc-37fa80affc7e.json |    9 -
 ....768ec43f-2c43-4071-9a7b-f53b5df43a33.json |    9 -
 ....771941bc-1dab-4451-ad03-1cf809b2c511.json |    9 -
 ....77377a19-7488-40de-a041-f488b3ae597c.json |    9 -
 ....781bcd5b-be77-4514-bffc-aa56d829aaff.json |    9 -
 ....78b682e0-a3be-4e49-990b-8fcc7083f6ca.json |    9 -
 ....790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json |    9 -
 ....792953b8-b5f7-44dc-8e32-d70629bf06a4.json |    9 -
 ....7980b93f-4708-4499-8047-08cb9469b4f2.json |    9 -
 ....7987b079-7f85-4303-ab3c-1338dbeaf171.json |    9 -
 ....7989ae69-0f6d-4a7d-b560-d828f76cfba4.json |    9 -
 ....79ce3fb5-ecce-4b0f-96a2-bf7094473416.json |    9 -
 ....79fdad19-834d-463e-89f6-059c0865a034.json |    9 -
 ....7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json |    9 -
 ....7a90ce1b-f0d9-443b-b143-b82562fef529.json |    9 -
 ....7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json |    9 -
 ....7b10727a-2349-4337-8e3e-9ae04f0e98c2.json |    9 -
 ....7b5a2a03-3f09-4876-8f0d-8056485566e8.json |    9 -
 ....7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json |    9 -
 ....7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json |    9 -
 ....7bc6b922-ec23-4389-8466-ffd96db33b29.json |    9 -
 ....7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json |    9 -
 ....7c632749-fb6d-4407-a8f2-aac72d959a4d.json |    9 -
 ....7d242a44-c31b-419e-848e-73eba79f962e.json |    9 -
 ....7e93586c-c6a0-410a-ae83-a1d50bc12743.json |    9 -
 ....7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json |    9 -
 ....7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json |    9 -
 ....7fce2f3b-7564-40a0-8dfc-741c66a3b993.json |    9 -
 ....7fe749a2-90b7-4d22-9dff-56eaa7adb3d5.json |    9 -
 ....805363c0-2306-47f5-b9ba-57995ebe12b3.json |    9 -
 ....80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json |    9 -
 ....8108dc36-1eb3-487b-9c03-600c49a6d11c.json |    9 -
 ....81676cf3-0b30-4619-a922-12ff3e16ba76.json |    3 +-
 ....8174931b-97d3-457f-8822-00c905fe9e1d.json |    9 -
 ....81e54ee3-c438-49d9-9450-27cafa5a7fae.json |    9 -
 ....81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json |    9 -
 ....820927f5-8c13-4b77-acb7-fae7fb55b459.json |    9 -
 ....82672338-b561-408d-a17e-902c1f37e6a9.json |    9 -
 ....82839e74-b53c-4d18-af5d-024d8f09fb3f.json |    9 -
 ....8290cf4e-cbbc-415d-b185-cbaba90d42d1.json |    9 -
 ....8293455b-3322-4e45-a24a-2d64f77db033.json |    9 -
 ....82af7a87-a737-49cd-84a0-872e820d9c91.json |    9 -
 ....82f12dce-4db3-44d8-9eff-b24feb20d568.json |    9 -
 ....82f169a8-a9cf-4705-abaa-f8e29912aa9f.json |    9 -
 ....82f39468-d922-4a18-88d4-9ef7b8b366f1.json |    9 -
 ....83443749-8720-4aa7-95b1-9c35e88f094f.json |    9 -
 ....83887671-81a2-4ffc-884c-a2d1b8ccacfa.json |    9 -
 ....83916d2b-f03f-4add-9276-5080b66925b4.json |    9 -
 ....848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json |    9 -
 ....84a6f9be-759c-42ea-815b-6b29a90b7742.json |    9 -
 ....84ede6fa-2682-4edf-8b22-ee603de0b8c7.json |    9 -
 ....85b61d26-e598-4b64-99b4-445d8d22fba5.json |    9 -
 ....862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json |    9 -
 ....86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json |    9 -
 ....8766d230-d3d4-45fb-82a6-2dbaec0c775b.json |    9 -
 ....88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json |    9 -
 ....898e3ece-caad-49b2-8486-400e653eea9d.json |    9 -
 ....8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json |    9 -
 ....8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json |    9 -
 ....8a88f79c-3593-4316-8308-8bbc9622d0ec.json |    9 -
 ....8b3f37aa-64aa-4d89-8593-52cbf781b713.json |    9 -
 ....8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json |    9 -
 ....8b84ccf4-bb4b-48fd-8009-2c2641466185.json |    9 -
 ....8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json |    9 -
 ....8be3d8d9-4e73-49db-93a6-83349ac1af05.json |    9 -
 ....8e31643d-a697-4068-8692-cdc472b96e90.json |    9 -
 ....8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json |    9 -
 ....8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json |    9 -
 ....8f2bed8f-56cb-4269-8e1d-082af6201775.json |    9 -
 ....90791de2-4132-43e3-94ea-41609f317429.json |    9 -
 ....90834219-4fa0-4db8-a34e-9a4e7b017359.json |    9 -
 ....90b4b442-bc96-4b9f-9e1b-70112f628de8.json |    9 -
 ....91985c48-6ce5-4270-8f51-478299bb9284.json |    9 -
 ....92168b2b-6e46-4548-a7b0-824c862126e3.json |    9 -
 ....92b0bd2f-d0fe-4d21-b208-961525c053ea.json |    9 -
 ....92cbe949-7398-4e53-b101-11fd2140c868.json |    9 -
 ....93b8a0b3-9766-47b1-a8bc-03975d6f3063.json |    9 -
 ....94472cb5-7302-4b56-9fb8-ad96fe2971f8.json |    9 -
 ....94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json |    9 -
 ....9533c89f-d5dd-4959-ba2c-66be5df70f60.json |    9 -
 ....95476ad8-f2dd-4667-99a5-5a5309299702.json |    9 -
 ....95a128d2-01a1-4e31-a6de-33bc7c091269.json |    9 -
 ....95f8e010-8e75-4da2-ac05-b59763888535.json |    9 -
 ....960814d3-b3bd-4a5a-a541-906c1e121902.json |    9 -
 ....97127b95-b383-490a-af5f-62e60aa11f0f.json |    9 -
 ....97ba47f0-b202-4ac4-974f-6bb9a50abb38.json |    9 -
 ....9834732b-1b38-471a-b1bb-64471b27a2ee.json |    9 -
 ....987bb32d-4dc3-49ff-bc30-2563ea769769.json |    9 -
 ....98d20258-bdbe-4286-a2d2-36dc4722cac1.json |    9 -
 ....98e6a250-a27f-41c2-8685-e80474a2d174.json |    9 -
 ....9986a906-35f4-4e86-8dc7-27b8e1f64be8.json |    9 -
 ....99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json |    9 -
 ....999e4bc2-3d7a-4d73-9f5e-62363accde44.json |    9 -
 ....99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json |    9 -
 ....9a9bcb91-1a60-4126-8a14-d477544568d1.json |    9 -
 ....9aba3fab-cb0a-4ea1-a439-9ff419b23841.json |    9 -
 ....9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json |    9 -
 ....9b65d27f-65f6-4913-b142-a1a128ebf21f.json |    9 -
 ....9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json |    9 -
 ....9cc91e25-0d1b-4a93-b367-7da047fce99e.json |    9 -
 ....9d0e577d-eca2-4b05-9266-00f94901ae69.json |    9 -
 ....9d57dff8-de30-4e32-8278-c5a947ef8c25.json |    9 -
 ....9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json |    9 -
 ....9dcd7b33-b2bc-41b1-9d17-f7536a670343.json |    9 -
 ....9deec245-c96a-44f5-a54c-95f61611051d.json |    9 -
 ....9ecc8bf3-5bf6-4713-9868-c6059db4d432.json |    9 -
 ....9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json |    9 -
 ....9f51855e-e397-420d-9ee8-e0780937cc24.json |    9 -
 ....9f663595-3a33-4503-a86e-c15b8e3113a0.json |    9 -
 ....9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json |    9 -
 ....9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json |    9 -
 ....9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json |    9 -
 ....a0631edf-ffac-4381-92b6-98e76e980131.json |    9 -
 ....a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json |    9 -
 ....a1dc0ff4-ae77-4126-a499-1f39e9c08115.json |    9 -
 ....a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json |    9 -
 ....a2b118ea-d319-4808-83f6-94ad79c302f2.json |    9 -
 ....a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json |    9 -
 ....a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json |    9 -
 ....a33ea357-381e-4171-9808-85c90c7602c7.json |    9 -
 ....a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json |    9 -
 ....a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json |    9 -
 ....a47d5366-6212-48d7-98b0-5ccc2506052c.json |    9 -
 ....a4efc095-f78d-45ae-854d-fc52c8afa41b.json |    9 -
 ....a504768a-c5bf-4660-986d-07590f6ee816.json |    9 -
 ....a520e72c-3fdf-476e-bdd7-0120e9e161ea.json |    9 -
 ....a564439d-3102-47dc-8f4b-70b080383552.json |    9 -
 ....a564cfaa-2b13-4739-af74-5fde2b75b1a0.json |    9 -
 ....a5a69bcd-a7f7-4957-ab0b-393437e4055d.json |    9 -
 ....a5edab26-6910-43c9-ba33-3f482849596a.json |    9 -
 ....a699f864-3453-4f53-92d5-b394bfaebef7.json |    9 -
 ....a76cc0ca-e585-42b5-8ec9-369b95da3eff.json |    9 -
 ....a7ee1363-3e3b-4733-b302-0c85aad15aea.json |    9 -
 ....a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json |    9 -
 ....a8753236-c6ec-4eab-88c0-cf1939cf0333.json |    9 -
 ....a8a1b0cc-8372-4285-a655-bdd1f77226d3.json |    9 -
 ....a8d650da-84f6-4d81-9384-bb26228f3dcb.json |    9 -
 ....a8e2e580-5b20-451d-80ef-7ee19aea62ec.json |    9 -
 ....a8f06c67-81eb-471c-9081-0648c9400e27.json |    9 -
 ....a9061df6-daf5-47f3-a217-39df555f9762.json |    9 -
 ....a96b6197-2490-4e22-8705-d372ee76664b.json |    9 -
 ....a97003d7-c86d-41a3-8655-ca35c6912d42.json |    9 -
 ....a986dbd9-92fb-45fc-9769-bf75542c9b49.json |    9 -
 ....a99289d5-ad45-4e3d-9d03-031569f7bf70.json |    9 -
 ....aa4b919c-76e4-43db-8962-2b2cacd33267.json |    9 -
 ....aa72d773-765e-42bb-bf5b-f070a97f5884.json |    9 -
 ....aa830670-f0ba-4069-98c1-c71a4e8c7d94.json |    9 -
 ....aba09cf2-f67c-4056-b503-5a53399e634b.json |    9 -
 ....aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json |    9 -
 ....abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json |    9 -
 ....abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json |    9 -
 ....ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json |    9 -
 ....ac11bd02-625e-4eef-83f3-6ed1f24485ff.json |    9 -
 ....ac349786-bc86-465d-9374-a277d15a892c.json |    9 -
 ....ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json |    9 -
 ....acdd68c3-34bb-4a9b-9feb-1c9580852eef.json |    9 -
 ....ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json |    9 -
 ....af1271f1-d7b4-446b-8fb0-1d94eee5846f.json |    9 -
 ....af570204-edaa-41d8-af54-5136ec8f0954.json |    9 -
 ....afe43360-ecca-472a-b501-062f898650a5.json |    9 -
 ....b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json |    9 -
 ....b0daabcd-f51d-4208-9742-4a4512e2bbb5.json |    9 -
 ....b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json |    9 -
 ....b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json |    9 -
 ....b2160fad-74d6-425b-9c76-d3b662807dbf.json |    9 -
 ....b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json |    9 -
 ....b2f30b62-d067-4e73-9fab-db655e9409d6.json |    9 -
 ....b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json |    9 -
 ....b38b290a-1ce1-481d-987b-9683245740da.json |    9 -
 ....b3a28a86-02c5-45ea-8a51-32508cd34b7d.json |    9 -
 ....b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json |    9 -
 ....b43ce1ab-0d83-463f-9421-d20aaacdd833.json |    9 -
 ....b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json |    9 -
 ....b475d325-7c60-4115-b465-f1d691ab75b0.json |    9 -
 ....b48769b5-0c48-4bee-a008-6a760db421de.json |    9 -
 ....b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json |    9 -
 ....b51a5709-0942-4244-b857-16e5b43ff2fb.json |    9 -
 ....b51b7b96-fe84-43ed-9181-3c590a4015ef.json |    9 -
 ....b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json |    9 -
 ....b54ead56-01d3-442f-9689-c422f5be5e27.json |    9 -
 ....b5b7cf41-fa32-4c63-a182-9b048c290f05.json |    9 -
 ....b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json |    9 -
 ....b61104ef-e514-4518-bec8-a10b1dcbaa4a.json |    9 -
 ....b66e30f0-28a1-459d-a0d2-193d1772ece1.json |    9 -
 ....b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json |    3 +-
 ....b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json |    9 -
 ....b8243d12-2068-42e4-bb31-6f0b5add5e5a.json |    9 -
 ....b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json |    9 -
 ....b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json |    9 -
 ....b892433b-6318-4716-9bb8-fc13e6a55fbb.json |    9 -
 ....b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json |    9 -
 ....b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json |    9 -
 ....b92a815e-5d21-4adc-8a1f-378ba6be23c8.json |    9 -
 ....ba009e81-1bbd-44dd-928f-21681d2dc1ff.json |    9 -
 ....ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json |    9 -
 ....ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json |    9 -
 ....baa04acc-64aa-435e-b012-1af94d0b0cf1.json |    9 -
 ....baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json |    9 -
 ....bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json |    9 -
 ....bbbe114e-124b-40cb-a884-9edd94353bba.json |    9 -
 ....bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json |    9 -
 ....bc747939-87ef-409b-bb1e-48c94863579c.json |    9 -
 ....bcfa962f-c9ea-4346-b10c-4317932097c7.json |    9 -
 ....bd0ab1a7-853f-44dd-a29f-967b3808e132.json |    9 -
 ....bd892fac-0009-4886-9ced-5fbffab2d540.json |    9 -
 ....bdb5298b-feed-4876-9d61-de877c6534da.json |    9 -
 ....be0c00dd-5149-4fe2-a17d-03564255330c.json |    9 -
 ....be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json |    9 -
 ....be331d8c-cc1c-404d-9764-7304a5309c80.json |    9 -
 ....befd9d9c-edd5-483e-b378-b3867451769d.json |    9 -
 ....bf04ca43-aaa4-4877-a1df-80042934a312.json |    9 -
 ....bfd168f9-71fe-41f9-a4f6-60ce897917a7.json |    9 -
 ....c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json |    9 -
 ....c027d77e-97c4-43eb-99cd-672dedcf8f14.json |    9 -
 ....c0d7b8ea-8a29-4d83-937d-52d951ce250b.json |    9 -
 ....c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json |    9 -
 ....c1064abb-f7f8-4e4d-bfb7-9842271b0938.json |    9 -
 ....c15ee1ad-adb1-4017-a5ef-a56071197a38.json |    9 -
 ....c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json |    9 -
 ....c1bc355c-4dfb-4ea0-a98e-9801871107f2.json |    9 -
 ....c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json |    9 -
 ....c2315804-efa4-4b5e-ae67-41457d8cd8c8.json |    9 -
 ....c28c0731-5f76-4b55-8326-a584e385e8cb.json |    9 -
 ....c2b27288-d156-4d16-ac94-cf431548f34a.json |    9 -
 ....c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json |    9 -
 ....c2ed3f01-0761-4b2a-a845-fccd30c84d57.json |    9 -
 ....c373d98a-0558-4f14-a58f-e253e43c3435.json |    9 -
 ....c4bece9a-e11b-43a8-861a-2a64a12e5a91.json |    9 -
 ....c58749a0-bec2-415b-aa25-33eca5cce8b7.json |    9 -
 ....c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json |    9 -
 ....c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json |    9 -
 ....c68956b5-95b2-48f4-873e-aabc074a5497.json |    9 -
 ....c6bc2e2d-1817-4856-9e5d-5a5136963485.json |    9 -
 ....c72430aa-0c6d-4cf8-8a43-812d245ea73d.json |    9 -
 ....c7423f08-eb5a-4602-b85f-9b4691efe3ab.json |    9 -
 ....c765b1bf-87ee-4324-843a-8ca578ef2f69.json |    9 -
 ....c798ba8d-2b67-459b-994d-97e286d33ca9.json |    9 -
 ....c7ad84af-f5c8-4ff8-92cd-873528acc623.json |    9 -
 ....c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json |    9 -
 ....c841583c-4e19-4eb2-898a-d7e61859daad.json |    9 -
 ....c87318b5-eb27-4eba-a3d4-a5328f362c9d.json |    9 -
 ....c8d78160-4a98-441c-a707-c1fde53f9044.json |    9 -
 ....c8e5ab46-3320-4a41-b322-11b08d92aeaa.json |    9 -
 ....c8fd5532-9338-4ea0-933f-798ce5782931.json |    9 -
 ....c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json |    9 -
 ....c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json |    9 -
 ....c9c11eda-6318-4e7c-b108-a01feea60e45.json |    9 -
 ....c9c4743b-a803-47b3-8405-f6aeb34a279b.json |    9 -
 ....c9ccd7f8-4727-49fa-9481-4507e7986fd9.json |    9 -
 ....ca145f06-f0f5-4538-978f-0af3f1c32d73.json |    9 -
 ....ca4340a2-6371-457a-8e95-885adbcdc256.json |    9 -
 ....ca7093b6-288d-4326-b755-cc96e0c262dc.json |    9 -
 ....cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json |    9 -
 ....cb4c03ee-f173-483a-b3b6-f9de065a7d04.json |    9 -
 ....cb59660e-e499-4b18-a779-46fed92d0879.json |    9 -
 ....cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json |    9 -
 ....cbc726a3-93f3-41e2-ba6b-9c591096eda9.json |    9 -
 ....cbd099ee-0b05-402b-803d-9753a84a9e83.json |    9 -
 ....cbfe0f07-d0fc-46d0-950f-167a091e020d.json |    9 -
 ....cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json |    9 -
 ....cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json |    9 -
 ....cd3df6ff-471f-4b56-af7c-9b9a6588367e.json |    9 -
 ....cd57083c-1262-450a-aab2-b03fa36456d2.json |    9 -
 ....cdd7350c-f06a-410e-841c-06acf0dc312c.json |    9 -
 ....cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json |    9 -
 ....ce877341-4025-4610-89b6-f1f4c9bfe5af.json |    9 -
 ....ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json |    9 -
 ....cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json |    9 -
 ....cfb22ecc-4401-41bf-8ed5-4a9321601a17.json |    9 -
 ....cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json |    9 -
 ....cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json |    9 -
 ....d047a824-fbb1-40b0-8391-ceba0cc250f5.json |    9 -
 ....d06d1e0c-2e71-4928-922f-c587f712a8e9.json |    9 -
 ....d0cabfc7-0a42-4d21-a028-eb1220bfece8.json |    9 -
 ....d0ee1aae-f2fc-49d2-8865-d4912209eeea.json |    9 -
 ....d146f785-7ae1-4728-8d90-20b9cbf8f35d.json |    9 -
 ....d1633911-dff9-4079-a0cb-5efe70d9a1fb.json |    9 -
 ....d1a650c6-fd8f-4509-801b-10c14f10344e.json |    9 -
 ....d31baf5d-0590-4126-aa80-85de9beed94f.json |    9 -
 ....d33493db-20b9-4946-94a1-bc2abfb6b998.json |    9 -
 ....d33e4704-c07e-421e-8227-f3f74e9f57ff.json |    9 -
 ....d344a28e-aa79-4533-8eac-f112926fe811.json |    9 -
 ....d3d14705-ef6a-4827-afad-bb2963dac369.json |    9 -
 ....d3e4d075-4050-46af-bfd3-94944eaae35b.json |    9 -
 ....d3fe0eae-7883-4fe6-9a98-747b53d860ca.json |    9 -
 ....d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json |    9 -
 ....d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json |    9 -
 ....d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json |    9 -
 ....d421a5a4-8025-4809-8a30-68c723e46af6.json |    9 -
 ....d487d829-d35c-4c4f-b4e8-af804b29463e.json |    9 -
 ....d4beee99-ab37-4663-b331-4de9f42ec333.json |    9 -
 ....d4e3757c-36f7-45f7-a679-6292e8300200.json |    9 -
 ....d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json |    9 -
 ....d592f939-eaf5-4c33-89f6-8af3b36d338f.json |    9 -
 ....d5957f63-fc2f-4046-864c-9e01c3978a6c.json |    9 -
 ....d5d38a64-f226-42e0-8691-6c1b128435bf.json |    3 +-
 ....d613376e-133d-4730-86f1-70661d24c7ff.json |    9 -
 ....d6363924-78ee-4086-8cf0-41e07c030fd4.json |    9 -
 ....d64f0811-a486-4194-99e8-67d21263cb7f.json |    9 -
 ....d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json |    9 -
 ....d753217f-2d8f-431d-850c-d54597b46b76.json |    9 -
 ....d783263e-b457-4785-b15c-ce631faf3192.json |    9 -
 ....d7924931-d38d-4c59-a987-6a10f48a18c9.json |    9 -
 ....d7a77497-05c5-4a42-8ecc-e0f171bb8097.json |    9 -
 ....d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json |    9 -
 ....d7c36fee-2434-4c3c-95d3-df1303603a35.json |    9 -
 ....d7d864f9-d3b6-4682-8e86-8d1f7c6f774e.json |    3 +-
 ....d7d93932-2902-44e3-94d3-331725ce1859.json |    9 -
 ....d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json |    9 -
 ....d9520278-39f8-4cdb-9f94-632cabb49acd.json |    9 -
 ....d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json |    9 -
 ....d9c346b8-279b-4432-9d3a-539a576da4e2.json |    9 -
 ....d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json |    9 -
 ....da3412f8-9a33-4395-a75e-4d107d2557a4.json |    9 -
 ....da4dbacd-671b-45ee-b70e-58aa16de7d8f.json |    9 -
 ....da62317b-2539-43bd-8db0-94bddb14174e.json |    9 -
 ....daaf3365-9511-4f12-a744-2a8c37a655b9.json |    9 -
 ....dab13df7-2835-407a-90c5-f5574585718b.json |    9 -
 ....dab1657a-80c4-4b6c-b7c5-28b874fff857.json |    9 -
 ....dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json |    9 -
 ....dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json |    9 -
 ....db312e00-7a9d-492d-a6db-7298848e06b2.json |    9 -
 ....dbb959b1-390d-45e8-b080-097a313545d8.json |    9 -
 ....dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json |    9 -
 ....dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json |    9 -
 ....dd462165-113a-4b0e-b566-a242cfd475dd.json |    9 -
 ....dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json |    9 -
 ....de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json |    9 -
 ....de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json |    9 -
 ....dea5d550-6603-412d-b1a6-eec70c353b96.json |    9 -
 ....deaafd9d-8951-41fb-bc84-745a611f3b1b.json |    9 -
 ....dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json |    9 -
 ....defbeab8-28ca-4444-b09b-5121de794602.json |    9 -
 ....df0a8efc-bfd5-4c57-adc6-08d63794041e.json |    9 -
 ....df628b2c-64d0-4b35-bbde-c3536bcb05bc.json |    9 -
 ....df8406e6-56bf-4de6-a8e0-64caf5b52058.json |    9 -
 ....dfe4489a-7d64-4368-b86e-e35180377c15.json |    9 -
 ....dfe87217-dc3b-413c-9e42-912386be5d5f.json |    9 -
 ....e00e0cdc-8668-4ca5-86e0-1219332907c0.json |    9 -
 ....e01efd03-7851-41b8-a34d-7b7a56d77d31.json |    9 -
 ....e0c0707d-b542-4aae-a8b4-8633673fd520.json |    9 -
 ....e0d6060d-596b-460f-9cac-22ef16a947b6.json |    9 -
 ....e11ce42f-0d2e-4afb-9017-521fde9521a2.json |    9 -
 ....e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json |    9 -
 ....e179e840-bd5c-45b3-8bae-2b3706861bb3.json |    9 -
 ....e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json |    9 -
 ....e2679ec1-9cf5-483f-86e0-f176db3daae4.json |    9 -
 ....e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json |    9 -
 ....e2991eb4-1aee-4d04-9045-989159a9b64f.json |    9 -
 ....e3391a68-8501-49ac-a509-c7a1ac579193.json |    9 -
 ....e35f213b-1b5c-453e-bf2d-fa542a37aac3.json |    9 -
 ....e52fda31-17cc-4379-b8cb-1a22c9e11601.json |    9 -
 ....e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json |    9 -
 ....e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json |    9 -
 ....e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json |    9 -
 ....e8275304-6db2-435e-bd89-9810a1f51490.json |    9 -
 ....e837c37b-a3b6-49bd-9af7-e3bc771c4786.json |    9 -
 ....e88621ad-4a3d-481e-b292-b710f0756313.json |    9 -
 ....e88b4449-20b6-4165-880b-6d34b9579781.json |    9 -
 ....e91d28ca-1730-4560-82ab-205175ca2bf9.json |    9 -
 ....ea06edab-74a5-42d4-add9-d4dce3d0f792.json |    9 -
 ....ea81e659-48e0-4eaf-ae3b-a30012102d0e.json |    9 -
 ....eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json |    9 -
 ....ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json |    9 -
 ....ebf479a8-f93c-4972-ae90-8b59a0ca8081.json |    9 -
 ....ec354679-9830-4361-b0eb-16e976e888ce.json |    9 -
 ....ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json |    9 -
 ....ec6af399-d960-4715-92c5-760fce33d803.json |    9 -
 ....ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json |    9 -
 ....ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json |    9 -
 ....ed95d76b-0dba-46a3-aa18-2d5f70b07511.json |    9 -
 ....edacb021-6f94-4f6f-a39b-4362609caea0.json |    9 -
 ....edd8befd-440a-479a-9759-c8f90b4a2528.json |    9 -
 ....ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json |    9 -
 ....ee81b821-f2be-4dce-a119-7e421bbc7e04.json |    9 -
 ....ee874ddb-dd03-4843-8a61-202936b2a845.json |    9 -
 ....eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json |    9 -
 ....eef4147e-e47a-411e-a7de-eb67638dc6bb.json |    9 -
 ....ef157ce9-4fc5-4441-8592-989b1fcd61b8.json |    9 -
 ....efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json |    9 -
 ....f076aa19-9261-4d21-8fbc-f330d9d4e87a.json |    9 -
 ....f0fe2425-0fca-41a3-8ca8-67953798b7a5.json |    9 -
 ....f2008694-9d04-4952-b40b-ae2fd880d9fe.json |    9 -
 ....f2220fec-35de-40a7-be72-9b3b643e15df.json |    9 -
 ....f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json |    9 -
 ....f245814b-3957-4c84-82fb-47134c3edd24.json |    9 -
 ....f33ae168-76dc-4662-9998-5f6729d19523.json |    9 -
 ....f343899f-5778-4b23-a97e-bda411656646.json |    9 -
 ....f3454ba6-e5bd-4d85-838a-b838f8687ce7.json |    9 -
 ....f38ff989-2a23-4834-9b3a-edc7d016d66d.json |    9 -
 ....f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json |    9 -
 ....f3e69f27-6b57-434e-a50a-308e99838872.json |    9 -
 ....f451e001-95a4-4c6c-94e0-cdbcda175b7b.json |    9 -
 ....f4845b86-e79e-4382-8d78-2376221f9324.json |    9 -
 ....f4b83f92-eda0-4174-a9e1-45a94d97fb05.json |    9 -
 ....f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json |    9 -
 ....f4e48486-b923-43bd-a250-d6db2aeb9411.json |    9 -
 ....f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json |    9 -
 ....f5117c12-30f6-4bb7-8e7d-32210d6d278e.json |    9 -
 ....f529894e-5912-4e77-91a3-d78b9cbf2584.json |    9 -
 ....f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json |    9 -
 ....f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json |    9 -
 ....f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json |    9 -
 ....f722e13d-4831-4153-9ba1-0243c3387b8c.json |    9 -
 ....f72f7027-2ca5-4473-a8f1-2047d8b400fd.json |    9 -
 ....f7411fd1-46e2-4056-be8c-89475875f768.json |    9 -
 ....f78a64e6-14a7-4654-95ab-04b1d1bb7318.json |    9 -
 ....f86b9901-80da-4765-aa94-3bf6025efde5.json |    9 -
 ....f8f9967c-cb22-4c57-b68d-629ca40f3d90.json |    9 -
 ....f98589c7-10e8-4903-b801-f2a42135b190.json |    9 -
 ....f9a1b695-bf65-4098-abce-c8593a427731.json |    9 -
 ....f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json |    9 -
 ....fa30b239-baa9-46ec-9ea2-4914280dd13b.json |    9 -
 ....fa7b57ee-9af5-49ce-9522-66d54642e219.json |    9 -
 ....fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json |    9 -
 ....faff03ba-71b2-4b4b-a107-9e7f499eeefd.json |    9 -
 ....fb679f64-e559-4319-9a36-b508bc870415.json |    9 -
 ....fb85bcd0-833b-4e23-bab7-4e9ae86075df.json |    9 -
 ....fb950c25-8deb-439d-a5c8-1a24b64cd5be.json |    9 -
 ....fba9e05d-92e9-4699-a6ad-dafae26a1670.json |    9 -
 ....fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json |    9 -
 ....fcd0906c-5337-4f6e-8938-c71c2fe672d8.json |    9 -
 ....fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json |    9 -
 ....fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json |    9 -
 ....fe168e9f-37bf-4cb4-b42d-1db79938223b.json |    9 -
 ....fe407991-a896-410c-9223-51a7ad43d4d2.json |    9 -
 ....fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json |    9 -
 ....fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json |    9 -
 ....fe815eab-027d-49db-afd1-e4a21387b2fe.json |    9 -
 ....ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json |    9 -
 ....ffa93a1b-f239-4c0a-9f34-50cd6532f353.json |    9 -
 851 files changed, 840 insertions(+), 10348 deletions(-)
 delete mode 100644 config/sync/core.entity_view_mode.feeds_feed.full.yml
 delete mode 100644 config/sync/feeds.feed_type.daily_emails.yml
 delete mode 100644 config/sync/feeds.settings.yml
 delete mode 100644 config/sync/field.field.node.daily_email.feeds_item.yml
 delete mode 100644 config/sync/field.storage.node.feeds_item.yml
 delete mode 100644 config/sync/system.action.feeds_feed_clear_action.yml
 delete mode 100644 config/sync/system.action.feeds_feed_delete_action.yml
 delete mode 100644 config/sync/system.action.feeds_feed_import_action.yml
 delete mode 100644 config/sync/views.view.feeds_feed.yml
 delete mode 100644 content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json

diff --git a/composer.json b/composer.json
index 3d317b649..8e5a067d5 100644
--- a/composer.json
+++ b/composer.json
@@ -22,7 +22,6 @@
         "drupal/core-project-message": "^11.1",
         "drupal/core-recommended": "^11.1",
         "drupal/drupal_cms_seo_tools": "^1.1",
-        "drupal/feeds": "^3.0",
         "drupal/markdown_easy": "^1.0",
         "drupal/paragraphs": "^1.19",
         "drupal/pathauto": "^1.13",
diff --git a/composer.lock b/composer.lock
index ff3d79d07..66b7b7215 100644
--- a/composer.lock
+++ b/composer.lock
@@ -4,7 +4,7 @@
         "Read more about it at https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies",
         "This file is @generated automatically"
     ],
-    "content-hash": "377f681cb29972bd5a9a2bf00efd10f7",
+    "content-hash": "7befc6549cf5eab7ceaa7aa2bca95acd",
     "packages": [
         {
             "name": "asm89/stack-cors",
@@ -2152,116 +2152,6 @@
                 "source": "https://git.drupalcode.org/project/entity_reference_revisions"
             }
         },
-        {
-            "name": "drupal/feeds",
-            "version": "3.0.0",
-            "source": {
-                "type": "git",
-                "url": "https://git.drupalcode.org/project/feeds.git",
-                "reference": "8.x-3.0"
-            },
-            "dist": {
-                "type": "zip",
-                "url": "https://ftp.drupal.org/files/projects/feeds-8.x-3.0.zip",
-                "reference": "8.x-3.0",
-                "shasum": "d6cbfdcc6ece690fe3b20dd62285eea91113089a"
-            },
-            "require": {
-                "drupal/core": "^10.1 || ^11",
-                "laminas/laminas-feed": "^2.22"
-            },
-            "require-dev": {
-                "drupal/pathauto": "^1.0",
-                "megachriz/drupalbook": "^1.0 || ^2.0"
-            },
-            "type": "drupal-module",
-            "extra": {
-                "drupal": {
-                    "version": "8.x-3.0",
-                    "datestamp": "1736951425",
-                    "security-coverage": {
-                        "status": "covered",
-                        "message": "Covered by Drupal's security advisory policy"
-                    }
-                },
-                "drush": {
-                    "services": {
-                        "drush.services.yml": ">=9"
-                    }
-                }
-            },
-            "notification-url": "https://packages.drupal.org/8/downloads",
-            "license": [
-                "GPL-2.0-or-later"
-            ],
-            "authors": [
-                {
-                    "name": "alex_b",
-                    "homepage": "https://www.drupal.org/user/53995"
-                },
-                {
-                    "name": "dave reid",
-                    "homepage": "https://www.drupal.org/user/53892"
-                },
-                {
-                    "name": "e2thex",
-                    "homepage": "https://www.drupal.org/user/189123"
-                },
-                {
-                    "name": "febbraro",
-                    "homepage": "https://www.drupal.org/user/43670"
-                },
-                {
-                    "name": "franz",
-                    "homepage": "https://www.drupal.org/user/581844"
-                },
-                {
-                    "name": "Ian Ward",
-                    "homepage": "https://www.drupal.org/user/4736"
-                },
-                {
-                    "name": "jmiccolis",
-                    "homepage": "https://www.drupal.org/user/31731"
-                },
-                {
-                    "name": "joelpittet",
-                    "homepage": "https://www.drupal.org/user/160302"
-                },
-                {
-                    "name": "kking",
-                    "homepage": "https://www.drupal.org/user/24399"
-                },
-                {
-                    "name": "megachriz",
-                    "homepage": "https://www.drupal.org/user/654114"
-                },
-                {
-                    "name": "tobby",
-                    "homepage": "https://www.drupal.org/user/154797"
-                },
-                {
-                    "name": "twistor",
-                    "homepage": "https://www.drupal.org/user/473738"
-                },
-                {
-                    "name": "Will White",
-                    "homepage": "https://www.drupal.org/user/32237"
-                },
-                {
-                    "name": "yhahn",
-                    "homepage": "https://www.drupal.org/user/264833"
-                }
-            ],
-            "description": "Aggregates RSS/Atom/RDF feeds, imports CSV files and more.",
-            "homepage": "https://www.drupal.org/project/feeds",
-            "keywords": [
-                "Drupal"
-            ],
-            "support": {
-                "source": "https://git.drupalcode.org/project/feeds",
-                "issues": "https://www.drupal.org/project/issues/feeds"
-            }
-        },
         {
             "name": "drupal/field_group",
             "version": "3.6.0",
@@ -4243,206 +4133,6 @@
             ],
             "time": "2025-03-27T12:30:47+00:00"
         },
-        {
-            "name": "laminas/laminas-escaper",
-            "version": "2.17.0",
-            "source": {
-                "type": "git",
-                "url": "https://github.com/laminas/laminas-escaper.git",
-                "reference": "df1ef9503299a8e3920079a16263b578eaf7c3ba"
-            },
-            "dist": {
-                "type": "zip",
-                "url": "https://api.github.com/repos/laminas/laminas-escaper/zipball/df1ef9503299a8e3920079a16263b578eaf7c3ba",
-                "reference": "df1ef9503299a8e3920079a16263b578eaf7c3ba",
-                "shasum": ""
-            },
-            "require": {
-                "ext-ctype": "*",
-                "ext-mbstring": "*",
-                "php": "~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0"
-            },
-            "conflict": {
-                "zendframework/zend-escaper": "*"
-            },
-            "require-dev": {
-                "infection/infection": "^0.29.8",
-                "laminas/laminas-coding-standard": "~3.0.1",
-                "phpunit/phpunit": "^10.5.45",
-                "psalm/plugin-phpunit": "^0.19.2",
-                "vimeo/psalm": "^6.6.2"
-            },
-            "type": "library",
-            "autoload": {
-                "psr-4": {
-                    "Laminas\\Escaper\\": "src/"
-                }
-            },
-            "notification-url": "https://packagist.org/downloads/",
-            "license": [
-                "BSD-3-Clause"
-            ],
-            "description": "Securely and safely escape HTML, HTML attributes, JavaScript, CSS, and URLs",
-            "homepage": "https://laminas.dev",
-            "keywords": [
-                "escaper",
-                "laminas"
-            ],
-            "support": {
-                "chat": "https://laminas.dev/chat",
-                "docs": "https://docs.laminas.dev/laminas-escaper/",
-                "forum": "https://discourse.laminas.dev",
-                "issues": "https://github.com/laminas/laminas-escaper/issues",
-                "rss": "https://github.com/laminas/laminas-escaper/releases.atom",
-                "source": "https://github.com/laminas/laminas-escaper"
-            },
-            "funding": [
-                {
-                    "url": "https://funding.communitybridge.org/projects/laminas-project",
-                    "type": "community_bridge"
-                }
-            ],
-            "time": "2025-05-06T19:29:36+00:00"
-        },
-        {
-            "name": "laminas/laminas-feed",
-            "version": "2.23.1",
-            "source": {
-                "type": "git",
-                "url": "https://github.com/laminas/laminas-feed.git",
-                "reference": "7c6755695cdca18f983d8a116bfa6a55439b1a94"
-            },
-            "dist": {
-                "type": "zip",
-                "url": "https://api.github.com/repos/laminas/laminas-feed/zipball/7c6755695cdca18f983d8a116bfa6a55439b1a94",
-                "reference": "7c6755695cdca18f983d8a116bfa6a55439b1a94",
-                "shasum": ""
-            },
-            "require": {
-                "ext-dom": "*",
-                "ext-libxml": "*",
-                "laminas/laminas-escaper": "^2.9",
-                "laminas/laminas-stdlib": "^3.6",
-                "php": "~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0"
-            },
-            "conflict": {
-                "laminas/laminas-servicemanager": "<3.3",
-                "zendframework/zend-feed": "*"
-            },
-            "require-dev": {
-                "laminas/laminas-cache": "^2.13.2 || ^3.12",
-                "laminas/laminas-cache-storage-adapter-memory": "^1.1.0 || ^2.3",
-                "laminas/laminas-coding-standard": "~2.5.0",
-                "laminas/laminas-db": "^2.18",
-                "laminas/laminas-http": "^2.19",
-                "laminas/laminas-servicemanager": "^3.22.1",
-                "laminas/laminas-validator": "^2.46",
-                "phpunit/phpunit": "^10.5.5",
-                "psalm/plugin-phpunit": "^0.19.0",
-                "psr/http-message": "^2.0",
-                "vimeo/psalm": "^5.18.0"
-            },
-            "suggest": {
-                "laminas/laminas-cache": "Laminas\\Cache component, for optionally caching feeds between requests",
-                "laminas/laminas-db": "Laminas\\Db component, for use with PubSubHubbub",
-                "laminas/laminas-http": "Laminas\\Http for PubSubHubbub, and optionally for use with Laminas\\Feed\\Reader",
-                "laminas/laminas-servicemanager": "Laminas\\ServiceManager component, for easily extending ExtensionManager implementations",
-                "laminas/laminas-validator": "Laminas\\Validator component, for validating email addresses used in Atom feeds and entries when using the Writer subcomponent",
-                "psr/http-message": "PSR-7 ^1.0.1, if you wish to use Laminas\\Feed\\Reader\\Http\\Psr7ResponseDecorator"
-            },
-            "type": "library",
-            "autoload": {
-                "psr-4": {
-                    "Laminas\\Feed\\": "src/"
-                }
-            },
-            "notification-url": "https://packagist.org/downloads/",
-            "license": [
-                "BSD-3-Clause"
-            ],
-            "description": "provides functionality for creating and consuming RSS and Atom feeds",
-            "homepage": "https://laminas.dev",
-            "keywords": [
-                "atom",
-                "feed",
-                "laminas",
-                "rss"
-            ],
-            "support": {
-                "chat": "https://laminas.dev/chat",
-                "docs": "https://docs.laminas.dev/laminas-feed/",
-                "forum": "https://discourse.laminas.dev",
-                "issues": "https://github.com/laminas/laminas-feed/issues",
-                "rss": "https://github.com/laminas/laminas-feed/releases.atom",
-                "source": "https://github.com/laminas/laminas-feed"
-            },
-            "funding": [
-                {
-                    "url": "https://funding.communitybridge.org/projects/laminas-project",
-                    "type": "community_bridge"
-                }
-            ],
-            "time": "2025-05-13T09:35:51+00:00"
-        },
-        {
-            "name": "laminas/laminas-stdlib",
-            "version": "3.20.0",
-            "source": {
-                "type": "git",
-                "url": "https://github.com/laminas/laminas-stdlib.git",
-                "reference": "8974a1213be42c3e2f70b2c27b17f910291ab2f4"
-            },
-            "dist": {
-                "type": "zip",
-                "url": "https://api.github.com/repos/laminas/laminas-stdlib/zipball/8974a1213be42c3e2f70b2c27b17f910291ab2f4",
-                "reference": "8974a1213be42c3e2f70b2c27b17f910291ab2f4",
-                "shasum": ""
-            },
-            "require": {
-                "php": "~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0"
-            },
-            "conflict": {
-                "zendframework/zend-stdlib": "*"
-            },
-            "require-dev": {
-                "laminas/laminas-coding-standard": "^3.0",
-                "phpbench/phpbench": "^1.3.1",
-                "phpunit/phpunit": "^10.5.38",
-                "psalm/plugin-phpunit": "^0.19.0",
-                "vimeo/psalm": "^5.26.1"
-            },
-            "type": "library",
-            "autoload": {
-                "psr-4": {
-                    "Laminas\\Stdlib\\": "src/"
-                }
-            },
-            "notification-url": "https://packagist.org/downloads/",
-            "license": [
-                "BSD-3-Clause"
-            ],
-            "description": "SPL extensions, array utilities, error handlers, and more",
-            "homepage": "https://laminas.dev",
-            "keywords": [
-                "laminas",
-                "stdlib"
-            ],
-            "support": {
-                "chat": "https://laminas.dev/chat",
-                "docs": "https://docs.laminas.dev/laminas-stdlib/",
-                "forum": "https://discourse.laminas.dev",
-                "issues": "https://github.com/laminas/laminas-stdlib/issues",
-                "rss": "https://github.com/laminas/laminas-stdlib/releases.atom",
-                "source": "https://github.com/laminas/laminas-stdlib"
-            },
-            "funding": [
-                {
-                    "url": "https://funding.communitybridge.org/projects/laminas-project",
-                    "type": "community_bridge"
-                }
-            ],
-            "time": "2024-10-29T13:46:07+00:00"
-        },
         {
             "name": "laravel/prompts",
             "version": "v0.3.5",
diff --git a/config/sync/core.entity_form_display.node.daily_email.default.yml b/config/sync/core.entity_form_display.node.daily_email.default.yml
index 4c90c6b1a..5bf61cee9 100644
--- a/config/sync/core.entity_form_display.node.daily_email.default.yml
+++ b/config/sync/core.entity_form_display.node.daily_email.default.yml
@@ -4,7 +4,6 @@ status: true
 dependencies:
   config:
     - field.field.node.daily_email.body
-    - field.field.node.daily_email.feeds_item
     - node.type.daily_email
   module:
     - path
@@ -80,5 +79,9 @@ content:
       size: 60
       placeholder: ''
     third_party_settings: {  }
-hidden:
-  feeds_item: true
+  url_redirects:
+    weight: 50
+    region: content
+    settings: {  }
+    third_party_settings: {  }
+hidden: {  }
diff --git a/config/sync/core.entity_view_display.node.daily_email.default.yml b/config/sync/core.entity_view_display.node.daily_email.default.yml
index 1678ad6ab..2206eb916 100644
--- a/config/sync/core.entity_view_display.node.daily_email.default.yml
+++ b/config/sync/core.entity_view_display.node.daily_email.default.yml
@@ -4,7 +4,6 @@ status: true
 dependencies:
   config:
     - field.field.node.daily_email.body
-    - field.field.node.daily_email.feeds_item
     - node.type.daily_email
   module:
     - text
@@ -22,5 +21,4 @@ content:
     weight: 0
     region: content
 hidden:
-  feeds_item: true
   links: true
diff --git a/config/sync/core.entity_view_display.node.daily_email.rss.yml b/config/sync/core.entity_view_display.node.daily_email.rss.yml
index 2b5661be1..cdf82fa8a 100644
--- a/config/sync/core.entity_view_display.node.daily_email.rss.yml
+++ b/config/sync/core.entity_view_display.node.daily_email.rss.yml
@@ -5,7 +5,6 @@ dependencies:
   config:
     - core.entity_view_mode.node.rss
     - field.field.node.daily_email.body
-    - field.field.node.daily_email.feeds_item
     - node.type.daily_email
   module:
     - layout_builder
@@ -28,5 +27,4 @@ content:
     weight: 0
     region: content
 hidden:
-  feeds_item: true
   links: true
diff --git a/config/sync/core.entity_view_display.node.daily_email.teaser.yml b/config/sync/core.entity_view_display.node.daily_email.teaser.yml
index 74940fd82..2958442a3 100644
--- a/config/sync/core.entity_view_display.node.daily_email.teaser.yml
+++ b/config/sync/core.entity_view_display.node.daily_email.teaser.yml
@@ -5,7 +5,6 @@ dependencies:
   config:
     - core.entity_view_mode.node.teaser
     - field.field.node.daily_email.body
-    - field.field.node.daily_email.feeds_item
     - node.type.daily_email
   module:
     - text
@@ -24,5 +23,4 @@ content:
     weight: 0
     region: content
 hidden:
-  feeds_item: true
   links: true
diff --git a/config/sync/core.entity_view_mode.feeds_feed.full.yml b/config/sync/core.entity_view_mode.feeds_feed.full.yml
deleted file mode 100644
index 7401b747e..000000000
--- a/config/sync/core.entity_view_mode.feeds_feed.full.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-uuid: 5d7c008f-6f2d-4055-9cbc-caeb6aa1ce79
-langcode: en
-status: false
-dependencies:
-  module:
-    - feeds
-_core:
-  default_config_hash: 8I9Vm3L0dLCdctKfCjpw5vLwMetyaJzxbWNMzb2V7-I
-id: feeds_feed.full
-label: 'Full feed'
-description: null
-targetEntityType: feeds_feed
-cache: true
diff --git a/config/sync/core.extension.yml b/config/sync/core.extension.yml
index a39054cbc..dbfe96166 100644
--- a/config/sync/core.extension.yml
+++ b/config/sync/core.extension.yml
@@ -26,7 +26,6 @@ module:
   eca_user: 0
   editor: 0
   entity_reference_revisions: 0
-  feeds: 0
   field: 0
   field_group: 0
   field_ui: 0
diff --git a/config/sync/feeds.feed_type.daily_emails.yml b/config/sync/feeds.feed_type.daily_emails.yml
deleted file mode 100644
index eadb21812..000000000
--- a/config/sync/feeds.feed_type.daily_emails.yml
+++ /dev/null
@@ -1,69 +0,0 @@
-uuid: bbef79e9-3f62-4d02-87f7-42aa5dc29f04
-langcode: en
-status: true
-dependencies:
-  config:
-    - field.field.node.daily_email.body
-    - node.type.daily_email
-  module:
-    - node
-label: 'Daily emails'
-id: daily_emails
-description: ''
-help: ''
-import_period: -1
-fetcher: http
-fetcher_configuration:
-  auto_detect_feeds: false
-  use_pubsubhubbub: false
-  always_download: false
-  fallback_hub: ''
-  request_timeout: 30
-parser: syndication
-parser_configuration: {  }
-processor: 'entity:node'
-processor_configuration:
-  values:
-    type: daily_email
-  langcode: en
-  insert_new: 1
-  update_existing: 0
-  update_non_existent: _keep
-  skip_hash_check: false
-  skip_validation: false
-  skip_validation_types: {  }
-  authorize: true
-  revision: false
-  expire: -1
-  owner_feed_author: false
-  owner_id: 1
-custom_sources: {  }
-mappings:
-  -
-    target: title
-    map:
-      value: title
-    settings:
-      language: null
-    unique: {  }
-  -
-    target: path
-    map:
-      alias: url
-    settings:
-      language: null
-  -
-    target: created
-    map:
-      value: timestamp
-    settings:
-      language: null
-      timezone: UTC
-  -
-    target: body
-    map:
-      value: content
-      summary: ''
-    settings:
-      language: ''
-      format: full_html
diff --git a/config/sync/feeds.settings.yml b/config/sync/feeds.settings.yml
deleted file mode 100644
index 30b1e14f0..000000000
--- a/config/sync/feeds.settings.yml
+++ /dev/null
@@ -1,3 +0,0 @@
-_core:
-  default_config_hash: HinPVeSuQPC-ststYO0ZlaHvrrLfgh3rC008LYb446k
-lock_timeout: 43200
diff --git a/config/sync/field.field.node.daily_email.feeds_item.yml b/config/sync/field.field.node.daily_email.feeds_item.yml
deleted file mode 100644
index 582d92fc9..000000000
--- a/config/sync/field.field.node.daily_email.feeds_item.yml
+++ /dev/null
@@ -1,23 +0,0 @@
-uuid: ce374884-abf4-4e9e-880e-c2bd504da762
-langcode: en
-status: true
-dependencies:
-  config:
-    - field.storage.node.feeds_item
-    - node.type.daily_email
-  module:
-    - feeds
-id: node.daily_email.feeds_item
-field_name: feeds_item
-entity_type: node
-bundle: daily_email
-label: 'Feeds item'
-description: ''
-required: false
-translatable: true
-default_value: {  }
-default_value_callback: ''
-settings:
-  handler: 'default:feeds_feed'
-  handler_settings: {  }
-field_type: feeds_item
diff --git a/config/sync/field.storage.node.feeds_item.yml b/config/sync/field.storage.node.feeds_item.yml
deleted file mode 100644
index 1c94fc2cf..000000000
--- a/config/sync/field.storage.node.feeds_item.yml
+++ /dev/null
@@ -1,20 +0,0 @@
-uuid: 9d2bdd56-8c87-4985-93ad-ead8cefc98c5
-langcode: en
-status: true
-dependencies:
-  module:
-    - feeds
-    - node
-id: node.feeds_item
-field_name: feeds_item
-entity_type: node
-type: feeds_item
-settings:
-  target_type: feeds_feed
-module: feeds
-locked: false
-cardinality: -1
-translatable: false
-indexes: {  }
-persist_with_no_fields: false
-custom_storage: false
diff --git a/config/sync/system.action.feeds_feed_clear_action.yml b/config/sync/system.action.feeds_feed_clear_action.yml
deleted file mode 100644
index 33e5e32b5..000000000
--- a/config/sync/system.action.feeds_feed_clear_action.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-uuid: 37be311a-3330-4c13-8d20-319f62d340f6
-langcode: en
-status: true
-dependencies:
-  module:
-    - feeds
-_core:
-  default_config_hash: Ur7RuR5ew0bsKEMwJUA7ZY0oY1mfXrSzcw4Tlt8FMJ0
-id: feeds_feed_clear_action
-label: 'Delete imported items of selected feeds'
-type: feeds_feed
-plugin: feeds_feed_clear_action
-configuration: {  }
diff --git a/config/sync/system.action.feeds_feed_delete_action.yml b/config/sync/system.action.feeds_feed_delete_action.yml
deleted file mode 100644
index 3d8e02208..000000000
--- a/config/sync/system.action.feeds_feed_delete_action.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-uuid: 4cfa8fe9-2d83-4211-a1a6-4ddd664799df
-langcode: en
-status: true
-dependencies:
-  module:
-    - feeds
-_core:
-  default_config_hash: yZW4ELH2L51kf2mGKd7f62uozGH-jFuWz1k9abACq1U
-id: feeds_feed_delete_action
-label: 'Delete selected feeds'
-type: feeds_feed
-plugin: feeds_feed_delete_action
-configuration: {  }
diff --git a/config/sync/system.action.feeds_feed_import_action.yml b/config/sync/system.action.feeds_feed_import_action.yml
deleted file mode 100644
index b3d7e30b9..000000000
--- a/config/sync/system.action.feeds_feed_import_action.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-uuid: 8f41e4fb-e97d-4799-ba3a-431d16261b07
-langcode: en
-status: true
-dependencies:
-  module:
-    - feeds
-_core:
-  default_config_hash: aQm30ToKvnhu77M_7zjucDLw0bxkaz5u3LDhByjaH8A
-id: feeds_feed_import_action
-label: 'Import selected feeds'
-type: feeds_feed
-plugin: feeds_feed_import_action
-configuration: {  }
diff --git a/config/sync/views.view.feeds_feed.yml b/config/sync/views.view.feeds_feed.yml
deleted file mode 100644
index cf7a3f012..000000000
--- a/config/sync/views.view.feeds_feed.yml
+++ /dev/null
@@ -1,737 +0,0 @@
-uuid: 7b32bdd2-6eee-49e0-ac5c-decae7ef386a
-langcode: en
-status: true
-dependencies:
-  config:
-    - system.menu.admin
-  module:
-    - feeds
-    - user
-_core:
-  default_config_hash: RbZ1xJz3BHNcfMQFvqYZv7O41f32c4ERI3DiwNKyss4
-id: feeds_feed
-label: Feeds
-module: views
-description: ''
-tag: ''
-base_table: feeds_feed
-base_field: fid
-display:
-  default:
-    display_plugin: default
-    id: default
-    display_title: Master
-    position: 0
-    display_options:
-      access:
-        type: perm
-        options:
-          perm: 'access feed overview'
-      cache:
-        type: none
-        options: {  }
-      query:
-        type: views_query
-        options:
-          disable_sql_rewrite: false
-          distinct: false
-          replica: false
-          query_comment: ''
-          query_tags: {  }
-      exposed_form:
-        type: basic
-        options:
-          submit_button: Apply
-          reset_button: false
-          reset_button_label: Reset
-          exposed_sorts_label: 'Sort by'
-          expose_sort_order: true
-          sort_asc_label: Asc
-          sort_desc_label: Desc
-      pager:
-        type: full
-        options:
-          items_per_page: 50
-          offset: 0
-          id: 0
-          total_pages: null
-          tags:
-            previous: '‹ previous'
-            next: 'next ›'
-            first: '« first'
-            last: 'last »'
-          expose:
-            items_per_page: false
-            items_per_page_label: 'Items per page'
-            items_per_page_options: '5, 10, 25, 50'
-            items_per_page_options_all: false
-            items_per_page_options_all_label: '- All -'
-            offset: false
-            offset_label: Offset
-          quantity: 9
-      style:
-        type: table
-        options:
-          grouping: {  }
-          row_class: ''
-          default_row_class: true
-          override: true
-          sticky: false
-          caption: ''
-          summary: ''
-          description: ''
-          columns:
-            feeds_feed_bulk_form: feeds_feed_bulk_form
-            title: title
-            type: type
-            name: name
-            changed: changed
-            imported: imported
-            operations: operations
-          info:
-            feeds_feed_bulk_form:
-              align: ''
-              separator: ''
-              empty_column: false
-              responsive: ''
-            title:
-              sortable: true
-              default_sort_order: asc
-              align: ''
-              separator: ''
-              empty_column: false
-              responsive: ''
-            type:
-              sortable: true
-              default_sort_order: asc
-              align: ''
-              separator: ''
-              empty_column: false
-              responsive: ''
-            name:
-              sortable: true
-              default_sort_order: asc
-              align: ''
-              separator: ''
-              empty_column: false
-              responsive: ''
-            changed:
-              sortable: true
-              default_sort_order: asc
-              align: ''
-              separator: ''
-              empty_column: false
-              responsive: ''
-            imported:
-              sortable: true
-              default_sort_order: asc
-              align: ''
-              separator: ''
-              empty_column: false
-              responsive: ''
-            operations:
-              align: ''
-              separator: ''
-              empty_column: false
-              responsive: ''
-          default: '-1'
-          empty_table: true
-      row:
-        type: fields
-      fields:
-        feeds_feed_bulk_form:
-          id: feeds_feed_bulk_form
-          table: feeds_feed
-          field: feeds_feed_bulk_form
-          relationship: none
-          group_type: group
-          admin_label: ''
-          label: 'Bulk update'
-          exclude: false
-          alter:
-            alter_text: false
-            text: ''
-            make_link: false
-            path: ''
-            absolute: false
-            external: false
-            replace_spaces: false
-            path_case: none
-            trim_whitespace: false
-            alt: ''
-            rel: ''
-            link_class: ''
-            prefix: ''
-            suffix: ''
-            target: ''
-            nl2br: false
-            max_length: 0
-            word_boundary: true
-            ellipsis: true
-            more_link: false
-            more_link_text: ''
-            more_link_path: ''
-            strip_tags: false
-            trim: false
-            preserve_tags: ''
-            html: false
-          element_type: ''
-          element_class: ''
-          element_label_type: ''
-          element_label_class: ''
-          element_label_colon: true
-          element_wrapper_type: ''
-          element_wrapper_class: ''
-          element_default_classes: true
-          empty: ''
-          hide_empty: false
-          empty_zero: false
-          hide_alter_empty: true
-          action_title: 'With selection'
-          include_exclude: exclude
-          selected_actions: {  }
-          entity_type: feeds_feed
-          plugin_id: bulk_form
-        title:
-          id: title
-          table: feeds_feed
-          field: title
-          relationship: none
-          group_type: group
-          admin_label: ''
-          label: Title
-          exclude: false
-          alter:
-            alter_text: false
-            text: ''
-            make_link: false
-            path: ''
-            absolute: false
-            external: false
-            replace_spaces: false
-            path_case: none
-            trim_whitespace: false
-            alt: ''
-            rel: ''
-            link_class: ''
-            prefix: ''
-            suffix: ''
-            target: ''
-            nl2br: false
-            max_length: 0
-            word_boundary: true
-            ellipsis: true
-            more_link: false
-            more_link_text: ''
-            more_link_path: ''
-            strip_tags: false
-            trim: false
-            preserve_tags: ''
-            html: false
-          element_type: ''
-          element_class: ''
-          element_label_type: ''
-          element_label_class: ''
-          element_label_colon: true
-          element_wrapper_type: ''
-          element_wrapper_class: ''
-          element_default_classes: true
-          empty: ''
-          hide_empty: false
-          empty_zero: false
-          hide_alter_empty: true
-          click_sort_column: value
-          type: string
-          settings:
-            link_to_entity: true
-          group_column: value
-          group_columns: {  }
-          group_rows: true
-          delta_limit: 0
-          delta_offset: 0
-          delta_reversed: false
-          delta_first_last: false
-          multi_type: separator
-          separator: ', '
-          field_api_classes: false
-          entity_type: null
-          entity_field: title
-          plugin_id: field
-        type:
-          id: type
-          table: feeds_feed
-          field: type
-          relationship: none
-          group_type: group
-          admin_label: ''
-          label: Type
-          exclude: false
-          alter:
-            alter_text: false
-            text: ''
-            make_link: false
-            path: ''
-            absolute: false
-            external: false
-            replace_spaces: false
-            path_case: none
-            trim_whitespace: false
-            alt: ''
-            rel: ''
-            link_class: ''
-            prefix: ''
-            suffix: ''
-            target: ''
-            nl2br: false
-            max_length: 0
-            word_boundary: true
-            ellipsis: true
-            more_link: false
-            more_link_text: ''
-            more_link_path: ''
-            strip_tags: false
-            trim: false
-            preserve_tags: ''
-            html: false
-          element_type: ''
-          element_class: ''
-          element_label_type: ''
-          element_label_class: ''
-          element_label_colon: true
-          element_wrapper_type: ''
-          element_wrapper_class: ''
-          element_default_classes: true
-          empty: ''
-          hide_empty: false
-          empty_zero: false
-          hide_alter_empty: true
-          click_sort_column: target_id
-          type: entity_reference_label
-          settings:
-            link: false
-          group_column: target_id
-          group_columns: {  }
-          group_rows: true
-          delta_limit: 0
-          delta_offset: 0
-          delta_reversed: false
-          delta_first_last: false
-          multi_type: separator
-          separator: ', '
-          field_api_classes: false
-          entity_type: feeds_feed
-          entity_field: type
-          plugin_id: field
-        name:
-          id: name
-          table: users_field_data
-          field: name
-          relationship: uid
-          group_type: group
-          admin_label: ''
-          label: Author
-          exclude: false
-          alter:
-            alter_text: false
-            text: ''
-            make_link: false
-            path: ''
-            absolute: false
-            external: false
-            replace_spaces: false
-            path_case: none
-            trim_whitespace: false
-            alt: ''
-            rel: ''
-            link_class: ''
-            prefix: ''
-            suffix: ''
-            target: ''
-            nl2br: false
-            max_length: 0
-            word_boundary: true
-            ellipsis: true
-            more_link: false
-            more_link_text: ''
-            more_link_path: ''
-            strip_tags: false
-            trim: false
-            preserve_tags: ''
-            html: false
-          element_type: ''
-          element_class: ''
-          element_label_type: ''
-          element_label_class: ''
-          element_label_colon: true
-          element_wrapper_type: ''
-          element_wrapper_class: ''
-          element_default_classes: true
-          empty: ''
-          hide_empty: false
-          empty_zero: false
-          hide_alter_empty: true
-          click_sort_column: value
-          type: user_name
-          settings:
-            link_to_entity: true
-          group_column: value
-          group_columns: {  }
-          group_rows: true
-          delta_limit: 0
-          delta_offset: 0
-          delta_reversed: false
-          delta_first_last: false
-          multi_type: separator
-          separator: ', '
-          field_api_classes: false
-          entity_type: user
-          entity_field: name
-          plugin_id: field
-        changed:
-          id: changed
-          table: feeds_feed
-          field: changed
-          relationship: none
-          group_type: group
-          admin_label: ''
-          label: Updated
-          exclude: false
-          alter:
-            alter_text: false
-            text: ''
-            make_link: false
-            path: ''
-            absolute: false
-            external: false
-            replace_spaces: false
-            path_case: none
-            trim_whitespace: false
-            alt: ''
-            rel: ''
-            link_class: ''
-            prefix: ''
-            suffix: ''
-            target: ''
-            nl2br: false
-            max_length: 0
-            word_boundary: true
-            ellipsis: true
-            more_link: false
-            more_link_text: ''
-            more_link_path: ''
-            strip_tags: false
-            trim: false
-            preserve_tags: ''
-            html: false
-          element_type: ''
-          element_class: ''
-          element_label_type: ''
-          element_label_class: ''
-          element_label_colon: true
-          element_wrapper_type: ''
-          element_wrapper_class: ''
-          element_default_classes: true
-          empty: ''
-          hide_empty: false
-          empty_zero: false
-          hide_alter_empty: true
-          click_sort_column: value
-          type: timestamp
-          settings:
-            date_format: short
-            custom_date_format: ''
-            timezone: ''
-          group_column: value
-          group_columns: {  }
-          group_rows: true
-          delta_limit: 0
-          delta_offset: 0
-          delta_reversed: false
-          delta_first_last: false
-          multi_type: separator
-          separator: ', '
-          field_api_classes: false
-          entity_type: feeds_feed
-          entity_field: changed
-          plugin_id: field
-        imported:
-          id: imported
-          table: feeds_feed
-          field: imported
-          relationship: none
-          group_type: group
-          admin_label: ''
-          label: Imported
-          exclude: false
-          alter:
-            alter_text: false
-            text: ''
-            make_link: false
-            path: ''
-            absolute: false
-            external: false
-            replace_spaces: false
-            path_case: none
-            trim_whitespace: false
-            alt: ''
-            rel: ''
-            link_class: ''
-            prefix: ''
-            suffix: ''
-            target: ''
-            nl2br: false
-            max_length: 0
-            word_boundary: true
-            ellipsis: true
-            more_link: false
-            more_link_text: ''
-            more_link_path: ''
-            strip_tags: false
-            trim: false
-            preserve_tags: ''
-            html: false
-          element_type: ''
-          element_class: ''
-          element_label_type: ''
-          element_label_class: ''
-          element_label_colon: true
-          element_wrapper_type: ''
-          element_wrapper_class: ''
-          element_default_classes: true
-          empty: ''
-          hide_empty: false
-          empty_zero: false
-          hide_alter_empty: true
-          click_sort_column: value
-          type: timestamp
-          settings:
-            date_format: short
-            custom_date_format: ''
-            timezone: ''
-          group_column: value
-          group_columns: {  }
-          group_rows: true
-          delta_limit: 0
-          delta_offset: 0
-          delta_reversed: false
-          delta_first_last: false
-          multi_type: separator
-          separator: ', '
-          field_api_classes: false
-          entity_type: feeds_feed
-          entity_field: imported
-          plugin_id: field
-        operations:
-          id: operations
-          table: feeds_feed
-          field: operations
-          relationship: none
-          group_type: group
-          admin_label: ''
-          label: Operations
-          exclude: false
-          alter:
-            alter_text: false
-            text: ''
-            make_link: false
-            path: ''
-            absolute: false
-            external: false
-            replace_spaces: false
-            path_case: none
-            trim_whitespace: false
-            alt: ''
-            rel: ''
-            link_class: ''
-            prefix: ''
-            suffix: ''
-            target: ''
-            nl2br: false
-            max_length: 0
-            word_boundary: true
-            ellipsis: true
-            more_link: false
-            more_link_text: ''
-            more_link_path: ''
-            strip_tags: false
-            trim: false
-            preserve_tags: ''
-            html: false
-          element_type: ''
-          element_class: ''
-          element_label_type: ''
-          element_label_class: ''
-          element_label_colon: true
-          element_wrapper_type: ''
-          element_wrapper_class: ''
-          element_default_classes: true
-          empty: ''
-          hide_empty: false
-          empty_zero: false
-          hide_alter_empty: true
-          destination: true
-          entity_type: feeds_feed
-          plugin_id: entity_operations
-      filters:
-        title:
-          id: title
-          table: feeds_feed
-          field: title
-          relationship: none
-          group_type: group
-          admin_label: ''
-          operator: contains
-          value: ''
-          group: 1
-          exposed: true
-          expose:
-            operator_id: title_op
-            label: Title
-            description: ''
-            use_operator: false
-            operator: title_op
-            identifier: title
-            required: false
-            remember: false
-            multiple: false
-            remember_roles:
-              authenticated: authenticated
-              anonymous: '0'
-          is_grouped: false
-          group_info:
-            label: ''
-            description: ''
-            identifier: ''
-            optional: true
-            widget: select
-            multiple: false
-            remember: false
-            default_group: All
-            default_group_multiple: {  }
-            group_items: {  }
-          entity_type: feeds_feed
-          entity_field: title
-          plugin_id: string
-        type:
-          id: type
-          table: feeds_feed
-          field: type
-          relationship: none
-          group_type: group
-          admin_label: ''
-          operator: in
-          value: {  }
-          group: 1
-          exposed: true
-          expose:
-            operator_id: type_op
-            label: Type
-            description: ''
-            use_operator: false
-            operator: type_op
-            identifier: type
-            required: false
-            remember: false
-            multiple: false
-            remember_roles:
-              authenticated: authenticated
-              anonymous: '0'
-            reduce: false
-          is_grouped: false
-          group_info:
-            label: ''
-            description: ''
-            identifier: ''
-            optional: true
-            widget: select
-            multiple: false
-            remember: false
-            default_group: All
-            default_group_multiple: {  }
-            group_items: {  }
-          entity_type: feeds_feed
-          entity_field: type
-          plugin_id: bundle
-      sorts:
-        changed:
-          id: changed
-          table: feeds_feed
-          field: changed
-          relationship: none
-          group_type: group
-          admin_label: ''
-          order: DESC
-          exposed: false
-          expose:
-            label: ''
-          granularity: second
-          entity_type: feeds_feed
-          entity_field: changed
-          plugin_id: date
-      title: Feeds
-      header: {  }
-      footer: {  }
-      empty:
-        result:
-          id: result
-          table: views
-          field: result
-          relationship: none
-          group_type: group
-          admin_label: ''
-          empty: true
-          content: 'There are no feeds yet.'
-          plugin_id: result
-      relationships:
-        uid:
-          id: uid
-          table: feeds_feed
-          field: uid
-          relationship: none
-          group_type: group
-          admin_label: Author
-          required: false
-          entity_type: feeds_feed
-          entity_field: uid
-          plugin_id: standard
-      arguments: {  }
-      display_extenders: {  }
-      filter_groups:
-        operator: AND
-        groups:
-          1: AND
-    cache_metadata:
-      max-age: 0
-      contexts:
-        - 'languages:language_content'
-        - 'languages:language_interface'
-        - url
-        - url.query_args
-        - user.permissions
-      tags: {  }
-  page_1:
-    display_plugin: page
-    id: page_1
-    display_title: Page
-    position: 1
-    display_options:
-      display_extenders: {  }
-      path: admin/content/feed
-      menu:
-        type: normal
-        title: Feeds
-        description: ''
-        expanded: false
-        parent: system.admin_content
-        weight: 0
-        context: '0'
-        menu_name: admin
-    cache_metadata:
-      max-age: 0
-      contexts:
-        - 'languages:language_content'
-        - 'languages:language_interface'
-        - url
-        - url.query_args
-        - user.permissions
-      tags: {  }
diff --git a/content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json b/content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json
deleted file mode 100644
index b52cd60bd..000000000
--- a/content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json
+++ /dev/null
@@ -1,73 +0,0 @@
-{
-    "uuid": [
-        {
-            "value": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
-    ],
-    "type": [
-        {
-            "target_id": "daily_emails",
-            "target_type": "feeds_feed_type",
-            "target_uuid": "bbef79e9-3f62-4d02-87f7-42aa5dc29f04"
-        }
-    ],
-    "title": [
-        {
-            "value": "Daily emails"
-        }
-    ],
-    "uid": [
-        {
-            "target_type": "user",
-            "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
-        }
-    ],
-    "status": [
-        {
-            "value": false
-        }
-    ],
-    "created": [
-        {
-            "value": "2025-04-16T14:12:30+00:00"
-        }
-    ],
-    "changed": [
-        {
-            "value": "2025-05-13T23:02:18+00:00"
-        }
-    ],
-    "imported": [
-        {
-            "value": "2025-05-11T09:01:00+00:00"
-        }
-    ],
-    "next": [
-        {
-            "value": "1969-12-31T23:59:59+00:00"
-        }
-    ],
-    "queued": [
-        {
-            "value": "1970-01-01T00:00:00+00:00"
-        }
-    ],
-    "source": [
-        {
-            "value": "https:\/\/www.oliverdavies.uk\/rss\/daily2.xml"
-        }
-    ],
-    "config": [
-        {
-            "fetcher": {
-                "fid": "1",
-                "usage_id": "728512ba-6198-4260-9eff-4e30b02d8ec6"
-            }
-        }
-    ],
-    "item_count": [
-        {
-            "value": 0
-        }
-    ]
-}
\ No newline at end of file
diff --git a/content/meta/index.json b/content/meta/index.json
index 5877b8f39..f43e13b98 100644
--- a/content/meta/index.json
+++ b/content/meta/index.json
@@ -20,9 +20,6 @@
     "crop.87fbc4e4-490e-4de5-a34f-c11e859cdd2d": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
-    "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
     "file.bf5bcd01-5c93-46fb-897d-5dc69c3cbc7f": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
@@ -462,3284 +459,2464 @@
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ca7093b6-288d-4326-b755-cc96e0c262dc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a99289d5-ad45-4e3d-9d03-031569f7bf70": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d6363924-78ee-4086-8cf0-41e07c030fd4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d344a28e-aa79-4533-8eac-f112926fe811": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fb679f64-e559-4319-9a36-b508bc870415": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.92b0bd2f-d0fe-4d21-b208-961525c053ea": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f86b9901-80da-4765-aa94-3bf6025efde5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.09d6a39f-ac99-44fc-b660-4f976132d813": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.71e7e05f-a075-432a-bda3-db66b0e733cc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3373d8dc-7c1d-477f-8628-f3029228b9c4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.753da3d5-1cc0-40df-8afa-101986188a96": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7210b16f-71c2-44c4-9dc1-4264b243c618": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f3e69f27-6b57-434e-a50a-308e99838872": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1550e619-abd2-4efe-b941-fd4e42507d51": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dab1657a-80c4-4b6c-b7c5-28b874fff857": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4df98b71-9bff-4c1d-9636-5074e31a7ace": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9a9bcb91-1a60-4126-8a14-d477544568d1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.526f1b74-c255-4dd3-ba7a-5d529545d01d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a8a1b0cc-8372-4285-a655-bdd1f77226d3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c9ccd7f8-4727-49fa-9481-4507e7986fd9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ec354679-9830-4361-b0eb-16e976e888ce": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4528246c-53df-4a2b-aba1-e72a45dc542d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.83443749-8720-4aa7-95b1-9c35e88f094f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ce877341-4025-4610-89b6-f1f4c9bfe5af": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.68c7948f-c44c-46e2-878f-432616c7e365": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.75787d98-31be-4b33-a434-15d5a43c07af": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6fb0a429-0264-4308-9436-f1115d5b108b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.01893784-8f45-4466-8586-17df23e7e4b5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a33ea357-381e-4171-9808-85c90c7602c7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.49a59848-0bef-4184-b9d2-5bf539c6e14c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3a13004e-2245-425f-8080-0b98e161bcb0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2142e27d-5c96-4c16-9650-dc47b2b85888": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0316dfcf-b709-47e1-9622-9355b5ece6d9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.44e71b80-61a3-4376-83aa-3b975401942b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1d8c474a-de0c-417c-bc05-179eef2e9bfb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c1064abb-f7f8-4e4d-bfb7-9842271b0938": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ee81b821-f2be-4dce-a119-7e421bbc7e04": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.78b682e0-a3be-4e49-990b-8fcc7083f6ca": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.018bf894-2d3e-4130-b0bd-43450ef5753a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.681c802d-45a6-409e-8dd1-3499184f7616": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a2b118ea-d319-4808-83f6-94ad79c302f2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.731a0026-d287-452b-96d7-aeaa3f4bec48": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0318e249-a9a8-476f-9bd4-432544369917": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0001428e-621c-49ca-83d3-4323ea446f48": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7678ac40-dfe5-43bd-98cc-37fa80affc7e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.38522a11-5473-4584-a8f0-c9097a843c9b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ea81e659-48e0-4eaf-ae3b-a30012102d0e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b48769b5-0c48-4bee-a008-6a760db421de": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0f349fae-6a04-42b4-979f-ed8428e97a2b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e2679ec1-9cf5-483f-86e0-f176db3daae4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.283e9379-f264-4191-8bbd-2cd8393c395b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.70c71a01-1c5a-4b25-8706-d02a4284662e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2d89873f-8f15-4e92-9f72-1a83855d3d82": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2959438c-8c12-49c7-84a2-d9ea9bf338e6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.792953b8-b5f7-44dc-8e32-d70629bf06a4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.da62317b-2539-43bd-8db0-94bddb14174e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c72430aa-0c6d-4cf8-8a43-812d245ea73d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4aec9154-e02d-48cd-84e3-26de40c4d4f3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cfb22ecc-4401-41bf-8ed5-4a9321601a17": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f4b83f92-eda0-4174-a9e1-45a94d97fb05": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.274408ed-379c-4eaf-914d-7f5599f513d3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c0d7b8ea-8a29-4d83-937d-52d951ce250b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0610a25f-884a-48b6-8be0-e969749d316a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e88b4449-20b6-4165-880b-6d34b9579781": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2a816ad4-7e24-4082-83c3-b93490294170": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.42744e61-acab-44e4-bd60-576a30cf7b60": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d753217f-2d8f-431d-850c-d54597b46b76": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d0ee1aae-f2fc-49d2-8865-d4912209eeea": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f2220fec-35de-40a7-be72-9b3b643e15df": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5af463dd-91dc-45a4-a0bc-58212e30d402": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4cdddd8a-3291-4d3f-81c9-e639f527f647": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8290cf4e-cbbc-415d-b185-cbaba90d42d1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.84ede6fa-2682-4edf-8b22-ee603de0b8c7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cd3df6ff-471f-4b56-af7c-9b9a6588367e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4af20d94-cb48-4351-a0a6-7f6a0387d105": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.92168b2b-6e46-4548-a7b0-824c862126e3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5d894fb5-1253-4f7e-a6ad-429618eeefef": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.03bbb03d-5963-477a-a904-19e2c1f1a581": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5e37f5e3-8ada-4d61-925d-5033258e441f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4e66101d-e2bf-4eab-904d-67c15d0466b8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.768ec43f-2c43-4071-9a7b-f53b5df43a33": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e52fda31-17cc-4379-b8cb-1a22c9e11601": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6118e44d-7b4b-465e-9e7d-d2268a2e2505": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e35f213b-1b5c-453e-bf2d-fa542a37aac3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5e8f1843-5372-46c1-bb61-0ff493ca22ae": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b43ce1ab-0d83-463f-9421-d20aaacdd833": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1007a975-f818-4568-8560-9532e96c4577": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d7a77497-05c5-4a42-8ecc-e0f171bb8097": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0100be71-79ef-44ea-922e-e75fcc26ae16": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.26f6be13-6309-441d-977f-eb84684b8a2f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.82f169a8-a9cf-4705-abaa-f8e29912aa9f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1c357f25-ed1e-406f-9899-ec9017548800": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.90791de2-4132-43e3-94ea-41609f317429": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7b5a2a03-3f09-4876-8f0d-8056485566e8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9deec245-c96a-44f5-a54c-95f61611051d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.43f35613-9c2f-46e9-b581-8253823fb7d8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.72ee8411-6b32-45e5-96e1-2b749601a0ae": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8174931b-97d3-457f-8822-00c905fe9e1d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.987bb32d-4dc3-49ff-bc30-2563ea769769": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dea5d550-6603-412d-b1a6-eec70c353b96": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.16dc23db-86e4-4c5d-b479-3f92828dae12": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.52049b70-5092-41ea-a749-5fde0d95b39e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.97127b95-b383-490a-af5f-62e60aa11f0f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.225110fb-82d3-4056-a394-0612d80e37ec": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dbb959b1-390d-45e8-b080-097a313545d8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.530d3f61-3f2c-4cb5-acc7-560d4608367f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b61104ef-e514-4518-bec8-a10b1dcbaa4a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.03c0a713-f32d-445b-9397-add68fbf2fe5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f0fe2425-0fca-41a3-8ca8-67953798b7a5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.49ef1a05-b415-4537-b2c7-285827e27463": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d613376e-133d-4730-86f1-70661d24c7ff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6ccfb609-6371-462c-b91c-4aa22d23d248": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7e93586c-c6a0-410a-ae83-a1d50bc12743": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4ae8b0fe-2248-4e67-b68a-816c8539528a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.179c3eed-b723-4f44-b9d4-398b90b916e7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0cc877ae-0361-456e-be2c-73c322fe1780": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7987b079-7f85-4303-ab3c-1338dbeaf171": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.805363c0-2306-47f5-b9ba-57995ebe12b3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.593bdaf4-b28c-4938-b1da-03052baef361": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4d6d623b-afb2-4628-b716-2e6c3adac5cb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2c022817-6bf1-4a2f-809e-8895c72a0e03": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0db2d25b-3e50-4f36-abe1-f84b938c21db": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c7ad84af-f5c8-4ff8-92cd-873528acc623": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f245814b-3957-4c84-82fb-47134c3edd24": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2b55b7dd-2287-462d-a951-62603ce334bd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.711d2246-a181-4fe5-900d-c6e4fee3c29d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a564cfaa-2b13-4739-af74-5fde2b75b1a0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c87318b5-eb27-4eba-a3d4-a5328f362c9d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.85b61d26-e598-4b64-99b4-445d8d22fba5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.01230324-62b5-442b-80e4-09268a31819b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.defbeab8-28ca-4444-b09b-5121de794602": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e8275304-6db2-435e-bd89-9810a1f51490": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.17a436ab-84f0-4c0a-9305-b04a9e1883ee": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.af570204-edaa-41d8-af54-5136ec8f0954": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9dcd7b33-b2bc-41b1-9d17-f7536a670343": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.deaafd9d-8951-41fb-bc84-745a611f3b1b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fe407991-a896-410c-9223-51a7ad43d4d2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d33493db-20b9-4946-94a1-bc2abfb6b998": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c2ed3f01-0761-4b2a-a845-fccd30c84d57": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2e4827a4-0d9c-458c-86eb-d6b40f18d608": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c7423f08-eb5a-4602-b85f-9b4691efe3ab": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9f51855e-e397-420d-9ee8-e0780937cc24": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.77377a19-7488-40de-a041-f488b3ae597c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.be331d8c-cc1c-404d-9764-7304a5309c80": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.557b60f7-1f31-40ec-b0c8-285df7a73dd9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.614cb089-7e70-46ab-9f5f-dd08b529f3d0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1254f835-445d-4a54-a831-2fc179b3d15c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0da14ab3-af09-42cf-9813-877a7a66cf87": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.eef4147e-e47a-411e-a7de-eb67638dc6bb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fa7b57ee-9af5-49ce-9522-66d54642e219": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.168c59ab-cadd-4dfc-8c72-de82d6578885": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7989ae69-0f6d-4a7d-b560-d828f76cfba4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a8d650da-84f6-4d81-9384-bb26228f3dcb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b38b290a-1ce1-481d-987b-9683245740da": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4b0999e1-0348-478a-af35-1487adb15b7a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ebf479a8-f93c-4972-ae90-8b59a0ca8081": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b3a28a86-02c5-45ea-8a51-32508cd34b7d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.59ae3523-9dc9-4b61-8387-aaeb708385e6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dfe4489a-7d64-4368-b86e-e35180377c15": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5e643127-50de-44fa-bd1f-70f69c72ee9f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f722e13d-4831-4153-9ba1-0243c3387b8c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7bc6b922-ec23-4389-8466-ffd96db33b29": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3e810095-a24b-4f0b-a62b-e39003df099e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c8fd5532-9338-4ea0-933f-798ce5782931": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fa30b239-baa9-46ec-9ea2-4914280dd13b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.32591463-ab8b-4210-84ca-419bb69439c4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d7c36fee-2434-4c3c-95d3-df1303603a35": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.81e54ee3-c438-49d9-9450-27cafa5a7fae": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.38988766-4898-4aec-a987-c189ae1ea6c6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8e31643d-a697-4068-8692-cdc472b96e90": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.29ab0d54-5f71-4615-b391-164735cada18": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dab13df7-2835-407a-90c5-f5574585718b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.53a00f10-a301-4294-ad39-916b9bc2ecd7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.290e62f9-ffc1-4420-91f7-decda6410276": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ea06edab-74a5-42d4-add9-d4dce3d0f792": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.26e4ff33-b5fd-47b4-926e-fc5b78677c88": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f529894e-5912-4e77-91a3-d78b9cbf2584": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2da2e369-297c-46bd-83e5-8fd16d4c85c1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.40f5b812-3bf8-47e5-bc39-57d9ae8db404": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3422a295-b8a9-43a0-9a03-a54d77e52513": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.597567b2-4065-4bea-890f-b8faef33f8c6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.57f28cf3-4474-4668-8222-c430cbe9b88b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.33bea7ca-ccf4-4865-bc17-314ce54b6988": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a4efc095-f78d-45ae-854d-fc52c8afa41b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9cc91e25-0d1b-4a93-b367-7da047fce99e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.720b01a3-3f38-46cd-8263-112571d62c60": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.46b8861e-c2e4-49ef-8b79-fb14effaef6a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.faff03ba-71b2-4b4b-a107-9e7f499eeefd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0ce2a823-c7ad-475b-9cca-29e1b1702e77": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7586b569-6528-43ba-b0a4-a55de9faafb3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e3391a68-8501-49ac-a509-c7a1ac579193": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b2f30b62-d067-4e73-9fab-db655e9409d6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.033f0b46-69f9-4ea0-9706-d930e67dd5d8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b51a5709-0942-4244-b857-16e5b43ff2fb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.572f5e16-12f6-4470-a07c-06baf52c26e5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0c899647-4916-4ad6-bde0-5ae1f397cc13": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d047a824-fbb1-40b0-8391-ceba0cc250f5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d9520278-39f8-4cdb-9f94-632cabb49acd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.90b4b442-bc96-4b9f-9e1b-70112f628de8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c4bece9a-e11b-43a8-861a-2a64a12e5a91": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d3d14705-ef6a-4827-afad-bb2963dac369": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4640cfe1-e531-48ab-8fb3-42655a77d667": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.10b3608a-50f6-4178-9ae2-d07f353a9c23": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.71882aa6-8635-4242-ad8c-3676d9640060": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.34be6fed-cd1a-4796-adb8-577340a359b4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.400a0b92-7c40-43b0-883d-5f199fb5471f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.467e5ad9-cca4-4700-8727-3356e81182aa": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0a04ac23-4d64-40e8-8e94-ead3cab7129d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a520e72c-3fdf-476e-bdd7-0120e9e161ea": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d64f0811-a486-4194-99e8-67d21263cb7f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c8e5ab46-3320-4a41-b322-11b08d92aeaa": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6eeb79ee-eae2-41ea-ab7e-56f216daf636": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.675fbf45-ad63-4685-9f22-e67e17764d9a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.02bd7b93-43c7-453f-8af9-0be875b27f82": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fba9e05d-92e9-4699-a6ad-dafae26a1670": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.90834219-4fa0-4db8-a34e-9a4e7b017359": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5c50152f-4832-4ccc-9751-31c5caeb7cc3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.021e00c1-b813-4edd-8064-71285bc3647d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4c0b0072-4046-48aa-b481-84515c265ca0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bcfa962f-c9ea-4346-b10c-4317932097c7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3cb7e223-af31-471e-acef-d3d069852841": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5060344a-0047-40ab-8fdb-a297518478fb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a7ee1363-3e3b-4733-b302-0c85aad15aea": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.066297b1-ab00-4769-afe1-d3831ed2a654": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b51b7b96-fe84-43ed-9181-3c590a4015ef": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.97ba47f0-b202-4ac4-974f-6bb9a50abb38": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.278813c0-1c8b-4558-bf13-3c2f03acaeb6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.759bb289-07cd-4103-bc90-107b7f13978d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6480661e-12de-42e9-aa02-d4f37b23942d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.05232b81-d945-4112-99bf-d1adb2552428": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.42904e0f-f6d7-496e-8bce-72bd1e669e99": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d487d829-d35c-4c4f-b4e8-af804b29463e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.98e6a250-a27f-41c2-8685-e80474a2d174": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0f64feba-0a96-41e4-b8e3-10358e4c86c6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.74447b1a-33da-45b7-aa4b-a35e2afb6803": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d0cabfc7-0a42-4d21-a028-eb1220bfece8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7fe749a2-90b7-4d22-9dff-56eaa7adb3d5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e88621ad-4a3d-481e-b292-b710f0756313": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.079f2e09-0827-458e-91d3-6dd5b8b80c56": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5b0c25b0-761b-437b-8be3-af045c9e00bc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0a2a3238-42ea-46de-8140-94e74f381916": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2885a415-17fb-4374-8070-0be55407af6c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.74b360bb-61b3-4ed4-8942-1c21bdf630ef": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.31026a42-b854-4517-b2d0-790036cfe6ad": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3b090ba6-775a-44a1-bc43-c6807380fb59": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2f503fac-0d18-436b-a5d1-64263c5fc616": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.befd9d9c-edd5-483e-b378-b3867451769d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0c1ee324-e522-440a-85bf-e91847091ec9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.465add9b-a2c7-48f1-84de-966fbbd20c27": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e2991eb4-1aee-4d04-9045-989159a9b64f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d3fe0eae-7883-4fe6-9a98-747b53d860ca": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.54a30090-50dd-4534-af69-bc7120297bf9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.df0a8efc-bfd5-4c57-adc6-08d63794041e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6c69f289-ca43-4731-9729-0341250e0591": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5e44dd96-8baf-47dd-9aba-79887e8c3835": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.614ba8ae-b911-4705-95f8-aafe213e00f3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a9061df6-daf5-47f3-a217-39df555f9762": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.235bcd7b-1bdb-4616-99bb-ecd321f449a0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c9c11eda-6318-4e7c-b108-a01feea60e45": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.57f698eb-511f-4cfb-95b0-a752efab60ea": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a97003d7-c86d-41a3-8655-ca35c6912d42": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3179746f-a523-4f4d-8bef-44d0c117cb43": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.09f421c4-eff1-4b5c-a692-45dfbd837758": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.79ce3fb5-ecce-4b0f-96a2-bf7094473416": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4619464a-a90c-4ce6-854d-9decfb58c603": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.358edef5-5436-46ca-a90c-4d691ea7c281": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6cc053d6-5012-4cc7-81e8-43768a0886be": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.43df816f-7fee-4e8a-b396-9a84b2214e7b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.75e0f02d-1c15-4877-8443-724ddfaf45f6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cb59660e-e499-4b18-a779-46fed92d0879": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.13c70679-77d6-404e-9b4d-ca214713e315": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.95476ad8-f2dd-4667-99a5-5a5309299702": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.56df3f74-7cd2-4229-98b7-a593d435ad70": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c58749a0-bec2-415b-aa25-33eca5cce8b7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.362530ad-9f84-49c4-a8cb-bea45c77c474": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2f576a37-bd5a-4894-9340-1e69775c8b68": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.aba09cf2-f67c-4056-b503-5a53399e634b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bd892fac-0009-4886-9ced-5fbffab2d540": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1d61b9ee-e6de-4db6-8782-68eba42d357a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.06b8d0b3-318a-4a06-902c-f42ce169774b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6d87c24a-6453-48fd-9921-cede6b1b0001": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c8d78160-4a98-441c-a707-c1fde53f9044": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dfe87217-dc3b-413c-9e42-912386be5d5f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d3e4d075-4050-46af-bfd3-94944eaae35b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2530ef2e-0df9-4364-8e08-5d872cd9621e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cbd099ee-0b05-402b-803d-9753a84a9e83": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e179e840-bd5c-45b3-8bae-2b3706861bb3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d4e3757c-36f7-45f7-a679-6292e8300200": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.00d62e94-80d1-4792-bdea-88a064f6bf65": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8be3d8d9-4e73-49db-93a6-83349ac1af05": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5563fb1b-a5a1-4372-84b9-b0be87acc501": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c28c0731-5f76-4b55-8326-a584e385e8cb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8108dc36-1eb3-487b-9c03-600c49a6d11c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c841583c-4e19-4eb2-898a-d7e61859daad": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.20010c04-2f30-4772-9041-6f7e836158f8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.21f3f75a-e37f-44b6-81f5-337cc11e5eac": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.624faf57-efdb-444b-85b7-fbb680ed2b73": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.50f6b3f3-e483-41b0-a44a-465109c160b7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.13312da0-7cf4-4825-ac6e-eb35c673e63e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8766d230-d3d4-45fb-82a6-2dbaec0c775b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dd462165-113a-4b0e-b566-a242cfd475dd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c9c4743b-a803-47b3-8405-f6aeb34a279b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.95a128d2-01a1-4e31-a6de-33bc7c091269": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5017b3a0-ce88-4884-bace-c0550e729ab5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7064860b-42de-47c3-b5ac-3560d941fe0f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.29a700d5-082c-4f6b-bafd-f4c4e1486624": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.43c6257e-4064-422d-8075-5ec55861c177": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.960814d3-b3bd-4a5a-a541-906c1e121902": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.323bc6bc-069b-497b-9f64-d64c21bdba79": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bc747939-87ef-409b-bb1e-48c94863579c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e00e0cdc-8668-4ca5-86e0-1219332907c0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a47d5366-6212-48d7-98b0-5ccc2506052c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a0631edf-ffac-4381-92b6-98e76e980131": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4e0d5cba-13d4-497e-a320-d1236df4dce2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.aa4b919c-76e4-43db-8962-2b2cacd33267": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9ecc8bf3-5bf6-4713-9868-c6059db4d432": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9b65d27f-65f6-4913-b142-a1a128ebf21f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bd0ab1a7-853f-44dd-a29f-967b3808e132": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.82af7a87-a737-49cd-84a0-872e820d9c91": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e91d28ca-1730-4560-82ab-205175ca2bf9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ffa93a1b-f239-4c0a-9f34-50cd6532f353": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.47749b6f-e118-4fe5-b13d-11fe1189d77d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1e59e156-0e2c-4f6d-a828-030d1322fde6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2f257fd0-6e5d-4690-9f01-3435e3578798": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c027d77e-97c4-43eb-99cd-672dedcf8f14": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b54ead56-01d3-442f-9689-c422f5be5e27": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.db312e00-7a9d-492d-a6db-7298848e06b2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.48384c9b-ce41-4356-8364-6ce566eac315": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.216f7a7d-663b-42a6-b430-3817a1180dbd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.93b8a0b3-9766-47b1-a8bc-03975d6f3063": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c2315804-efa4-4b5e-ae67-41457d8cd8c8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2be6f96b-eecb-4205-9ca9-b364196535ab": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.82672338-b561-408d-a17e-902c1f37e6a9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9533c89f-d5dd-4959-ba2c-66be5df70f60": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b8243d12-2068-42e4-bb31-6f0b5add5e5a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b5b7cf41-fa32-4c63-a182-9b048c290f05": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fb85bcd0-833b-4e23-bab7-4e9ae86075df": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b892433b-6318-4716-9bb8-fc13e6a55fbb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.25833838-38b9-414d-bca6-de0bf5c2ac28": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.98d20258-bdbe-4286-a2d2-36dc4722cac1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cdd7350c-f06a-410e-841c-06acf0dc312c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.47578912-129e-4ee2-9392-a5e04f4592b4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a564439d-3102-47dc-8f4b-70b080383552": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.19376fcb-fc7a-4b4a-9fea-6865e423519e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c68956b5-95b2-48f4-873e-aabc074a5497": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2bf48b4d-12c8-43be-9f95-c4c54fe34712": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fe815eab-027d-49db-afd1-e4a21387b2fe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.42741272-127f-46fb-b058-172301e5edd1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4c1497cc-4638-40fc-b045-f342c4d3e5b3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.36d7f751-faeb-48a4-9fb3-fc8248bb515c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.09dff532-7bc4-4949-bfdf-7c4a6e59097a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.050a5113-59bc-461e-ac78-420e16055303": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a8753236-c6ec-4eab-88c0-cf1939cf0333": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.178c6bab-7e28-413a-9055-24fac0de0d0a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.266918e6-af3d-48f8-89d4-657ff2214626": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a504768a-c5bf-4660-986d-07590f6ee816": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d4beee99-ab37-4663-b331-4de9f42ec333": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5652a68a-720a-4954-adfa-38b8e2890b8d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.84a6f9be-759c-42ea-815b-6b29a90b7742": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a8e2e580-5b20-451d-80ef-7ee19aea62ec": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6c7900af-a3e4-4402-937d-9eeda843398f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a1dc0ff4-ae77-4126-a499-1f39e9c08115": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.53ad5789-5fd6-41e8-b748-ce9e0bff280b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.af1271f1-d7b4-446b-8fb0-1d94eee5846f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bfd168f9-71fe-41f9-a4f6-60ce897917a7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a5a69bcd-a7f7-4957-ab0b-393437e4055d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3d777436-a3ab-4465-b3c2-63d7eb28b50d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7a90ce1b-f0d9-443b-b143-b82562fef529": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e0c0707d-b542-4aae-a8b4-8633673fd520": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.66485e91-b88c-4a7c-8472-e593b8496e82": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.39db6489-2e23-4cb3-a0be-a4e78a2e9142": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.09073a81-2a1b-4200-905b-98b43152fe37": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.82f12dce-4db3-44d8-9eff-b24feb20d568": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b2160fad-74d6-425b-9c76-d3b662807dbf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0d707bca-be14-4504-b500-9e44abebab44": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.037796b8-42d8-4ea4-abec-f8c8de0d97e8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1fd87ecf-4269-4874-859e-d49c238694bf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9834732b-1b38-471a-b1bb-64471b27a2ee": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c765b1bf-87ee-4324-843a-8ca578ef2f69": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f451e001-95a4-4c6c-94e0-cdbcda175b7b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.83916d2b-f03f-4add-9276-5080b66925b4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6cecf88f-e9d9-4954-b64e-00246781b591": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.08209d64-40fa-4771-9415-c23e962a5028": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d1633911-dff9-4079-a0cb-5efe70d9a1fb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ca145f06-f0f5-4538-978f-0af3f1c32d73": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b92a815e-5d21-4adc-8a1f-378ba6be23c8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.59cd5b64-d1c8-4249-ab41-2106e25df543": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bf04ca43-aaa4-4877-a1df-80042934a312": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9aba3fab-cb0a-4ea1-a439-9ff419b23841": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.18cac962-eefd-4506-8efd-cd584f027369": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9f663595-3a33-4503-a86e-c15b8e3113a0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.898e3ece-caad-49b2-8486-400e653eea9d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4f2f14d0-f991-4f10-b516-20e744c08fce": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.739826e2-62a6-4726-8294-5359016f8d24": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e0d6060d-596b-460f-9cac-22ef16a947b6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5c687659-3110-4757-b25f-ab28a7190da5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b0daabcd-f51d-4208-9742-4a4512e2bbb5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bbbe114e-124b-40cb-a884-9edd94353bba": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ee874ddb-dd03-4843-8a61-202936b2a845": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.112ace31-6c57-405a-8c91-a2a19364fa20": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.df628b2c-64d0-4b35-bbde-c3536bcb05bc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9d57dff8-de30-4e32-8278-c5a947ef8c25": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2c83980a-deb6-4e52-95a8-a87155cc3e2a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7039fa97-b91e-42c4-b974-c75ab08e4d51": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4f6883d1-6421-4350-8ca5-7bfc57da20e9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f343899f-5778-4b23-a97e-bda411656646": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1420a8f0-0482-4fa6-86ec-876d84c27255": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.63c8df59-28ad-49c9-a605-028d5730d2b6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.da4dbacd-671b-45ee-b70e-58aa16de7d8f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d33e4704-c07e-421e-8227-f3f74e9f57ff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a699f864-3453-4f53-92d5-b394bfaebef7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.64f12aa1-bb09-4c30-902f-0e94ffb936cb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ed95d76b-0dba-46a3-aa18-2d5f70b07511": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6e3be613-f4eb-4a14-87cd-398b0161eeda": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2facc6b4-52da-4fc5-b957-e29d06f19ae8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0a3bf034-7203-45c2-aae5-74f9211929fa": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.42e9e133-51d4-4a91-b132-413eece2278c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5920cf0f-3b24-488f-8534-53239f441f5b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bdb5298b-feed-4876-9d61-de877c6534da": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fcd0906c-5337-4f6e-8938-c71c2fe672d8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6842a257-a488-48aa-bb63-5663fe8e9f6a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4c3faf72-fafe-4559-a496-7a0e1ddbc948": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4d1139c2-0183-4670-af08-003694dec455": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.050525d7-3275-486e-8f0e-9548aa81a156": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2234ff18-11e6-4689-9316-cae9fb3f0579": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.516e5193-61d3-4f2b-885b-4e0c5e81c775": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cbfe0f07-d0fc-46d0-950f-167a091e020d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.461af26d-2006-48e4-9aec-6eb2db31d4ef": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1bac9c8b-18bd-4f09-a8ae-867c43798762": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.edacb021-6f94-4f6f-a39b-4362609caea0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.15237599-15e7-496b-a7e0-c02fddae26f8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f2008694-9d04-4952-b40b-ae2fd880d9fe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.da3412f8-9a33-4395-a75e-4d107d2557a4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ca4340a2-6371-457a-8e95-885adbcdc256": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f78a64e6-14a7-4654-95ab-04b1d1bb7318": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.162509c1-9ef9-4647-9ae5-843e6b214cce": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9986a906-35f4-4e86-8dc7-27b8e1f64be8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f9a1b695-bf65-4098-abce-c8593a427731": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f4845b86-e79e-4382-8d78-2376221f9324": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.025f0dde-748b-44f4-93e2-4e0602d30104": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.190e33fc-0d42-49fd-8f4d-1cfd174b988a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.141f3c86-ae34-430f-9cba-d1278047fe0d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.10d399d8-6247-48ef-a1b2-d777ecca827d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1f9686d7-f067-4253-88a6-639125a625a6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.09097ac1-03ea-456c-a1bd-49bdc2bb9499": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d592f939-eaf5-4c33-89f6-8af3b36d338f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cbc726a3-93f3-41e2-ba6b-9c591096eda9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a5edab26-6910-43c9-ba33-3f482849596a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.01f3b831-e981-471f-aef9-076b054e3495": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7c632749-fb6d-4407-a8f2-aac72d959a4d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7281f569-60d5-45bd-8f3c-b01762098f77": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1f99779d-11cb-4679-9a0e-fce1be58f6b7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6433f0ed-d000-473b-8412-c61c8e39a80e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ac11bd02-625e-4eef-83f3-6ed1f24485ff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.16ed92b5-de67-44e4-b11a-7474081a00d2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.12fb6cce-1f55-4359-b189-700c8ba16935": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.999e4bc2-3d7a-4d73-9f5e-62363accde44": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8b84ccf4-bb4b-48fd-8009-2c2641466185": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d783263e-b457-4785-b15c-ce631faf3192": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.733458ea-e46c-49ed-8e8f-de95148cf0bc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2eadbc08-32b4-4485-9cfd-087223e7040b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c798ba8d-2b67-459b-994d-97e286d33ca9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d31baf5d-0590-4126-aa80-85de9beed94f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.aa830670-f0ba-4069-98c1-c71a4e8c7d94": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.acdd68c3-34bb-4a9b-9feb-1c9580852eef": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.71802d07-348e-45af-9fed-f4f8232b9142": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7d242a44-c31b-419e-848e-73eba79f962e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4d270194-23a5-445f-8b66-5ee347054400": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6d13ed35-7c06-41c2-afe7-847072a84d7a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.be0c00dd-5149-4fe2-a17d-03564255330c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7980b93f-4708-4499-8047-08cb9469b4f2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.494f1c44-47b9-48be-9240-5a9df560fdaf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5ec8d076-631f-428e-aaf3-44fef2b83bac": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.13e1b1ea-a0df-43b2-8f1b-e8340bb62df8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.123f0530-1218-4db1-b8ce-aecf38d8ec41": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.024f2c81-68af-4eef-bea5-1b1d43bd1b39": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6118c41e-e92e-4865-9f1c-64dd19e2bc40": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.34e3bc00-ec41-4e3a-986d-af500b03fc5c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5df88778-175b-486a-88fb-aba781cb3b05": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d7d93932-2902-44e3-94d3-331725ce1859": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5da0ef0c-154d-445e-8632-02cd3b280785": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.46604509-5226-42af-ba63-41eeaed19074": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4177af82-b6e3-4200-9fb8-d66f47611742": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7b10727a-2349-4337-8e3e-9ae04f0e98c2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e837c37b-a3b6-49bd-9af7-e3bc771c4786": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.140628f4-5b97-4b01-8a55-ca68cf49c635": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d5957f63-fc2f-4046-864c-9e01c3978a6c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ba009e81-1bbd-44dd-928f-21681d2dc1ff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c373d98a-0558-4f14-a58f-e253e43c3435": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e11ce42f-0d2e-4afb-9017-521fde9521a2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2aed4449-60c0-45a6-884d-73eee930eed8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.92cbe949-7398-4e53-b101-11fd2140c868": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.001f3ebb-79dc-43ad-a363-6dc668d06a0c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f7411fd1-46e2-4056-be8c-89475875f768": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.82f39468-d922-4a18-88d4-9ef7b8b366f1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.301495eb-5851-4dce-9625-779ebb8d7b2b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8b3f37aa-64aa-4d89-8593-52cbf781b713": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2258201f-7beb-4b2a-8a52-ea31c09de73f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.00497277-4b40-4d36-a473-8d8e1a187c18": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.12b405e6-2827-4279-b85a-7f06475a69a4": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9d0e577d-eca2-4b05-9266-00f94901ae69": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.df8406e6-56bf-4de6-a8e0-64caf5b52058": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.62684ebe-62d0-4999-b4c3-c768e371caac": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d421a5a4-8025-4809-8a30-68c723e46af6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.098d8367-a714-4e16-97b5-44f42a2a1cc2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.10105b0a-c18f-4b77-8ac9-bec3250e37b7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fb950c25-8deb-439d-a5c8-1a24b64cd5be": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.771941bc-1dab-4451-ad03-1cf809b2c511": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c15ee1ad-adb1-4017-a5ef-a56071197a38": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.036a8839-c5f9-4206-a979-201e9dac1557": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.41754bbf-ade6-41a3-97f6-90f101c65265": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.192c6112-5287-46c9-9fed-5260db08a41c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a96b6197-2490-4e22-8705-d372ee76664b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.13aced92-5b3d-407d-b242-fb8187a78dd7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2b747510-63ea-489c-88de-af7995d94d45": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.54108c84-c648-4c91-92c6-816711878a4f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4a2000eb-92b5-4a41-8f80-6fa1a6849855": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8f2bed8f-56cb-4269-8e1d-082af6201775": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f076aa19-9261-4d21-8fbc-f330d9d4e87a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.edd8befd-440a-479a-9759-c8f90b4a2528": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.484a7001-9bbd-43fd-b99f-08c6370723d1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f72f7027-2ca5-4473-a8f1-2047d8b400fd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ac349786-bc86-465d-9374-a277d15a892c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4de8ccc0-035a-46b9-870d-6df54238eb65": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d7924931-d38d-4c59-a987-6a10f48a18c9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ef157ce9-4fc5-4441-8592-989b1fcd61b8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.afe43360-ecca-472a-b501-062f898650a5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5715449a-bcad-41cd-bdb7-252d43b3ebcf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cd57083c-1262-450a-aab2-b03fa36456d2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b66e30f0-28a1-459d-a0d2-193d1772ece1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0843614b-645e-4d55-9e70-f960d504cadb": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.12950855-9231-4731-9ccc-e8bc9f61e170": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c1bc355c-4dfb-4ea0-a98e-9801871107f2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4b7e6128-69d3-4511-a3ca-cfba25c6e002": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.79fdad19-834d-463e-89f6-059c0865a034": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.68735c24-e65b-47f6-9c23-e1be5123f6a6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4d65036f-7cf3-4ec5-be30-d20f684b820a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a986dbd9-92fb-45fc-9769-bf75542c9b49": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c6bc2e2d-1817-4856-9e5d-5a5136963485": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.aa72d773-765e-42bb-bf5b-f070a97f5884": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5bc7bc61-6e00-45ed-800d-e324a3ee1196": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.b475d325-7c60-4115-b465-f1d691ab75b0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f98589c7-10e8-4903-b801-f2a42135b190": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.22e50919-7f11-45ed-881e-31482670f416": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.217616ab-32cb-4c7f-b51c-7da3974de4e2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.781bcd5b-be77-4514-bffc-aa56d829aaff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a8f06c67-81eb-471c-9081-0648c9400e27": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4297cfc8-623f-4d32-b353-5a441c2c632f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e01efd03-7851-41b8-a34d-7b7a56d77d31": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1a024983-b73b-4b2c-a350-db9152de27a9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f5117c12-30f6-4bb7-8e7d-32210d6d278e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2d0b16d8-0781-411e-a06b-f62bf9a9c253": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.41b8a70d-5df8-45f5-956a-c30b2f3e06de": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.294ea660-e93e-4596-ad81-5a53d2ba2555": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.23bff06b-34e8-4f9a-ae67-4405393c874c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.daaf3365-9511-4f12-a744-2a8c37a655b9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f38ff989-2a23-4834-9b3a-edc7d016d66d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2cd07893-c184-4369-bbeb-45c2e9e055a7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.62d91e86-a22e-4ef9-851d-bd2b02c411a9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.0cedee86-a2d2-4325-a662-a7399be15d44": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.baa04acc-64aa-435e-b012-1af94d0b0cf1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.820927f5-8c13-4b77-acb7-fae7fb55b459": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f8f9967c-cb22-4c57-b68d-629ca40f3d90": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f4e48486-b923-43bd-a250-d6db2aeb9411": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.27159a73-e3ac-4fa9-b18c-2f70157e31d7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.a76cc0ca-e585-42b5-8ec9-369b95da3eff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.83887671-81a2-4ffc-884c-a2d1b8ccacfa": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.4d20a016-5fcf-45a6-946d-9fabe2319230": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.172b603f-fddb-46cc-ac9e-0cd90a339c77": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.95f8e010-8e75-4da2-ac05-b59763888535": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f3454ba6-e5bd-4d85-838a-b838f8687ce7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2fed4dad-d36f-47f1-9671-07dc97cfb50c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.fe168e9f-37bf-4cb4-b42d-1db79938223b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.113e4367-2915-402c-887f-f7dafdb28c86": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ec6af399-d960-4715-92c5-760fce33d803": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.312fd370-dae0-41b9-977f-282fc553e701": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2492a986-0932-437a-a7b4-414dbebb4a2a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.394246dc-42f8-4fbd-987c-7b62c47b9f06": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d1a650c6-fd8f-4509-801b-10c14f10344e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3933cd74-d4f5-4129-b3a1-71d573c5bf85": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.3681f8cd-22d5-4c2c-b03f-a751bc39753d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.94472cb5-7302-4b56-9fb8-ad96fe2971f8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.44dcbb55-20f6-4737-9557-d6301fca587d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.f33ae168-76dc-4662-9998-5f6729d19523": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.369e9679-fef1-4678-aab9-7edcb39f5533": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d9c346b8-279b-4432-9d3a-539a576da4e2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.7fce2f3b-7564-40a0-8dfc-741c66a3b993": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8a88f79c-3593-4316-8308-8bbc9622d0ec": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1f3f5a8f-412f-4da1-8e7a-4303962079d1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d06d1e0c-2e71-4928-922f-c587f712a8e9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.82839e74-b53c-4d18-af5d-024d8f09fb3f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.26335c09-8a6a-461d-85c7-f0dbe37bb890": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cb4c03ee-f173-483a-b3b6-f9de065a7d04": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.27926937-f426-490f-ac0a-454d9d2def37": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.02777730-3fe8-4eba-8a16-e847042b7351": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c2b27288-d156-4d16-ac94-cf431548f34a": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.042e4d0c-f835-47dd-8075-745df0a7f8f2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.25294346-8919-49c4-affa-d87616ed3df5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.d146f785-7ae1-4728-8d90-20b9cbf8f35d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.1c57b2eb-1206-4833-afb0-a65ec3f432a0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5cc109fc-0d43-4d3d-9523-b60e9b27198d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5a811f7d-30af-40bd-a691-0f181f125541": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.91985c48-6ce5-4270-8f51-478299bb9284": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.8293455b-3322-4e45-a24a-2d64f77db033": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.5c793601-f8ea-470d-8c64-3e669226e651": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
     "node.530c4270-2e61-4e03-af91-4969a5ac9b01": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
diff --git a/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json b/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json
index 43bf9461c..6733d201c 100644
--- a/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json
+++ b/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common mistake I see with new Developers and Development teams when starting with automated testing is to split development time and testing into separate tasks.<\/p>\n\n<p>They'll say when quoting a client or in an estimation session that the development time will take x hours and writing tests will take y hours.<\/p>\n\n<p>This is something I've always avoided.<\/p>\n\n<p>When broken out this way, it implies the automated tests are optional when they should be an integral part of the development process.<\/p>\n\n<p>They aren't a separate task that can be removed or skipped to save time or money.<\/p>\n\n<p>If I take my car to a garage, I don't ask them how long it will take to repair and how long to test what they've done.<\/p>\n\n<p>I want to know how much the whole task will cost and how long it will take.<\/p>\n\n<p>I assume they automatically test and verify the work they do and follow their industry's standard and best practices.<\/p>\n\n<p>I'm doing the same when developing software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "71938847a402f6b5af7c2e34bca063d3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json b/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json
index 247ab866a..35cbd87fd 100644
--- a/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json
+++ b/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Test cases are usually split into two or three sections - \"Arrange, Act, Assert\" or \"Given, When, Then\".<\/p>\n\n<p>If the test has a prerequisite, such as some users or content to be created or in a given state, you create the required environment for the test. With unit tests, this would include mocking any dependencies you need to use.<\/p>\n\n<p>Then you perform an action on the subject under test and, finally, assert that the system is in the desired state.<\/p>\n\n<p>Maybe a user was pending initially, and they're active after running a command or a cron task. You can assert the initial state of the user as well as the final state to ensure the action did what it was supposed to do.<\/p>\n\n<h2 id=\"option-1\">Option 1<\/h2>\n\n<p>To help me get started, I'll sometimes write a test like this with placeholders to separate the test into its separate stages:<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\nfunction should_activate_a_pending_user(): void {\n  \/\/ Arrange.\n\n  \/\/ Act.\n\n  \/\/ Assert.\n}\n<\/code><\/pre>\n\n<p>This makes me think about the different stages and what each might need to contain.<\/p>\n\n<h2 id=\"option-2\">Option 2<\/h2>\n\n<p>Or I might write it out in the \"Given, When, Then\" format:<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\nfunction should_activate_a_pending_user(): void {\n  \/\/ Given I have a user.\n  \/\/ And the user is pending.\n\n  \/\/ When I run the user update command.\n\n  \/\/ Then the user should no longer be 'pending'.\n  \/\/ And the user status should be 'active'.\n}\n<\/code><\/pre>\n\n<p>This takes a little longer to write but feels more familiar if you're used to a behavioural testing framework like Behat.<\/p>\n\n<p>Either way, sometimes, I'll remove the comments once I've written the code around them or leave them to provide additional context.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a1a228d3231ffab8895ec0cbd78f0b1d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json b/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json
index a62ed3e85..0c71feebc 100644
--- a/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json
+++ b/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A side effect of <a href=\"http:\/\/default\/daily\/2023\/03\/04\/why-i-built-a-tool-to-generate-configuration-files\">using a tool to generate build configuration files<\/a> with templates is the consistency that it introduces.<\/p>\n\n<p>The majority of my projects use a PHP-FPM or PHP CLI container. In my Docker Compose file, the service was mostly named <code>php<\/code> but sometimes it was <code>php-fpm<\/code>. In the templated file, it's always named <code>php<\/code>.<\/p>\n\n<p>Some projects would use <code>mysql<\/code> or <code>mariadb<\/code> for the database service and <code>nginx<\/code> or <code>caddy<\/code> depending on which server was being used. These are now always <code>database<\/code> and <code>web<\/code> respectively.<\/p>\n\n<p>As well as being easier to switch between projects and not having to think about which names are used in each codebase, it's also much easier to write tools and automation when the names are consistent.<\/p>\n\n<p>For example, I'd always write a long-ish command to import a database file - reading and unzipping it, and importing it by connecting to the database running in its container. The command would essentially be the same with slight changes based on that project - such as the database service name.<\/p>\n\n<p>Now the command is the same for all projects, and I can automate it by writing a script that works on any project meaning I no longer need to write the long command at all.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "aacb745c094cf5a9f668c64b15000f49",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json b/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json
index 666cc01eb..bcbb69ed3 100644
--- a/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json
+++ b/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I see on many Developers' websites and CVs is percentages or levels of how well they know certain tools and frameworks.<\/p>\n\n<p>Things like \"80% of PHP\" or \"Advanced in HTML and CSS\".<\/p>\n\n<p>But how do you quantify that?<\/p>\n\n<p>Do people alter their percentages accordingly if a new feature is added to a language or framework?<\/p>\n\n<p>Or, instead of trying to show how much you understand, focus on what problems you can solve with those tools and how you can provide value to customers or employers instead of what tools you'd use to do it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3bf8b7e44f82bf7d6ad5ce1fda692ae6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json b/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json
index de3e280a4..9a3089855 100644
--- a/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json
+++ b/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common reason why environments aren't updated and get out of sync is because it's a time-consuming or complex task.<\/p>\n\n<p>The process should be simple to run, quick, reliable and reproducible.<\/p>\n\n<p>It's the same as deploying a change to a staging or production environment.<\/p>\n\n<p>You want the same result on every time on every environment.<\/p>\n\n<p>You want every environment - including <a href=\"http:\/\/default\/daily\/2024\/12\/25\/localhost\">local development environments<\/a> to be as consistent as possible to minimise bugs and errors.<\/p>\n\n<p>To do this, I automate things to make them as simple as possible.<\/p>\n\n<p>I use <a href=\"http:\/\/default\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">run files<\/a> with commands to import databases, perform updates and run pre-update and post-update tasks.<\/p>\n\n<p>I use tools like Nix and <a href=\"http:\/\/default\/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">devenv<\/a> to create identical and reproducible environments.<\/p>\n\n<p>The simpler and quicker is it, the more it can and will be done.<\/p>\n\n<p>You can also use automation to perform long or complex tasks outside of working hours such as sanitising and importing large databases.<\/p>\n\n<p>The more you can automate, the better.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "957251b7baf05530d91b2a9731016317",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.01230324-62b5-442b-80e4-09268a31819b.json b/content/node.01230324-62b5-442b-80e4-09268a31819b.json
index 89862fa7a..7ab11661f 100644
--- a/content/node.01230324-62b5-442b-80e4-09268a31819b.json
+++ b/content/node.01230324-62b5-442b-80e4-09268a31819b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I started learning software and web development with HTML and CSS in 2007. Then I started with PHP and soon after started to learn Drupal 6 (or maybe 5).<\/p>\n\n<p>A lot of Developers' first programming language was PHP and maybe used earlier versions of Drupal before moving to another CMS, framework or language.<\/p>\n\n<p>They still remember, though, how things were when they used it and aren't aware of the advancements and improvements that have been made.<\/p>\n\n<p>The PHP language itself has improved significantly in recent versions with new features and much better peformance.<\/p>\n\n<p>Drupal is more powerful with a lot more available in core compared to when I started to use it and, since adopting modern PHP approaches and third-party code in Drupal 8, writing custom Drupal modules is different with fewer Drupalisms and more industry-standard approaches.<\/p>\n\n<p>If there's a tool you haven't tried for a while, maybe take another look and see if it's improved since you last used it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3baa147faae6a26ac886bb26940c8f43",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json b/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json
index 827b38a4e..7dc33c1b3 100644
--- a/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json
+++ b/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>PHPStan is a static analysis tool for PHP.<\/p>\n\n<p>It finds potential issues in PHP code without needing to run it, so Developers can find and resolve potential issues sooner.<\/p>\n\n<p>I use it on all my projects including existing ones I've inherited.<\/p>\n\n<p>But how can you add a static analysis tool to a codebase without getting a lot of errors from the existing code?<\/p>\n\n<p>PHPStan has different levels of strictness.<\/p>\n\n<p>Level 0 is the least strict and each level adds more rules and strictness, resulting in more errors.<\/p>\n\n<p>Most of the time, people will start by running PHPStan on level 0, fixing any errors and committing the changes.<\/p>\n\n<p>Then repeat the process as many times as needed until you reach the level you want to achieve.<\/p>\n\n<p>I don't think this is the right approach.<\/p>\n\n<p>This could mean that you need to edit the same files multiple times as you work through the levels.<\/p>\n\n<p>There's also a period of time where Developers can still write suboptimal code whilst you work your way up to your desired level.<\/p>\n\n<p>Another approach is to use a feature of PHPStan called the baseline.<\/p>\n\n<p>The baseline is a way of capturing and saving all the existing errors up to the selected level so they are no longer reported.<\/p>\n\n<p>If you did this for an existing project, it would return no errors as everything would be included in the baseline.<\/p>\n\n<p>Once you decide what level you want your project to run, you can start as soon as the baseline is generated and without needing to change files multiple times.<\/p>\n\n<p>Instead of spending time working through the levels one at a time, commit some time to pruning the baseline and reducing the errors in it.<\/p>\n\n<p>This I think is a better approach and how I add PHPStan to existing codebases.<\/p>\n\n<p>To learn more about static analysis and PHPStan, listen to <a href=\"http:\/\/default\/podcast\/22-dave-liddament\">episode 22 of the Beyond Blocks podcast<\/a> with Dave Liddament.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9a7b258b69b97c51304c0aa8d6b87263",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json b/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json
index f8f2080b6..b2e8aef99 100644
--- a/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json
+++ b/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Before I started to use [Tailwind CSS][0], I used CSS preprocessors like Less and Sass to add features like variables and nesting to my CSS files.<\/p>\n\n<p>Stylesheets would be written in .scss, .sass or .less files and processed to create the stylesheets that would be used by browsers.<\/p>\n\n<p>But, with the recent improvements to CSS, do we still need these preprocessors?<\/p>\n\n<p>Here's a very small example of some CSS that just works:<\/p>\n\n<pre><code class=\"css\">:root {\n  --color-primary: red;\n  --color-secondary: green;\n}\n\na {\n  color: var(--color-primary);\n\n  &amp;:hover, &amp;:focus {\n    color: var(--color-secondary);\n  }\n}\n<\/code><\/pre>\n\n<p>It looks like a Sass file, but it's native CSS.<\/p>\n\n<p>It has variables (a.k.a. custom properties) and nesting, which I think are the most used features from preprocessors.<\/p>\n\n<p>But there's no additional build step to generate the end stylesheet. I can use this stylesheet as it is - making it easier to work on and less confusing for new Developers.<\/p>\n\n<p>If I'm not using Tailwind CSS or atomic styles, writing plain CSS files is the approach I'd use.<\/p>\n\n<p>No preprocessors needed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cdd9ab25b0351a9082e1580898e5ecbc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.01f3b831-e981-471f-aef9-076b054e3495.json b/content/node.01f3b831-e981-471f-aef9-076b054e3495.json
index 4e026dd42..4a005336e 100644
--- a/content/node.01f3b831-e981-471f-aef9-076b054e3495.json
+++ b/content/node.01f3b831-e981-471f-aef9-076b054e3495.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Testing - manual or automated - is about building confidence.<\/p>\n\n<p>If we deploy this change or release this feature, are we confident it will work as expected and not cause regressions elsewhere?<\/p>\n\n<p>What if someone asked you on a scale between one and ten?<\/p>\n\n<p>From an automated perspective, have you written enough tests for the feature to be confident it works?<\/p>\n\n<p>If you're fixing a bug, do you have a test that reproduces the bug that was originally failing but now passing since you've added the fix?<\/p>\n\n<p>Do the tests have enough assertions, and have you covered enough use cases and scenarios?<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>You can utilise code coverage metrics, but no hard rule says that the feature will work once x percentage is covered. Something with 100% coverage can still contain bugs.<\/p>\n\n<p>For me, it's about the answer to the question:<\/p>\n\n<p>If we deploy this change, how confident are you that it will work as expected?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "60c550711c51c2b739051e4640eba954",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json b/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json
index b771a7ad5..c94f1c7a6 100644
--- a/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json
+++ b/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json
@@ -87,6 +87,5 @@
             "processed": "<p>There's nothing more frustrating for me than seeing an error I've seen before and not remembering how I fixed it last time.<\/p><p>I try to remember and search for the error message, just to find and read the same articles and posts again or watch the same videos.<\/p><p>I wrote my first blog post on my website in 2010 to document my learning for myself and to share with others.<\/p><p>I've also been a keen note taker, using tools like Evernote and others to take notes and write documentation for myself to refer to in the future.<\/p><p>These days, I just <a href=\"http:\/\/default\/daily\/2024\/11\/10\/write-plain-text-files\">write plain text files<\/a> using <a href=\"https:\/\/github.com\/nickjj\/notes\">Nick Janetakis' notes program<\/a>, which I've modified slightly <a href=\"http:\/\/default\/daily\/2025\/04\/21\/patch\">by patching it<\/a> to create daily notes instead of monthly ones.&nbsp;<\/p><p>They're fast to write, easy to search and available offline if I'm traveling or away from my computer.<\/p><p>I much prefer being able to search my notes and find what I'm looking for or, if it's a post that I've written publicly, searching online and finding my own answer.<\/p><p>Whether you're a new or experienced Developer, you're always learning new things, so write them down for yourself and, if you want, write publicly and share your learnings with others.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json b/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json
index 70b549196..92b59f34b 100644
--- a/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json
+++ b/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently <a href=\"https:\/\/x.com\/StefanGalescu\/status\/1798421063355007017\">saw this post on X<\/a>, talking about an open-source project.<\/p>\n\n<p>This was the part that I want to highlight:<\/p>\n\n<blockquote>\n  <p>I was also impressed by the decisions documents. More projects should implement this concept.<\/p>\n<\/blockquote>\n\n<p>Looking at the repository, it contains records of 36 decisions made on the project between May 2023 and April 2024.<\/p>\n\n<p>Decision records provide useful information to new people to a project, whether you want to contribute to an open-source project or it's a new client or work codebase.<\/p>\n\n<p>The code and project will likely continue once you've finished working on it, so capturing decisions for future Developers is key.<\/p>\n\n<p>I've often joined projects and wondered why or how something was done, and can only guess as the decision wasn't recorded or is somewhere not available to me, such as an old wiki or ticketing system.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I agree with the poster.<\/p>\n\n<p>More people should record the decisions made on their project, whether it's open-source or not.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bc11c3125e2e228f16b76f91b749c764",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json b/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json
index 2db8fb91d..518b0641a 100644
--- a/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json
+++ b/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When reviewing a pull or merge request, tools like GitHub and GitHub offer the option to squash the commits before merging.<\/p>\n\n<p>If the request had twenty commits, they'd be combined into a single commit before being merged.<\/p>\n\n<p>But should you do it?<\/p>\n\n<p>The answer will be \"it depends\" based on the project or team, but I'm personally not a fan of squashing commits.<\/p>\n\n<p>Even though I commit small changes often, I put quite a bit of effort into <a href=\"http:\/\/default\/daily\/2023\/01\/24\/small-commits-and-good-commit-messges\">crafting commits and writing detailed commit messages<\/a> that capture the reason for each change. If the commits are squashed, either the messages will be combined into one extra-long commit message or I've seen them be deleted completely.<\/p>\n\n<p>One large commit message would be very difficult to read and connect specific messages with their changes, and deleting the commit body would lose the history completely and waste the time it took to write the messages and craft the commits. It may be available within the pull or merge request page but there's no guarantee that you'll continue to use the same repository hosting service in the future.<\/p>\n\n<p>One large commit would also be difficult to debug if there was an error. If the whole feature was added in a single commit, tools like <a href=\"http:\/\/default\/daily\/2023\/01\/23\/debugging-with-git-bisect\">git bisect<\/a> would no longer work and a single commit couldn't be simply reverted if it contained a bug.<\/p>\n\n<p>I prefer to keep the original small commits and instead prefer to use rebasing and only fast-forward merges to avoid merge commits and keep a simple, linear history in my Git log, and be able to easily read, find and, if needed, fix the code that's been committed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "54447bfd288cd6e71d4b06bd0646502d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json b/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json
index 1726a3422..90988d4f9 100644
--- a/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json
+++ b/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In yesterday's email, I mentioned that deprecating code allows it to be backwards compatible - but what does that mean?<\/p>\n\n<p>If I were to remove a function like <code>drupal_set_message()<\/code> that is used code elsewhere in an application, the code would no longer work and would break.<\/p>\n\n<p>As a module or library maintainer, I don't want to cause applications to break by making backward incompatible changes (a \"BC break\" or a \"breaking change\").<\/p>\n\n<p>Maintaining backward compatibility means that people who use the code can update to the latest version without breakages, and if they use any deprecated code, they know to update it to be compatible with future versions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "18e7b8e123a0c299bb44600a75b56d9e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json b/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json
index 8c2c5f37c..d591a8bdf 100644
--- a/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json
+++ b/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I was speaking with a colleague about configuring Git, which led to a conversation about dotfiles repositories - somewhere where you version the changes to your configuration files and, usually, create symlinks to their expected locations.<\/p>\n\n<p>Afterwards, I realised the first commit to <a href=\"https:\/\/github.com\/opdavies\/dotfiles\">my personal dotfiles repository<\/a> was over eight years ago, in July 2015.<\/p>\n\n<p>What started as a repository to put my own Git configuration has undergone various changes since the tools I use changed, as well as the tools to manage the files themselves.<\/p>\n\n<p>In 2021, I switched my <code>.vimrc<\/code> configuration file to an <code>init.vim<\/code> and switched to Neovim full-time and, most recently, almost a year ago, I started to use the Nix package manager and later adopted NixOS as my primary Linux distribution.<\/p>\n\n<p>My complete NixOS and Home Manager configurations are within my <code>dotfiles<\/code> repository, and the configuration for tools, including Neovim, tmux and Git.<\/p>\n\n<p>I wonder what the repository will look like in another eight years...<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b663fb9c5e0257d2fdece24454ad3bfd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json b/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json
index 941036510..9ffc86930 100644
--- a/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json
+++ b/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I've been at an event run by a local animal rescue charity. It's one that we attend often as my children like to enter the dog show, but this year, I've also sponsored one of the categories.<\/p>\n\n<p>As well as organising the PHP South Wales user group, I'm also now a sponsor - donating books and elePHPant plushies for raffle prizes and paying the group's Meetup.com subscription costs.<\/p>\n\n<p>Giving back and supporting open-source maintainers and content creators is a big priority of mine. If I use some open-source software or find that someone's Twitch or YouTube channel is useful, if that person or organisation is on GitHub or Patron, then I'll sponsor them, or I'll subscribe to their channel.<\/p>\n\n<p>If I find a useful blog post or video, I'll add a comment or link to it on Twitter, thanking them and letting them know that it helped me.<\/p>\n\n<p>Especially if it's something that I've used within my projects, it makes sense to support it and it's maintainers, so that they keep working on and improving the software, continue streaming, and keep writing blog posts and recording videos for me to learn from.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "891d018e5d9b5fa68288878004365cce",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json b/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json
index d8951f2b1..833fba019 100644
--- a/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json
+++ b/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How do you validate an idea from a client or stakeholder?<\/p>\n\n<p>Unlike a minimum viable product, which is the smallest amount of functionality for a feature to be released, a proof of concept is an initial investigation into whether the idea is viable.<\/p>\n\n<p>What's the least amount of development you can do to prove the concept?<\/p>\n\n<p>Can you create something using a smaller data set or with simplified functionality?<\/p>\n\n<p>What can you build within a minimal timeframe so, if the idea isn't used, too much time wasn't invested in it, but still verifies it?<\/p>\n\n<p>Do you need to write any code or do any development at all?<\/p>\n\n<p>All we need to do is find out if the concept could work.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f671ea961bdda4e275277b04dc159c79",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json b/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json
index aac457b30..01a1be1a2 100644
--- a/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json
+++ b/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The main programming languages I write are PHP and JavaScript.<\/p>\n\n<p>Both offer types where, as well as declaring a parameter or property, you can define what type it is - whether it's a string, array, boolean, etc.<\/p>\n\n<p>Adding types is optional.<\/p>\n\n<p>You don't need to add types to your PHP code, and you can choose to write plain JavaScript instead of TypeScript.<\/p>\n\n<p>Some people prefer simpler or cleaner code or less \"visual debt\".<\/p>\n\n<p>I like the extra clarity that types add.<\/p>\n\n<p>I like to be able to read some code and immediately know what types things should be.<\/p>\n\n<p>I like the clearer errors and messages if a different type is given than was expected.<\/p>\n\n<p>Tools like PHPStan know more about my code and give better recommendations than if I don't add types.<\/p>\n\n<p>I like the better autocompletion I get when writing code that has types.<\/p>\n\n<p>I like types, but I also like the flexibility of whether or not to add them and for Developers and development teams to make their own decisions based on their preferences.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c50e363614371738c421f8a32ee763f3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json b/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json
index 80d7a01d6..6ae1bbb5a 100644
--- a/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json
+++ b/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2023\/11\/03\/why-your-company-should-contribute-to-open-source-software\">Yesterday's email<\/a> explained why your company should contribute to open-source software, but why should you contribute as an individual?<\/p>\n\n<p>Most of the same reasons apply, such as gaining experience and improved knowledge from contributing.<\/p>\n\n<p>As an individual, you can build your own reputation and personal brand.<\/p>\n\n<p>You'll get exposure from contributions and involvement with initiatives, such as the Drupal admin UI improvements and other core initiatives, which look great on your CV and LinkedIn profile.<\/p>\n\n<p>This could lead to better career opportunities and potential projects.<\/p>\n\n<p>I've had paid development work directly from my open-source code contributions, as well as public speaking and event organising, so I can vouch for this.<\/p>\n\n<p>Like companies, if you make money from open-source software - either a salary or from paid projects or courses - it's in your interest to contribute so the software you use is maintained and improved so it's the best it can be.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0f37079942ad6ce63ae32e8ea7c57c79",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json b/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json
index 20c3e8880..71b41bdb7 100644
--- a/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json
+++ b/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Does your team have a \"No deploy Friday\" policy?<\/p>\n\n<p>What about not deploying after a certain time in the afternoon?<\/p>\n\n<p>These approaches are attempts to minimise risk when deploying.<\/p>\n\n<p>If there is an issue, will someone be available during the evening or weekend to resolve it?<\/p>\n\n<p>To me, this indicates the deployment process is too complicated, possibly due to a lack of automation, or deployments aren't happening frequently enough.<\/p>\n\n<p>Having a <a href=\"http:\/\/default\/daily\/2025\/01\/30\/gatekeeper\">robust and passing CI pipeline<\/a> that runs automated checks and tests is crucial to know the code is deployable.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2023\/09\/28\/feature-flags-enable-continuous-integration\">Feature flags are a great way<\/a> to separate deploying code from releasing changes to users, which means you don't need to avoid pushing some code until the change is complete. It can be done incrementally and released over several deployments.<\/p>\n\n<p>Too much time between deployments is a smell.<\/p>\n\n<p>The more time there is between a deployment and the larger the changeset, the riskier the deployment will be.<\/p>\n\n<p>There is more to go wrong and it'll be harder to diagnose and resolve any issues.<\/p>\n\n<p>I always advocate for many smaller releases than larger less frequent ones.<\/p>\n\n<p>Ideally, a production release every day - even if the changes are small or everything is hidden behind feature flags.<\/p>\n\n<p>Deploying on Friday is easy if you last deployed on Thursday.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "021827be7bf3f083020a0f2ff11066d8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0318e249-a9a8-476f-9bd4-432544369917.json b/content/node.0318e249-a9a8-476f-9bd4-432544369917.json
index abd9d7501..2a844e1cc 100644
--- a/content/node.0318e249-a9a8-476f-9bd4-432544369917.json
+++ b/content/node.0318e249-a9a8-476f-9bd4-432544369917.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2025\/01\/13\/patches\">Applying patch files<\/a> is a common way to customise and extend open source software, and how we used to submit changes to Drupal before issue forks and merge requests were added to Drupal.org.<\/p>\n\n<p>Some software, such as dwm and st from suckless.org are released as minimal versions that you patch to add features to.<\/p>\n\n<p>If you find a line of code that you want to add, edit or delete, a patch file describes the changes so you can re-apply them whenever the source file changes.<\/p>\n\n<p>Patching offers unlimited customisation and flexibility.<\/p>\n\n<p>Whatever changes you want to make, you can.<\/p>\n\n<p>The downside is you need to maintain any patches you've written.<\/p>\n\n<p>If a change is made that causes your patch to no longer apply, you'll need to update the patch.<\/p>\n\n<p>There are some patches I commonly apply to Drupal projects, but I'll try to either contribute the changes back to the Drupal so I no longer need the patch or make the change in a custom module.<\/p>\n\n<p>Sometimes, though, <a href=\"http:\/\/default\/daily\/2025\/01\/14\/patching-drupal\">patching is the only option<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e1882c079f5b933697958ec2ac91a1b7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json b/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json
index 833ae8771..dba56f68b 100644
--- a/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json
+++ b/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>My website is built with Sculpin - a static site generator written in PHP.<\/p>\n\n<p>It uses a some of the same Symfony components as Drupal, uses Twig for templating and YAML for configuration, and has similar features like content types and taxonomies for structuring content.<\/p>\n\n<p>When I first created my website it was on Drupal 6 and upgraded to Drupal 7 before I started to take an interest in static site generators and later using Jekyll, Sculpin and Astro (and Sculpin, again).<\/p>\n\n<p>I enjoyed learning Sculpin and took it as an opportunity to learn Twig before Drupal 8, which I spoke about in <a href=\"http:\/\/default\/presentations\/test-drive-twig-with-sculpin\">the first Sculpin talk I gave<\/a>, at DrupalCamp North in July 2015.<\/p>\n\n<p>I had three Git repositories, the current Sculpin one, the Astro version, and the original Sculpin version with its first commit in March 2015 - a few months before DrupalCamp North.<\/p>\n\n<p>Static site generators keep the files in text files intead of a database, so I was wondering if it was possible to merge the repositories together and combine the information whilst keeping the same commit history so existing tags and contribtions would still apply to the original commits.<\/p>\n\n<p>In short, I was able to do it by adding the old repositories as additional remotes and using the <code>--allow-unrelated-histories<\/code> <a href=\"https:\/\/git-scm.com\/docs\/git-merge#Documentation\/git-merge.txt---allow-unrelated-histories\">option for git merge<\/a>.<\/p>\n\n<p>After fixing some minor merge conflicts, everything was merged successfully and I have [one repository containing 5,272 all commits][2], going back to 2015.<\/p>\n\n<p>This makes it older than <a href=\"http:\/\/default\/daily\/2023\/08\/08\/8-years-of-dotfiles\">my dotfiles repository<\/a>, which I started in July 2015.<\/p>\n\n<p>Similar to <a href=\"http:\/\/default\/daily\/2024\/07\/31\/why-i-use-linux\">why I use Linux<\/a>, I believe in owning your own content rather than relying on third-party platforms, so having all my content and history in one repository is great.<\/p>\n\n<p>And I learned something new about Git at the same time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cc353a3343b4a9ed6dc01850a09c8f76",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json b/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json
index ee4d0661d..4e2bd240c 100644
--- a/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json
+++ b/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently started as a Mentor for the School of Code, working with a student on their cohort that started last week. Whilst the Bootcamp is focussed on JavaScript and node, and is currently looking at front-end development and using APIs, we've already started talking about different back-end technologies and frameworks.<\/p>\n\n<p>Something that I've believed for a while is that software development is about solving problems and different languages and frameworks are tools to use to solve the problem and achieve the desired result. The programming fundamentals that he's learning now can be applied to different languages and some may be better depending on the problem that needs to be solved.<\/p>\n\n<p>I've also said when speaking with a client this week that development is about adding business value.<\/p>\n\n<p>Whilst there is some value to doing security updates and maintenance to keep an application running and secure, I'd much rather be working on tasks that directly add value for the client like some of the tasks I've done for them recently like improving eCommerce conversions and adding new payment methods or revenue streams.<\/p>\n\n<p>It's easier for the client to justify and see the results of the work, it improves the experience for their customers or users, and it's more interesting and fulfilling for me.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7256a5bb0e6800a548d88e2979344646",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json b/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json
index 8dfe76d70..f82f6cdef 100644
--- a/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json
+++ b/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/podcast\/2-alternate-realities\">This week's episode<\/a> of the Beyond Blocks podcast is live, where I speak with Panagiotis Moutsopoulos (vensires on Drupal.org) - Drupal Backend Developer at E-Sepia.<\/p>\n\n<p>We discuss his first time DrupalCon and, more specifically, his session \"Drupal's Alternate Realities\" - a \"Birds of a Feather\" (BoF) session presenting some history, but mainly the different ways to tackle a problem in Drupal using different methodologies.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4ddf140ca0555c2028d2bb2db394282f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json b/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json
index 85d82b9d0..9d868adfa 100644
--- a/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json
+++ b/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are three things you can do with legacy code.<\/p>\n\n<p>Refactor it, remove it or replace it.<\/p>\n\n<p>You can refactor it to make it easier to maintain and change in the future.<\/p>\n\n<p>If it's not needed, you can remove it.<\/p>\n\n<p>If it's not used, there's no need to keep it.<\/p>\n\n<p>Or you can replace it with something else.<\/p>\n\n<p>There isn't one right answer and the correct approach will depend on the situation and objective.<\/p>\n\n<p>In a future email, I'll give some examples of how I refactor legacy code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a3ea19c23705f4574c9b1455cc2169bc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json b/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json
index 2bc2585d5..bca2bd993 100644
--- a/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json
+++ b/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2024\/11\/27\/nix-as-an-operating-system\">my laptop configuration<\/a>, <a href=\"http:\/\/default\/daily\/2024\/11\/30\/using-nix-for-local-application-development\">local development environments<\/a> and <a href=\"http:\/\/default\/daily\/2024\/11\/28\/running-nixos-in-the-cloud\">production server<\/a>, I've also been using Nix for something else recently.<\/p>\n\n<p>Setting up and configuring a Homelab on an old laptop.<\/p>\n\n<p>I've been able to install and configure services like Jellyfin for playing video files, Immich for photo hosting and management, Gitea as my own Git server, Vaultwarden for securely storing my passwords and Traefik as a reverse proxy.<\/p>\n\n<p>Each of these was very easy to configure with only a few lines of the Nix language and avoided a heavy use of Docker which seems common in most Homelab setups.<\/p>\n\n<p>Next, I'd like to add home automation with Home Assistant and explore running a local DNS server within my network.<\/p>\n\n<p>I'm looking forward to these, and seeing what else I can add to this setup using Nix and NixOS.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ddffb71cbb4982c0c4d9ca78fecdcd4c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json b/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json
index d73539315..3425f95df 100644
--- a/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json
+++ b/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After yesterday's post on why I prefer using Git on the command line rather than using a GUI tool, today I thought that I'd post about how I've configured Git.<\/p>\n\n<p>First, I rarely ever run the <code>git<\/code> command - I usually run a <code>g<\/code> function that I've created within my zsh configuration.<\/p>\n\n<p>Rather than being an simple alias, it's a shell function that will run <code>git status -sb<\/code> to show the current status of the repository if there are no additional arguments. If there are, such as when running <code>g add<\/code>, then this is executed as a normal Git command. (This is something that I first saw from Thoughtbot, if I remember correctly).<\/p>\n\n<h2 id=\"using-.gitconfig\">Using .gitconfig<\/h2>\n\n<p>The main part of my configuration is within Git's <code>~\/.gitconfig<\/code> file, where I can configure Git to work how I want.<\/p>\n\n<p>For example, I like to avoid merge conflicts, so I always want to use fast-forward merges whilst pulling and also to rebase by default. I can do this by adding <code>ff = only<\/code> and <code>rebase = true<\/code> to the <code>[pull]<\/code> section of my <code>~\/.gitconfig<\/code> file.<\/p>\n\n<p>I can do this manually, or running <code>git config --global pull.rebase true<\/code> will set the option but also update the file automatically.<\/p>\n\n<p>Some of the tweaks that I've made are to only allow fast-forward merges by adding <code>merge.ff = only<\/code>, automatically squash commits when rebasing by setting <code>rebase.autosquash = true<\/code>, and automatically pruning branches by adding <code>fetch.prune = true<\/code>.<\/p>\n\n<h3 id=\"simple-aliases\">Simple aliases<\/h3>\n\n<p>Another way that I configure Git is using aliases, which are also within the <code>~\/.gitconfig<\/code> file.<\/p>\n\n<p>For example, if I ran <code>git config --global alias.b \"branch\"<\/code>, then running <code>git b<\/code> would just run <code>git branch<\/code> which shortens the command and saves some time and keystrokes.<\/p>\n\n<p>I have similar one- or two letter \"short\" aliases for pushing and pulling code, and some that also set some additional arguments such as <code>aa<\/code> for <code>add --all<\/code> and <code>worktrees<\/code> for <code>worktree list<\/code>.<\/p>\n\n<h3 id=\"more-complicated-aliases\">More complicated aliases<\/h3>\n\n<p>Aliases can be more complex if needed by prefixing it with a <code>!<\/code>, meaning that it executes it as a shell command.<\/p>\n\n<p>This means that I can have <code>repush = !git pull --rebase &amp;&amp; git push<\/code> to chain two separate Git commands and combine them into one, and <code>ureset = !git reset --hard $(git upstream)<\/code> which executes the full command, including another alias as part of it.<\/p>\n\n<p>I also have <code>issues = !gh issue list --web<\/code> and <code>pulls = !gh pr list --web<\/code> to open the current repository's GitHub issues or pull requests respectively, which can be done as it's not limited to just running <code>git<\/code> commands.<\/p>\n\n<h3 id=\"custom-functions\">Custom functions<\/h3>\n\n<p>Finally, if an alias is getting too long or complex, then it can extracted to it's own file.<\/p>\n\n<p>Any executable file within your <code>$PATH<\/code> that starts with <code>git-<\/code> will automatically become a Git command.<\/p>\n\n<p>One example that I have is <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/blob\/2b20cd1e59ae3b1fa81074077e855cbdfa02f146\/bin\/bin\/git-cm\">git-cm<\/a> which, similar to the <code>g<\/code> function`, is a bash script that checks for any arguments passed to it and runs a slightly different command. It achieves the same thing as if it were an alias, but it does make it easier to write and maintain as it's in a separate file.<\/p>\n\n<p>These are just some examples. If you want to see my entire configuration, then check out <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/tree\/2b20cd1e59ae3b1fa81074077e855cbdfa02f146\/roles\/git\/files\">my dotfiles repository on GitHub<\/a>.<\/p>\n\n<p>How have you configured Git for your workflow? Reply to this email and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4d3892ad51836bdd33e47e7043615d75",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json b/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json
index be9ace625..e0c57f56d 100644
--- a/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json
+++ b/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The more code you have, the more potential problems you have.<\/p>\n\n<p>More code means more opportunities for bugs in your software.<\/p>\n\n<p>There's more code to maintain and more chance of encountering breaking changes as you update between major software versions of your project's dependencies, such as a CMS or framework.<\/p>\n\n<p>If you can keep your amount of code to a minimum and reduce the maintenance overhead, you are less likely to experience issues.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "137f467c7894dcf4d534ab6c7572567a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json b/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json
index f86304c1f..0e05915c0 100644
--- a/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json
+++ b/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Code review with pull and merge requests is great for open-source but not for development teams or soloists.<\/p>\n\n<p>On an open-source project, the code changes are most likely being submitted by someone you don't know and don't work with regularly, so having a step to review the code prior to merging it and decide if you want to take on the responsibility of maintaining it is a big decision.<\/p>\n\n<p>On a development team, you work closely with the person submitting the change request and you have a shared responsibility and ownership of the code being added. The person isn't going to submit their change and not be seen again.<\/p>\n\n<p>It takes time for code to be reviewed, which means it takes longer for the change to be released to users.<\/p>\n\n<p>If you're a soloist, are you going to submit a request for you to review your own code?<\/p>\n\n<p>If you don't need to do code review on your team, do you need to create feature or topic branches?<\/p>\n\n<p>I'd suggest sticking to one canonical branch and doing trunk-based development instead.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "54fdebe3f9556a6d18a8f24c72f72652",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.050a5113-59bc-461e-ac78-420e16055303.json b/content/node.050a5113-59bc-461e-ac78-420e16055303.json
index 1132b0225..084a763af 100644
--- a/content/node.050a5113-59bc-461e-ac78-420e16055303.json
+++ b/content/node.050a5113-59bc-461e-ac78-420e16055303.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week on the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a>, I'm joined by Dan Leech - a PHP Developer and open-source project creator.<\/p>\n\n<p>He and I recently gave talks at the PHP South West meetup, where Dan introduced a new project - PHP-TUI - for building terminal user interfaces (TUIs) with PHP.<\/p>\n\n<p>I use one of Dan's other open-source projects - Phpactor - within Neovim, and he also presented at PHP South Wales about PHPBench, so it was great to discuss and learn more about these in this episode.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/6-dan-leech-php-tui\">Listen to the episode now<\/a>, and I'll be back with more in the New Year.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3cc8c054a1675b2ab1a1ec63dd5f49ad",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.05232b81-d945-4112-99bf-d1adb2552428.json b/content/node.05232b81-d945-4112-99bf-d1adb2552428.json
index 0ae10181f..7fecd4d5b 100644
--- a/content/node.05232b81-d945-4112-99bf-d1adb2552428.json
+++ b/content/node.05232b81-d945-4112-99bf-d1adb2552428.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've noticed a lot of Developers recently adopting SQLite for their database and I wonder why this is.<\/p>\n\n<p>Laravel changed their default database to SQLite for local development.<\/p>\n\n<p>It simplifies the development environment as there's no need for a separate database like MySQL or MariaDB but, if you'll be using one of those in production, won't that cause more issues when you migrate your local application?<\/p>\n\n<p>Drupal supports using SQLite, but, other than for <a href=\"http:\/\/default\/atdc\">my automated testing course<\/a>, or when running automated tests, I've always used a MySQL or MariaDB database.<\/p>\n\n<p>Maybe this is something to keep an eye on and potentially use more for some scenarios in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "91a7ebf19cb056c110911fc721129f1a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0610a25f-884a-48b6-8be0-e969749d316a.json b/content/node.0610a25f-884a-48b6-8be0-e969749d316a.json
index 33ee76c7b..bddd99e18 100644
--- a/content/node.0610a25f-884a-48b6-8be0-e969749d316a.json
+++ b/content/node.0610a25f-884a-48b6-8be0-e969749d316a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>With most things, it's easy to see where an issue is. There's only one way to build a car or a mobile phone, for example.<\/p>\n\n<p>With other things, such as software, it's not as clear.<\/p>\n\n<p>There are usually multiple ways to achieve the same result, but not all implementations are equal.<\/p>\n\n<p>It's important to understand if an issue is caused by the software itself or how it's been implemented.<\/p>\n\n<p>Some approaches may be quicker, better for end-user experience or more performant.<\/p>\n\n<p>Each has its own advantages and disadvantages.<\/p>\n\n<p>What was the correct solution then may not be the best one now.<\/p>\n\n<p>Priorities may have changed or new approaches could be available.<\/p>\n\n<p>You know more now about the problem that's being solved than you did at the time.<\/p>\n\n<p>One of the original discarded solutions could now be the best option, or a new option that wasn't previously available that solves the problem in a different way.<\/p>\n\n<p>The software may be capable of achieving what you want - it may just need to be configured in a different way.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "838a5e92a344c70d064478815bc8dd16",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json b/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json
index 6320964b7..0a46a83dd 100644
--- a/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json
+++ b/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A quote I heard from DrupalCon, made by my former colleague Tim Lehnen - CTO at the Drupal Association - when talking about contribution:<\/p>\n\n<blockquote>\n  <p>Contribution is what makes Drupal thrive.<\/p>\n  \n  <p>Drupal is built by people.<\/p>\n  \n  <p>No one entity, no one person builds Drupal.<\/p>\n  \n  <p>It's you who builds Drupal.<\/p>\n<\/blockquote>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "957b36c5f9d9b70a87a9a60d1f31f9ab",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json b/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json
index 8f731db06..b062c09d1 100644
--- a/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json
+++ b/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2024\/06\/03\/writing-comments-first\">writing comments first<\/a>, when writing tests, I sometimes like to write my tests backwards and start by writing the assertions first.<\/p>\n\n<p>I know what I want to assert in the test, so it's an easy place to start.<\/p>\n\n<p>I'll run it, see the error, fix it and continue working backwards.<\/p>\n\n<p>For example, I could start with this:<\/p>\n\n<pre><code class=\"php\">public function testOnlyPostNodesAreShown(): void {\n  $assert = $this-&gt;assertSession();\n  $assert-&gt;pageTextContains('Post one');\n  $assert-&gt;pageTextContains('Post two');\n  $assert-&gt;pageTextNotContains('This is not a post');\n}\n<\/code><\/pre>\n\n<p>This test will fail when I run it, but it makes me think about what I need to do to fix the error and how to do so in the best way.<\/p>\n\n<p>In this case, I need to make a request to the page that should render the text:<\/p>\n\n<pre><code class=\"php\">public function testOnlyPostNodesAreShown(): void {\n  $this-&gt;drupalGet('\/blog');\n\n  $assert = $this-&gt;assertSession();\n  $assert-&gt;pageTextContains('Post one');\n  $assert-&gt;pageTextContains('Post two');\n  $assert-&gt;pageTextNotContains('This is not a post');\n}\n<\/code><\/pre>\n\n<p>This will still fail, as I also need to create the required posts:<\/p>\n\n<pre><code class=\"php\">public function testOnlyPostNodesAreShown(): void {\n  PostBuilder::create()-&gt;setTitle('Post one')-&gt;getPost();\n  PostBuilder::create()-&gt;setTitle('Post two')-&gt;getPost();\n\n  $this-&gt;createNode([\n    'title' =&gt; 'This is not a post',\n    'type' =&gt; 'page',\n  ]);\n\n  $this-&gt;drupalGet('\/blog');\n\n  $assert = $this-&gt;assertSession();\n  $assert-&gt;pageTextContains('Post one');\n  $assert-&gt;pageTextContains('Post two');\n  $assert-&gt;pageTextNotContains('This is not a post');\n}\n<\/code><\/pre>\n\n<p>Now the test passes.<\/p>\n\n<p>Doing test-driven development keeps my code clean and minimal, and I find this approach keeps my test clean, too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3bdc81d1ff8f05f8b1beb3069dfdd370",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json b/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json
index 1628a42c1..85520b1bd 100644
--- a/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json
+++ b/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, it was announced that Newport City Council's (my local council) website is now running on LocalGov Drupal - a distribution for council websites.<\/p>\n\n<p>This increases the total to 44 councils in the UK and Ireland.<\/p>\n\n<p>Newport is the first Welsh council to use it and the first LocalGov website to be bilingual, serving content in both English and Welsh.<\/p>\n\n<p>It's great to see Drupal adoption continue to grow in Wales and within the Welsh public sector, and LocalGov being adopted by more councils across the UK and Ireland.<\/p>\n\n<p>I think LocalGov Drupal is a great project and one <a href=\"https:\/\/github.com\/localgovdrupal\/localgov_alert_banner\/pull\/225\">I've contributed to previously<\/a>, and I plan to do more in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2955d4cb562bc0a9ba0456bc040c629b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json b/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json
index aac618038..6eb7e4471 100644
--- a/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json
+++ b/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It's shown in the examples of the <a href=\"http:\/\/default\/daily\/2023\/11\/24\/are-conventional-commits-worth-it\">conventional commits specification<\/a> as part of the optional footer data.<\/p>\n\n<p>But is it useful?<\/p>\n\n<p>It can be if your issue tracker is linked to your Git repository and you can click the issue ID in a commit message and see the issue.<\/p>\n\n<p>But, how often do teams change issue-tracking software or the project is passed to a different company that uses a different issue tracker?<\/p>\n\n<p>That makes the issue IDs that reference the old IDs useless as no one has access to the issues it references.<\/p>\n\n<p>I'd recommend putting as much information in the commit message itself and not relying on it being in an external source, like an issue tracker.<\/p>\n\n<p>The Git log and commit messages will remain even if a different issue tracker is used, or a different team starts working on the project, and that additional information isn't lost.<\/p>\n\n<p>I'm not against putting the issue ID in the commit message but don't do it instead of writing a descriptive commit message.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1029a860138fe970164e891ad1617d01",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.08209d64-40fa-4771-9415-c23e962a5028.json b/content/node.08209d64-40fa-4771-9415-c23e962a5028.json
index 04714395d..48f4d10ef 100644
--- a/content/node.08209d64-40fa-4771-9415-c23e962a5028.json
+++ b/content/node.08209d64-40fa-4771-9415-c23e962a5028.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Usually, in software development, there isn't always a definitive black-and-white answer to a question or situation.<\/p>\n\n<p>Most of the time, the answer is \"it depends\".<\/p>\n\n<p>How you approach a problem depends on context.<\/p>\n\n<p>How long do you have?<\/p>\n\n<p>Are you working on the final version or a prototype or minimum-viable product?<\/p>\n\n<p>Should you use a contributed module or write one yourself?<\/p>\n\n<p>What if an existing module hasn't been updated for some time or doesn't have tests or other quality checks included?<\/p>\n\n<p>Do you write custom CSS or use a framework like Tailwind CSS or Bootstrap?<\/p>\n\n<p>Should this project be written in this framework or CMS, or would a different one be better suited?<\/p>\n\n<h2 id=\"here%27s-the-thing...\">Here's the thing...<\/h2>\n\n<p>There are usually multiple approaches to achieve the same result.<\/p>\n\n<p>Decisions will depend on a combination of various factors. In a different situation, the answer could be different.<\/p>\n\n<p>This doesn't make any solution outright wrong.<\/p>\n\n<p>It was right given the situation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f40826212e5c798e718edd8ad155d3c0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json b/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json
index 8bb3fa25d..d7c6b1967 100644
--- a/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json
+++ b/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I took a bit of time off from these emails whilst I was preparing for the first PHP Stoke event which happened last week in Stoke-on-Trent.<\/p>\n\n<p>It was a great event with around 35 attendees and two other speakers as well as myself.<\/p>\n\n<p>The <a href=\"http:\/\/default\/presentations\/things-you-should-know-about-php\">latest version of my slides are online<\/a> as well <a href=\"http:\/\/default\/things-about-php\">some updated resources<\/a>.<\/p>\n\n<p>My next talk will be at the Norfolk Developers conference next month where I'll be presenting an updated version of <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS<\/a>.<\/p>\n\n<p>If you have a topic idea for a talk or would like me to speak at your meetup or conference, please get in touch.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c6186e7dbf6c19f8512dc083f70d7840",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json b/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json
index 8d0dcb4d1..33b4e27f7 100644
--- a/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json
+++ b/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>\"Frequency reduces difficulty\" is a phrase I heard on a podcast today, though I have heard it before.<\/p>\n\n<p>It's a better way of saying, \"If it hurts, do it more often\".<\/p>\n\n<p>If software deployments and releases are large, risky, and contain bugs, break them into smaller, less-risky deployments and release them more often.<\/p>\n\n<p>If you get a lot of merge conflicts in Git, merge your code more frequently. Make your topic branches as short-lived as possible, or try trunk-based development and avoid topic branches by default.<\/p>\n\n<p>If writing tests is difficult and takes time, persevere. It will get easier the more you do it, and you'll save time in the future by releasing fewer bugs and being able to refactor safely.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "48855aeeae21e4c8f58c4898ddd9fea4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json b/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json
index 43b434b79..9e2cbdc6c 100644
--- a/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json
+++ b/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The Override Node Options module that I said yesterday is used on 35,000 websites isn't a complicated module.<\/p>\n\n<p>It doesn't add a lot of features.<\/p>\n\n<p>It solves a problem by adding additional permissions to Drupal that site administrators can assign to user roles and not need to give a more global permission like \"administer nodes\".<\/p>\n\n<p>The problem being solved is allowing users to set node options, like the created date or published status, in a secure way.<\/p>\n\n<p>If it wasn't solving a problem, it wouldn't be used on 35,000 Drupal websites.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1c6afa84bf0230b6fc71cdc42239c6e2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json b/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json
index d5d079ef0..2e44c5dce 100644
--- a/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json
+++ b/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of my favorite features that was introducted in PHP 8 was promoted constructor properties.<\/p>\n\n<p>If I'm passing arguments into a constructor, I can declare a visibility and it will be promoted to a property on the class.<\/p>\n\n<p>Here's an example of a value of a data transfer object that accepts a sort code and account number as strings:<\/p>\n\n<pre><code class=\"language-php\">class AccountDetails {\n\n  public function __construct(\n    public string $accountNumber,\n    public string $sortCode,\n  ) {}\n\n}\n<\/code><\/pre>\n\n<p>Without promoted constructor properties, I'd need to create the properties and assign them manually, and I'd have this:<\/p>\n\n<pre><code class=\"language-php\">class AccountDetails {\n\n  public string $accountNumber;\n\n  public string $sortCode;\n\n  public function __construct(\n    string $accountNumber,\n    string $sortCode,\n  ) {\n    $this-&gt;accountNumber = $accountNumber;\n    $this-&gt;sortCode = $sortCode;\n  }\n\n}\n<\/code><\/pre>\n\n<p>Whilst text editors and IDEs can create the properties automatically, I prefer this as it's less code, more readable and easier to understand.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6e7b86e1b92a964e048c10b4a1bb65da",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json b/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json
index ea39a1563..96083eea7 100644
--- a/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json
+++ b/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been using Drupal since 2008 and built the first version of my website with Drupal 6 before updating it to Drupal 7.<\/p>\n\n<p>Around that time, I discovered static site generators and built the next version of my website with Jekyll.<\/p>\n\n<p>I liked how I could write content in simple plain files, export them to HTML and upload them to a server.<\/p>\n\n<p>Static websites are fast and secure.<\/p>\n\n<p>There was no need for PHP or a database. Just a simple web server like Apache or Nginx that can serve static files.<\/p>\n\n<p>I later switched to Sculpin, a static site generator written with PHP, which has a lot of similarities with Drupal.<\/p>\n\n<p>But what if you want the power of Drupal with the benefits of a static website?<\/p>\n\n<p><a href=\"https:\/\/www.drupal.org\/project\/tome\">Tome<\/a> is a module that turns Drupal into a static site generator.<\/p>\n\n<p>Drupal works the same locally with access to all the usual core functionality and contrib modules and themes from Drupal.org, but you export everything to static files - the same as using Jekyll or Sculpin.<\/p>\n\n<p>Sam Mortenson, the creator of the Tome module discussed it on <a href=\"http:\/\/default\/podcast\/19-sam-mortenson\">our episode of the Beyond Blocks podcast<\/a> where we also talked about single file components.<\/p>\n\n<p>If you want the power of a flexible content management system and the performance and security benefits of a static website, Tome gives you the best of both worlds.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2b68ef78311dde7624d8a9f3bf2aecd5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json b/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json
index d7680363a..ae7fba060 100644
--- a/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json
+++ b/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I started developing websites in HTML and CSS in 2007 before adopting PHP and Drupal in 2008.<\/p>\n\n<p>Since then, I've used Drupal 6, 7, 8, 9 and 10 to deliver applications for clients, agencies and in-house teams.<\/p>\n\n<p>I also use Symfony and Laravel, as well as JavaScript, TypeScript and Vue.js.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>There isn't one outright \"best\" programming language, CMS or framework.<\/p>\n\n<p>It depends on the project and its requirements as well as the knowledge and experience of the team working on it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6878d25dc442270921c029ddd00724c8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json b/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json
index f2ee22d67..0fa7854b1 100644
--- a/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json
+++ b/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As with client applications, I recommend releasing new versions of open-source software as often as possible.<\/p>\n\n<p>This makes it easier for users to update to newer versions as they can easily see the changes, and less risky as it's easier to roll back or diagnose the problem if there is an issue.<\/p>\n\n<p>If you've added a feature or fixed a bug, fewer people will likely use it if it's not within a released version of your project and sat on a development branch or waiting for a tagged release. This means they're not benefiting from the changes and getting value from them.<\/p>\n\n<p>You can add feature flags to hide work-in-progress features that you don't want people to use yet, but you don't want to block yourself from releasing a new version until it's complete.<\/p>\n\n<p>Regular releases encourage smaller and simpler changes rather than larger and more complex - and potentially breaking - changes.<\/p>\n\n<p>I like to have a release day each month to release new versions of my open-source projects, which works well for me.<\/p>\n\n<p>I have a recurring task on my To Do list to review my projects and tag and release any new versions that are needed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2a66b63393fa72ffccd1e378ef840bca",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json b/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json
index 0824072c3..31e20b58d 100644
--- a/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json
+++ b/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday I replied to <a href=\"https:\/\/x.com\/ianmiell\/status\/1304103008242991111\">a post on X<\/a>:<\/p>\n\n<blockquote>\n  <p>I have worked on many teams that use CI tooling and call their process CI, but I have never seen CI actually done as defined on Wikipedia:<\/p>\n  \n  <p>\"CI is the practice of merging all developers' working copies to a shared mainline several times a day\"<\/p>\n<\/blockquote>\n\n<p><a href=\"http:\/\/default\/blog\/continuous-integration-vs-continuous-integration\">I've written about this before<\/a> and I think the term CI or CI\/CD is one of the most misused or misleading in software development.<\/p>\n\n<p>CI, or continuous integration, is, as the post days, the process of everyone merging their changes at least once, or usually several, times a day.<\/p>\n\n<p>It isn't something that is configured or created - it's a process.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>You can do CI without a CI pipeline and vice versa.<\/p>\n\n<p>You can have a CI pipeline but not do continuous delivery or deployment.<\/p>\n\n<p>What most people think of as CI or CI\/CD is a set of automated checks that run when code is updated - usually on a feature or topic branch.<\/p>\n\n<p>Whilst important, it's not \"CI\".<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "44876b1c656f7fa3e4611f4f47e7c361",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json b/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json
index 0b6fc8df2..8210834a0 100644
--- a/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json
+++ b/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last Friday and Saturday, I was happy to attend and present two sessions at DrupalCamp Ghent in Belgium.<\/p>\n\n<p>I was able to present talks on automated testing and Tailwind CSS, which were my 99th and 100th talks, respectively!<\/p>\n\n<p>The sessions were streamed live, or the slides and previous recordings <a href=\"http:\/\/default\/dcg\">are on my website<\/a>.<\/p>\n\n<p>It was a great event and it's always nice to see and meet new people within the Drupal community, to see new places and share knowledge by giving presentations.<\/p>\n\n<p>Reply and let me know if you have any feedback on the sessions or if you'd like me to present a talk or workshop at your event.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "666722719a2759d76794a08b3c2837fa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json b/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json
index c78cc7e4e..a277c3809 100644
--- a/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json
+++ b/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When giving talks and workshops or coaching on automated testing and test-driven development, some people may not have written tests before and aren't familiar with the structure or know where to begin.<\/p>\n\n<p>In the workshops I ran for DrupalCamp London and DrupalCamp NYC, I wanted to cover this first before writing any implementation code.<\/p>\n\n<p>Where do you put a test class, and what does it contain?<\/p>\n\n<p>How do you run the tests, and how can you make it pass or fail?<\/p>\n\n<h2 id=\"what-we-did\">What we did<\/h2>\n\n<p>To start, we wrote a test for existing functionality within Drupal core - anonymous users can visit the front page.<\/p>\n\n<p>This is the whole test:<\/p>\n\n<pre><code class=\"language-php\">&lt;?php\n\nnamespace Drupal\\Tests\\my_module\\Functional;\n\nuse Drupal\\Tests\\BrowserTestBase;\nuse Symfony\\Component\\HttpFoundation\\Response;\n\nclass MyModuleTest extends BrowserTestBase {\n\n&nbsp; protected $defaultTheme = 'stark';\n\n&nbsp; \/** @test *\/\n&nbsp; public function the_front_page_loads_for_anonymous_users() {\n&nbsp; &nbsp; $this-&gt;drupalGet('&lt;front&gt;');\n\n&nbsp; &nbsp; $this-&gt;assertResponse(Response::HTTP_OK);\n&nbsp; }\n\n}\n<\/code><\/pre>\n\n<p>This is a test someone can write, run and see the test pass.<\/p>\n\n<p>They can then experiment by changing the values to make the test fail in different ways.<\/p>\n\n<h2 id=\"what-next%3F\">What next?<\/h2>\n\n<p>Then, we tested anonymous users cannot access the administration pages, which is also already the case in Drupal core, and then authenticated users with the correct permissions could access them.<\/p>\n\n<p>People were getting the idea by now, and we moved on to writing and testing some of our own code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "af41a18ab3e2e252ab86e7243333ad9f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json b/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json
index 84ff4a80e..76fc6b5ab 100644
--- a/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json
+++ b/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common cause of not refactoring code is a lack of test coverage.<\/p>\n\n<p>Why change some code if it works? What if we break it whilst refactoring it and introduce a regression?<\/p>\n\n<p>If the code has accompanying automated tests, this can't happen.<\/p>\n\n<p>The tests should be passing before starting a refactor and should be passing once the refactor is complete.<\/p>\n\n<p>If the tests fail, the refactor was unsuccessful and should be reverted.<\/p>\n\n<p>If you have a CI pipeline, a failing test should break the pipeline and prevent any further steps if you're doing continuous delivery or deployment whilst signalling to the Developer their refactor was unsuccessful and the pipeline needs to be fixed.<\/p>\n\n<p>Without tests, the code could be broken during the refactor, and we wouldn't know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "aa56bdd02fef215659f339a51ad72312",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json b/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json
index a325627f7..a30d5ea8a 100644
--- a/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json
+++ b/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If <a href=\"http:\/\/default\/daily\/2025\/02\/18\/conflicts\">feature branches cause conflicts<\/a>, what is the alternative?<\/p>\n\n<p>Don't branch.<\/p>\n\n<p>Keep all changes on a single branch and avoid merge conflicts between branches by not having branches.<\/p>\n\n<p>But how can you avoid releasing changes before they are ready?<\/p>\n\n<p>You can have a local branch with your changes that you don't push and rebase locally, but then <a href=\"http:\/\/default\/daily\/2025\/02\/17\/ci-cd\">you're not doing continuous integration<\/a> and you're just as likely to get conflicts and have incompatible code.<\/p>\n\n<p>One of the main benefits of trunk-based development, where everything is on a single branch, is that everyone's work always works together.<\/p>\n\n<p>The better option is to use feature toggles (aka feature flags).<\/p>\n\n<p>Wrapping code in feature toggles separates deploying the code from releasing the feature.<\/p>\n\n<p>The code can be released, but the feature isn't active until the toggle is enabled.<\/p>\n\n<p>This means everyone can work on the same branch and continuously deploy changes whilst being selective about the features that are visible to the end users.<\/p>\n\n<p>If you have multiple environments, the same code can be used with different toggles enabled to allow for testing different features.<\/p>\n\n<p>Then, once the feature is ready to be enabled, there is no deployment needed.<\/p>\n\n<p>The code is already there - it just needs to be enabled.<\/p>\n\n<p>For Drupal, there is a <a href=\"https:\/\/www.drupal.org\/project\/feature_toggle\">Feature Toggle module<\/a> and <a href=\"https:\/\/www.drupal.org\/project\/feature_toggle_twig\">an extension that I wrote<\/a> that make it easy to use and manage feature toggles by just logging into the admin UI and selecting the active toggles you want.<\/p>\n\n<p>And, if an issue is discovered, it can also be easily disabled <a href=\"http:\/\/default\/daily\/2025\/02\/19\/back-or-forward\">without needing to roll back to the previous version<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "118c906a95ca0d083c79dec04035d210",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json b/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json
index 488519dd7..e148c8235 100644
--- a/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json
+++ b/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Instead of <a href=\"http:\/\/default\/daily\/2024\/05\/31\/putting-glue-on-pizza\">using AI to autocomplete code<\/a> or <a href=\"http:\/\/default\/daily\/2024\/10\/08\/ai-in-drupal\">perform tasks within your Drupal website<\/a>, I've seen people using AI as a virtual pair programming partner.<\/p>\n\n<p>Similar to using a search engine or finding results on websites like Stack Overflow, but also being able to ask follow-up questions and for clarification as part of a conversation.<\/p>\n\n<p>You're still relying on its answers and advice to be correct, but using AI as a learning tool seems like a sensible approach if you don't have a non-AI pairing partner available.<\/p>\n\n<p>Just make sure to validate and verify whatever it gives you.<\/p>\n\n<p>Once you've committed it, you're responsible for it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e41c8f0126dd0649815f7d2f25e91bbc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json b/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json
index 265d4a56d..d3349ffba 100644
--- a/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json
+++ b/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Following the announcement at DrupalCon, the official announcement has been released regarding Drupal 7's end-of-life extension:<\/p>\n\n<blockquote>\n  <p>Today, we are officially announcing that Drupal 7 will reach its end of life on January 5, 2025.<\/p>\n  \n  <p>With this final extension, the Drupal Security Team is also adjusting the level of support provided.<\/p>\n  \n  <p>This will be the final extension.<\/p>\n<\/blockquote>\n\n<p>If you're involved with one of the ~400,000 Drupal 7 websites (according to https:\/\/www.drupal.org\/project\/usage\/drupal), what does the additional year and a half of Drupal 7 mean to you?<\/p>\n\n<p>Will you use the time to find the budget to upgrade, assemble a migration plan, port any missing contributed modules or refactor your custom modules or theme to make it easier to upgrade?<\/p>\n\n<p>Is it different knowing it\u2019s the final extension compared to the previous time when it wasn\u2019t known if it would be extended again?<\/p>\n\n<p>If you're stuck on Drupal 7 or staying on it into 2024 or 2025, what's stopping you from upgrading?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3d0846676f872cb7c1f67b9afcb995ac",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json b/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json
index 833ad0ad6..51bc4fb96 100644
--- a/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json
+++ b/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently saw a social media post that said something like \"Don't add blank lines within functions. They take up space and don't add anything\".<\/p>\n\n<p>I may have misremembered the exact wording, but that was the gist of it.<\/p>\n\n<p>I like to add blank lines within my functions to create and add separation between logical blocks of code.<\/p>\n\n<p>Whilst this doesn't add anything for a computer parsing and serving the code, or a CI pipeline performing checks, it makes the code easier for people to read and understand which, it my opinion, adds its own value - even if the functionality is the same.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d138c01e7e0e6b18b39148606ce5111a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json b/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json
index b0c147eed..ff224011e 100644
--- a/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json
+++ b/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A major addition to my Git workflow has been the ability to interactively add hunks of code to be committed.<\/p>\n\n<p>There's <code>git add -i<\/code> to interactively add, though I usually go straight to <code>git add -p<\/code> to use <code>patch<\/code>.<\/p>\n\n<p>This will ask you to confirm if you want to add each hunk to the commit (a.k.a. the staging area) or not.<\/p>\n\n<p>For example, here's the prompt I get whilst working on the post for this email:<\/p>\n\n<pre><code class=\"shell\">diff --git a\/source\/_daily_emails\/2024-05-06.md b\/source\/_daily_emails\/2024-05-06.md\nindex 42fe48f..ef36a2b 100644\n--- a\/source\/_daily_emails\/2024-05-06.md\n+++ b\/source\/_daily_emails\/2024-05-06.md\n@@ -4,10 +4,12 @@ date: 2024-05-06\n permalink: daily\/2024\/05\/06\/interactive-staging\n tags:\n   - software-development\n-    # - drupal\n-    # - php\n-    # - podcast\n+    - git\n cta: ~\n snippet: |\n   TODO\n ---\n+\n+A major addition to my Git workflow has been the ability to interactively add hunks of code to be committed.\n+\n+There's `git add -i` to interactively add, though I usually go straight to `git add -p` to use `patch`.\n+There's `git add -i` to interactively add, though I usually go straight to `git add -p` to use `patch`.\n(1\/1) Stage this hunk [y,n,q,a,d,s,e,?]?\n<\/code><\/pre>\n\n<p>I can add the whole hunk, split it into smaller hunks, add all the hunks in the file or ignore this hunk and later hunks in the file.<\/p>\n\n<p>Then the process is repeated for any following hunks.<\/p>\n\n<p>This means I can add the relevant hunks to craft the commit I want and I can keep my commits small and meaningful, and easy to revert if there is an issue.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4f660d322ca2ed3306e781c6c10053a1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json b/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json
index 81952507b..4dba67f2d 100644
--- a/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json
+++ b/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently decided I'm going to open source <a href=\"http:\/\/default\/presentations\/building-build-configs\">Build Configs tool<\/a> that I use to generate build configuration files for Drupal, Sculpin and Fractal projects.<\/p>\n\n<p>Inspired by <a href=\"http:\/\/default\/presentations\/working-with-workspace\">Workspace<\/a> and others, and based on previous versions of similar tools - most recently by <a href=\"https:\/\/github.com\/ALT-F4-LLC\/build-configs\">TheAltF4Stream's project with the same name<\/a> (which is written in Rust and supports different template types) - I've been using this tool to manage configuration files for various personal, client and open-source projects.<\/p>\n\n<p>Before I open-source it, there are some changes I'd like to make, such as renaming some template types and updating the format and keys within the configuration file.<\/p>\n\n<p>Changes to the configuration file would be a breaking change and, whilst it's only me using it, I want my other projects to keep working and for me to continue supporting the prior versions - at least for now, so I want to make sure any changes are backward compatible.<\/p>\n\n<h2 id=\"how-it-works\">How it works<\/h2>\n\n<p>There are four steps performed when generating files for a project:<\/p>\n\n<ul>\n<li>Create a final configuration object from the project's configuration file as well as any defaults.<\/li>\n<li>Validate the final configuration.<\/li>\n<li>Create a list of files to generate.<\/li>\n<li>Generate the files.<\/li>\n<\/ul>\n\n<p>If I change <code>sculpin<\/code> to <code>sculpin-site<\/code> in a configuration file, for example, it will fail the validation step.<\/p>\n\n<p>But, I have an opportunity within the first step to perform any normalisation that's needed and to provide a compatibility layer - such as changing <code>sculpin-site<\/code>, which is an invalid value, to <code>sculpin<\/code>.<\/p>\n\n<p>I also renamed <code>symfony<\/code> to <code>symfony-cli<\/code> by performing the same step.<\/p>\n\n<p>This means the validation step will receive valid data that it can use and the new changes have been encapsulated within a single step of the process. I haven't needed to change any code elsewhere.<\/p>\n\n<p>I can also add deprecation warnings if legacy values are used.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Similar to feature flags, this is temporary code that will later be removed when I'm ready to remove the compatibility layer, similar to how <code>drupal_set_message()<\/code> was deprecated and changed to use the <code>Messenger<\/code> service before being removed in Drupal 9.<\/p>\n\n<p>In the future, I can refactor the internal logic to use a different approach and when I'm ready, eventually remove the compatibility layer and tag a new major version with the breaking changes.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a38ce17b89e3700c2d33876324be5747",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json b/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json
index 5da138e98..a7c77963c 100644
--- a/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json
+++ b/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I started using the Nix package manager <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\/commit\/af1d8d37\">in September 2022<\/a> as a replacement for Ansible.<\/p>\n\n<p>Since then, I've switched to daily-driving NixOS as my main operating system and Home Manager to manage my dotfiles (configuration files for managing application settings, like Neovim, tmux and Alacritty).<\/p>\n\n<p>A benefit I didn't initially think of was that now I can write all my configuration files in the Nix language.<\/p>\n\n<p>I don't need to write YAML, TOML, INI or JSON configuration files. Nix and Home Manager will convert it for me.<\/p>\n\n<p>For example, see <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/blob\/172b7c9ca61d2dd6ffdc967af9102b1ca24edd81\/nix\/modules\/home-manager\/git.nix#L25\">my Git configuration written in Nix<\/a> which is converted and written to .gitignore.<\/p>\n\n<p>And, if there isn't a built-in module for what I need, there are functions like <code>toJSON<\/code> that will convert Nix code to JSON that I can write to a file.<\/p>\n\n<p>This is also great if a program changes its configuration file language, which Alacritty did recently.<\/p>\n\n<p>They changed from YAML to TOML and I didn't need to change anything.<\/p>\n\n<p>Nix has become my one configuration language to rule them all.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "afe58adbc88026446b4472112f8ea2a7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json b/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json
index 4dc6abd1d..287cd3228 100644
--- a/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json
+++ b/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Computers don't care how code is written or formatted, but humans do.<\/p>\n\n<p>A computer will parse and execute your code whether it's written on a single line or multiple.<\/p>\n\n<p>So, don't optimise for computers.<\/p>\n\n<p>Optimise your code for humans.<\/p>\n\n<p>People read more code than they write, so write your code in a readable way so it's easy for people to read and understand - not the computer.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "00288ea28683ef7e8d770a0109344500",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json b/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json
index d951b54dd..a29ba441a 100644
--- a/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json
+++ b/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Surprisingly, it's been two and a half years since I last did a live coding stream.<\/p>\n\n<p>As well as talk recordings and demos, I did a few live streams back then, working on the \"Test-Driven Drupal\" project and submitting a merge request to Drupal core.<\/p>\n\n<p>It's been something that I'd like to get back into and pick up again, and I plan on doing that within the next few weeks.<\/p>\n\n<p>I have a new freelance project due to start in December but getting back into streaming seems like a good way to make sure that I put aside time for open-source and side projects, as well as for writing longer form blog posts and hopefully starting to prepare more meetup and conference talks again.<\/p>\n\n<p>I'll be streaming again on my YouTube channel, so if you'd like to be notified when I do, <a href=\"https:\/\/www.youtube.com\/channel\/UCkeK0qF9HHUPQH_fvn4ghqQ?sub_confirmation=1\">please subscribe<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ed9692196aea3236ab447bca233fd4bc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json b/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json
index 4d8245e34..23660660d 100644
--- a/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json
+++ b/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json
@@ -87,14 +87,5 @@
             "processed": "\n          <h2 id=\"what-is-a-changelog%3F\">What is a Changelog?<\/h2>\n\n<p>A Changelog is a file that documents changes made to a codebase.<\/p>\n\n<p>In its simplest form, it's a plain text file within a code repository, or it can be written in Markdown or reStructuredText or kept within a separate tool like Confluence or Sharepoint. Regardless of where it's kept, the main thing is the content.<\/p>\n\n<p>It's not a copy of the Git log. It's a summary of the changes to be read by humans and for them to see what's changed, not a list of Git commits.<\/p>\n\n<p>If you're considering using my open-source package, you can see what changes I've released, when, and what changes are due to release.<\/p>\n\n<h2 id=\"how-is-it-structured%3F\">How is it structured?<\/h2>\n\n<p>Each version should have a heading specifying the version number and\/or release date and a list of changes grouped by their type - whether something was added, changed, deprecated, removed, etc. This works well if you use conventional commits!<\/p>\n\n<p>I like to follow a format called <a href=\"https:\/\/keepachangelog.com\">Keep a Changelog<\/a>.<\/p>\n\n<p>The headings link to a diff so you can see all of the commits and changes made to the code, and there's an <code>Unreleased<\/code> section that shows commits that have yet to be tagged and released.<\/p>\n\n<p>If you need to present changes to a review or approval board, having an easy-to-read list of changes, separated by their type, is a much clearer format than a list of Git commits.<\/p>\n\n<h2 id=\"when-should-it-be-updated%3F\">When should it be updated?<\/h2>\n\n<p>I recommend continually updating the Changelog rather than leaving it to just before a deployment. It's quick to add it to the <code>Unreleased<\/code> section as part of the commit and update the headings later.<\/p>\n\n<h2 id=\"can-i-see-an-example%3F\">Can I see an example?<\/h2>\n\n<p>Sure. See the one I added to the <a href=\"https:\/\/github.com\/opdavies\/national-rail-enquiries-feed-parser\/blob\/main\/CHANGELOG.md\">National Rail Enquiries feed parser library<\/a> I've been working on or the <a href=\"https:\/\/git.drupalcode.org\/project\/tailwindcss\/-\/blob\/5.x\/CHANGELOG.md\">Tailwind CSS starter kit theme for Drupal<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e760bef0560b6cb431513a24b2eb0212",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0d707bca-be14-4504-b500-9e44abebab44.json b/content/node.0d707bca-be14-4504-b500-9e44abebab44.json
index 1fa8cccd0..c820c8490 100644
--- a/content/node.0d707bca-be14-4504-b500-9e44abebab44.json
+++ b/content/node.0d707bca-be14-4504-b500-9e44abebab44.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In some of my first emails to this list, I wrote about <code>just<\/code> and <code>run<\/code> files.<\/p>\n\n<p>Both allow you to write project-specific aliases and commands. For example, instead of running <code>docker compose exec php phpunit<\/code>, you run <code>just test<\/code> or <code>run test<\/code>.<\/p>\n\n<p>While <code>just<\/code> uses a simple Makefile-like syntax, it requires its own program, so it needs to be installed.<\/p>\n\n<p>While I have it installed locally, I've had instances where CI pipelines have failed because they can't download and install <code>just<\/code> and not because of an error in my code.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>A <code>run<\/code> script is a file of Bash functions.<\/p>\n\n<p>Because it's written in Bash, it runs anywhere without installing additional dependencies.<\/p>\n\n<p>If a CI pipeline fails, which is less often, it's due to a failure within my code and not because of a download error.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ef1660e036d0cc4b520bdd563fad7f86",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json b/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json
index 21200a29f..f89286658 100644
--- a/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json
+++ b/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>With Drupal 7's end-of-life date of the 5th of January 2025 quickly approaching, I've recently seen again a number of companies offering support for Drupal 7 after its end-of-life date.<\/p>\n\n<p>I've seen the same in corporate IT environments where they're running versions of software post their EOL date, so it's not only Drupal 7, but I wonder if this is a good thing?<\/p>\n\n<p>Is this deterring companies from upgrading if they know this is an option, or should everyone upgrade and we can move forward from Drupal 7 and other end-of-life software?<\/p>\n\n<p>According to <a href=\"https:\/\/www.drupal.org\/project\/usage\/drupal\">https:\/\/www.drupal.org\/project\/usage\/drupal<\/a>, there are still 281,000 active Drupal 7 installations.<\/p>\n\n<p>It's considerably less than before - this  time last year, it was over 380,000 installations - but it's still a lot of Drupal 7 being used.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e3227fd692a43f0f5a3b4f9afed9df94",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json b/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json
index a39640de0..2eb0d5a9c 100644
--- a/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json
+++ b/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common misunderstanding for new Developers is that Git and GitHub are the same thing, but they aren't.<\/p>\n\n<p>Git is decentralised, so doesn't rely on using external repositories on services like GitHub, GitLab or Bitbucket.<\/p>\n\n<p>You can run <code>git init<\/code> and use it locally without pushing to any remote services.<\/p>\n\n<p>These services also add extra terminology, such as forks, syncing and pull or merge requests which aren't part of Git itself.<\/p>\n\n<p>This can cause confusion, which is why <a href=\"http:\/\/default\/daily\/2022\/08\/23\/git-gui-command-line\">I think it's important to learn Git itself<\/a> instead of relying on external services or desktop apps.<\/p>\n\n<p>And, if you're going to use a remote repository, consider something like Gitea, which you can host yourself and keep control of your data.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "22be20101f09fc0d4e10cd3c6b867b76",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json b/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json
index e6fa47566..c074463a1 100644
--- a/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json
+++ b/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I made my <a href=\"https:\/\/github.com\/opdavies\/drupal-module-template\">Drupal module template<\/a> compatible with Drupal 10.<\/p>\n\n<p>Because Drupal 10 is developed from Drupal 9, the changes between the two and the changes required are minimal.<\/p>\n\n<p>In this case, I only needed to change the <code>core_version_requirement<\/code> in <code>drupal_module_template.info.yml<\/code> from <code>^9<\/code> to <code>^9 || ^10<\/code> - meaning the template works for both Drupal 9 and 10, so there's no need for different versions.<\/p>\n\n<p>If it used any deprecated code that was removed before Drupal 10, I'd have needed to update it to use the Drupal 10-compliant code.<\/p>\n\n<p>Updating to new major Drupal versions is much easier than it used to be!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d9902d3f03d57f8eef7e67d29133f05f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json b/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json
index 9bf4cfb38..d41ea0a96 100644
--- a/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json
+++ b/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been a Drupal and Linux user for a long time, as well as using command-line tools and utilities like Neovim and tmux.<\/p>\n\n<p>Since September 2022, I've used NixOS as my daily operating system on my computers.<\/p>\n\n<p>Based on similar programs, in particular by ThePrimeagen, I wrote and use a program to automatically open tmux sessions and run initial commands for any project in my Code directory.<\/p>\n\n<p>In October, he released <a href=\"https:\/\/github.com\/ThePrimeagen\/tmux-sessionizer\">tmux-sessionizer as its own package<\/a>.<\/p>\n\n<p>There is a <code>tmux-sessionizer<\/code> already in nixpkgs, but <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/nix-config\/src\/commit\/28d75ce6b85e0852aa3f8454bab4f2206ad7e50a\/pkgs\/tmux-sessionizer\/default.nix\">I wrote my own derivation<\/a> to use Prime's.<\/p>\n\n<p>There was also this problem in the code:<\/p>\n\n<pre><code class=\"bash\"># If someone wants to make this extensible, i'll accept\n# PR\nselected=$(find ~\/ ~\/personal ~\/personal\/dev\/env\/.config -mindepth 1 -maxdepth 1 -type d | fzf)\n<\/code><\/pre>\n\n<p>These directories don't match what I use on my computers.<\/p>\n\n<p>People have submitted pull requests, but these haven't yet been merged.<\/p>\n\n<p>Either I change my directory structure or I can't use it.<\/p>\n\n<p>But, in my derivation, I can apply my own patch files to make any changes I want - such as changing the directories to ones I'd want to use - making it usable for me.<\/p>\n\n<p>I can also apply other people's patches, the same as I'm doing with dwm.<\/p>\n\n<p>Someone has created a pull request to make the directories dynamic based on a configuration file.<\/p>\n\n<p>I can apply these changes as a patch to my configuration and remove my custom one.<\/p>\n\n<p>I can make any other changes I want or need to.<\/p>\n\n<p>The possibilities are endless.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8a79fcd4efce6727224214430cc26505",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json b/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json
index c1e02dfda..1493409d6 100644
--- a/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json
+++ b/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This morning, I was asked a \u201cCould you build\u2026\u201d question.<\/p>\n\n<p>It was an idea mentioned a short while ago and involves a simple, interactive form on the front end that sends requests to a public API, filters the results from the response and displays them to the user.<\/p>\n\n<p>I\u2019d probably want to hide the API request behind a service responsible for interacting with the API and filtering the results - ensuring that the API could be switched with something else later if needed.<\/p>\n\n<p>This afternoon, I built a small proof-of-concept application with Vue.js and TypeScript.<\/p>\n\n<p>There\u2019s no API, or service retrieving real-time results. All of the data is hard-coded within the App component, as well as the code that filters, sorts and returns the results.<\/p>\n\n<p>The results are shown by adding a <code>&lt;pre&gt;&lt;\/pre&gt;<\/code> to the page, with a <code>&lt;pre&gt;&lt;\/pre&gt;<\/code> to show the input data.<\/p>\n\n<p>There isn\u2019t even any styling, with just some basic horizontal rules to split the page - similar to <a href=\"https:\/\/twitter.com\/taylorotwell\/status\/1203356860818087944\">these screenshots from Taylor Otwell<\/a> of some work-in-progress versions of Vapor and Nova.<\/p>\n\n<p>A working proof of concept, or a \"spike\", answers the initial \"Can we build...\" question. It can be shown to a client or other stakeholders, act as a starting point for discussions and requirements gathering and then be turned into user stories. It also allows the Developers to validate their initial thoughts and experiment with different approaches.<\/p>\n\n<p>If the spike is successful, the idea can then be moved forward and implemented in a full way, otherwise, it can be stopped with a minimal amount of effort and time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f378ea534b4141dc8290191f8941df2c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json b/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json
index 98508dec3..a2088d39f 100644
--- a/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json
+++ b/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json
@@ -87,6 +87,5 @@
             "processed": "<p>I've been surprised to still recently find software development agencies using their own proprietary content management systems and frameworks.<\/p><p>With so many available open source options, like Drupal and Symfony, why would people write their own?<\/p><p>Why spend the time and effort to build basic functionality like user registration and login when existing tools already solve that problem?<\/p><p>Why ignore the thousands of open source modules, themes, plugins, packages and libraries that are available?<\/p><p>Instead, leverage the tools that already exist and focus on solving domain-specific issues and writing code that's genuinely specific to the project.<\/p><p>Then you can contribute some of the saved time back to the project and make it better for yourself and others in the future and ready for the next project.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json b/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json
index 39dd61f07..bc13c42a9 100644
--- a/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json
+++ b/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've built Drupal websites for 18 years and have worked with versions as old as Drupal 5.<\/p>\n\n<p>A common issue for people using the CMS has been the editorial experience when adding and editing content.<\/p>\n\n<p>Once logged in, to add or edit a node, they need to go to a separate administration screen to enter or change the content.<\/p>\n\n<p>The administration page usually looks nothing like what the page will look like once published, with the user only seeing large forms and different styles, or a different theme altogether.<\/p>\n\n<p>There is a page preview option, but this only works once the forms have been completed and requires the user to be able to \"see\" how the page will look beforehand and know what content will appear where.<\/p>\n\n<p>This has become trickier with the use of Paragraphs and entity reference fields, where the editor only sees the title of the content they want to reference but not what they will see or how it will look.<\/p>\n\n<p>As well as being difficult to create content, it also makes it difficult to edit it.<\/p>\n\n<h2 id=\"layout-builder\">Layout Builder<\/h2>\n\n<p>This is why I like Drupal's Layout Builder module.<\/p>\n\n<p>Originally released as a contributed module, it has been part of Drupal core since 8.7 and allows editors to be able to create complex pages using a drag and drop interface and instantly see how they look.<\/p>\n\n<p>There's now an ecosystem of Layout Builder-related modules, <a href=\"https:\/\/www.drupal.org\/project\/layout_builder_extra_templates\">including one I wrote<\/a>, that add more functionality to the Layout Builder, such as adding more template suggestions, restricting the available blocks, or adding inline styles - making it even more powerful.<\/p>\n\n<p>If you have a Drupal site and haven't tried Layout Builder, you can incrementally opt in and only enable it for certain content types. You don't need to go all in straight away.<\/p>\n\n<p>But, I think that once you've tried it, you won't be able to go back.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cba5205b68a6ba553b9b34ef661692d2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json b/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json
index f9ba1ccbd..d74cece71 100644
--- a/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json
+++ b/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Before adding a new feature or change to a codebase, ask if it's really needed and consider its long-term implications.<\/p>\n\n<p>Code is easy to write, but needs to be maintained as newer language or framework features are added or have breaking changes.<\/p>\n\n<p>Something I've added recently to Build Configs was an option to use an <a href=\"http:\/\/default\/daily\/2024\/01\/27\/gitignore-inclusive-or-exclusive\">inclusive or exclusive .gitignore file<\/a>.<\/p>\n\n<p>Whilst it's only adding an if condition based on a value, it adds a separate path in my code and both need to be maintained.<\/p>\n\n<p>I've been thinking of adding <code>just<\/code> again to some projects instead of a <code>run<\/code> file, which would add separate files that need to be maintained and kept up-to-date with each other so both offer the same features.<\/p>\n\n<p>Is this something I want to maintain going forward? Does it add enough value to justify its maintenance?<\/p>\n\n<p>Different to a feature flag, which usually has a known lifespan, this could need be maintained for the whole lifespan of the application.<\/p>\n\n<p>On a client project, this could be having two sets of buttons with rounded and square corners.<\/p>\n\n<p>Do we need both?<\/p>\n\n<p>It could be the positioning of a title in a header. Fewer options mean there is less code to write and maintain.<\/p>\n\n<p>In a Drupal project, each choice could mean adding a different field, taxonomy term, or content or block type to achieve the desired result.<\/p>\n\n<p>The more we can achieve with fewer options means the application will be easier to maintain and work on in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b412bcd2d4532d309472dae5c82e8109",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json b/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json
index 5416ece86..0f3948610 100644
--- a/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json
+++ b/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently had <a href=\"http:\/\/default\/podcast\/27-drupalisms\">my first podcast episode with two guests<\/a>, where I discussed Drupal terminology and Drupalisms with Emma Horrell and Luke McCormick.<\/p>\n\n<p>It was a great episode, but there was something I needed to do before I could release it.<\/p>\n\n<p>Before I could release the episode, I needed to update my website to show both guest names.<\/p>\n\n<p>The other 26 episodes only had a single guest per episode, and my podcast pages were built to only show the first guest name.<\/p>\n\n<p>When building the pages for the <a href=\"http:\/\/default\/podcast\/1-retrofit\">first episode with Matt Glaman<\/a>, I only needed to show a single guest name.<\/p>\n\n<p>There was no need to show multiple guest names until I had an episode with multiple guests.<\/p>\n\n<p>I wrote the simplest code to achieve the requirements I had at the time.<\/p>\n\n<p>If I wrote for two guests but never had an episode with two guests, my website would be bloated and have functionality that wasn't needed or used.<\/p>\n\n<p>Now my requirements have changed.<\/p>\n\n<p>I can have an episode with one or two guests, but not three or more guests.<\/p>\n\n<p>If I have an episode with more than two guests, I'll write that functionality then.<\/p>\n\n<p>But not before.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6d7fff29a7d69d2505863bd126857e30",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json b/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json
index f30d7a3dc..7ec483a51 100644
--- a/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json
+++ b/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, I asked <a href=\"http:\/\/default\/daily\/2024\/05\/15\/should-you-include-issue-ids-in-your-commit-messages\">whether you should include issue IDs in commit messages<\/a>.<\/p>\n\n<p>Another thing I like to reference in a commit message is the commit ID (or SHA) of a related commit.<\/p>\n\n<p>For example, when I run <code>git log<\/code> in my website repository, I see commits like this:<\/p>\n\n<pre><code class=\"plain\">commit 0c91825c16217d0fe7eff4ea100a67550051c4a9\nAuthor: Oliver Davies &lt;oliver@oliverdavies.dev&gt;\nDate:   Sat May 11 15:32:07 2024 +0200\n\n    Create a cached talk counter\n\n    Create a cached version of the talk counter service that returns a\n    cached result of the talk count for that day.\n\n    This uses the Decorator design pattern to decorate the existing\n    `TalkCounter` service and works as they both implement the same\n    `TalkCounterInterface`.\n<\/code><\/pre>\n\n<p>The sha for this commit is <code>0c91825c16217d0fe7eff4ea100a67550051c4a9<\/code>.<\/p>\n\n<p>If I was to make another commit that was related to this one, I can include this commit sha in my new commit message.<\/p>\n\n<p>I also don't need to include the entire thing - only enough for it to be unique (usually five or six characters).<\/p>\n\n<p>Once pushed, the commit IDs should never change, so this will be a permanent reference to the first commit.<\/p>\n\n<p>Helpfully, websites like GitHub, GitLab and Bitbucket will identify it as a commit sha and make it clickable so you can easily navigate to the referenced commit.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0fa771c1556974be2eeabf42a87e75c4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json b/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json
index 62af6d530..5c7ec8807 100644
--- a/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json
+++ b/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I've been following a conversation on Twitter and reading a blog post about Drupal naming and removing the version number from promotional materials.<\/p>\n\n<p>In the post, the author recommends stopping using the version number and \"just say Drupal\" and referring to Drupal 7 and older as \"Legacy Drupal\".<\/p>\n\n<p>Here's a quote from the article that stood out to me:<\/p>\n\n<blockquote>\n  <p>This is no longer true! We have successfully eliminated the need for organizations to leave Drupal because \u201cit\u2019s cheaper to just rebuild it in Wordpress than upgrade from 8 to 9 or from 9 to 10.\u201d We\u2019ve made it easier for our clients to spend less on major upgrades, we should be proud!<\/p>\n<\/blockquote>\n\n<p>Another suggestion was to also use the term \"Modern Drupal\" for anything since Drupal 8.<\/p>\n\n<p>I've been doing this or calling it \"Drupal 8+\" on streams and podcast episodes, but I like this approach and I'm going to standardise on this, help change the perception of Drupal and that large rebuilds are no longer needed to upgrade as they were between the older legacy versions.<\/p>\n\n<p><a href=\"https:\/\/ten7.com\/blog\/post\/just-say-drupal\">Read the article<\/a> for more information about this.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e9efe0920d1be12d60386b0f70dfbd4b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json b/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json
index 39e3d00d9..6f7b62724 100644
--- a/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json
+++ b/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Note: The numbers within this post are taken from my <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">Test-Driven Drupal talk<\/a>, in which I also talk about this.<\/p>\n\n<p>My first commit to the 7.x-1.x branch of the Override Node Options module was in March 2012. According to Drupal.org, the module was used on 9,212 websites then.<\/p>\n\n<p>As well as the 7.x-1.x branch, there's the 8.x-2.x branch which supports Drupal 9 and 10, and previously Drupal 8.<\/p>\n\n<p>The most recent statistics show the module is currently used on 34,981 websites and is consistently around 35,000.<\/p>\n\n<h2 id=\"what-does-that-mean%3F\">What does that mean?<\/h2>\n\n<p>The module is considered feature complete, but I'm not ruling out any new additions.<\/p>\n\n<p>The main thing is ensuring that any changes don't break 35,000 websites!<\/p>\n\n<p>I do this by relying on the module's automated test suite and ensuring that tests are added for any features or bugs and that the tests are passing before any new release.<\/p>\n\n<h2 id=\"this-has-worked-well\">This has worked well<\/h2>\n\n<p>A few years ago, I committed a feature request to both versions. While it didn't include additional tests, I verified the existing functionality worked after resolving a large merge conflict by ensuring the original tests passed.<\/p>\n\n<p>More recently, a colleague and I refactored the module and split each override into its own class, making adding and maintaining overrides easier.<\/p>\n\n<p>Because the tests were still passing, we knew our refactor was successful and not causing regressions.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Having automated tests and ensuring they're always passing has allowed me to add features and refactor code that I wouldn't have done or had the confidence to do otherwise.<\/p>\n\n<p>It's great to have a popular module, but on the other hand, I don't want to break 35,000 websites which makes the tests invaluable.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ae450dbfadd5cdf2b2b209019173a073",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1007a975-f818-4568-8560-9532e96c4577.json b/content/node.1007a975-f818-4568-8560-9532e96c4577.json
index f515375ba..d7fcdcbef 100644
--- a/content/node.1007a975-f818-4568-8560-9532e96c4577.json
+++ b/content/node.1007a975-f818-4568-8560-9532e96c4577.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was recently working with a client and in-house development team who were working in a Git Flow-like way with different branches for each sprint and feature..<\/p>\n\n<p>Each sprint branch has its own environment that can be reviewed and tested.<\/p>\n\n<p>Once the sprint is complete, the sprint branch is merged into the mainline branch.<\/p>\n\n<p>Due to the number of branches and environments, it was hard to tell what was where.<\/p>\n\n<p>If they wanted to test a particular change, it could be in various places depending on which branches had been merged and had been deployed.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>My suggestion was to simplify things by limiting the number of branches and environments.<\/p>\n\n<p>If they used trunk-based development on a single branch, it would be much easier to find a change and less likely for there to be differences or regressions.<\/p>\n\n<p>If they used feature flags, they could control features by toggling them on and off as needed, or enable features for users with a certain role, in a group or a particular email domain.<\/p>\n\n<p>There would also be less overhead and process, allowing the team to focus on delivery and not working which branch their change was on or which environment they need to test.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4c40524b5ba4570cdb941cb4e59e0508",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json b/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json
index ef5851242..6d0d6127c 100644
--- a/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json
+++ b/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><code>just<\/code> compared to <code>make<\/code> is something that was asked during my PHP London talk, and whilst they are similar, <code>just<\/code> has differences for me that explains why I use it:<\/p>\n\n<h2 id=\"tabs-or-spaces\">Tabs or spaces<\/h2>\n\n<p>A Makefile needs to use tabs. Justfiles are more flexible and work with tabs or any number of spaces.<\/p>\n\n<h2 id=\".phony\">.PHONY<\/h2>\n\n<p>With a Makefile, you need to declare some targets as \"phony\". I believe that this is for targets that don't generate artifact files with that name, so as I'm not compiling and building files with <code>make<\/code>, this is redundant and adds visual noise.<\/p>\n\n<h2 id=\"passing-arguments\">Passing arguments<\/h2>\n\n<p>This is how a <code>composer<\/code> target looks like in a Makefile:<\/p>\n\n<pre><code class=\"make\">composer:\n    docker compose exec php composer\n<\/code><\/pre>\n\n<p>With this, I'd expect to be able to pass arguments to it - e.g. <code>make composer info drupal\/core<\/code>.<\/p>\n\n<p>But, instead of seeing the expected output, I get an error: <code>make: *** No rule to make target 'info'. &nbsp;Stop.<\/code>.<\/p>\n\n<p>This is what I'd need to do to pass arguments to the <code>composer<\/code> target:<\/p>\n\n<pre><code class=\"make\">composer:\n    docker compose exec php composer $(COMPOSER_ARGS)\n<\/code><\/pre>\n\n<p>Now I can run <code>make composer COMPOSER_ARGS=\"info drupal\/core\"<\/code> and see what I was expecting but the syntax isn't what I'd want.<\/p>\n\n<p><code>just<\/code>, on the other hand, allows for defining parameters to its recipes:<\/p>\n\n<pre><code class=\"language-yaml\">composer *args:\n&nbsp; docker compose exec php composer \n<\/code><\/pre>\n\n<p>Here, I can create as many named parameters as needed and use them in the recipe with the syntax that I wanted - <code>just composer info drupal\/core<\/code>.<\/p>\n\n<p>I can think of a few others but this is is the main reason why I moved from <code>make<\/code> and later adopted <code>just<\/code>.<\/p>\n\n<p><code>just<\/code>, for me, gives the flexibilty that I need whilst using a simple and familiar syntax but without some of the confusing and complicated behaviours of <code>make<\/code>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0747677b2ea7269056a31e78221a91aa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json b/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json
index 971d5c9ec..c4564983a 100644
--- a/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json
+++ b/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2023\/01\/02\/dont-use-arbitrary-values-in-tailwind-css\">I generally don't use aritrary classes with Tailwind CSS<\/a>.<\/p>\n\n<p>But, they are powerful, and I do use them in some situations.<\/p>\n\n<p>A few months ago, <a href=\"https:\/\/x.com\/opdavies\/status\/1755332703308652730\">I posted a screenshot of a timeline component<\/a> I've built for a client project.<\/p>\n\n<p>Today, I needed to fix an issue with the first and last \"paths\" as they were stretching further than they should.<\/p>\n\n<p>This is the class I added to fix the problem:<\/p>\n\n<blockquote>\n  <p>mr-[calc(50%<em>-_calc(var(--path-width)<\/em>\/_2))]<\/p>\n<\/blockquote>\n\n<p>It adds an arbitrary amount of right margin, which is 50% of the container minus half of the path width, which is the <code>--path-width<\/code> variable.<\/p>\n\n<p>This class uses the <code>calc<\/code> function as well as <code>var<\/code> to determine the correct margin to apply, whilst keeping the code adaptable in case the path width changes.<\/p>\n\n<p>And, as this is a value that's only used in this component, there's no benefit to writing this in a stylesheet - making an arbitrary value was a good option.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bb3e2c953c9fc62ba7bde1aa86085a2d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json b/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json
index aae9e05c1..dece9523f 100644
--- a/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json
+++ b/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently saw a social media website taking over users' handles - renaming them so they can have the original.<\/p>\n\n<p>There were similar issues a few years ago when a website put a paywall in front of articles written by its users.<\/p>\n\n<p>I've written articles and tutorials for companies I've worked at that no longer exist as the companies have been acquired.<\/p>\n\n<p>This is why I like to own and control my content. I still have my versions if a website shuts down or changes its settings.<\/p>\n\n<p>There are a lot of options, including Drupal, that can help with this. It's easy to set up a new website and start publishing your own content.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "674a5bd2088bccaaabc0533c88ba62f8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json b/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json
index 330ecadd5..39c0965b1 100644
--- a/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json
+++ b/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I've said recently when mentoring bootcamp students and working with Junior Developers is that there isn't a perfect solution to each problem, and there are multiple ways to achieve the same result.<\/p>\n\n<p>Similarly, there isn't a perfect tool for every situation.<\/p>\n\n<p>You can use different tools and get the same outcome.<\/p>\n\n<p>In some of my early emails, I talked about <code>run<\/code> files and <code>just<\/code> - two ways to write project-specific commands or aliases that simplify complex commands or group multiple commands together.<\/p>\n\n<p>Both do the same thing, but each have pros and cons.<\/p>\n\n<p><code>run<\/code> files are files written in Bash, which are more verbose but can run anywhere.<\/p>\n\n<p>just is its own program that needs to be installed for it to be available, so Developers will need to have it installed, and it will need to be added to a CI pipeline to be available.<\/p>\n\n<p>I've had CI pipelines fail because they can't download just, and not because of anything in the application code.<\/p>\n\n<p>I like the simplicity of justfiles, though, and that the files are simpler.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>If there isn't a perfect solution, approach, or tool, it comes down to the pros and cons of each. Which option is best for you, your project, or your team?<\/p>\n\n<p>There isn't a \"one size fits all\" solution that works for everyone all the time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3579f9c1128a7333aacc2788d9b130b3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json b/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json
index fa798aa74..4b6d82671 100644
--- a/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json
+++ b/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>On a current project, I've decided to use a component library as the first place to do front-end development.<\/p>\n\n<p>I'm using <a href=\"https:\/\/fractal.build\">Fractal<\/a> as I can use Twig for templates. As Drupal also uses Twig templates, I have more reusabilty between the components in Fractal and Drupal compared to converting them from a different templating language like Handlebars or Nunjucks.<\/p>\n\n<p>Rather than developing directly within the custom Drupal theme, I've been creating new components and pages initially within Fractal.<\/p>\n\n<p>I have been able to create new components quickly and easily with the views uing Twig templates and inject data to it using a context file - a YAML file for each component that contains data that is injected automatically into the view.<\/p>\n\n<p>This meant that I've been able to develop new components from scratch without needing to set up content types or paragraphs within Drupal, validate and confirm my data model, and present the templates to the client for review in Fractal. If a change is needed, it's quick to do.<\/p>\n\n<p>I've also moved my asset generation step into Fractal. No CSS or JavaScript is being compiled within the Drupal theme, it is created within Fractal and copied over with the Twig templates.<\/p>\n\n<p>In most cases, I've been able to copy the Twig templates into Drupal and replace the static context data with dynamic data from Drupal without needing to make any further changes.<\/p>\n\n<p>In a couple of situations, I've needed to change my implementation slightly when moving a template into Drupal, so in this workflow, I've made the changes in Fractal and re-exported them to keep things in sync between the two systems.<\/p>\n\n<p>In situations where there is existing markup and\/or styles from the Drupal side, I've copied those into Fractal so that they match before adding the additional styling and any markup changes.<\/p>\n\n<p>In general, I like the approach as it gives me more flexibility upfront to make changes before needing to configure Drupal. I can see how things could get out of sync between the two systems, but hopefully having the assets compiled in Fractal and needing to copy them into Drupal will keep things synced up.<\/p>\n\n<p>I don't think that I'd use this approach for all projects, but for this one, where I'm working with multiple themes and will need to later add different variants of pages and components, it's worked well so far.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "51b7b1bae4312428d8b9e7a4c5ac11ea",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json b/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json
index 44a3f5887..f9a9108a4 100644
--- a/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json
+++ b/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few years ago, decoupled or headless Drupal - where Drupal is used as an API with a separate front-end - was very popular with some large Drupal agencies and clients using it.<\/p>\n\n<p><a href=\"http:\/\/default\/talks\/decoupling-drupal-vuejs\">I gave a conference talk<\/a> about how to use Drupal as a backend application for a Vue.js frontend.<\/p>\n\n<p>Recently, though, I haven't heard much about it.<\/p>\n\n<p>Some previous advocates have moved back to the more traditional approach.<\/p>\n\n<p>Interestingly, though, I did hear quite a bit about it at DrupalCon and about Drupal and Next.js in particular.<\/p>\n\n<p>I want to try using Drupal with Astro in the future and see what the landscape is like now.<\/p>\n\n<h2 id=\"what-about-you%3F\">What about you?<\/h2>\n\n<p>Do you use Drupal in a decoupled or headless way? If so, what do you use for the frontend?<\/p>\n\n<p>If not, or if you've moved back to a more traditional approach, why?<\/p>\n\n<p>Reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dbf68a40071443f9943fde754f0bddb3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json b/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json
index b9b097f1f..ed8d73437 100644
--- a/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json
+++ b/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The version number of a release is a key indicator of whether it\u2019s compatible with existing code.<\/p>\n\n<p>Semantic versioning is a popular approach used by Drupal core, and many contributed modules, themes and distributions.<\/p>\n\n<p>It uses version numbers like 1.0.0 to show the major, minor and patch versions.<\/p>\n\n<p>If the second or third number changes, e.g. 1.1.0 or 1.0.1, the release contains new backwards-compatible features or fixes, so it\u2019s safe to update.<\/p>\n\n<p>If the first number changes, e.g. 2.0.0, the release is not backwards compatible and contains breaking changes that you\u2019ll need to review and update your code accordingly.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c787c2846b67f55a45525ab52acd36c1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json b/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json
index e4ee68199..c6ef489b9 100644
--- a/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json
+++ b/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the most recent episode of the Beyond Blocks podcast, I spoke with J\u00fcrgen Haas about Drupal's ECA module.<\/p>\n\n<p>ECA stands for Events, Conditions and Actions and is a module I was aware of, but haven't used before - so I was great to learn more about it.<\/p>\n\n<p>I also got to meet J\u00fcrgen at DrupalCon in Barcelona, as well as several other podcast guests, which was fantastic.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/23-jurgen-haas-eca\">Listen to the episode now<\/a>.<\/p>\n\n<p>If you'd like to be a guest on the podcast or want to suggest a topic, reply and let me know!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cf37bf626cc98ddb264219b228efc723",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json b/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json
index 5cdfef152..bd066ba9f 100644
--- a/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json
+++ b/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the main concerns for Developers evaluating or starting with a utility-first approach to styling is maintainability due to the number and duplication of classes.<\/p>\n\n<p>For example, with this component, as I duplicate it to add more links, I also duplicate the classes applied to the link - making it harder to maintain:<\/p>\n\n<pre><code class=\"html\">&lt;li&gt;\n  &lt;a class=\"block py-2 border-b-2 border-transparent hover:text-blue-500 hover:border-blue-500 focus:bg-yellow-400 focus:border-current focus:outline-none\" href=\"#0\"&gt;About&lt;\/a&gt;\n&lt;\/li&gt;\n<\/code><\/pre>\n\n<p>There are some solutions to this, which you can also see in an example Astro project at https:\/\/github.com\/opdavies\/reducing-utility-class-duplication.<\/p>\n\n<h2 id=\"extracting-a-variable-of-class-names\">Extracting a variable of class names<\/h2>\n\n<p>The simplest way to remove the duplication is to create a variable that holds the class names which can be reused. For example, Astro allows variables to be created within the frontmatter section and used within the template. Creating variables can be done in other templating engines too.<\/p>\n\n<pre><code class=\"astro\">---\nconst linkClasses =    \"py-2 block border-b-2 border-transparent hover:border-blue-500 hover:text-blue-500 focus:outline-none focus:bg-yellow-400 focus:border-current\";\n---\n\n&lt;li&gt;&lt;a class={linkClasses} href=\"#0\"&gt;About&lt;\/a&gt;&lt;\/li&gt;\n&lt;li&gt;&lt;a class={linkClasses} href=\"#0\"&gt;Talks&lt;\/a&gt;&lt;\/li&gt;\n&lt;li&gt;&lt;a class={linkClasses} href=\"#0\"&gt;Blog&lt;\/a&gt;&lt;\/li&gt;\n<\/code><\/pre>\n\n<h2 id=\"extracting-css-components\">Extracting CSS components<\/h2>\n\n<p>Instead of extracting a variable, you could also extract a CSS component. With Tailwind, the <code>@apply<\/code> directive within a stylesheet will create a reusable CSS component:<\/p>\n\n<pre><code class=\"astro\">&lt;Layout&gt;\n  &lt;ul\n    class=\"flex flex-col gap-4 justify-center sm:flex-row sm:flex-wrap sm:gap-6\"\n  &gt;\n    &lt;li&gt;&lt;a class=\"link\" href=\"#0\"&gt;About&lt;\/a&gt;&lt;\/li&gt;\n    &lt;li&gt;&lt;a class=\"link\" href=\"#0\"&gt;Blog&lt;\/a&gt;&lt;\/li&gt;\n    &lt;li&gt;&lt;a class=\"link\" href=\"#0\"&gt;Talks&lt;\/a&gt;&lt;\/li&gt;\n  &lt;\/ul&gt;\n&lt;\/Layout&gt;\n\n&lt;style&gt;\n  .link {\n    @apply py-2 block border-b-2 border-transparent hover:border-blue-500 hover:text-blue-500 focus:outline-none focus:bg-yellow-400 focus:border-current;\n  }\n&lt;\/style&gt;\n<\/code><\/pre>\n\n<p>The <code>link<\/code> class can be added to any link items, and whilst the approach works, I prefer to use template-based solutions and keep the classes within the HTML markup.<\/p>\n\n<h2 id=\"loops-and-maps\">Loops and maps<\/h2>\n\n<p>Templating engines will have a way to loop over a list of items. This can be used to remove the duplication and only have a single list of classes whilst keeping the benefits of keeping them in the HTML code.<\/p>\n\n<p>For example, in Astro:<\/p>\n\n<pre><code class=\"astro\">---\nconst links = [\n    { name: \"About\" },\n    { name: \"Blog\" },\n    { name: \"Talks\" },\n    { name: \"Daily list\" },\n    { name: \"Search\" },\n];\n---\n\n{links.map(link =&gt; (\n  &lt;li&gt;\n    &lt;a class=\"block py-2 border-b-2 border-transparent hover:text-blue-500 hover:border-blue-500 focus:bg-yellow-400 focus:border-current focus:outline-none\" href=\"#0\"&gt;\n      {link.name}\n    &lt;\/a&gt;\n  &lt;\/li&gt;\n))}\n<\/code><\/pre>\n\n<h2 id=\"extracting-html-components\">Extracting HTML components<\/h2>\n\n<p>Finally, if the component needs to be reused, it can be extracted into its own file and re-imported where needed.<\/p>\n\n<p>This is the extracted component:<\/p>\n\n<pre><code class=\"astro\">---\nconst { name } = Astro.props;\n---\n\n&lt;a class=\"block py-2 border-b-2 border-transparent hover:text-blue-500 hover:border-blue-500 focus:bg-yellow-400 focus:border-current focus:outline-none\" href=\"#0\"&gt;\n  {name}\n&lt;\/a&gt;\n<\/code><\/pre>\n\n<p>And the original file:<\/p>\n\n<pre><code class=\"astro\">---\nimport Layout from \"~\/layouts\/Layout.astro\";\nimport Link from \"~\/components\/Link.astro\";\n---\n\n&lt;Layout&gt;\n  &lt;ul class=\"flex flex-col gap-4 justify-center sm:flex-row sm:flex-wrap sm:gap-6\"&gt;\n    &lt;li&gt;&lt;Link name=\"About\" \/&gt;&lt;\/li&gt;\n    &lt;li&gt;&lt;Link name=\"Blog\" \/&gt;&lt;\/li&gt;\n    &lt;li&gt;&lt;Link name=\"Talks\" \/&gt;&lt;\/li&gt;\n    &lt;li&gt;&lt;Link name=\"Daily list\" \/&gt;&lt;\/li&gt;\n    &lt;li&gt;&lt;Link name=\"Search\" \/&gt;&lt;\/li&gt;\n  &lt;\/ul&gt;\n&lt;\/Layout&gt;\n<\/code><\/pre>\n\n<p>This can now be used anywhere within this project and could be combined with the loop approach, passing the appropriate value to the <code>name<\/code> prop.<\/p>\n\n<h2 id=\"summary\">Summary<\/h2>\n\n<p>All of these approaches remove duplication, either using features provided by Tailwind CSS or a templating engine, to make the code more maintainable.<\/p>\n\n<p>I've shown <a href=\"https:\/\/astro.build\">Astro<\/a> in these examples but the same can be done with PHP, Twig, Blade, Vue, React, etc.<\/p>\n\n<p>The examples are public on GitHub at https:\/\/github.com\/opdavies\/reducing-utility-class-duplication\/tree\/main\/src\/pages.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "41ef4a1e143c80e2836519ef5da477d0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json b/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json
index c816b286d..443437eaa 100644
--- a/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json
+++ b/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I wanted to make a breaking change to my <a href=\"http:\/\/default\/daily\/2023\/03\/04\/why-i-built-a-tool-to-generate-configuration-files\">build-configs project<\/a> - changing the default database credentials that are used by Docker Compose.<\/p>\n\n<p>As I have several projects based on generated files by the tool, changing the values could cause issues in those projects in the future and this is something that I wanted to avoid.<\/p>\n\n<h2 id=\"what-did-i-do%3F\">What did I do?<\/h2>\n\n<p>To avoid this issue and needing to update all of my projects at once, I added a feature flag to the <code>build.yaml<\/code> file so I can opt-in to this feature on a per-project basis.<\/p>\n\n<p>If a project, like my <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\">Drupal<\/a> and <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal-localgov\">LocalGov Drupal<\/a> Docker examples, are opted in, its files will get the new credentials. If not, it will continue to use the original ones.<\/p>\n\n<p><a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\/commit\/3f496168d5c32f9706970519023b431ee02c4b19\">In this commit<\/a>, you'll see where I enabled the feature flag and committed the resulting change.<\/p>\n\n<h2 id=\"what-does-this-achieve%3F\">What does this achieve?<\/h2>\n\n<p>I can continue to work on existing projects without them breaking, and migrate projects one at a time by using the feature flag instead of needing to do them all once.<\/p>\n\n<p>Once all active projects have been migrated or completed, the feature flag can be removed and I can refactor and simplify the code - removing the feature flag and the legacy values.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "12cfe483b3ce1a78d111407418450b62",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json b/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json
index d4571aa94..a12134fb0 100644
--- a/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json
+++ b/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When creating a custom module, where do you put your business logic?<\/p>\n\n<p>You want to keep classes like Controllers and Commands simple and move any reusable logic into separate files.<\/p>\n\n<p>Usually, this means 'Service' classes, but another approach I like is to use 'Action' classes.<\/p>\n\n<h2 id=\"what-is-an-action-class%3F\">What is an Action class?<\/h2>\n\n<p>An Action is a PHP class representing a single action that must be performed.<\/p>\n\n<p>It usually contains a single method with a descriptive name summarising the task, such as <code>GetAccessToken<\/code>.<\/p>\n\n<p>This differs from a generic service like <code>ApiService<\/code> with multiple methods like <code>getAccessToken()<\/code>.<\/p>\n\n<h2 id=\"using-action-classes\">Using Action classes<\/h2>\n\n<p>I'll register Action classes in the service container to use dependency injection and autowiring and easily inject the Action into other classes that need it, like Controllers and Commands.<\/p>\n\n<p>If you need multiple implementations, multiple actions can implement the same Interface and make them swappable, such as having <code>GetAccessToken<\/code> and <code>GetAndCacheAccessToken<\/code> implement the same <code>GetsAccessToken<\/code> interface.<\/p>\n\n<p>That also enables using design patterns like Decorators with Actions.<\/p>\n\n<h2 id=\"why-i-like-actions\">Why I like Actions<\/h2>\n\n<p>I like more readable and meaningful class names and prefer working with multiple simpler classes than those with fewer complex ones.<\/p>\n\n<p>I like leveraging design patterns I'm used to, such as the Decorator pattern, by having common interfaces and contracts.<\/p>\n\n<p>I like that if I need to add another implementation, I can add it without changing the existing code, so it follows the SOLID principles.<\/p>\n\n<h2 id=\"what-about-you%3F\">What about you?<\/h2>\n\n<p>Do you use Action classes in your code, or do you use Services or something else?<\/p>\n\n<p>Reply to this email and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f43fe44d7a6115a84e3ad56bda9fb804",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json b/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json
index 71561018e..ee2bcddff 100644
--- a/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json
+++ b/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After my Beyond Blocks episode with Mark Conroy, I've spent some time this week experimenting with web components.<\/p>\n\n<p>The team and I are building a new design system in Fractal and, as Drupal is our main application, we're using Twig as our templating language within Fractal so the changes are easier to port between systems.<\/p>\n\n<p>Web components are agnostic, so they work within different languages and frameworks.<\/p>\n\n<p>We also use other technologies, such as Vue.js, and third-party suppliers, so having an agnostic web component would reduce the time and effort needed to implement the design system across different technologies and applications.<\/p>\n\n<p>If we can make self-contained web components that include their own styling and behaviour, that also improves re-usability and reduces the maintenance overhead as there would be one canonical version for everyone to use - not just a reference implementation everyone would need to recreate.<\/p>\n\n<p>After this spike, I'm intrigued to see how we could use web components and what potential issues we can solve with them whilst reducing our implementation and maintenance efforts.<\/p>\n\n<p>Are you interested in web components, too? <a href=\"http:\/\/default\/podcast\/11-mark-conroy\">Listen to the podcast episode with Mark Conroy<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "00668a369ffa2c0cb637d1b9d53bbfb4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json b/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json
index 30f01ba24..0c8b83e49 100644
--- a/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json
+++ b/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This is a question that I always ask before starting any development task, and I was very happy to see a slide in one of the keynote sessions at nor(DEV):con asking this question.<\/p>\n\n<p>I'd much rather have a collegue or client come to me with a problem that needs solving rather than a self-diagnosis and a decided solution.<\/p>\n\n<p>Depending what on the problem is, and other factors like timescales, I may suggest a different solution or approach. This happened recently when I suggested a different approach using Drupal's built-in maintenance mode feature.<\/p>\n\n<p>If there's no problem to solve, what's the reason for doing the work?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "35beb2b86a757c4691d2b49f4d652b0c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json b/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json
index 5fe678591..7693ad61f 100644
--- a/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json
+++ b/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Two of the main things I like about Drupal are its flexibility and scalability.<\/p>\n\n<p>It works well for basic applications, such as personal websites and blogs (like mine) and for large, complex applications such as Drupal.org itself and many others.<\/p>\n\n<p>I don't need to learn one tool for small or simple projects and another for large or complex projects.<\/p>\n\n<p>Drupal is one size fits all.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7fae72b5dced45dcf868b050b1fa5bc8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.13e1b1ea-a0df-43b2-8f1b-e8340bb62df8.json b/content/node.13e1b1ea-a0df-43b2-8f1b-e8340bb62df8.json
index bba85c00f..a5ffff851 100644
--- a/content/node.13e1b1ea-a0df-43b2-8f1b-e8340bb62df8.json
+++ b/content/node.13e1b1ea-a0df-43b2-8f1b-e8340bb62df8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, in the repository of an open-source project, I saw an issue comment saying, \"This is a minor breaking change.\".<\/p>\n\n<p>It detailed what was removed and suggested an alternative.<\/p>\n\n<p>I don't know how you define a \"minor\" breaking change.<\/p>\n\n<p>Is it because it's a single line and easy to replace, or is it part of the code that is rarely used by consumers and less likely to cause an issue?<\/p>\n\n<p>Regardless, if it's a breaking change, anyone using that project will need to update their code if they use something that was removed, whether it's minor or not.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fec65b7e84bf75434bce2cbc5521ace3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json b/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json
index 3687a575a..454105815 100644
--- a/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json
+++ b/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>With automated testing and test-driven development, it's important to see a test fail.\nIf a test passes straight away, how do you know that you're testing the right thing? You could be accidentally testing a different piece of functionality, or it could be a false positive.<\/p>\n\n<p>If the functionality already exists, do you need another test for it?<\/p>\n\n<p>When you see a test fail, you know that the functionality hasn't been implemented, that you're testing the correct thing, and you have a clear goal to work towards.<\/p>\n\n<p>If you're fixing a bug, writing a test and seeing it fail verifies the bug exists and that, once the bug is fixed, the test will pass.<\/p>\n\n<p>Usually, you can anticipate why a test will fail as it evolves and know when it will pass. If a test passes before I expect, I'm immediately sceptical and will look into why rather than assuming it passed for the right reasons.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dea295dc493bba491afadc1db32d16fe",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json b/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json
index ee80fa96f..bd91312c3 100644
--- a/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json
+++ b/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>During a recent coding dojo session, we spoke about YAGNI - i.e. \"You aren't going to need it\".<\/p>\n\n<p>In this situation, we discussed how many numbers we should support passing to a method in a calculator application.<\/p>\n\n<p>There's no technical limit to how many numbers we can pass, but there may be a requirement where we only need to add or subtract two numbers. In that case, we don't need to calculate three or more numbers, so there's no benefit or value to writing that code.<\/p>\n\n<p>If we follow YAGNI, we only write the code we need now. If the requirement changes in the future, we revisit the code and change it as required.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a09433a4fbfd96fc58654fe54aeeb036",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json b/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json
index 51f96f405..6f1da6949 100644
--- a/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json
+++ b/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whether it's PHP or JavaScript\/TypeScript, I prefer type declarations in my code.<\/p>\n\n<p>As well as benefits like auto-completion in your IDE or text editor and being able to more effectively statically analyse the code, to me, the code is more readable and easier to understand with the types included.<\/p>\n\n<p>It's more to read, but I can do so easily and immediately know what a function expects as function arguments and what it will return.<\/p>\n\n<p>Here's the code from my previous email on types from a few days ago, with and without the types declared:<\/p>\n\n<pre><code class=\"js\">add(...numbers) {\n  \/\/ ...\n}\n\nsubtract(...numbers) {\n  \/\/ ...\n}\n\nadd(...numbers: number[]): number {\n  \/\/ ...\n}\n\nsubtract(...numbers: number[]): number {\n  \/\/ ...\n}\n<\/code><\/pre>\n\n<p>Without types, I can infer what the function accepts and returns, but that's based on my assumption, which could be incorrect.<\/p>\n\n<p>What if <code>numbers<\/code> was an array of strings of numbers - e.g. <code>['one', 'two', 'three']<\/code> - and what if instead of returning the result, it stored it in state to return from a different method like <code>equals()<\/code> or <code>calculate()<\/code>?<\/p>\n\n<p>With the type declarations included, I don't need to presume, infer or make best guesses.<\/p>\n\n<p>It's clear from just reading the code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "506ce77f679ad7914294ef3ac3d0201c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json b/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json
index 4123a9171..a9972a717 100644
--- a/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json
+++ b/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After my talk at DrupalCon, I was asked when you should run your tests.<\/p>\n\n<p>Of course, if you're doing test-driven development, you have to run the tests as you work on them and have the red, green, refactor cycle as you work on the feature or bug fix.<\/p>\n\n<p>If you're not doing TDD, I'd recommend running the whole test suite before you push your code to know it works before a peer review or to an environment for quality assurance or user-acceptance testing.<\/p>\n\n<h2 id=\"what-about-ci-pipelines%3F\">What about CI pipelines?<\/h2>\n\n<p>As well as running tests manually, I'd add them to a CI pipeline, such as GitHub Actions, GitLab CI or Bitbucket Pipelines.<\/p>\n\n<p>There, tasks can be run automatically each time a commit is pushed, so you don't need to rely on them being run manually.<\/p>\n\n<p>If you're doing trunk-based development, you want the CI pipeline to run on every push to prevent regressions and ensure the tests continue to pass.<\/p>\n\n<p>If you're working with feature branches and doing code review, run the tests as part of the merge or pull request so you know everything works as expected before the code is reviewed.<\/p>\n\n<p>This answers the main \"Does it work?\" question, and allows the reviewer to focus on reviewing the code and suggesting improvements.<\/p>\n\n<p>If the CI pipeline in the merge or pull request fails, it needs to be fixed before submitting it for review as there's no need to review the code before it changes to fix the pipeline.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1f2cab06d1412951184ea5c3b5d74edb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json b/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json
index f74692a23..db37c6225 100644
--- a/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json
+++ b/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as assertions within tests, you can also check within implementation code that things are in an expected state or contain a certain value.<\/p>\n\n<p>In PHP, this is done by throwing an Exception if a condition is met.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"language-php\">if (!is_array(false)) {\n  throw new \\Exception('Not an array');\n}\n<\/code><\/pre>\n\n<p>There's also the <code>assert<\/code> construct which, since PHP 8.0, throws an Exception by default:<\/p>\n\n<pre><code class=\"language-php\">assert(is_array(false));\n<\/code><\/pre>\n\n<p>You can also use an assertion library, such as <code>webmozart\/assert<\/code> or <code>beberlei\/assert<\/code> which provide assertions and guard methods:<\/p>\n\n<pre><code class=\"language-php\">use Webmozart\\Assert\\Assert;\n\nAssert::isArray(false);\n<\/code><\/pre>\n\n<p>Similarly, if the condition fails, it throws an Exception that can be caught elsewhere.<\/p>\n\n<p>As well as basic assertions such as the item is the expected type or don't match the condition, there are more complex assertions, such as all items within an array are a certain type or that an integer is positive.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I use guard conditions a lot within my code. If something is not as I'd expect, I like for an error to be thrown. This makes is easy to test and to debug any failures compared to failing silently.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fff5236abf836cd7767bdeeb7e9ba028",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json b/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json
index 1762feb23..517663046 100644
--- a/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json
+++ b/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2025\/04\/05\/strategies\">working with different versions of an API<\/a>, I was able to use the same technique I wrote about yesterday to easily add a cacheable version of the API client.<\/p>\n\n<p>As they all implement the same <code>ApiClientInterface<\/code>, I can inject and decorate a client with another client, making one solely responsible for caching the result from the API whilst keeping the API interaction logic separate (aka <a href=\"http:\/\/default\/daily\/2022\/12\/08\/the-decorator-design-pattern\">the Decorator design pattern<\/a>).<\/p>\n\n<p>Here's an example based on the code I wrote:<\/p>\n\n<pre><code class=\"php\">final class CacheableApiClient implements ApiClientInterface {\n\n  \/**\n   * The cache duration in seconds.\n   *\/\n  private const CACHE_DURATION = 3600;\n\n  public function __construct(\n    private readonly ApiClientInterface $client,\n    private readonly TimeInterface $time,\n    private readonly CacheBackendInterface $cache,\n  ) {\n  }\n\n  public function getResults(): Collection {\n    $key = $this-&gt;getCacheKey();\n\n    $cache = $this-&gt;cache-&gt;get($key);\n\n    if ($cache !== FALSE) {\n      return $cache-&gt;data;\n    }\n\n    $result = $this-&gt;client-&gt;getResults();\n\n    $this-&gt;cache-&gt;set(\n      cid: $key,\n      data: $result,\n      expire: $this-&gt;time-&gt;getRequestTime() + self::CACHE_DURATION,\n    );\n\n    return $result;\n  }\n\n}\n<\/code><\/pre>\n\n<p>Nothing in this instance is specific to either version of the API.<\/p>\n\n<p>This client is only concerned with retrieving and saving cache data, and delegating any other logic to the original version.<\/p>\n\n<p>With this approach, I can switch between <code>V1ApiClient<\/code>, <code>V2ApiClient<\/code> or any other version with the same methods without having to reimplement caching as that's handled within the <code>CacheableApiClient<\/code>.<\/p>\n\n<p>But what if I don't want to interact with the API at all?<\/p>\n\n<p>For local development, I have a <code>FakeApiClient<\/code> that returns a static response that I can work with.<\/p>\n\n<p>The possibilities are endless.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dd52b641b6c5a3e8eb19c47343f766c3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json b/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json
index 181099f4f..0f64435c2 100644
--- a/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json
+++ b/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json
@@ -87,6 +87,5 @@
             "processed": "<p>I have recently <a href=\"http:\/\/default\/daily\/2025\/05\/11\/email-archive-tome\">migrated my daily email archive<\/a> to Drupal and Tome.<\/p><p>The result is the same - a static website that I can upload onto my server, but it's created with Drupal 11 locally and exported to a static website.<\/p><p>Similar to being able to <a href=\"http:\/\/default\/daily\/2025\/05\/02\/extend\">extend Sculpin with PHP<\/a>, I get the same benefit with Tome.<\/p><p>I can write the same PHP code and custom Drupal modules as I would with a non-Tome Drupal website.<\/p><p>To count the number of sent daily emails, I created a <code>opd_daily_emails<\/code> module with a token that generates the number of emails, and displays it on the page.<\/p><p>I can also write the same automated tests.<\/p><p>I have a functional test that confirms the token result is generated and rendered correctly using <code>TokenTestTrait<\/code> - supported by some kernel tests and a custom <code>DailyEmailTestTrait<\/code> that makes it easier to create daily email nodes within the tests.<\/p><p>I have all the power and flexibility of Drupal locally and the benefits of a static site when it's deployed.<\/p><p>P.S. If you want to learn how to write automated tests in Drupal, subscribe to <a href=\"http:\/\/default\/atdc\">my free 10-day email course<\/a>.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json b/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json
index e83f8130d..2808c2f0c 100644
--- a/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json
+++ b/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Having a passing test suite or CI pipeline doesn't tell you if your appliction works.<\/p>\n\n<p>There could be scenarios or edge-cases that aren't covered within the test suite and contain bugs, but aren't covered by the test suite.<\/p>\n\n<p>There could be untested code that isn't covered at all.<\/p>\n\n<p>A passing test suite proves that the tests that have been written so far pass and that there are no regressions introduced by the latest change.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Instead of telling you that your application works by passing, the test suite tells you something is broken when it fails.<\/p>\n\n<p>If a previously-passing test is failing, the application is broken and should not be deployed - not that the application is working if the tests don't fail.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "84286e59b43f96ea62a57ef17279149e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json b/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json
index 00618d415..008c7f54a 100644
--- a/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json
+++ b/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common issue I see for people introducing automated testing is estimating the testing and implementation of a task separately.<\/p>\n\n<p>Something like, \"It'll take x to do the work and x to write the tests for it\".<\/p>\n\n<p>As well as implying you'd write all the code and then all the tests or vice versa, if you provide separate estimates, it's easy for someone to think the tests are optional and can be removed.<\/p>\n\n<p>If you provide one estimate for both, this can't happen.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b2a503f52e0d13b65158e0770ce490d5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json b/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json
index c31ac1cdc..3b2e92eec 100644
--- a/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json
+++ b/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Decorator is a structural design pattern that allows you to add extra functionality, such as if you want to add caching or logging to a service, without changing the original class.<\/p>\n\n<p>As long as a class implements an Interface, it can be decorated.<\/p>\n\n<p>For example, if I have this PHP interface:<\/p>\n\n<pre><code class=\"language-php\">interface DoesSomething\n{\n    public function doSomething(): void;\n}\n<\/code><\/pre>\n\n<p>I could have this class that does something:<\/p>\n\n<pre><code class=\"language-php\">final class FirstClass implements DoesSomething\n{\n    public function doSomething(): void\n    {\n        \/\/ Does something.\n    }\n}\n<\/code><\/pre>\n\n<p>If I need to do something else, like caching or logging the result, I can decorate it.<\/p>\n\n<p>To do this, I need another class that implements the same interface and inject the original version.<\/p>\n\n<pre><code class=\"language-php\">final class SecondClass implements DoesSomething\n{\n    public function __constuct(\n        private DoesSomething $originalClass\n   ) {}\n\n    public function doSomething()\n    {\n        \/\/ Do something else before.\n\n        $this-&gt;originalClass-&gt;doSomething();\n\n        \/\/ Do something else afterwards.\n    }\n}\n<\/code><\/pre>\n\n<p>Within the new class, the methods can be overridden, extra functionality can be added, and the original method can be run to execute the original functionality.<\/p>\n\n<p>As the two classes implement the same interface, I can swap between different versions and decorate multiple times if needed.<\/p>\n\n<p>This a pattern that I used recently to extend a service that retrieved some data from an API and saved it to a file, to change some arguments and do more work with it.<\/p>\n\n<p>The original class was unchanged, the new class was minimal and easy to understand as it only had a single responsibility, and if I needed to switch back to the original version, I could easily do that.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "02610d24642398171de58810a96abcd6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.168c59ab-cadd-4dfc-8c72-de82d6578885.json b/content/node.168c59ab-cadd-4dfc-8c72-de82d6578885.json
index a04f993d4..ebe41f1ff 100644
--- a/content/node.168c59ab-cadd-4dfc-8c72-de82d6578885.json
+++ b/content/node.168c59ab-cadd-4dfc-8c72-de82d6578885.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Technical debt is an overused term with people often referring to any legacy code, outdated dependencies or bugs as technical debt.<\/p>\n\n<p>Technical debt specifically refers to the future cost when a short-term solution is selected over a more flexible or efficient one.<\/p>\n\n<p>For example, hard-coding something for now and making it dynamic later.<\/p>\n\n<p>It's not any code the current Developers didn't write or no longer want to support.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "238cdb2a724852497414bcfd508b5a90",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json b/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json
index a7bcac25d..152420786 100644
--- a/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json
+++ b/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As I've added software to my NixOS homelab server, I've found some things that aren't yet available in the nixpkgs repository.<\/p>\n\n<p>A common approach seems to be to use Docker and Docker Compose to run things in containers, especially ones that need multiple services like a web server, a database and a cache or proxy.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/12\/09\/drupal-devenv\">I've moved my development projects from Docker to devenv<\/a>, but I still have Docker installed and available.<\/p>\n\n<p>I knew it was easy to create a container image from a Nix-based setup, but the opposite is also true.<\/p>\n\n<p>It's very easy to run containers within NixOS.<\/p>\n\n<p>For example, here's <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/blob\/8cdc6a511dab5a31b1bc0a90bcdcf361043498e7\/nix\/modules\/nixos\/features\/homelab\/tubearchivist-container.nix\">how I've configured Tube Archivist<\/a>.<\/p>\n\n<p>This was created using a tool called <code>compose2nix<\/code>, but I've seen simpler examples for other services.<\/p>\n\n<p>This made it easy to take a Docker Compose file and convert it to a Docker or Podman container.<\/p>\n\n<p>My preference is to use NixOS services if they exist, but it's great to be able to do this as an alternative when needed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c46666fe3bbd6c27133967d0e0f292cb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json b/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json
index d3ca5a1de..b673303fc 100644
--- a/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json
+++ b/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When I speak to people about automated testing or hear others speak about it, it's often confused with unit testing.<\/p>\n\n<p>Drupal and many other projects use PHPUnit. Its website describes PHPUnit as \"a programmer-oriented testing framework for PHP\", whereas Wikipedia explicitly says \"PHPUnit is a unit testing framework\".<\/p>\n\n<p>But automated testing includes much more.<\/p>\n\n<h2 id=\"other-types-of-tests\">Other types of tests<\/h2>\n\n<p>In Drupal, whilst there are unit tests, PHPUnit also does feature (aka functional or browser) testing, where it can make an HTTP request to an endpoint and perform assertions on the response's status code and the returned text. This is great for checking if a page exists at a certain path, whether the correct users can access it and whether it contains the expected text. This isn't something that can be done with a unit test.<\/p>\n\n<p>There are also integration (aka kernel) tests which don't access the browser but have access to Drupal's service container to interact with its services and can save and retrieve values from the database. Again, this isn't available in a unit test which relies heavily on mocking.<\/p>\n\n<h2 id=\"what-else-is-there%3F\">What else is there?<\/h2>\n\n<p>In Drupal, I've also used Behat - a behaviour-driven development testing framework that allows writing tests in a plain English syntax called Gherkin instead of PHP.<\/p>\n\n<p>Pest PHP has an architecture plugin.<\/p>\n\n<p>There are dedicated front-end testing frameworks like Cypress for UI testing.<\/p>\n\n<p>Other quality tools like static analysis can also be considered testing tools.<\/p>\n\n<h2 id=\"want-to-learn-more%3F\">Want to learn more?<\/h2>\n\n<p>If you want to learn more about automated testing in Drupal, <a href=\"http:\/\/default\/talks\/tdd-test-driven-drupal\">I have a talk about that<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f7cd5903bb37498e5fec20b1ac28f287",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json b/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json
index 350233c1b..518903c8d 100644
--- a/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json
+++ b/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week I attended another of Simon Vrachliotis' Pro Tailwind workshops.<\/p>\n\n<p>The workshop again was great, teaching us about multi-style Tailwind components, such as a button that has props for variants like size, shape and impact, and how to create them in a flexible and maintainable way as well as making use of Headless UI.<\/p>\n\n<p>For this workshop though, the examples and challenges used a tool that I wasn't familiar with - the Astro web framework.<\/p>\n\n<p>I've seen a lot of blog posts and streams mentioning it but I hadn't tried it out for myself until the workshop.<\/p>\n\n<p>What I find interesting is that it comes with a number of available integrations - from Tailwind CSS, to Vue, React, and Alpine.js, and you can use the all within the same project, or even on the same page. Installing an integration is as simple as <code>yarn astro add tailwindcss<\/code>.<\/p>\n\n<p>The templates feel familiar and make use of front matter within Astro components, and regular YAML front matter works within Markdown files - which are supported out of the box.<\/p>\n\n<p>I've been thinking of redoing my personal website and evaluating options, but I think that Astro might be a new one to add to the list.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "896df6011c053cbdee1b18906879608e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json b/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json
index 16fbb6fb3..bc9d4e5f9 100644
--- a/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json
+++ b/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I've started to add snapshot tests to the <a href=\"https:\/\/www.oliverdavies.dev\/build-configs\">Build Configs project<\/a>.<\/p>\n\n<p>I had unit tests for the DTO validation to ensure the configuration was correct, but the main thing I wanted to test was I could run it for a given configuration file and get the expected files and contents to be generated.<\/p>\n\n<p>With snapshot tests, I generate the files for each configuration and compare them to a set that I know to be correct.<\/p>\n\n<p>If the files match, the tests pass, but, if they don't - such as a bug in the code, the tests will fail.<\/p>\n\n<p>This is the level that I want to be testing this project and that provides the most value.<\/p>\n\n<p>If a snapshot test fails, I can try to replicate the underlying issue in a unit test whilst also fixing the snapshot test.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f438aefd37b258b1946af9f1abcf9bed",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json b/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json
index 4094c88a0..e5d5330e9 100644
--- a/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json
+++ b/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Do you know every software package installed on your computer?<\/p>\n\n<p>Do you know every configuration file you've added or edited?<\/p>\n\n<p>If you needed to create a new computer or server that matches your current configuration, how long would that take you?<\/p>\n\n<p>This is why I started automating my system and having tools like Ansible install and configure software instead of me doing it manually.<\/p>\n\n<p>But, that doesn't prevent anyone from adding more things or changing files on the fly.<\/p>\n\n<p>Nix and NixOS have a read-only store of packages and configuration files, and I can <a href=\"https:\/\/github.com\/opdavies\/dotfiles\">read my dotfiles repository<\/a> and see exactly what's installed and how it's configured.<\/p>\n\n<p>If I want to add or remove a package or change some configuration, I update a Nix file and rebuild my system.<\/p>\n\n<p>There are no more random, rogue or leftover packages.<\/p>\n\n<p>If I get a new computer or create a new server, I add it to my dotfiles repository and apply the configuration and I'm up and running in no time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5f836cbcedf162cecbf20a6f752387dd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json b/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json
index fdd292906..f3268fc19 100644
--- a/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json
+++ b/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you do code reviews, they should be about reviewing the code and not about the style of the code.<\/p>\n\n<p>There shouldn't be comments about whether tabs or spaces are used, how many spaces are on each line, where the braces are, or whether there should be semicolons.<\/p>\n\n<p>A code style should be defined upfront and checking code against it can be done automatically with tools such as phpcs or Prettier.<\/p>\n\n<p>You don't need to wait for a human to review the code style - automated tools can be run locally or in a CI pipeline and provide feedback much faster.<\/p>\n\n<p>And if people aren't reviewing the code style, they can focus on reviewing the code itself.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9fe14e0414ae452819b91e9a2abc8403",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.18cac962-eefd-4506-8efd-cd584f027369.json b/content/node.18cac962-eefd-4506-8efd-cd584f027369.json
index 2cbd552bb..b12a10a35 100644
--- a/content/node.18cac962-eefd-4506-8efd-cd584f027369.json
+++ b/content/node.18cac962-eefd-4506-8efd-cd584f027369.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was also asked at DrupalCon how you write tests for code you didn't write and how you cover all of the use cases and scenarios.<\/p>\n\n<p>This is tricky. If you didn't write the code, how can you know all the scenarios you need to test?<\/p>\n\n<p>Presumably, there is some documentation, Jira tickets, user stories or acceptance criteria from when the code was written that will help you with this.<\/p>\n\n<p>Decide the most critical functionality to be tested and focus on that, as that will provide the most value.<\/p>\n\n<p>I'd start with functional tests and test for high-level outcomes, such as whether a page loads, returns the correct status code, and contains the expected text.<\/p>\n\n<p>Then, iteratively add more tests for other scenarios. Once you have the first one written, this should be easier as you already have the setup steps, such as which modules must be enabled and what configuration needs to be installed.<\/p>\n\n<p><strong>One test is better than none.<\/strong><\/p>\n\n<p>If you need to add any new features or fixes, ensure they have their own tests to keep a consistent level of coverage.<\/p>\n\n<p>Even with a simple module, you're unlikely to be able to identify all of the scenarios, write all the tests in one go, and have everything covered.<\/p>\n\n<p>Start with the most important test first and continue to add more iteratively.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "221517dc07bba403f3df3cb3e605aab2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json b/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json
index 2b7283963..a9783a921 100644
--- a/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json
+++ b/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently reviewed a client's Drupal 9 website to gather information about upgrading it to Drupal 10.<\/p>\n\n<p>The site has a number of custom modules. They all require changes to make them Drupal 10-compatible - some are a <code>core_version_requirement<\/code> update, and some are more complex.<\/p>\n\n<p>None of these modules have automated tests.<\/p>\n\n<p>If they did, I'd be able to run them and see if they pass, make my changes, and rerun the tests to verify they still pass, and the module works as it did previously.<\/p>\n\n<p>But I can't.<\/p>\n\n<p>I'd need to test each module beforehand to understand what it does manually and again after making the changes.<\/p>\n\n<p>This is more time-consuming, riskier, and easier for me to introduce regressions or new bugs.<\/p>\n\n<p>Whether it's a major CMS version upgrade, updating a contrib module or refactoring custom code, having a passing test suite you can use and rely on makes updates easier and less risky.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2b4eb1f8e6b76d78d911e2cbd7350312",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json b/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json
index 0a42a4574..d39a63b60 100644
--- a/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json
+++ b/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When looking at some websites, you can tell that it was built using a certain CSS framework.<\/p>\n\n<p>Whether it's using a standard component like a navbar or card, or it's using the default colour palette, you can confidently know that website uses ___.<\/p>\n\n<p>As Tailwind includes no components (other than the <code>container<\/code>) and only has low-level utility classes for things like spacing and colours (amongst many other things), you can build radically different-looking websites with the same classes.<\/p>\n\n<p>There are some <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">examples of UIs that I've rebuilt<\/a> and some websites that I show in my <a href=\"http:\/\/default\/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS talk<\/a>.<\/p>\n\n<p>If you take a look, you'll see what I mean.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "942ef7d759d47a0c58947ce472a9986a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json b/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json
index 5e958862c..5ba399b1d 100644
--- a/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json
+++ b/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Doing pair or programming doesn't mean you need to be working in groups continuously.<\/p>\n\n<p>If you've asked a colleague to review the code you're writing or help you fix a bug, that's pair programming.<\/p>\n\n<p>You don't always need a driver and navigator, a set rotation time or dedicated allocated daily pair programming time.<\/p>\n\n<p>While that works for some teams, and on some occasions, you can do what's needed or feels right at the time to complete the task at hand.<\/p>\n\n<p>If you need a short pair programming session to fix a bug or finish a feature, to review some code before you merge it or submit it for code review, or want to pair ad-hoc or for one afternoon a week, that works, too.<\/p>\n\n<p>There isn't one way to do pair or mob programming.<\/p>\n\n<p>Do what works for you.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a738fae17df1cd911b70ef29ae3283c8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json b/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json
index c55c899b4..8499c0447 100644
--- a/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json
+++ b/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In yesterday's email, I wrote about why <a href=\"http:\/\/default\/daily\/2024\/08\/16\/what-are-err--req-and-res\">readable variable names are important<\/a> and why I use descriptive variable names in my code.<\/p>\n\n<p>Given this pseudo-code:<\/p>\n\n<pre><code class=\"php\">function hande(req, res) {\n}\n<\/code><\/pre>\n\n<p>With the short variable names, whilst you can guess, it's unclear what the variable names are.<\/p>\n\n<p>However, in this code, we have the same variable names, but we also have additional type information:<\/p>\n\n<pre><code class=\"php\">function handle(Request req, Response res): void {\n}\n<\/code><\/pre>\n\n<p>Even with the same variable names, I know what their types are and what the function returns, I have better completions and diagnostics in my editor and better static analysis of my code, making it easier to identify and fix potential bugs.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "227626df1c8fc0c0d8c11465862dad57",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json b/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json
index d165fac8f..654b21e11 100644
--- a/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json
+++ b/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you have a request that starts with \"Just\", it's likely a red flag!<\/p>\n\n<p>Why is it being made?<\/p>\n\n<p>What problem is it going to solve?<\/p>\n\n<p>Whose problem does it solve?<\/p>\n\n<p>Is the problem time-sensitive?<\/p>\n\n<p>What value does it add?<\/p>\n\n<p>Is it the best solution to fix the problem?<\/p>\n\n<p>Is it the best solution to fix the problem right now?<\/p>\n\n<p>To know this, we need to know why it's needed and it \"just\" needs doing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4f25a7d5fdd045a4a767afa851b0d6f0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1a024983-b73b-4b2c-a350-db9152de27a9.json b/content/node.1a024983-b73b-4b2c-a350-db9152de27a9.json
index 1e2a19bb0..ebd20fd07 100644
--- a/content/node.1a024983-b73b-4b2c-a350-db9152de27a9.json
+++ b/content/node.1a024983-b73b-4b2c-a350-db9152de27a9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I <a href=\"https:\/\/twitter.com\/scottkeckwarren\/status\/1594752744165847040\">saw a tweet<\/a> where the writer said they were \u201cfalling into the branch, pull request, and merge after actions pass I use at work even though I'm the only one working on it\u201d.<\/p>\n\n<p>After reading this, my question is, \"Should you, or do you need to, create branches if you're the only person working on a project?\".<\/p>\n\n<p>These days, I use trunk-based development as much as possible, so I hardly ever create new branches, whether working on a project myself or with a team.<\/p>\n\n<p><a href=\"http:\/\/default\/presentations\/git-flow\">I used to use Git Flow<\/a> and create branches for every new feature and bug fix, but I remember, whilst demonstrating two work-in-progress features to a client, switching between the different branches caused my local site to break. Whilst it wasn\u2019t a major issue, it wouldn't have seemed professional.<\/p>\n\n<p>In a team environment, feature branches are intended to keep different changes and different people's work separate.<\/p>\n\n<p>But is this needed if you\u2019re the only in the team?<\/p>\n\n<p>Assumingly, you're only working on one change at a time, so what's the benefit of creating a separate branch?<\/p>\n\n<p>If you need to switch to a different task, another approach could be to revert your work-in-progress commits, move them onto another local branch temporarily, or wrap them within a feature flag so that the changes are committed but not active.<\/p>\n\n<p>The other part of the tweet said, \u201cI like the little integrations to make sure the tests pass\u201d.<\/p>\n\n<p>I\u2019m comfortable working on a single branch and committing and pushing small changes often.<\/p>\n\n<p>My CI pipelines run for every change that I push, and if one fails, I\u2019ll either push a small fix to get it passing again or revert the failing change and investigate further.<\/p>\n\n<p>For me, working on a single branch keeps my workflow simple and lean, allowing me to focus on the changes and the tasks that I need to work on and not worry about which branch I\u2019m working on.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "de98c57a7d583eb2f17a08ed813ccc09",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json b/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json
index 24cb5d3c2..c5fda0fe3 100644
--- a/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json
+++ b/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Here are some examples of PHP code from Drupal core:<\/p>\n\n<pre><code class=\"php\">\/**\n * The weight of this role in administrative listings.\n *\n * @var int\n *\/\nprotected $weight;\n<\/code><\/pre>\n\n<pre><code class=\"php\">\/**\n * Path of the image file.\n *\n * @var string\n *\/\nprotected $source = '';\n<\/code><\/pre>\n\n<pre><code class=\"php\">\/**\n * Alter the list of mail backend plugin definitions.\n *\n * @param array $info\n *   The mail backend plugin definitions to be altered.\n *\/\n<\/code><\/pre>\n\n<p>These use some of the standard PHPDoc types of <code>int<\/code>, <code>string<\/code> and <code>array<\/code>.<\/p>\n\n<p>Although they are comments, docblocks are checked by static analysis tools like PHPStan to parse the code and report any potential errors.<\/p>\n\n<p>If you want to go deeper, PHPStan has <a href=\"https:\/\/phpstan.org\/writing-php-code\/phpdoc-types\">its own PHPDoc types<\/a> that you can use to add more information and context.<\/p>\n\n<p>Instead of specifying an argument must be a <code>string<\/code>, you can specify it's a <code>non-empty-string<\/code> or a <code>class-string<\/code>.<\/p>\n\n<p>You can specify whether an integer is a <code>positive-int<\/code> or <code>negative-int<\/code>, or within a certain range.<\/p>\n\n<p>You can define the shape of an array or object, whether an array is empty, or the types of keys and values in an array.<\/p>\n\n<p>All of this is used by PHPStan when analysing the code and will give better results and find more potential bugs before anyone else does.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ded9b2a6eb8ff4129f9653ceb3555f58",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json b/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json
index 8552fc709..3f79bc860 100644
--- a/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json
+++ b/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm sure you've seen code comments that say the code will do something when, in fact, it does something different.<\/p>\n\n<p>Or documentation that has become outdated and stale and no longer correct.<\/p>\n\n<p>Automated tests and other tools, such as static analysis, are executable documentation, so they can't become stale.<\/p>\n\n<p>If the implementation code changes and no longer matches the tests, the tests will fail, and either the implementation or test can be updated.<\/p>\n\n<p>Then, if you need to refer to the test, as long as it's passing, you know what it shows is still applicable.<\/p>\n\n<p>The same can't be said for markdown files, Confluence pages, Word documents or other static documentation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1a79c3d8c5b39c15a45407dd2f8915dd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json b/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json
index 9b9f40104..a25063094 100644
--- a/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json
+++ b/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The main part of my CI pipeline tasks are running the automated tests, coding standards checks and static analysis.<\/p>\n\n<p>But which of these are the most valuable?<\/p>\n\n<p>I used to run the coding standards check first as it was the quickest, followed by static analysis and the automated tests.<\/p>\n\n<p>If a task were going to fail, it would fail quickly.<\/p>\n\n<p>But is that the objective of the CI pipeline?<\/p>\n\n<p>Whilst it needs to be quick, the main reason to run these is to ensure things work as expected.<\/p>\n\n<p>Recently, I changed my pipelines to run the tests first, as these verify the code's behaviour.<\/p>\n\n<p>I want to know if the code works but has a coding standard error that needs to be fixed rather than the pipeline failing on the error and not knowing whether the code works.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "40970926a00c3a7ef56c821881cbbc63",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json b/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json
index 9009d87b2..940903953 100644
--- a/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json
+++ b/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I'll be in Lille, France for DrupalCon Europe, where I'm presenting a session on automated testing and test-driven development in Drupal.<\/p>\n\n<p>I'll be taking a short break from these emails to enjoy the conference, focus on my talk, and finish my <a href=\"http:\/\/default\/atdc\">free email course on automated testing in Drupal<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "70254b7f809c1c35bcb40109b901f96e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json b/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json
index fc96cfe6a..a78f4b048 100644
--- a/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json
+++ b/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How many environments do you have for your software application, other than live\/production?<\/p>\n\n<p>Testing?\nStaging?\nUAT?\nPilot?\nQA?\nDev?<\/p>\n\n<p>What do you use each one for?<\/p>\n\n<p>What if you only had one pre-prod environment and production?<\/p>\n\n<p>What if you only had production?<\/p>\n\n<p>What if you only had one branch in your code repository?<\/p>\n\n<p>No more merge conflicts.<\/p>\n\n<p>No more confusion about which environment to test a change on.<\/p>\n\n<p>How much simpler would that make things?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "620e6d173305d1f917ba7bae4ae3d704",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json b/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json
index c5f346b51..606287cc4 100644
--- a/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json
+++ b/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I dusted off our Meetup page and posted our next <a href=\"https:\/\/www.meetup.com\/php-south-wales\">PHP South Wales meetup<\/a> event.<\/p>\n\n<p>We've had online meetups and code practice sessions throughout the pandemic and during lockdowns, but this will be our first offline\/in person\/IRL meetup since February 2020.<\/p>\n\n<p>As well as organising our online meetups during COVID, I attended a lot of other online events, <a href=\"http:\/\/default\/blog\/speaking-remotely-during-covid-19\">usually giving various talks or workshops<\/a>, and whilst they were good for a while, I eventually started to get burned out by them.<\/p>\n\n<p>I've been an organiser of various meetups and conferences for a long time, and attending events has been a very large part of my career so far - providing opportunities to learn, to network and socialise with other attendees, and pass knowledge on through talks, workshops and mentoring.<\/p>\n\n<p>It's been great to see some offline events returning, from local user groups to conferences such as DevOpsDays, DrupalCon and SymfonyLive.<\/p>\n\n<p>I've given one talk this year - a lot less than this time last year - but it was in front of an audience instead of a screen, and whilst it seemed strange, I'm sure that it's something that will feel normal again in time.<\/p>\n\n<p>I'm thinking of attending a conference next month, I've submitted some talk suggestions to some other conferences which I'm waiting to hear from, and am considering travelling to some of the other UK user groups as they restart - some of which I joined or spoke at online but it would be great to meet them in person.<\/p>\n\n<p>For next week, I'll be glad to have PHP South Wales events running again and to see our community back together in person, and then do it again and start getting ready for next month's event.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "99c8f2f1d316c939a4a59c03a17de896",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json b/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json
index a738246d7..f1381083a 100644
--- a/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json
+++ b/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as starting to speak again at conferences and meetups, I've been very busy lately with various client projects. I've been working on completing the next phase and launch of the next website for a long-term client and handed over some other completed projects.<\/p>\n\n<p>This has affected me sending out these emails every day and I missed a few days last month.<\/p>\n\n<p>I'll do better!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6b223577d98aafcacf18ecbf423a3497",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1d61b9ee-e6de-4db6-8782-68eba42d357a.json b/content/node.1d61b9ee-e6de-4db6-8782-68eba42d357a.json
index 514872018..792105e05 100644
--- a/content/node.1d61b9ee-e6de-4db6-8782-68eba42d357a.json
+++ b/content/node.1d61b9ee-e6de-4db6-8782-68eba42d357a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last month, I wrote an email explaining <a href=\"http:\/\/default\/daily\/2024\/02\/28\/why-i-dont-branch\">why I don't create branches<\/a>.<\/p>\n\n<p>After sending that email, I received this question from a reader (shared with permission):<\/p>\n\n<blockquote>\n  <p>I'm trying to work at one feature at a time, so I usually don't need feature branches.<\/p>\n  \n  <p>There's one thing that's difficult for me, maybe you could tell us something about this in one of your upcoming posts:<\/p>\n  \n  <p>How do you deal with hot fixes?<\/p>\n  \n  <p>I know, there's keeping features small, commit often and early. But sometimes this isn't possible, and a feature will take e.g. 3 days of work. Now, if there's an urgent bug in production that should be fixed asap, what are you doing?<\/p>\n  \n  <p>Git stash probably won't help here, as there might be commits already that would deliver an incomplete feature.<\/p>\n<\/blockquote>\n\n<h2 id=\"option-1%3A-worktrees\">Option 1: Worktrees<\/h2>\n\n<p>Whilst I don't create branches, I do use <a href=\"http:\/\/default\/daily\/2022\/08\/12\/git-worktrees-docker-compose\">Git worktrees<\/a>, which allows me to have multiple versions of the code checked out at the same time - similar to having multiple clones of a repository.<\/p>\n\n<p>Having multiple worktrees, you don't need to stash the code for your incomplete feature or worry about commits you haven't pushed yet.<\/p>\n\n<p>You can create a new worktree, fix the urgent bug and switch back to your <code>main<\/code> worktree when you're finished.<\/p>\n\n<p>You'll still need to update the original worktree with your new changes which may result in conflicts - the same as merging or rebasing onto a branch.<\/p>\n\n<h2 id=\"option-2%3A-feature-flags\">Option 2: Feature Flags<\/h2>\n\n<p>My preferred approach is to use <a href=\"http:\/\/default\/daily\/2022\/12\/07\/separating-releases-from-deployments-with-feature-flags\">feature flags<\/a>, a.k.a. feature toggles.<\/p>\n\n<p>My wrapping the incomplete feature in a feature flag, it can be deployed but won't be active until the flag is enabled - similar to writing a new Drupal module but not enabling it.<\/p>\n\n<p>This is a technique I use often as it works well with trunk-based development and continuous integration and delivery.<\/p>\n\n<p>When the incomplete feature is feature-flagged, you can fix the bug and deploy the hotfix without stashing or rebasing any changes, and you can leave the flag disabled.\nWhen the feature is ready, enable the feature flag to activate it and, if you need to turn it off again (maybe that's causing the next bug), you can easily disable it without needing to revert and deploy the code again.<\/p>\n\n<p>You can just turn the feature flag back off.<\/p>\n\n<p>I hope that helps!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4bbe23be0133c280a8c7e9fe479570ad",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json b/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json
index edc9ab693..0e9db4a3f 100644
--- a/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json
+++ b/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The call for session proposals is currently open for DrupalCon Europe, which is happening in Vienna this October.<\/p>\n\n<p>The tracks are slightly different this year.<\/p>\n\n<p>The tracks are:<\/p>\n\n<ul>\n<li>Agency &amp; Business.<\/li>\n<li>Coding &amp; Site Building.<\/li>\n<li>Community Health.<\/li>\n<li>Clients &amp; Industry Experience.<\/li>\n<li>Drupal CMS.<\/li>\n<li>InfoSec &amp; DevOps.<\/li>\n<li>Open Web.<\/li>\n<\/ul>\n\n<p>I'm happy to be on the Coding &amp; Site Building track team this year, having been on the Makers &amp; Builders track previously.<\/p>\n\n<p>The call for proposals is open until the 28th of April, but feel free to <a href=\"https:\/\/kuonicongress.eventsair.com\/drupalcon-vienna-2025\/session-submission-portal\">get your session proposal in now<\/a>.<\/p>\n\n<p>For more information and blog posts from the track teams, go to <a href=\"https:\/\/events.drupal.org\/vienna2025\">https:\/\/events.drupal.org\/vienna2025<\/a>.<\/p>\n\n<p>If you're submitting to the Coding &amp; Site Building track, I'll look forward to reading your proposal.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "44eace8ddc51bab34e23bb1cc0825908",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json b/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json
index 95eda3da2..041ee84a7 100644
--- a/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json
+++ b/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently used <a href=\"https:\/\/www.drupal.org\/project\/feature_toggle\">Drupal's Feature Toggle module<\/a> to set a data attribute which enabled some new styling for buttons.<\/p>\n\n<p>Firstly, within the theme's .theme file, I added this code:<\/p>\n\n<pre><code class=\"php\">\/**\n * Implements hook_preprocess_html().\n *\/\nfunction mytheme_preprocess_html(array &amp;$variables): void {\n  $variables['attributes']['data-use-new-button-styles'] = \\Drupal::service('feature_toggle.feature_status')-&gt;getStatus('use_the_new_button_styling');\n}\n<\/code><\/pre>\n\n<p>If the feature toggle is enabled, it adds a <code>data-use-new-button-styles=\"\"<\/code> attribute to the <code>body<\/code> element.<\/p>\n\n<p>If it is disabled, the attribute is not added, so I can write CSS that's applied when the data attribute is present:<\/p>\n\n<pre><code class=\"css\">[data-use-new-button-styles] .btn-primary {\n  background-color: red;\n}\n<\/code><\/pre>\n\n<p>In a Tailwind CSS project (this isn't), the same could be achiveable with a custom interaction state - similar to <code>hover<\/code>, <code>focus<\/code> and <code>active<\/code>. Something like <code>new-button-styles:bg-red-500<\/code>.<\/p>\n\n<p>I like using feature flags and was happy to find a way to use them when adding this new CSS.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "290ba77a217288ad367ab07bf02a2265",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json b/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json
index e4fd0c4f2..3ec782b8d 100644
--- a/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json
+++ b/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been through several iterations of my website over the years and used different technologies.<\/p>\n\n<p>The first versions were on Drupal 6 and 7 before I started to explore static site generators like Jekyll and Sculpin.<\/p>\n\n<p>One version was written with a JavaScript-based static site generator, but it needed a lot of JavaScript to render a simple HTML website.<\/p>\n\n<p>The current version has no JavaScript at all.<\/p>\n\n<p>There is no analytics script, carousels or fancy transitions.<\/p>\n\n<p>I keep the functionality as simple as possible.<\/p>\n\n<p>It's fast, accessible and responsive.<\/p>\n\n<p>If I'm considering adding something, I ask \"do I really need this?\".<\/p>\n\n<p>What impact will it have? Positive or negative.<\/p>\n\n<p>Do I want to take on the overhead of maintaining it?<\/p>\n\n<p>If not, I don't add it.<\/p>\n\n<p>If you don't already ask this in your projects, start.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "765bdd698c2180895d0727169bf613cb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json b/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json
index c31e453eb..f1487afcf 100644
--- a/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json
+++ b/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In <a href=\"http:\/\/default\/podcast\/8-eirik-morland-violinist\">today's episode of the Beyond Blocks podcast<\/a>, I'm joined by Eirik Morland - the Developer of <a href=\"https:\/\/violinist.io\">Violinist<\/a>.<\/p>\n\n<p>We discuss why you'd want to use a tool like Violinist to manage your dependency updates, why you'd want to automate repetitive tasks and focus on providing value for clients and customers.<\/p>\n\n<p>We also discuss running a SaaS business and why Drupal is a good choice for SaaS products - though this could be a full episode on its own.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "630fb2a05269acd6616e9f0d51b2c360",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json b/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json
index 0268e6088..abf995a82 100644
--- a/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json
+++ b/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/archives\/2022\/09\/03\/creating-infrastructure-with-ansible\">In yesterday's email<\/a>, I described how to set up a blank server with Ansible.<\/p>\n\n<p>Now that we've done that, it needs to be configured.<\/p>\n\n<p>Once the server\u2019s IP address or hostname has been added to a <code>hosts.ini<\/code> file, you can run ad-hoc commands against it - such as <code>ansible all -i hosts.ini -m ping<\/code> to run Ansible's <code>ping<\/code> module on all of the hosts in your inventory and check that you can connect to them.<\/p>\n\n<p>Another useful one that you can use is the <code>shell<\/code> module, that runs ad-hoc run commands on each host. If you need to check the uptime of each of your servers, run <code>ansible all -i hosts.ini -m shell -a uptime<\/code>. You can replace the last argument with any other shell command that you need to run, like <code>df<\/code> or <code>free<\/code>.<\/p>\n\n<p>Running commands in this way is great for getting started, for routine maintenance, or an emergency free disk space check, but for more complex tasks like configuration management, using playbooks is the better option. They are YAML files that contain lists of tasks that Ansible will run through and execute in order.<\/p>\n\n<p>If you have a group of related tasks, such as for installing a piece of software, then you can combine them into roles. In fact, Ansible Galaxy has thousands of pre-built collections and roles that you can download, include in your playbooks, configure, and run.<\/p>\n\n<p>Very quickly, you can get a full stack installed and configured - ready to serve your application.<\/p>\n\n<hr>\n\n<p>Want to learn more about how I use Ansible? <a href=\"http:\/\/default\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "316effd21316b7cbda5678cf691fc683",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json b/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json
index 1eda3d0f2..2a6f364a3 100644
--- a/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json
+++ b/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Although I wouldn't consider myself a \"Laravel Developer\", I enjoy watching the talks from the Laravel conferences, most recently Laracon US, that took place last week.<\/p>\n\n<p>I like to learn from other communities and adopt relevant practices or tools within my projects. I did this with Laravel Collections, which I use on nearly every project.<\/p>\n\n<h2 id=\"laravel-prompts\">Laravel Prompts<\/h2>\n\n<p>I watched Jess Archer's talk on the new Laravel Prompts and was happy when she said it worked with plain PHP projects, not just Laravel.<\/p>\n\n<p>This means I can potentially use it with Drupal and Drush or Symfony Console applications, too, such as my build configuration file generator.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I like tools I can use across multiple technologies and prefer framework-agnostic tools to specific ones.<\/p>\n\n<p>Then, if I'm working on a different project, I can use the tools I already know instead of learning something different just for that.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "37e18d6b3d8c61b4ed2592c0d3ede8c2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json b/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json
index f2874169a..15a0ddd18 100644
--- a/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json
+++ b/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>During a webinar I watched recently, someone described test-driven-development as clicker training for Developers.<\/p>\n\n<p>Similar to when people want to train an animal, the short cycles and quick feedback loops make it easier to stay focussed as you work on a task, and the satisfaction of getting a test to pass, completing a feature, or refactoring some messy code is the reward.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a039f34850bd65b5d0ce42db6cc13f1b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json b/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json
index 4d3ae95ba..1d65ac454 100644
--- a/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json
+++ b/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In unit tests, and sometimes in kernel tests, you need to mock the dependencies you aren't testing, but you can over-mock and only be testing the mocks and not the code you want to test.<\/p>\n\n<p>Here's an example (thanks, ChatGPT, for the code).<\/p>\n\n<h2 id=\"the-class-to-be-tested-myclass.php\">The Class to be tested (MyClass.php)<\/h2>\n\n<pre><code class=\"language-php\">&lt;?php\n\nclass MyClass {\n\n  public function __construct(\n    private DependencyInterface $dependency\n  ) {\n  }\n\n  public function doSomething() {\n    $result = $this-&gt;dependency-&gt;performAction();\n\n    return \"Result: \" . $result;\n  }\n}\n<\/code><\/pre>\n\n<h2 id=\"dependency-interface-dependencyinterface.php\">Dependency Interface (DependencyInterface.php)<\/h2>\n\n<pre><code class=\"language-php\">&lt;?php\n\ninterface DependencyInterface {\n\n  public function performAction();\n\n}\n<\/code><\/pre>\n\n<h2 id=\"a-test-class-that-ends-up-testing-mocks-myclasstest.php\">A test class that ends up testing mocks (MyClassTest.php)<\/h2>\n\n<pre><code class=\"language-php\">&lt;?php\n\nuse PHPUnit\\Framework\\TestCase;\n\nclass MyClassTest extends TestCase {\n\n  public function testDoSomething() {\n    \/\/ Creating a mock of the DependencyInterface.\n    $dependencyMock = $this-&gt;createMock(DependencyInterface::class);\n\n    \/\/ Setting up the mock to return a specific value.\n    $dependencyMock-&gt;expects($this-&gt;once())\n      -&gt;method('performAction')\n      -&gt;willReturn('Mocked result');\n\n    \/\/ Creating an instance of MyClass with the mock.\n    $myClass = new MyClass($dependencyMock);\n\n    \/\/ Calling the method to be tested.\n    $result = $myClass-&gt;doSomething();\n\n    \/\/ Asserting that the result matches the expected value.\n    $this-&gt;assertEquals('Result: Mocked result', $result);\n  }\n\n}\n<\/code><\/pre>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>In this example, the test creates a mock for the <code>DependencyInterface<\/code> and sets up an expectation that the performAction method will be called once, returning a specific value.<\/p>\n\n<p>The test then calls the <code>doSomething<\/code> method on <code>MyClass<\/code> and asserts that the result is as expected.<\/p>\n\n<p>The issue with this test is that it's not testing the actual behaviour of <code>MyClass<\/code>.<\/p>\n\n<p>It's only testing that the mock is configured correctly.<\/p>\n\n<p>If the real implementation of <code>MyClass<\/code> has a bug, this test won't catch it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "db65f35f5c7767e34b717942905448f4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json b/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json
index 89e8c1b69..9dd59174c 100644
--- a/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json
+++ b/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/03\/04\/why-you-need-layers-in-your-application-code\">Yesterday<\/a>, I wrote about writing layers in your application code and the benefits of loosely coupled code.<\/p>\n\n<p>Something else you can do with this approach is to write framework-agnostic code.<\/p>\n\n<p>By writing your business logic in code that isn't tied to a specific framework or CMS, with a small adapter layer, you can upgrade to a newer version of the framework, such as Drupal 7 to 10, or a different framework,  keep most of the code the same and only update the parts that connect the business logic and the framework.<\/p>\n\n<p>This is something that Commerce Guys (now Centarro) did when creating Drupal Commerce 2.0.<\/p>\n\n<p>The logic around addressing, tax, etc., was released in separate PHP libraries, each with its own release cycle and reusable logic.<\/p>\n\n<p>This meant the Drupal modules were much smaller, and other eCommerce systems and frameworks could use the agnostic libraries.<\/p>\n\n<p>It's something to consider when writing your next Drupal module.<\/p>\n\n<p>It's something <a href=\"https:\/\/github.com\/opdavies\/national-rail-enquiries-feed-parser\">I did recently<\/a> and have done on client projects previously, and it can be a good approach.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b758f9153177dd2e50122508bd8103c6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json b/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json
index 7b2c53af4..3551efeb9 100644
--- a/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json
+++ b/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Open-source software, such as Drupal modules and themes, PHP libraries and Tailwind CSS plugins, is great.<\/p>\n\n<p>Instead of writing everything from scratch, if someone else has written what you need, you can use it.<\/p>\n\n<p>In the Drupal ecosystem, there's a saying - \"There's a module for that!\".<\/p>\n\n<p>But, assuming you find a project that adds the functionality you need, you should review and vet it before adding it to your application.<\/p>\n\n<p>Adding too many modules and libraries can cause performance issues, add a maintenance overhead, introduce upstream bugs and add potential security vulnerabilities.<\/p>\n\n<p>As well as reading the code, here are some questions I ask and things I look for when deciding to add a project or not:<\/p>\n\n<ul>\n<li>Does it do what I need?<\/li>\n<li>Does it add too much functionality? Is there a more minimal version that does what I need without the extra overhead?<\/li>\n<li>Does it have a stable release? If there's only a development or alpha release (which are unstable and can break at any time), I wouldn't add it.<\/li>\n<li>Is it extendable? Can I configure or extend it if I need to add more or alter it's default functionality?<\/li>\n<li>How many other websites are using it? Websites like Drupal.org and Packagist will show usage statistics.<\/li>\n<li>How many open issues are there?<\/li>\n<li>When was the most recent commit and release?<\/li>\n<li>Does it have automated tests? If so, are they passing?<\/li>\n<li>Does it have a README.md file or other documentation?<\/li>\n<li>Who are the maintainers?<\/li>\n<li>Are they responsive to issues and accepting of outside contributions? If I find a bug, can I fix and contribute it?<\/li>\n<li>Does the project have a published roadmap?<\/li>\n<\/ul>\n\n<p>Finally:<\/p>\n\n<p>Do I really need it?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "920f52af5b2ff64ff720e6726ce03219",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json b/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json
index e1239776a..0398a92e3 100644
--- a/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json
+++ b/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Static websites are the easiest way to build websites.<\/p>\n\n<p>You create an index.html file, type some words, open the file in a browser and you'll see the words you entered.<\/p>\n\n<p>You built a website!<\/p>\n\n<p>Then you can create any more pages you need and style it with CSS.<\/p>\n\n<p>This how I built my first website, for a Tae Kwon-Do school I used to train at.<\/p>\n\n<p>This worked great, but at some point, becomes hard to scale.<\/p>\n\n<p>What if you want to add a new link to your navigation menu? You'd need to update each HTML page separately.<\/p>\n\n<p>At this point, I started to learn about PHP and MySQL, and then Drupal.<\/p>\n\n<p>Static site generators like Sculpin, Jekyll and Hugo also fix this problem.<\/p>\n\n<p>They allow you to write HTML files with a template language like Twig and use includes, loops and conditions to make your files easier to create and maintain with a language and tools you're familiar with.<\/p>\n\n<p>It still generates a static website with HTML files, but in a more maintainable way.<\/p>\n\n<p>As a PHP Developer, I like Sculpin but also like Tome to export a Drupal website to static HTML.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "898a4ca4ca6f3d15e2c342efb0420bee",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json b/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json
index 9a5765b88..24481882c 100644
--- a/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json
+++ b/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>At Saturday's hackathon that I mentioned in yesterday's email, most of the squads decided to try Tailwind CSS in their applications.<\/p>\n\n<p>I've been using Tailwind since it was released, and first gave <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">a Tailwind CSS talk<\/a> in January 2018.<\/p>\n\n<p>It's one of my most popular talks and, during COVID lockdowns, I also gave a workshop\/webinar on Tailwind CSS for some online conferences.<\/p>\n\n<p><a href=\"https:\/\/www.youtube.com\/watch?v=phFDKF-9j0Y\">Here's a recording<\/a> of the session I gave for DrupalCamp Florida, in which I cover some Tailwind CSS concepts and show how to install and customise Tailwind before rebuilding the Florida DrupalCamp website live.<\/p>\n\n<p>If this helps anyone on their Tailwind CSS learning journey, please reply and let me know!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5d155c99bbf381198855ff0d06445dcc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json b/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json
index 3eb3f32ab..87220b1e3 100644
--- a/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json
+++ b/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've usually written user stories that follow this format:<\/p>\n\n<p>As a...\nI want...\nSo that...<\/p>\n\n<p>You focus on the person who needs the task first, followed by what they want, and why they want it.<\/p>\n\n<p>Lately, I've been re-ordering stories to follow this order:<\/p>\n\n<p>So that...\nAs a...\nI want...<\/p>\n\n<p>What I like about this is that it focuses on capturing the \"why\" of the story first rather than at the end or maybe even forgetting it altogether.<\/p>\n\n<p>What's needed and who needs it doesn't matter unless you also capture why it's needed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "03e072b02f75cb69315b1b458f6b6e71",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json b/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json
index c8341089c..d59b8923f 100644
--- a/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json
+++ b/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I reviewed a client's Drupal 9 website and investigated the steps needed to upgrade to Drupal 10.<\/p>\n\n<p>Looking at the Git log to see the commits for a module, I see <code>Week 20 development<\/code> as the latest commit message.<\/p>\n\n<p>That commit changed 106 files, added 3,453 lines and removed 17 lines, including custom module and theme changes, contrib module updates and library updates.<\/p>\n\n<p>This should have been several commits, each performing a clear and separate task.<\/p>\n\n<p>Updating the dependencies should be its own commit, and changes to the custom modules and theme should be separate commits.<\/p>\n\n<p>Then each commit could have its own clear and descriptive commit message explaining why each change was needed, any issues that were encountered during the change, and any alternative approaches considered.<\/p>\n\n<p>That would have been more useful for me whilst looking through the logs than <code>Week 20 development<\/code>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "75d576395418eeee1ebec49730c22762",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json b/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json
index 5207f5e52..feb6cd0d1 100644
--- a/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json
+++ b/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You need to add an integration with a new service or supplier to your application code.<\/p>\n\n<p>You should avoid writing code that interacts directly with that service or supplier - a.k.a tightly-coupled code.<\/p>\n\n<p>What if you change to a different service or supplier in the future?<\/p>\n\n<p>What if they release a new version of their API that includes breaking changes?<\/p>\n\n<p>If your code is tightly coupled to a single implementation, you'd need to rewrite the code, and there wouldn't be a way to easily switch from the old version to the new one.<\/p>\n\n<p>By introducing an adapter layer, you make your code more loosely coupled.<\/p>\n\n<p>You can have multiple implementations, with one for each different supplier, service, or version.<\/p>\n\n<p>You can have a consistent interface and API for every implementation, making them hot-swappable and making it easy to switch between different implementations.<\/p>\n\n<p>If you change supplier or they release a new version, you write a new implementation for it and switch when you're ready.<\/p>\n\n<p>Also, as every implementation satisfies a common interface, it's easy to make a fake implementation that you can use for testing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d5f31c0bb830b46174ae9f0b2d15e7ea",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json b/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json
index 8968af69f..c5ec18474 100644
--- a/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json
+++ b/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When working with teams who are starting with automated tests and test-driven development, a common issue is being stuck on a failing test and trying to do too much at once while getting it to pass.<\/p>\n\n<p>Instead, work in small bite-sized iterations and focus on getting the test to pass as quickly as possible.<\/p>\n\n<p>You don't want to be stuck in a failing state for longer than you need to.<\/p>\n\n<p>Run the tests often, write the simplest code possible and don't write any code that isn't driven by a failing test.<\/p>\n\n<p>Don't make too many changes at once so, if you do get stuck, you can reset to the last working test and start again.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6779f3fdf5c222d23fde37cb0801d08c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json b/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json
index 5ff3f5ea6..874fb856f 100644
--- a/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json
+++ b/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As someone who develops with open-source software such as Drupal, Symfony, and Sculpin and uses Linux to <a href=\"http:\/\/default\/daily\/2024\/11\/28\/running-nixos-in-the-cloud\">host my applications<\/a> and <a href=\"http:\/\/default\/daily\/2024\/11\/23\/no-more-random-packages\">configure my laptop<\/a>, I've recently started to explore creating a home lab and self-hosting services based on other open source software.<\/p>\n\n<p>I've started using Jellyfin for media management and playback, Immich for photos, Gitea for hosting my private Git repositories, and Tube Archivist for backing up YouTube videos.<\/p>\n\n<p>There are a lot of other popular applications that people self-host that I want to look at, as well as maybe hosting my own website.<\/p>\n\n<p>I've removed proprietary note-taking applications <a href=\"http:\/\/default\/daily\/2024\/11\/10\/write-plain-text-files\">in favour of plain text files<\/a> and continued searching for free and open source alternatives to services I've used.<\/p>\n\n<p>My ethos is to be open source first and to favour an open source solution if there is one.<\/p>\n\n<p>And if there isn't, I can write one.<\/p>\n\n<p>As well as creating free and open source software, I want to use it as much as I can as well as using open source software to create my open source software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "826ea7f42a178becea87291123dedc78",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json b/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json
index 71826fa9d..def95a09f 100644
--- a/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json
+++ b/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>For some time, <a href=\"https:\/\/www.drupal.org\/docs\/develop\/standards\/php\/php-coding-standards#s-functions-and-variables\">Drupal's PHP coding standards<\/a> allows for writing variables in either snake-case (e.g. <code>$my_variable<\/code>) or lower camel-case (<code>e.g. $myVariable<\/code>).<\/p>\n\n<p>It originally only allowed for snake-case variable names but once it accepted both, I switched to camel-case as my default.<\/p>\n\n<p>Why? I didn't like the inconsistency of using one approach for variable names and one for method and property names in PHP classes (which were always camel-case).<\/p>\n\n<p>I'd have had code like this with a mixture of both:<\/p>\n\n<pre><code class=\"language-php\">class MyClass {\n\n  private EntityTypeManagerInterface $entityTypeManager;\n\n  public function __construct(EntityTypeManagerInterface $entity_type_manager) {\n    $this-&gt;entityTypeManager = $entity_type_manager;\n  }\n\n}\n<\/code><\/pre>\n\n<p>Or even more simply:<\/p>\n\n<pre><code class=\"language-php\">$entity_type_manager = \\Drupal::entityTypeManager();\n<\/code><\/pre>\n\n<p>I prefer not to have to consistently think about which to use and, if possible, like to use standard approaches in different codebases whether I'm working on a Drupal project, a Symfony project, or a PHP library.<\/p>\n\n<p>Plus, I get to use new PHP features like <a href=\"http:\/\/default\/daily\/2023\/04\/12\/cleaner-php-code-with-promoted-constructor-properties\">promoted constructor properties<\/a> if everything is named in the same format.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0d32d809ef0473c3b8fd336040076cae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json b/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json
index aeffd6092..26997cd94 100644
--- a/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json
+++ b/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As a Developer with 15 years of experience, I still sometimes get \"deployment anxiety\" - when I've backed up the database and tagged a release, but even though the CI pipelines are passing and the staging site is working, I'm holding off on pushing the latest code to be released to production - trying to think of any potential issues that could arise from this deployment and avoid any downtime.<\/p>\n\n<p>When I thought about this further, the releases that I've felt anxious or nervous about have usually been in at one or both of the following categories:<\/p>\n\n<ul>\n<li>The release includes a lot of changes, and maybe a combination of different types of changes such as framework or CMS updates, bug fixes, or new features.<\/li>\n<li>It's been a long time, maybe weeks or months, since the last production release.<\/li>\n<\/ul>\n\n<p>The best way to resolve both of these issues, I think, is to break down the large releases into smaller ones, and to deploy them more frequently.<\/p>\n\n<p>In the opposite scenario, the releases where the changes are small and it's been a short time since the previous release - ideally minutes or hours - have been the ones where I've been the least nervous.<\/p>\n\n<p>If a single commit is being released, then I can be confident that if there is a failure, I can either revert it and put things back the way they were or quickly identify the issue and push a fix. This isn't the case for large changes as the potential source of the failure is larger and it will take longer to find and fix.<\/p>\n\n<p>If a bug fix or a feature needs to be reverted, I'm happy knowing that I can do that easily without also reverting the CMS update that was deployed separately - rather than them all being released together.<\/p>\n\n<p>There are other advantages too - clients or product owners are generally happier if the new feature or fix that they requested is on production within hours or days rather than weeks or months, and having your latest code deployed to production rather than on a staging branch makes it a lot easier if you need to deploy an urgent fix or security update.<\/p>\n\n<p>If you're familiar with the DevOps Research and Assessment (DORA) team, three of their key metrics are deployment frequency, lead time for changes, and time to restore service. All of these are improved by small and frequent releases.<\/p>\n\n<p>In my <a href=\"http:\/\/default\/presentations\/deploying-php-ansible-ansistrano\">Deployments with Ansible and Ansistrano talk<\/a>, I mention that there is a separate rollback role, but I don't think that I've ever used it.<\/p>\n\n<p>Because I'm deploying small changes often, it's usually much easier to fix forward than it is to rollback, and knowing this makes me a lot less anxious when deploying changes.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "31f3de322f3c108fbaf235ca30453bf5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.22e50919-7f11-45ed-881e-31482670f416.json b/content/node.22e50919-7f11-45ed-881e-31482670f416.json
index 13d9a9144..55250c3db 100644
--- a/content/node.22e50919-7f11-45ed-881e-31482670f416.json
+++ b/content/node.22e50919-7f11-45ed-881e-31482670f416.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In a typical feature release process, a feature is released when you merge the code and push it to production.<\/p>\n\n<p>If a bug is found after the release, the code needs to be reverted (and any conflicts or issues dealt with) and deployed again.<\/p>\n\n<p>Also, features can only be merged once they are complete, which may take hours, days or weeks, depending on the size of the feature.<\/p>\n\n<p>These are some reasons I like to use feature flags (aka feature toggles) and separate the code deployment from releasing the feature. The code is deployed as before, but the feature isn't released, and the code isn't executed until a feature flag is enabled.<\/p>\n\n<p>If there is a bug, the feature flag can be disabled, and the feature is turned off until a fix can be pushed - without needing another code deployment.<\/p>\n\n<p>If my feature is incomplete, if it's feature flagged, I can commit and deploy it without users seeing it or affecting the running application, resulting in smaller and more manageable commits and deployments.<\/p>\n\n<p>If you wanted, you could enable a feature flag for a subset or a certain subsection of your users - allowing them to test it before making it available to everyone.<\/p>\n\n<p>Another way I use feature flags is within a <a href=\"http:\/\/default\/daily\/2022\/11\/13\/how-i-manage-multiple-drupal-websites-using-the-same-codebase\">multi-site Drupal application<\/a> to enable a different feature set per site and allow me to keep one version of the code for all sites to keep this easy to manage and maintain.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c91a13187040e9edc5a979e4742e7619",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json b/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json
index ec7400802..652a835e5 100644
--- a/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json
+++ b/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json
@@ -87,6 +87,5 @@
             "processed": "<p>A few days ago, I published a new episode of the Beyond Blocks podcast with Luke McCormick, where we spoke about using AI and tools like Cursor for web coding.<\/p><p>Unfortunately, there was an export issue with the episode that affected the sound quality.<\/p><p>The recording was fine and the mp3 file was re-created and uploaded again to the episode page and the podcast feed for Spotify, Pocket Casts, etc.<\/p><p><a href=\"http:\/\/default\/podcast\/28-using-ai-tools-web-coding\">Listen to the episode here<\/a>.<\/p><p>Apologies to Luke and anyone who listened to the original release for the poor quality, but it should be fine now and I'll add this to my checklist when editing podcast episodes to ensure it doesn't happen again.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json b/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json
index e36341006..198fe1d28 100644
--- a/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json
+++ b/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was recently asked about setting up different testing environments based on topic (a.k.a. feature) branches.<\/p>\n\n<p>When a feature or bug fix was finished, it would create a new environment for it to be tested.<\/p>\n\n<p>If it passed testing, the topic branch was merged and it would be included in the next release.<\/p>\n\n<p>But, there's no guarantee it still works once it's been merged.<\/p>\n\n<p>It could conflict with changes from a different topic branch and no longer work - even if it worked when it was tested in isolation on its own branch.<\/p>\n\n<p>To ensure it still works, it will need to be tested again.<\/p>\n\n<p>So, what is the benefit of testing it in isolation if it needs to be tested again once it's merged?<\/p>\n\n<p>This is why I prefer continuous integration and delivery (CI\/CD), as I always know all changes work together and not just in isolation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a3e94e918c387456f8b5d5871cf5e306",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json b/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json
index 8b7bee7cf..0e75ba910 100644
--- a/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json
+++ b/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something that I often see in code examples or tutorials are test methods like <code>testGet<\/code> or <code>testAdd<\/code>, or <code>testSubtract<\/code>. Short method names that don't describe the scenario that they're testing in much detail.<\/p>\n\n<p>What if a <code>get<\/code> method returns different types of value based on the input or a string is passed into a calculator method like <code>add<\/code> or <code>subtract<\/code>?<\/p>\n\n<p>I'd assume that the result of the calculation returns the total, but the test method doesn't say this.<\/p>\n\n<p>I'd rather be overly descriptive and write methods like <code>should_add_two_or_more_numbers_and_return_the_total()<\/code> rather than <code>testAdd<\/code>. It's a lot more readable and easier to see what the intention of the test is, and it's much better to use longer descriptive names when using options like <code>--testdox<\/code> with PHPUnit, which converts the method name into a sentence, which is what I do when running tests in CI pipelines.<\/p>\n\n<p>Something that I've picked up and recommend is to start each test case with the word \"It\" or \"Should\". This gives it a more behavioural feel and puts you in the mindset of what you're testing and not the methods that you're executing.<\/p>\n\n<p>A method like 'testAdd' might make sense within a unit test focusing on a single class and method, but as I usually do outside-in testing - which mostly uses functional and integration tests - this approach works well for me.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e95a217380424b7821a1a9e61d048019",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json b/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json
index 154a74d0b..f853d7745 100644
--- a/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json
+++ b/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week is DrupalCon Prague, and although I'm not at this event, I'd like to write about some my experiences at DrupalCon - in particular about being a contribution mentor.<\/p>\n\n<h2 id=\"my-first-drupalcon\">My first DrupalCon<\/h2>\n\n<p>The first DrupalCon that I attended was in 2013, also in Prague.<\/p>\n\n<p>I was enjoying the session days when I stopped at the mentoring table to find out more about the contribution sprints that were happening on the Friday.<\/p>\n\n<p>I didn't have any commits in Drupal core but had already worked on and released some of my own contributed modules, so I was familiar with the tools and the Drupal.org contribution workflow. In short, I was signed up to be a mentor during the sprints.<\/p>\n\n<p>I remember being involved in the preparation too, sitting in a hotel lobby, identifying potential issues for new contributors to work on, alongside people who I'd previously interacted with in the issue queues on Drupal.org.<\/p>\n\n<p>On the day, I helped new contributors get their local environments up and running, select issues to work on, and perform tasks like creating and re-rolling patch files and submitting them for review.<\/p>\n\n<p>One of my highlights at the end of the day was the live commit, when a patch that a new contributor had worked on that day was committed to Drupal core live on stage!<\/p>\n\n<p>Whenever I've attended DrupalCon events since, I've always volunteered to be a contribution mentor, as well as mentoring and organising sprints at other Drupal events.<\/p>\n\n<h2 id=\"the-five-year-issue\">The Five Year Issue<\/h2>\n\n<p>One of the most memorable times mentoring was whilst working with a group of contributors at DrupalCon in May 2015.<\/p>\n\n<p>Someone was working on a Drupal core issue that was very similar to <a href=\"https:\/\/www.drupal.org\/project\/drupal\/issues\/753898\">one that I'd looked at<\/a> a few years before.<\/p>\n\n<p>We focused on the original issue that I'd commented on, reviewed, tested, and re-rolled the patch, fixed a failing test, and marked it as \"reviewed and tested by the community\".<\/p>\n\n<p>A few days after the conference, and just over five years after my original comment, the patch was committed - giving my contributors their first commits to Drupal 8 core, and also <a href=\"https:\/\/git.drupalcode.org\/project\/drupal\/-\/commits\/9.5.x?search=opdavies\">one of mine<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0c8202093b9bab15e532858ca4d09169",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json b/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json
index d6bdc1d63..69f4949b8 100644
--- a/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json
+++ b/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you use PHP and need to make a static website, <a href=\"https:\/\/sculpin.io\">Sculpin<\/a> is a great choice!<\/p>\n\n<h2 id=\"what-is-it%3F\">What is it?<\/h2>\n\n<p>Built with PHP and using Symfony components, it converts Markdown files and Twig templates into static HTML that can be easily deployed and hosted.<\/p>\n\n<p>Once generated, you can upload the files to a web host of your choice as the generated files are simple HTML, such as an S3 bucket with static hosting or GitHub Pages.<\/p>\n\n<h2 id=\"why-do-i-use-it%3F\">Why do I use it?<\/h2>\n\n<p>As a PHP Developer, it's already familiar and I can immediately start instead of learning a new language or templating engine, which I'd need to do if I were to use a static site generator written in Ruby, JavaScript or Go.<\/p>\n\n<p>If I need to extend it, I already can.<\/p>\n\n<p>I already know how to write custom Twig extensions, for example, so I can do it in Sculpin in the same way. (<a href=\"https:\/\/github.com\/opdavies\/sculpin-twig-markdown-bundle\">I made one<\/a> and open-sourced it)<\/p>\n\n<p>I already know how to use PHPUnit to write tests.<\/p>\n\n<h2 id=\"what-do-i-use-it-for%3F\">What do I use it for?<\/h2>\n\n<p>I use Sculpin for <a href=\"https:\/\/github.com\/opdavies\/oliverdavies.uk\">this website<\/a> and client projects that don't need the features of a CMS or framework with the ability to have reusable components and functionality provided by Twig (this works great with Tailwind CSS, too).<\/p>\n\n<p>I used it to <a href=\"http:\/\/default\/test-drive-twig-with-sculpin\">learn Twig before Drupal 8 was released<\/a>, back in 2015.<\/p>\n\n<p>I've also given a talk on <a href=\"http:\/\/default\/building-static-websites-sculpin\">building websites with Sculpin<\/a> which I may submit to some upcoming conferences.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6b0cc2a798390fc93ca034bf92dc6df9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.25294346-8919-49c4-affa-d87616ed3df5.json b/content/node.25294346-8919-49c4-affa-d87616ed3df5.json
index 71a1d3dbe..64f0f9871 100644
--- a/content/node.25294346-8919-49c4-affa-d87616ed3df5.json
+++ b/content/node.25294346-8919-49c4-affa-d87616ed3df5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I\u2019ve been using Git for a long time. My first full-time Developer role in 2010 was working on an in-house team and that project used Git as it\u2019s version control system.<\/p>\n\n<p>I remember typing commands into an Ubuntu terminal and trying to wrap my head around the process of adding and staging files, (sometimes) pulling, and then pushing to a remote. I think the remote was a simple bare repository on a server, so there was no UI like there is in GitHub and similar tools today.<\/p>\n\n<p>In fact, GitHub only started two years earlier in 2008, and GitLab wasn\u2019t around until 2014.<\/p>\n\n<p>Looking back, my introduction to Git as a Junior Developer wasn't easy and I remember starting to get frustrated until it eventually \"clicked\" and made sense.<\/p>\n\n<p>I don't remember if there were GUIs at that time (I remember using gitk but I can't think when), but having a tool like GitHub where I could see the code, branches and commits, would probably have been helpful with my initial learning.<\/p>\n\n<p>Whilst working locally, I've tried some of the desktop GUI tools like Sourcetree, gitkraken and Tower, but I always come back to using Git on the command line.<\/p>\n\n<p>While a Git GUI tool may make it easier to learn Git initially as a Junior Developer, I'd recommend trying to learn the command line too.<\/p>\n\n<p>In my opinion, understanding what\u2019s happening \"under the hood\" when is important working with a GUI - just in case you find yourself unexpectedly having to use the command line. I\u2019ve seen an error in a Git GUI that suggests running commands in the terminal to debug or fix the issue. If you aren't familiar with the terminal commands or what they do, then I'd expect this to be intimidating and confusing.<\/p>\n\n<p>If you're working as part of a team or contributing to an open-source project then the consistency that the command line provides will make it easier when working with colleagues or getting help from project maintainers. You're also learning Git itself rather than a tool that may add it's own terminology or change how Git itself works, also causing confusion.<\/p>\n\n<p>There's a lot of Git functionality and concepts that I wouldn't have explored if I wasn't using the command line and relying on a GUI, such as adding and removing code in chunks using patch mode, using bisect to find when a bug was introduced, worktrees for local code organisation, and understanding merging vs rebasing, interactive and non-interactive rebases, and merge commits and fast-forward merges.<\/p>\n\n<p>Of course, if you prefer to use a GUI and it works for you, then that's fine. Personally, I like to dig deep when learning tools, to know them inside-out and understand how to use them well, and I think that the time that I've spent learning Git and optimising my workflow paid for itself a long time ago.<\/p>\n\n<p>How do you like to use Git? Do you prefer to use the command line or a GUI tool? Reply to this email and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fde61ed0e072a1110a954bab54a9eb1a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json b/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json
index 13782508d..cfeabffee 100644
--- a/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json
+++ b/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How do you define legacy code?<\/p>\n\n<p>Is it code written by previous Developers who worked on the codebase?<\/p>\n\n<p>Is it code you wrote last week or last month?<\/p>\n\n<p>Is it code for features everyone no longer uses?<\/p>\n\n<p>Is it the \"old\" part of the application that no one wants to work on?<\/p>\n\n<p>It is any code that's not nice to work on or difficult to change?<\/p>\n\n<p>Is it code written with different conventions to your current ones or in a different style?<\/p>\n\n<p>Is it any code that doesn't have automated tests or wasn't written with test-driven development?<\/p>\n\n<p>Is it code built with outdated tooling or frameworks (like CSS libraries) that were popular then but have since been replaced by something newer?<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>These are just some of the potential definitions I can think of.<\/p>\n\n<p>The term \"legacy code\" and others, such as \"technical debt\", often mean different things.<\/p>\n\n<p>What's your definition? Reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8a91a1475b9f9764550b81c084c64421",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.25833838-38b9-414d-bca6-de0bf5c2ac28.json b/content/node.25833838-38b9-414d-bca6-de0bf5c2ac28.json
index 2011f33ac..5bf7a3ed4 100644
--- a/content/node.25833838-38b9-414d-bca6-de0bf5c2ac28.json
+++ b/content/node.25833838-38b9-414d-bca6-de0bf5c2ac28.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Here is some code from my website:<\/p>\n\n<p><img src=\"https:\/\/www.oliverdavies.uk\/assets\/images\/talk-count-code.png\" alt=\"A screenshot of the code that calculates the number of talks I've given.\"><\/p>\n\n<p>If you want, you can also <a href=\"https:\/\/raw.githubusercontent.com\/opdavies\/oliverdavies.uk\/main\/source\/_pages\/presentations.md\">view it on GitHub<\/a>.<\/p>\n\n<p>It is business logic responsible for counting the number of talks I've given at different events so I can display it on my Talks page.<\/p>\n\n<p>It starts at zero, loops over each talk, and increments the talk count if the event is the current day or a past date.<\/p>\n\n<p>It's only used in a single place, so the same logic isn't duplicated elsewhere.<\/p>\n\n<p>But it's in the page's Twig template.<\/p>\n\n<p>It has no test coverage.<\/p>\n\n<p>If I need to change or refactor it, I'd need to test it again manually.<\/p>\n\n<p>Don't do this.<\/p>\n\n<h2 id=\"so%2C-what-should-i-do%3F\">So, what should I do?<\/h2>\n\n<p>It's OK to put simple presentational logic, such as looping over a list or whether to show or hide a value within a template, but not complex business logic.<\/p>\n\n<p>Business logic should be separated and executed elsewhere. The values should be passed to the template to be rendered.<\/p>\n\n<p>This makes the business logic easier to test as you can test the logic itself and determine the value passed to the template is correct without being concerned about the templating engine.<\/p>\n\n<p>In an application, you may need to output a value to a template and a terminal. You'd have one source of truth, such as a Service, Action or Command class that calculates the value before passing it to the appropriate output.<\/p>\n\n<p>Once the logic is separated, you only need to test it once.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>In a previous version of my website, I did this by creating a custom Twig function.<\/p>\n\n<p>It was as simple as adding <code><\/code> to the template.<\/p>\n\n<p>All the logic was moved from the template to my custom extension.<\/p>\n\n<p>The logic was separated.<\/p>\n\n<p>It had tests.<\/p>\n\n<p>This is the approach I'd take to achieve the same result for a client application.<\/p>\n\n<p>For a client, I want to run a test suite and be confident my logic works as expected - now and in the future.<\/p>\n\n<p>For myself, and for calculating something simple, this is fine.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a75b22468e6abeb329819fa5a65c2bc1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json b/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json
index 23e404d17..b0cbbcfd5 100644
--- a/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json
+++ b/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the things that I've done since joining my current team is to implement a standard approach for our commit messages.<\/p>\n\n<p>We're using the <a href=\"https:\/\/www.conventionalcommits.org\">Conventional Commits specification<\/a>, which gives some additional rules to follow when writing commit messages.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code>build(deps): update Drupal to 9.4.5\n\nUpdated Drupal's `drupal\/core-*` packages to 9.4.5.\n\nSee https:\/\/www.drupal.org\/project\/drupal\/releases\/9.4.5.\n\nRefs: #123\n<\/code><\/pre>\n\n<p>We can see that this is a <code>build<\/code> task that relates to our project dependencies, in this example, we're updating Drupal core. We can also see this in the subject line.<\/p>\n\n<p>In the commit body, I add as much information as possible to do with the change and include any relevant links, just in case I need to refer to them again, and the list the names of anyone else who worked with me. I also typically include any ticket numbers or links in the commit footer.<\/p>\n\n<p>So far, I've mostly used the <code>build<\/code>, <code>chore<\/code>, <code>ci<\/code>, <code>docs<\/code> and <code>refactor<\/code> commit types, which are types that are recommended and used by <a href=\"https:\/\/github.com\/angular\/angular\/blob\/22b96b9\/CONTRIBUTING.md#-commit-message-guidelines\">the Angular convention<\/a>.<\/p>\n\n<p>Following this standard means that it's very easy to look at the Git log and see what type of changes are going to be included within a release and, if you're using scopes, which part of the application are affected.<\/p>\n\n<p>Conventional commits also works nicely with something else that we've introduced, which is a CHANGELOG file.<\/p>\n\n<p>There are tools that can generate and update CHANGELOGs automatically from conventional commits, but so far, we've been following the <a href=\"https:\/\/keepachangelog.com\">Keep a Changelog<\/a> format.<\/p>\n\n<p>It's easy to match the commits to the <code>Added<\/code>, <code>Changed<\/code> or <code>Fixed<\/code> types, and although it needs to be updated manually, it's easy to add to the <code>Unreleased<\/code> section of the file and re-organise everything within the appropriate headings as needed as part of a release.<\/p>\n\n<p>What I like about this format is that it's more human-friendly and gives a higher level overview of the changes rather than a reformatted Git log.<\/p>\n\n<p>As we do trunk-based development and continuous integration on our projects, there can be numerous commits related to the same change, so I'd rather only see a single line in the CHANGELOG for each change. This also makes it easier to share the CHANGELOG file with others, and we can still view and grep the Git log to see the individual commits if we need to.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b60d333d6f7149040d0e846c6f1c03b5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json b/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json
index aff1ff837..5d0104d15 100644
--- a/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json
+++ b/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>On several occasions, I've seen companies who build a lot of Drupal projects creating their own in-house [Drupal distribution] for new projects.<\/p>\n\n<p>Whilst this seems like a good idea, the ones I've seen are either not well maintained due to limited time between projects, or they're bloated with features and trying to include too much out of the box.<\/p>\n\n<p>If you maintain an in-house distribution, or are thinking of creating one, my advice is to ensure it's maintained by allocating enough time for this, and to keep it lean and only include the minimum amount of required functionality.<\/p>\n\n<p>Alternatively, maybe keep a template composer.json file to base new projects on instead of a full distribution.<\/p>\n\n<p>That could declare the modules and themes you want to include, without the additional overhead.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2023\/12\/14\/save-time-and-effort-with-drupal-distributions\">drupal distribution<\/a><\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e35818bb9ede99b340e53301552fc08c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json b/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json
index b82177553..267e613a9 100644
--- a/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json
+++ b/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Your first objective when writing software is to make it work by - any means necessary.<\/p>\n\n<p>If you're doing test-driven development, you want to get a failing test to pass as quickly as possible.<\/p>\n\n<p>You want to get your application into a working state, whether that's hard-coding some values, focusing on the happy path implementation, holding off on implementing design patterns, or something else - you just want the code to work, even if it's a \"bad\" solution.<\/p>\n\n<p>Once it's working, you can refactor it into a good solution.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a5dc3593db0a86eecc10e4b173ce6607",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json b/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json
index ec1e0c0dc..3feec9722 100644
--- a/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json
+++ b/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The <a href=\"http:\/\/default\/daily\/2024\/12\/24\/moving-changes\">harder it is to update an environment<\/a>, the less often it will be done and the more out of sync your environments will become.<\/p>\n\n<p>The more out of sync your environments are, the higher the chance there will be bugs or issues when changes are moved between environments.<\/p>\n\n<p>I've had situations where the code I wrote worked for my local database but didn't when moved to staging or production.<\/p>\n\n<p>I worked at one company where my development database was refreshed nightly, so my site was at most one day out of sync with production.<\/p>\n\n<p>I knew my code would work with the latest production data and not only the data from days, weeks or months before.<\/p>\n\n<p>It also meant that I needed to write my changes in an automated and repeatable way so they would be executed on the refreshed database and re-added instead of having to do it manually.<\/p>\n\n<p>How in sync are your environments and how similar to production is the environment you're testing against?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "393d67cc8b24f5363cab347c90d38206",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json b/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json
index fa744dce1..4410f69d4 100644
--- a/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json
+++ b/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">I've written a few earlier emails<\/a> about <code>run<\/code> files - a simple bash file that I add to my projects to simplify or combine common commands that I need to run often.<\/p>\n\n<p>Recently, I've looked at a couple of alternatives to see how they compare.<\/p>\n\n<p>One is very YAML based where all commands are written within a YAML file, and one is very Makefile-like and it does fix some of the confusion and issues that I've made with Makefiles in the past - such as passing arguments to commands, and dealing with <code>.PHONY<\/code>.<\/p>\n\n<p>Whilst I like both of these approaches and that they offer small additional features like auto-completion of task names, after using one of them in a project for a short while, I think that I'm going to stick with the <code>run<\/code> file.<\/p>\n\n<p>The main reason for this is that I like the simplicity of the <code>run<\/code> file, and that it's just a Bash file that contains functions.<\/p>\n\n<p>There were a couple of things that I couldn't quite get to work in one of the other tools, such as setting the TTY value in a Docker Command - which is something that I was able to do with bash within the <code>run<\/code> file. The fact that I can write regular bash and reuse existing knowledge is a big plus rather than having to try to learn another syntax or DSL for another tool.<\/p>\n\n<p>The main reason though is because bash is already installed everywhere. There's no additional tool for Developers to download and install so it keeps the barrier to entry low, and there's no additional dependencies to add to my CI pipeline for it to work.<\/p>\n\n<p>I was able to use one of these other tools in GitHub Actions as someone had already written a workflow for it, and although I could possibly install it via a package manager, just being able to run a bash file in any CI tool was probably the deciding factor to stick with <code>run<\/code> files.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0e6ead78bb287e96b7e18dc6b884ec14",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json b/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json
index 63a45db53..6d93d4815 100644
--- a/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json
+++ b/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How do you know if a commit to your codebase is deployable?<\/p>\n\n<p>What gives you confidence if a change will work once it's released?<\/p>\n\n<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.<\/p>\n\n<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.<\/p>\n\n<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.<\/p>\n\n<p>This can include running automated tests, linting code and running static analysis and anything else you need.<\/p>\n\n<p>This is what determines if the change is deployable.<\/p>\n\n<p>If your CI pipeline passes, the commit is good can be deployed.<\/p>\n\n<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href=\"http:\/\/default\/daily\/2023\/06\/28\/theres-no-value-in-a-broken-ci-pipeline\">there's no value in a broken CI pipeline<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f0ce2f69b9db5c6cc971459f685e5a9c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json b/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json
index 7c62d1468..dd72aee6d 100644
--- a/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json
+++ b/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It's June, so there's only seven months left of security updates for Drupal 7.<\/p>\n\n<p>Originally released in 2011, Drupal 7 is now on version 7.101 and there are still over 315,000 active Drupal 7 websites according to the project page on Drupal.org.<\/p>\n\n<p>Are you stuck on D7 or haven't upgraded yet?<\/p>\n\n<p>I'm interested to know why. Reply to this email and let me know.<\/p>\n\n<p>Will you be migrating to Drupal 10, or something else?<\/p>\n\n<p>If you need help, with <a href=\"http:\/\/default\/drupal-upgrade\">my Drupal 7 upgrade roadmap<\/a>, I'll create an individual plan to upgrade and enjoy easy upgrades to Drupal 11 and beyond!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "18059b58dd6e070d2ab12d72dcee5cd6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.27926937-f426-490f-ac0a-454d9d2def37.json b/content/node.27926937-f426-490f-ac0a-454d9d2def37.json
index dde878648..e407c3eb1 100644
--- a/content/node.27926937-f426-490f-ac0a-454d9d2def37.json
+++ b/content/node.27926937-f426-490f-ac0a-454d9d2def37.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In 2007, I was working in the IT sector in a Desktop Support role but hadn't done any coding professionally.<\/p>\n\n<p>In my spare time, I was a black belt in Tae Kwon-Do and enjoyed training at a few different schools. Because of my IT experience, I was asked if I could create a website for one of the schools - somewhere that we could post information and class times for new starters, as well as news articles and competition results.<\/p>\n\n<p>This would be my introduction to programming.<\/p>\n\n<p>I started learning what I needed to know, starting with HTML and CSS - experimenting with a template that I found online and was able to tweak to match the school's colours.<\/p>\n\n<p>I was able to complete the first version of the website with static HTML pages and CSS but had to manually create a new HTML page for every new news article and edit existing pages manually.<\/p>\n\n<p>I wanted to make it more dynamic, and started to learn about PHP and MySQL from video courses and online forums.<\/p>\n\n<p>After posting a question about some PHP code that I'd written, someone suggested that I look at content management systems - namely Drupal, which was used for that forum (I have <a href=\"https:\/\/twitter.com\/opdavies\/status\/1185456825103241216\">a screenshot of the reply<\/a>). This was a new concept to me as until that point, I'd written everything so far myself whilst learning it.<\/p>\n\n<p>I remember evaluating Drupal alongside some others - rebuilding the same website a few different times, but stuck with Drupal and relaunched it on Drupal 6 and a custom theme that I'd created from the original templates.<\/p>\n\n<p>I signed up for a Drupal.org account, started to do some freelance work for a local web design agency, and built a new website for a local cattery.<\/p>\n\n<p>I started blogging, attending meetups, and when an opportunity to switch careers to software development came along, I applied for and got the job.<\/p>\n\n<p>That job was also using Drupal and, in another email, I'll write more about why I still like and use Drupal years later.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f97cc46c7cd91b966de8bd195077270d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json b/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json
index 94bbf5ea0..552d71b37 100644
--- a/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json
+++ b/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After the topic of Drupalisms and Drupal jargon came up in previous podcast episodes, I was happy to speak with Emma Horrell and Luke McCormick.<\/p>\n\n<p>We discussed the work happening in Drupal and Drupal CMS to de-jargon Drupal, the Drupalisms working group.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/27-drupalisms\">Listen to the episode here<\/a>.<\/p>\n\n<p>If you want to be a guest on the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a>, reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "67a1fcf34fe0816f85b2a62cf901f80c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2885a415-17fb-4374-8070-0be55407af6c.json b/content/node.2885a415-17fb-4374-8070-0be55407af6c.json
index 115ff9127..9e6e0ce17 100644
--- a/content/node.2885a415-17fb-4374-8070-0be55407af6c.json
+++ b/content/node.2885a415-17fb-4374-8070-0be55407af6c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since I posted about <a href=\"http:\/\/default\/daily\/2024\/05\/10\/optimise-for-revertability\">optimising for revertability<\/a>, I've received a few questions about how I avoid merge commits when working with Git.<\/p>\n\n<p>This is an extract from my <code>.config\/git\/.config<\/code> file:<\/p>\n\n<pre><code class=\"ini\">[merge]\n    ff = \"only\"\n\n[pull]\n    ff = \"only\"\n    rebase = true\n<\/code><\/pre>\n\n<p>This changes the behaviour of when I run <code>git pull<\/code> to always include <code>--rebase<\/code> by default and to only allow fast-forward merges and pulls.<\/p>\n\n<p>Only allowing fast-forward merges avoids merge commits as Git can just move the pointer for the branch to the latest commit.<\/p>\n\n<p>If I can't do a fast-forward merge, I need to rebase first to update everything and bring it up to date.<\/p>\n\n<p>Sometimes, when working in team, merge commits will still creep in sometimes and there are situations where you can only create a merge commit.<\/p>\n\n<p>In this situation, I can do <code>git merge --ff<\/code> to allow a merge commit temporarily, but this is the exception instead of the default.<\/p>\n\n<blockquote>\n  <p>Hint: there's a lot more information on the configuration and arguments if you run and read <code>man git-merge<\/code>.<\/p>\n<\/blockquote>\n\n<p>When working with online tools such as GitHub and GitLab, I avoid any options like <code>Squash and merge<\/code> or <code>Create a merge commit<\/code> and will use rebase options, although I've seen where different commit IDs have been generated when merged in the UI, which is why I prefer to do merges locally.<\/p>\n\n<p>Or use <a href=\"http:\/\/default\/daily\/2023\/06\/17\/avoid-git-merge-hell-with-trunk-based-development\">trunk-based development<\/a> and don't work on topic branches at all.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "df04ab02769a8e43f0227ca122c3d48c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json b/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json
index db968cc6e..284bf6cb3 100644
--- a/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json
+++ b/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When you're working on a task - <a href=\"http:\/\/default\/daily\/2024\/08\/31\/make-it-work-then-make-it-good\">whether you're making it work or making it good<\/a>, you can commit your code changes as often as you like.<\/p>\n\n<p>You should definitely commit your changes every time you have a working iteration, even if it's not the complete or final version, or even if the code doesn't pass all the coding standards and static analysis checks.<\/p>\n\n<p>Things can be fixed or improved in subsequent commits.<\/p>\n\n<p>You can amend or squash commits locally so your clean-up and work-in-progress commits are removed before you push your final version to your remote repository.<\/p>\n\n<p>Whilst test-driven development says you should work in small feedback loops and steps, you don't need to push every commit as you wrote them.<\/p>\n\n<p>Until you run <code>git push<\/code>, your commits are yours and yours only.<\/p>\n\n<p>You have the opportunity to tidy up and organise your changes - making your commits easier to review and more likely to be approved in a code review.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a06b7f39d8e65a002d540490d71af34c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json b/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json
index c20836d0c..fc13fd2f2 100644
--- a/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json
+++ b/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Many projects I\u2019ve worked on in the past haven\u2019t had an automated test suite.<\/p>\n\n<p>If you don't or can't write tests for your project for some reason, I'd love it if you could reply to this email or <a href=\"https:\/\/twitter.com\/opdavies\">let me know on Twitter<\/a> and let me know why.<\/p>\n\n<p>I know some of the classic reasons, like \"I don't have time\" and \"My clients won't pay for me to write them\", but I'd like to get some more real-world examples.<\/p>\n\n<p>Then I'll do some follow-up posts to look into and address them.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a791b47a1f23adb15571ee034ecf7976",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json b/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json
index b5d007c18..e40c78dd0 100644
--- a/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json
+++ b/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As I said <a href=\"http:\/\/default\/daily\/2025\/02\/10\/refactoring\">in yesterday's email<\/a>, sometimes you change your mind whilst working on something.<\/p>\n\n<p>Maybe you change your approach and have a commit that supersedes an earlier one, fix a typo, or find a bug and need to revert a commit.<\/p>\n\n<p>If you're pushing your changes to a branch for review, I suggest using <code>git rebase<\/code> to clean up your commits.<\/p>\n\n<p>You can squash the typo fix into the commit that introduced the typo, or remove the original implementation that you later moved away from.<\/p>\n\n<p>Whilst there is an option to squash all the commits when merging, I don't like it and prefer people to tidy their commits before pushing.<\/p>\n\n<p>This means the commits are easier to review and you can keep the original commit history and all the context within the messages instead of a generic <code>Merge commit..<\/code> message.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9244db868e27ad48ece974399c743c82",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json b/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json
index cff40dda6..a756cc18c 100644
--- a/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json
+++ b/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json
@@ -87,6 +87,5 @@
             "processed": "<p>I use NixOS as the Linux distribution on my laptop and home server, and specifically the unstable channel.<\/p><p>This is the \"rolling\" version of NixOS that is continuously updated with the newest and latest packages, compared to the stable releases like 24.11 and 25.05 that are released twice a year.<\/p><p>I don't necessarily do this to get the latest packages.<\/p><p>I do it to keep on top of configuration changes.<\/p><p>I run \"nix flake update\" usually once a week to download the latest updates.<\/p><p>If there are breaking changes or notices since I last updated, I can address them and do it iteratively rather than waiting to do them every six months.<\/p><p>Similar to application deployments, <a href=\"http:\/\/default\/daily\/2023\/05\/14\/releasing-small-changes-often-is-less-risky\">I update early and often<\/a>.<\/p><p>One of the great things about NixOS is, if there is an application that breaks on the unstable branch, I can pin it to the stable release until it works again.<\/p><p>This means I get the benefits of both the rolling and stable approaches.<\/p><p>If you want to see my NixOS configuration, it's <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/nix-config\">publicly available on my Forgejo instance<\/a>.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json b/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json
index 0252f7ebc..41ba928bf 100644
--- a/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json
+++ b/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I started to build a new open-source project - Versa, the versatile command-line tool that standardises common commands across projects.<\/p>\n\n<p>After watching a Twitch streamer building something similar in Rust, I decided to build my take on it and add features I'd need, such as support for local vs Docker-based commands and to run different commands for different projects.<\/p>\n\n<p>For example, <code>versa run<\/code> would need to run different commands for Drupal and Sculpin projects, <code>versa test<\/code> should support different test frameworks for the same language - e.g. PHPUnit, Pest and ParaTest for PHP - and the commands will need to be different in Docker Compose-based projects.<\/p>\n\n<p>Currently, this logic is within my <a href=\"http:\/\/default\/build-configs\">Build Configs<\/a> project but can be moved to Versa.<\/p>\n\n<p>This reduces the complexity within that codebase and means I can open-source it as it's a separate project.<\/p>\n\n<p>At the moment, I've added PHP as the only supported language but I will add JavaScript\/TypeScript support so it supports projects like Fractal.<\/p>\n\n<p>It's still in the prototype phase and includes some initial commands, but the interesting parts will be making it clever.<\/p>\n\n<p>Instead of running <code>versa run --type sculpin<\/code>, I'd like to just do <code>versa run<\/code> and have it determine the type of project automatically.<\/p>\n\n<p><code>versa test<\/code> should be able to determine the testing framework automatically based on what's in the project's <code>composer.json<\/code> file instead of having to specify it.<\/p>\n\n<p>Likewise, for JavaScript, <code>versa install<\/code> should be able to determine if <code>npm<\/code>, <code>yarn<\/code> or <code>pnpm<\/code> is used.<\/p>\n\n<p>That'll be where the more complex code will be added and when I start doing test-driven development - maybe with Behat, which is also something I've been thinking about for Build Configs.<\/p>\n\n<p>Interested? <a href=\"https:\/\/github.com\/opdavies\/versa\">Take a look at the code<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "58a70b657ecf7c7093121dc7fa471790",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.29ab0d54-5f71-4615-b391-164735cada18.json b/content/node.29ab0d54-5f71-4615-b391-164735cada18.json
index 90a84c9e0..82f8be479 100644
--- a/content/node.29ab0d54-5f71-4615-b391-164735cada18.json
+++ b/content/node.29ab0d54-5f71-4615-b391-164735cada18.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week on the Beyond Blocks podcast, I spoke with George Gordon - a graduate from the School of Code who was recently employed in their first Junior Developer role - about their move into tech and software development, their experiences at hack days and meetups, and their introduction to Drupal.<\/p>\n\n<p>I've been a mentor for School of Code for the last few cohorts as well as attending on-site events such as the TechConnect meetup and hack days.<\/p>\n\n<p>I wasn't George's mentor, but I met him at a hackday earlier this year and at a PHP meetup a few months later, so I was happy to have him on the podcast.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/20-george-gordon\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6ec6e1f6816951ce4fdbbb57c251fbf6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json b/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json
index 4013d9e39..b55a93245 100644
--- a/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json
+++ b/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Regardless of whether I was working as part of a team or individually, I used to create a new branch for every change. I'd do the work and merge the feature branch back into the mainline branch - usually either <code>main<\/code> or <code>develop<\/code>.<\/p>\n\n<p>When working on a team, conflicts are common that prevent different changes from being merged, and they're more likely the more time it's been since the last merge and how large the change is.<\/p>\n\n<p>Once, when demoing some in-progress work to a freelance client, I needed to switch branches as the changes were on different feature branches. Doing so broke my local environment and derailed the demo.<\/p>\n\n<h2 id=\"trunk-based-development\">Trunk-based development<\/h2>\n\n<p>These days, I advocate for and prefer to use trunk-based development. Instead of committing changes to feature branches, they are made directly to the mainline branch.<\/p>\n\n<p>As there are no feature branches, there are no merge conflicts when merging into mainline.<\/p>\n\n<p>Although there can still be conflicts when pulling remote changes, trunk-based development pairs nicely with continuous integration - when everyone works in small commits and pushes changes at least once daily. This makes conflicts less likely but also smaller and easier to resolve, and because everyone's changes are not hidden on feature branches, you know they will integrate and work together.<\/p>\n\n<p>It also stops me from breaking my environment during client demos!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6b4f2625c11b6774d4cd0648c3870116",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json b/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json
index 2afef307e..6a24758e8 100644
--- a/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json
+++ b/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As of the 5th of January, Drupal 7 is no longer supported and will receive no new security or compatibility updates.<\/p>\n\n<p>But what if you already have a working Drupal 7 installation?<\/p>\n\n<p>Why should you upgrade?<\/p>\n\n<p>The major reason is security.<\/p>\n\n<p>There will be no new security updates for Drupal 7, so to stay secure and protect your data - especially if you have users or customer data - you should upgrade and continue receiving security updates.<\/p>\n\n<p>Aside from Drupal 7 core, a lot of Drupal 7 modules and themes have been unsupported for some time, so you may have other insecure or unsupported modules that you need to upgrade.<\/p>\n\n<h2 id=\"dependencies\">Dependencies<\/h2>\n\n<p>To keep up to date with the latest versions of PHP and MySQL - the software needed to run Drupal, and other dependencies - you should upgrade to Drupal 10 or 11.<\/p>\n\n<p>Drupal 11 requires PHP 8.3 and MySQL 8.0, so by upgrading, you'll also keep your dependencies up to date, benefit from their security updates, bug fixes and performance improvements.<\/p>\n\n<h2 id=\"developer-experience\">Developer Experience<\/h2>\n\n<p>Newer versions of software are nicer to work with, making it easier to find Developers.<\/p>\n\n<p>PHP 8 can look very different to earlier versions used by Drupal 7, making it nicer and quicker to write - and easier to deliver features.<\/p>\n\n<p>Drupal 7 was probably one of the only projects using SimpleTest for automated tests, whereas the newer versions have used PHPUnit - the defacto PHP testing tool - making automated testing and test-driven development easier and more accessible.<\/p>\n\n<p>Drupal 8 also uses Twig as its templating engine, making theming more powerful and more familiar to front-end developers.<\/p>\n\n<h2 id=\"more-choice\">More Choice<\/h2>\n\n<p>Whilst a lot of the same Drupal modules and themes exist for Drupal 7 and 10, there are a lot of new options available and a lot more in Drupal core, such as Layout Builder, media management and built-in APIs, and a lot more in the new Drupal CMS version.<\/p>\n\n<p>The new versions of Drupal are constantly evolving, adding new features and functionality without you needing to rebuild your application and rewrite your code as you'd have needed to do for previous major version upgrades.<\/p>\n\n<p>Maybe you can replace some of your existing code with some of these new or updated modules.<\/p>\n\n<h2 id=\"anything-else%3F\">Anything Else?<\/h2>\n\n<p>These are some of the reasons I think you should upgrade from Drupal 7, but there are others.<\/p>\n\n<p>If you want to hear more, email me and we can discuss more and, if you're stuck on Drupal 7, I can create a custom roadmap for you to get you moving towards Drupal 11.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2f6f3299f4d4c9892dbdc2a885fcef62",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json b/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json
index 12a534d8d..fa3fbf11f 100644
--- a/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json
+++ b/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json
@@ -87,6 +87,5 @@
             "processed": "<p>This email will be the first in my archive to be powered by Drupal and Tome.<\/p><p>I'm a long-time fan of static site generators and have used Sculpin for several years for my website, but it has slowed down recently - I think because of the number of pages it needs to generate for my email archive pages.<\/p><p>This email will be #821.<\/p><p>I've considered moving to Tome - a static site generator for Drupal - since <a href=\"http:\/\/default\/podcast\/19-sam-mortenson\">recording a podcast episode with Sam Mortenson<\/a> and, after porting across my theme and migrating the emails using the Feeds module, I've updated my Nginx configuration to serve the email archive section to HTML generated by Tome.<\/p><p>The main branch in <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/src\/branch\/main\">my code repository<\/a> now includes the Tome commits and I'll be working my way through <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/src\/branch\/main\/todo.txt\">my task list<\/a> as I continue <a href=\"http:\/\/default\/daily\/2025\/04\/17\/incrementally\">migrating incrementally<\/a> and switching more sections to Tome.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json b/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json
index 8a69f6180..e381496fa 100644
--- a/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json
+++ b/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>For the last few years, I've used Docker and Docker Compose exclusively on all of my projects. When I start a new project or onboard a new client, usually one of the first things that I need to do is get an application running in Docker so that I can work on it.<\/p>\n\n<!-- Since I started programming, I've used a number of different local environments. Starting with WAMP and XAMPP on Windows, MAMP on macOS, Laravel Valet, the Symfony local server, and various open-source Docker-based solutions. -->\n\n<p>I've inherited projects with no environment configuration or documentation at all and I need to start from scratch to get it running. Ideally, each project would have it's local environment configuration in the same Git repository as the application code.<\/p>\n\n<p>For my own projects, these days I prefer to use Docker and Docker Compose - creating my own Dockerfiles for each project so that the correct dependencies are present and the required build steps are executed, as well as acting as documentation.<\/p>\n\n<p>It's lean as the environment is built specifically for each project, and easy to configure using Docker and Docker Compose directly using native patterns such as override files, environment variables and interpolation, and multi-stage builds.<\/p>\n\n<p>The configuration can be as simple or complicated as it needs to be for each project rather than using \"a one size fits all\" approach. If I'm working with Drupal, Fractal, Vue.js, a PHP library, a Go command line tool, or something else entirely, I can use the most appropriate starting point.<\/p>\n\n<p>As well as local developments, it's easy to use Docker and Docker Compose in CI environments with tools like GitHub Actions and Bitbucket Pipelines. They will either be present by default or will be easy to install, and it's simple to run a <code>docker-compose build<\/code> or <code>docker-compose run<\/code> command within a pipeline to check that the project builds correctly and to execute tasks such as automated tests or static analysis.<\/p>\n\n<p>As well as using it for projects, Docker has been useful for me in other situations where I need to run small tools such as rst2pdf for generating presentation slides, and ADR Tools for working with architectural decision records.<\/p>\n\n<p>For some situations like an open-source contribution day, using an off-the-shelf solution would probably be a better option, and some teams will have their own preferences, but I prefer to use Docker and Docker Compose when I can.<\/p>\n\n<p>Personally, I like to invest time into learning tools that provide reusable knowledge, such as Docker and Docker Compose. I'd prefer to spend time learning something, even if it may take longer compared to other tools, if it's going to give me a return on that investment in the medium- to long-term.<\/p>\n\n<p>For some examples of how I work with Docker and Docker Compose, you can <a href=\"https:\/\/github.com\/opdavies?tab=repositories&amp;q=docker\">see my public GitHub repositories<\/a> and how things are put together there.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "87cacdc5c22db3ecc6f35586d0a72902",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json b/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json
index 95ec8a84c..da0ea5cf8 100644
--- a/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json
+++ b/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal 7, first released in January 2011, is now on version 7.97.<\/p>\n\n<p>As things stand, it's supported until November 2023, which makes me wonder whether we'll see the first version of Drupal to get 100 releases.<\/p>\n\n<p>It was originally supposed to be end-of-life in November 2022, I also wonder if it'll be extended again and whether it should be.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f39decae02bf9939850675018c7bda4b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json b/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json
index 4ea4bc22f..b220be1a7 100644
--- a/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json
+++ b/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Have you worked on a project where different Developers are developing with different tools or have different versions of packages installed?<\/p>\n\n<p>In a development team, you want all environments to be consistent - including every Developer's local environment.<\/p>\n\n<p>You want to have every environment to be as close as possible to each other or, ideally, identical.<\/p>\n\n<p>You want everyone to use the same PHP version, the same web and database servers and the same packages installed.<\/p>\n\n<p>Once things start to diverge, bugs can be introduced - such as writing code locally in a newer version of PHP than what's on production.<\/p>\n\n<p>Ideally, you also want everything to be reproducible with locked dependencies and generate the same outcome regardless of when the commands are run.<\/p>\n\n<p>This is one of the main reasons I've <a href=\"http:\/\/default\/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">started to use Nix and devenv for projects<\/a> - because they create environments that are both consistent and reproducible, reducing the chances of dependency mismatches and bugs creeping into my code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c2e765d3c10eb420e55c4f3c307a115f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2b747510-63ea-489c-88de-af7995d94d45.json b/content/node.2b747510-63ea-489c-88de-af7995d94d45.json
index 9482caf15..a49c2f39d 100644
--- a/content/node.2b747510-63ea-489c-88de-af7995d94d45.json
+++ b/content/node.2b747510-63ea-489c-88de-af7995d94d45.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Of the three tools I mentioned in yesterday's email - Ansible, Terraform and Pulumi - I mostly use Pulumi these days for writing automation code.<\/p>\n\n<p>Why? As someone who is already familiar with writing code in certain programming languages, I like that I can use those languages to also write automation, avoid learning a domain-specific language, and those existing approaches like functions and classes to make reusable components and resources.<\/p>\n\n<p>I like that it supports a number of languages. I started with TypeScript but since watching a recent episode of the AltF4Stream, I'm looking at Python too. I've written Python before with Fabric and what you can achieve in Pulumi with a small amount of Python code is very impressive compared to other languages like Go and TypeScript.<\/p>\n\n<p>If you prefer those other languages, why not give Pulumi a try with it?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4ebd7a5d82aef0e0b2dc79ae2d389b04",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json b/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json
index 29825ffeb..1ce932317 100644
--- a/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json
+++ b/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I've seen in code is the unclear use of zero when adding limits, such as loading items from a database.<\/p>\n\n<p>In some instances, setting zero will return all items - essentially, an 'unlimited' value in disguise - rather than returning no results, which is what I'd expect.<\/p>\n\n<p>I imagine the code looks something like this:<\/p>\n\n<pre><code class=\"language-php\">if ($limit &gt; 0) {\n  $query-&gt;range(0, $limit);\n}\n<\/code><\/pre>\n\n<p>If <code>$limit<\/code> is greater than one, add it to the query.<\/p>\n\n<p>For me, using <code>0<\/code> as the unlimited value doesn't seem like the best option.<\/p>\n\n<p>I'd prefer to use a <code>null<\/code> value as the default and only add the limit if it's set - i.e. an integer or not null.<\/p>\n\n<p>It means the value could be either an integer or null, but I think the intent of the code is more explicit.<\/p>\n\n<p>This would make the code look like this:<\/p>\n\n<pre><code class=\"language-php\">if (is_int($limit)) {\n  $query-&gt;range(0, $limit);\n}\n<\/code><\/pre>\n\n<p>Whilst this is clearer, it doesn't cover all use cases.<\/p>\n\n<p>Presumably, the limit should only be a positive integer.<\/p>\n\n<p>It wouldn't make sense to set a negative number as the limit or, as the unlimited value is <code>null<\/code>, setting it to zero.<\/p>\n\n<p>This is the end code I'd likely write:<\/p>\n\n<pre><code class=\"language-php\">if (is_int($limit)) {\n  if ($limit &lt; 1) {\n    throw new InvalidArgumentException('A limit must be a positive integer.');\n  }\n\n  $query-&gt;range(0, $limit);\n}\n<\/code><\/pre>\n\n<p>If the limit is not an integer, nothing happens.<\/p>\n\n<p>It throws an Exception if the value is invalid - i.e. less than one.<\/p>\n\n<p>The limit is applied if the limit is greater than or equal to one.<\/p>\n\n<p>While it's more complex as there are more checks to perform and different types in use, I think this is clearer and easier for someone reading or implementing the code to understand what it does and use it correctly.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "19f4733147fd635802fdcc6ed648d534",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json b/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json
index 02051cac6..44ecf7b5a 100644
--- a/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json
+++ b/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I was reading a support request on a public forum.<\/p>\n\n<p>The poster asked a question about a technical issue and explained the problem they were experiencing. I was experiencing the same thing, which is how I found it.<\/p>\n\n<p>A community member responded and suggested a solution.<\/p>\n\n<p>To this, the original poster responded:<\/p>\n\n<blockquote>\n  <p>Not too proud to ask where I [make the change].<\/p>\n<\/blockquote>\n\n<p>The response to this was what caught my attention:<\/p>\n\n<blockquote>\n  <p>No problem. Don't let pride get in the way of productivity.<\/p>\n<\/blockquote>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Don't be afraid to ask questions or say you don't know or understand something.<\/p>\n\n<p>No one knows everything, and there's no such thing as a stupid question.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f1921114d6e52e6b1147419cd0c37c8c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json b/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json
index 286233263..7cfd54c53 100644
--- a/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json
+++ b/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Before <a href=\"http:\/\/default\/daily\/2024\/11\/13\/speaking-at-the-drupal-london-meetup\">my remote talk for the Drupal London meetup<\/a>, I'm updating the usage statistics for <a href=\"https:\/\/www.drupal.org\/project\/override_node_options\">the Override Node Options module<\/a> - one of the modules I maintain on Drupal.org.<\/p>\n\n<p>In my slides for DrupalCamp Belgium, I showed the usage figures from October 2023, which showed 38,096 installations and it being the 173rd most installed module.<\/p>\n\n<p>This week, the number of installations has slightly increased to 38,223.<\/p>\n\n<p>What's interesting is that whilst the number of installations has been consistent, there are a lot less Drupal 7 websites using the module and a lot more Drupal 8+ sites using it.<\/p>\n\n<h2 id=\"october-2023\">October 2023<\/h2>\n\n<ul>\n<li>5.x-1.x: 1<\/li>\n<li>6.x-1.x: 297<\/li>\n<li>7.x-1.x: 13,717<\/li>\n<li>8.x-2.x: 24,081<\/li>\n<li>Total: 38,096<\/li>\n<\/ul>\n\n<h2 id=\"november-2024\">November 2024<\/h2>\n\n<ul>\n<li>5.x-1.x: 4<\/li>\n<li>6.x-1.x: 202<\/li>\n<li>7.x-1.x: 10,429<\/li>\n<li>8.x-2.x: 27,588<\/li>\n<li>Total: 38,223<\/li>\n<\/ul>\n\n<p>Assuming these numbers are correct, this makes me feel very positive and happy about the adoption of newer versions of Drupal and that people are upgrading their D7 websites to Drupal 10 or 11.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cd0913ec770f5778cd0c8fc66aca2797",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json b/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json
index d3a0820b0..d07fd95f8 100644
--- a/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json
+++ b/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I received the first \"Automated Drupal 11 compatibility fixes\" email from the Rector-powered Project Update Bot.<\/p>\n\n<p>It was for the <a href=\"https:\/\/www.drupal.org\/project\/feature_toggle_twig\">Feature Toggle Twig module<\/a> that adds a <code>featureIsEnabled()<\/code> function to Twig to check if a feature toggle is enabled.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"language-twig\">{% if featureIsEnabled('foo') %}\n  {# ... #}\n{% endif %}\n<\/code><\/pre>\n\n<h2 id=\"what-changes-were-needed%3F\">What Changes Were Needed?<\/h2>\n\n<p>The only change needed to make the module Drupal 11 compatible was updating the <code>core_version_requirement<\/code> to <code>^10 || ^11<\/code> - allowing the module to support Drupal 10 and 11 at the same time as it uses no deprecated code.<\/p>\n\n<p>That's a great thing about modern Drupal compared to legacy versions - no major changes or rewrites to support a new major version!<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the Thing<\/h2>\n\n<p>I thought this was a great initiative in previous versions and I'm glad to see it again for Drupal 11, and it's great that it's being done with time before the Drupal 11 release as it gives maintainers the time to update their projects so as many modules as possible will be Drupal 11-compatible when it's released.<\/p>\n\n<p>I look forward to getting more of these emails for my <a href=\"http:\/\/default\/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">other contributed projects on Drupal.org<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "31597e09d4634a2345186aa8fe52bac9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json b/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json
index 91d195c61..ec9a5f23e 100644
--- a/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json
+++ b/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You work on feature or bug fix.<\/p>\n\n<p>It gets tested manually by you, a tester, and the person who requested the feature or reported the bug.<\/p>\n\n<p>It may get tested on multiple environments.<\/p>\n\n<p>It passes and it moved to production.<\/p>\n\n<p>But now it's live, it's not tested again.<\/p>\n\n<p>Although it works now, there's no guarantee it's not broken or regressed by subsequent changes.<\/p>\n\n<p>It's definitely not tested manually before every future release.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Automated testing offers repeatability.<\/p>\n\n<p>The tests pass, so the functionality works when you wrote it, and you can re-check it by re-running the test.<\/p>\n\n<p>The test suite can be run by Developers whilst working on other changes, before code review and before deployments.<\/p>\n\n<p>The test suite can be run automatically in a CI pipeline for every change that's pushed, and you'll know your change not only worked at the time but will continue to work.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b0878912a8e161c77d109a47fd2b797b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json b/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json
index c154c083a..4e4c51bcd 100644
--- a/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json
+++ b/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday's email was about a proof-of-concept application that I\u2019d quickly built to validate an idea and explore some initial approaches.<\/p>\n\n<p>Today, I\u2019ve been working on a client project that I\u2019ve improved and maintained for a few years.<\/p>\n\n<p>When I started working with this client, they had one website, built with Drupal 7 and Drupal Commerce. Now, there are x websites using the same codebase due to Drupal\u2019s multi-site functionality.<\/p>\n\n<p>My main task for the last few months has been to get one of their sites onto Drupal 9 (which I did, it went live in October).<\/p>\n\n<p>This first site was the \"minimum viable product\" (MVP) - the least amount of functionality required to make it releasable to customers. This is different to a proof of concept which is to validate the idea and start a conversation about requirements and scope - where we define the MVP.<\/p>\n\n<p>For example, there is the ability to create products and product variations from a CSV file. It loads the file from disk and creates the products, but it doesn't update a product variation if a row with an existing SKU is changed, or disable the variation if a row is removed from the file. There is no admin UI for the client to upload a file - the only file that it'll use is the one that's path is hard-coded within the module.<\/p>\n\n<p>There are user stories for this, but we decided that we didn't need it for the initial launch and that we were happy to take on some technical debt, knowing that we can address it later when the original solutions are no longer sufficient.<\/p>\n\n<p>Now the minimum viable solution has been released, we can continue to iterate and enhance it based on customers' feedback, add more functionality, and address the technical debt as needed and as requirements require us to do so.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f44966eb1681af53eb81ff390ccadd27",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json b/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json
index d1e6dddc4..cd0163f98 100644
--- a/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json
+++ b/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I listened to a podcast episode recently which talked about monorepos - i.e. code repositories that contain multiple project codebases rather than a single repository for each codebase - and this got me thinking about whether I should be using these more.<\/p>\n\n<p>It's something that I've been trialling recently in my <a href=\"https:\/\/github.com\/opdavies\/docker-examples\">Docker examples<\/a> and <a href=\"https:\/\/github.com\/OliverDaviesLtd\/docker-images\">Docker images<\/a> repositories, where one repository contains and builds multiple Docker images.<\/p>\n\n<p>I'm not suggesting that I put all of my client projects into one repository, but at least combining the different parts of the same project into the same repository.<\/p>\n\n<p>For example, I'm working for one client on their current Drupal 7 websites whilst developing the new Drupal 9 versions, which are currently in two separate repositories. I'm also developing an embeddable Vue.js application as part of the Drupal 9 website, and using Fractal as a component library. These are also in their own repositories.<\/p>\n\n<p>Using a monorepo approach, all of these projects would be in the same repository.<\/p>\n\n<p>I can see advantages to being able to see cross-project changes in the same place - such as an API change in Drupal that needs a update to be made in Vue.js, or vice-versa - rather than needing to look at separate repositories. This could also make versioning easier as everything will be stored and tagged inside the same repository.<\/p>\n\n<p>Each project has it's own CI pipeline, so it would require some changes where I set a specific pipeline to run only when a directory is changed.<\/p>\n\n<p>I see how deployments may be tricker if I need to push an update within a directory to another Git repository, which makes me wonder if I'll need to look into using subtree splits to create separate deployment repositories - similar to how the Symfony project has one main repository and then each component split into its own repository.<\/p>\n\n<p>I'll keep trialling it in my open-source projects and maybe test it with some client projects, but if you have experience with monorepos that you'd like to share, then please reply to this email - I'd love to hear about it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6863b2793bb9008b2672513b2cf9f503",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json b/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json
index ee2f32ce8..e4777b19c 100644
--- a/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json
+++ b/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/08\/16\/what-are-err--req-and-res\">Whilst mentoring at the School of Code Hackathon<\/a>, something the team and I discussed was documentation and documenting any decisions we made about the approaches they were taking, the techologies to use, etc.<\/p>\n\n<p>We kept it simple by adding this to a README file, but I also mentioned <a href=\"http:\/\/default\/daily\/2022\/09\/23\/adrs-technical-design-documents\">ADRs and technical decision documents<\/a> and how they can be written in Markdown and stored alongside the code in the same repository.<\/p>\n\n<p>Another approach to documentation that I like is to create diagrams and flow charts.<\/p>\n\n<p>I've used various tools to do this, but recently, I've started to use <a href=\"https:\/\/github.com\/mermaid-js\/mermaid\">Mermaid<\/a>, which is a Markdown-like syntax to generate charts and diagrams.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>There are online tools to do this, but there's also <code>mmdc<\/code> command-line tool that generates diagrams locally.<\/p>\n\n<p>This means that I can easily generate diagrams and store in the codebase too, and have them version-controlled so I can see the history as they evolve during the project.<\/p>\n\n<h2 id=\"want-an-example%3F\">Want an example?<\/h2>\n\n<p><a href=\"https:\/\/github.com\/opdavies\/build-configs\/blob\/f02fce7ff5b5cff202ec8b893a4b3c7e7c56f3c4\/docs\/diagram.mmd\">Here's one I did for the Build Configs tool<\/a>, which I recently open-sourced, and that GitHub renders by default (you can click the 'Code' tab to see the code for the chart).<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1acf10e20cf336c87647e51e764cdd12",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json b/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json
index 3a2bd390d..3a43cbe8b 100644
--- a/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json
+++ b/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This is a quote from a presentation by Diego Aguiar at SymfonyCon that I saw from <a href=\"https:\/\/twitter.com\/SymfonyCasts\/status\/1593551105471938560?t=A8wnRUa0tLbb2q5qLhcQnA\">a tweet from SymfonyCasts<\/a>.<\/p>\n\n<p>I haven't seen the rest of the presentation, but I liked this quote and the idea of continuously improving a codebase using automated tests.<\/p>\n\n<p>The talk was titled \"Advanced Test Driven Development\" so I assume that it was focused on ensuring that new functionality also has accompanying tests but it could also apply to existing code.<\/p>\n\n<p>A lot of existing code that I've worked on wasn't covered by tests, so going back and writing tests for that code would be beneficial too - even if it's only one test a day. It would help to prevent and uncover existing bugs, enable the code to be refactored and changed without introducing regressions, and make the codebase more maintainable.<\/p>\n\n<p>Small changes over time add up.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "53ec3852bd16e9152d04d6bd43553d18",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json b/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json
index 5faf98acd..f982fa9b0 100644
--- a/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json
+++ b/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Due to an local outage, I've had no broadband connection and been mostly offline for the last few days.<\/p>\n\n<p>The only connection I've had is a weak 4G signal from my mobile phone that I've been able to tether from to check emails, etc.<\/p>\n\n<p>But this is slow and I struggled to load the majority of websites.<\/p>\n\n<p>Some would take a number of seconds or minutes to load, or fail.<\/p>\n\n<p>As websites and applications develop and grow, it's important to try and keep your codebase as lean and performant as possible.<\/p>\n\n<p>You never know what connection people will be using your code from.<\/p>\n\n<p>What if their broadband goes down or they're in an area with a poor mobile signal?<\/p>\n\n<p>They may not be able to download your large CSS or JS file, or execute the unoptimised database query.<\/p>\n\n<p>You can't assume everyone will be using a high speed Internet connection, so avoid feature bloat, optimise for performance and keep things small and fast.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f6c37d9d9fa156de34d1f69cd5c937cc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json b/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json
index 0b747815f..31651b11b 100644
--- a/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json
+++ b/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the most recent episode of the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a>, I spoke with <a href=\"https:\/\/mortenson.coffee\">Sam Mortenson<\/a> about Single File Components in Drupal as well as building static Drupal websites with Tome.<\/p>\n\n<p>As a Drupal Specialist who works with other technologies including Vue.js, Symfony and Sculpin, it was great to discuss and learn more about both topics.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/19-sam-mortenson\">Listen to the episode now<\/a>.<\/p>\n\n<p>Also, prior to releasing this episode, the total downloads for the podcast are almost at 1,000. Thank you to all the previous guests and everyone who listens to the podcast!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5c9c6d0aa35f183dfbf3569302fc4c45",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json b/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json
index d505527a4..3b52887de 100644
--- a/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json
+++ b/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/10\/19\/phpunit-or-pest\">Whether you prefer PHPUnit or Pest PHP<\/a>, or if you're coding in a different language, it's important to have automated tests - especially before you refactor any code.<\/p>\n\n<p>Before you refactor, you want to have passing tests that you're confident cover all the required functionality.<\/p>\n\n<p>When you finish refactoring, the tests should still pass.<\/p>\n\n<p>Then you know the functionality is the same and the code still works after it's been refactored.<\/p>\n\n<p>If you don't have tests, how do you know everything still works, or how likely are you to do the refactor at all?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fb957020708c21d55d5d99c008e1797b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json b/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json
index 8d867fef3..23697d9b1 100644
--- a/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json
+++ b/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Imagine having a team member who tests each feature before every deployment, reviews the code to ensure its style is consistent, runs quality checks like linting and static analysis, and checks for insecure dependencies.<\/p>\n\n<p>If those checks all pass, they automatically deploy the changes and make them live or update a pre-production environment.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>A CI pipeline can do that. Automatically. For every commit and change to your codebase.<\/p>\n\n<p>Having a CI pipeline is like having an additional team member and one who's always ready and waiting for someone to push a change to test.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3276725453a049753043e098fb26dc65",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json b/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json
index 964216016..c5ecd97ca 100644
--- a/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json
+++ b/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Imagine you've made a commit and want to undo it, or a particular commit is causing issues in production and you want to roll it back.<\/p>\n\n<p>Instead of having to change it back manually, <code>git revert<\/code> can do it for you.<\/p>\n\n<p>You specify the commit SHA you want to revert and Git will automatically try and revert that commit.<\/p>\n\n<p>It creates its own commit message which includes the original commit message and <a href=\"http:\/\/default\/daily\/2024\/05\/20\/referencing-other-commits-in-commit-messages\">the reverted commit SHA<\/a>, so you can easily find or navigate to the original commit.<\/p>\n\n<p>For example:<\/p>\n\n<blockquote>\n  <p>Revert \"Sort talks only by the event date\"<\/p>\n  \n  <p>This reverts commit cbd1417b24a608df8b451a3ab5c9f888de41e758.<\/p>\n<\/blockquote>\n\n<p>Next time, instead of manually reverting a commit, give <code>git revert<\/code> a try.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3ae42369d30ace581b59bd14ab59566a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json b/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json
index aae63e0d0..d7601b71b 100644
--- a/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json
+++ b/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Add everything and ignore what you don't want, or ignore everything and explicitly add what you need.<\/p>\n\n<p>There are two ways to structure a .gitignore file.<\/p>\n\n<p>The default approach is that all files can be added, and you specify the files and directories you want to ignore.<\/p>\n\n<p>For example, if my <code>.gitignore<\/code> file was this, these two directories would be ignored:<\/p>\n\n<pre><code class=\"language-plain\">vendor\nweb\n<\/code><\/pre>\n\n<p>The other approach is to ignore everything and unignore the things to add. For example:<\/p>\n\n<pre><code class=\"language-plain\">*\n!build.yaml\n!Dockerfile\n!docker-compose.yaml\n!web\/*\/custom\n<\/code><\/pre>\n\n<p>Both approaches work and are regularly used.<\/p>\n\n<p>Which approach do you prefer and why?<\/p>\n\n<p>Reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5b63bfce940fe7e208810bb77d3cd2d6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json b/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json
index 8ef452fa1..cfcde408e 100644
--- a/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json
+++ b/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you've written or seen automated tests in PHP, you'll have seen lines like this:<\/p>\n\n<pre><code class=\"php\">self::assertTrue(FALSE);\n<\/code><\/pre>\n\n<p>But, did you know assertions can be used outside of tests.<\/p>\n\n<p>PHP has an <code>assert()<\/code> function that can be used anywhere.<\/p>\n\n<p>For example, if I had this code:<\/p>\n\n<pre><code class=\"php\">$node = Node::load(1);\n\nassert($node instanceof NodeInterface);\nassert($node-&gt;bundle() === 'page');\n<\/code><\/pre>\n\n<p>I know <code>$node<\/code> is a node with the correct bundle type and I can continue.<\/p>\n\n<p>I've made my assumptions explicit.<\/p>\n\n<p>If <code>$node<\/code> is not the correct type or returns an unexpected bundle, the assertion will fail and an Exception will be thrown.<\/p>\n\n<p>I think this is better than assuming or hoping the values are as you expect, and it also makes the intent of the code much easier to see and understand.<\/p>\n\n<p>If you haven't tried <code>assert()<\/code> before, give it a try.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6be3e710df2ce66a5d47787fde5a3e20",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json b/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json
index 3b9f9671c..2ef2590dc 100644
--- a/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json
+++ b/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Another question that followed my recent Git emails was, \" I assume you use rebase over merge?\"<\/p>\n\n<p>The short answer is \"yes\". I like to keep the history of my repositories clean and simple to read by keeping the logs linear and not full of merge commits.<\/p>\n\n<p>The longer answer is that I do merges, but only fast-forward merges, at least by default.<\/p>\n\n<p>If, when merging, Git can fast-forward my branch to the latest commit without creating a merge commit, it will do so.<\/p>\n\n<p>If not, I can then rebase my changes to make them linear and fast-forwardable. Alternatively, if the commits have already been pushed and cannot be overwritten, I can explicitly allow a non-fast-forward merge in that situation.<\/p>\n\n<p>I have Git configured to work this way as that's how I want it to work, and that configurability is something I like about Git.<\/p>\n\n<p>If you want to see how I have Git configured, my settings are in <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\/blob\/462eff64f227332d58c7c3652eeaa88b692c064d\/lib\/shared\/modules\/git.nix#L95-L135\">my dotfiles repository<\/a> (note this file is written in the Nix language as I use Nix to manage my configuration).<\/p>\n\n<p>If you're working in a team, I'd suggest having a common configuration for everyone and defined rules for how you're going to use Git (branch names, merge or rebase, etc) to avoid inconsistencies.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e5e300294005922421e456824c17e754",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json b/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json
index cdc1ce5e6..7e0df3f14 100644
--- a/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json
+++ b/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Do you go back and proactively refactor code you've previously written?<\/p>\n\n<p>In my experience, once some code is working, it's usually not reviewed again and refactored, and any TODO comments are still there.<\/p>\n\n<p>If code is refactored, it's usually triggered by adding a new feature or fixing a bug that will be difficult or impossible with the existing code - i.e., make the change easy, then make the easy change.<\/p>\n\n<p>Very rarely have I seen code be refactored to make it easier to read or change in the future.<\/p>\n\n<p>Do you proactively refactor code or wait until something forces it to happen?<\/p>\n\n<p>Do you not refactor code at all once it's been written?<\/p>\n\n<p>Reply to this email and let me know which and why.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a062ba3a2fcfeca0edc718bd206fe2b6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json b/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json
index a36e29788..f5fa68780 100644
--- a/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json
+++ b/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tonight was our September meetup for the PHP South Wales user group, where I ran a hands-on session on mob programming.<\/p>\n\n<p>I created <a href=\"https:\/\/speakerdeck.com\/opdavies\/an-introduction-to-mob-programming\">a small slide deck<\/a> before we started a mob session with the group.<\/p>\n\n<p>We worked on the FizzBuzz kata in PHP, using Pest for our automated tests.<\/p>\n\n<p>We followed the Driver and Navigator model, with one person responsible for the typing and interpreting the instructions from the Navigators, and switched roles every ten minutes.<\/p>\n\n<p>You can <a href=\"https:\/\/github.com\/opdavies\/code-katas\/blob\/1da5dd5a79bc7ca083c0c4216fc3b4b0854f623d\/php\/tests\/FizzBuzzTest.php\">see the code that we wrote<\/a> on my code katas GitHub repository.<\/p>\n\n<p>It was a fun experience and nice to code with some people who I hadn't coded with before.<\/p>\n\n<p>We did some code kata sessions during our online meetups which also seemed to go well, so coding nights on katas or personal or open-source projects might be something that we do more of in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0e528eb2f03aa1240b5f28b0ef0f38eb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json b/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json
index a4669fc06..06275224a 100644
--- a/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json
+++ b/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After using my \"build-configs\" tool to generate and manage configuration files for several personal and client Drupal projects for the past few months, I'm offering it as a product to purchase.<\/p>\n\n<p>I can provide an initial Drupal project skeleton built using <code>build-configs<\/code>, and for a recurring monthly amount, ongoing updates and unlimited support via Slack.<\/p>\n\n<p>I can retrofit it to an existing codebase, but as this will be different every time, I'll need more information to give a price.<\/p>\n\n<p>See https:\/\/www.oliverdavies.uk\/build-configs for more information and, as a list subscriber, use the code <code>dailyconfigs<\/code> to get an early-bird discount.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "618399863f1103ba0fb1c30d07467918",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json b/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json
index d65502e11..4d31870e2 100644
--- a/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json
+++ b/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are two things I avoid when merging changes in Git.<\/p>\n\n<p>Merge commits and squashing commits.<\/p>\n\n<p>Both make it hard to revert changes if needed once they've been merged, such as a major bug in production and you quickly need to roll back.<\/p>\n\n<p>Merge commits are difficult to revert and if a commit has been squashed into one larger commit, you can't revert it without also reverting everything else.<\/p>\n\n<p>Working with small, unsquashed commits makes it simple to revert a specific one and only that one.<\/p>\n\n<p>If I need to revert something, I want to be able to do as simply and specifically as possible.<\/p>\n\n<p>Optimise for revertability.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e672c406c3284040f0cc248f0e94010b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.312fd370-dae0-41b9-977f-282fc553e701.json b/content/node.312fd370-dae0-41b9-977f-282fc553e701.json
index 668b0adef..6d34155be 100644
--- a/content/node.312fd370-dae0-41b9-977f-282fc553e701.json
+++ b/content/node.312fd370-dae0-41b9-977f-282fc553e701.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I an the idea to create a reusable template for new Drupal modules, based on how I like to build modules and how I've shown others to do so in my Drupal testing workshop.<\/p>\n\n<p>So I did, and released it for free <a href=\"https:\/\/github.com\/opdavies\/drupal-module-template\">on my GitHub account<\/a>.<\/p>\n\n<p>Like my Tailwind CSS starter theme on Drupal.org, it's not intended to be added as a module directly, but something that can be cloned and used as a base for people's own modules.<\/p>\n\n<p>It includes an example route and Controller that load a basic page, and has a test to ensure that the page exists and loads correctly.<\/p>\n\n<p>The Controller is defined as a service and uses autowiring to automatically inject the its dependencies, the same as in my workshop example code.<\/p>\n\n<p>It's the initial release so it's rough around the edges still. I'll use it tomorrow to create a new module and document the steps to add to the README as well as other pieces of documentation.<\/p>\n\n<p>If you're creating a new Drupal module and try it out, start a discussion on the GitHub repository or <a href=\"https:\/\/twitter.com\/opdavies\">let me know on Twitter<\/a>. If you have questions, create a discussion or just reply to this email and I'll get back to you.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "70de2df26133c67db29db3a24a4e7e6a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json b/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json
index ca3b1083f..1556b5846 100644
--- a/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json
+++ b/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I submitted <a href=\"https:\/\/github.com\/localgovdrupal\/localgov_microsites_project\/pull\/43\">my first change<\/a> to the LocalGov Microsites project.<\/p>\n\n<p>It was a small change - correcting a typo that I spotted within the README file.<\/p>\n\n<p>It's OK to start small, especially when first working on a new codebase.<\/p>\n\n<p>It was a good introduction to the project and the first of what I hope to be numerous contributions to the Microsites distribution and LocalGov Drupal in general.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fd6b39dc43f5f73bcb60ca70e2547173",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json b/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json
index 4093c80eb..40725b5e6 100644
--- a/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json
+++ b/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>While I can't find the original quote, I've heard numerous people describe any code without automated tests as legacy.<\/p>\n\n<p>Legacy code is typically inherited from other Developers and is riskier to work on and harder to change, as there is no guarantee changing one piece of code won't cause breakages elsewhere in the codebase.<\/p>\n\n<p>This is true for code that doesn't have accompanying automated tests, regardless of when it was written.<\/p>\n\n<p>I can release a feature to an environment, and although it may be checked and tested at the time, it likely won't be again for every subsequent release. Automated tests can run automatically for every commit and before every deployment, ensuring the code continues to work and for it to be edited without causing regressions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6264aa9a95fe638fa46104484949a1b4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json b/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json
index 014c44358..a18d32079 100644
--- a/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json
+++ b/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Inspired by some recent podcast guests, I've started writing the first code for a Drupal-based SaaS product that I've been thinking of creating.<\/p>\n\n<p>Here's an early iteration of the first test I wrote:<\/p>\n\n<pre><code class=\"language-php\">public function test_it_creates_a_project_node_from_json(): void {\n  self::assertNull(Node::load(id: 1));\n\n  $this-&gt;installEntitySchema(entity_type_id: 'node');\n  $this-&gt;installConfig(modules: self::$modules);\n\n  $projectData = json_decode(json: self::$projectJson, associative: TRUE);\n  self::assertNotNull($projectData);\n\n  Node::create([\n    'title' =&gt; $projectData['list'][0]['title'],\n    'type' =&gt; 'drupal_project',\n  ])-&gt;save();\n\n  $node = Node::load(id: 1);\n\n  self::assertNotNull($node);\n  self::assertInstanceOf(actual: $node, expected: NodeInterface::class);\n  self::assertSame(actual: $node-&gt;label(), expected: 'Override Node Options');\n\n  self::assertSame(\n    actual: $node-&gt;get('field_drupalorg_node_id')-&gt;getString(),\n    expected: strval(107871),\n  );\n}\n<\/code><\/pre>\n\n<p>It checks that, given some defined JSON data, it will create a node in my database.<\/p>\n\n<p>It confirms no node ID exists when starting, runs some setup setups (this is a Kernel test), decodes the JSON, creates the node and asserts it contains the expected values.<\/p>\n\n<p>There are two things that you may be wondering...<\/p>\n\n<ul>\n<li>Why do you have test setup code that you'll need within the test? Won't you need that for every test?<\/li>\n<li>Why are you creating the node within the test and not somewhere else?<\/li>\n<\/ul>\n\n<p>The answer to both is that this is the first test, and I want to write <strong>as little code as possible for it to pass<\/strong>.<\/p>\n\n<p>When I write the second test, I'll either need to duplicate the setup lines or extract them to a <code>setUp()<\/code> method.<\/p>\n\n<p>I'll also need to refactor the code that creates the node.<\/p>\n\n<p>Once I've written the second test, to get it to pass, I refactored to use Repository, Builder and Action classes.<\/p>\n\n<p>If there's a regression, the test I had will fail, and I could revert to the passing version before reattempting the refactor.<\/p>\n\n<p>With test-driven development, I want to work in small and simple steps and get to green by making the smallest and easiest possible change.<\/p>\n\n<p>When I have a test that forces me to refactor and adopt a more complex approach, I'll do it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d430f601217ebbf8a937cf42e8daac88",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json b/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json
index ad391d185..5a92bfd79 100644
--- a/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json
+++ b/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Do you deploy changes to production on Fridays?<\/p>\n\n<p>Some people don't as they're worried about potential issues occurring over the weekend.<\/p>\n\n<p>When's the last time you did a deployment which caused a issue 24 or 48 hours later?<\/p>\n\n<p>In my experience, most issues are visible immediately or shortly after a deployment and not days later.<\/p>\n\n<p>Deploying on a Friday may not be as risky as you think.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9814fa80db8f88e683db868e11d9d67b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json b/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json
index 7307e27dd..ff26200f7 100644
--- a/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json
+++ b/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently started <a href=\"http:\/\/default\/daily\/2025\/04\/07\/nix-rst2pdf\">using Nix to build my PDF presentation slides<\/a> that <a href=\"http:\/\/default\/presentations\/building-presenting-slide-decks-rst2pdf\">I create with rst2pdf<\/a>.<\/p>\n\n<p>I removed the custom build script that was generating the PDF files and moved that code into a Nix derivation.<\/p>\n\n<p>Now I can run <code>nix build .#test-driven-drupal<\/code> and it will generate the slides for that talk.<\/p>\n\n<p>As well as the files specific to each presentation, I also have a derivation for shared assets that apply to all talks - i.e. the stylesheets and fonts that are embedded within the PDF.<\/p>\n\n<p>The font files were stored in the repository but I wanted to remove them and use the font files available in nixpkgs.<\/p>\n\n<p>After some small changes, <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/talks\/commit\/e24d2df83f04e492151b1a1f4901490ce76ffd45\">I was able to do it<\/a> and remove the font files from my repository.<\/p>\n\n<p>The Inter font is available in nixpkgs, but it downloads an <code>InterVariable.ttf<\/code> font that rst2pdf didn't know how to change the font weight for, so I made my own derivation of the static Inter font based on the releases from GitHub.<\/p>\n\n<p>I'm happy that I was able to achieve this, as my repository is leaner and I'm continuing to find new and interesting uses for Nix in my workflows.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "663165d347672170986b3ba5d0f0ac13",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json b/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json
index 7b23a54ef..e87c6c9e5 100644
--- a/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json
+++ b/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as PHP, JavaScript, HTML, CSS, etc, I write a lot of Bash scripts.<\/p>\n\n<p>From <a href=\"http:\/\/default\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">project-specific run files<\/a> to CI pipelines, Dockerfiles and deployment scripts, Bash is used a lot in the ops side of software development.<\/p>\n\n<p>Today, though, I wrote <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\/blob\/a1ef2d1402c9c607e7a3e4427ce125d0cabeddcd\/lib\/shared\/scripts\/export-video-list.nix#L12-L31\">a small Bash script for my personal laptop<\/a>.<\/p>\n\n<p>I store an archive of video files on an external hard drive of conference talks, courses, tutorials or live streams that I want to keep or rewatch, and found that I've sometimes downloaded the same videos more than once, with the same files on my laptop and hard drive.<\/p>\n\n<p>A few days ago, I was watching a video that I thought I'd save, but wasn't sure if I already had, so this script dumps the contents of my hard drive into a JSON file that I can easily browse or search through to see if I already have a video archived.<\/p>\n\n<p>The script is fairly simple and uses <code>tree<\/code> and <code>jq<\/code> to display and format the data before saving it to a file on my laptop.<\/p>\n\n<p>When I need to update the file, I plug in the hard drive and run it again.<\/p>\n\n<p>A simple problem, and not something related to a particular project, but something I was able to solve with a Bash script.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d8356a3f3c57c5eb0702b65d33904107",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3422a295-b8a9-43a0-9a03-a54d77e52513.json b/content/node.3422a295-b8a9-43a0-9a03-a54d77e52513.json
index 404772450..c0525c6f2 100644
--- a/content/node.3422a295-b8a9-43a0-9a03-a54d77e52513.json
+++ b/content/node.3422a295-b8a9-43a0-9a03-a54d77e52513.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I'm speaking at the newly-restarted PHP Berkshire meetup.<\/p>\n\n<p>Organised by Humand Talent, the same people who now organise PHP Oxford (where I spoke in January), this time I'm <a href=\"http:\/\/default\/presentations\/building-static-websites-sculpin\">speaking about Sculpin<\/a> - the PHP static site generator I use for my website and to publish my <a href=\"https:\/\/zet.oliverdavies.uk\">new Zettlekasten notes<\/a>.<\/p>\n\n<p>I'm looking forward to discussing again why I like static site generators and what benefits they offer.<\/p>\n\n<p>I have some things I want to make sure I mention, so expect a note in my Zettlekasten about that soon, too.<\/p>\n\n<p>If you're interested, <a href=\"https:\/\/phpsw-sculpin-demo.oliverdavies.uk\">here's the demo website<\/a> I did for PHP South West, <a href=\"https:\/\/github.com\/opdavies\/phpsw-sculpin-demo\">along with the code on GitHub<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "622d843638b7ecbce4c0a0e042ea0b2e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json b/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json
index 72c62719b..09a8a1e02 100644
--- a/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json
+++ b/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I said that <a href=\"http:\/\/default\/daily\/2024\/07\/08\/back-to-sass-and-traditional-css\">I'm working on a Sass project with no utility or atomic styles<\/a>.<\/p>\n\n<p>But, the two aren't mutually exclusive.<\/p>\n\n<p>You can do both.<\/p>\n\n<p>You can write your own utility classes, like <code>flex<\/code>, <code>font-bold<\/code> or <code>text-red<\/code> in Sass or plain CSS.<\/p>\n\n<p>You can use a framework like Tailwind CSS, but you don't need to.<\/p>\n\n<p>In some projects, with existing stylesheets and usually other frameworks, you can't add anothe full framework without having unintended consequences.<\/p>\n\n<p>Usually, if I want to introduce utility classes to an existing project, I start by writing my own that are inspired by a framework such as Tailwind CSS and maybe refactor to the framework later once the concept has been introduced and the codebase is able to work with it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c6b94af805606062e0a2afbdef9c24fc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json b/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json
index f43b53254..f2b7661ef 100644
--- a/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json
+++ b/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Spending time to learn and master your tools, whether it's your IDE or text editor, CMS or framework, or something else that you use regularly like Git, spending time to expand on the basics and learn it more thoroughly is an investment in your future.<\/p>\n\n<p>I try to keep up to date with the latest additions and changes to Drupal and the PHP language so that I can be more productive and write better and cleaner code.<\/p>\n\n<p>I invest time to make my development environment and tools work as effectively and efficiently as possible. If I can make it easier and quicker to perform simple tasks like navigating to and creating files, and scaffolding new content within them, that time will be paid back in future time saved.<\/p>\n\n<p>If I find a new plugin, module, theme or tool that will make future tasks easier - even something as easy as commenting out a line or block of code - putting aside some time to investigate and evaluate it and decide if I want to use it is time well spent.<\/p>\n\n<p>As someone said in a video recently, \"you invest time now to buy back time later\".<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0c1e2de02ecb6e43c1e99c96b2fed971",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json b/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json
index 5d5dc08cd..c0e6ac1ac 100644
--- a/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json
+++ b/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It\u2019s already been a month since I started my email list and writing daily emails.<\/p>\n\n<p>Since then, I\u2019ve written emails on various development and workflow-based topics, including Drupal, Git, Docker, Neovim, Ansible and Tailwind CSS.<\/p>\n\n<p>The first email was written on Thursday the 12th of August and after initially wondering whether I should start on the upcoming Monday, or how often to post, I decided to jump in with both feet and wrote the first daily post that day. The first few weren't actually emailed as I waited to see if I could sustain writing a daily post (I was just posting them to my website), but after a few days, I set up the email list and started sending the posts.<\/p>\n\n<p>I can confirm what <a href=\"https:\/\/jonathanstark.com\">Jonathan Stark<\/a> and <a href=\"https:\/\/jhall.io\">Jonathan Hall<\/a> have said - that it's easier to write daily and that you start to see topic ideas everywhere. I started with a list of between 20 and 25 ideas and still have most of them as I've pivoted on a day's topic based on an article or tweet that I saw, some code that I'd written, or some approach that I took.<\/p>\n\n<p>If you're considering starting a daily email list, I'd recommend it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "01eb9599a4993e6a38dff0ff03338270",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json b/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json
index 077c20ceb..df9d2909f 100644
--- a/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json
+++ b/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/04\/10\/resurrecting-the-speakerdeck-field-module\">In Wednesday's email<\/a>, I said I was resurrecting the Speakerdeck Field module, and the same version works on Drupal 8, 9, 10 and 11.<\/p>\n\n<p>How do I know this?<\/p>\n\n<p>One of my favourite PHP libraries is Rector - a tool for upgrading code to the newest versions of PHP or, in this case, Drupal using Drupal Rector.<\/p>\n\n<p>It runs automatically on modules, including Speakerdeck Field, via the Project Upgrade Bot and generates a set of updates to apply.<\/p>\n\n<p>CI pipelines with GitLab CI and a reliable test suite make it much easier to upgrade modules to the latest Drupal version and ensure they still work.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3b4ab476b38477647ebc719045e413e0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json b/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json
index 8c4419cef..07edd4d00 100644
--- a/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json
+++ b/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>On the 24th of April, I'll be attending a LocalGov Drupal Camp in Birmingham, UK.<\/p>\n\n<p>As someone keen to get more involved and contribute more to the project, and who's <a href=\"http:\/\/default\/daily\/2024\/03\/25\/newport-city-council-running-localgov-drupal\">local council recently switched to LocalGov<\/a>, I'm looking forward to the chance to learn and contribute on the day and afterwards.<\/p>\n\n<p>If you want to attend also, there are a few remaining tickets available and you can <a href=\"https:\/\/www.eventbrite.co.uk\/e\/localgov-drupal-camp-2024-tickets-847025314517\">register on Eventbrite<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "aa7f86148acbd8f7d810a7b26d5bc29b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json b/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json
index 6427c08c4..31ee6f194 100644
--- a/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json
+++ b/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In <a href=\"http:\/\/default\/daily\/2022\/09\/14\/simpletest-drupal-test\">Wednesday's email<\/a>, I showed how quick it is to get started writing automated tests for a new Drupal module, starting with a functional test.<\/p>\n\n<p>I prefer the outside-in style (or London approach) of test-driven development, where I start with a the highest-level test that I can for a task. If the task needs me to make a HTTP request, then I\u2019ll use a functional test. If not, I\u2019ll use a kernel (or integration) test.<\/p>\n\n<p>I find that these higher-level types of tests are easier and quicker to set up compared to starting with lower-level unit tests, cover more functionality, and make it easier to refactor.<\/p>\n\n<h2 id=\"an-example\">An example<\/h2>\n\n<p>For example, this <code>Device<\/code> class which is a data transfer object around Drupal's <code>NodeInterface<\/code>. It ensures that the correct type of node is provided, and includes a named constructor and a helper method to retrieve a device's asset ID from a field:<\/p>\n\n<pre><code class=\"language-php\">final class Device {\n\n  private NodeInterface $node;\n\n  public function __construct(NodeInterface $node) {\n    if ($node-&gt;bundle() != 'device') {\n      throw new \\InvalidArgumentException();\n    }\n\n    $this-&gt;node = $node;\n  }\n\n  public function getAssetId(): string {\n    return $this-&gt;node-&gt;get('field_asset_id')-&gt;getString();\n  }\n\n  public static function fromNode(NodeInterface $node): self {\n    return new self($node);\n  }\n\n}\n<\/code><\/pre>\n\n<h2 id=\"testing-getting-the-asset-id-using-a-unit-test\">Testing getting the asset ID using a unit test<\/h2>\n\n<p>As the <code>Node::create()<\/code> method (what I'd normally use to create a node) interacts with the database, I need to create a mock node to wrap with my DTO.<\/p>\n\n<p>I need to specify what value is returned from the <code>bundle()<\/code> method as well as getting the asset ID field value.<\/p>\n\n<p>I need to mock the <code>get()<\/code> method and specify the field name that I'm getting the value for, which also returns it's own mock for <code>FieldItemListInterface<\/code> with a value set for the <code>getString()<\/code> method.<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\npublic function should_return_an_asset_id(): void {\n  \/\/ Arrange.\n  $fieldItemList = $this-&gt;createMock(FieldItemListInterface::class);\n\n  $fieldItemList\n    -&gt;method('getString')\n    -&gt;willReturn('ABC');\n\n  $deviceNode = $this-&gt;createMock(NodeInterface::class);\n\n  $deviceNode\n    -&gt;method('bundle')\n    -&gt;willReturn('device');\n\n  $deviceNode\n    -&gt;method('get')\n    -&gt;with('field_asset_id')\n    -&gt;willReturn($fieldItemList);\n\n  \/\/ Act.\n  $device = Device::fromNode($deviceNode);\n\n  \/\/ Assert.\n  self::assertSame('ABC', $device-&gt;getAssetId());\n}\n<\/code><\/pre>\n\n<p>This is quite a long 'arrange' section for this test, and just be confusing for those new to automated testing.<\/p>\n\n<p>If I was to refactor from using the <code>get()<\/code> and <code>getString()<\/code> methods to a different implementation, it's likely that the test would fail.<\/p>\n\n<h2 id=\"refactoring-to-a-kernel-test\">Refactoring to a kernel test<\/h2>\n\n<p>This is how I could write the same test using a kernel (integration) test:<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\npublic function should_return_an_asset_id(): void {\n  \/\/ Arrange.\n  $node = Node::create([\n    'field_asset_id' =&gt; 'ABC',\n    'type' =&gt; 'device'\n  ]);\n\n  \/\/ Assert.\n  self::assertSame('ABC', Device::fromNode($node)-&gt;getAssetId());\n}\n<\/code><\/pre>\n\n<p>I can create a real <code>Node<\/code> object, pass that to the <code>Device<\/code> DTO, and call the <code>getAssetId()<\/code> method.<\/p>\n\n<p>As I can interact with the database, there's no need to create mocks or define return values.<\/p>\n\n<p>The 'arrange' step is much smaller, and I think that this is easier to read and understand.<\/p>\n\n<h3 id=\"trade-offs\">Trade-offs<\/h3>\n\n<p>Even though the test is cleaner, because there are no mocks there's other setup to do, including having the required configuration available, enabling modules, and installing schemas and configuration as part of the test - and having test-specific modules to store the needed configuration files.<\/p>\n\n<p>Because of this, functional and kernel tests will take more time to run than unit tests, but an outside-in approach could be worth considering, depending on your project and team.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "486689fda2edf70f316d73b2d3cd04a9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json b/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json
index 62bf73750..bfe9fcdbc 100644
--- a/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json
+++ b/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After last night's Pro Tailwind theming workshop, I decided to revisit and refactor some similar code that I'd worked on before.<\/p>\n\n<p>It was a demo for a presentation on utility-first CSS and Tailwind whilst I was at Inviqa.<\/p>\n\n<p>I'd taken one of the components from the website that we'd lauched and rebuilt it - in particular to show how Tailwind could be used for responsive and themeable components.<\/p>\n\n<p><a href=\"https:\/\/play.tailwindcss.com\/Yfmw8O5UNN\">The original version<\/a> was written in Tailwind 1 and used custom CSS with <code>@apply<\/code> rules to include text or background colours to elements based on the theme being used on that page or component.<\/p>\n\n<p>As well as moving it into a Next.js application, <a href=\"https:\/\/github.com\/opdavies\/inviqa-tailwindcss-example\">the new version<\/a> uses techniques covered in Simon's workshop - using CSS custom properties (aka variables) to override the colours, and writing custom plugins to generate the required styles. It doesn't include everything from the workshop, but enough for this refactor.<\/p>\n\n<p>I also moved the <code>flex-basis<\/code> classes into their own standalone plugin and might release that as it's own open-source plugin.<\/p>\n\n<p>I'm working on a client project at the moment which will need switchable themes so I'm looking forward to putting these techniques to use again in the near future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6aba0a6c06896212f2bad2652c917717",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json b/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json
index ab53abe12..bdf8fb2b4 100644
--- a/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json
+++ b/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How often do you see comments like \"This should never happen\" in a software codebase?<\/p>\n\n<p>If that's true, why is it there?<\/p>\n\n<p>If it truly should never happen, the additional code only adds more noise and distracts from the code that is run.<\/p>\n\n<p>You can add a test that checks a method isn't called, but what value does this offer?<\/p>\n\n<p>If it doesn't happen or some code isn't run, remove it and keep it as simple, clean and easy to understand as possible.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1a504b384817d66ba5d480432140f3aa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json b/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json
index 221d81fb9..123a2b113 100644
--- a/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json
+++ b/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>An interesting exercise is to run a tool like <a href=\"https:\/\/github.com\/AlDanial\/cloc\">cloc<\/a> to count the number of lines in your application.<\/p>\n\n<p>It counts the number of files and lines within them, as well as how many lines are blank, comments or code.<\/p>\n\n<p>It's a metric that I like to check occasionally as I like to keep codebases lean and with the minimum amount of code.<\/p>\n\n<p>I don't like to have features that aren't used or <a href=\"http:\/\/default\/daily\/2025\/02\/16\/pre-optimise\">pre-optimised code<\/a> for use cases that may not happen.<\/p>\n\n<p>The more code there is in your application, the problems you could encounter.<\/p>\n\n<p>There are more places for bugs and issues to hide.<\/p>\n\n<p>Keeping the amount of code to a minimum makes it quicker and easier to write, review and release as well as fix any bugs that are found in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b9286b595be8e5830126c8065b86f549",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json b/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json
index 03e3fbae8..adbc5d81c 100644
--- a/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json
+++ b/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json
@@ -87,6 +87,5 @@
             "processed": "<p>Once you've <a href=\"http:\/\/default\/daily\/2025\/05\/18\/how-quickly-can-you-get-back-online\">resolved an issue and restored service<\/a>, what lessons can be learned to ensure the same issue doesn't happen again?<\/p><p>Could the issue have been caught or identified sooner, before it got to production?<\/p><p>Ideally, an issue would be identified in a local environment, in a CI pipeline or a staging environment.<\/p><p>Anything before production, but the sooner, the better.<\/p><p>Can you introduce more tools or automated checks?<\/p><p>PHP in particular has a lot of tools for linting, analysing and testing code, such as PHPStan and PHPUnit.<\/p><p>These can be run locally or automatically within a CI pipeline.<\/p><p>If the pipeline is passing, the code should be deployable.<\/p><p>But, if there is an issue, what needs to be added to the pipeline that would have identified it?<\/p><p>How can you iterate and make your development and deployment processes better and more robust?<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json b/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json
index 94c47404b..af0bdaf5a 100644
--- a/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json
+++ b/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, my daily driver laptop suddenly died.<\/p>\n\n<p>The charging lights are on and the keyboard backlights are on, but there's no display on the internal screen or when I plug it into an external monitor.<\/p>\n\n<p>Today, it's gone into a local computer repair shop so I'm writing this email from a different laptop than normal.<\/p>\n\n<p>The great thing about using NixOS and Home Manager is that all of my laptop's configuration is saved within <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\">my dotfiles repository<\/a> - from the operating system and window manager configuration to the programs I have installed and how they are configured.<\/p>\n\n<p>I was able to get half a laptop (an old one with a broken lid) working with my external monitor and running with an identical configuration very quickly.<\/p>\n\n<p>I didn't need to wonder what programs I had installed or how I configured them. It was all available in my dotfiles.<\/p>\n\n<p>And, because I commit early and often, the code I've been working on recently is all in remote Git repositories and using tools like Nix and Docker, I can get them running again quickly too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a630770a77303507c11aab1e65b36b5e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json b/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json
index 2976a871c..0354377b1 100644
--- a/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json
+++ b/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday's email talked about <a href=\"http:\/\/default\/daily\/2022\/10\/28\/why-write-framework-agnostic-packages\">writing reusable, framework-agnostic packages<\/a> but didn't mention where those packages could be located.<\/p>\n\n<p>They could be kept within a private repository and still have the same benefits, such as re-usability for internal projects, but I like to open-source code as often as I can and make it available publicly to see and use.<\/p>\n\n<p>My preference is to follow an open-source-first workflow, identify which parts of a solution can be open-sourced and create them as open-source libraries or modules from the beginning rather than planning to extract them later. They can then be included within the main project using a dependency manager tool like Composer, npm or Yarn.<\/p>\n\n<p>The eBook integration project that I mentioned was an example of this. I identified which pieces could be open-sourced, set up a public repository and put together an MVP based on that project's requirements. Issues were created for nice-to-have additions that could be added later, and the working version was installed with Composer.<\/p>\n\n<p>There was no need to extract the code from the main project, no need to \"clean it up\" or check that it contained no client information, and I had the full Git history for the project - not just a new history from the point when the code was extracted and open-sourced.<\/p>\n\n<p>I've worked on projects that contained a number of potential open-source components that would be released after project completion, but this didn't always happen - I assume due to time pressures to move on to the next project, a focus on adding new features or avoiding the risk of introducing breakages into the code. If the code had been open-sourced from the beginning, these things wouldn't have been an issue.<\/p>\n\n<p>I've also worked on projects where I've followed an open-source-first approach and released a number of PHP libraries and Drupal modules, including <a href=\"https:\/\/www.drupal.org\/project\/private_message_queue\">Private Message Queue<\/a>, <a href=\"https:\/\/www.drupal.org\/project\/system_user\">System User<\/a>, and <a href=\"https:\/\/www.drupal.org\/project\/null_user\">Null User<\/a> modules. I've also been working on some legacy code recently and started to replace it with a library that I've already open-sourced, even though I'm in the early stages of developing it.<\/p>\n\n<p>As someone who enjoys creating and working on open-source software, I would encourage you to open-source your code if you can and to do so sooner rather than later and not wait until the end of your project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e2137fff0c7d5222b90615f0e322973b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json b/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json
index 7fc8740a0..bbf65a82d 100644
--- a/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json
+++ b/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>For a long time, I've been focused on writing code that complies with defined coding standards, either to pass an automated check from a tool like PHP Code Sniffer (PHPCS) or eslint, or a code review from a team member.<\/p>\n\n<p>Complying with the standards though is something that I've done manually.<\/p>\n\n<p>As well as automated tools for linting the code, there are tools like PHP Code Beautifier and Fixer, and Prettier for formatting the code based on the same standards, which I've started to use more recently.<\/p>\n\n<p>These tools can be run on the command line, VS Code has a \"Format on save\" option, and I can do the same in Neovim using an auto-command that runs after writing a file if an LSP is attached. I typically use a key mapping for this though so I can run it when I need, rather than it running automatically every time a file is saved.<\/p>\n\n<p>One of my concerns with automated code formatting is what to do when working with existing code that doesn't already follow the standards. If I need to make a change to a file, with automated formatting, the rest of the file can change due to formatting being applied when I save my change.<\/p>\n\n<p>I recently introduced a PHPCS step to a CI pipeline for an existing project. I knew that it was going to fail initially, but I was able to see the list of errors. I ran the code formatter on each of the files to fix the errors, committed and pushed the changes, and watched the pipeline run successfully.<\/p>\n\n<p>This meant that I had a commit reformatting all of the affected files, but it was good to combine these together rather than having them separate, and not mixed with any other changes like a new feature or a bug fix.<\/p>\n\n<p>Since doing this, it's been nice when working in this codebase to not have to worry about code style violations, and I can focus on writing the code that I need to, knowing that I can rely on the automated formatting to fix any issues before I commit them.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b89a2eb3b71c7524ba4153e60220af05",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json b/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json
index 5d3e46770..ff2bb8e50 100644
--- a/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json
+++ b/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>For the majority of my software development career, I've worked with version control in a very similar way.<\/p>\n\n<p>There are one or two long-lived branches, usually a combination of <code>develop<\/code>, <code>master<\/code> or <code>main<\/code>, that contain the production version of the code. When starting work on a new feature or bug fix, a new branch is created where the changes are made in isolation, and is submitted for review once complete. This is typically referred to as \"Git Flow\" or \"GitHub Flow\".<\/p>\n\n<p>Whilst those changes are awaiting review, a new task is started and the process is repeated.<\/p>\n\n<h2 id=\"trunk-based-development\">Trunk-based development<\/h2>\n\n<p>Something that I've been practicing and advocating for lately is trunk-based development, where there's only one branch that everyone works on, and commits and pushes to instead of creating separate per-task branches.<\/p>\n\n<p>Even on a client project where I was the only Developer, I was used to creating per-task branches and I can recall when trying to demo two features to a client and the application broke when switching between branches.<\/p>\n\n<p>The vast majority of the time, whether working individually or on a team, I've found that the per-task branches weren't needed and working on a single branch was easier and simpler.<\/p>\n\n<p>There are still occassions when a temporary branch is needed, but in general, all changes are made to the single branch.<\/p>\n\n<p>Trunk-based development ties in nicely with the continuous integration approach, where everyone commits and pushes their work at least once a day - ideally, multiple times a day. This eliminates long-running feature or bug fix branches that get out of sync with the main branch as well as conflicting with each other.<\/p>\n\n<p>It seemed scary to begin with, having been used to per-task branches and asynchronous peer reviews via pull or merge requests, but trunk-based development has made things simpler and encourages other best practices such as pair and mob programming. having a good CI pipeline to identify regressions, using feature flags to separate code deployments from feature releases, and frequent code integration and deployment via continuous commits and pushes.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5297a15011e2b7e487d8a29171c25b19",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json b/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json
index ee435f7a3..5111bf53b 100644
--- a/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json
+++ b/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In most cases, clients don't care which CMS, framework, CSS library or design patterns you use. Clients are focused on the business value that those tools can provide, such as increasing traffic or conversion rate to increase revenue or awareness.<\/p>\n\n<p>Improving the load speed of a page is good, but what business value does that offer? Are customers more likely to make a purchase if the page is faster?<\/p>\n\n<p>If you can build the same page with different CMSes or frameworks, and style it in the same way with different CSS libraries, is there a business case for one over the other, such as better maintainability or a quicker time to launch the application?<\/p>\n\n<p>Can you ship a simple MVP sooner, and refactor to use design patterns later?<\/p>\n\n<p>Instead of focusing on technologies, tools and strategies, focus on the benefits and business value they can offer.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9d8842c7057445df7a5341831b17c570",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json b/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json
index efac4a2fb..3268584f4 100644
--- a/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json
+++ b/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I wrote a test whilst fixing a bug in some legacy custom Drupal code.<\/p>\n\n<p>The code is for a custom block, which can be configured using user-defined settings - including a link URL.<\/p>\n\n<p>In this case, if the link was null (one hadn't been provided), the link was generated to the home page instead of the desired destination.<\/p>\n\n<h2 id=\"my-first-attempt\">My first attempt<\/h2>\n\n<p>There was a combination of settings needed to replicate the bug, such as the current site language, the node type the block was placed on and, of course, an empty link URL.<\/p>\n\n<p>Because the block uses the current route to get the current node, my first attempt to test this was to use a browser\/functional test.<\/p>\n\n<p>That failed quickly after having to enable various other custom modules due to dependencies and to add and configure unrelated configuration settings.<\/p>\n\n<h2 id=\"my-second-attempt\">My second attempt<\/h2>\n\n<p>My second attempt used kernel\/integration tests, but as there's no <code>setParameter()<\/code> method on the route matcher I could use in the test, I'd need to rely on mocking.<\/p>\n\n<p>In a unit test, everything needs to be mocked, but a kernel test allows me to be more selective, only mock what I need, and use the real services for everything else - a.k.a. partial mocking.<\/p>\n\n<h2 id=\"the-result\">The result<\/h2>\n\n<p>I replicated the bug by setting the default and current languages, creating a mock language manager, creating a node of the required type and returning it from a mocked route match.<\/p>\n\n<p>Everything else remained the same.<\/p>\n\n<p>Then, I fixed the bug and used a data provider to provide different variables into the test so each use case was covered.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The whole test file is 129 lines and would have been much more if I'd had to replicate all the configuration in a functional test or mock everything in a unit test.<\/p>\n\n<p>An integration test with partial mocking was ideal in this case, as it gave me the most flexibility to test what I needed whilst keeping the code simple.<\/p>\n\n<p>Whilst I'm aware of over-using mocks, this was an ideal situation to use them.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f5ae32e6a60dafd8afa4ab8aa2073638",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json b/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json
index 87e76d1b4..90d645cbf 100644
--- a/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json
+++ b/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Another reason I like static websites is that they're easy and quick to deploy.<\/p>\n\n<p>Whether you use write each HTML file by hand or <a href=\"http:\/\/default\/daily\/2025\/03\/12\/easy\">use a static site generator<\/a>, a simple Web server like Caddy, Nginx or Apache can load and serve your website for everyone to see.<\/p>\n\n<p>My Sculpin website generates an output_prod directory after I run <code>sculpin generate<\/code> with my deployable files.<\/p>\n\n<p>I manage my own server with NixOS that hosts a number of static websites, such as examples from talks and blog posts.<\/p>\n\n<p>To upload my files onto the server, I just use rsync - a small command line tool to synchronise files between computers.<\/p>\n\n<p>It's a single command to upload the contents of my output_prod directory to the directory on my server.<\/p>\n\n<p>No complex CI pipelines or database migrations.<\/p>\n\n<p>It's fast, simple and minimal.<\/p>\n\n<p>If you prefer to use a service like Netlify or Vercel, they work great for static websites too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2241d99c8a6cb9f5e690ba3e1a835383",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json b/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json
index 23c2fb118..95aa72eb8 100644
--- a/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json
+++ b/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Does your task or project have a deadline for completion?<\/p>\n\n<p>Is there a date that it must be completed by?<\/p>\n\n<p>Or, is your \"deadline\" an arbitrary date that can be moved?<\/p>\n\n<p>If so, you don't have a deadline.<\/p>\n\n<p>You have a goal.<\/p>\n\n<p>Understand and be clear whether you have a fixed deadline or a flexible goal.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "da68f3e7c31ad8f0011576d75e320bd3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json b/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json
index 6e5b2cbdf..a571bc053 100644
--- a/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json
+++ b/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I spent some time refactoring a large test within a client project, splitting it into several smaller tests. The commit removed 169 lines but added 233 lines.<\/p>\n\n<p>So, why did I do this?<\/p>\n\n<p>This test is responsible for testing the creation of products and product variants within Drupal Commerce from a custom CSV file and originally had a very generic name - \"Should create a product and product variations from an array of data\".<\/p>\n\n<p>But it did much more than that:<\/p>\n\n<ol>\n<li>It asserted that there are no initial existing products or product variations.<\/li>\n<li>It ran a product import using some stub data.<\/li>\n<li>It asserted that there are two products, each with two variations.<\/li>\n<li>It asserted that each product has the correct title.<\/li>\n<li>It asserted that each product variation has the correct title.<\/li>\n<li>It asserted that each variation has the correct SKU.<\/li>\n<li>It asserted that each variation has the correct price.<\/li>\n<li>It asserted that each variation has the correct value for 10 product attributes.<\/li>\n<\/ol>\n\n<p>All of this was hidden within a single test.<\/p>\n\n<p>Whilst it was great as the original test name (I usually start with a vague name whilst I'm spiking the first test and until it's clearer to me what it's testing and what the correct name is), what I actually want this test to do is to check that the correct number of products and variations are created.<\/p>\n\n<p>This refactoring task was to split the remaining assertions into their own named tests, after which I had six different tests.<\/p>\n\n<p>This means that each piece of functionality and related assertions are now contained within their own named tests. I can read the test file and see the expected functionality within the test names rather than everything being grouped and hidden within a single vaguely-named test.<\/p>\n\n<p>If an assertion fails, I can easily see in which test the failure occurred.<\/p>\n\n<p>Each test is very simple and only a few lines long - it runs the product import, loads the created variation, and runs the appropriate assertions.<\/p>\n\n<p>It'll be much easier to add new functionality to the importer by adding a new separate test rather than continuously adding to the large original one.<\/p>\n\n<p>Even though there are more lines in the file after the refactoring, most of those are just because of adding the additional test functions. There are only 72 lines of actual test methods, and the reusable steps, such as running the product import as well as custom assertions, are defined as private methods to avoid duplication.<\/p>\n\n<p>In my opinion, this was a good refactor to do, and now was a good time to do it before we get started on the next phase of the project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6626dc792ceb7d83e35859940d8a2c43",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json b/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json
index 80fd5e6b8..fc6ec0b98 100644
--- a/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json
+++ b/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2022\/11\/20\/version-controlled-commented-out-code\">Yesterday's email<\/a> talked about whether commented-out code should be present if your code is version-controlled, but how do you avoid committing it in the first place?<\/p>\n\n<p>You could make sure that you remove everything manually before you stage and commit your changes, or I like to use <code>git add --patch<\/code> (or <code>git add -p<\/code>) to interactively stage my changes, allowing me to select which parts of files I want to include in my commit and ignore anything else. The <code>--patch<\/code> option also works for other commands, including  <code>checkout<\/code> and <code>reset<\/code>.<\/p>\n\n<p>If you've already committed something like some debug code, you can use <code>git commit --amend<\/code> to amend the previous commit before pushing it, or if you have a separate clean-up commit, you can use <code>git rebase --interactive<\/code> and either the squash or fixup options to amend the original commit.<\/p>\n\n<p>If some old code has been removed and you want to find it, you can use <code>git log -S<\/code> with a string to search for, and Git will show a list of commits where the specified string was changed.<\/p>\n\n<p>If instead, you wanted to search for text within the commit message, you can use <code>git log --grep<\/code> with a string like an issue number to see a list of commits with that text in the commit message subject line or body.<\/p>\n\n<p>I hope these tips help keep unwanted code out of your version-control repository.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f2a468fba8e2f7e05ff09b2678031534",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json b/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json
index 7ea5eb012..c2c99cd74 100644
--- a/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json
+++ b/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I did a show-and-tell session with my team where I demonstrated an integration I've been working on for a few months and recently released to production.<\/p>\n\n<p>The simplified workflow is we collate some data, send it to a third-party system for translation, receive the translated file and import the translations into Drupal's translation system.<\/p>\n\n<h2 id=\"where-did-i-start%3F\">Where did I start?<\/h2>\n\n<p>The first thing I did was not to collate the data and generate the file but to send a minimal, hard-coded version of the contents to the third-party system.<\/p>\n\n<p>I'd have started with the code to import the translated strings if I hadn't already done this in an earlier spike.<\/p>\n\n<p>This allowed me to send the file, check the response from the third party and ensure they could work with that file type and my proposed content structure.<\/p>\n\n<p>If needed, I could have changed direction and avoided investing much time. This wouldn't have been the case if I'd left this until the end of the process.<\/p>\n\n<p>I also have a working end-to-end test, and I can send a file and get the response I need.<\/p>\n\n<p>What if I'd written all the code and discovered something wouldn't work?<\/p>\n\n<h2 id=\"what-next%3F\">What next?<\/h2>\n\n<p>Now, I can work backwards and start to make the content dynamic.<\/p>\n\n<p>I can introduce more authentic and complicated data, remove the hard-coded test data, and check that things still work.<\/p>\n\n<p>I still have the quick feedback loop, as I can always send the data to the third-party system and verify things work as I iterate on my implementation.<\/p>\n\n<p>With the main pieces of the puzzle in place, I can continue building and filling in the others.<\/p>\n\n<p>Once I have a complete feature with all the pieces in place, I can refactor as needed.<\/p>\n\n<p>I still have the same finished puzzle - I just built it in a different order.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4f3f3eed089d1a4af0d75429f2731bfe",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3cb7e223-af31-471e-acef-d3d069852841.json b/content/node.3cb7e223-af31-471e-acef-d3d069852841.json
index fc9584481..7754b83f5 100644
--- a/content/node.3cb7e223-af31-471e-acef-d3d069852841.json
+++ b/content/node.3cb7e223-af31-471e-acef-d3d069852841.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whilst writing <a href=\"http:\/\/default\/daily\/2024\/06\/07\/not-invented-here\">yesterday's email<\/a> about \"not invented here\", I started thinking about how Drupal's timeline (which was created 23 years ago) compares to some of the other similar or related projects.<\/p>\n\n<p>Here's a list of project release dates from ChatGPT, which seem correct to me at a glance:<\/p>\n\n<ul>\n<li>Drupal: January 15, 2001.<\/li>\n<li>Git: April 7, 2005.<\/li>\n<li>Symfony 1: October 22, 2005.<\/li>\n<li>GitHub and Bitbucket: 2008.<\/li>\n<li>GitLab: October 2011.<\/li>\n<li>Laravel: June 9, 2011.<\/li>\n<li>Drupal 7: January 5, 2011.<\/li>\n<li>Symfony 2: July 28, 2011.<\/li>\n<li>Composer: March 1, 2012.<\/li>\n<li>Drupal 8: November 19, 2015.<\/li>\n<\/ul>\n\n<p>Looking at this list, when speaking about \"not invented here\", a lot of what Drupal would come to use and depend on just didn't exist in its early years.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "26c761c39af062f8236f0e3f605571b4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json b/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json
index e1befa7eb..f6df52389 100644
--- a/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json
+++ b/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently listened to a podcast episode that was discussing if bugs are good for users.<\/p>\n\n<p>It suggested that bugs allowed for engagement between you and the user.<\/p>\n\n<p>If someone reports a bug, you can tell them when you've fixed it. This encourages communication, and the customer will feel more connected to the product.<\/p>\n\n<p>While this may be true, I think that users would prefer applications that just work.<\/p>\n\n<p>If your application has major bugs, they may just go elsewhere. Maybe they won't even report the issue to you.<\/p>\n\n<p>Major bugs can damage your reputation with your users and potential customers, as well as affect potential sales.<\/p>\n\n<p>If you can avoid them to begin with, that's what I'd suggest. That's what tools and processes such as automated testing, test-driven development and static analysis are for.<\/p>\n\n<p>When a user reports it (if they do at all), it could be too late.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "22b1b257bc8acefc91b3f682df2bfa7d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json b/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json
index 2872ce658..a808afb09 100644
--- a/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json
+++ b/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As someone who works on multiple Drupal applications, I know it can be tricky to keep on top of all the available updates.<\/p>\n\n<p>So, I'm building a SaaS project to display all your available updates in one place.<\/p>\n\n<p>If you're a freelancer or work for an agency or any team that works on multiple Drupal applications, this could be useful for you.<\/p>\n\n<p>If this is you, I'm looking for alpha testers to help me test it.<\/p>\n\n<p>If you're interested, reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7efd20a8b45fd58c71c9d69d560899f3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json b/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json
index 77ce6fc5a..06cfab900 100644
--- a/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json
+++ b/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I spent most of today working on some code I wrote for the first phase of a client project a few months ago.<\/p>\n\n<p>The previous version used hard-coded data within a Vue.js application, which was sufficient for the previous criteria and in line with the lean approach we decided to take.<\/p>\n\n<p>It was the simplest thing that worked.<\/p>\n\n<p>A new requirement means that the hard-coded data no longer works, so I need to refactor and enhance the code to work with different configurations. I have a proof of concept of this working using JSON from an API endpoint, but I would also like to use a static JSON file when needed for local development.<\/p>\n\n<p>I experimented with a few different ways to approach this before asking myself, \"What's the simplest possible thing I can do to get this working?\".<\/p>\n\n<p>I already knew that I needed to make a change to the structure of the data, which I was able to do quickly with the hard-coded data that I already had, and whilst a static JSON file would be a nice-to-have, I could quickly move the hard-coded data into the API endpoint that I'd already created and continue building on my proof of concept.<\/p>\n\n<p>The idea of \"What's the simplest thing?\" is something that I use regularly.<\/p>\n\n<p>When teaching or coaching test-driven development, I want to write the smallest failing test and then find the quickest and simplest way to get it to pass - even if it means returning a hard-coded value for now.<\/p>\n\n<p>When working on development tasks, I like to break things down as much as possible and find the smallest thing I can do, commit, and push. This gets the ball rolling, and then I repeat the process.<\/p>\n\n<p>Even when writing an email or blog post, once I start writing, it's much easier to continue once I'm in the flow.<\/p>\n\n<p>Taking the simplest approach and not making assumptions about future requirements or scope means less and more maintainable code, as well as being a productivity hack.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "70b03f1c2962ba75e6f89142c23c6791",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json b/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json
index e9d147d83..f80ce27d5 100644
--- a/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json
+++ b/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm currently working on a project that doesn't use any atomic or utility-first CSS.<\/p>\n\n<p>It uses Sass, which I haven't used for some time, but it has reminded me of some of the reasons I like the utility-first approach to CSS.<\/p>\n\n<h2 id=\"specificity-and-cascading\">Specificity and cascading<\/h2>\n\n<p>With utility styles, there are no specificity or cascading issues as styles are added to each element and provide a local scope.<\/p>\n\n<p>With global styles, your element can be overridden or altered by another part of CSS elsewhere in the stylesheet.<\/p>\n\n<p>I've also had situations where I've had to \"undo\" unwanted styling that was added elsewhere, such as on a hover or focus state.<\/p>\n\n<h2 id=\"easier-to-read-and-understand\">Easier to read and understand<\/h2>\n\n<p>With utility styles, I can read the classes on an element and understand straight away what styles are applied to it and start to make changes - especially when using a framework, such as Tailwind CSS.<\/p>\n\n<p>With generic class names or IDs, I'm not able to do that.<\/p>\n\n<h2 id=\"context-switching\">Context switching<\/h2>\n\n<p>To make changes to an element, once I've found it in the HTML, I then need to find the stylesheet (or stylesheets) that add the styling and switch between the HTML and CSS files as many times as needed.<\/p>\n\n<p>Usually with utility styles, I rarely need to edit the stylesheet and can work almost exclusively in the HTML and not need to switch between files.<\/p>\n\n<h2 id=\"concatination-and-nesting\">Concatination and nesting<\/h2>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/07\/08\/back-to-sass-and-traditional-css\">Something I've avoided with Sass<\/a>, as well as newer versions of CSS, is the over-use of nesting styles, which makes it harder to find them when searching for the correct stylesheet.<\/p>\n\n<p>If there was this CSS:<\/p>\n\n<pre><code class=\"css\">.sidebar {\n  &amp;-wrapper {\n    a {\n      &amp;:hover,\n      &amp;:focus {\n      }\n    }\n  }\n}\n<\/code><\/pre>\n\n<p>If I tried searching for <code>.sidebar-wrapper<\/code> or <code>.sidebar-wrapper a:hover<\/code>, they wouldn't be found and it would take me longer to find it.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>It's taken me a while to get back into this way of working with CSS, but it does remind me <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">why I prefer to use utility styles<\/a> for my own projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "608cb7069f4b0d69aa56c86a6d0e262b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json b/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json
index d8826122c..23905547f 100644
--- a/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json
+++ b/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When starting a new task, find the simplest way to prove the concept.<\/p>\n\n<p>Investigate upfront and evaluate potential approaches.<\/p>\n\n<p>What's the smallest or quickest thing you could do to validate an idea?<\/p>\n\n<p>It could be a small script that you can run and verify something works before moving it to its correct place within your application or creating a first implementation with hard-coded data that you refactor once you've proven the concept.<\/p>\n\n<p>If you can't, you'll know it won't work without investing a large amount of time and you can move on to the next potential approach.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "53531d5906d1f9a7bfd86d494bd38724",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json b/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json
index d5c2ecdd2..27e578f6d 100644
--- a/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json
+++ b/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Shell aliases are a useful way to shorten long or complicated commands or to easily add additional arguments when running commands.<\/p>\n\n<p>Common aliases are I see are <code>gs<\/code> for <code>git status<\/code>, <code>a<\/code> for <code>artisan<\/code> and <code>dr<\/code> for <code>drush<\/code>.<\/p>\n\n<p>I've been experimenting with Zellij for the last day or so, and have written aliases like <code>zl<\/code> for <code>zellij list-sessions<\/code>, but have also added extra arguments such as <code>zellij list-sessions | sort | grep -v EXITED<\/code> to sort the sessions and filter any exited sessions.<\/p>\n\n<p>Running aliases makes it easier and quicker for me to run these commands, and less likely for me to make errors and type incorrectly.<\/p>\n\n<p>The issue with aliases is that you can forget that the underlying commands are if you only type and see <code>gs<\/code> or <code>zl<\/code>.<\/p>\n\n<p>It's also not easy when giving demos or pair or mob programming for others to see and understand the commands that are being run.<\/p>\n\n<p>Instead of aliases, I mostly use abbreviations with zsh-abbr that expand automatically after pressing the space key.<\/p>\n\n<p>That way, I and others get to see and understand the commands being run.<\/p>\n\n<p>I still have some aliases that don't expand but now I use abbreviations as my default approach.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ef19563099602226d685a997087e53be",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json b/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json
index a0ba93216..d082c40f4 100644
--- a/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json
+++ b/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When working with traditional CSS, the first thing you do when you need to style a new page or component is to open a stylesheet and start writing new CSS.<\/p>\n\n<p>Also when editing existing styles, sometimes you'll write new styles to avoid breaking the existing pages in unexpected ways in other parts of the page. This is why I've not seen many projects where the styling is maintained or refactored over time - only added to.<\/p>\n\n<p>By writing new CSS for every new page or component, the size of your stylesheets will continue to grow and be less performant and harder to maintain over time.<\/p>\n\n<p>With utility styles and frameworks like Tailwind CSS, this happens a lot less or sometimes not at all.<\/p>\n\n<p>If you need to use a class like <code>flex<\/code> or <code>grid<\/code> and you already use that in your project, there's no new CSS to add and the stylesheet doesn't grow. Because these type of classes are so specific, they're much more reusable which means less duplication of CSS rules and less CSS in total.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "92a7979f45a6c8ae09c876e6d4bd42ce",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json b/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json
index f5ed3ca14..5e2d031d1 100644
--- a/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json
+++ b/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>CSS usually has a global scope which can make change risky.<\/p>\n\n<p>How do you know that changing CSS in a global stylesheet to fix a bug won't cause more elsewhere?<\/p>\n\n<p>Tailwind CSS and utility classes change CSS to a local scope.<\/p>\n\n<p>You can see what styling is applied to an element by looking at its classes and easily make changes without worrying that it will cause unexpected issues elsewhere.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "641df2822210add8bce07e680ceed39d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json b/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json
index a9c9f1eb5..91562b663 100644
--- a/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json
+++ b/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As I work on various projects, I use several different CI tools, such as GitHub Actions, Bitbucket Pipelines, and GitLab CI, as well as hosting providers that have build and deploy steps.<\/p>\n\n<p>Some only run continuous integration checks, like automated tests and static analysis, some build and push Docker images, and some use Ansible and Ansistrano to deploy the changes to production.<\/p>\n\n<p>Each tool has its configuration file with different settings and formats.<\/p>\n\n<p>Rather than being too tightly coupled to a particular tool, I like to keep things as agnostic as possible and <a href=\"http:\/\/default\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">use a run file<\/a> with separate <code>ci:build<\/code> and <code>ci:deploy<\/code> tasks.<\/p>\n\n<p>This means that all the logic is within the run file rather than the CI tool-specific configuration file, so the file is shorter and cleaner; I can make changes to the CI tasks locally and quickly test changes and iterate, and also, as the logic is within the run file, I can easily switch to a different CI tool if needed without making changes to the tasks themselves.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3fa7aa685c79856ae622fccfd49a503d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.42741272-127f-46fb-b058-172301e5edd1.json b/content/node.42741272-127f-46fb-b058-172301e5edd1.json
index 613897ffd..91d929f40 100644
--- a/content/node.42741272-127f-46fb-b058-172301e5edd1.json
+++ b/content/node.42741272-127f-46fb-b058-172301e5edd1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Good code is not about being easy to write. It's about how easy it is to change.<\/p>\n\n<p>Once you've written some code, how easily and confidently could you change it in the future, either adding new features or fixing a bug?<\/p>\n\n<p>How easily could you refactor the code or remove it altogether if it's no longer needed?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6f729533d71878ba50e24fef55c23dda",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json b/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json
index 3c4428b8f..d7774b64c 100644
--- a/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json
+++ b/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are two parts to a good commit message.<\/p>\n\n<p>The first line summarises the change, but this can be seen by running <code>git diff<\/code> or <code>git show<\/code>.<\/p>\n\n<p>The subsequent lines should describe why the change was needed, including any additional context, alternative approaches that were considered or tried, follow up steps, issues encountered or anything else that it would be useful to read if someone runs <code>git log<\/code> or <code>git blame<\/code> to look at the commit history.<\/p>\n\n<p>If there was an issue with this code in the future, what information would be useful to know?<\/p>\n\n<p>Why did you take this approach over a different one?<\/p>\n\n<p>What error does this commit fix? Include the error message.<\/p>\n\n<p>Who requested the change and why? What information can you include that you wouldn't want to lose if you changed your project management or issue tracking software? Don't just link to the issue or add the ticket number.<\/p>\n\n<p>What other information and context did you know when you made the commit?<\/p>\n\n<p>If anything changes in the future, you can make another commit and repeat the process.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bfe45200bff8e8397ce77077eda3cd7d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json b/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json
index 922ed1aab..ae3e3586f 100644
--- a/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json
+++ b/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few days ago, I said that <a href=\"http:\/\/default\/daily\/2025\/02\/02\/simple\">I still like to use RSS<\/a> to consume a lot of online content.<\/p>\n\n<p>Unfortunately, a lot of websites either don't have RSS or Atom feeds, or they aren't easy to find without viewing the website's source code.<\/p>\n\n<p>The ability for people to publish and easily consume other people's content is a main principle of the open web, instead of relying on other websites and social media.<\/p>\n\n<p>Drupal is one of the projects <a href=\"https:\/\/www.drupal.org\/association\/open-web-manifesto\">that make an open web possible<\/a>.<\/p>\n\n<p>It's easy to create an RSS feed of your articles, events or any other content on your Drupal website for others to consume.<\/p>\n\n<p>I also love that Drupal.org itself does this by publishing RSS feeds for project releases and various other content - not just news or blog posts.<\/p>\n\n<p>Because of this, I can subscribe to the feeds I want from any website that creates them and I can consume it how and when I want.<\/p>\n\n<p>Long live the open web!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "994cf3233994d78c7c19d5d17c52c6f5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json b/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json
index 9613433df..7ec3688ac 100644
--- a/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json
+++ b/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I asked <a href=\"http:\/\/default\/daily\/2024\/05\/26\/is-it-time-to-stop-writing-sass\">if it's time to stop writing Sass<\/a>.<\/p>\n\n<p>If you still use Sass and are writing new styles with Sass, I'd like to know why.<\/p>\n\n<p>Reply to this email and let me know.<\/p>\n\n<p>I'm working on a project and migrating from the existing Sass styles to Tailwind CSS-generated utility classes, but with CSS custom properties (variables) and other Sass-like features now supported by browsers, writing vanilla CSS again is an interesting option.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0ad492a3800d1a39b43b8381b03a167a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json b/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json
index 44da6db9b..1381b3881 100644
--- a/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json
+++ b/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I needed to investigate and fix a bug within some existing code.<\/p>\n\n<p>It's code written some time ago and not by anyone working on the team.<\/p>\n\n<p>The code wasn't very readable, so before I could fix the bug, I needed to figure out what the code was supposed to be doing.<\/p>\n\n<p>I started to write a list of things that would make the code easier to read and understand - no single-letter variable names, reduced levels of indentation and splitting some nested ternary operators to use separate return statements.<\/p>\n\n<p>I also watched a video of a conference talk titled \"Writing code you won't hate tomorrow\", which re-introduced me to Object Callisthenics.<\/p>\n\n<p>They are from \"The ThoughtWorks Anthology\" book and are some steps that include some of the points that I had written:<\/p>\n\n<ol>\n<li>Use only one level of indentation per method.<\/li>\n<li>Don\u2019t use the else keyword.<\/li>\n<li>Wrap all primitives and strings.<\/li>\n<li>Use only one dot per line.<\/li>\n<li>Don\u2019t abbreviate.<\/li>\n<li>Keep all entities small.<\/li>\n<li>Don\u2019t use any classes with more than two instance variables.<\/li>\n<li>Use first-class collections.<\/li>\n<li>Don\u2019t use any getters\/setters\/properties<\/li>\n<\/ol>\n\n<p>As well as the original book, there are numerous blog posts and videos on this topic.<\/p>\n\n<p>Why try some of them on the next code you write and see if it's easier to read and understand?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2753953e3bfd1a1568643626ad56e3cf",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json b/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json
index 834bb54c0..8056da208 100644
--- a/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json
+++ b/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Recently, a steamer said they \"prefer verbosity over abstraction\/confusion\".<\/p>\n\n<p>In that scenario, it was regarding the name of a microservice they were creating. It was long and verbose, but it described what it did.<\/p>\n\n<p>It was clear to anyone working on that project what that service did, now and in the future.<\/p>\n\n<p>I prefer this to shorter, less-descriptive names.<\/p>\n\n<p>I hardly ever create a variable called <code>$x<\/code>, <code>$k<\/code> or <code>$v<\/code>. I only would if it was clear what it meant within its context.<\/p>\n\n<p>I like to write descriptive names for test methods that explain what the test is doing. Even if I start with a vague name, I'll refactor it to make it more specific and clearer.<\/p>\n\n<p>I prefer not to use PHP functions like <code>compact<\/code> and to write it out and avoid the abstraction and any confusion it could cause.<\/p>\n\n<p>I prefer code to be verbose, descriptive and easy to read, understand and change.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9d832e6a96400a2022d179422d39c66a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json b/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json
index 3ea5c8d19..87cc26a66 100644
--- a/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json
+++ b/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you need to integrate your application with a third-party service, don't integrate it directly - even if it has an SDK.<\/p>\n\n<p>Doing so locks you into a single implementation and a single vendor.<\/p>\n\n<p>If you write your own integration layer, it's possible to add multiple implementations, such as different payment gateways, that conform with a single interface.<\/p>\n\n<p>If you need to switch to a different provider or add multiple options, you can without changing the existing code.<\/p>\n\n<p>It also makes it easier to test as you can write a fake implementation and use it for testing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b3ce2b27a1306357903fea42bae79618",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.43c6257e-4064-422d-8075-5ec55861c177.json b/content/node.43c6257e-4064-422d-8075-5ec55861c177.json
index e21d42c30..07626a1e6 100644
--- a/content/node.43c6257e-4064-422d-8075-5ec55861c177.json
+++ b/content/node.43c6257e-4064-422d-8075-5ec55861c177.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week on the Beyond Blocks podcast, I'm joined by Mark Conroy - Director of Development at Annertech to discuss all things front-end development and building something useful in one day.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/11-mark-conroy\">Listen now<\/a><\/p>\n\n<h2 id=\"talking-points\">Talking points<\/h2>\n\n<ul>\n<li>Building better websites faster, including Drupal distributions, such as LocalGov.<\/li>\n<li>What Drupal gives you out of the box and using the right tool for the job.<\/li>\n<li>Drupal migrations and migrating Drupal configuration from a spreadsheet.<\/li>\n<li>Saving time and improving efficiency by standardising base builds with Docksal and Composer.<\/li>\n<li>How to build projects, like the Running Plan Generator, in a day and training for 10Ks and marathons.<\/li>\n<li>Prioritising tasks.<\/li>\n<li>Annertech's development workflow and standardisation by developing on remote servers.<\/li>\n<li>Why you may not need preprocessors and complicated front-end build tools, and reducing complexity using vanilla CSS, JavaScript and web components.<\/li>\n<li>Lowering the barrier to entry to contribute to open-source projects.<\/li>\n<li>Building a design system\/component library with web components.<\/li>\n<li>The Content Access by Path module that was developed for Essex County Council.<\/li>\n<\/ul>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4c926214319ed46035a786ecace696ae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json b/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json
index 482e4dbcb..9a28caa73 100644
--- a/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json
+++ b/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I've resurrected the <a href=\"https:\/\/www.drupal.org\/project\/speakerdeck_field\">Speakerdeck field Drupal module<\/a>.<\/p>\n\n<p>It's a module I wrote in 2017 for the Drupal 8 version of my website to embed Speakerdeck slides on my talk pages.<\/p>\n\n<p>My website now runs on Drupal 10, but the great thing is that the same code that worked for Drupal 8 also works for Drupal 9 and 10.<\/p>\n\n<p>There was no rewrite for each major version, and as I'm not using any deprecated code, the same code works for all the modern versions mentioned, and it looks like it will for Drupal 11, too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "40260e52aebd6f8cd05d453734954342",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json b/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json
index ea15447ca..dab4125e8 100644
--- a/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json
+++ b/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As part of my recent digital simplification, I've started hosting the episodes of the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a> myself.<\/p>\n\n<p>I've always had the podcast pages on my website and used them as the primary pages to redirect people for information about the episodes.<\/p>\n\n<p>I embedded an audio player from a third party service that were hosting the files, but have replaced it with the native HTML audio element.<\/p>\n\n<p>It's simpler, but I like it.<\/p>\n\n<p>My website is built with Sculpin, so I was able to do this easily with Twig by adding the path to the MP3 file to each episode:<\/p>\n\n<pre><code class=\"twig\">&lt;audio controls&gt;\n  &lt;source src=\"http:\/\/default\/files\/bb\/episodes\/%7B%7B%20page.episode_filename%20%7D%7D\" type=\"audio\/mp3\"&gt;\n&lt;\/audio&gt;\n<\/code><\/pre>\n\n<p>This is already live. You can see it on <a href=\"http:\/\/default\/podcast\/25-jess-archer-drush-laravel-prompts\">any of the podcast episode pages<\/a>.<\/p>\n\n<p>The other thing I'm using is the feed that publishes episodes to Spotify,  iTunes, etc.<\/p>\n\n<p>But I have all the information and ability to create this myself.<\/p>\n\n<p>This part is still in development and I'll need to test it before switching to it, but it will mean the feed URL will change and people may need to resubscribe.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Using a hosted service was a great way to get the podcast up and running quickly, but I'm looking forward to having more control over it, even if it involves a little upfront development work.<\/p>\n\n<p>But, it will make it easier to post future episodes as I'll be able to do it all in one place.<\/p>\n\n<p>I have some new guests lined up for 2025, which I'm looking forward to.<\/p>\n\n<p>If you want to be a guest on the podcast or want to make a suggestion for someone I should have on, reply to this email and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a4601bf866ebb0eb1ac20cbe52f0bbcd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json b/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json
index a53d1bffb..3e1408cea 100644
--- a/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json
+++ b/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are three ways to add custom styles to a Tailwind CSS project. As there have been <a href=\"https:\/\/twitter.com\/adamwathan\/status\/1559250403547652097\">some recent tweets<\/a> around one of them - the <code>@apply<\/code> directive - I'd like to look at and give examples for each.<\/p>\n\n<h2 id=\"what-is-%60%40apply%60%3F\">What is <code>@apply<\/code>?<\/h2>\n\n<p><code>@apply<\/code> is a PostCSS directive, provided by Tailwind, to allow re-using it's classes - either when extracting components or overriding third-party styles.<\/p>\n\n<p>The CSS file is the same as if you were writing traditional CSS, but rather than adding declarations to a ruleset, you use the <code>@apply<\/code> directive and specify the Tailwind CSS class names that you want to apply.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"css\">fieldset {\n  @apply bg-primary-dark;\n}\n<\/code><\/pre>\n\n<p>This is a simple example but it's easy to see how this could be used in ways that weren't intended and how edge-cases can be found.<\/p>\n\n<p>Adam said in a another tweet:<\/p>\n\n<blockquote>\n  <p>I estimate that we spend at least $10,000\/month trying to debug extremely edge-case issues people run into by using <code>@apply<\/code> in weird ways.<\/p>\n<\/blockquote>\n\n<h2 id=\"using-the-%60theme%60-function\">Using the <code>theme<\/code> function<\/h2>\n\n<p>As well as <code>@apply<\/code>, Tailwind also provides a <code>theme<\/code> function that you can use in your CSS file. This removes the abstraction of using the class names and adds the ability to retrieve values from the <code>theme<\/code> section of your tailwind.config.js file.<\/p>\n\n<pre><code class=\"css\">fieldset {\n  backgroundColor: theme('colors.primary.dark');\n}\n<\/code><\/pre>\n\n<p>This seems to be the preferred approach over using <code>@apply<\/code>.<\/p>\n\n<h2 id=\"creating-a-custom-plugin\">Creating a custom plugin<\/h2>\n\n<p>The <code>theme<\/code> function is also available if you write a custom Tailwind CSS plugin:<\/p>\n\n<pre><code class=\"javascript\">const plugin = require('tailwindcss\/plugin')\n\nplugin(({ addBase, theme }) =&gt; {\n  addBase({\n    fieldset: {\n      backgroundColor: theme('colors.primary.dark'),\n    }\n  })\n})\n<\/code><\/pre>\n\n<p>This is an approach that I've used for <a href=\"https:\/\/github.com\/opdavies?tab=repositories&amp;q=%23tailwindcss-plugin\">generic, open-source plugins<\/a> but for project-specific styling, I've mostly used <code>@apply<\/code> or the <code>theme<\/code> function.<\/p>\n\n<p>That said, I like the modular architecture of having different custom plugins - especially if they're separated into their own files - and being able to easily toggle plugins by simply adding to or removing from the <code>plugins<\/code> array.<\/p>\n\n<p>I usually don't write many custom styles in a Tailwind project but I think that I'll focus on using the <code>theme<\/code> function going forward, either in a stylesheet or a custom plugin.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6b48ac239501bd0ff52a0f5acaedb81c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json b/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json
index 4a7cb8de4..eef3fc3cc 100644
--- a/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json
+++ b/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Most Drupal projects include writing custom code to add functionality required for that project or that doesn't yet exist.<\/p>\n\n<p>Some of this may be identified as code that could be contributed back to the Drupal community and uploaded to Drupal.org as reusable code for others to use.<\/p>\n\n<p>Usually, this involves \"cleaning up\" the code to make it ready to be open sourced - ensuring it complies with coding standards, follows best practices and doesn't contain any sensitive or project-specific data.<\/p>\n\n<p>Unfortunately, this doesn't always happen as the next project or task is waiting to be started, and the code is never contributed.<\/p>\n\n<p>I like to do contrib-first or contrib-driven development, where the code is open sourced upfront, developed in the open and used on the project as I'm developing it.<\/p>\n\n<p>A common argument to this approach is that it takes too much time.<\/p>\n\n<p>I assume that's because people think I need to cover every use case and situation in the module because I'm open sourcing it.<\/p>\n\n<p>That's not true.<\/p>\n\n<p>When I wrote modules like <a href=\"https:\/\/www.drupal.org\/project\/system_user\">System User<\/a>, <a href=\"https:\/\/www.drupal.org\/project\/null_user\">Null User<\/a> and <a href=\"https:\/\/www.drupal.org\/project\/private_message_queue\">Private Message Queue<\/a>, I wrote the same code I'd have written if I was going to contribute it later - but I didn't need to clean it up afterwards.<\/p>\n\n<p>I didn't need to ensure it didn't contain anything I'd need to remove.<\/p>\n\n<p>It wasn't a big task to open source them as they were already open sourced.<\/p>\n\n<p>If other people want to use the module and need additional features, they could open an issue, submit a patch or create their own patches.<\/p>\n\n<p>Just because code has been open sourced doesn't mean it needs to do everything for everyone.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b44dc92d2bb08665b6bec22b5fda467c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json b/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json
index 60c9724f2..0eecfd6d8 100644
--- a/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json
+++ b/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are a lot of <a href=\"https:\/\/www.drupal.org\/project\/issues\/search?status[]=1&amp;status[]=13&amp;issue_tags_op=%3D&amp;issue_tags=Needs+tests\">open issues on Drupal.org<\/a> that have the \"Needs tests\" label.<\/p>\n\n<p>These could be maintainers leaving themselves reminders to add tests once they've finished spiking out the first version of their code, or someone contributing to project but needs an accompanying test to ensure the feature works or that a bug is fixed (and will stay fixed).<\/p>\n\n<p>There are currently 3,711 issues across all projects and 2,030 in Drupal core.<\/p>\n\n<p>If one of those is your issue or module, I can write the tests you need.<\/p>\n\n<p>After my <a href=\"http:\/\/default\/podcast\/11-mark-conroy\">first podcast episode with Mark Conroy<\/a>, I did this for <a href=\"https:\/\/www.drupal.org\/project\/content_access_by_path\/issues\/3428680\">the Content Access by Path module<\/a>, which now has tests and automated checks with GitLab CI - so they will be run for every future merge request.<\/p>\n\n<p>You can see me writing them on <a href=\"https:\/\/www.youtube.com\/watch?v=XTpliKd47Lg\">a previous live stream<\/a>.<\/p>\n\n<p>If you need tests written or help writing them yourself, reply and get in touch.<\/p>\n\n<p>If you want to <a href=\"http:\/\/default\/sponsor\">sponsor my contribution time<\/a>, you'll also get contribution credit for any issues or merge requests I work on during that time and, whilst it's been a while since my last live stream, you'd also be mentioned there as I work on these issues.<\/p>\n\n<p>I have around a day a week available for sponsored contribution time.<\/p>\n\n<p>If you're interested, reply and let's get it arranged.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0800e5f256b7e5d9dc618733f4dec508",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json b/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json
index 250d90d39..688d08373 100644
--- a/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json
+++ b/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json
@@ -87,6 +87,5 @@
             "processed": "<p>In Drupal, there are different types of automated tests we can write.<\/p><p>The most common I use are Functional, Kernel and Unit - which I explain about in <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">my Test Driven Drupal talk<\/a>.<\/p><p>If I'm writing multiple of the same type, I'll often create my own base test class that extends <code>BrowserTestCase<\/code>, <code>KernelTestCase<\/code> or whatever base class I need rather than extending it directly.<\/p><p>This allows me to write custom helper functions and share behaviour between the tests.<\/p><p>An example is the <code>createDailyEmailNode<\/code> method I wrote to simplify creating daily emails in my tests <a href=\"http:\/\/default\/daily\/2025\/05\/11\/email-archive-tome\">since migrating to Tome<\/a>.<\/p><p>But, what if you want to do this for different types of test?<\/p><p>Enter, traits.<\/p><p>Traits are a way of reusing code without inheritance - meaning without extending a base class.<\/p><p>I can use a trait in my functional and kernel tests whilst both extend their required base classes.<\/p><p>I did this with my <code>createDailyEmailNode<\/code> method so I could re-use it in both types of tests when counting the number of sent daily emails.<\/p><p>To see this, you can <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/src\/commit\/88ec3d9e5136c6cbefebba063863ef1a058f4b09\/modules\/opd_daily_emails\/tests\/src\">look at the code<\/a> on my Forgejo instance.<\/p><p>P.S. If you want to learn how to write automated tests in Drupal, subscribe to <a href=\"http:\/\/localhost:8888\/atdc\">my free 10-day email course<\/a>.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json b/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json
index a22309acc..1cc901faf 100644
--- a/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json
+++ b/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I like framework-agnostic tools.<\/p>\n\n<p>I like to reuse knowledge and tools across projects, whether I'm working with Drupal, Symfony, Laravel or Sculpin.<\/p>\n\n<p>Rector is one of those tools.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/04\/12\/drupal-rector-and-the-project-update-bot\">Yesterday<\/a> I said I use it to create automatic updates to my Drupal module code, but it can be used for other PHP projects, too.<\/p>\n\n<p>If you're upgrading a PHP library and want to use promoted constructor properties, for example, Rector can do that for you - and a lot more.<\/p>\n\n<p>You define which rules or presets you want to use, run Rector on the code, and it will make those changes.<\/p>\n\n<p>Having Rector do this work leaves me free to stay focused on other tasks.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0c86fb80c00db44f4daefbe61a6ba03b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json b/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json
index a08ce82a1..db1f1b827 100644
--- a/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json
+++ b/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You have a CI pipeline in your project.<\/p>\n\n<p>Every time you push a commit, the CI pipeline runs and performs its checks.<\/p>\n\n<p>It runs the automated tests and verifies they pass, statically analyses the code to identify any issues and validates the code follows the correct coding style and standards.<\/p>\n\n<p>Everything passes.<\/p>\n\n<h2 id=\"what-next%3F\">What next?<\/h2>\n\n<p>If the pipeline passes, your change is deployable.<\/p>\n\n<p>So, why not extend the pipeline to deploy the change once the checks pass?<\/p>\n\n<p>If the checks don't pass, don't deploy.<\/p>\n\n<p>It could be as simple as pushing the code to an S3 bucket, a separate Git branch or repository for managing deployments, or creating an artifact like a Docker image.<\/p>\n\n<p>Instead of waiting for someone to do this manually, remove a step and automate it within the pipeline.<\/p>\n\n<p>The sooner it's deployed, the sooner it provides value for your application's users.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6e88858810fb772741027a9ce37485cc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json b/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json
index 639545cc0..55722c8ec 100644
--- a/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json
+++ b/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Do you have long-running or performance-heavy tasks in your application?<\/p>\n\n<p>What about performing complex actions when a user completes a task, such as submitting a form?<\/p>\n\n<p>What if the action took several seconds or minutes to complete?<\/p>\n\n<p>The user would assume their submission failed and may either leave or submit the form again and cause duplicate submissions.<\/p>\n\n<p>Instead, maybe use a queue.<\/p>\n\n<p>When the user submits the form, all you need to do is create a queue item for that submission and let the form submit as normal.<\/p>\n\n<p>In the background, the queue items will be processed when they can take more time or memory to perform the tasks and without blocking the user - giving them a better experience.<\/p>\n\n<p>Drupal supports queues by default, storing queue items in its database.<\/p>\n\n<p>For an example, see the <a href=\"https:\/\/www.drupal.org\/project\/private_message_queue\">Private Message Queue module<\/a> on Drupal.org.<\/p>\n\n<p>I wrote it for a client project to use queues when sending private messages to event attendees, which could be hundreds per event.<\/p>\n\n<p>Without a queue, the request would have taken a long time to complete, or likely timed out.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e3d2f5da90f0708c2f7168e8c649f8c9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json b/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json
index 8d5feeb3e..191082063 100644
--- a/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json
+++ b/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Continuing yesterday's thought on <a href=\"http:\/\/default\/daily\/2024\/05\/04\/strict-typing-in-php\">strictness in PHP<\/a>, today I want to talk about adding more strictness to PHPStan.<\/p>\n\n<p>Adding the <a href=\"https:\/\/github.com\/phpstan\/phpstan-strict-rules\">PHPStan Strict Rules extension<\/a> makes PHPStan stricter by adding new, more opinionated rules.<\/p>\n\n<p>For example:<\/p>\n\n<ul>\n<li>Require booleans in if, elseif, ternary operator, after !, and on both sides of &amp;&amp; and ||.<\/li>\n<li>Use the <code>$strict<\/code> parameter with <code>in_array<\/code>, <code>array_search<\/code>, <code>array_keys<\/code> and <code>base64_decode<\/code>.<\/li>\n<li>Disallow empty().<\/li>\n<li>Require calling parent constructor.<\/li>\n<\/ul>\n\n<p>You can enable and disable rules as needed but, like setting the PHPStan level, ideally I like to enable them all by default and see how strict I go.<\/p>\n\n<p>It depends on the code being tested and the preference of the team, though I find the stricter the rules, the less bugs there are.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2ff6c4f363c796e474dd5ad89dd20907",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.46604509-5226-42af-ba63-41eeaed19074.json b/content/node.46604509-5226-42af-ba63-41eeaed19074.json
index efe0b86ce..28664bbb4 100644
--- a/content/node.46604509-5226-42af-ba63-41eeaed19074.json
+++ b/content/node.46604509-5226-42af-ba63-41eeaed19074.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When working as part of a team, I like to do pair or mob programming as much as possible.<\/p>\n\n<p>I like being able to give and receive feedback in real-time; everyone can contribute to the solution and more shared knowledge, so there's less siloing, and it's much harder to block multiple people than a single person.<\/p>\n\n<p>Working in pairs or a mob is a great opportunity to onboard new team members, train and mentor, and share tips and tricks.<\/p>\n\n<p>It's usually more productive than working separately, and it's nice to speak and socialise with other team members whilst working on a task.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b0e612367a93931235c02addd4091033",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json b/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json
index 0cdab4928..79538f71b 100644
--- a/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json
+++ b/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the main uses for <a href=\"http:\/\/default\/daily\/2024\/07\/02\/ci-not-ci-pipeline\">a CI pipeline<\/a> is to build artifacts for your application, such as installing your dependencies using Composer or npm, or using build tools to perform tasks such as building your CSS and JavaScript assets.<\/p>\n\n<p>Performing these tasks in a CI pipeline means the resulting files can be ignored from your code repository and not committed - making your commits smaller and easier to review, and less likely for you to encounter merge conflicts.<\/p>\n\n<p>The alternative approach is to not use a CI pipline and to perform the tasks manually and commit them to your repository.<\/p>\n\n<p>This introduces a separate set of challenges, but people like having the files in their repository and not worrying about failures in their pipeline.<\/p>\n\n<p>Which do you prefer?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2bda9bfc260c442486c03a20105f9ef3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json b/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json
index 6ee925c00..bd5c5f3d5 100644
--- a/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json
+++ b/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Have you wondered why a file or directory is being ignored in your Git repository and isn't appearing when you run <code>git status<\/code>?<\/p>\n\n<p>Maybe you have multiple <code>.gitignore<\/code> files and you don't know which is causing the issue, or you ignore everything and explicitly unignore the files that you want to add.<\/p>\n\n<h2 id=\"%60check-ignore%60-to-the-rescue\"><code>check-ignore<\/code> to the rescue<\/h2>\n\n<p><code>git check-ignore<\/code> accepts a list of paths and checks if each is ignored.<\/p>\n\n<p>There's also a <code>--verbose<\/code> option that will tell you which <code>.gitignore<\/code> file is causing it to be ignored as well as the line number and the pattern - great information for debugging, and no more force adding files.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b132c7f6277c6bbb308c6905d1673959",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json b/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json
index 1c01e4b33..89dab52fb 100644
--- a/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json
+++ b/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It's been <a href=\"http:\/\/default\/daily\/2023\/08\/08\/8-years-of-dotfiles\">more than nine years<\/a> since I started <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\">my dotfiles repository<\/a>, which is a collection of configuration files for tools I use.<\/p>\n\n<p>Originally containing my <code>.gitconfig<\/code> configuration file for Git, it now contains my configuration for Neovim, tmux, Git and a lot more.<\/p>\n\n<p>One of the things I like is being able to see and read other peoples' dotfiles and take inspiration from their configurations.<\/p>\n\n<p>I see some configurations that are very complex and customised, and some which are simpler.<\/p>\n\n<p>Recently, I've been thinking about how much customisation is too much, and moving towards a more minimal configuration.<\/p>\n\n<p>This isn't specific to command-line tools and also applies to customising GUI programs such as PhpStorm or VSCode.<\/p>\n\n<p>A more complex configuration means more code to maintain.<\/p>\n\n<p>It's more difficult to work on different computers, whether you're pair or mob programming, or working on a remote server. Would you still be productive if you didn't have all your configurations?<\/p>\n\n<p>If you've changed the default behaviour of a command, such as not allowing merge commits in Git or rebasing by default, if someone doesn't have that same option, is that going to cause confusion or introduce inconsistencies?<\/p>\n\n<p>I'm not going to reset all my configuration files to their default values, but I'll continue to review and decide whether I want to customise something on a case by case basis and whether adding it - especially if it's a larger addition, such as adding a Vim plugin - is worth the maintenance overhead.<\/p>\n\n<p>The same as in an application, I don't want to add modules or plugins that I'm not going to use or aren't adding value, and I want to ensure I'm making the most of what the software offers.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e1997b3a167015374e1ceb9ac28b690e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json b/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json
index fd8b7730e..da1beafb7 100644
--- a/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json
+++ b/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>For some time, I've written commit messages following the Conventional Commits specification, where you start the subject with the type of commit - such as <code>feat<\/code>, <code>fix<\/code>, <code>chore<\/code>, <code>docs<\/code>, etc - and provide an optional scope before completing the subject line (the first line in the message).<\/p>\n\n<p>Then, it is encouraged to add a longer body to the message and provide any links and task IDs that the change relates to.<\/p>\n\n<p>Now I've been using it for a while, I'm deciding whether it adds value for me and whether it's worth me using it.<\/p>\n\n<p>I don't create automatic CHANGELOG files from the commit types.<\/p>\n\n<p>The scopes are usually arbitrary, it's unclear which scope (or scopes) should be added, or it repeats the module name I'm working on (which I could see from the Git diff).<\/p>\n\n<p>While I see value in writing descriptive commit messages, I'm unsure if I do to format the subject line in this way.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I like to use an iterative approach to my workflow. I like to try things and see if they work for me. If not, I can stop or continue iterating.<\/p>\n\n<p>If working with others, should you focus on writing commits that categorise commit messages within their subject or writing descriptive commit messages that capture why the change is needed?<\/p>\n\n<p>Which provides the most value when looking back at the Git log in the future?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e3dc97eea5cca21de24880789f8cf5fd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json b/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json
index a4b904a2d..54e0e3a71 100644
--- a/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json
+++ b/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I posted a screenshot from my <a href=\"http:\/\/default\/atdc\">automated testing in Drupal email course<\/a> on Twitter as a sneak peek of what's included.<\/p>\n\n<p>Here it is again:<\/p>\n\n<p><img src=\"https:\/\/www.oliverdavies.uk\/assets\/images\/php-neovim-1.png\" alt=\"Screenshot of a lesson from my automated testing email course\"><\/p>\n\n<p>I also posted a screenshot of the accompanying code in my text editor, Neovim, which had a few likes.<\/p>\n\n<p><img src=\"https:\/\/www.oliverdavies.uk\/assets\/images\/php-neovim-2.png\" alt=\"Screenshot of Drupal code in Neovim\"><\/p>\n\n<p>Since July 2021, I've used Neovim as my daily driver for writing all my code, which I spoke about during my <a href=\"http:\/\/default\/presentations\/working-without-workspace\">Working without Workspace talk<\/a>.<\/p>\n\n<p>You can also see my NixOS-based <a href=\"https:\/\/github.com\/opdavies\/dotfiles\">dotfiles on GitHub<\/a> which contains my Neovim configuration.<\/p>\n\n<p>Register now to find out when the email course is live, or <a href=\"http:\/\/default\/daily\/2023\/12\/25\/zero-to-test\">read the first lesson<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f9f7d8ae3da04b94c84b29061624b268",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json b/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json
index ceff2bdc3..b2c78d710 100644
--- a/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json
+++ b/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm in the final phase of a Drupal development project for a customer.<\/p>\n\n<p>It has some custom modules and code I wrote with automated tests and test-driven development.<\/p>\n\n<p>Today, the client reported a bug.<\/p>\n\n<p>But, instead of something working incorrectly, this was a use case I hadn't considered.<\/p>\n\n<p>The tests were passing, but there wasn't one for this.<\/p>\n\n<p>I wrote the code for the use cases I was aware of when I started, and now I'm aware of another, I can add a test for it and ensure it's tested and working.<\/p>\n\n<p>To do test-driven development, you don't need to know all the use cases and functionality upfront.<\/p>\n\n<p>Write for what you know at the time, then expand and iterate in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "15b5f4507ca4a5cb62249ea0461feb8a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json b/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json
index 6e56f6146..f2574656b 100644
--- a/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json
+++ b/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, I recorded an episode of <a href=\"http:\/\/default\/podcast\">Beyond Blocks<\/a> with Eirik Morland - the Developer of violinist.io, a tool for automating dependency updates in PHP projects.<\/p>\n\n<p>Instead of a person manually running <code>composer update<\/code> in each project, tools like Violinist can do that for you and submit pull or merge requests to your project for you to review.<\/p>\n\n<p>But why would you want this?<\/p>\n\n<p>There are technical reasons, such as not having to rely on everyone having the same local environment and avoiding potential conflicts, and consistency by ensuring the same command is run every time.<\/p>\n\n<p>But, the big advantage, in my opinion, is the time it saves and allows you to reuse.<\/p>\n\n<p>Instead of manually updating each project's dependencies, I can focus on tasks that deliver value to my customers and clients and move us towards our objectives.<\/p>\n\n<p>Dependency updates, such as a new version of Drupal core or a contrib module, don't contain any perceived value compared to other tasks, such as adding a new feature or fixing a bug.<\/p>\n\n<p>They happen behind the scenes, often invisibly, without any visual changes to show an update has been done.<\/p>\n\n<p>If they aren't done often, they will be riskier to deploy due to the larger changes, and the longer it takes, the greater the potential for insecure versions to be exploited - potentially affecting your reputation and your customer's and with any remedial work taking the focus from other tasks.<\/p>\n\n<p>Having a service like Violinist performing the updates for you means they can be applied and deployed more regularly, reducing the risk and making it easier to stay up-to-date and run secure versions of your dependencies.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f6dc73181ab39abab3e420cbef29003a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json b/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json
index c99afb84a..b8f9e02fb 100644
--- a/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json
+++ b/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I reviewed <a href=\"https:\/\/www.drupal.org\/project\/override_node_options\/issues\/3269901\">the issue and merge request<\/a> to make the <a href=\"https:\/\/www.drupal.org\/project\/override_node_options\">Override Node Options<\/a> module compatible with Drupal 10.<\/p>\n\n<p>It's a small patch that mainly affects the module's test suite so has a low risk of breaking the functionality of the module.<\/p>\n\n<p>As well as the automated tests, I've done some manual testing with the patch applied on both Drupal 9.5 and 10.<\/p>\n\n<p>The project page shows the module is currently used on over 34,000 sites including 18,565 Drupal 8 and 9 websites on the 8.x-2.x branch. Hopefully this number will continue to increase once the Drupal 10 version is released.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a4d60c0bc89cf319cc0a3598dc62b82f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.494f1c44-47b9-48be-9240-5a9df560fdaf.json b/content/node.494f1c44-47b9-48be-9240-5a9df560fdaf.json
index e98cbe306..479058e7a 100644
--- a/content/node.494f1c44-47b9-48be-9240-5a9df560fdaf.json
+++ b/content/node.494f1c44-47b9-48be-9240-5a9df560fdaf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It was announced this week at DrupalCon that the end-of-life date for Drupal 7 has been extended until the 5th of January 2025, giving another year for people to upgrade the 40,000+ Drupal 7 websites.<\/p>\n\n<p>Whilst there's no official announcement yet, it seems this is the final extension and will be when support ends.<\/p>\n\n<p>Of course, it doesn't mean all of the contributed modules, themes and distributions will be supported or updated until then, but this will give additional time to plan and migrate the remaining Drupal 7 websites whilst still giving clarity by setting a final date that will not be extended again.<\/p>\n\n<p>If you're still on Drupal 7 and need to learn more about upgrading to Drupal 10, <a href=\"http:\/\/default\/call\">book an advisory call<\/a> or <a href=\"http:\/\/default\/drupal7\">an upgrade roadmap<\/a> for your Drupal 7 project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f03a3434c8c7ccf722ebf0de5355df06",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json b/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json
index fe53651ef..dbc9ba8e1 100644
--- a/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json
+++ b/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Do you want to learn automated testing in Drupal?<\/p>\n\n<p>My free email course is live!<\/p>\n\n<p>Learn how to write tests in Drupal from a DrupalCon speaker, workshop trainer, and module maintainer (me!).<\/p>\n\n<p>Register for the course and get a lesson each day where you build a module from scratch with automated tests and test-driven development based on my previous talks and workshops.<\/p>\n\n<p>All emails are sent from my personal email address, so if you have questions or issues, you can press reply and let me know. I'll be happy to help!<\/p>\n\n<p>Happy testing!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "738a534ae36eaaaaee08f143a195474d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json b/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json
index 644ce0071..87df49a2b 100644
--- a/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json
+++ b/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as being <a href=\"http:\/\/default\/daily\/2025\/03\/12\/easy\">easy to build<\/a> and <a href=\"http:\/\/default\/daily\/2025\/03\/13\/deploy\">simple to deploy<\/a>, static websites are easy to backup and, if needed, restore.<\/p>\n\n<p>I backup several static websites from my server using rsync - the same command I use to deploy them.<\/p>\n\n<p>rsync is fast as it only downloads files that have changed, so backing up several websites only takes a few seconds.<\/p>\n\n<p>There are are no databases to worry about - all I need to do is backup the static files themselves.<\/p>\n\n<p>Running the backups is also easy.<\/p>\n\n<p>I have a scheduled cron job that downloads everything from the <code>\/var\/www\/vhosts<\/code> directory on my server and creates a local copy.<\/p>\n\n<p>If I need to restore from a backup or migrate to a different server, I just run the appropriate rsync command to re-upload them - the same as how I deployed them originally.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cad56e3254ecbb16885c1f741f0776f9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json b/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json
index eb2200736..951235977 100644
--- a/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json
+++ b/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/11\/25\/nix-the-package-manager\">As well as Nix managing packages<\/a> and <a href=\"http:\/\/default\/daily\/2024\/11\/27\/nix-as-an-operating-system\">NixOS as your operating system<\/a>, you can use Nix to manage your user configuration and dotfiles.<\/p>\n\n<p>Enter, Home Manager.<\/p>\n\n<p>Home Manager is available as a module for NixOS and a standalone package for other Linux distributions and macOS.<\/p>\n\n<p>With it, you can install and configure programs for specific users and create and manage dotfiles such as .gitconfig, .tmux.conf and .zshrc instead of using a tool like Stow.<\/p>\n\n<p>There's also the extra benefit that <a href=\"http:\/\/default\/daily\/2024\/11\/21\/one-configuration-language-to-rule-them-all\">you can write these files in the Nix language<\/a> and only focus on one configuration language.<\/p>\n\n<p>Nix and Home Manager will create the desired output file in whatever the program wants, whether it's JSON, ini, YAML or something else.<\/p>\n\n<p>A good example is <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/blob\/3acd73f6a2e19eadcc16baf22afad5dfad5e049b\/nix\/modules\/home-manager\/features\/cli\/git.nix\">my .gitconfig configuration<\/a>. It includes settings for Git itself, aliases, global excludes, adds extra packages such as <a href=\"https:\/\/zet.oliverdavies.uk\/notes\/10\">git-instafix<\/a> and some environment variables.<\/p>\n\n<p>All in one file and all in one language.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f0ade844887ddbd5a34d24a087017478",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json b/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json
index 14ca8ecae..747f1a4a1 100644
--- a/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json
+++ b/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm an advocate of both automated testing and static analysis but have mostly kept the two separate.<\/p>\n\n<p>I've typically not run PHPStan on my automated test files - ignoring them in my PHPStan configuration.<\/p>\n\n<p>As tests aren't production\/implementation code, what's the benefit of analysing them?<\/p>\n\n<p>Recently, though, I've challenged this and, on some projects, started to run PHPStan on my test classes.<\/p>\n\n<p>Depending on what level PHPStan is running, the more changes you're likely to have to make to get your test classes to pass the static analysis, and whilst it results in more verbose and explicit code, I prefer that and being able to easily understand what it does rather than implicit.<\/p>\n\n<p>If you have a bug in your test, static analysis will potentially find that, too, making your test suite more robust.<\/p>\n\n<p>Looking at some large open-source PHP projects, they run static analysis on their test code.<\/p>\n\n<p>Presumably, they're benefiting from it, so I'll try it and see if I get the same.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "244fb1e186ffb1e05c56a3441aef004b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json b/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json
index 7ab5770d9..50a63af23 100644
--- a/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json
+++ b/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm not a professional Ruby or Rails Developer, but I am a professional test-driven Developer.<\/p>\n\n<p>I like to see how others do TDD and have been watching videos of <a href=\"https:\/\/www.codewithjason.com\">Jason Swett<\/a>'s online meetups where he works on his Saturn CI project.<\/p>\n\n<p>A few times he's mentioned using dull and sharp blades as an alternative metaphor for technical debt.<\/p>\n\n<p>He's also written an article about it.<\/p>\n\n<p>Here's an excerpt:<\/p>\n\n<blockquote>\n  <p>I prefer to think of a software system as a collection of blades.<\/p>\n  \n  <p>A dull blade is never preferable to a sharp one. Sometimes it may be better to just cut with the dull blade instead of taking the time to sharpen the blade before cutting, but it\u2019s clear that that\u2019s a compromise. No one would talk about \u201cstrategic dull blades\u201d the way they talk about strategic technical debt.<\/p>\n  \n  <p>Unlike debt which you can simply choose not to take on, blades unavoidably get dull with use. Having technical debt makes it sound like you did something wrong. But you don\u2019t have to do anything wrong in order to end up with bad code. Often, bad code is simply the result of entropy. The blade metaphor makes it clear that dullness is normal and unavoidable.<\/p>\n<\/blockquote>\n\n<p>If you like this, you can <a href=\"https:\/\/www.codewithjason.com\/sharp-blades-and-dull-blades\">read the whole article<\/a>.<\/p>\n\n<p>Do you have other metaphors for technical debt? Reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0bb94ff586d310b9b4782afab2635483",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json b/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json
index a8c3d9191..d7d63f8e2 100644
--- a/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json
+++ b/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How often have you need code like this?<\/p>\n\n<pre><code class=\"php\">\/\/ Returns true.\nreturn false;\n<\/code><\/pre>\n\n<p>Whilst a comment like this could have been true when it was written, the code can change independently of the comment - making them out of sync and the comment no longer true.<\/p>\n\n<p>As the comment is not evaluated or executed, there isn't a way to validate whether it's still correct, so whilst it could be, it may not be.<\/p>\n\n<p>Comments should describe why the code is needed, not what it does.<\/p>\n\n<p>If a comment describes the functionality, it can be refactored and extracted to a class, method or function - a.k.a. self-documenting code.<\/p>\n\n<p>But, if you want something that will alert you if the functionality changes, look into <a href=\"http:\/\/default\/atdc\">automated testing<\/a>.<\/p>\n\n<p>If you have a passing test that suddenly starts to fail, you know the behaviour has changed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "39666fa6935e0010996ee0d41ac7462b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json b/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json
index a870dd852..837f1b976 100644
--- a/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json
+++ b/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been a Mentor for students on a coding bootcamp a few times before, and I'm looking forward to doing this again - this time with <a href=\"https:\/\/www.schoolofcode.co.uk\">School of Code<\/a>.<\/p>\n\n<p>After hearing about them at a PHP meetup last year, I was keen to get involved after the previous bootcamp I was involved with closed its doors.<\/p>\n\n<p>I've always been impressed to see people with little, or usually no prior coding experience, on these bootcamps and what they can learn and achieve in a short amount of time - and one of the things that drew me to School of Code is that the bootcamp is free for learners.<\/p>\n\n<p>This week is the mentor kick-off session, with the new cohort starting next week.<\/p>\n\n<p>I'm looking forward to seeing who I'm paired up with, and helping them take their first steps into a career in software development.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ef838351b3125011ce7d336faa1387f0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json b/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json
index 03ab1a88e..3140e80ea 100644
--- a/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json
+++ b/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After starting with jQuery in Drupal 6 and moving to full JavaScript frameworks like Vue, I've recently been using Stimulus when adding JavaScript to my projects.<\/p>\n\n<p>After finding it via SymfonyCasts and Symfony UX (I can't remember if Ryan and I discussed it <a href=\"http:\/\/default\/podcast\/10-ryan-weaver-symfonycasts\">in our podcast episode<\/a>), I like that it works on top of my existing HTML and Twig templates instead of having to rewrite or duplicate all the markup.<\/p>\n\n<p>You enable and configure it with data attributes like <code>data-controller<\/code> and <code>data-action<\/code> in your HTML which refer to separate JavaScript classes and methods, so you have some structure and organisation compared to putting all the logic in Twig.<\/p>\n\n<p>Having separate controllers also makes it easy to reuse logic in other parts of your application or extract it for use in other projects.<\/p>\n\n<p>If you want an example of how I've set up stimulus with esbuild, <a href=\"https:\/\/github.com\/opdavies\/stimulus-esbuild-example\">take a look at this GitHub repository<\/a>, or <a href=\"https:\/\/symfonycasts.com\/screencast\/stimulus\">watch the Stimulus course on SymfonyCasts<\/a>.<\/p>\n\n<p>I skipped the lessons on Stimulus before and didn't try it for a while, but I'm glad I have.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a6007d2feefccdaac0d128595fe05dd0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json b/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json
index d82f87889..5a4e4b0d5 100644
--- a/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json
+++ b/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as being easy to test, good software is easy to change.<\/p>\n\n<p>If requirements change or a bug is found, it should be easy to change the code.<\/p>\n\n<p>Simple code is easier to read and fix, and code split into smaller functions and classes - particularly when using design patterns - make it easier to change the existing code or its behaviour by writing new code.<\/p>\n\n<p>For example, if you need to change your payment gateway provider, ideally your software has been written so that each payment gateway has its own implementation and then can be swapped without needing to change the original code.<\/p>\n\n<p>If you need to change the behaviour of a class, you could use a Decorator to wrap and extend it.<\/p>\n\n<p>Having tests also makes the code easier to change as you can validate and verify the behaviour before and after the change.<\/p>\n\n<p>Changing code that doesn't have tests is risky, so if there aren't any, write some before changing the code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "529c210a492581735189b8a17c332053",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json b/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json
index 78334edc4..5edae10a1 100644
--- a/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json
+++ b/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've occasionally been experimenting with AI whilst programming.<\/p>\n\n<p>Not in my editor, but asking it questions if I'm unsure how to do something or something isn't working.<\/p>\n\n<p>As a pair programming partner of sorts.<\/p>\n\n<p>Its results and suggestions are still mixed.<\/p>\n\n<p>But I've noticed I've started to ask AI for answers to simple questions I can find or figure out myself.<\/p>\n\n<p>Things like how to show more verbose output for a command, which I can find from the command's help text or manual.<\/p>\n\n<p>This was part of a larger issue which, instead of asking AI, I would usually investigate by reading the available documentation or source code.<\/p>\n\n<p>I don't want to lose my problem solving skills.<\/p>\n\n<p>I like reading documentation and code to learn more about the tools I'm using and to solve issues I encounter.<\/p>\n\n<p>I like to read articles others have written on their websites about the same or similar issues.<\/p>\n\n<p>Whilst AI can be a useful tool, I don't want to become over reliant on it.<\/p>\n\n<p>I still want to be able to investigate, solve and learn things for myself and enjoy the process.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6e42e4070398b24d913cecbd7fa25945",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json b/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json
index d14fe1105..de5d0971a 100644
--- a/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json
+++ b/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I remember a while ago, someone could call themselves a \"real\" Software Developer if they don't write automated tests.<\/p>\n\n<p>This is, of course, not the case.<\/p>\n\n<p>But I'd suggest that it makes you a better Developer who writes better and more robust software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4bab95f073ef6c5bab4596c03470a49c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json b/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json
index 0db179746..fcb02ab38 100644
--- a/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json
+++ b/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tailwind's configuration file also makes it easy to add it to an existing codebase, whether it uses custom CSS or another CSS framework.<\/p>\n\n<p>You can opt-out of Tailwind's CSS reset and normalisation by adding <code>corePlugins: { preflight: false }<\/code> to tailwind.config.js, and if you have duplicate classes with existing classes and Tailwind-generated ones, you can add <code>prefix: 'tw-'<\/code> to prefix all of Tailwind's class names and avoid the conflicts.<\/p>\n\n<p>If you need to deal with specificity, you can mark Tailwind-generated classes as important by adding <code>important: true<\/code> so that they can override any existing styling. You can do the same in HTML code by prefixing a class name with an exclamation mark - e.g. <code>!flex<\/code>.<\/p>\n\n<p>Or, if you know that your Tailwind styles will only be used within a certain element, like <code>#app<\/code>, instead of making all classes important, by adding <code>important: \"#app\"<\/code> to the configuration, Tailwind classes will be prefixed with that selector - making them more specific.<\/p>\n\n<p>Once these options are set, you can start using Tailwind without affecting the existing styles.<\/p>\n\n<p>Doing this, and starting small by using a small number of utilities can be a good step towards migrating an existing codebase to use Tailwind and removing the existing styles at a later date.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7da91326631cb7cf3b105e8837f5879c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json b/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json
index 7b1a2f792..923e06ce7 100644
--- a/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json
+++ b/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently watched <a href=\"https:\/\/www.youtube.com\/watch?v=DuozyaJQQ1U\">a video about separating logic<\/a> into different categories within your custom code.<\/p>\n\n<p>It wasn't a PHP video, but the concept applies to any programming language or framework.<\/p>\n\n<p>This was the final structure of the directories:<\/p>\n\n<pre><code class=\"plain\">src\/\n  Controllers\/\n  Domain\/\n  Persistence\/\n  Properties\/\n  Services\/\n<\/code><\/pre>\n\n<p>It was described as using <code>Controllers<\/code> for presentational logic, <code>Domain<\/code> for domain logic, and <code>Services<\/code> for application logic, and reminds me of a domain-driven design (DDD) approach to organising code.<\/p>\n\n<p>I remember watching other older videos showing separating business and presentational logic in React into different components (if I remember correctly).<\/p>\n\n<p>This isn't an approach I see in Drupal code, maybe more-so in other PHP framework-based projects like Symfony or Laravel.<\/p>\n\n<p>It's something I've been thinking of trying, potentially on my website codebase.<\/p>\n\n<p>Do you organise your code in this or a similar way?<\/p>\n\n<p>If so, why?<\/p>\n\n<p>What advantages does it bring?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a59b6f540ddfce9e980f906b5921178c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json b/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json
index 7357770d0..82ad7103a 100644
--- a/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json
+++ b/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Happy Christmas!<\/p>\n\n<p>Here's my present - a sneak peek at the first lesson in my free upcoming Automated Testing for Drupal email course.<\/p>\n\n<p>In this lesson, we start from scratch and end with a working test suite.<\/p>\n\n<p>If you like it, <a href=\"http:\/\/default\/atdc\">register for free and get the full course<\/a> when it launches.<\/p>\n\n<h2 id=\"creating-a-drupal-project\">Creating a Drupal project<\/h2>\n\n<p>If you don't have one, you'll need to create a new Drupal project. I'd suggest using Drupal 10.2 and the instructions at <a href=\"https:\/\/www.drupal.org\/download\">https:\/\/www.drupal.org\/download<\/a>.<\/p>\n\n<p>You'll need <a href=\"https:\/\/www.php.net\/manual\/en\/install.php\">PHP<\/a> and <a href=\"https:\/\/getcomposer.org\/doc\/00-intro.md\">Composer<\/a>.<\/p>\n\n<p>First, run <code>composer create-project drupal\/recommended-project drupal<\/code> followed by <code>cd drupal &amp;&amp; composer require --dev drupal\/core-dev<\/code> to add the development dependencies, including PHPUnit.<\/p>\n\n<p>At this point, you should have a <code>web<\/code> directory and a <code>phpunit<\/code> file within <code>vendor\/bin<\/code>.<\/p>\n\n<p>Finally, run <code>php -S 0.0.0.0:8000 -t web<\/code> to start a local web server.<\/p>\n\n<p>You don't need to install Drupal - as long as you see the installation page, that's fine.<\/p>\n\n<h2 id=\"creating-a-custom-module\">Creating a custom module<\/h2>\n\n<p>Before adding tests, you must create a module to place them in.<\/p>\n\n<p>Run <code>mkdir -p web\/modules\/custom\/atdc<\/code> to create an empty module directory, and create an <code>atdc.info.yml<\/code> file within it with this content:<\/p>\n\n<pre><code class=\"language-yaml\">name: Example\ntype: module\ncore_version_requirement: ^10\npackage: Custom\n<\/code><\/pre>\n\n<p>This is the minimum content needed for a module to be installable.<\/p>\n\n<h3 id=\"writing-your-first-test-class\">Writing your first test class<\/h3>\n\n<p>Test classes are placed within each module's <code>tests\/src<\/code> directory.<\/p>\n\n<p>Run <code>mkdir -p web\/modules\/custom\/atdc\/tests\/src\/Functional &amp;&amp; touch web\/modules\/custom\/atdc\/tests\/src\/Functional\/ExampleTest.php<\/code> to create the directory structure and a blank test class.<\/p>\n\n<p>Then, add this content.<\/p>\n\n<pre><code class=\"language-php\">&lt;?php\n\nnamespace Drupal\\Tests\\atdc\\Functional;\n\nuse Drupal\\Tests\\BrowserTestBase;\nuse Symfony\\Component\\HttpFoundation\\Response;\n\nclass ExampleTest extends BrowserTestBase {\n\n&nbsp; public $defaultTheme = 'stark';\n\n}\n<\/code><\/pre>\n\n<p>Note: within a test class, the namespace is <code>Drupal\\Tests\\{module_name}<\/code> instead of <code>Drupal\\{module_name}<\/code>.<\/p>\n\n<p>With the boilerplate class added, create a test method within it:<\/p>\n\n<pre><code class=\"language-php\">public function testBasic(): void {\n&nbsp; self::assertTrue(FALSE);\n}\n<\/code><\/pre>\n\n<p>Note: the class name must be suffixed with <code>Test<\/code>, and the test method must be prefixed with <code>test<\/code> for them to be run.<\/p>\n\n<p>Now we have a test with an assertion, we need to run it and see if it passes.<\/p>\n\n<h2 id=\"running-the-test\">Running the test<\/h2>\n\n<p>On the command line, run <code>vendor\/bin\/phpunit web\/modules\/custom<\/code>, and you'll get an error like:<\/p>\n\n<blockquote>\n  <p>PHPUnit\\TextUI\\RuntimeException: Class \"Drupal\\Tests\\BrowserTestBase\" not found.<\/p>\n<\/blockquote>\n\n<p>This isn't an assertion failure, but that PHPUnit can't find the files it needs to run.<\/p>\n\n<p>To fix this, let's configure PHPUnit.<\/p>\n\n<h2 id=\"configuring-phpunit\">Configuring PHPUnit<\/h2>\n\n<p>Create a new <code>phpunit.xml.dist<\/code> file at the root of your project, with this content:<\/p>\n\n<pre><code class=\"xml\">&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n&lt;phpunit bootstrap=\"web\/core\/tests\/bootstrap.php\" colors=\"true\"&gt;\n  &lt;php&gt;\n    &lt;env name=\"SIMPLETEST_BASE_URL\" value=\"http:\/\/localhost:8000\"\/&gt;\n    &lt;env name=\"SIMPLETEST_DB\" value=\"sqlite:\/\/localhost\/\/dev\/shm\/test.sqlite\"\/&gt;\n    &lt;ini name=\"error_reporting\" value=\"32767\"\/&gt;\n    &lt;ini name=\"memory_limit\" value=\"-1\"\/&gt;\n  &lt;\/php&gt;\n  &lt;testsuites&gt;\n    &lt;testsuite name=\"Example tests\"&gt;\n      &lt;directory suffix=\"Test.php\"&gt;.\/web\/modules\/**&lt;\/directory&gt;\n    &lt;\/testsuite&gt;\n  &lt;\/testsuites&gt;\n&lt;\/phpunit&gt;\n<\/code><\/pre>\n\n<p>This is based on <code>web\/core\/phpunit.xml.dist<\/code> with some project-specific changes.<\/p>\n\n<p>Namely, setting the <code>bootstrap<\/code> value to include the <code>web\/core<\/code> path and fix the error, and populating the <code>SIMPLETEST_BASE_URL<\/code> and <code>SIMPLETEST_DB<\/code> environment variables.<\/p>\n\n<p>PHPUnit now knows where the files are, to connect to Drupal at <a href=\"http:\/\/localhost:8000\">http:\/\/localhost:8000<\/a> (matching the PHP web server address) and an SQLite database.<\/p>\n\n<p>I've also added a <code>testsuite<\/code> that declares where any test classes will be located so the path doesn't need to be specified on the command line.<\/p>\n\n<h2 id=\"re-running-the-tests\">Re-running the tests<\/h2>\n\n<p>Running the tests again will give the expected error about a failing assertion:<\/p>\n\n<blockquote>\n  <p>Failed asserting that false is true.<\/p>\n<\/blockquote>\n\n<p>Fix the assertion in the test by changing <code>FALSE<\/code> to <code>TRUE<\/code>, run <code>vendor\/bin\/phpunit<\/code> again, and you should see a passing test.<\/p>\n\n<blockquote>\n  <p>OK (1 test, 2 assertions)<\/p>\n<\/blockquote>\n\n<h2 id=\"improving-the-tests\">Improving the tests<\/h2>\n\n<p>Now you have as passing test and know PHPUnit is working, let's improve it.<\/p>\n\n<p>Instead of the basic check, let's check whether certain pages exist and are accessible.<\/p>\n\n<p>To keep things simple and focused on writing and running tests, let's use some standard Drupal pages - the front and administration pages instead of writing your own.<\/p>\n\n<p>As you're writing functional tests by extending <code>BrowserTestBase<\/code>, you can make HTTP requests to the web server, and make assertions on the responses.<\/p>\n\n<p>Replace the <code>testBasic<\/code> test method with the following:<\/p>\n\n<pre><code class=\"language-php\">public function testFrontPage(): void {\n  $this-&gt;drupalGet('\/');\n\n  $assert = $this-&gt;assertSession();\n  $assert-&gt;statusCodeEquals(Response::HTTP_FORBIDDEN);\n}\n\npublic function testAdminPage(): void {\n  $this-&gt;drupalGet('\/admin');\n\n  $assert = $this-&gt;assertSession();\n  $assert-&gt;statusCodeEquals(Response::HTTP_OK);\n}\n<\/code><\/pre>\n\n<p>These tests will make HTTP requests to the specified paths and assert the status code on the response matches the expected values.<\/p>\n\n<p>I'm using the constants on the <code>Response<\/code> class, but you can also use the status code numbers - e.g. <code>200<\/code> and <code>403<\/code>.<\/p>\n\n<h2 id=\"running-the-updated-tests\">Running the updated tests<\/h2>\n\n<p>Running <code>vendor\/bin\/phpunit<\/code>, you'll get two errors:<\/p>\n\n<blockquote>\n  <p>1) Drupal\\Tests\\atdc\\Functional\\ExampleTest::testFrontPage\n  Behat\\Mink\\Exception\\ExpectationException: Current response status code is 200, but 403 expected.<\/p>\n  \n  <p>2) Drupal\\Tests\\atdc\\Functional\\ExampleTest::testAdminPage\n  Behat\\Mink\\Exception\\ExpectationException: Current response status code is 403, but 200 expected.<\/p>\n  \n  <p>ERRORS!<br>\n  Tests: 2, Assertions: 4, Errors: 2.<\/p>\n<\/blockquote>\n\n<p>The responses are not returning the expected status codes, so the tests are failing.<\/p>\n\n<p>Reviewing them, the front page should return a 200 response code (<code>HTTP_OK<\/code>) as it's accessible to all users, including anonymous users.<\/p>\n\n<p>As we're logged out, the administration page should return a 403 (<code>HTTP_FORBIDDEN<\/code>).<\/p>\n\n<p>Swapping the assertions should get the tests to pass.<\/p>\n\n<p>Now, running <code>vendor\/bin\/phpunit<\/code> returns no errors or failures.<\/p>\n\n<blockquote>\n  <p>OK (2 tests, 4 assertions)<\/p>\n<\/blockquote>\n\n<p>Congratulations!<\/p>\n\n<h2 id=\"conclusion\">Conclusion<\/h2>\n\n<p>In this lesson, you've created a new Drupal 10 project, configured PHPUnit and created a custom module with your first passing browser tests.<\/p>\n\n<p>From this, you can hopefully see that automated testing doesn't need to be difficult, and the configuration you've done here will work for the upcoming lessons, where you'll expand on what you've done and explore more that Drupal and PHPUnit have to offer.<\/p>\n\n<p>I hope you enjoyed this sneak peek, and if you'd like to receive the course once it's complete, <a href=\"http:\/\/default\/atdc\">register here for free<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fa1fa6afff083eeef00370e7db237279",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json b/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json
index 866d0e5da..29e9f21c3 100644
--- a/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json
+++ b/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When working on projects, it's common to see messages like \"The website encountered an unexpected error. Please try again later.\".<\/p>\n\n<p>Usually, this is the message shown to the user, whilst a more detailed error message is logged for Developers to diagnose and fix the underlying error.<\/p>\n\n<p>The wording \"unexpected error\" has been intriguing to me, though. When do you expect an error?<\/p>\n\n<p>The best example I can think of for an expected error is when doing test-driven development.<\/p>\n\n<p>When doing TDD, you want to see an error to start as you start with a failing test.<\/p>\n\n<p>Then, you write the code to remove the error and get the test passing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d896323fbe54f5997b5e4edeb7c0c0dc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json b/content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json
index 094609a74..1586c0299 100644
--- a/content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json
+++ b/content/node.4c9fd2d9-307a-43a1-8993-d422261eabd7.json
@@ -87,6 +87,5 @@
             "processed": "<p>You are working on a new feature.<\/p><p>You have two options.<\/p><p>You can commit and deploy a small amount of code every day, using feature flags when needed to show and hide the changes or ensure things aren't broken whilst being developed.<\/p><p>Or, you can wait and deploy everything at once.<\/p><p>Which is the less risky approach?<\/p><p>Which, if there is an issue, would make it easier to find and fix it?<\/p><p>Is it quicker to find an issue in tens of lines of code, or hundreds or thousands?<\/p><p>Is it simpler to disable a feature flag to hide the changes or roll back by reverting the commits, re-deploying the code and going through the same process again?<\/p><p>Which would you choose?<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json b/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json
index f3504b034..dad2c2518 100644
--- a/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json
+++ b/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When I'm working as part of a Development team, working on open source projects, watching live streams or reading code that people have released online - such as their website or dotfiles - I read a lot of other people's code.<\/p>\n\n<p>It's an opportunity to learn from others and how they approach things.<\/p>\n\n<p>How they achieved a desired result or fixed a bug, which I can learn from.<\/p>\n\n<p>I can refer to it if I need to do something similar in the future.<\/p>\n\n<p>Or I may find something random that's I didn't know I needed, such as a module, library or configuration setting I wasn't aware of.<\/p>\n\n<p>I recently learned about .mailmap files from Greg Hurrell (wincent)'s dotfiles on GitHub.<\/p>\n\n<p>.mailmap is a file that is used by Git when displaying history, such as running <code>git log<\/code>, and allows you to define canonical names and email addresses for committers and contributors.<\/p>\n\n<p>I've accidentally used the wrong email address or typed my name incorrectly before in my Git configuration, which was there for all to see, but this file allows me to consolidate my identities within a repository so my commits are grouped together and attributed to me, regardless of which email address I used or how I wrote my name.<\/p>\n\n<p>You can see <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/src\/commit\/633e11abedfa4cc8d85d37695c1ca014874fd4c1\/.mailmap\">the one I added to my website directory<\/a>.<\/p>\n\n<p>If I hadn't looked at that repository, I wouldn't have learned about it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "87636a91b190a3f76a189dfb1cfa6e92",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4d1139c2-0183-4670-af08-003694dec455.json b/content/node.4d1139c2-0183-4670-af08-003694dec455.json
index eec731075..227c71cf2 100644
--- a/content/node.4d1139c2-0183-4670-af08-003694dec455.json
+++ b/content/node.4d1139c2-0183-4670-af08-003694dec455.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've worked on various teams over the last 13 years on which we've needed to do feature branches, pull requests and code reviews.<\/p>\n\n<p>If the request isn't approved by (usually) two people, it won't be merged.<\/p>\n\n<p>Instead of focusing on the problem that needed to be solved and how I'd done it, many reviews focused on the small details.<\/p>\n\n<p>Do the lines have the correct number of spaces before them?<\/p>\n\n<p>Do the comments end with a full stop?<\/p>\n\n<p>Do the lines wrap at the correct point, and are your variable names in the right case?<\/p>\n\n<p>Essentially, does the code comply with the agreed coding standards?<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Whilst important (you want the code to follow standards and be in a consistent format), doing these checks manually is not a good use of time and is not what the code review should focus on.<\/p>\n\n<p>These checks can be automated using CI pipelines or Git hooks to run tools like PHPCS to review and sometimes fix coding standards issues.<\/p>\n\n<p>Automating these checks means the Developers can focus on what they should be reviewing.<\/p>\n\n<p>How are they solving the problem, not how many spaces is the code indented by.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "629f68f940bdb03dfa139e991ac3b2b1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json b/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json
index 8de5aed55..1c2013b49 100644
--- a/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json
+++ b/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since looking more into Astro, I was looking through the GitHub repository - specifically within the examples - and spotted a typo within the title of one of the examples.<\/p>\n\n<p>Rather than leaving it, I decided to follow the \"boy-scout rule\" and submit a fix and leave the code in a better state than I found it.<\/p>\n\n<p>The Astro repository is hosted on GitHub so I was able to fork the repository, fix the typo and create a pull request with a few clicks in the GitHub UI.<\/p>\n\n<p>Contributing to open-source software - particularly if you're new to it - doesn't mean that you need to always add large and complex changes. Small changes such as fixing a typo, updating documentation, fixing a small bug, or adding additional tests are all valid contributions that improve open-source projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "63159fd033bcf1d7e3129da389c832f2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4d270194-23a5-445f-8b66-5ee347054400.json b/content/node.4d270194-23a5-445f-8b66-5ee347054400.json
index 77132aaf5..e3849332f 100644
--- a/content/node.4d270194-23a5-445f-8b66-5ee347054400.json
+++ b/content/node.4d270194-23a5-445f-8b66-5ee347054400.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whilst it's probably impractical to feature flag every new feature or change to your application, considering it is something I do for each change.<\/p>\n\n<p>If you find a bug after a feature has been released, if it's feature flagged, you can quickly disable it without needing to make a code change or release another version.<\/p>\n\n<p>Instead of needing a rollback plan for a release and reverting to the previous version, it can be as simple as disabling the feature flag again to turn it off whilst the cause is investigated.<\/p>\n\n<p>There is a maintenance overhead to adding a feature flag, and it can cause complexity by creating separate paths within the code but using feature flags gives a lot of benefits too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b9604073a92a4e15df6ba36f167ff649",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json b/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json
index a0a3909ca..6b6e8fcbd 100644
--- a/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json
+++ b/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It's been almost five years since I gave the first version of my \"<a href=\"http:\/\/default\/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS<\/a>\" talk at the Drupal Bristol meetup in January 2018.<\/p>\n\n<p>It's a talk that I've updated every time I've given it, showing new rebuilt example UIs and the new features in the framework, as well as tweaking content like installation steps for different audiences.<\/p>\n\n<p>As I prepare for the Norfolk Developers Conference (nordevcon) next month, I'm updating the talk again.<\/p>\n\n<p>One feature that wasn't in the last version of the talk is arbitrary values in class names. This, I think, is an antipattern and something that I avoid using.<\/p>\n\n<p>Whilst you could always add arbitrary values in custom CSS, one of my original reasons for liking and adopting Tailwind CSS was that there was a predefined list of classes to choose from.<\/p>\n\n<p>A set list of colours, text sizes, margins and padding, for example, meant that UIs looked more consistent and the generated CSS was smaller.<\/p>\n\n<p>If you need an additional value or to replace the existing values, you can do so within your <code>tailwind.config.js<\/code> file, and Tailwind will generate classes accordingly.<\/p>\n\n<p>Whilst writing custom CSS, inline styles, and arbitrary values are all possible, I'd suggest using the configuration file, generating the classes that you need, and sticking to them as much as you can and enjoying the consistency and benefits that brings.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6922005e460c87b7b1c677699162005b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json b/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json
index c929b73fa..931307a43 100644
--- a/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json
+++ b/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/11\/16\/an-interesting-thing-i-spotted-about-the-override-node-options-module\">In yesterday's email<\/a>, I showed some of the usage numbers of the Override Node Options module and how the current numbers match those around a year ago.<\/p>\n\n<p>Whilst the overall numbers are similar, there are a lot less Drupal 7 installations of the module and around the same number more Drupal 8+ installations.<\/p>\n\n<p>Somewhere I was happy to see it being used recently is within the <a href=\"https:\/\/localgovdrupal.org\/products\/microsites\">LocalGov Drupal microsites distribution<\/a>.<\/p>\n\n<p>It's great when being brought into a project to see your modules being used, but it's fantastic to see a module I maintain and code that I wrote being used by a large distribution like LocalGov Drupal and benefiting local councils and people in the UK and Ireland.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "abbf5f0e4c7e129fc05e499228722a6f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json b/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json
index 5110b8d76..12d6f7635 100644
--- a/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json
+++ b/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2023\/02\/08\/fetching-api-data-with-astro\">fetching API data<\/a>, you can also use Astro to generate your own API endpoints.<\/p>\n\n<p>This is an example of an endpoint that I recently created as part of a demo application:<\/p>\n\n<pre><code class=\"javascript\">\/\/ trains.json.ts\n\nimport data from \"@\/data.json\";\nimport type { APIRoute } from \"astro\";\nimport type { Train } from \"@\/types\";\n\nexport const get: APIRoute = () =&gt; {\n  return {\n    body: JSON.stringify(data.trains as Train[]),\n  };\n};\n<\/code><\/pre>\n\n<p>The train data is imported from a JSON file, and Astro's <code>APIRoute<\/code> is responsible for setting the appropriate response headers.<\/p>\n\n<p>For server-side rendered applications, you can also have endpoints for <code>post<\/code>, <code>del<\/code> and <code>all<\/code>, though for this example, I only needed to support GET requests.<\/p>\n\n<p>This is something that I've used a db-json library for previously, but being able to do this in Astro seemed like a good fit as I can easily manage lists of stations as well as a single station from one JSON file but I can just take the static HTML that Astro generates and upload it to a static hosting solution which simplifies the hosting side of things a lot.<\/p>\n\n<p>And, as the example application that consumes the data is also written with Astro, having them both using the same solution has advantages too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c6a3315ecb8173fc096250981c691fbe",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json b/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json
index 3219f29ad..a6890ebf9 100644
--- a/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json
+++ b/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Another common Git issue I see is people using <code>git add .<\/code> to commit every change in every file they have locally.<\/p>\n\n<p>Similar to <a href=\"http:\/\/default\/daily\/2025\/04\/02\/commit\">committing with <code>-m<\/code><\/a>, this seems to be a common in Git tutorials, but can have consequences due to unexpected changes being staged and committed.<\/p>\n\n<p>Maybe there are unrelated changes in the same file or other files have been changed that you don't want to commit yet.<\/p>\n\n<p>What if something was committed and pushed that caused the CI pipeline to fail or break production?<\/p>\n\n<p>At the least, it's going to add time and delay getting the intended changes live as someone will need to revert and fix the commits or address the changes in a code review.<\/p>\n\n<p>I'm very selective about what I include in each commit to keep my code stable and the commits easy to review and, if needed, revert.<\/p>\n\n<p>I always use <code>git add -p<\/code> to interactively stage changes from the command line or use keybindings in my Neovim configuration to add particular lines.<\/p>\n\n<p>I'll also review my staged changes before committing and the commit once it's been made using <code>git log --stat<\/code> to see what's included.<\/p>\n\n<p>Only once I'm sure my commits include only what I intended will I push them or submit them for review.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "397621c34a88f800e52750829b4bc177",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json b/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json
index 5d5ff7982..64a1181df 100644
--- a/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json
+++ b/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently made a change to a Drupal project with several custom modules.<\/p>\n\n<p>As part of the change, there was a method that was no longer being used, so I went ahead and removed it.<\/p>\n\n<p>There were no tests for this part of the codebase, and the existing tests were still passing.<\/p>\n\n<p>My change was successfully finished and deployed, including removing the unused method.<\/p>\n\n<p>A few days later, we noticed cron jobs were no longer running on the website.<\/p>\n\n<p>The method I'd removed was attempting to be called from within a different module.<\/p>\n\n<p>Because it no longer existed, it was causing an error and stopping the cron job from running successfully.<\/p>\n\n<p>When I re-added the method, the cron jobs worked again.<\/p>\n\n<p>There were no <code>dependencies<\/code> set in either module's .info.yml file, though that would only prevent you from uninstalling either module.<\/p>\n\n<p>It wouldn't prevent me from deleting code used by another module.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is why I've been <a href=\"http:\/\/default\/daily\/2024\/02\/08\/experimenting-with-architectural-testing\">experimenting with architectural testing<\/a>. To ensure that modules only use their own code and to start enforcing layers within each module.<\/p>\n\n<p>Then, if I had the same situation again, I'd know straight away that there was an issue and not have to wait for the bug to be deployed to production.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ac7bcb6f2dcaec78fb9959f65d264b1f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json b/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json
index 96751c236..13a0de170 100644
--- a/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json
+++ b/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Have you worked on some code, whether it's to add or extend functionality or fix a bug and thought, \"This would be much easier if...\"?<\/p>\n\n<p>A quote by Kent Beck:<\/p>\n\n<blockquote>\n  <p>For each desired change, make the change easy (warning: this may be hard), then make the easy change<\/p>\n<\/blockquote>\n\n<p>If you can refactor the code and make it easier to implement your required change, do so.<\/p>\n\n<p>Any automated tests should be passing before and after, and I'd commit the refactored code to ensure any CI pipelines and checks are still passing.<\/p>\n\n<p>Then, go ahead and make the required change - add the feature or fix the bug - which should now be easy.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0758277d9d9ff772a843ca188916ffa7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json b/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json
index 8d1d71e0b..a3defd326 100644
--- a/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json
+++ b/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This was one of the key takeaways for me from DHH's <a href=\"https:\/\/www.youtube.com\/watch?v=-cEn_83zRFw\">keynote talk from Rails World 2024<\/a>.<\/p>\n\n<p>It's more fun to be competent.<\/p>\n\n<p>In this section of the talk, which starts around 32:45, he was speaking about his move from the Cloud to on-prem infrastructure and adopting Linux as his main development environment.<\/p>\n\n<p>That people suffer from \"server-phobia\" when they could learn these skills from themselves.<\/p>\n\n<p>As a self-taught Developer, I started to learn coding in 2010 and had to learn everything from scratch - starting with HTML and CSS before introducing PHP.<\/p>\n\n<p>Since then, I've learned various other related technologies, including Linux, and exclusively run Linux for my computers and servers.<\/p>\n\n<p><a href=\"http:\/\/default\/blog\/going-full-vim\">I switched full-time to Neovim<\/a> in 2021.<\/p>\n\n<p>For the past couple of years, I've been using NixOS as my primary operating system.<\/p>\n\n<p>It was another language to learn and a different way to think about server configuration and automation.<\/p>\n\n<p>But, I recently went to add something to my configuration and knew exactly how I was going to implement it.\nI was able to do it quickly and easily as I'd invested enough time to be competent and feel confident and that I knew what I was doing.<\/p>\n\n<p>I've been writing a new Drupal module this week and have been in a constant flow state as I knew how I need to implement it.<\/p>\n\n<p>I've been doing test-driven development and working through a few different iterations, guided by my tests and ensuring I don't break what I've already written.<\/p>\n\n<p>These are skills and knowledge that that took time to learn.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Whether you're a new Developer getting into programming or an experienced Developer learning something new, you will become competent.<\/p>\n\n<p>And it is more fun.<\/p>\n\n<p>It just takes time and effort.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cb4f6ebcd079c83203db842b57e9d34f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json b/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json
index 90684d27d..4f0e5bba7 100644
--- a/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json
+++ b/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the initial negatives when Drupal 8 launched was introducing Composer, PHP's dependency manager, and how it could affect non-technical users.<\/p>\n\n<p>When I started doing Drupal, I downloaded the .tar.gz or .zip file of Drupal, extracted it, and placed it within my project.<\/p>\n\n<p>I did the same for any additional modules I needed.<\/p>\n\n<p>To update them, I needed to delete my files and repeat the process of downloading and replacing them.<\/p>\n\n<h2 id=\"drush\">Drush<\/h2>\n\n<p>Then, instead of doing it manually, I used Drush, the \"Drupal shell\", to download the files. This saved some time, but it still has down-sides.<\/p>\n\n<p>What if you needed to install a module like Pathauto, which has dependencies you also need to download and install?<\/p>\n\n<p>With Drush or downloading the files manually, you'd need to download the dependencies separately.<\/p>\n\n<h2 id=\"composer\">Composer<\/h2>\n\n<p>Composer is a dependency manager, which means it can handle these dependencies for us.<\/p>\n\n<p>It looks at each project's <code>composer.json<\/code> file to find its dependencies and downloads them.<\/p>\n\n<p>For example, to install Pathauto, you run <code>composer require drupal\/pathauto<\/code>.<\/p>\n\n<p>Within its output, you'll see this:<\/p>\n\n<pre><code class=\"language-plain\">Package operations: 3 installs, 0 updates, 0 removals\n  - Downloading drupal\/token (1.12.0)\n  - Downloading drupal\/ctools (4.0.4)\n  - Downloading drupal\/pathauto (1.12.0)\n<\/code><\/pre>\n\n<p>As well as Pathauto, it's downloading its dependencies - ctools and pathauto.<\/p>\n\n<p>Instead of downloading three modules, we can do it with one command.<\/p>\n\n<p>In fact, we don't need to know what its dependencies are - Composer will do that.<\/p>\n\n<p>Also, updating the modules is just another simple command - <code>composer update<\/code>.<\/p>\n\n<p>While it may be intimidating to non-technical users, learning a few simple commands makes installing and updating modules much easier!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "18b329b870189395601442a5d226290c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json b/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json
index 1354aa98c..e8f9d2fb5 100644
--- a/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json
+++ b/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common question is which [Git] branch should be on which environment.<\/p>\n\n<p>Most projects I've worked on have two or more environments: production, staging (or test) and development.<\/p>\n\n<p>Earlier in my career, we used Git Flow heavily. A Git branching workflow based on having different branches - i.e. <code>develop<\/code>, <code>master<\/code> and any arbitrary short-lived feature, hotfix and release branches.<\/p>\n\n<p>These matched nicely with our three environments.<\/p>\n\n<p>Usually, the <code>develop<\/code> branch would be used in the development environment. The <code>master<\/code> branch would be on staging and a tagged release from <code>master<\/code> on production.<\/p>\n\n<h2 id=\"what-about-now%3F\">What about now?<\/h2>\n\n<p>I prefer trunk-based development, where there is one long-lived branch to which everyone commits their changes.<\/p>\n\n<p>There's only one branch, so you can either follow continuous deployment and use the same branch for all environments - including production - or separate production using a dedicated branch or tag if you need more control.<\/p>\n\n<p>The mainline branch is used in all pre-production environments, such as staging and development.<\/p>\n\n<h2 id=\"what-about-differences-between-the-environments%3F\">What about differences between the environments?<\/h2>\n\n<p>What if we need differences, such as a feature that must be enabled in a particular environment if the same code is on both?<\/p>\n\n<p>My go-to approach is feature flagging, and this approach is something I'll describe more in tomorrow's email.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3b27ec6a81d5e6dcf310dfe3e6204b69",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json b/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json
index 6fdfa0129..b6d7b14df 100644
--- a/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json
+++ b/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As a Software Developer, it's common to hear that you need to ask questions to progress or work efficiently.<\/p>\n\n<p>You shouldn't just ask technical questions, though.<\/p>\n\n<p>Also ask questions like:<\/p>\n\n<ul>\n<li>What do we want to achieve by delivering this feature?<\/li>\n<li>How do we know if it's a success (or not)?<\/li>\n<li>What business value does this add and who will benefit?<\/li>\n<li>Why do this now? Why not wait a few months or not do it at all?<\/li>\n<li>Is there an existing solution for this?<\/li>\n<li>Can we achieve the same or a similar result in a different way?<\/li>\n<\/ul>\n\n<p>As well as knowing how to do something, it's important to know why it needs to be done.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f0c3d6e951782cfb763d893c57d2dced",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json b/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json
index 1198ab660..4db89dfc9 100644
--- a/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json
+++ b/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, whilst speaking about Sculpin at PHP South West, I showed an example from a client project I'd built with Sculpin.<\/p>\n\n<p>The project was for a local gym and fitness centre, and I was demonstrating how I'd created the timetable page and kept the data separate from the HTML and Twig markup so the client could easily administer it (they edit the files on GitHub, which triggers a rebuild of the website).<\/p>\n\n<p>Each class should have a name and start and end times and be on a specified day.<\/p>\n\n<p>But what if the client didn't include a name or start or end time?<\/p>\n\n<p>What if they put a number or boolean instead of a string?<\/p>\n\n<p>What if there are no classes on a particular day?<\/p>\n\n<p>You don't know how people will use your software, so it's best to be defensive - validate and verify things before rendering them and prevent the page or whole application from breaking if something isn't as you expected or assumed.<\/p>\n\n<p>We also can't assume the \"happy path\" will always be correct.<\/p>\n\n<p>What if there aren't any classes? Do we put an empty message on the timetable or not show that day?<\/p>\n\n<h2 id=\"another-scenario\">Another scenario<\/h2>\n\n<p>If you were retrieving or posting data to an API endpoint, would you assume it was successful or verify the response code is what you expected?<\/p>\n\n<p>If you get the data, do you check if it's in the correct format and something you can use?<\/p>\n\n<p>If not, do you verify other actions in your application haven't run and it's not in an invalid state?<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>In PHP, a common approach is to use the <code>assert()<\/code> function, as we saw in <a href=\"http:\/\/default\/daily\/2024\/02\/20\/which-level-is-right-for-you\">yesterday's email<\/a>.<\/p>\n\n<p>Then, write automated tests that don't test just the happy path but also the unhappy paths.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0c791781778c8aeadb8f49363376f730",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json b/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json
index eea2b1a73..c976085a8 100644
--- a/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json
+++ b/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal used to suffer from a case of \"not invented here\" syndrome.<\/p>\n\n<p>Prior to Drupal 8, all the code within Drupal (with the exception of jQuery, I believe) was written by Drupal Developers.<\/p>\n\n<p>The PHP code was mostly procedural and didn't match how modern PHP code was being written in other projects.<\/p>\n\n<p>There was no other third-party code and we had to rely on downloading zip files from Drupal.org, using <code>drush dl<\/code> or Drush Make - a Drupal-only tool for specifying and downloading the specified versions of Drupal and other modules you were using - to get the latest updates.<\/p>\n\n<p>Drupal.org has its own Git hosting, testing infrastructure and issue queues.<\/p>\n\n<p>Luckily, since Drupal 8's release in 2015, this has been changing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7f6dcf1b5ac7259908a71513a4e6b908",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json b/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json
index 855dd47ac..0b95442a8 100644
--- a/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json
+++ b/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, after saying I wanted to get back into it, I did my first live coding stream in over two years.<\/p>\n\n<p>I spent around an hour and a half working on <a href=\"http:\/\/default\/build-configs\">Build Configs<\/a> - a Symfony command line application I wrote to generate build configuration files.<\/p>\n\n<p>To learn more about it, I <a href=\"http:\/\/default\/presentations\/building-build-configs\">gave a meetup talk<\/a> about it recently.<\/p>\n\n<p>On stream, I explained what Build Configs is, added a <code>--dry-run<\/code> option that prevents any files from being created and started to look again at Behat to see how I might use it to test the app's functionality.<\/p>\n\n<p>I want to do at least one stream a week going forward. Most likely, it will be on Friday afternoons.\nYou can <a href=\"https:\/\/www.youtube.com\/watch?v=Wlkcf1PLWN8\">watch the full stream<\/a> on YouTube now. I'll split it into sections this week and upload some lightly edited versions to the same channel.<\/p>\n\n<p>I won't post a link to every video here, so please subscribe to my YouTube channel to be notified when I go live next.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e93ad68bebb864569d626ff3d30d67bc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json b/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json
index 71ed7090d..a9988c286 100644
--- a/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json
+++ b/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you're unsure what your first test should be, start by writing a test with an intentionally vague name, just to get you started.<\/p>\n\n<p>It may not be clear straight away what you're trying to test.<\/p>\n\n<p>Once you get the ball rolling and you write more, it will usually become clear.<\/p>\n\n<p>Then you can go back and rename the test method to something more specific.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "019e5d597f894b924aac0c6b461b07fd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json b/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json
index 04608307e..26a0092af 100644
--- a/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json
+++ b/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently said that <a href=\"http:\/\/default\/daily\/2024\/11\/30\/using-nix-for-local-application-development\">I've been using devenv to run Drupal applications locally<\/a>.<\/p>\n\n<p>Here's the <code>devenv.nix<\/code> file I used for <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">my recent talk for the Drupal London meetup<\/a>:<\/p>\n\n<pre><code class=\"nix\">{ pkgs, ... }:\n\nlet\n  drupal.root = \"web\";\nin\n{\n  packages = [ pkgs.git ];\n\n  dotenv.disableHint = true;\n\n  languages = {\n    php = {\n      enable = true;\n      version = \"8.2\";\n\n      ini = ''\n        memory_limit = 256M\n      '';\n\n      fpm.pools.web = {\n        listen = \"127.0.0.1:9000\";\n\n        settings = {\n          \"pm\" = \"dynamic\";\n          \"pm.max_children\" = 75;\n          \"pm.max_requests\" = 500;\n          \"pm.max_spare_servers\" = 20;\n          \"pm.min_spare_servers\" = 5;\n          \"pm.start_servers\" = 10;\n        };\n      };\n    };\n  };\n\n  processes = { };\n\n  services = {\n    caddy = {\n      enable = true;\n\n      config = ''\n        {\n          http_port 8080\n        }\n\n        localhost:8080 {\n          root * ${drupal.root}\n          encode gzip\n          php_fastcgi localhost:9000\n          file_server\n        }\n      '';\n    };\n\n    mysql = {\n      enable = true;\n      initialDatabases = [ { name = \"drupal_london\"; } ];\n    };\n  };\n\n  enterShell = ''\n    if [[ ! -d vendor ]]; then\n      composer install\n    fi\n  '';\n\n  enterTest = ''\n    phpunit --testdox\n  '';\n}\n<\/code><\/pre>\n\n<p>It installs the required version of PHP for this project, creates a web server (Caddy) and configures MariaDB with a default database.<\/p>\n\n<p>I've also added commands to run <code>composer install<\/code> to download dependencies when entering the shell and <code>phpunit<\/code> for tests.<\/p>\n\n<p>With this approach, there's no need for containers as everything is run locally and I can view the site at <a href=\"http:\/\/localhost:8080\">http:\/\/localhost:8080<\/a> (or whatever port is defined).<\/p>\n\n<p>All of my current development projects are using this approach and I think it'll be my default method for future projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "47f25a425d659c954d97d5112ac43a64",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json b/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json
index 7c8aeb92a..7c7562fb5 100644
--- a/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json
+++ b/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In my <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">talk about automated testing and test-driven development<\/a>, I speak about a custom module I wrote for a client's Drupal project.<\/p>\n\n<p>It was to integrate with a third-party job application system that they would log into and enter information via a form (similar to Drupal's node forms) that they wanted to appear on the Drupal website.<\/p>\n\n<p>Once submitted, the system would send a POST request to an endpoint provided by the custom module. The module would process it and create the job node with the appropriate field values.<\/p>\n\n<p>I wrote automated tests and did test-driven development.<\/p>\n\n<p>Everything worked great for a few weeks or months.<\/p>\n\n<p>Later, we had a message from the client saying the integration was broken and we needed to fix it.<\/p>\n\n<p>I don't think I'd worked on this module for a while, but I was concerned that a Drupal core update or another change could have caused a regression.<\/p>\n\n<p>The first thing I did was run the tests I'd written and verify they still passed, which they did.<\/p>\n\n<p>This confirmed that as long as the data was being sent in the expected format, the node would be created and the integration would work.<\/p>\n\n<p>Due to an upstream issue, the data was no longer in the expected format, which meant the node could not be created.<\/p>\n\n<p>Once it was fixed, everything started working again.<\/p>\n\n<p>My debugging time was practically zero as I was able to rely on my tests and that they were still passing.<\/p>\n\n<p>I could confidently tell the client that the issue wasn't with our code and must've been an third-party issue.<\/p>\n\n<p>Writing tests takes some time, but having tests saves time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8f98e53db611d2a06dded4a390a73ab4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json b/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json
index 7fa2a203f..70ce9723f 100644
--- a/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json
+++ b/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm often asked by people what the first test is they should write in their application.<\/p>\n\n<p>Matt Stauffer asked in previous talks at Laravel conferences and podcasts:<\/p>\n\n<p>What would get you fired or your company in the news for a bad reason?<\/p>\n\n<p>That seems like a good place to start.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a1e1e81b117aed3458e6cb11e916a04b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json b/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json
index 990db5d10..6ee0f922a 100644
--- a/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json
+++ b/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The Drupal Association recently launched the \"Adopt a Document\" program for Drupal.org, making documentation pages available for adoption.<\/p>\n\n<p>From <a href=\"https:\/\/www.drupal.org\/about\/starshot\/blog\/adopt-a-document-new-program-to-bring-drupal-documentation-to-the-next-level\">the blog post<\/a>:<\/p>\n\n<blockquote>\n  <p>Inspired by the \u201cAdopt a Highway\u201d program that is becoming more and more popular in North America, we created a way for the partners to get involved in creating great documentation by taking care of one of the Drupal CMS milestones and sponsoring creation and further maintenance of the documentation for one or multiple Drupal CMS working tracks.<\/p>\n  \n  <p>Thanks to your support, future users of Drupal CMS will be able to easily find answers to the questions that might arise as they discover Drupal CMS capabilities.<\/p>\n<\/blockquote>\n\n<p>I think this is a great way for Drupal's documentation to continue improving and to give companies another way to contribute to the Drupal project.<\/p>\n\n<p>If you were looking for a way to contribute to Drupal, this may be a good option.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b063958005e2aa3015d2060e0878c0aa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json b/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json
index 3f0be2074..8734627d1 100644
--- a/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json
+++ b/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You've been asked to add a new feature to or refactor some existing code.<\/p>\n\n<p>Assuming you have automated tests already (if not, why not?), before you change the code, you should ask whether they're good enough.<\/p>\n\n<p>They need to be passing, but do you feel confident the existing functionality will still work after you make your changes?<\/p>\n\n<p>Do you have all the existing use cases covered?<\/p>\n\n<p>If so, carry on.<\/p>\n\n<p>If not, spend some time improving your tests first to get that confidence before making any changes.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0ceafa8785ee51630825fb772ad853a6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json b/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json
index 2d3c79cd3..502d068ae 100644
--- a/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json
+++ b/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Once you've <a href=\"http:\/\/default\/daily\/2024\/09\/02\/no-one-sees-your-clean-up-commits\">cleaned up and tided your commits<\/a>, re-ordered them and squashed any commits together to combine them into logical changes, before you push them, you should also check if your commit messages still make sense.<\/p>\n\n<p>Using short or generic commit messages is fine when spiking a solution in very short feedback loops, but when you push your changes, you want them to be as descriptive and meaningful as possible.<\/p>\n\n<p>If someone ran <code>git log<\/code> weeks, months or years from now, would they get value from reading the commit messages?<\/p>\n\n<p>Are you using the subject and body correctly and wrapping text when needed?<\/p>\n\n<p>Does each message accurately reflect and describe the change?<\/p>\n\n<p>Does it capture why the change is needed, any alternative approaches that we considered or tried, or any complications that were encountered?<\/p>\n\n<p>If you're following a standard like <a href=\"http:\/\/default\/daily\/2022\/09\/01\/conventional-commits-changelogs\">conventional commits<\/a>, have you correctly included the required information, such as the type, scope and any references, such as the task reference?<\/p>\n\n<p>Having a Git log with detailed history is valuable when you need to review the changes in the future, but it also makes it more likely your changes will be approved and merged, whether you're working on a paid project or volunteering on an open-source project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "674c9c37b7fd93e1d85171115f3aec2a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json b/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json
index d8d4da578..479642b3e 100644
--- a/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json
+++ b/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>An argument against the <a href=\"http:\/\/default\/daily\/2023\/12\/01\/the-contribution-first-workflow\">contribution-first and open-source-first approach<\/a> is that it takes longer than writing custom code.<\/p>\n\n<p>I think that this is due to thinking that you need to cover all use cases within the code if it's open-sourced, whereas, in custom code, you only write the code you need.<\/p>\n\n<p>My approach is to write the same code, whether it's private and custom or open-sourced.<\/p>\n\n<p>The code is based on the same set of requirements, and the only code that should be written should be enough to satisfy those requirements.<\/p>\n\n<p>It doesn't get written if something isn't part of that objective.<\/p>\n\n<p>It could be added to a public roadmap for the future if it doesn't need to be part of the initial minimal version.<\/p>\n\n<p>If someone creates an issue to request new functionality or submits a pull request to contribute potential changes, you decide whether to accept or reject it or even add them as a maintainer to manage their own contributions as well as administrative tasks like managing the issue queues.<\/p>\n\n<p>If you accept their code, you get the benefit of it (though you also need to maintain and own it) or, if you reject it, you can continue focusing on your minimum-viable version for its initial project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0b1a8be5345c3efb403f70fca1daabbf",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json b/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json
index 30e3e59e0..119446fbf 100644
--- a/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json
+++ b/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Recently I <a href=\"https:\/\/twitter.com\/OneJKMolina\/status\/1303047499238776832\">saw this tweet<\/a> in a screenshot on a LinkedIn post.<\/p>\n\n<p>The post was about improving business writing, but the original tweet was about software engineering.<\/p>\n\n<p>For me, the main sentence within the tweet is, \"Resist the urge to do something before having a plan.\" - or as the LinkedIn post said, \"Resist the urge to start typing before having a plan.\".<\/p>\n\n<p>This is something that I've focused on a lot over the last few years, always asking, \"What problem are we trying to solve?\" and using flow charts and ADRs or technical design documents to come up with a plan before starting to write any code.<\/p>\n\n<p>Doing this makes me think of and answer as much as possible upfront - what we need, how things should work, the required steps, and what edge cases and pitfalls there might be. I'll usually have two or three solutions I'll consider and document, as well as which I decided to use and why.<\/p>\n\n<p>Once I've planned the solution, coding is usually very fast and straightforward, as most or all questions should already have been answered. I don't need to stop and answer questions whilst writing the code, and the code should be cleaner as I'm coding to the plan rather than figuring it out as I go.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a856af7f62fcf490200ee880fa6e6f73",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json b/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json
index 481578c58..231bb4841 100644
--- a/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json
+++ b/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I wrote about <a href=\"http:\/\/default\/daily\/2024\/06\/13\/vetting-third-party-open-source-software\">some things I look for when evaluating open-source projects<\/a>.<\/p>\n\n<p>One thing I said was \"When was the most recent commit and release?\".<\/p>\n\n<p>If a project hasn't had many recent commits, it could be outdated or no longer supported.<\/p>\n\n<p>Alternatively, it could be considered feature complete and not getting new features, and only getting bug fixes and maintenance updates.<\/p>\n\n<p>I see this a lot with Vim plugins that were written several years ago and are now minimally maintained and updated, but getting no new features.<\/p>\n\n<p>This happens in the Drupal space, too, when people wrote a module for a project which they have since completed, or no longer work with that client or for that company.<\/p>\n\n<p>If there are at least commits for security compatibility, such as new versions of PHP or node, that's a sign the project is in a maintenance phase.<\/p>\n\n<p>If there are no recent commits, the project could be dead and I'd carefully consider if you want to add or use it.<\/p>\n\n<p>Something that could help is if maintainers are explicit about what state their project is in.<\/p>\n\n<p>Add a note to the README.md or CONTRIBUTING.md file saying if the project is feature complete or what the maintenance state is.<\/p>\n\n<p>If the project is no longer maintained, you can also document it and potentially archive the repository too to show that it will no longer be updated and to avoid confusion.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5b8c0219dc018568e03908b9744aff46",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.54108c84-c648-4c91-92c6-816711878a4f.json b/content/node.54108c84-c648-4c91-92c6-816711878a4f.json
index 504209663..8aa5b9757 100644
--- a/content/node.54108c84-c648-4c91-92c6-816711878a4f.json
+++ b/content/node.54108c84-c648-4c91-92c6-816711878a4f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Are you responsible for creating and maintaining resources like GitHub repositories, DigitalOcean servers, Amazon S3 buckets and Cloudfront distributions or DNS records in Cloudflare?<\/p>\n\n<p>Do you do that through the various web UIs?<\/p>\n\n<p>I'd recommend looking into infrastructure as code tools such as Ansible, Terraform and Pulumi.<\/p>\n\n<p>You can create, manage and destroy these resources by writing text files rather than clicking around in web UIs, which you can store and share using version control tools.<\/p>\n\n<p>Infrastructure as code (IaC) tools are something that I use when working with infrastructure, whether it's for a client project or <a href=\"https:\/\/github.com\/opdavies\/rebuilding-acquia\/blob\/4efe94398f4d8715d22ca677756beb36017d4e74\/main.tf\">a talk demo<\/a> (this uses Terraform to create an Amazon S3 bucket and Cloudflare distribution, link it to an SSL certificate and create my DNS records - all automatically).<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2971b28664070325dea116a96e60f866",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json b/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json
index 7db3ce20d..783aa52ce 100644
--- a/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json
+++ b/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It's been a while since I used Ansible.<\/p>\n\n<p>I used it for automating infrastructure and deploying applications.<\/p>\n\n<p><a href=\"http:\/\/default\/presentations\/deploying-php-ansible-ansistrano\">I gave a talk about it<\/a> on several occasions, including remotely for the Ansible London meetup during COVID.<\/p>\n\n<p>I haven't had to use it recently but, today, I <a href=\"https:\/\/github.com\/opdavies\/oliverdavies.uk\/commit\/cd6575c6fcc091a0b7c98b6985b3a92b85e279e3\">brought it back<\/a> out of my toolkit.<\/p>\n\n<p>I was reviewing how I manage my website's configuration and files and Ansible seemed to be a perfect choice.<\/p>\n\n<p>The files need to be uploaded to the server and, to handle redirects, I also have a custom NGINX virtual host configuration that needs to be uploaded if I change it and the NGINX service reloaded.<\/p>\n\n<p>Ansible is a great tool for this type of task and, just because it's a tool I haven't used it for a while, that doesn't mean I can't re-evaluate it and see if fits my current requirements.<\/p>\n\n<p>It's still in my toolkit, just in case I need it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ea9be0481194a0fa60a57a3ea920440c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json b/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json
index 45c32b221..a076eae11 100644
--- a/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json
+++ b/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week on the Beyond Blocks podcast, I'm joined by Yuri Gerasymov to discuss Diffy visual regression testing.<\/p>\n\n<h2 id=\"talking-points\">Talking Points<\/h2>\n\n<ul>\n<li>What is visual regression testing?<\/li>\n<li>How do you deal with false positives?<\/li>\n<li>Different use cases for visual regression testing.<\/li>\n<li>Automatic updates.<\/li>\n<li>Scheduling content.<\/li>\n<li>Visual regression testing in CI.<\/li>\n<li>Diffy in WordPress.<\/li>\n<li>What's a baseline?<\/li>\n<li>Initial setup and onboarding feedback.<\/li>\n<li>Testing dark mode?<\/li>\n<li>Component testing with Storybook and Fractal?<\/li>\n<li>Testing local environments.<\/li>\n<li>Testing as authenticated users.<\/li>\n<li>The roadmap for Diffy.<\/li>\n<\/ul>\n\n<h2 id=\"quotable-quotes\">Quotable Quotes<\/h2>\n\n<ul>\n<li>We help development teams to have less visual bugs in their website. We take screenshots of the pages and compare them so you can see what changed and how. (YG)<\/li>\n<li>We built tools for you to mock the content. You provide selectors for the elements with the content of the article and we'll replace it with lorem ipsum text so it will be exactly the same across multiple environments. (YG)<\/li>\n<li>I can still write an assertion to check the text is on the page or not, but it won't confirm it's in the correct place. (OD)<\/li>\n<li>Having a tool checking for changes on a regular basis instead of only after a deployment would be very useful. (OD)<\/li>\n<li>So, you could have a tool like Violinst automatically creating pull requests and Diffy checking those PRs, so the two could work together? (OD)<\/li>\n<li>With visual testing, it's very easy to get started. (YG)<\/li>\n<li>Visual testing is great for showing your client your work. (YG)<\/li>\n<\/ul>\n\n<p>I learned a lot during this conversation and have added visual regression testing to my testing toolbox for working on projects.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/14-yuri-gerasymov-diffy\">Listen to the episode<\/a><\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f767e648d91ab4e42156d03ff67f7f6c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json b/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json
index a49ca6251..a36f99a77 100644
--- a/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json
+++ b/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whether you get <a href=\"http:\/\/default\/daily\/2024\/10\/09\/ai-as-a-pair-programming-partner\">a solution from AI<\/a>, GitHub, Stack Overflow or somewhere else, don't blindly copy and paste it.<\/p>\n\n<p>Validate and verify it's the right solution.<\/p>\n\n<p>Process and understand it and its pros and cons so you can decide why and when to use it again in the future.<\/p>\n\n<p>Once you've committed it, you're responsible for it and need to maintain it - regardless of where it came from.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4644916c3b9cfef844fa7c5503ae3b85",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json b/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json
index d03dc2430..8d17628a8 100644
--- a/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json
+++ b/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The survey results from my automated testing and test-driven development session at DrupalCon Lille are in, and here they are:<\/p>\n\n<h2 id=\"how-would-you-rate-the-speakers%27s-mastery-of-this-topic%3F\">How would you rate the speaker(s)'s mastery of this topic?<\/h2>\n\n<p>24 responses.<\/p>\n\n<ul>\n<li>Excellent - 33.3%<\/li>\n<li>Very good - 50%<\/li>\n<li>Good - 16.7%<\/li>\n<li>Fair - 0%<\/li>\n<li>Poor - 0%<\/li>\n<\/ul>\n\n<h2 id=\"how-would-you-rate-the-speakers%27s-presentation-skills%3F\">How would you rate the speaker(s)'s presentation skills?<\/h2>\n\n<p>24 responses.<\/p>\n\n<ul>\n<li>Excellent - 20.8%<\/li>\n<li>Very good - 37.5%<\/li>\n<li>Good - 33.3%<\/li>\n<li>Fair - 8.3%<\/li>\n<li>Poor - 0%<\/li>\n<\/ul>\n\n<h2 id=\"how-would-you-rate-the-speakers%E2%80%99s-slides-and-other-session-materials%3F\">How would you rate the speaker(s)\u2019s slides and other session materials?<\/h2>\n\n<p>25 responses.<\/p>\n\n<ul>\n<li>Excellent - 24%<\/li>\n<li>Very good - 32%<\/li>\n<li>Good - 36%<\/li>\n<li>Fair - 8%<\/li>\n<li>Poor - 0%<\/li>\n<\/ul>\n\n<h2 id=\"overall%2C-how-would-you-rate-this-session%3F\">Overall, how would you rate this session?<\/h2>\n\n<p>25 responses.<\/p>\n\n<ul>\n<li>Excellent - 36%<\/li>\n<li>Very good - 28%<\/li>\n<li>Good - 36%<\/li>\n<li>Fair - 0%<\/li>\n<li>Poor - 0%<\/li>\n<\/ul>\n\n<p>Thanks to everyone who completed the survey for their feedback.<\/p>\n\n<p>P.S. If you'd like your own software development training or coaching, including automated testing and test-driven development, I currently have availability for <a href=\"http:\/\/default\/team-coaching\">team coaching<\/a> and <a href=\"http:\/\/default\/pricing\">private talks and workshops<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a6dfd22ba492a4321428a81447ebc21a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json b/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json
index 769911af5..c6da5bb5d 100644
--- a/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json
+++ b/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of my goals when coding is to reduce the amount of nesting in the code I write.<\/p>\n\n<p>I mean both in my PHP code where if conditions and foreach loops can be nested within each other, and CSS and Sass files, which support nesting CSS rules.<\/p>\n\n<p>My aim is to have a maximum of two or three levels of indentation, though sometimes this isn't possible.<\/p>\n\n<p>Doing so where I can, though, makes my code easier to read and understand and encourages other clean code approaches, such as having small and well-named functions.<\/p>\n\n<p>In CSS or Sass, avoiding nesting makes it easier to find a rule I'm looking for instead of having to find how rules have been nested or names have been concatenated - making it hard to search or grep for a string.<\/p>\n\n<p>This approach is part of \"object callisthenics\", which was introduced by Jeff Bay and includes other approaches that I like to follow, such as not using the <code>else<\/code> keyword and other good practices that I like to try and implement when possible.--<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6f502f1378e2ffcb9acf63bd11ff5325",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json b/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json
index e8fb078f0..87fcd4e71 100644
--- a/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json
+++ b/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Have you been in a situation where you needed to switch something in a project, like the type of database or a payment provider?<\/p>\n\n<p>Today, I decided to switch a project from NGINX to Apache.<\/p>\n\n<p>Usually, this would involve using a different base Docker image, creating new configuration files, and changing things like the root directory for my project.<\/p>\n\n<p>But, because I'd built this into <a href=\"http:\/\/default\/talks\/building-build-configs\">Build Configs<\/a>, I was able to change a few lines in one file, and when I re-generated the configuration files, this project was running Apache.<\/p>\n\n<p>This is an excellent example of why I built this tool: to save time and reduce duplication across my projects.<\/p>\n\n<p>For this change, it did both.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "df8a1f8e4c5825078db0d4b92837624d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json b/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json
index 64f933bb6..e22b89caf 100644
--- a/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json
+++ b/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Over the next few weeks, I'm going to create another email course, this time about building websites with the <a href=\"https:\/\/sculpin.io\">Sculpin static site generator<\/a>.<\/p>\n\n<p>I've been using Sculpin since 2015 when <a href=\"http:\/\/default\/presentations\/test-drive-twig-with-sculpin\">I used it to learn Twig<\/a> before Drupal 8's release and I use it to generate my website.<\/p>\n\n<p>I've recently been <a href=\"http:\/\/default\/presentations\/building-static-websites-sculpin\">speaking about it at user groups<\/a> like PHP South West, BrumPHP and PHP Berkshire.<\/p>\n\n<p>Similar to my <a href=\"http:\/\/default\/atdc\">automated testing email course<\/a>, this will send a lesson every day straight to your inbox and will show how to build a website with Sculpin from scratch.<\/p>\n\n<p>If you want to be added when it's ready or have questions, reply to this email and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6b905a72c2e1be12adf25aea58ea044c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json b/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json
index 35eeca496..a5718777a 100644
--- a/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json
+++ b/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In my <a href=\"http:\/\/default\/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS talk<\/a>, I've described Tailwind as a CSS utility class generator. You write a configuration file that Tailwind reads and generates the appropriate classes.<\/p>\n\n<p>Yesterday I mentioned the <a href=\"https:\/\/phpsw.uk\">PHP South West user group<\/a> website. It's a project that <a href=\"https:\/\/twitter.com\/opdavies\/status\/934488762276564993\">I worked on in November 2017<\/a> and uses Tailwind 0.5.<\/p>\n\n<p>For me, a big advantage of Tailwind was that once it generates the classes, they are ours. They aren't hidden within the framework or an npm package. We can see them, commit them to version control and keep them for as long as we need.<\/p>\n\n<p>Even if the Tailwind CSS framework disappeared tomorrow (I hope it doesn't), I'd be able to continue using the styles that it generated, and my projects would continue to work and look the same.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5856ee99a95c5407d33af80db814c94d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json b/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json
index 61e35c281..9865a044d 100644
--- a/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json
+++ b/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common reason when speaking with Developers who use Linux as their operating system is that their software will run on Linux in production, so it's best to run it on Linux locally.<\/p>\n\n<p>For me, it's more to do with what software I'm using instead of where it's hosted.<\/p>\n\n<p>I develop using open-source software - Git, PHP, Drupal, Sculpin, Vue.js, Ansible, Nix, Tailwind CSS, Neovim - just to name a few, as well as maintaining my own open-source projects.<\/p>\n\n<p>It aligns with my ethos and ethics that my operating system and the applications I use are open-source too, when possible.<\/p>\n\n<p>I use NixOS as my operating system.<\/p>\n\n<p>I develop in Alacritty, tmux and Neovim, and use open-source tools and language servers when coding.<\/p>\n\n<p>I edit podcasts and videos in Kdenlive, and create thumbnails in GIMP.<\/p>\n\n<p>I don't use exclusively open-source tools, but that's my preference.<\/p>\n\n<p>I'm also not locked in to one hardware supplier or one way of doing something.<\/p>\n\n<p>If I want to change to a different window manager or from stable to rolling releases, I can.<\/p>\n\n<p>I can make my tools work for me instead of adapting my workflow around them.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7eb65ae3f24b2f4806b258bdef6f47ae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json b/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json
index 489ee08ee..ca567fb62 100644
--- a/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json
+++ b/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I wrote about <a href=\"http:\/\/default\/daily\/2024\/08\/19\/bash-scripting-for-fun-and-profit\">a bash script I've written<\/a> to export a list of videos on my external hard drive.<\/p>\n\n<p>If you <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\/blob\/a1ef2d1402c9c607e7a3e4427ce125d0cabeddcd\/lib\/shared\/scripts\/export-video-list.nix#L12-L31\">looked at the script on GitHub<\/a> and you're familiar with bash scripting, you may have thought it looked a bit odd or missing some things.<\/p>\n\n<p>That's because I wrote it <a href=\"http:\/\/default\/daily\/2022\/09\/26\/experimenting-with-the-nix-package-manager\">with Nix<\/a> - the tool I've been using for almost two years to manage my dotfiles and operating system configuration.<\/p>\n\n<p>Using Nix for bash scripts has advantages, like automatically adding the shebang line, setting sensible defaults for error handling, and automatically running <code>shellcheck<\/code> when switching.<\/p>\n\n<p>I think the main advantage, though, is it can inject any dependency packages into the script.<\/p>\n\n<p>This script needs <code>tree<\/code> and <code>jq<\/code>, so they are dependencies of the script and the script can't run if they aren't installed.<\/p>\n\n<p>But, I don't need to assume they are available. Nix can do it automatically and make any packages added as build inputs available.<\/p>\n\n<p>Now, if anyone else wanted to use this script, or I wanted to share another script with colleagues or a client, they can use it without needing to install any dependencies separately and the script will continue to work in the future using its explicitly-added dependencies.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b9459e8502e6216a6d8f4cd2842d9bba",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json b/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json
index 8ca56b0f9..97790fdb7 100644
--- a/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json
+++ b/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/talks\">My talks page<\/a> on my website says I've presented 98 talks and workshops at different events since September 2012.<\/p>\n\n<p>Next month, I'm giving two talks at DrupalCamp Ghent.<\/p>\n\n<p>One on <a href=\"http:\/\/default\/talks\/tdd-test-driven-drupal\">automated testing and test-driven development<\/a> and another on <a href=\"http:\/\/default\/talks\/taking-flight-with-tailwind-css\">Tailwind CSS<\/a>.<\/p>\n\n<p>This means that these will be my 99th and 100th presentations!<\/p>\n\n<p>I enjoy speaking at events such as meetups and conferences, and I hope people have learned from them as well.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "46b853586496fec3d554e44ee4bdf81f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json b/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json
index d656da444..a8af3fd97 100644
--- a/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json
+++ b/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the first things I do when reviewing whether an application can be upgraded is to look for anything that can be removed.<\/p>\n\n<p>If it has modules that aren't used, uninstall and remove them.<\/p>\n\n<p>A common one for Drupal projects is modules left from previous migrations, such as from Field Collections to Paragraphs that are no longer needed but still present.<\/p>\n\n<p>Remove any old themes that are no longer used.<\/p>\n\n<p>If you have content types, fields or views that aren't used, remove them, assuming you don't need the data.<\/p>\n\n<p>Remove unused routes, Controllers or other classes not used in custom modules, or any other unused custom code.<\/p>\n\n<p>Less moving parts means less to upgrade now and maintain in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fcd2d826fa4f9caf9ec7194920add0bb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json b/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json
index 1647d8360..cdba19226 100644
--- a/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json
+++ b/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week I learned about the <a href=\"https:\/\/www.drush.org\/13.x\/deploycommand\">drush deploy command<\/a>.<\/p>\n\n<p>It's been available since Drush 10.3 and combines several commands together in an attempt to \"standardise how Drupal deployments work\".<\/p>\n\n<p>These commands are:<\/p>\n\n<pre><code class=\"shell\">drush updatedb\ndrush config:import\ndrush cache:rebuild\ndrush deploy:hook\n<\/code><\/pre>\n\n<p>Usually, I run these commands separately but grouping them and standardising makes a lot of sense.<\/p>\n\n<p><code>drush deploy:hook<\/code> is also very interesting and allows for adding deploy hooks similar to update hooks in .install files.<\/p>\n\n<p>I'm looking forward to updating my deployment pipelines to use this and making them simpler and easier to maintain.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4720dadf7849019a7ca4401ddec374be",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json b/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json
index 60ff77cca..b49ed1ba7 100644
--- a/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json
+++ b/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Inspired by others like rwxrob and Mischa van den Burg, I've started experimenting with the Zettelkasten method of atomic note-taking alongside my current methods.<\/p>\n\n<p>Originally writing notes as text files in Vim, I've decided to <a href=\"https:\/\/zet.oliverdavies.uk\">start publishing them online<\/a>, where possible. The first notes are already there.<\/p>\n\n<p>This will be separate to this email list and will contain notes on various topics, not just programming and software development, although I can imagine some notes progressing to be part of emails sent to this list.<\/p>\n\n<p>The website itself is open-source and <a href=\"https:\/\/github.com\/opdavies\/zet.oliverdavies.uk\">hosted on GitHub<\/a>, and each page has an \"Improve this page\" link to edit that page and submit a pull request on GitHub.<\/p>\n\n<p>The website is a basic <a href=\"http:\/\/default\/presentations\/building-static-websites-sculpin\">Sculpin static site<\/a> with a notes content type.<\/p>\n\n<p>There is no styling yet, as I wanted to focus on deploying the MVP version, but I will add some styling and some additional features in the future.<\/p>\n\n<p>At the moment, I'm focusing on writing as often as possible for this email list and in my new Zettelkasten.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dd0fbfd753d7cc8349477b9e7228c8c4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json b/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json
index ad10ed1a5..8cdb81dcc 100644
--- a/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json
+++ b/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whether you <a href=\"http:\/\/default\/daily\/2024\/09\/19\/the-two-ways-of-writing-php-code\">prefer strict code or not<\/a>, <a href=\"http:\/\/default\/daily\/2023\/04\/19\/camel-case-or-snake-case-for-drupal-code\">use snake-case or camel-case for variable names<\/a> or <a href=\"http:\/\/default\/daily\/2022\/11\/14\/camel-case-or-snake-case-for-test-methods\">how you write your test methods<\/a>, it is important to be consistent in how code is written.<\/p>\n\n<p>If you're working in a file that uses snake-case variable names, you should do the same and follow the same conventions.<\/p>\n\n<p>When reading a file, everything should be consistent and seem like it was written by the same person following the same approaches.<\/p>\n\n<p>Otherwise, when you need to add to or refactor this code in the future, it will be harder to do so.<\/p>\n\n<p>Consistency is key.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "868d9285f3f2c28b801786ad11418bb5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json b/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json
index 2f761e9f3..1ed971ec4 100644
--- a/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json
+++ b/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Many development teams and projects use code coverage - e.g. how many lines of code are covered by automated tests - as an objective, and saying it must be 100% or another percentage.<\/p>\n\n<p>But is this an effective metric?<\/p>\n\n<p>In the same way as deleting failing tests to fix a pipeline, a code coverage amount can be faked.<\/p>\n\n<p>With this in mind, what if, instead of setting an objective such as 100% code coverage, you used it as a guideline?<\/p>\n\n<p>If you're working on a legacy project, what if you set a minimum code coverage amount as a guideline to ensure any new code has tests by not dropping under that level?<\/p>\n\n<p>Would that be better than saying every line of code needs to be covered?<\/p>\n\n<p>Code coverage is something I'm thinking of using more, so I want to know what you think.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "37779b8be562eca580a1d3eb2ead9f83",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json b/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json
index d5ca46221..f9c8dbcc5 100644
--- a/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json
+++ b/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2023\/12\/22\/best-language-cms-or-framework\">In yesterday's email<\/a>, I mentioned using several programming languages and frameworks.<\/p>\n\n<p>Drupal is my main specialism and the one I have the most experience and knowledge of, but you don't need to use only Drupal code.<\/p>\n\n<p>Using Composer, you can add parts of other frameworks to other projects.<\/p>\n\n<p>I don't use Laravel often as a full-stack framework, but I use the Collections library, and recently the Pipelines library, in almost every project - whether it's Drupal or Symfony, it can be added to any PHP project.<\/p>\n\n<p>Start small, keep things simple, and add what you need.<\/p>\n\n<p>You don't need to go all in on one option, you can pick the pieces you like and that work for you.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cc64c7935024e569db0c62815dab704a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json b/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json
index 6157f80ff..1ba8bffd6 100644
--- a/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json
+++ b/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In yesterday's email, I mentioned Git hooks but didn't go into any detail. So, what are they?<\/p>\n\n<p>Git hooks are Bash scripts that you add to your repository that are executed when certain events happen, such as before a commit is made or before a push to a remote.<\/p>\n\n<p>By default, the script files need to be within the <code>.git\/hooks<\/code> directory, have executable permissions, and be named to exactly match the name of the hook - e.g. <code>pre-push<\/code> - with no file extension.<\/p>\n\n<p>If it returns an error exit code then the process is stopped and the action doesn't complete.<\/p>\n\n<p>This is useful if, for example, you or your team use a specified format for commit messages and you want to prevent the commit if the message doesn't match the requirements.<\/p>\n\n<p>But, the main benefit that I get from Git hooks if from the <code>pre-push<\/code> hook.<\/p>\n\n<p>I use it to run a subset of the checks that are run within project's CI pipeline to limit failures in the CI tool and fix simple errors before I push the code.<\/p>\n\n<p>Typically, these are the quicker tasks such as ensuring the Docker image builds, running linting and static analysis, validating lock files, and some of the automated tests if they don't take too long to run.<\/p>\n\n<p>If a build is going to fail because of something simply like a linting error, then I'd rather find that out and fix it locally rather than waiting for a CI tool to fail.<\/p>\n\n<p>Also, if you're utilising trunk-based development and continuous integration where team members are pushing changes regularly, then you want to keep the pipeline in a passing, deployable state as much as possible and prevent disruption.<\/p>\n\n<p>But what have Git hooks got to do with the \"run\" file?<\/p>\n\n<p>Firstly, I like to keep the scripts as minimal as possible and move the majority of the code into functions within the <code>run<\/code> file. This means that the scripts are only responsible for running functions like <code>.\/run test:commit<\/code> and returning the appropriate exit code, but also means that it's easy to iterate and test them locally without making fake commits or trying to push them to your actual remote repository (and hoping that they don't get pushed).<\/p>\n\n<p>Secondly, I like to simplify the setup of Git hooks with their own functions.<\/p>\n\n<p>For security reasons, the <code>.git\/hooks<\/code> directory cannot be committed and pushed to your remote so they need to be enabled per user within their own clone of the repository.<\/p>\n\n<p>A common workaround is to put the scripts in a directory like <code>.githooks<\/code> and either symlink them to where Git expects them to be, or to use the <code>core.hooksPath<\/code> configuration option and change where Git is going to look.<\/p>\n\n<p>I like to lower the barrier for any team members by creating <code>git-hooks:on<\/code> and <code>git-hooks:off<\/code> functions which either set or unset the <code>core.hooksPath<\/code>. If someone wants to enable the Git hooks then they only need to run one of those commands rather than having to remember the name of the configuration option or manually creating or removing symlinks.<\/p>\n\n<p>There are other Git hooks that can be used but just using <code>pre-commit<\/code> and <code>pre-push<\/code> has saved me and teams that I've worked on both Developer time and build minutes, provides quicker feedback and fewer disruptions in our build pipelines, and I like how simple it can be by creating custom functions in a <code>run<\/code> file.<\/p>\n\n<p>Lastly, I've created <a href=\"https:\/\/github.com\/opdavies\/git-hooks-scratch\">https:\/\/github.com\/opdavies\/git-hooks-scratch<\/a> as an example with a minimal <code>run<\/code> file and some example hooks.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2dc52bfbe73534ab29285ff16486431f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe.json b/content/node.5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe.json
index 6987eeb2d..1b757a158 100644
--- a/content/node.5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe.json
+++ b/content/node.5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When you download and install Drupal, you get so much functionality available out-of-the-box.<\/p>\n\n<p>For example:<\/p>\n\n<ul>\n<li>Content creation and editing capabilities with a flexible content type<\/li>\n<li>A taxonomy system for categorising content.<\/li>\n<li>Tools for managing editorial workflows.<\/li>\n<li>User registration and authentication.<\/li>\n<li>A role-based permission system.<\/li>\n<li>Support for creating multilingual websites with translation tools.<\/li>\n<li>Caching mechanisms to optimise performance.<\/li>\n<li>Scalability features for handling high-traffic websites.<\/li>\n<li>Built-in search functionality.<\/li>\n<li>Robust security features, including input validation and output filtering.<\/li>\n<li>RESTful web services for building web applications and mobile apps.<\/li>\n<li>A flexible page and layout builder.<\/li>\n<\/ul>\n\n<p>There are over 50,000 contributed modules on Drupal.org that you can download to add functionality like eCommerce, analytics, social media integrations, quizzes, webforms and surveys.<\/p>\n\n<p>You can add specific functionality by writing your own modules, and customise a project by creating a theme.<\/p>\n\n<p>It's a great choice for a new web project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "58c0962d04b426f68f113c3d3701de68",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json b/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json
index cc9c0a5e8..528059be3 100644
--- a/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json
+++ b/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I still like RSS and consume a lot of my online content from RSS feeds.<\/p>\n\n<p>I've recently switched from a self hosted RSS reader application on my homelab to a simpler terminal-based one.<\/p>\n\n<p>It's very simple to use, fast, and easy to configure and manage feed URLs - just by editing two text files.<\/p>\n\n<p>There's no UI to click around and no Docker containers or database services running.<\/p>\n\n<p>Everything is stored in a local SQLite database, which also makes it easy to backup and move between devices if needed.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When writing software, I always try and think of the simplest solution to solve a problem.<\/p>\n\n<p>I like solutions that are easy to use, configure, manage and maintain and want to avoid complex or \"feature bloated\" software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "45f3a63e2d57203a2e7971e0d93c8e4c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json b/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json
index 28ac66dbe..d1624049e 100644
--- a/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json
+++ b/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>During one of Nuno Maduro's live streams, he was speaking about static analysis and PHPStan when either he or someone in the chat said \"PHPStan is TypeScript for PHP\".<\/p>\n\n<p>I thought this was an interesting comparison.<\/p>\n\n<p>PHP has types and type checking - the same as TypeScript - but it's only performed when the code is executed.<\/p>\n\n<p>TypeScript's build step will run its type checks and identify any errors when compiling the application.<\/p>\n\n<p>Static analysis tools do the same for PHP, allowing you to execute the type checks without executing the code.<\/p>\n\n<p>The means you can do it from the command line, in an IDE or text editor, or in a CI pipeline.<\/p>\n\n<p><a href=\"https:\/\/www.youtube.com\/watch?v=sOQC_-pkMYk\">Nuno's follow-up YouTube video<\/a> is a great one to watch if you want to see static analysis and PHPStan in action!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8a6c7300585b92faff3cdc9aeaf92cf6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json b/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json
index 9e4aa8d4f..6efa87c5e 100644
--- a/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json
+++ b/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Do you want to contribute to open-source software, such as Drupal core or one of the thousands of modules or themes?<\/p>\n\n<p>Are you worried about receiving negative comments or feedback?<\/p>\n\n<p>Instead, think of it as free code reviews.<\/p>\n\n<p>Contributing to open-source is a great way to gain experience and learn from other Developers, and something that I still do often, 17 years after starting to develop software.<\/p>\n\n<p>I'm also happy to review people's open-source for free. If that would be of interest, reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d65b8a6ca1d38217328e475662fad99e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json b/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json
index d4ef5c74f..d1cbdf4d1 100644
--- a/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json
+++ b/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, Drupal 10 was released alongside Drupal 9.5.<\/p>\n\n<p>This means that, as of today, Drupal 9.3 is no longer supported, so people should update to 9.4, 9.5, or 10.<\/p>\n\n<p>As things stand, Drupal 7 is still supported until November 2023.<\/p>\n\n<p>I haven't tried upgrading any existing websites from Drupal 9 to 10 yet, but I have already started a new client project with Drupal 10.<\/p>\n\n<p>It's a project for a new client that we've been discussing for a few months, and we wanted to wait until Drupal 10 was released before starting. My preparation work has been on the release candidate version of Drupal 10, so I can't foresee any issues updating to the stable 10.0.0 version.<\/p>\n\n<p>As an open-source Drupal project maintainer, I'll soon release Drupal 10 compatible versions of my maintained modules and themes, such as Override Node Options and the Tailwind CSS starter kit theme.<\/p>\n\n<p>If your company has a Drupal module that needs to be upgraded to be Drupal 10 compatible, or needs a module to integrate your service with Drupal 10, reply to this email and let's arrange a call and see if we can work together.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9396b3bf8fe0703b3a6bd95debc95407",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5c50152f-4832-4ccc-9751-31c5caeb7cc3.json b/content/node.5c50152f-4832-4ccc-9751-31c5caeb7cc3.json
index d2c17719a..e595bbd04 100644
--- a/content/node.5c50152f-4832-4ccc-9751-31c5caeb7cc3.json
+++ b/content/node.5c50152f-4832-4ccc-9751-31c5caeb7cc3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/pricing\">All of my software development proposals and services<\/a> include a bug-free guarantee.<\/p>\n\n<p>What does that mean?<\/p>\n\n<p>For a set period after the code is delivered, if it's broken or doesn't work as you expect, I'll fix it.<\/p>\n\n<p>For free.<\/p>\n\n<p>You just let me know, and I'll make it work.<\/p>\n\n<p>No additional charges, invoices or change requests.<\/p>\n\n<p>Just working code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8acef66d71f6264594f0485bcd7cfb2d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json b/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json
index 30ff48d81..b6fb1bc16 100644
--- a/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json
+++ b/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've just added the hundredth test to a client project I'm developing.<\/p>\n\n<p>I'm following <a href=\"http:\/\/default\/daily\/2023\/09\/14\/outside-in-or-inside-out\">the outside-in approach<\/a>, starting with functional tests and moving to kernel and unit tests where needed - meaning more functional tests and fewer unit tests - most of which cover some complex search functionality containing custom blocks, forms, endpoints for autocomplete lists, pattern matching and results pages, which is the core functionality of the project.<\/p>\n\n<p>Here's the breakdown of the different types of tests:<\/p>\n\n<ul>\n<li>Functional - 57 tests, 180 assertions<\/li>\n<li>Kernel - 38 tests, 495 assertions<\/li>\n<li>Unit - 5 tests, 18 assertions<\/li>\n<\/ul>\n\n<p>The tests are run automatically in a CI pipeline by GitHub Actions and Docker and usually run in two or three minutes.<\/p>\n\n<p>The project is still in progress, so I'll add more tests for the remaining functionality and possibly remove some too, as I refactor some of the code.<\/p>\n\n<hr>\n\n<p>P.S. Are you interested in automated testing and test-driven development? I'm speaking about it at DrupalCon Europe on the 17th of October!<\/p>\n\n<p>You can also pre-register for my free 10-day automated testing email course at https:\/\/opdavi.es\/testing-email-course.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "af6787c66c99562dd87d058806ab584e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json b/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json
index 41182d4cd..ee825a4bd 100644
--- a/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json
+++ b/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently started trialing Git worktrees again as part of my development workflow.<\/p>\n\n<p>If you are unfamiliar with Git worktrees, they allow you to have muliple branches of a repository checked out at the same time in different directories.<\/p>\n\n<p>For example, this is what I see within my local checkout of my website repository:<\/p>\n\n<pre><code>.\n\u251c\u2500\u2500 config\n\u251c\u2500\u2500 HEAD\n\u251c\u2500\u2500 main\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 ansible\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 nginx\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 README.md\n\u2502&nbsp;&nbsp; \u2514\u2500\u2500 website\n\u251c\u2500\u2500 new-post\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 ansible\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 nginx\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 README.md\n\u2502&nbsp;&nbsp; \u2514\u2500\u2500 website\n\u251c\u2500\u2500 objects\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 info\n\u2502&nbsp;&nbsp; \u2514\u2500\u2500 pack\n\u251c\u2500\u2500 packed-refs\n\u251c\u2500\u2500 refs\n\u2502&nbsp;&nbsp; \u251c\u2500\u2500 heads\n\u2502&nbsp;&nbsp; \u2514\u2500\u2500 tags\n\u2514\u2500\u2500 worktrees\n    \u251c\u2500\u2500 main\n    \u2514\u2500\u2500 new-post\n<\/code><\/pre>\n\n<p>The first thing that you'll notice is, because it's a bare clone, it looks a little different to a what you usually see in a Git repository.<\/p>\n\n<p>Each worktree has it's own directory, so my \"main\" branch inside the <code>main<\/code> directory.<\/p>\n\n<p>If I need to work on a different branch, such as <code>new-post<\/code>, then I can create a new worktree, move into that directory and start working. I don't need to commit or stash any in-progress work and switch branches.<\/p>\n\n<h2 id=\"complications-with-docker-compose\">Complications with Docker Compose<\/h2>\n\n<p>I use Docker and Docker Compose for my projects, and this caused some issues for me the last time that I tried using worktrees.<\/p>\n\n<p>By default, Docker Compose will use the name of the directory that the Compose file is in to name its containers. If the directory name is \"oliverdavies-uk\", then the containers will be <code>oliverdavies-uk-web_1<\/code>, <code>oliverdavies-uk-db_1<\/code> etc.<\/p>\n\n<p>This doesn't work so well if the directory is a worktree called \"main\" or \"master\" as you'll have containers called <code>main_web_1<\/code> or <code>master_db_1<\/code>.<\/p>\n\n<p>The way to solve this is to use the <code>COMPOSE_PROJECT_NAME<\/code> environment variable.<\/p>\n\n<p>If you prefix Docker Compose commands with <code>COMPOSE_PROJECT_NAME=your-project<\/code>, or add it to an <code>.env<\/code> file (Docker Compose will load this automatically), then this will override the prefix in the container names to be <code>your-project-{service}<\/code>.<\/p>\n\n<h2 id=\"container-names-per-worktree\">Container names per worktree<\/h2>\n\n<p>Whilst you could use the same Compose project name within all of your worktrees, I prefer to include the worktree name as a suffix - something like <code>my-project-main<\/code> or <code>my-project-staging<\/code> - and keep these stored in an <code>.env<\/code> file in each worktree's directory.<\/p>\n\n<p>As each worktree now has unique container names, I can have multiple instances of a project running at the same time, and each worktree will have it's own separate data - meaning that I can make changes and test something in one worktree without affecting any others.<\/p>\n\n<p>You can also use the <code>COMPOSE_PROJECT_NAME<\/code> variable inside Docker Compose files.<\/p>\n\n<p>For example, if you use Traefik and needed to override the host URL for a service, the string will be interpolated and the project name would be injected as you'd expect.<\/p>\n\n<pre><code class=\"language-yaml\">labels:\n    - \"traefik.http.routers.${COMPOSE_PROJECT_NAME}.rule=Host(\n        `${COMPOSE_PROJECT_NAME}.docker.localhost`,\n        `admin.${COMPOSE_PROJECT_NAME}.docker.localhost`\n      )\"\n<\/code><\/pre>\n\n<p>This means that Traefik would continue to use a different URL for each worktree without you needing to make any changes to your Docker Compose file.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "370654d00cb259d64990285329962aa4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json b/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json
index 57831e8bf..53301d0ef 100644
--- a/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json
+++ b/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whilst starting to upgrade my <a href=\"http:\/\/default\/atdc\">automated testing email course<\/a> to Drupal 11, I needed to update Drush and <a href=\"https:\/\/x.com\/opdavies\/status\/1825940869595201905\">noticed the output was different<\/a>.<\/p>\n\n<p>People replied to that post, saying Drush was now using Laravel Prompts.<\/p>\n\n<p>I've seen the conference talk <a href=\"https:\/\/www.youtube.com\/watch?v=PW-2_-KxF-8\">where Jess Archer unveiled Laravel Prompts<\/a> at Laracon EU, but wasn't aware it was being used by Drush.<\/p>\n\n<p>It's great to see Laravel Prompts being used in other PHP projects, which was one of Jess' main objectives, and the Drupal ecosystem continuing to <a href=\"http:\/\/default\/daily\/2024\/06\/09\/proudly-found-elsewhere\">get off the island<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d75c458cf9b991240a7570f820d0e33d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json b/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json
index 5223243fb..a99ea7c39 100644
--- a/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json
+++ b/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In March, I was a guest again on the Talking Drupal podcast. This time I was talking about utility CSS and, in particular, the Tailwind CSS framework.<\/p>\n\n<p>I've become a big fan of this approach to styling websites and was an early adopter of Tailwind, and have released <a href=\"https:\/\/www.drupal.org\/project\/tailwindcss\">a starter-kit theme<\/a> for building custom Drupal themes with Tailwind CSS based on what I was using for my own client projects.<\/p>\n\n<h2 id=\"rebuilding-talking-drupal-with-tailwind\">Rebuilding Talking Drupal with Tailwind<\/h2>\n\n<p>Usually when I give a Tailwind CSS talk at a conference or user group, I rebuild something familiar - maybe a page of their website - as an example and to explain some of the concepts and anything that was particularly interesting during the build. (I have <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">a blog post<\/a> that lists the ones that I've done before).<\/p>\n\n<p>After this podcast episode, I built a <a href=\"https:\/\/talking-drupal-tailwindcss.oliverdavies.uk\">Tailwind version of the Talking Drupal homepage<\/a>.<\/p>\n\n<p>But, given that Drupal uses Twig and that we'd talked about best practices around using a templating engine to use loops and extract components to organise code and reduce duplication, I definitely wanted to build this example using Twig templates.<\/p>\n\n<p>Drupal seemed like too much for a single page example, and Symfony or Sculpin could distract from the main focus of the demo, so I decided to start from scratch with an empty PHP file and add Twig and any other dependencies myself.<\/p>\n\n<p><a href=\"https:\/\/github.com\/opdavies\/talking-drupal-tailwindcss\">The code repository<\/a> is publicly viewable on my GitHub profile so people can look at the code and see some of the things that I talked about during the episode in practice and not just the resulting HTML a browser.<\/p>\n\n<p>You can <a href=\"https:\/\/talkingdrupal.com\/338\">listen to the episode<\/a>, and if you want any more information, the slides and video from my <a href=\"http:\/\/default\/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS talk<\/a> are on my website.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "aea872543f2df95bb71f3cb9dffe5360",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5d894fb5-1253-4f7e-a6ad-429618eeefef.json b/content/node.5d894fb5-1253-4f7e-a6ad-429618eeefef.json
index 097d89ded..3e3edc723 100644
--- a/content/node.5d894fb5-1253-4f7e-a6ad-429618eeefef.json
+++ b/content/node.5d894fb5-1253-4f7e-a6ad-429618eeefef.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I don't use complicated or bloated applications to test HTTP requests and API endpoints.<\/p>\n\n<p>I just use <code>curl<\/code> on my command line.<\/p>\n\n<p>For example, if I want to query the Drupal.org API for my user information, I can run <code>curl https:\/\/www.drupal.org\/api-d7\/user.json?uid=381388<\/code> and see the response.<\/p>\n\n<p>To see the request and response headers, status code, SSL certificate information and more, I can run <code>curl -v<\/code> to run it in verbose mode.<\/p>\n\n<p>If the response returns JSON, I can use <code>jq<\/code> to format the results.<\/p>\n\n<p>If I need to make a POST request, I can use <code>-X POST<\/code>, I can use <code>--data<\/code> or <code>--json<\/code> to send data and <code>--header<\/code> to send any required headers.<\/p>\n\n<p>curl is great program with so many options and no AI bloat, complicated UIs or paid plans.<\/p>\n\n<p>Want to see what else it can do?<\/p>\n\n<p>Just open your terminal and type <code>man curl<\/code>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "071392af7e184fa125a44531711fdfde",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json b/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json
index e94025d02..0d887a963 100644
--- a/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json
+++ b/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I think this quote from Futurama also applies well to software development:<\/p>\n\n<blockquote>\n  <p>When You Do Things Right, People Won\u2019t Be Sure You\u2019ve Done Anything at All<\/p>\n<\/blockquote>\n\n<p>Today I did multiple releases to production websites. There were no outages or downtime, or messages from clients or colleagues.<\/p>\n\n<p>Processes were followed, and everything worked as it should. As far as everyone's concerned, everything still \"just works\".<\/p>\n\n<p>So, did I do anything at all?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2afeabd81ff9e0d49b2e428521c127d1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json b/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json
index f4e28bb26..4885219f7 100644
--- a/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json
+++ b/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, whilst debugging some legacy code within an application, I found several blocks of commented-out code.<\/p>\n\n<p>Some were previous debugging code which had been commented out, and some were old components or previous implementations - but instead of being removed when they were no longer needed, they remained in the codebase as commented-out lines - inactive but adding noise and complexity around the code that I was trying to understand and debug.<\/p>\n\n<p>To make it easier for me to figure out this code, I'd like it to be as clean to read and as simple to understand as possible.<\/p>\n\n<p>The codebase is version-controlled, so why would there be a need to comment out and keep the lines?<\/p>\n\n<p>Version control systems have a log of each change, so if you need to see previous changes, you can view the log and see what changed, when, and by who.<\/p>\n\n<p>You can also see any other files that were changed in the same commit, and usually, there will be a reference to the issue or ticket that required that change.<\/p>\n\n<p>If you need to re-add a change that had been removed, you can either do this manually or by reverting the commit.<\/p>\n\n<p>Should there be commented-out code within a codebase if it's version controlled? I'd say no unless there's a good reason for it to be there and it's providing some additional context or for a specific purpose. If it's an outdated implementation, some old debugging code, or a component that's no longer needed, I think that it should be removed, and people can use version control tools to find or re-introduce those changes if needed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "14f3a718b42c7abd68a912676fde8f73",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json b/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json
index 00f0f3d1f..73ed30549 100644
--- a/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json
+++ b/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Compared to Drupal 7, <a href=\"https:\/\/oliverdavies.dev\/daily\/2023\/04\/30\/will-we-see-drupal-7-100\">which is almost at version 100<\/a>, the release cycle from Drupal 9 onwards has been quite different.<\/p>\n\n<p>We've adopted semantic versioning with new feature releases every six months, and we've already sunsetted Drupal 8 and moved on to Drupal 9 and 10.<\/p>\n\n<p>Major versions are released more quickly, with Drupal 9 support ending in November 2023 and Drupal 11 potentially being released in May or November 2024.<\/p>\n\n<p>But is it too quick, as someone asked on Twitter?<\/p>\n\n<p>The main reason I'm aware of is to keep in sync with major versions of projects that Drupal uses, such as the components used by Symfony. As they update and release new major versions, we also need to do so.<\/p>\n\n<p>As a module and theme maintainer, I don't think it's too fast and have been happy with the number of changes to upgrade them and make them Drupal 10 compatible. In most cases, I only had to change the <code>core_version_requirement<\/code> key to include the new version.<\/p>\n\n<p>It depends on how well the project is maintained during the earlier versions. If you keep up to date with changes in minor versions and remove any deprecated code, there will be less to do in the future.<\/p>\n\n<p>The same applies to any custom code within website projects, not just contributed modules and themes.<\/p>\n\n<p>The more often you maintain and update what you have; the easier it will be.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e338b7c88d5cb20842d58191906582b0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json b/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json
index a8616784e..fdf807efd 100644
--- a/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json
+++ b/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was recently writing code for a project and found myself making assumptions about what I was writing.<\/p>\n\n<p>I was creating my own requirements.<\/p>\n\n<p>Something no-one asked for.<\/p>\n\n<p>I was assuming a value was always going to be a certain number of digits long.<\/p>\n\n<p>I was writing code that verified this was true or throw an Exception.<\/p>\n\n<p>Until I found out that that one of the values wasn't the same length as the others.<\/p>\n\n<p>This could be an error in the data or it could correct.<\/p>\n\n<p>No-one told me the lengths were always going to be the same.<\/p>\n\n<p>So why was I checking it?<\/p>\n\n<p>Why was I adding bugs to the code?<\/p>\n\n<p>I've reverted the code that checks the length of the value and gone to find clarification.<\/p>\n\n<p>If it's an issue, it'll be fixed in the source data.<\/p>\n\n<p>If the lengths should all be the same, I'll potentially re-add the check.<\/p>\n\n<p>Until I'm sure, I'll only write what's needed to deliver the feature and stop adding my own requirements and assumptions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2ddc207d69aba210aead45269c83988b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json b/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json
index e3ad02297..7c501a2d2 100644
--- a/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json
+++ b/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently received these kind words from Frank Landry, who recently completed my <a href=\"http:\/\/default\/atdc\">Drupal automated testing email course<\/a>:<\/p>\n\n<blockquote>\n  <p>The course was very informative.<\/p>\n  \n  <p>One of the biggest pain points with Drupal testing was that there was no clear and definitive guide on setting up the php unit XML file to get functional and kernel tests working right away.<\/p>\n  \n  <p>Your guide was fantastic and I will definitely be using it going forward in my module development for work.<\/p>\n<\/blockquote>\n\n<p>Thanks, Frank, for your feedback.<\/p>\n\n<p>It's great to get feedback on my content and to know it's helping and providing value to people.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "931b8ae559e296532c83db53d0eb0671",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json b/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json
index 5674faca9..67945afc1 100644
--- a/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json
+++ b/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I learned there is a Drupalisms Working Group - a group focused on de-jargoning Drupal and making it easier for newcomers to Drupal by removing some of the Drupal-specific language.<\/p>\n\n<p>From <a href=\"https:\/\/www.drupal.org\/association\/blog\/de-jargoning-drupal-working-with-the-community-to-open-up-drupals-terminology\">the introductory blog post<\/a>:<\/p>\n\n<blockquote>\n  <p>If you\u2019re familiar with Drupal, you will have learned its language. You will be familiar with words like Views, Blocks and Paragraphs, and you will appreciate their respective features and functions. But for those new to Drupal, getting to grips with what words mean can mean a steep learning curve.<\/p>\n<\/blockquote>\n\n<p>Drupalisms is something I've discussed on a few episodes of Beyond Blocks, including <a href=\"http:\/\/default\/podcast\/21-eirik-morland-violinist-2\">the most recent episode and the seonc with Eirik Morland<\/a>.<\/p>\n\n<p>I didn't realise there were BoF sessions about this at DrupalCon Lille last year, so I'm hoping there will be more next week in Barcelona.<\/p>\n\n<p>Anything that helps Drupal easier to use and adopt is a good thing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e8fab9a9c586506079edcd257eb1d672",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json b/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json
index 9888244c7..2080bf115 100644
--- a/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json
+++ b/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I can't believe it's 2025!<\/p>\n\n<p>It's going to be a busy year with Drupal's 23rd birthday, Drupal 7's end-of-life date and the release of Drupal CMS all happening in January!<\/p>\n\n<p>There's the inaugural DrupalCamp England in Cambridge in March that I'm planning to attend, and the Global Contribution Day event in London (and everywhere else).<\/p>\n\n<p>I'm looking forward to the upcoming episodes of <a href=\"http:\/\/default\/podcast\">the Beyond Blocks podcast<\/a> and finding time for more open source contributions and <a href=\"https:\/\/www.youtube.com\/@opdavies\/streams\">coding live streams<\/a> again.<\/p>\n\n<p>This is daily email #714, which means I'll get to 1,000 emails in October - which will be a huge milestone!<\/p>\n\n<p>Of course, I want to continue growing my email list, podcast listeners and YouTube followers, so if anything is interesting to you, please share it with anyone else you think would benefit from it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "48e2d5e019f08af995265a4dcb06e4f5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json b/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json
index ea4d6ead1..eb3361c86 100644
--- a/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json
+++ b/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Instead of creating a branch that lives for as long as the code takes to write, if it's behind a feature flag, the code can be merged into the mainline branch without affecting the rest of the codebase.<\/p>\n\n<p>Being able to release changes incrementally lowers the risk compared to releasing a large change all at once.<\/p>\n\n<p>But the same issue can occur with feature flags, and the longer that code is behind a feature flag, the more risk there will be when enabling the feature.<\/p>\n\n<p>So, like feature branches, feature flags should be short-lived and only used for as long as is needed to create the first releasable version of the feature. The feature flag can be removed once the feature is live, and the feature can continue to be iterated on and improved.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d7e1f6d61d5541ac83cd2bfe9bc3e669",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json b/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json
index b073660fa..f604e64cf 100644
--- a/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json
+++ b/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've seen a lot of recent posts that ask questions like \"Is it time to stop writing Sass?\".<\/p>\n\n<p>I haven't written a Less or Sass stylesheet since I adopted utility classes and Tachyons, and then Tailwind CSS, and I moved to PostCSS.<\/p>\n\n<p>But, with recent native browser support added for some Sass features, such as <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/CSS\/CSS_nesting\">CSS nesting<\/a> and <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/CSS\/Using_CSS_custom_properties\">CSS custom properties<\/a> (variables), people are considering moving from Sass to regular CSS.<\/p>\n\n<p>Using regular CSS also makes it easier to onboard new Developers onto your project, which is particularly helpful in open-source projects, as <a href=\"http:\/\/default\/podcast\/11-mark-conroy\">Mark Conroy and I discussed<\/a> on the Beyond Blocks podcast.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a7d6c56ee6f6fe36ad6ab0b6d430d52b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json b/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json
index c6a3b24cb..640063db3 100644
--- a/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json
+++ b/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A couple of years ago, I wrote an integration for a client's Drupal Commerce website with an online eBook service as they wanted to sell eBook variations of their products.<\/p>\n\n<p>They provided me with some example code for different PHP frameworks, each were separate and tightly-coupled to each framework, so there was no code shared between them. Because of this, and because there was no Drupal Commerce example, I wrote my own version.<\/p>\n\n<p>However, I decided to make my version as reusable and loosely-coupled as possible. This meant that I'd be able to potentially reuse it for other clients and the same code could be used for different implementations.<\/p>\n\n<p>Reusable code such as the configuration, different types of Requests, value objects for Customers, Orders and OrderItems, were all written within a separate, reusable PHP library. It contains it's own tests, has it's own CI pipeline, and it's own static analysis - ensuring that things work as expected.<\/p>\n\n<p>With this code separated, the Drupal module was much smaller and responsible only for bridging the library's code with Drupal Commerce and adding any other Drupal-specific code.<\/p>\n\n<p>The client is currently considering an upgrade from Drupal 7 to Drupal 9, which would also mean upgrading this module. But, with this approach, there's a lot less to upgrade. The library code can still be used, and I can focus on any Drupal-specific changes within the Drupal module.<\/p>\n\n<p>I recently had an enquiry from someone who needs an integration with the same service. Whilst their requirements may be different, I could still re-use the reusable library code, and write any client-specific code within a custom module.<\/p>\n\n<p>Finally, if I wanted to reuse this code within a different PHP eCommerce framework then I could by installing the library with Composer. This means that I'd get the same code without needing to manually copy it, keeping a single source that can be maintained separately upstream. I'd get the same code that I'm already familiar with, so I could focus only on how to integrate the library with that framework - again meaning less framework-specific code and a much lower development effort.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "676d182d739ffcfdc08fb352326a6503",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json b/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json
index d1867085d..636258054 100644
--- a/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json
+++ b/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Continuing from <a href=\"http:\/\/default\/daily\/2024\/01\/30\/tdd-doesnt-mean-you-know-everything-upfront\">my last few emails<\/a>, as well as adding the new use case more easily and quicker, having automated tests also saved me from adding a regression into the code I was changing.<\/p>\n\n<p>I'd written a condition in the query to ensure only results that started with the search term.<\/p>\n\n<p>Initially, I removed it, but then the tests failed.<\/p>\n\n<p>This reminded me why I'd written the condition that way, and I was able to re-add my fix differently.<\/p>\n\n<p>Without the tests, I'd likely have removed it and introduced a regression.<\/p>\n\n<p>Whilst fixing a bug, I'd have introduced a different bug.<\/p>\n\n<p>My tests saved me from doing that and I was able to rectify it quickly before pushing to CI or the staging environment.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4da060af4834ea01bfde91a020ba0f5f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json b/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json
index c121fe5d5..a513fc0f1 100644
--- a/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json
+++ b/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When practising test-driven development, you don't need to think about what to do next.<\/p>\n\n<p>If you have a failing test, the objective is to get that test to pass as quickly and simply as possible, and you rely on the error from the failing test to tell you the next step.<\/p>\n\n<p>It could be a failing assertion, an undefined variable or function, or a yet-to-be-implemented service.<\/p>\n\n<p>Once you've fixed that error, the test will either pass or fail. If it fails, you'll have a new error and know the next step.<\/p>\n\n<p>When working in this way, it's like being on autopilot. You can focus only on fixing each error until the feature or fix is complete and the test is passing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "db22261b5253a478d77e2c07ea03d3da",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json b/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json
index 759595cc0..232a05625 100644
--- a/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json
+++ b/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Deprecating code is a way of identifying code that will be removed in a future major version.<\/p>\n\n<p>For example, the <code>drupal_set_message()<\/code> function was deprecated in Drupal 8.5 and removed in Drupal 9 as the <code>messenger<\/code> service replaced it.<\/p>\n\n<p>Once it was deprecated, the function was changed to use the new service to avoid duplicating code and a message was added to notify Developers:<\/p>\n\n<pre><code class=\"language-php\">function drupal_set_message($message = NULL, $type = 'status', $repeat = FALSE) {\n  @trigger_error('drupal_set_message() is deprecated in Drupal 8.5.0 and will be removed before Drupal 9.0.0. Use \\Drupal\\Core\\Messenger\\MessengerInterface::addMessage() instead. See https:\/\/www.drupal.org\/node\/2774931', E_USER_DEPRECATED);\n\n  $messenger = \\Drupal::messenger();\n  if (isset($message)) {\n    $messenger-&gt;addMessage($message, $type, $repeat);\n  }\n\n  return $messenger-&gt;all();\n}\n<\/code><\/pre>\n\n<p>This approach means that code can be refactored without breaking backwards-compatibility and, to upgrade any custom code to be compatible with Drupal 9, any references to <code>drupal_set_message()<\/code> just needed to be updated to use the new Messenger service.<\/p>\n\n<p>No large rewrite needed!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "354a128b2c40c5adae2aa3cc4b1fd6ef",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json b/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json
index 0da469cd6..3e5967cac 100644
--- a/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json
+++ b/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the last Beyond Blocks podcast of 2024, I caught up with Mark Conroy to discuss open source sustainability and sponsorship, different ways to charge for development services and setting up your own agency.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/26-mark-conroy-the-confident\">Listen to the episode now<\/a>.<\/p>\n\n<p>It was great to speak with Mark again, and I'm looking forward to speaking with the guests I have lined up to be on the podcast soon.<\/p>\n\n<p>If you'd like to be on the podcast in 2025 or want to suggest a guest or topic, <a href=\"mailto:oliver+website@oliverdavies.uk?subject=Beyond Blocks podcast suggestion\">get in touch<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "411c32cffbc1e2bf68a8ab3d2c9c503f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json b/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json
index 03eed9b92..94662db78 100644
--- a/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json
+++ b/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When fixing a bug, can you write a new failing test to replicate the bug?<\/p>\n\n<p>If so, you verify the bug exists, you know when it's fixed (the test passes), and you know you won't introduce the same bug again - otherwise, the new test will fail.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1cd5f63516d47e313f05f821bfa74ee8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json b/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json
index a944dfbcd..14a5588a2 100644
--- a/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json
+++ b/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I saw a lot of AI-related content at DrupalCon, including the Driesnote and the Track Lead keynote.<\/p>\n\n<p>The Driesnote showed a demonstration of Drupal CMS (aka Starshot), which included an AI chatbot that performed tasks such as renaming content types and building views.<\/p>\n\n<p>I also remember seeing AI populating alt text for images in one of the sessions.<\/p>\n\n<p>I'm still on the fence about AI and when and how it should be used.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/05\/31\/putting-glue-on-pizza\">My experiences of using AI so far haven't been great<\/a>, but I have seen some interesting implementation and use-cases for it.<\/p>\n\n<p>I'm seeing AI being added everywhere - from my search results to suggesting social media comments and generating notes and issues within services I use.<\/p>\n\n<p>I can see how a AI-driven approach to site building in Drupal could be useful, but I'm still unsure.<\/p>\n\n<p>What do you think?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f2796dcd8b3c66004a440f61ec59c655",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json b/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json
index dbaa04b3e..13b0cbf49 100644
--- a/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json
+++ b/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week on Beyond Blocks, I'mj oined by Ryan Szrama, CEO of Centarro, to discuss Drupal Commerce, Commerce Kickstart, Mario Kart and the dreaded <code>cache_form<\/code> table.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/13-ryan-szrama-centarro\">Listen to the episode now<\/a>.<\/p>\n\n<h2 id=\"key-points\">Key points<\/h2>\n\n<ul>\n<li>eCommerce, Ubercart and Drupal Commerce.<\/li>\n<li>How Commerce Guys started.<\/li>\n<li>How Ryan started in the eCommerce space.<\/li>\n<li>The origins of Drupal Commerce and Commerce Guys.<\/li>\n<li>Commerce Kickstart.<\/li>\n<\/ul>\n\n<h2 id=\"quotes\">Quotes<\/h2>\n\n<ul>\n<li>The best code isn't the most novel or most compact, it's the most easily readable and easily extendable (RS).<\/li>\n<li>My only resource for learning PHP was php.net (RS)<\/li>\n<li>I'm a self-taught Developer or community-taught, I suppose (OD).<\/li>\n<li>Porting osCommerce into Drupal, which became Ubercart (RS).<\/li>\n<li>Do we do this in Ubercart and Drupal 6 that we know works, or this new thing that was Drupal Commerce in Drupal 7 (OD).<\/li>\n<li>It was built in Ubercart and was in production until quite recently, considering we're in 2024 (OD).<\/li>\n<li>Once you get thoroughly entrenched in a platform, the cost to re-platform outweighs the cost of maintaining it in-house (RS).<\/li>\n<li>If there's 10,000 of anybody, they're going to want to pay for support (RS).<\/li>\n<li>How do we convince them to invest in an upgrade that doesn't see them jettison Drupal entirely? (RS)<\/li>\n<li>One thing I like about Drupal Commerce is its flexibility. (OD)<\/li>\n<li>It doesn't need to be a t-shirt or book shop. You can do some outside the box things with it. (OD)<\/li>\n<li>Being a native extension of Drupal has a lot more advantages and pros than cons. (RS)<\/li>\n<li>Ubercart was more \"batteries included\" and \"this is what it does\", whereas Drupal Commerce is more flexible and although it requires a bit more setup to begin with, you can plug it together the way you want to. (OD)<\/li>\n<li>Our vision was to go the next step of getting off the Drupal island. (RS)<\/li>\n<li>The Commerce Addressing library is now over 17,000,000 downloads. (OD)<\/li>\n<li>Composer allowed us to separate our projects and separate our concerns. (RS)<\/li>\n<li>Do you know when you should not use Views and when you decouple that component and use JavaScript and the REST API? (RS)<\/li>\n<li>If we can reduce the number of times introduce those kinds of problems, that's how I would certify somebody. (RS)<\/li>\n<\/ul>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ece6d288969fcecbef1ddc355b89ca0e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json b/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json
index 9ac79e58a..0c38465f0 100644
--- a/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json
+++ b/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the last few emails, we've seen a data transfer object called <code>AccountDetails<\/code> that stores the account number and sort code for a bank account.<\/p>\n\n<p>A data transfer object only stores data but we could also use a value object that can do more tasks, like validating the values.<\/p>\n\n<p>For example, we could validate that the account number is the correct length and the sort code is the correct format:<\/p>\n\n<pre><code class=\"language-php\">class AccountDetails {\n\n  public function __construct(\n    public readonly string $accountNumber,\n    public readonly string $sortCode,\n  ) {\n    \/\/ Validate the account number.\n    if (!preg_match('\/^\\d{8}$\/', $accountNumber)) {\n      throw new \\InvalidArgumentException('Account number must be an 8-digit number');\n    }\n\n    \/\/ Validate the sort code.\n    if (!preg_match('\/^\\d{2}-\\d{2}-\\d{2}$\/', $sortCode)) {\n      throw new \\InvalidArgumentException('Sort code must be in the format 00-00-00');\n    }\n  }\n\n}\n<\/code><\/pre>\n\n<p>Helper methods can also be added to a value object as long as they don't modify the state of the object, such as getting the raw sort code without the separating dashes or performing further checks on the input values.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cd7cf8aa226ddd46c78eab76f4c2e300",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.62d91e86-a22e-4ef9-851d-bd2b02c411a9.json b/content/node.62d91e86-a22e-4ef9-851d-bd2b02c411a9.json
index 0c8ced4eb..b23fd5cbf 100644
--- a/content/node.62d91e86-a22e-4ef9-851d-bd2b02c411a9.json
+++ b/content/node.62d91e86-a22e-4ef9-851d-bd2b02c411a9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It's been common for me whilst working on software projects to have work organised into sprints or cycles - a period, usually between 1 and 3 weeks, where the team is working on stories and tasks for that project.<\/p>\n\n<p>In my experience, those changes are usually released at the end of that cycle. But it seems that's not always the case; see <a href=\"https:\/\/scrumdictionary.com\/term\/release-sprint\">release sprints<\/a>:<\/p>\n\n<blockquote>\n  <p>A specialised sprint whose purpose is to release deliverable results; it contains stories specific to release activities and finishing undone work.  A release sprint usually contains no additional development.<\/p>\n<\/blockquote>\n\n<p>If we worked in two-week cycles and released at the end of each one, it would be at least two weeks before a change could be deployed to production. But what if we wanted to follow continuous deployment and release more frequently? Maybe daily or hourly?<\/p>\n\n<p>Instead of waiting for a release sprint, if we released multiple times within a single sprint, how would this fit into or affect the process?<\/p>\n\n<p>Does the release cycle need to be tightly coupled to the sprint cycle or can they be separate and independent of each other?<\/p>\n\n<p>I've worked on projects - including a current one - where I've done multiple releases in a sprint, so of course, it can be done from a technical perspective, but how do we get the best from both processes - whether they work together or separately?<\/p>\n\n<p>This is something that I'm going to continue to experiment with, iterate on, and learn more about going forward.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "efd0ec8ddb3fb7929febf9e8017a8f84",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json b/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json
index e6014419a..20f27bbe1 100644
--- a/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json
+++ b/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few years ago, I worked at an agency on a client project.<\/p>\n\n<p>We were writing automated tests and doing test-driven development. We were releasing features, and everything was going well.<\/p>\n\n<p>Mid-way through the project, we were told to stop writing tests as it was taking \"too long\".<\/p>\n\n<p>We did, and the number of bugs increased almost instantly.<\/p>\n\n<p>We went from essentially no bugs to having a number of tickets being rejected through our quality assurance and the client's user-acceptance testing, as well as in production by the website's users.<\/p>\n\n<p>The time we spent re-working the issues, fixing the bugs and doing remedial work in production would likely have been less than the time it would have taken to write the tests initially and avoided any reputational damage.<\/p>\n\n<p>We started writing tests again later during that project, but the middle phase was the most stressful part, and the most bugs were created.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>It's not just about how long it takes to write the tests.<\/p>\n\n<p>Having tests will save time overall by having fewer bugs that need to be fixed, less remedial work in production, and less reshuffling of priorities to re-work tickets that affect the project plan and timescales as well as the team's output and velocity.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "eed28c15ec49405ff32aaeab6788dec9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json b/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json
index 323b1afae..a4ce06a92 100644
--- a/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json
+++ b/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Sometimes when <a href=\"http:\/\/default\/daily\/2025\/02\/11\/tidy\">tidying my commits<\/a> or updating a local branch with remote changes, the order of commits changes - making them out of order in when running <code>git log<\/code>.<\/p>\n\n<p>I want the commits in the log to be in the correct sequential order.<\/p>\n\n<p>If not, it would be confusing if I review the commits in the future.<\/p>\n\n<p>This is easy to fix when running <code>git rebase -i<\/code> to perform an interactive rebase on the commits.<\/p>\n\n<p>The commit has a <code>-x<\/code> or <code>--exec<\/code> option that will perform a given command on each commit.<\/p>\n\n<p>The commit date can be reset using <code>git reset --amend<\/code>, and combining these commands will amend the date of each commit.<\/p>\n\n<p>Running <code>git rebase --interactive --exec \"git commit --amend --no-edit --date now\"<\/code> will amend and update each commit, keeping the commit message the same, but changing the commit date to the current time - leaving the Git log in the correct order.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "945a9ecd7e9f1ec6de312f2b03035231",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json b/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json
index 0304bd564..c999cccf9 100644
--- a/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json
+++ b/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently considered moving my infrastructure automation code from Pulumi to Terraform.<\/p>\n\n<p>One of Pulumi's features is that you can write your automation in a programming language instead of a domain-specific language (DSL) with Terraform.<\/p>\n\n<p>As a Developer, this seems appealing, but it poses an important question - which programming language should you use?<\/p>\n\n<p>I've written and re-written Pulumi code in TypeScript and Python and experimented with Go to see which feels best for me.<\/p>\n\n<p>If one of these were my primary language, it would be a no-brainer.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When I go into my automation repository, I want to write my code as quickly and simply as possible. I don't want to be thinking about how to write it or what language would be best to write it in.<\/p>\n\n<p>Whilst I'd have to learn another DSL for Terraform, it would simplify my options by removing that choice for me, but also if I write automation code and hand it over to a client.<\/p>\n\n<p>It's like taking my children to a restaurant.<\/p>\n\n<p>They'll get overwhelmed if there are too many options on the menu. If we limit the options or order for them, they won't.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "960ab3763a91c3a533d2f22da91bd8fd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json b/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json
index 526aadd48..a3ee04cab 100644
--- a/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json
+++ b/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>What can you do to make your current task easier to achieve?<\/p>\n\n<p>Can you refactor the existing code to make it easier to change?<\/p>\n\n<p>Are there requirements that are no longer needed and can be de-scoped to make the code simpler or smaller?<\/p>\n\n<p>Is there a more minimum-viable version that you can release now and iterate on it later?<\/p>\n\n<p>Is there an existing solution, such as a library, module or plugin you can use instead of implementing it yourself?<\/p>\n\n<p>Is there a different or simpler implementation that satisfies most of the requirements that you can use?<\/p>\n\n<p>Taking an easier option means less code to maintain and a more stable application.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "17e2867cfaf4f7465ecd07558b97ce21",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json b/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json
index 77657980c..1fad1a058 100644
--- a/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json
+++ b/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Here are two versions of some example code I've recently been working on.<\/p>\n\n<p>One has types and uses TypeScript, the other is JavaScript and has no types.<\/p>\n\n<p>Which do you prefer and why?<\/p>\n\n<h2 id=\"typescript-with-types\">TypeScript (with types)<\/h2>\n\n<pre><code class=\"js\">add(...numbers: number[]): number {\n  return numbers.reduce((a: number, b: number) =&gt; a + b, 0);\n}\n\nsubtract(...numbers: number[]): number {\n  let total = numbers[0];\n\n  for (var i = 1, length = numbers.length; i &lt; length; i++) {\n    total -= numbers[i];\n  }\n  return total;\n}\n<\/code><\/pre>\n\n<h2 id=\"javascript-no-types\">JavaScript (no types)<\/h2>\n\n<pre><code class=\"js\">add(...numbers){\n  return numbers.reduce((a, b) =&gt; a + b, 0);\n}\n\nsubtract(...numbers) {\n  let total = numbers[0];\n\n  for (var i = 1, length = numbers.length; i &lt; length; i++) {\n    total -= numbers[i];\n  }\n\n  return total;\n}\n<\/code><\/pre>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "02563327b263204583e6aa95ad8c9bd2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json b/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json
index 3acf8b4c1..66bea0900 100644
--- a/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json
+++ b/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2024\/07\/03\/committing-ci-artifacts\">committing build artifacts<\/a>, another common use for CI pipelines is for running automated checks.<\/p>\n\n<p>This could include code linting, static analysis, automated tests, checking for security vulnerabilities, and more.<\/p>\n\n<p>Instead of relying on Developers running these checks manually, running them automatically in a CI pipeline ensures they're run regularly and that each commit is deployable.<\/p>\n\n<p>If all the checks pass, a commit can be promoted and released.<\/p>\n\n<p>If not, the commit should not be deployed and it should be fixed.<\/p>\n\n<p>This makes a CI pipeline and automated checks vital to ensure the quality of your software, to identify regressions, and to avoid promoting and releasing broken code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "45fc5e3725cf16ecee4a27e40566329d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json b/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json
index 65a6bbc53..177cbb154 100644
--- a/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json
+++ b/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week's guest on the Beyond Blocks podcast is&nbsp;Niklas Franke - Digital Marketing Manager at Factorial.<\/p>\n\n<p>Niklas was a fellow speaker at the recent DrupalCon conference in Lille - presenting multiple sessions, whilst Factorial were sponsors of the event.<\/p>\n\n<p>In this episode, Niklas and I discussed his first experience of DrupalCon, presenting a session on contribution for non-technical Drupalers, the German Drupal community, what the Splash Awards are and how to organise your own event.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/3-non-technical-contribution\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "51dd20dbb9299ddbcf934107a9b20553",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json b/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json
index ecf33db13..1e0feec5d 100644
--- a/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json
+++ b/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/03\/11\/feature-flags-should-be-short-lived\">In yesterday's email<\/a>, I mentioned my recent <a href=\"https:\/\/twitter.com\/opdavies\/status\/1767846980250714261\">\"minimum viable feature flag\" tweet<\/a> and that I think feature flags should be short-lived.<\/p>\n\n<p>But how do you know when a feature flag should be removed?<\/p>\n\n<p>My approach is to add a TODO comment above where I use a feature flag.<\/p>\n\n<p>In that comment, I added why the feature flag was added and when it can be removed.<\/p>\n\n<p>It can be something like \"Remove this when x is deployed\" and\/or a targeted date when I'd expect to be able to remove the flag.<\/p>\n\n<p>Then, when reading through the code, anyone can see when it should be possible to remove each feature flag, and it's easy to find flags that can be removed by reviewing the TODO comments.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d85f39009078b66d9ee5dacc770a0a22",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json b/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json
index fd1aed6ab..122466aa3 100644
--- a/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json
+++ b/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Shell aliases are a good way to increase productivity by shortening long commands, adding additional options to existing ones or creating new ones that even combine multiple commands.<\/p>\n\n<p>Common aliases are <code>g<\/code> for <code>git<\/code>, <code>gs<\/code> for <code>git status<\/code> and <code>dr<\/code> for <code>drush<\/code>, but they will be different for each person depending on what tools they use and what commands they type often.<\/p>\n\n<p>Whilst aliases are great for personal productivity, there are times I'd suggest not using them.<\/p>\n\n<p>If you're giving a demo as part of a presentation or working in a pair or mob, either use the full commands or explain what custom aliases or functions you're running, what they do, and how they differ from the default functionality.<\/p>\n\n<p>I recently watched a video where someone was using a <code>gc<\/code> command.<\/p>\n\n<p>It could have been an alias for <code>git clone<\/code>, <code>git checkout<\/code>, <code>git commit<\/code> or <code>git cherry-pick<\/code> - just to name a few options.<\/p>\n\n<p>It could have been something else altogether.<\/p>\n\n<p>Another approach I use is to have aliases auto-expand and show the full command. This makes it possible for others to see the commands being executed and reminds you, too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d77f4c3aa58ffc20e26976b05b6332a5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json b/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json
index a949fea21..3f4469f5b 100644
--- a/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json
+++ b/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When you're writing open source code, such as a PHP library or a Drupal module, the larger it is, the harder it can be to reuse.<\/p>\n\n<p>Each implementation will have its own requirements and specifics, so why have code that tries to do everything?<\/p>\n\n<p>The smaller the code, the more reusable it is.<\/p>\n\n<p>The most reusable code I've written have been in smaller modules, like the <a href=\"https:\/\/www.drupal.org\/project\/system_user\">System User<\/a> and <a href=\"https:\/\/www.drupal.org\/project\/null_user\">Null User<\/a> Drupal modules.<\/p>\n\n<p>Both are very small and solve a specific problem.<\/p>\n\n<p>The Null User module is used by the System User module to provide a default if no system user is defined.<\/p>\n\n<p>It could have been part of the System User module, but extracting it into a separate module makes it more reusable.<\/p>\n\n<p>It also makes System User leaner, less bloated and more focused on its use case and its own functionality.<\/p>\n\n<p>This approach is based on the UNIX philosophy of a program doing one thing well, and chaining programs together when needed to solve a larger problem.<\/p>\n\n<p>Then, if you need, you can extend the code in a custom module or add features <a href=\"http:\/\/default\/daily\/2025\/02\/24\/patch\">by applying patches<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "937f6aa16a83423afa9730474711b269",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json b/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json
index dbb86e911..d143f09e3 100644
--- a/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json
+++ b/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If, for every change to a codebase, you need to create a topic branch, create a pull or merge request, and wait for it to be reviewed and approved - which can take days, weeks or longer - does that discourage you from making small changes?<\/p>\n\n<p>If you spotted some unused commented-out code whilst working in a file and went to remove it or a variable that could have a better name, would you change it?<\/p>\n\n<p>Alternatively, if you could make the change and know from a CI pipeline within a few minutes that everything still worked, would you be more likely to make the change and improve the code for yourself and the next person to work on it?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7b218181f5d1024fd603acad4aa84aac",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json b/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json
index 08f7c6b66..4bcc7e779 100644
--- a/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json
+++ b/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as the library of utility CSS classes that Tailwind provides, the ability to easily add your own has been one of my main advantages of using it.<\/p>\n\n<p>You can add your own CSS to a stylesheet within a specific layer, customise the theme settings within a <code>tailwind.config.js<\/code> file, and write your own custom plugins that you can reuse and even release as separate open-source projects.<\/p>\n\n<p>Here is a complete plugin that I've added to some projects recently:<\/p>\n\n<pre><code class=\"js\">const plugin = require('tailwindcss\/plugin');\n\nplugin(function({ addVariant }) {\n   addVariant('hocus', ['&amp;:hover', '&amp;:focus'])\n});\n<\/code><\/pre>\n\n<p>By adding these lines of JavaScript, Tailwind will generate a new set of utility classes that apply styles to both hover and focus states for an element - reducing the number of classes that need to be added and making it more maintainable.<\/p>\n\n<p>Other plugins that I've written recently include creating different variants of buttons, styling elements within an HTML table (similar to the Tailwind typography plugin), and adding multi-theme support to make components themable with different colours.<\/p>\n\n<p>I've also released some <a href=\"https:\/\/github.com\/opdavies?tab=repositories&amp;q=tailwind-plugin\">as open-source projects on GitHub<\/a>.<\/p>\n\n<p>The interesting thing is that the plugin API is how Tailwind itself generates its own classes, and I like the stability that provides.<\/p>\n\n<p>However you extend Tailwind, the fact you can tweak and extend it for each project is great and something that you can't always do or do easily with other tools or frameworks.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8bb372459a76d7f0e6bbc559bd44f81c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.68c7948f-c44c-46e2-878f-432616c7e365.json b/content/node.68c7948f-c44c-46e2-878f-432616c7e365.json
index 907106b28..4ac638aaa 100644
--- a/content/node.68c7948f-c44c-46e2-878f-432616c7e365.json
+++ b/content/node.68c7948f-c44c-46e2-878f-432616c7e365.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How do you define legacy code?<\/p>\n\n<p>Code that was written by someone else?<\/p>\n\n<p>Code that doesn't have tests?<\/p>\n\n<p>Any code that has been released to production?<\/p>\n\n<p>Code that's more than a day old?<\/p>\n\n<p>In a talk I recently watched, the speaker suggested that any code written more than thirty minutes ago is legacy code.<\/p>\n\n<p>Once you've written some code and left it for half an hour, you need to re-read it to remember and re-learn what the code does and decide how you want to implement your next requirement.<\/p>\n\n<p>This is the same approach for code that was written longer ago or written by someone else.<\/p>\n\n<p>What do you think?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9983c859dafd94ec45282b7438b9cb59",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json b/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json
index 7bce92c19..2a9cf5c63 100644
--- a/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json
+++ b/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Can you make an automated test fail when you want it to?<\/p>\n\n<p>If not, how do you know it's testing the correct thing?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "477dd3acb45552ebd9d3abd74691f723",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json b/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json
index 4b80a9e7d..1c7d74644 100644
--- a/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json
+++ b/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2022\/10\/08\/first-impressions-astro\">being introduced to Astro<\/a> in Simon's most recent Pro Tailwind workshop, something else that we discussed was implicit vs explicit coding, and coding defensively.<\/p>\n\n<p>For example, if you had this code:<\/p>\n\n<pre><code class=\"javascript\">const sizeClasses = {\n  small: 'px-3 py-1 text-sm',\n  medium: 'px-5 py-2',\n  large: 'px-7 py-2.5 text-lg',\n}\n\nconst shapeClasses = {\n  square: '',\n  rounded: 'rounded',\n  pill: 'rounded-full',\n}\n<\/code><\/pre>\n\n<p>Both the <code>medium<\/code> size and <code>square<\/code> shape have an implicit value.<\/p>\n\n<p>The <code>small<\/code> size has a text size class of <code>text-sm<\/code> and the <code>large<\/code> size has <code>text-lg<\/code>. As there isn't a text size added for <code>medium<\/code>, it is implicitly <code>text-base<\/code> - the default text size.<\/p>\n\n<p>Likewise, the <code>rounded<\/code> shape has a class of <code>rounded<\/code> and the <code>pill<\/code> shape has <code>rounded-full<\/code>. As a square button doesn't have any rounding, it has an empty string but it is implicitly <code>rounded-none<\/code> - the default border radius value.<\/p>\n\n<p>If we were to code this explicitly, <code>text-base<\/code> and <code>rounded-none<\/code> would be added to their respective size and shape classes.<\/p>\n\n<p>It's mostly personal preference, but explicitly adding the additional classes could potentially future-proof the components if there was a situation where the text size or border radius was being overridden.<\/p>\n\n<p>It also makes it more obvious to anyone reading the code that these values are being set, rather than them needing to make that assumption - assuming that they're aware of the default values at all.<\/p>\n\n<p>It's similar to having this example PHP code:<\/p>\n\n<pre><code class=\"language-php\">function __invoke(string $type, int $limit): void {};\n<\/code><\/pre>\n\n<p>Whilst I'm using type hints for the parameters to ensure that the values are a string and an integer respectively, it's also safe to assume that the type shouldn't be an empty string, so do we check for that?<\/p>\n\n<p>I'd also suggest that the limit shouldn't be a negative integer, so we'd want to check that the value is not less than zero, or if zero isn't being used as an \"all\" value, then we'd want to check that the limit is greater than one.<\/p>\n\n<p>In this case, the type hints add some explicitness to the parameters, but checking for these additional conditions adds another defensive layer to the code - forcing it to return earlier with an explicit error message rather than causing a vaguer error and elsewhere in the application.<\/p>\n\n<p>Personally, I like to be explicit and code defensively, making sure that I try and cover as many edge cases as possible and writing test cases for them.<\/p>\n\n<p>Coming back to the Tailwind example, the majority of us decided to add in extra classes after the exercise and it was an interesting discussion and part of the workshop.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2396dbcb354eade3105e541370b34bef",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json b/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json
index 509e9047e..d1338964d 100644
--- a/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json
+++ b/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There's no value in a test suite that isn't run and the less often it's run, the less likely you are to spot a failure or regression.<\/p>\n\n<p>If the tests are only run weekly, you aren't going to be aware of an issue that could have been introduced at the start of the week until the tests are run.<\/p>\n\n<p>Then, there are more changes that need to be reviewed to find the cause of the issue compared to if it was found sooner.<\/p>\n\n<p>Ideally, everyone should be running tests locally as well as having them run automatically in a CI pipeline for each commit.<\/p>\n\n<p>As soon as a failing commit is pushed, it will be identified and it will be easy to fix or revert.<\/p>\n\n<p>Also, the more often you push changes and in smaller batches - the easier it will be to diagnose and resolve the issue.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8ecf5375b76358c09922dc94523f6dfc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6c69f289-ca43-4731-9729-0341250e0591.json b/content/node.6c69f289-ca43-4731-9729-0341250e0591.json
index 73121ff8e..9a01edc84 100644
--- a/content/node.6c69f289-ca43-4731-9729-0341250e0591.json
+++ b/content/node.6c69f289-ca43-4731-9729-0341250e0591.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In PHP, we have functions like <code>var_dump()<\/code>, <code>dump()<\/code> and <code>dd()<\/code> that are used to debug code and print output to the screen.<\/p>\n\n<p>In Drupal, we have functions like <code>dpm()<\/code> and <code>kint()<\/code>, too.<\/p>\n\n<p>These functions are great for simple debugging but sometimes I need more, which is when I reach for a step debugger - namely, Xdebug.<\/p>\n\n<p>This is common when working in complex legacy code, where you need to be able to see a breakpoint and step through the code to see what path it takes and what the state is at each step.<\/p>\n\n<h2 id=\"enter-xdebug\">Enter Xdebug<\/h2>\n\n<p>Xdebug is a tool I use fairly often and something I have configured on an individual project basis.<\/p>\n\n<p>This week, I spent some time adding it to a new project and ensured my notes and documentation still worked.<\/p>\n\n<p>I use Docker and Docker Compose on Linux, so there are slight changes compared to running PHP natively, so I wanted to make sure it still works.<\/p>\n\n<p>I've added my latest setup to my <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\">Drupal Docker Example repository<\/a> and plan to add it to my standard <a href=\"http:\/\/default\/build-configs\">Build Configs<\/a> setup for Drupal projects.<\/p>\n\n<p>If you use Docker Compose on Linux, it may be useful for you.<\/p>\n\n<p>If you haven't tried Xdebug before, I suggest giving it a try and see if improves your debugging.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "685bea9e2790b5b0bd16d23d8c64a61a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json b/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json
index 70b2987bb..0c5549257 100644
--- a/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json
+++ b/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A quote that stuck out to me from today's Neovimconf conference was this by Bj\u00f6rn Linse (aka bfredl):<\/p>\n\n<blockquote>\n  <p>Don't just rewrite. Re-invent.<\/p>\n  \n  <p>If you're going to start over from scratch, reconsider everything.<\/p>\n<\/blockquote>\n\n<p>This was in the context of what would be added to the core editor, what would be delegated to plugins, etc, but this also applies to other things.<\/p>\n\n<p>I'm discussing with someone whether to build a new Drupal theme or keep iterating on the existing one.<\/p>\n\n<p>If they start from scratch, they can re-invent and re-consider everything and decide which parts of the existing theme to reuse and which to leave and re-create.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "42e38b75bd8ecb458273f77d2cd34883",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json b/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json
index 9f9fd9acf..67c7b2b4e 100644
--- a/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json
+++ b/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since launching my Automated Testing in Drupal email course, over 100 people have subscribed and received the free ten daily lessons where I explain how to start from scratch to build a Drupal module with automated tests and test-driven development.<\/p>\n\n<p>Thanks to everyone who has taken the course so far and those who have provided feedback.<\/p>\n\n<p>Automated testing and test-driven development were game changers for me and enabled me to deliver better projects.<\/p>\n\n<p>If you'd like to take the course and learn how to do automated testing in Drupal, you can <a href=\"http:\/\/default\/atdc\">register for free<\/a> and get them direct to your inbox.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3943dc4ec9de105dc8129ddcc5e62eae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json b/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json
index 23d1194bc..fb1b8ae47 100644
--- a/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json
+++ b/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I wrote about <a href=\"http:\/\/default\/daily\/2024\/11\/25\/nix-the-package-manager\">Nix the package manager<\/a>.<\/p>\n\n<p>To use it, you need to write code in the Nix language in .nix files.<\/p>\n\n<p>To see an example, you can see <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/tree\/main\/nix\">my dotfiles on GitHub<\/a> as well as lots of other people's that they've published.<\/p>\n\n<p>It's a functional language so some of the concepts were new to me, but I picked it up fairly quickly and learned some of the paradigms and conventions.<\/p>\n\n<p>This is the code that installs Nginx on my server:<\/p>\n\n<pre><code class=\"nix\">services.nginx = {\n  enable = true;\n  serverNamesHashBucketSize = 256;\n};\n<\/code><\/pre>\n\n<p>These are some of the packages I have installed on my laptop:<\/p>\n\n<pre><code class=\"nix\">environment.systemPackages = with pkgs: {\n  devenv\n  dog\n  git\n  go\n  jq\n  php\n  phpPackages.composer\n  pv\n  tldr\n}\n<\/code><\/pre>\n\n<p>And this is how to configure processes <a href=\"http:\/\/default\/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">in a devenv configuration<\/a>, which is built with Nix:<\/p>\n\n<pre><code class=\"nix\">processes = {\n  tailwind.exec = ''\n    cd ${drupal.theme.path}\n    watchexec --exts css,twig tailwindcss --config assets\/tailwind.config.ts \\\n      --output dist\/tailwind.css\n  '';\n};\n<\/code><\/pre>\n\n<p>Once you have written the configuration, you can run it and install what you've specified, and it will do it the same way every time.<\/p>\n\n<p>For a crash course in the Nix language, take a look at <a href=\"https:\/\/zero-to-nix.com\/concepts\/nix-language\">https:\/\/zero-to-nix.com\/concepts\/nix-language<\/a> or one of the many open-sourced configurations on GitHub.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7cd6f305207bb1a29052636f877e416e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json b/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json
index 5d3b89bc3..c400489c1 100644
--- a/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json
+++ b/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This evening, I'm presenting a lightning talk at the PHP South West meetup in Bristol.<\/p>\n\n<p>The talk is 'Building \"Build Configs\"' - a Symfony command-line tool I wrote (based on TheAltF4Stream's Rust version with the same name) that generates project-specific build configuration files.<\/p>\n\n<p>Since creating it, I've used it for personal projects, projects for clients, and example projects on GitHub - such as <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\">my Docker Example Drupal project<\/a>.<\/p>\n\n<p>Having a set of standardised and configurable templates makes it much easier and quicker to start a new project, which I did when creating a <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal-commerce-kickstart\">Drupal Commerce Kickstart example<\/a> at DrupalCon.<\/p>\n\n<p><a href=\"http:\/\/default\/presentations\/building-build-configs\">The slides are already online<\/a> and I've created <a href=\"http:\/\/default\/build-configs\">an example video<\/a> where I go from nothing to a ready-to-work-on Drupal website in less than a minute!<\/p>\n\n<p>If you have any questions, hit reply and let me know!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d52c150ed8a1993d5bffe35438c3f3ae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json b/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json
index c02030c47..806fc55c1 100644
--- a/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json
+++ b/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A lot is different between Drupal 7 and 10, with the introduction of Composer, object-orientated code, Symfony components and other third-party libraries, to name a few things.<\/p>\n\n<p>But, when upgrading a project, the business logic may not need to change.<\/p>\n\n<p>How it integrates with the new version of Drupal may change - it may use a different module, such as Paragraphs instead of Field Collection, or be within a Controller or Service class instead of a Drupal \"hook\", but if the majority of the logic can remain the same, it might as well be reused instead of written from scratch.<\/p>\n\n<p>Presumably, it works as it does in Drupal 7, which may not be the case after it's been rewritten, as bugs and issues may have been introduced.<\/p>\n\n<p>This is the approach I took when migrating the Override Node Options module to Drupal 8. I picked a test, migrated it from SimpleTest (Drupal 7) to PHPUnit (Drupal 8), ported enough code to make it pass, and moved to the next test.<\/p>\n\n<p>Most custom applications, though, tend to be rewritten and the old business logic discarded.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>If it works, why rewrite it?<\/p>\n\n<p>Migrate what you can and only rewrite what you need.<\/p>\n\n<p>As someone who works on fixed-price projects and includes a bug-free guarantee, it's in my interests to deliver working and stable software as soon as possible, which is also in my client's interests as they get their new software sooner and not from a drawn-out process where everything is re-done from scratch.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "66217a4b2a3ea98d7ca6fe3ff56a3c40",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json b/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json
index b2e5e6a1d..67dc0b71a 100644
--- a/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json
+++ b/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A scenario for having long-lived feature flags is in a multi-tenant application where the same codebase serves multiple projects - e.g. a multi-site Drupal application or a module reused on multiple websites.<\/p>\n\n<p>This is the use case I have for a client project which uses a multi-site setup to serve multiple websites from the same Drupal codebase.<\/p>\n\n<p>If I need to add a feature to sites 1 and 3 but not site 2 or test a change to only site 2, I can do this by enabling a per-site feature flag.<\/p>\n\n<p>Instead of being removed, these flags will remain until the change can be made permanent on all websites, meaning it can be toggled on and off as needed - allowing each site to be configured separately whilst keeping it easy to maintain by having a single canonical codebase.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "03045df60932b862e9b472db135f3986",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json b/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json
index 0ca585103..b99ced0d7 100644
--- a/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json
+++ b/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been a Git user since my first full-time Developer position in 2010.<\/p>\n\n<p>I've used other version control systems, too, early in my career, but I settled on Git and haven't looked back.<\/p>\n\n<p>I've used GUI tools for Git, such as Sourcetree and GitHub Desktop, but I prefer to use Git on the command line instead of a GUI or TUI.<\/p>\n\n<p>As a Developer who uses a command-line-focused workflow and works mainly in a terminal, there is less context switching, but I want to focus on learning the tool itself rather than a wrapper around it.<\/p>\n\n<p>Some GUIs add their own terminology or functionality, making it difficult for people to debug something on the command line if they experience an issue.<\/p>\n\n<p>It's easier to solve problems if you understand the tool itself.<\/p>\n\n<p>What if I had a favourite Git GUI that became no longer supported or maintained?<\/p>\n\n<p>Would any time spent learning that GUI have been wasted?<\/p>\n\n<p>This was also a reason why I switched to using Docker and Docker Compose instead of pre-built wrappers.<\/p>\n\n<p>I want to better understand and be efficient with the underlying tool, not only someone else's implementation of it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d474dfb74634c98fe69659a4f3c55620",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6e3be613-f4eb-4a14-87cd-398b0161eeda.json b/content/node.6e3be613-f4eb-4a14-87cd-398b0161eeda.json
index bd4da3797..1924632b6 100644
--- a/content/node.6e3be613-f4eb-4a14-87cd-398b0161eeda.json
+++ b/content/node.6e3be613-f4eb-4a14-87cd-398b0161eeda.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A lot of code is written once by one person and not changed again.<\/p>\n\n<p>But it's read by multiple people at multiple times.<\/p>\n\n<p>If the code is read more than it's written, we should be optimising it for readability so it's easier for people to understand.<\/p>\n\n<p>The application doesn't care whether you wrote the code the \"clever\" way or the \"boring\" way, but people will appreciate the more readable version.<\/p>\n\n<p>If I need to review or work on the code in the future, I want to read and understand it easily.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f626ebe8fc2c0602e0f849a7068055c7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6eeb79ee-eae2-41ea-ab7e-56f216daf636.json b/content/node.6eeb79ee-eae2-41ea-ab7e-56f216daf636.json
index 7f62cda66..d22396331 100644
--- a/content/node.6eeb79ee-eae2-41ea-ab7e-56f216daf636.json
+++ b/content/node.6eeb79ee-eae2-41ea-ab7e-56f216daf636.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I said <a href=\"http:\/\/default\/daily\/2024\/06\/21\/dont-use-aliases\">not to use custom shell aliases and functions<\/a> during presentations and group programming sessions to avoid confusion.<\/p>\n\n<p>I use aliases, but they expand after I type them, the same as as snippet in an IDE or text editor.<\/p>\n\n<p>Me and everyone else can see the underlying command, and that's also what's saved in my shell history.<\/p>\n\n<p>I still have the benefit of not having to type the whole command without obscuring it.<\/p>\n\n<p>I used to have custom code in my zsh configuration, but recently <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\/commit\/0df5f17dae4328546b5d08eef141656a5de2b522\">switched to zsh-abbr<\/a>.<\/p>\n\n<p>The first impressions are positive and I no longer need to maintain my custom code.<\/p>\n\n<p>I use aliases for commands I don't want to expand, but I've moved everything else has moved to abbreviations.<\/p>\n\n<p>If you use zsh, I recommend trying it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e8c940daa789af9482140efa9f72c6fe",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json b/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json
index 4cc248a32..6dce0edad 100644
--- a/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json
+++ b/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've written a number of emails about feature flags, or feature toggles, and am a strong advocate of using them whilst developing new features.<\/p>\n\n<p>I've used them a couple of times recently on my website so I wanted to share them as examples.<\/p>\n\n<h2 id=\"experimenting-with-presentation-layouts\">Experimenting with presentation layouts<\/h2>\n\n<p>Firstly, I wanted to experiment with a different layout for my presentation pages.<\/p>\n\n<p>They currently have a list of events, embedded slides and a video recording when there is one.<\/p>\n\n<p>Each event linked to its website, where applicable, and the slides and video were from one of the most recent versions of the presentation.<\/p>\n\n<p>I wanted to change this so each event would have links to its own slides, example code or demo.<\/p>\n\n<p>I didn't want to change this yet for all presentations, only <a href=\"http:\/\/default\/presentations\/sculpin\">my Sculpin talk<\/a> as it's the most recent and, if I like it, later apply it to the others.<\/p>\n\n<p>My website is built with Sculpin, so adding a feature flag was as simple as adding <code>new: true<\/code> to the YAML front matter at the top of the file for that presentation.<\/p>\n\n<p>This is available as <code>page.new<\/code> in the layout file and I can use this <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/commit\/8b721e63fb64f3c98b81353ca9cec7545d72a595\">to load different markup<\/a>.<\/p>\n\n<h2 id=\"rewriting-my-css\">Rewriting my CSS<\/h2>\n\n<p>Secondly, I've been wanting to re-style my website with Tailwind CSS 4 and refactor some of the templating.<\/p>\n\n<p>As this is a change I wanted to be site-wide, I added <code>new_css: true<\/code> to my sculpin_site.yml file.<\/p>\n\n<p>This time, I was able to use <code>site.new_css<\/code> to <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/commit\/fa884644cf5aa233ad22fb28b83c5a0b150b037d\">toggle the loaded stylesheet<\/a> and using Sculpin's environment files - e.g. sculpin_site_dev.yml and sculpin_site_prod.yml - I can be explicit about which stylesheets are used locally and for my live website.<\/p>\n\n<h2 id=\"summary\">Summary<\/h2>\n\n<p>Feature flags are a great approach to splitting up large changes into manageable, deployable pieces, and they don't need to be complicated.<\/p>\n\n<p>Essentially, they are a simple boolean value that you can use to execute different code based on whether it's false or true.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "55f785f8b5b1bcd8bf8f2c8c09ee1e1e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json b/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json
index 8aaa3e81b..e21c0988e 100644
--- a/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json
+++ b/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Previously when I gave my <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS<\/a> talk, I created examples that relate to the event such as something related to that technology or event.<\/p>\n\n<p>The nor(DEV):con website already uses Tailwind CSS so I've been looking for other examples and have started to build some of the <a href=\"https:\/\/getbootstrap.com\/docs\/4.0\/examples\">Bootstrap CSS components<\/a> with Tailwind CSS.<\/p>\n\n<p>I've created the <a href=\"http:\/\/bootstrap-with-tailwind.s3-website.eu-west-2.amazonaws.com\/album\">Album<\/a> and <a href=\"http:\/\/bootstrap-with-tailwind.s3-website.eu-west-2.amazonaws.com\/pricing\">Pricing<\/a> components so far but will likely do more before the conference as I think they're good examples.<\/p>\n\n<p><a href=\"https:\/\/github.com\/opdavies\/bootstrap-with-tailwind\">The source code<\/a> is on my GitHub profile, uses Astro and its Tailwind CSS integration, the default Tailwind configuration with some slight colour and font tweaks, the official Typography plugin and a small custom plugin that adds a \"hocus\" variant for both hover and focus styles.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d4da3e8cb513d3d3feb0000033cee884",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json b/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json
index 3e7443ad4..f3e8ffeff 100644
--- a/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json
+++ b/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You have two or more environments and versions of your application, but you do trunk-based development, so you only have a single branch that you use on all environments.<\/p>\n\n<p>But if all environments have the same code, how can we have differences between them?<\/p>\n\n<p>What if we want a feature enabled on one environment and not the other?<\/p>\n\n<h2 id=\"feature-flags\">Feature flags<\/h2>\n\n<p>Feature flags are an approach I've previously written about. You have two branches of logic within your code, and the flow changes based on whether a flag is enabled.<\/p>\n\n<p>If a flag is enabled, execute the first block of code. Otherwise, execute the second.<\/p>\n\n<p>Now, you enable and disable the required feature flags for each environment.<\/p>\n\n<p><strong>The code is the same for all environments, but the enabled features and functionality are different.<\/strong><\/p>\n\n<p>Then, once the feature has been deployed and released in production, the feature flag can be removed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f85ae7fca421a364a7e48e49450abb31",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json b/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json
index 61186f9ef..c1bd0e33b 100644
--- a/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json
+++ b/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, whilst working on <a href=\"http:\/\/default\/daily\/2024\/02\/19\/introducing-versa\">Versa<\/a>, I was experimenting with different PHPStan levels.<\/p>\n\n<p>Level 1 is the least strict level, and applies the fewest rules and returns the fewest results.<\/p>\n\n<p>As you increase the level, the stricter PHPStan is.<\/p>\n\n<h2 id=\"levelling-up-to-9\">Levelling up to 9<\/h2>\n\n<p>Here is the code to get the values of the <code>--extra-args<\/code> and <code>--working-dir<\/code> options:<\/p>\n\n<pre><code class=\"language-php\">$extraArgs = $input-&gt;getOption('extra-args');\n$workingDir = $input-&gt;getOption('working-dir');\n<\/code><\/pre>\n\n<p>This passed PHPStan level 8, but these are the errors I get when running level 9:<\/p>\n\n<pre><code class=\"language-plain\">------ -------------------------------------------------------------------------------------------------------\n Line   versa\n------ -------------------------------------------------------------------------------------------------------\n 61     Parameter $extraArgs of static method App\\Process\\Process::create() expects string|null, mixed given.\n 62     Parameter $workingDir of static method App\\Process\\Process::create() expects string, mixed given.\n 72     Parameter $extraArgs of static method App\\Process\\Process::create() expects string|null, mixed given.\n 73     Parameter $workingDir of static method App\\Process\\Process::create() expects string, mixed given.\n 84     Parameter $extraArgs of static method App\\Process\\Process::create() expects string|null, mixed given.\n 85     Parameter $workingDir of static method App\\Process\\Process::create() expects string, mixed given.\n 94     Parameter $extraArgs of static method App\\Process\\Process::create() expects string|null, mixed given.\n 95     Parameter $workingDir of static method App\\Process\\Process::create() expects string, mixed given.\n 104    Parameter $extraArgs of static method App\\Process\\Process::create() expects string|null, mixed given.\n 105    Parameter $workingDir of static method App\\Process\\Process::create() expects string, mixed given.\n 119    Parameter $extraArgs of static method App\\Process\\Process::create() expects string|null, mixed given.\n 120    Parameter $workingDir of static method App\\Process\\Process::create() expects string, mixed given.\n------ -------------------------------------------------------------------------------------------------------\n\n[ERROR] Found 12 errors\n<\/code><\/pre>\n\n<p>The issue is that <code>$input-&gt;getOption()<\/code> from Symfony's <code>InputInterface<\/code> returns <code>mixed<\/code> - even though it always returns <code>null<\/code> or a string.<\/p>\n\n<p>If I did <code>--working-dir 2<\/code>, it would return the string <code>\"2\"<\/code>.<\/p>\n\n<p>An empty string throws an error, and an empty value (if there are no extra arguments) returns <code>null<\/code>.<\/p>\n\n<p>So, I know <code>$workingDir<\/code> will always be a string and <code>$extraArgs<\/code> will either a string or <code>null<\/code>.<\/p>\n\n<h2 id=\"passing-level-8\">Passing level 8<\/h2>\n\n<p>To pass level 8, PHPStan needs to be sure the variables are what I think they are.<\/p>\n\n<p>Here's the code I can use to get it to pass:<\/p>\n\n<pre><code class=\"language-php\">$extraArgs = $input-&gt;getOption('extra-args');\n$workingDir = $input-&gt;getOption('working-dir');\nassert(is_string($extraArgs) || is_null($extraArgs));\nassert(is_string($workingDir));\n<\/code><\/pre>\n\n<p>By using <code>assert()<\/code> and throwing an Exception if the condition fails, PHPStan is now happy with the code and my code passes level 9.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Although the extra code gets PHPStan to pass, it it worth it?<\/p>\n\n<p>Is this extra code adding value? Does it make the code more readable or is it likely to prevent a bug?<\/p>\n\n<p>In this case, I know the value will always be the type I expect.<\/p>\n\n<p>I can work around this using a baseline or annotations for PHPStan to ignore these lines, <strong>or is level 8 good enough for this project<\/strong>?<\/p>\n\n<p>Similar to 100% test coverage, is aiming for the highest PHPStan level an objective to be met, or is enough value being added added by the lower level?<\/p>\n\n<p>Which level is right for you and this codebase?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "04a7f9d899ae8eb0f4c33ff32a7dabae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json b/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json
index 1f64b37eb..a5866e7cb 100644
--- a/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json
+++ b/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since PHP 8.1, properties on PHP classes have been able to be marked as <code>readonly<\/code>.<\/p>\n\n<p>Once they've been set, they can't be changed or overwritten.<\/p>\n\n<p>This is great for data transfer objects (DTOs) that you want to be immutable and know the values are the same as when they were set.<\/p>\n\n<p>Here's an example:<\/p>\n\n<pre><code class=\"php\">class MyDto {\n\n  public function __construct(\n    public readonly string $name,\n    public readonly int $age,\n  ) {\n  }\n\n}\n<\/code><\/pre>\n\n<p>I don't need to make the properties private or protected and write getter methods for them.<\/p>\n\n<p>I can make them public,  knowing the values can't be changed.<\/p>\n\n<h2 id=\"readonly-classes\">readonly classes<\/h2>\n\n<p>Since PHP 8.2, the entire class can be <code>readonly<\/code>, making the code cleaner and easier to read.<\/p>\n\n<p>This class does the same as the previous example:<\/p>\n\n<pre><code class=\"php\">readonly class MyDto {\n\n  public function __construct(\n    public string $name,\n    public int $age,\n  ) {\n  }\n\n}\n<\/code><\/pre>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is a great example of how the PHP language continues to evolve and improve, and it's been a great way to make it easier to keep my code clean and with fewer bugs.<\/p>\n\n<p>If you want a way to easily add <code>readonly<\/code> to properties or classes, <a href=\"http:\/\/default\/daily\/2025\/01\/31\/rector\">take a look at Rector<\/a> which can automate it for you.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6fe5dce6168b08b6f939c7125d2ebdb8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json b/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json
index ba2d681d6..f568ff714 100644
--- a/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json
+++ b/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I started using the Nix package manager <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\/commit\/af1d8d37\">in September 2022<\/a> as a replacement for Ansible to manage my dotfiles.<\/p>\n\n<p>Since then, I've switched to daily-driving NixOS as my main operating system and started to use Nix instead of Docker for some development projects.<\/p>\n\n<p>Even though I'm running Linux, there's a benefit to not running containers for simple projects as well as the reproducibility that Nix provides.<\/p>\n\n<p>I hadn't invested much time in using Nix as Docker replacement for Drupal projects, but this week, I've started to look at <a href=\"https:\/\/devenv.sh\">devenv<\/a> - a development tool based on Nix.<\/p>\n\n<p>As well as declaring and locking the package versions I need for each project, it also manages the services I need, such as PHP-FPM and MariaDB or MySQL.<\/p>\n\n<p>It also configures Git hooks, test scripts and custom processes, such as running Tailwind CSS.<\/p>\n\n<p>I've configured it for a few projects this week and it could be a potential Docker replacement for me.<\/p>\n\n<p>If you want to see an example, <a href=\"https:\/\/github.com\/opdavies\/drupal-london-meetup\/blob\/main\/devenv.nix\">see this repo on GitHub<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d6d6e37268d4aebacb46e15def1075f8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json b/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json
index e256fca6f..1d2c4cc3b 100644
--- a/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json
+++ b/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There's a common saying about not deploying changes on a Friday to prevent outages or issues before the weekend.<\/p>\n\n<p>I've also seen this where people won't deploy after a particular time of the day as it's too close to the evening.<\/p>\n\n<h2 id=\"when-did-you-last-deploy%3F\">When did you last deploy?<\/h2>\n\n<p>The longer it's been since the last deployment, the risker each deployment is.<\/p>\n\n<p>If there are weeks or months of changes, it will be risky regardless of which day it is.<\/p>\n\n<p>If your last deployment was an afternoon, deploying a small change the following morning will be low risk, even on a Thursday and Friday.<\/p>\n\n<h2 id=\"conclusion\">Conclusion<\/h2>\n\n<p>If you're nervous about deploying on a Friday, I think you need to aim for smaller and more frequent deployments to minimise the risk.<\/p>\n\n<p>The issue isn't when you're deploying. You likely need to do so more often.<\/p>\n\n<p>If there is an issue after a large release, it will take more time to debug or roll back compared to a small release which is easier to find and fix the problem or revert that single change.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "531214c785675f0543e778a343d5a677",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json b/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json
index 7e84cc44d..2692a1512 100644
--- a/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json
+++ b/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Before I started using atomic CSS classes, I used to use a popular component-based CSS framework.<\/p>\n\n<p>You'd include the styles as well as the HTML markup you needed.<\/p>\n\n<p>Whilst using the other framework, I started to sprinkle CSS classes on top of my existing styles, to make it easy to set values such as text sizes, colours, margin and padding without repeating myself and duplicating styles.<\/p>\n\n<p>Later, I realised I didn't need the original framework and I could do it myself with atomic classes.<\/p>\n\n<p>Page by page and component by component, I refactored everything to use atomic classes.<\/p>\n\n<p>Once everything was refactored, I removed the original framework.<\/p>\n\n<p>I haven't looked back.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6bf45d9427593b0a048a809e9b03eb1b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json b/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json
index 113153108..07354769b 100644
--- a/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json
+++ b/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Did you know you can have more than one version of your website in production at the same time?<\/p>\n\n<p>If you're migrating to a new platform or upgrading to a new major version, such as Drupal 7 to Drupal 11, you don't need to do it all at once.<\/p>\n\n<p>You can do it incrementally, and seamlessly for end users.<\/p>\n\n<p>The MVP for your new website can be a particular section or a single page that is developed and launched to production alongside the current website.<\/p>\n\n<p>Depending on the path someone goes to, they'll either see the new website or the old one.<\/p>\n\n<p>Focusing on delivering a single page or section of a website is much faster compared to rebuilding the entire thing, it's a lot less risky as the feedback loop is much shorter and you get feedback from real users.<\/p>\n\n<p>Once you have the new MVP deployed to a hosting environment, you can configure a proxy to assign traffic between it and the existing hosting based on path, request headers, or a combination of different options.<\/p>\n\n<p>This is an approach I've taken with my website as I've upgraded between different versions of Drupal and also static site generators such as Jekyll, Astro and Sculpin.<\/p>\n\n<p>Instead of waiting for months to deliver a new website to production, do it in days or weeks.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "36902cd3f90743c2ffd35168c819c294",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json b/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json
index c0134866c..3d491a45e 100644
--- a/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json
+++ b/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When using a version control system, such as Git, commits are quick and cheap.<\/p>\n\n<p>I like to make small commits as often as possible whilst working on a task.<\/p>\n\n<p>For example, when doing test-driven development, I commit my changes wherever the tests are passing or after a refactor.<\/p>\n\n<p>Each commit is a checkpoint I can easily roll back to if needed.<\/p>\n\n<p>I've never regretted making a commit, but I've regretted not making one.<\/p>\n\n<p>Commits are cheap, but debugging without a recent commit is expensive.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4931ceb5b78e05e6999e53dccad1f30d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json b/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json
index 1b5077f4f..90ded8f67 100644
--- a/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json
+++ b/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday I showed <a href=\"http:\/\/default\/daily\/2025\/04\/07\/nix-rst2pdf\">how I'm using Nix to build my presentation slide decks<\/a> with rst2pdf.<\/p>\n\n<p>This allows me to run a simple command like <code>nix build .#test-driven-drupal<\/code> to build the slides for the given presentation.<\/p>\n\n<p>But I can use other tools to make this even easier.<\/p>\n\n<p>What if I wanted to have a list of the available presentations to select from, and selecting one would build it?<\/p>\n\n<p>Following the UNIX philosophy, I can use multiple tools together to achieve this.<\/p>\n\n<p>Firstly, I can run <code>nix flake show --json<\/code> to show the output from my flake.nix file, which looks something like this:<\/p>\n\n<pre><code class=\"json\">{\n  \"devShells\": { ... },\n  \"formatter\": { ... },\n  \"packages\": {\n    \"x86_64-linux\": {\n      \"build-configs\": { ... },\n      \"sculpin\": { ... },\n      \"shared\": { ... }\n    }\n  }\n}\n<\/code><\/pre>\n\n<p>The package names - a.k.a. the presentation names - are what I want to select from.<\/p>\n\n<p>I can parse the JSON object with <code>jq<\/code>, remove any unwanted options with <code>grep -v<\/code> and use <code>fzf<\/code> to give me a list I can fuzzy search in.<\/p>\n\n<p>In a Bash script, I can assign this to a variable:<\/p>\n\n<pre><code class=\"bash\">selected=$(nix flake show --json | jq --raw-output '.packages[\"x86_64-linux\"] | keys[]' | grep -v shared | fzf)\n<\/code><\/pre>\n\n<p>Once I have selected a name, I can call <code>nix build<\/code> on it.<\/p>\n\n<pre><code class=\"bash\">nix build .#\"$selected\"\n<\/code><\/pre>\n\n<p>This is a simple example, but it shows how programs can be used together and output can be passed through each program to get the result you want.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6a6105cc8b6ef3e9fadb5aec0f56aaeb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json b/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json
index e8239201c..af743fb37 100644
--- a/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json
+++ b/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Automated tests aren't just checks to verify your software is working.<\/p>\n\n<p>They're a communication tool that shows people working on the code how it's supposed to be used.<\/p>\n\n<p>It's a form of documentation.<\/p>\n\n<p>They are living examples of how to use the code with the benefit that you can run them and see if they still work, which isn't the case for markdown files or other types of static documentation that can become outdated.<\/p>\n\n<p>Something I often do when evaluating or using software that has a test suite is review the tests and see how it's supposed to be used.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9de3480ade1a052c5db39773e18ab7f3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json b/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json
index c66267fc2..750f6e11e 100644
--- a/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json
+++ b/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I was writing Pulumi code in Typescript, and I although I have autocompletion, I mistyped the name of a property.<\/p>\n\n<p>But, because of the types that I'd declared and how I have Neovim configured, the error was immediately shown, and I was able to fix the typo and what would have been a compilation error if I'd tried to run it.<\/p>\n\n<p>It only took a second or two for me to make and fix the mistake.<\/p>\n\n<p>I didn't need to run the code or commit it and push it to a CI pipeline to find out that there was a bug.<\/p>\n\n<p>I found out and fixed it immediately, and moved on as if I hadn't written the typo at all. This is why I like types and static analysis.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f16171ae436a71a3e9a07afc18cf2a36",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json b/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json
index bcfa59a04..00627a342 100644
--- a/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json
+++ b/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Did you know you can use programs like lynx or w3m to browse the web on the command line?<\/p>\n\n<p>No CSS, JavaScript or images, just plain text.<\/p>\n\n<p>Similar to using a screen reader, you can quickly tab between focusable elements like links and buttons to find what you need.<\/p>\n\n<p>While it will probably not replace Firefox or Chrome as a daily driver, it is useful to know if you're on a server without a browser or  need to quickly find information without distractions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9da4d3a86f1c672f86f84b3581e8b6e9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json b/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json
index 630b5d6e7..234b727bf 100644
--- a/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json
+++ b/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>suckless.org is the \"home of dwm, dmenu and other quality software with a focus on simplicity, clarity, and frugality\".<\/p>\n\n<p>Here's an excerpt from <a href=\"https:\/\/suckless.org\/philosophy\">the Suckless philosophy<\/a>:<\/p>\n\n<blockquote>\n  <p>We are the home of quality software such as dwm, dmenu, st and plenty of other tools, with a focus on simplicity, clarity and frugality. Our philosophy is about keeping things simple, minimal and usable. We believe this should become the mainstream philosophy in the IT sector. Unfortunately, the tendency for complex, error-prone and slow software seems to be prevalent in the present-day software industry. We intend to prove the opposite with our software projects.<\/p>\n<\/blockquote>\n\n<p>I've previously wondered <a href=\"http:\/\/default\/daily\/2024\/11\/08\/what-will-be-included-in-drupal-cms\">what would be included in future versions<\/a> of Drupal or Drupal CMS after usually needing to install the same modules on every new project.<\/p>\n\n<p>But I was recently wondering what if more was removed from Drupal?<\/p>\n\n<p>What if modules like Layout Builder and JSON:API that aren't needed on every project were moved into contrib and added via Composer when needed, making Drupal core smaller?<\/p>\n\n<p>I'm not saying that it will or should happen, but it's an interesting to think about how much of what's in Drupal currently is used.<\/p>\n\n<p>Core functionality like user registration and logins, password management, content types, fields and menus should stay.<\/p>\n\n<p>But I can think of a number of other things that could be removed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "059042bee3271e131a06b01030f2f4fd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json b/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json
index c0db015be..807080b9f 100644
--- a/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json
+++ b/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The value in a CI pipeline is when its commands and checks are running successfully, and the pipeline is passing.<\/p>\n\n<p>And then keeping it passing.<\/p>\n\n<p>If the pipeline fails, it loses all of its value.<\/p>\n\n<p>Passing should be its default state, and effort should be made to ensure it continues to pass.<\/p>\n\n<p>If a pipeline fails, the change is not deployed, and the failure should be investigated and rectified so the pipeline is returned to a passing state and providing value.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "10d1ecac9f555ea67f22615547fb1f6a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.739826e2-62a6-4726-8294-5359016f8d24.json b/content/node.739826e2-62a6-4726-8294-5359016f8d24.json
index f2c48f95e..708d31faf 100644
--- a/content/node.739826e2-62a6-4726-8294-5359016f8d24.json
+++ b/content/node.739826e2-62a6-4726-8294-5359016f8d24.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently updated my <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\">Drupal Docker example project<\/a> to Drupal 10.1.5 and have been spotting new things.<\/p>\n\n<p>From British English as my default option during installation, UX improvements to the admin pages, and developer settings such as Twig caching being configurable in the admin UI.<\/p>\n\n<p>Something I've loved since Drupal 8 is the constant new features and iterative improvements being added to Drupal core.<\/p>\n\n<p>I'm looking forward to finding more of these as I keep upgrading my Docker example project as well as others.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ea5781765624e864ecd53e39eda44615",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json b/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json
index 540ab7432..49abc9265 100644
--- a/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json
+++ b/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I released the most recent episode of the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a>.<\/p>\n\n<p>My guest this week is Jochen Lillich - the Monospace Mentor, aka geewiz.<\/p>\n\n<p>Jochen and I discuss content creation, live streaming on Twitch and YouTube, infrastructure automation, Linux, mentoring and, of course, mechanical keyboards.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/17-jochen-lillich\">Listen to the episode now<\/a>.<\/p>\n\n<p>I've been a fan of Jochen's content and Twitch streams for a long time, and it was great to meet him at DrupalCon Lille and have him on the podcast.<\/p>\n\n<p>I have a few more recorded episodes that will be released over the next few weeks.<\/p>\n\n<p>If you want to be a guest on Beyond Blocks, <a href=\"https:\/\/forms.gle\/5LCDdrXyqyrbC4ry9\">let me know<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4fe4a1ea6d73ab3a78060bfa1a6153e2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json b/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json
index 52b4f69c2..7cf7199c0 100644
--- a/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json
+++ b/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I read <a href=\"https:\/\/kevinquillen.com\/ddev-being-considered-official-drupal-development-environment\">a post by Kevin Quillen<\/a> titled 'DDEV being considered as the \"official\" Drupal development environment'.<\/p>\n\n<p>I've been a DDEV user, and I've also used most, if not all, of the other popular Drupal development environments.<\/p>\n\n<p>These days, I use <a href=\"http:\/\/default\/daily\/2022\/08\/21\/2022-08-21\">my own Docker Compose-based setup<\/a>, but I feel having an official development environment would be an excellent move for the Drupal community and project - and for new Drupal users, evaluators and contributors in particular.<\/p>\n\n<p>Anything that lowers the barrier to using or contributing to Drupal is a good thing and allows for more focused documentation and a simpler onboarding experience, similar to what other projects have - such as Laravel with Homestead, Valet and now, Sail.<\/p>\n\n<h2 id=\"collaboration-is-key\">Collaboration is key<\/h2>\n\n<p>Instead of multiple similar projects creating the same features and fixing the same issues, there could be an opportunity to collaborate or even combine projects and resources in the future.<\/p>\n\n<h2 id=\"but-what-about-existing-teams-and-projects%3F\">But what about existing teams and projects?<\/h2>\n\n<p>If your company or team already uses another option, you can continue to use it.<\/p>\n\n<p>If you have an existing solution, I don't think it will be removed or abandoned in the near future.<\/p>\n\n<p>But, for new Drupal users and teams, one official development environment would be a big plus.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6549977c5d3e11dfcbc2dadcbeef7dea",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json b/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json
index a4e733f3f..dd5704867 100644
--- a/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json
+++ b/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you're working on a team or project that uses pull or merge requests, then <a href=\"http:\/\/default\/daily\/2024\/05\/17\/why-i-dont-commit-with--m\">writing commit messages with detailed descriptions<\/a> using the message body and not just the subject line, will result in better pull requests.<\/p>\n\n<p>Whatever text you put in the message body will be used as the description for your pull or merge request, as well as the subject line being used for the title.<\/p>\n\n<p>So, instead of writing the message after completing the work, when you may forget important details, write it at the time in the message when writing the commit and re-use it in the PR or MR.<\/p>\n\n<p>Pull or merge requests with more information and detail are more likely to be accepted and merged.<\/p>\n\n<p>The text will also remain in the pull or merge request, even if <a href=\"http:\/\/default\/daily\/2024\/05\/11\/don-t-delete-my-commit-messages\">someone squashes your commits and deletes the old messages<\/a>.<\/p>\n\n<p>The issue then is, <a href=\"http:\/\/default\/daily\/2024\/05\/15\/should-you-include-issue-ids-in-your-commit-messages\">what if you move to a different Git hosting service<\/a>?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dc029e11f32f64e5a3c7d6d908e5572f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json b/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json
index 3ac95a887..63555c5d2 100644
--- a/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json
+++ b/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Another reason I don't like squashing commits within pull\/merge request is losing detail within the commit messages.<\/p>\n\n<p>As someone who usually writes detailed commit messages that explain why the change is being made, any gotchas or alternative approaches that were tried, etc, I want that information to be retained.<\/p>\n\n<p>Previously, when working on a team and doing merge\/pull requests, when merging a feature or release branch, either the tool or reviewer would delete all the messages from the squashed commits.<\/p>\n\n<p>The time I spent writing the messages was wasted, and the information was lost.<\/p>\n\n<p>I'd rather <a href=\"http:\/\/default\/daily\/2024\/05\/10\/optimise-for-revertability\">keep the original commits intact<\/a> but, if you need to squash commits, please don't remove the previous messages as they could be useful in the future.<\/p>\n\n<p>People can see the changes by viewing the commits, but the information within the commit messages are valuable, too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "90c94c7043655d521ff0ddc32b560713",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json b/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json
index bdcc7442a..5b15b2100 100644
--- a/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json
+++ b/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was listening to a podcast today, and the question was mentioned - \"What if there was no open-source software?\".<\/p>\n\n<p>As a self-taught Developer who has worked with open-source technologies and become an expert in Drupal - an open-source content management system - this would have had a big effect.<\/p>\n\n<p>If there were no open-source frameworks or CMSes like Drupal, Symfony, Laravel or Vue.js, Developers would need to write everything from scratch, and companies would need to pay for the extra time.<\/p>\n\n<p>There would be no reusable knowledge as Developers move to different companies as everything would be written in-house.<\/p>\n\n<p>There would be no communities and events like conferences and meetups for open-source technologies.<\/p>\n\n<p>As well as frameworks, what about languages like PHP that are open-sourced? Would companies also need to write and maintain their own programming languages?<\/p>\n\n<p>What about Linux, which I use every day for my desktop environment and servers, and other tools like Neovim, PHPStan, PHPUnit and Pest that are all open-source?<\/p>\n\n<p>Even as someone who contributes to and sponsors open-source projects and their Developers, it's still a shock to think how things would work without open-source software.<\/p>\n\n<p>If you use open-source software, please consider sponsoring, supporting or contributing to the projects you use and depend on.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c70e6f1af7689e9704999c27d288916d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json b/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json
index 92e31f568..b3f72d309 100644
--- a/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json
+++ b/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was recently explaining and demonstrating Nix and direnv to a colleague and showing how, when I moved into a directory, new packages or different versions of packages became available.<\/p>\n\n<p>If I left the directory, I was reverted back to my global packages and versions.<\/p>\n\n<p>In this demonstration, I was showing how I can have different versions of PHP and node for a particular project - replacing a lot of what I'd previously used tools like Vagrant and Docker for.<\/p>\n\n<p>I came up with a comparison between Nix and nvm - the node version manager - a tool that allows you to install multiple versions of nodejs and switch between them.<\/p>\n\n<p>Using Nix and direnv is more seamless, but it works for everything.<\/p>\n\n<p>I'm able to switch versions of PHP, MySQL, MariaDB, PostgreSQL or anything else I need with Nix.<\/p>\n\n<p>Not just node, and without needing containers.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1f1938498491ff40c88d4e5b99fc617b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json b/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json
index b2f11bc35..ed1a583c1 100644
--- a/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json
+++ b/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"http:\/\/default\/presentations\/sculpin\">a static site generator<\/a>.<\/p>\n\n<p>But what if you've already got a dynamic website that you no longer need to be editable?<\/p>\n\n<p>What if it was for an event that has passed, like a DrupalCamp?<\/p>\n\n<p>If you no longer need to update the content via the admin UI, you could archive it by converting it to a static website.<\/p>\n\n<p>Then you no longer need to maintain and update it, and <a href=\"http:\/\/default\/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"http:\/\/default\/daily\/2025\/03\/15\/tome\">Tome, a static site generator for Drupal<\/a>, or use command line tools like <code>wget<\/code> with options like <code>--mirror<\/code> to create a static version by crawling a live website.<\/p>\n\n<p>There are <a href=\"https:\/\/www.drupal.org\/docs\/administering-a-drupal-site\/creating-a-static-archive-of-a-drupal-site\">a few options on Drupal.org<\/a>, which will also work with other CMSes and frameworks.<\/p>\n\n<p>This is what I've done for old websites like our old DrupalCamp Bristol websites.<\/p>\n\n<p>That means they're still available for people to see, but without the maintenance and security overhead.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a776e5053b9f9b1276b131cb30130d86",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json b/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json
index 3f40d7e45..ef0665c68 100644
--- a/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json
+++ b/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Of course, your application code is important.<\/p>\n\n<p>In a Drupal project, in addition to the framework itself, you'll likely have additional community-contributed (contrib) modules that add functionality and any project-specific custom modules and themes.<\/p>\n\n<p>The application code, though, is only one piece of the puzzle.<\/p>\n\n<p>You also need infrastructure code to ensure the code runs with the correct dependencies and versions for everyone working with it.<\/p>\n\n<p>You don't want people using different versions of PHP or a different web server.<\/p>\n\n<p>You want consistency between all environments to lower the risk of introducing bugs.<\/p>\n\n<p>You also want the infrastructure code to be reliable and simple to run and bundled with the code for each access.<\/p>\n\n<p>Instead of using something like MAMP or XAMPP, software like Nix and Docker (or wrappers like Lando and DDEV) have files that can be kept with the application code.<\/p>\n\n<p>This makes it much easier for people to contribute, whether they're employees, freelancers, consultants or open-source contributors.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0cc84c28d13f650205484c629a9967a2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json b/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json
index fa13669ce..5ad9cf821 100644
--- a/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json
+++ b/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In <a href=\"http:\/\/default\/daily\/2024\/05\/31\/putting-glue-on-pizza\">yesterday's email<\/a>, I mentioned some of the recent issues I've seen from AI tools.<\/p>\n\n<p>I'm wary of any code generated by AI, as I've often found it to be incorrect.<\/p>\n\n<p>If you rely on AI-generated code, I'd be especially wary if it also generates the automated tests.<\/p>\n\n<p>Automated tests verify your application works as expected, so you need to ensure they are testing the correct things and the logic is correct.<\/p>\n\n<p>Can you make a test purposely fail by changing some logic within the test or implementation code?<\/p>\n\n<p>Is it clear what each test is doing?<\/p>\n\n<p>Are the tests running the implementation code or just testing mocks or running meaningless assertions like <code>self::assertTrue(TRUE)<\/code>?<\/p>\n\n<p>Writing tests is about building confidence, which you can't do if you don't know what your tests are testing or how.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9270caa76092aa60451a52a5d428601a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json b/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json
index 0da60f7fc..027ff1fec 100644
--- a/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json
+++ b/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as building applications with PHP and Drupal, I spend a lot of time helping others and \"paying it forward\".<\/p>\n\n<p>I write and contribute to open-source software and offer free online pair programming sessions to work on open-source projects.<\/p>\n\n<p>I speak at conferences and meetups.<\/p>\n\n<p>I create content, including videos and coding live streams.<\/p>\n\n<p>I mentor at in-person events, such as DrupalCon, and for bootcamps, such as School of Code.<\/p>\n\n<p>I've organised events, such as PHP South Wales and DrupalCamp Bristol, and reviewed session submissions for DrupalCon.<\/p>\n\n<p>But I wouldn't have been able to do this without others doing the same when I was learning and getting into software development.<\/p>\n\n<p>In July 2008, when I was evaluating technologies, I posted a question on a forum (I was learning HTML, PHP and MySQL then).<\/p>\n\n<p>Someone replied and recommended using Drupal, which is how I learned about the project.<\/p>\n\n<p>If they hadn't done that, I may not be in the position I am now.<\/p>\n\n<p>I might not have found Drupal, contributed to it, worked for the Drupal Association, or spoken at DrupalCon.<\/p>\n\n<p>Now, it's my turn to pay it forward.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "43ead52317b471703708839250e11a67",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json b/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json
index b96663317..a51811b4d 100644
--- a/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json
+++ b/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After speaking at PHP Oxford last January, I'm happy to be going back to Oxford to give my first presentation in 2025 at the renamed PHP Thames Valley meetup.<\/p>\n\n<p>The event is the 20th of March and I'll be speaking about Sculpin - the PHP static website generator that I use for my personal website.<\/p>\n\n<p>I'll explain what static site generators are, why I like them and some of Sculpin's core concepts before jumping into a live demo.<\/p>\n\n<p><a href=\"https:\/\/www.meetup.com\/php-thames-valley\/events\/305915971\">RSVPs are open<\/a> for the event and I'd love to see you there!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "befbe4ca73c04262f510b6bce517e12f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json b/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json
index a98b3ffe5..c2f0cc6e7 100644
--- a/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json
+++ b/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I started to write a new class and was trying to decide what to name it and what pattern I wanted to follow.<\/p>\n\n<p>Option 1:<\/p>\n\n<pre><code class=\"php\">class StoreInformationDownloader {\n\n  public function download() {\n    \/\/ ...\n  }\n}\n<\/code><\/pre>\n\n<p>Option 2:<\/p>\n\n<pre><code class=\"php\">class DownloadStoreInformation {\n\n  public function execute() {\n    \/\/ ...\n  }\n}\n<\/code><\/pre>\n\n<p>Option 1 is a typical Service class.<\/p>\n\n<p>Option 2 follows the Command or Action pattern.<\/p>\n\n<p>Which would you choose?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "029c147e61f92d36ce162b6e31eefed7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json b/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json
index 5ff72c7df..d31f67422 100644
--- a/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json
+++ b/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>tmux is a \"terminal multiplexer\" - a program that makes one terminal window into many.<\/p>\n\n<p>I use the terminal a lot and am often switching between codebase so this is very useful for me.<\/p>\n\n<p>I use a different session for each codebase. If I'm working on one and need to switch to another, I can detatch from one session and attach to another. Later, when I'm ready to switch back, I do the same again.<\/p>\n\n<p>I usually have multiple windows inside a session. Neovim will be in the main one, and I can run separate commands - especially long-running ones like watchers - with their own windows.<\/p>\n\n<p>If I need to split a window and have Neovim on the left and a terminal for running tests on the right, I can do this with different panes.<\/p>\n\n<p>Being able to organise my workspace in this way has become a big part blogof my development workflow and my productivity.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b46a6b2e5b2994af854133e567634c6c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.77377a19-7488-40de-a041-f488b3ae597c.json b/content/node.77377a19-7488-40de-a041-f488b3ae597c.json
index e85505c96..7fea75402 100644
--- a/content/node.77377a19-7488-40de-a041-f488b3ae597c.json
+++ b/content/node.77377a19-7488-40de-a041-f488b3ae597c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As of today, <a href=\"https:\/\/www.drupal.org\/u\/opdavies\">my user profile on Drupal.org<\/a> says I've been on it for 16 years.<\/p>\n\n<p>Originally self-learning HTML and CSS to build a website for a Tae Kwon-Do School I used to train at, I later started to learn PHP and MySQL before trying Drupal after it was suggested to me in a response to a question on a forum (which was also built with Drupal).<\/p>\n\n<p>Since then, I've done great things with Drupal and met many great people at different events.<\/p>\n\n<p>I've even <a href=\"http:\/\/default\/podcast\">started to interview some of them<\/a> on my podcast.<\/p>\n\n<p>Here's to the next 16 years, and I'm very excited so see where Drupal and PHP go.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b4f1eb8f00f69ca46c2ae3c230ebc37d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.781bcd5b-be77-4514-bffc-aa56d829aaff.json b/content/node.781bcd5b-be77-4514-bffc-aa56d829aaff.json
index 281dec7d6..d1035f077 100644
--- a/content/node.781bcd5b-be77-4514-bffc-aa56d829aaff.json
+++ b/content/node.781bcd5b-be77-4514-bffc-aa56d829aaff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2022\/11\/20\/version-controlled-commented-out-code\">In a previous email<\/a>, I wrote about commented-out code and whether it should remain in a codebase - especially if it's version controlled and there's a commit log of all changes.<\/p>\n\n<p>But what about TODO comments that remind you to do something?<\/p>\n\n<p>When I think of TODO comments, I think of times when I've found them left in codebases from a long time ago by Developers who no longer work on it - never to be looked at again.<\/p>\n\n<p>I recently removed a small number from a codebase I added while working on the first MVP.<\/p>\n\n<p>They were comments like \"Move this to a repository\" or \"Remove this hard-coded value and make this configurable\".<\/p>\n\n<p>These weren't things that would affect the functionality of the code - but nice-to-haves, things that could be done differently, or reminders of things where hard-coded values were fine but would need to be replaced in the future.<\/p>\n\n<p>Instead of being code comments that only I was aware of, I moved them into the issue-tracking system I'm using. This allows the client to have visibility of them and that they can be scheduled and prioritised alongside other work, providing a truer reflection of the current tasks.<\/p>\n\n<p>Some have since been addressed, but some will remain and be actioned in the future. If they were still code comments, they might not have been addressed at all, so the issue tracker seems like the better place for them to be.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0cb985cce483116ecdf0ef9bbb61febe",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json b/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json
index a2c803d8d..f21190714 100644
--- a/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json
+++ b/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When using <code>git log<\/code> to look through the history of codebases, I often see large commits that combine several changes.<\/p>\n\n<p>These also lead to vague commit messages like \"Changes\", \"wip\" or \"Fixes\".<\/p>\n\n<p>These aren't helpful when reviewing the history and large commits are difficult to review and revert if there is a problem.<\/p>\n\n<p>Each commit should be focused on a single change, whether its adding part of a new feature, fixing a bug or refactoring.<\/p>\n\n<p>If it's a combination, they should be split into separate commits.<\/p>\n\n<p>Each commit should have its own well-written commit message that explains why the change was needed, any consequences or manual deployment steps, alternative approaches that were tried, issues encountered and any follow up actions.<\/p>\n\n<p>If you can't properly describe the changes made in a commit, the commit is too big.<\/p>\n\n<p>You should uncommit the changes and use <code>git add -p<\/code> to create a more focused commit.<\/p>\n\n<p>This is why <a href=\"http:\/\/default\/daily\/2024\/05\/11\/don-t-delete-my-commit-messages\">I don't squash commits<\/a>.<\/p>\n\n<p>If people have made an effort to create good commits with good commit messages, I don't want them to be lost when the commits are merged.<\/p>\n\n<p>I want to keep the history of the changes intact and as it originally was.<\/p>\n\n<p>I do sometimes need to <a href=\"http:\/\/default\/daily\/2025\/02\/11\/tidy\">tidy up my own commits<\/a>, though, before I push them for anyone else to see.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4fba08380c1f4dbf231499fd7ddea935",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json b/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json
index f097b5cdf..d0d175c70 100644
--- a/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json
+++ b/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm happy to be speaking at DrupalCamp Belgium next month, on the 10th and 11th of May in Ghent.<\/p>\n\n<p>I'll be presenting two sessions on <a href=\"https:\/\/www.drupalcamp.be\/en\/drupalcamp-ghent-2024\/schedule\/friday\">automated testing in Drupal<\/a> (Friday) and <a href=\"https:\/\/www.drupalcamp.be\/en\/drupalcamp-ghent-2024\/schedule\/saturday\">Tailwind CSS<\/a> (Saturday).<\/p>\n\n<p>I spoke about testing most recently at DrupalCon Lille, and I'm looking forward to updating my Tailwind talk again to include the latest features within the framework.<\/p>\n\n<p><a href=\"https:\/\/www.drupalcamp.be\/en\/drupalcamp-ghent-2024\/tickets\">Tickets are still available<\/a> and it would be great to see you there.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3e72cb7c3d2fb565211c4e716fbe236a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json b/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json
index 9f681818b..ce97784e5 100644
--- a/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json
+++ b/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2025\/02\/07\/less\">having less code than you started with<\/a>, another good type of change is one where there are tests accompanying the production code.<\/p>\n\n<p>Whether the tests were written after the code or before with a test-driven development approach, the main thing is that there are tests when the code is committed.<\/p>\n\n<p>There should also be more test code than production code.<\/p>\n\n<p>There is only one implementation of the production code, but there should be multiple tests for it.<\/p>\n\n<p>There should be different tests for different situations, such as different types of input and no input, testing for throwing Exceptions and other failure cases and not just the \"happy path\".<\/p>\n\n<p>Looking at the diff of a commit or merge request, there should be more changes to the test then the code it's testing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3da78a8b0a4a8e0177c79d863316c825",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json b/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json
index 3b83f8ba2..eae8f2cbd 100644
--- a/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json
+++ b/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>An approach I like to make my Drupal code more maintainable is to write less of it and move any generic PHP code into separate framework-agnostic libraries.<\/p>\n\n<p>These could be in open-sourced packages installed from Packagist or kept within the same repository.<\/p>\n\n<p>Having less Drupal-specific code keeps modules smaller and easier to maintain and upgrade.<\/p>\n\n<p>If I need to upgrade a module from Drupal 7 to Drupal 10, I can reuse the generic code and focus on changing its integration points with Drupal to make it compatible.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "42c6dd915ed7b6d8f3872f4c213105fb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json b/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json
index 75b792691..9232b20a0 100644
--- a/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json
+++ b/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I gave my <a href=\"http:\/\/default\/talks\/tdd-test-driven-drupal\">Test Driven Drupal talk<\/a> to the Drupal London user group.<\/p>\n\n<p>The majority of the talk was the same as in previous versions, but I decided to live code the demo section this time instead of demonstrating with slides.<\/p>\n\n<p>I've done live coding demos in talks before and have done <a href=\"https:\/\/www.youtube.com\/@opdavies\">live streams on YouTube<\/a>, but live coding during a talk is harder as there's a time limit before the next speaker starts or before everyone gets thrown out of the building before it closes.<\/p>\n\n<p>I've seen live coding demos go well and take a lot from them, but I've also seen them not go well and it can be stressful and awkward for the speaker as well as the audience.<\/p>\n\n<p>I had some unexpected issues during my demo which the audience were able to help me with, which is why I enjoy pair and group programming. People can spot my typos for me!<\/p>\n\n<p>When done well, I think live coding can be very impactful when it's done well.<\/p>\n\n<p>It's something I want to get better at, and I plan to do more YouTube streams soon, such as refreshing my <a href=\"http:\/\/default\/atdc\">automated testing email course<\/a> with some new examples, so subscribe on YouTube if you want to know when I next go live.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b42fcb964b1303b371ff145dd35982e1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json b/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json
index 5f4767f4f..ec17899b1 100644
--- a/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json
+++ b/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/09\/28\/testing-personal-projects\">Do some Developers skip writing tests for their personal projects<\/a> because they think it's a chore?<\/p>\n\n<p>If they've written the code, so they then think it's too much work to write tests or need to move on to the next task?<\/p>\n\n<p>Is it boring to write tests for code that's already written and will pass straight away?<\/p>\n\n<p>This is why I do test-driven development and start with a failing test and then write code to make it pass.<\/p>\n\n<p>Then, I add more to the test until it fails and then get that to pass.<\/p>\n\n<p>When that test is finished, I'll move to a new test for a different piece of functionality.<\/p>\n\n<p>I like this approach of working in small feedback cycles and alternating between failing and passing tests.<\/p>\n\n<p>Testing this way isn't boring or a chore and much more interesting for me compared to writing all the code first and maybe writing the tests later.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4b2d47376db0c887f15bedf49de35711",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json b/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json
index 87d2e3ebf..4d5d3eb4d 100644
--- a/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json
+++ b/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently updated a website to the latest version of Drupal.<\/p>\n\n<p>Doing so introduced a bug in a contributed module I was using.<\/p>\n\n<p>A fix was committed to the 2.x branch of the module, which is still in an unstable alpha phase, and the issue was closed.<\/p>\n\n<p>There was no fix for the stable 1.x branch.<\/p>\n\n<p>There was no fix backported to the 1.x branch.<\/p>\n\n<p>There are breaking changes between the 1.x and 2.x branches that require me to update custom code that uses the module, which I don't want to do yet, and I don't want to update to an unstable version.<\/p>\n\n<p>If you maintain open-source software, don't force people to update too quickly.<\/p>\n\n<p>If you can, make it easy for people to update to the next major version by keeping breaking changes to a minimum and providing time and clear instructions for doing so.<\/p>\n\n<p>If these are too difficult, it could discourage or prevent people from using your software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f0b824f4d171e8138cf1c6b8e9bf5604",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.79fdad19-834d-463e-89f6-059c0865a034.json b/content/node.79fdad19-834d-463e-89f6-059c0865a034.json
index 984646153..ff5df5d1e 100644
--- a/content/node.79fdad19-834d-463e-89f6-059c0865a034.json
+++ b/content/node.79fdad19-834d-463e-89f6-059c0865a034.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A great thing about <a href=\"http:\/\/default\/daily\/2023\/01\/03\/tailwind-css-extensibility-is-one-of-its-best-features\">Tailwind CSS plugins<\/a> being written in JavaScript is that they can be tested using tools like Jest.<\/p>\n\n<p>Here's an example from https:\/\/github.com\/opdavies\/tailwindcss-plugin-jest-example (it may need updating to work with the latest Tailwind versions or to use the latest best practices):<\/p>\n\n<pre><code class=\"javascript\">function run(options = {}) {\n  return postcss(\n    tailwindcss({\n      corePlugins: false,\n      plugins: [plugin(options)]\n    })\n  )\n  .process('@tailwind utilities;', {\n    from: undefined\n  })\n}\n\nexpect.extend({\n  toMatchCss: cssMatcher\n})\n\ntest('it generates the correct classes with no variants', () =&gt; {\n  const output = `\n    .test {\n      display: block\n    }\n  `\n\n  run().then(result =&gt; {\n    expect(result.css).toMatchCss(output)\n  })\n})\n\ntest('it generates the correct classes with variants', () =&gt; {\n  const output = `\n    .test {\n      display: block\n    }\n    .hover\\\\:test:hover {\n      display: block\n    }\n    .focus\\\\:test:focus {\n      display: block\n    }\n  `\n\n  run({ variants: ['hover', 'focus'] }).then(result =&gt; {\n    expect(result.css).toMatchCss(output)\n  })\n});\n<\/code><\/pre>\n\n<p>Within the test, Tailwind can be run using PostCSS and generates styles based on a provided configuration, which is then checked against some expected output. If the generated styles match what was expected, the tests pass and the plugin is working as expected.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "66179cf5075396d9979accd64d8ccb0d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json b/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json
index a1bb92473..3475b7396 100644
--- a/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json
+++ b/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I'm aware of when working in a pair or mob is to always listen to input from other team members.<\/p>\n\n<p>A pair or mob session isn't just focused on one person's ideas or solution. It's a collaborative effort based on everyone's input, experience and ideas.<\/p>\n\n<p>If there are conflicting or different ideas or approaches, they can be discussed, and everyone can agree on the way forward. Approaches may also change as you learn more together during the session.<\/p>\n\n<p>Together, you will come up with the best solution - even if it's different from what you had in mind to begin with.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ecc568cf8fbe4c5c917c60aaa6ec3460",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json b/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json
index 486f8536c..fe141eeb5 100644
--- a/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json
+++ b/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as different base classes for types of tests - i.e. functional, kernel and unit - there are other test base classes within those that can be used to simplify things.<\/p>\n\n<p>For example, if we have this test:<\/p>\n\n<pre><code class=\"language-php\">&lt;?php\n\nnamespace Drupal\\Tests\\example\\Kernel;\n\nuse Drupal\\KernelTests\\KernelTestBase;\nuse Drupal\\Tests\\node\\Traits\\NodeCreationTrait;\nuse Drupal\\Tests\\user\\Traits\\UserCreationTrait;\n\nclass ExampleTest extends KernelTestBase {\n\n  use NodeCreationTrait;\n  use UserCreationTrait;\n\n  protected static $modules = [\n    'node',\n    'user',\n  ];\n\n  public function setUp(): void {\n    parent::setUp();\n\n    $this-&gt;installEntitySchema(entity_type_id: 'node');\n    $this-&gt;installEntitySchema(entity_type_id: 'user');\n  }\n\n  public function testExample(): void {\n    $user = $this-&gt;createUser();\n\n    $article = $this-&gt;createNode([\n      'title' =&gt; 'Test article',\n      'uid' =&gt; $user,\n    ]);\n\n    self::assertSame('1', $article-&gt;getOwnerId());\n  }\n\n}\n<\/code><\/pre>\n\n<p>Both creation traits must be imported, the <code>node<\/code> and <code>user<\/code> modules must be enabled, and the entity tables must be installed.<\/p>\n\n<p>When writing a lot of tests, this can result in duplication and more complex tests that take longer to write.<\/p>\n\n<p>This can be simplified using <code>EntityKernelTestBase<\/code> instead of <code>KernelTestBase<\/code>:<\/p>\n\n<pre><code class=\"language-php\">&lt;?php\n\nuse Drupal\\KernelTests\\Core\\Entity\\EntityKernelTestBase;\nuse Drupal\\Tests\\node\\Traits\\NodeCreationTrait;\n\nclass ExampleTest extends EntityKernelTestBase {\n\n  use NodeCreationTrait;\n\n  protected static $modules = [\n    'node',\n  ];\n\n  public function testExample(): void {\n    $user = $this-&gt;createUser();\n\n    $article = $this-&gt;createNode([\n      'title' =&gt; 'Test article',\n      'uid' =&gt; $user,\n    ]);\n\n    self::assertSame('1', $article-&gt;getOwnerId());\n  }\n\n}\n<\/code><\/pre>\n\n<p>The class is simpler, fewer modules must be specified, and the entity schemas are automatically installed.<\/p>\n\n<p>As well as the core modules, some contrib modules also provide their own base test cases.<\/p>\n\n<p>If you're using the Webform module, you may want to use <code>WebformAccessTestBase<\/code> instead of the standard <code>UnitTestCase<\/code>.<\/p>\n\n<p>It's definitely worth spending some time looking at what base test cases are available and which are the best ones to use for your own tests.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "550456dfd70a84795f8c61ba84691a1d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json b/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json
index e0afc289c..41a43b7ac 100644
--- a/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json
+++ b/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal includes a lot of default functionality and additional core modules you can enable to extend it.<\/p>\n\n<p>There are also over 50,000 community-contributed modules you can download and add.<\/p>\n\n<p>But is it worth adding every module?<\/p>\n\n<p>If you're browsing the list of modules on Drupal.org and find one of interest, is the functionality it adds more valuable than the cost of maintaining it?<\/p>\n\n<p>Each module increases the number of updates you'll need to do to maintain the website.<\/p>\n\n<p>What if it becomes unmaintained in the future and prevents you from updating your website to the next version of Drupal or has a security issue and introduces a vulnerability?<\/p>\n\n<p>Some modules will be crucial to your website, others you can do without if you prefer a smaller maintenance overhead.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "39ad9b31772a4824f9e1b5335fbb0b48",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json b/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json
index 7b2940c8f..3b37c7d32 100644
--- a/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json
+++ b/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I added a new feature to a project that allows a member to search for a node based on either its title or a specified field on that node, select a result from an autocomplete list and then be redirected to their selected node.<\/p>\n\n<p>I've already implemented this for other node types but needed to do the same for this node type.<\/p>\n\n<p>There are some differences, such as the node type to query for; the additional field depends on which node type as does the text shown in the autocomplete list.<\/p>\n\n<p>To do this, I needed to add a custom block and form, update the <code>AutocompleteController<\/code>, create a new instance of a <code>NodeQuery<\/code> class (a custom class within the custom module), register it as a service and update the <code>SearchQueryFactory<\/code> class.<\/p>\n\n<p>A principle that I follow as much as possible is the single responsibility principle, or SRP (the 'S' in SOLID), where each function or class only has one responsibility - such as returning a response for the autocomplete list, determining the correct node query to use based on the search being run or building the query itself - these are separated and split into their own files.<\/p>\n\n<p>Although more files and functions are created when coding in this way, though they are smaller and more straightforward to work with - which makes them easier to read, debug and maintain. It also makes code like the node query classes reusable as they aren't embedded within a larger class and are easier to test.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "74bd5f418ef3374adbd56755b08e95bb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json b/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json
index d75ee019d..3b9f48d23 100644
--- a/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json
+++ b/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You wrote some code that was pushed to production, but it contained a bug.<\/p>\n\n<p>Would you rather it be code you wrote hours, days, weeks, or months ago?<\/p>\n\n<p>If you wrote it months ago, you'll have worked on numerous other tasks since then and forgotten all the context and edge cases you had in your mind when you wrote it.<\/p>\n\n<p>Before fixing the bug, you need to remember all that context and information - if possible.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The less time between the code being written and deployed, the more likely you are to remember what you thought when you wrote it.<\/p>\n\n<p>If it were code you wrote today or yesterday, it would be easier and quicker for you to fix it.<\/p>\n\n<p>And, the quicker your release schedule is, the sooner the fix will be deployed to your users, customers or clients.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ed6e2359d50107af3a75d41ec9f33762",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json b/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json
index db8b33772..18eea95e0 100644
--- a/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json
+++ b/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm a big advocate for automation, from having a reproducible Docker and Docker Compose environment, automated tests, static analysis, and code linting in my projects to running them automatically on every push to a remote repository using a CI pipeline.<\/p>\n\n<p>I've written scripts to simplify common complex tasks and automated my local development environment setup before using tools like Ansible and, recently, the Nix package manager, NixOS and Home Manager.<\/p>\n\n<p>Another main piece of automation I use is to create and manage the infrastructure my applications run in.<\/p>\n\n<p>I've talked about it in my <a href=\"http:\/\/default\/talks\/deploying-php-ansible-ansistrano\">Deploying PHP applications with Ansible and Ansistrano talk<\/a>, that before you can deploy an application, you need a server with the required packages installed to run it. You may also need a CDN endpoint, SSL certificate, DNS records, CORS policy, database server, container registry, object storage bucket or a number of various other things.<\/p>\n\n<p>Using automation tools like Terraform, Pulumi or Ansible, you can run a single command to create, update or destroy resources or your entire stack.<\/p>\n\n<p>The automation code acts as living documentation, can be version-controlled, stored alongside the code, and read by the Developers or anyone else involved with the project.<\/p>\n\n<p>If you need to hand over the hosting requirements to a client or create their own version, you can do that with the same automation code.<\/p>\n\n<p>And if a disaster scenario was to happen and you needed to recreate your infrastructure from scratch or move to a different cloud provider, you could do that quickly using automation tools, knowing that the new infrastructure would be consistent with the original, all of the pieces would be in place, and without needing to recreate everything manually from scratch.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "02bc3a05396c873cc0f9bed77cfe2d63",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json b/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json
index 0a8f0e285..6bf52904e 100644
--- a/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json
+++ b/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been working on a project with a client, using <a href=\"https:\/\/fractal.build\">Fractal<\/a> for our component library. I've been working on it locally but yesterday I needed to make it public for the client to review the work I've done.<\/p>\n\n<p>I recently added <code>node<\/code> support to my <a href=\"http:\/\/default\/daily\/2023\/03\/04\/why-i-built-a-tool-to-generate-configuration-files\">build configuration file generator<\/a> and used that to generate and use a consistent set of configuration files for a Fractal project.<\/p>\n\n<p>I've used Terraform in <a href=\"https:\/\/github.com\/opdavies\/rebuilding-acquia\">some codebases<\/a> to create and configure AWS resources like S3 buckets and Cloudfront distributions, so I was able to use that to create what I needed as well as adding the DNS record for a new subdomain to access Cloudfront.<\/p>\n\n<p>I use a <code>justfile<\/code> to automate tasks such as generating production assets from Fractal and uploading it to the S3 bucket, so I can do this in a single command instead of multiple and in a consistent and reproducible way.<\/p>\n\n<p>I started with a standalone project on my laptop and finished with a consistent cloud-based environment for my client and their project to review their component library, and because of the automation that I've built and used, this only took a few minutes to do.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f29346ee784205182d857cb2d30f2d23",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json b/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json
index b1767f382..866e36608 100644
--- a/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json
+++ b/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently sent a database to a client whose new Drupal website I'm building.<\/p>\n\n<p>I'd populated&nbsp;it with some default users, nodes and menu links that they'd be able to review after they import the database into their hosting.<\/p>\n\n<p>That worked well, but I've also recently been using the <a href=\"https:\/\/www.drupal.org\/project\/default_content\">Default Content module<\/a> which exports entities into YAML and saves them as code alongside the configuration.<\/p>\n\n<p>Now I can install the website from scratch using the exported configuration to re-add the content types, block types, etc, and by enabling a custom module, all the default content will also be recreated.<\/p>\n\n<p>I can tear the site down now and rebuild it as often as I like and avoid contaminating&nbsp;my environment with any rogue configuration or content changes.<\/p>\n\n<p>Everything is reproducible.<\/p>\n\n<p>I also wouldn't have needed to send the database to the client. They could have installed Drupal and followed the same steps&nbsp;I would do locally and got exactly the same result.<\/p>\n\n<p>I like this approach and can see me using it more on future projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "47bd091b2e6434c4dab3ae5151f7881c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json b/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json
index 13c42eb0b..d2c6f3275 100644
--- a/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json
+++ b/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as writing and maintaining my open-source software projects, I regularly contribute to other people's - including PHP libraries, Drupal modules and Tailwind CSS plugins.<\/p>\n\n<p>I'm more likely to contribute to your project if you release new versions regularly.<\/p>\n\n<p>Why would I if my changes may sit on a development branch for a long time or not be released at all?<\/p>\n\n<p>If I can see that my changes are likely to be released soon, I'm more likely to spend the time and effort to contribute instead of looking for a different solution.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b1298d5da5638a46cefadc614b1673e6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json b/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json
index 51c78980e..39cbff4cd 100644
--- a/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json
+++ b/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I often hear that code should be \"self-documenting\".<\/p>\n\n<p>Instead of writing a comment, you should create a function or class with that name instead.<\/p>\n\n<p>Whilst I agree with this, I think that code comments shouldn't describe what the code is doing - they should explain why the code is needed and provide any additional context to the person reading it.<\/p>\n\n<p>If a comment just says <code>Returns true<\/code> or <code>Sends an email<\/code>, that can be understood by reading the code, so isn't providing any extra value or context. They can also become outdated as the code changes.<\/p>\n\n<p>If a line of code is needed to fix a certain state or situation, or if a piece of code isn't particularly readable and isn't obvious what it does, those are good times to add comments.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d8831ac5b7ba46ed9c5772cb19a46954",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json b/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json
index 3cc1e3b2a..43a791424 100644
--- a/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json
+++ b/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Does your team really do CI\/CD (continuous integration and delivery)?<\/p>\n\n<p>I recently watched a recording of a talk from another daily emailer, <a href=\"https:\/\/jhall.io\">Jonathan Hall<\/a>, who started by asking the audience to raise their hands and keep them raised if...<\/p>\n\n<ul>\n<li>They did a release to production in the last week.<\/li>\n<li>They did a release to production yesterday.<\/li>\n<li>They do not have a permanent branch called <code>develop<\/code>.<\/li>\n<li>They do not have a special \"hotfix\" procedure.<\/li>\n<li>Every Developer on their team merged work into <code>main<\/code> yesterday.<\/li>\n<li>They have no pull requests more than 24 hours old.<\/li>\n<\/ul>\n\n<h2 id=\"ci%2Fcd-is-about-process\">CI\/CD is about process<\/h2>\n\n<p>This is an excellent way to highlight that CI\/CD is about processes, not technologies.<\/p>\n\n<p>Continuous integration is about how often everyone merges and pushes their changes, and continuous delivery and deployment is how you create releasable software and how long it takes for a change to get into production - not whether or not you use GitHub Actions, GitLab CI, CircleCI or Jenkins.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "157de5e6e946c20d3a97800528ded3fa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json b/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json
index 8b7bee50f..d5f7a1d2d 100644
--- a/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json
+++ b/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In previous emails, <a href=\"http:\/\/default\/daily\/2024\/11\/21\/one-configuration-language-to-rule-them-all\">I've written briefly about Nix<\/a>. Over the next few days, I want to write more about it and explain the different components of the Nix ecosystem and how I use them.<\/p>\n\n<p>Firstly, Nix is a package manager, similar to apt on Ubuntu or homebrew on MacOS.<\/p>\n\n<p>It contains over 100,000 packages that can be installed once you've installed Nix and if you're on a Mac, there's nix-darwin to have it manage macOS settings too.<\/p>\n\n<p>There are two stable releases a year and a rolling \"unstable\" version so you can be as stable or up-to-date as you like, or you can mix and match in the same configuration.<\/p>\n\n<p>It's easy to add custom packages and apply overrides to existing packages.<\/p>\n\n<p>You can have multiple versions of the same package installed at once.<\/p>\n\n<p>And <a href=\"http:\/\/default\/daily\/2024\/11\/12\/why-consistency-and-reproducibility-are-important\">because Nix is reproducible<\/a>, you can get exactly the same configuration over and over again.<\/p>\n\n<p>In another email, I'll write about NixOS, but you don't need to use it to use Nix the package manager.<\/p>\n\n<p>I used a different Linux distribution when I started using Nix and installed it as a secondary package manager.<\/p>\n\n<p>If you're looking for an alternative package manager for Linux or macOS, I recommend giving Nix a try.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5be7c33a9387a20f7181ac5805318554",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json b/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json
index b5a07dd8f..0d5d1baca 100644
--- a/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json
+++ b/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I started to learn about automated testing in 2012 when I took over maintainership of the Drupal module, Override Node Options.<\/p>\n\n<p>At the time, it had around 9,000 active installations (now more than 35,000), and I was concerned about breaking those sites if I pushed a bug and wanted confidence to make changes without introducing regressions.<\/p>\n\n<p>Later, I started to learn about test-driven development and how to develop and design software by writing the tests first.<\/p>\n\n<p>Although I'm not a Laravel Developer, Adam Wathan's \"Test Driven Laravel\" course was a great resource and information, as well as a number of presentations and talks at PHP meetups and conferences.<\/p>\n\n<p>Once I understood how to write tests and do TDD, I took any opportunity to practice it, whether on projects or coding katas.<\/p>\n\n<p>At one point, I was writing module code during work hours and writing tests for it during the evening.<\/p>\n\n<h2 id=\"what-about-you%3F\">What about you?<\/h2>\n\n<p>How did you learn automated testing or test-driven development? Reply to this email and let me know.<\/p>\n\n<p>Bonus points if it was at one of my conference talks or workshops!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e96f6c60d2ba5103f1f830ef50fc6fb2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json b/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json
index b680641d2..ce3f70233 100644
--- a/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json
+++ b/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A great thing about committing often is that you leave a trail of breadcrumbs for yourself, and you can easily find your way back.<\/p>\n\n<p>If you are trying to get a test to pass or fix a bug and you get a bit lost, you can see what you've changed since your last commit instead of everything since you started working on your task.<\/p>\n\n<p>If needed, you can discard your changes and reset to your last working commit to try again, similar to using the \"test and commit or revert\" approach.<\/p>\n\n<p>If I commit too often, I can squash them before pushing.<\/p>\n\n<p>If I don't commit often enough, I can regret not committing more regularly if I get stuck or lost.<\/p>\n\n<p>I'd rather do the former.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "44157cba9274734c7d7c0029601ad594",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7fce2f3b-7564-40a0-8dfc-741c66a3b993.json b/content/node.7fce2f3b-7564-40a0-8dfc-741c66a3b993.json
index 0460f0a13..c468e2416 100644
--- a/content/node.7fce2f3b-7564-40a0-8dfc-741c66a3b993.json
+++ b/content/node.7fce2f3b-7564-40a0-8dfc-741c66a3b993.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tomorrow night, I'm attending one of Simon Vrachliotis (simonswiss)'s Pro Tailwind workshops, so I thought that it would be a good time, as Simon has done himself recently on the Navbar podcast, to describe how I started using Tailwind CSS.<\/p>\n\n<p>I remember watching a lot of Adam Wathan's live streams on YouTube before Tailwind CSS, and I remember when he started a new project - a SaaS product called KiteTail.<\/p>\n\n<p>It was a Laravel and Vue.js project, and although I'm not a Laravel Developer primarily, I got a lot of other information from Adam's streams about automated testing, test-driven development, and Vue.js as I was learning Vue at the time.<\/p>\n\n<p>One of the episodes was about styling a card component using some styles that Adam was copying between projects - which would eventually be the starting point for Tailwind CSS.<\/p>\n\n<p>In fact, I think I watched some of the episode and stopped as I was happy with the Sass and BEM or SMACSS approach that I was using at the time, and didn't initially see the value of the utility CSS approach that I was seeing for the first time (everyone has a similar reaction initially).<\/p>\n\n<p>After a while, I did re-visit it but because Tailwind CSS wasn't released as it's own project yet, I (like Simon) started to experiment with Tachyons - another utility CSS library.<\/p>\n\n<p>I rebuilt a particularly tricky component that I'd just finished working on and had caused me some issues, and managed to re-do it in only a few minutes.<\/p>\n\n<p>I started to use Tachyons on some personal and client projects as a layer on other frameworks like Bootstrap and Bulma, and later moved on to Tailwind CSS once it has been released.<\/p>\n\n<p>I was working in this way on a project when I released that I could use Tailwind for all of the styling instead of just adding small sprinklings of utilities here and there. I refactored everything and removed the other framework that I'd been using - leaving just Tailwind CSS.<\/p>\n\n<p>With the exception of some legacy projects, now I use Tailwind CSS exclusively and have used it for a number of projects. I've given lunch and learn sessions to teams that I've worked on, <a href=\"http:\/\/default\/presentations\/taking-flight-tailwind-css\">presented a Tailwind CSS talk<\/a> at a number of PHP, Drupal, WordPress, and JavaScript events, and maintain <a href=\"https:\/\/www.drupal.org\/project\/tailwindcss\">a starter-kit theme<\/a> for using Tailwind in custom Drupal themes.<\/p>\n\n<p>I've also rebuilt a <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">number of existing sites<\/a> as examples and written some <a href=\"http:\/\/default\/blog\/tags\/tailwind-css\">Tailwind CSS related blog posts<\/a>.<\/p>\n\n<p>I'm looking forward to attending Simon's workshop tomorrow and quickly putting that knowledge to use in the next phase of a project that I'm currently working on.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "94469e62075ac965bc1432cadee4e2eb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.7fe749a2-90b7-4d22-9dff-56eaa7adb3d5.json b/content/node.7fe749a2-90b7-4d22-9dff-56eaa7adb3d5.json
index 4b78072ce..89a053b3f 100644
--- a/content/node.7fe749a2-90b7-4d22-9dff-56eaa7adb3d5.json
+++ b/content/node.7fe749a2-90b7-4d22-9dff-56eaa7adb3d5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A lot of tutorials show using <code>git commit -m<\/code> to create commits using an inline message.<\/p>\n\n<p>I don't do that, though.<\/p>\n\n<p>Using the <code>-m<\/code> option to specify an inline commit message encourages writing short one-line commit messages instead of using the subject and body effectively to document more about the change, such as why it was needed, any other approaches taken and the consequences of the change within the commit.<\/p>\n\n<p>Alternatively, people could write a longer commit message in one line and not follow the 50 character limit for the subject line.<\/p>\n\n<p>Whilst it's possible to write multi-line commits on the command-line, I use my editor (Neovim) to write my commit messages.<\/p>\n\n<p>I can write as much information as I need, I have coloured columns for the 50 character subject limit and the 72 characters for wrapping the body message and, if I write more than that, it will either wrap for me, or I can format the message for it to be compliant.<\/p>\n\n<p>These are rules that aren't also enforced in some Git tools, so I prefer knowing my setup is configured correctly.<\/p>\n\n<p>Though, whether you use <code>-m<\/code> or not, capture as much information in the message as you can, as future Developers on the project (including you) will thank you for it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "413c39dc33012102e00c123c13251c85",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json b/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json
index 6cfddc71f..78c7ca506 100644
--- a/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json
+++ b/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently been working with a client to kickstart the front-end development on their Drupal upgrade project from Drupal 7 to 10.<\/p>\n\n<p>They've been working hard on the back-end code and migrations, but hadn't done anything on the front-end yet.<\/p>\n\n<p>I was asked to come in and set up a new theme for them and provide some training to get them going.<\/p>\n\n<p>A requirement they mentioned was to make it themable, so they could later change colours of buttons and other elements based on the page type being viewed or if they added sub-sites in the future.<\/p>\n\n<p>This is something I've done a lot with Tailwind CSS and, as it's <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">the CSS framework I'm most familiar with<\/a>, we decided to go with Tailwind CSS - and specifically the alpha version of Tailwind CSS v4.<\/p>\n\n<p>Although it's still in an alpha phase, I've been experimenting with Tailwind v4 in personal projects and on some live streams and it seemed stable enough to use in production.<\/p>\n\n<p>It also makes theming a lot easier as it uses CSS variables everywhere, which made it a no-brainer for this project.<\/p>\n\n<p>Aside from the new features, the setup for Tailwind CSS is so easy and straight forward.<\/p>\n\n<p>There's no JavaScript configuration file and everything is done in a CSS file, making it simpler to set up and more consistent if you need to write CSS anyway to add custom fonts or work with CSS variables - these are no longer in separate places and are now combined in one stylesheet.<\/p>\n\n<p>All the colour configuration and adding plugins is done in the CSS file and Tailwind will find the content files to scan automatically so you no longer need to declare where your template files are - it just knows.<\/p>\n\n<p>It's worked well for this project, and I'll look forward to using Tailwind v4 more on YouTube and for personal and client projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "06fce1aaa4c20b2a830e2a22ab305a5e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json b/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json
index 2550d542e..7ac4ad311 100644
--- a/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json
+++ b/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In PHPUnit, there are different ways to write test methods.<\/p>\n\n<p>The standard way is to use camel-case method names with a <code>test<\/code> prefix, for example:<\/p>\n\n<pre><code class=\"language-php\">public function testTheProjectNameShouldBeAString(): void\n{\n    \/\/ ...\n}\n<\/code><\/pre>\n\n<p>Another popular way, particularly in some frameworks, is to use snake-case method names:<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\npublic function the_project_name_should_be_a_string(): void\n{\n    \/\/ ...\n}\n<\/code><\/pre>\n\n<p>This may be more readable but only works if the <code>@test<\/code> annotation is present.<\/p>\n\n<p>What if you need to add another annotation, such as <code>@dataProvider<\/code> to the test? Do you do multi-line docblocks everywhere, or mix and match single and multiple line docblocks depending on the test?<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>My preference switches between both ways of writing test methods.<\/p>\n\n<p>But, whichever way I write it, I write descriptive method names that explain what the test does - even if it means having a long method name.<\/p>\n\n<p>I avoid short and generic names like <code>testUpdate()<\/code>.<\/p>\n\n<p>People should be able to read the test name and understand what it does and what it's testing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "05bef1d24f084368e652eb41e2831725",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json b/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json
index 643de7486..09a8c0d7d 100644
--- a/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json
+++ b/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I previously wrote about why you shouldn't use variable names like <code>$x<\/code> and <code>$y<\/code> in your code and why you should use more descriptive names.<\/p>\n\n<p>But what if there is an existing convention?<\/p>\n\n<p>For example, I use Lua to configure Neovim and noticed that it's common to use shortened variable names, such as <code>buffer<\/code> instead of <code>buffer_number<\/code> or <code>bufferNumber<\/code>.<\/p>\n\n<p>It's also common to use the variable <code>M<\/code> to declare a module. For example:<\/p>\n\n<pre><code class=\"language-lua\">local M = {}\nM.find_files = function()\n  \/\/ ...\nend\n\nreturn M\n<\/code><\/pre>\n\n<p>Whilst <code>Module<\/code> would be a more descriptive name, would deviating from the convention be more confusing for anyone reading the code?<\/p>\n\n<p>Do the benefits of following a convention outweigh the benefits of using more descriptive variable and function names?<\/p>\n\n<p>Which would be easier for newcomers to your project or team to understand and allow them to be productive sooner?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "517f057d243494aec133607af3972ad8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json b/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json
index d7a085e24..ff4ee19e4 100644
--- a/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json
+++ b/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json
@@ -87,6 +87,5 @@
             "processed": "<p>Following my daily email archive, I've recently switched the podcast pages on my website from Sculpin to Drupal\/Tome.<\/p><p>The <a href=\"http:\/\/default\/podcast\/28-using-ai-tools-web-coding\">recent episode with Luke McCormick<\/a> was the first to be created in Drupal and served from static HTML generated by Tome, and I've since re-created the other podcast episodes and <a href=\"http:\/\/default\/podcast\">the podcast landing page<\/a>.<\/p><p>The next steps are to re-add the links on a podcast episode page to other episodes with the same guests, and to rebuild the podcast feed that's used to update players like Spotify and PocketCasts.<\/p><p>Once I've finished this, I'll move on to <a href=\"http:\/\/default\/presentations\">my presentations pages<\/a> as those are the ones that change next frequently.<\/p><h2>How am I doing this?<\/h2><p>A lot of the content is still served from HTML generated by Sculpin, which is stored in one directory on my server.<\/p><p>The newer content, generated by Tome, is stored in another directory.<\/p><p>In my Nginx configuration, I change the <code>root<\/code> value based on the URL, so depending on which page you're visiting, you'll get content from Sculpin or Tome.<\/p><p>Here's part of that configuration:<\/p><pre><code class=\"language-plaintext\">server {\n  listen localhost:8095:\n  server_name www.oliverdavies.uk:\n  root \/var\/www\/vhosts\/website-sculpin;\n\n  location \/ {\n    try_files $uri $uri.html $uri\/index.html =404;\n  }\n\n  location ~ ^\/archive {\n    try_files $uri $uri.html $uri\/index.html =404;\n    root \/var\/www\/vhosts\/website-tome;\n  }\n\n  location ~ ^\/core {\n    try_files $uri $uri.html $uri\/index.html =404;\n    root \/var\/www\/vhosts\/website-tome;\n  }\n\n  location ~ ^\/daily\/.+ {\n    try_files $uri $uri.html $uri\/index.html =404;\n    root \/var\/www\/vhosts\/website-tome;\n  }\n\n  location ~ ^\/homelab {\n    try_files $uri $uri.html $uri\/index.html =404;\n    root \/var\/www\/vhosts\/website-tome;\n  }\n\n  location ~ ^\/podcast {\n    try_files $uri $uri.html $uri\/index.html =404;\n    root \/var\/www\/vhosts\/website-tome;\n  }\n\n  location ~ ^\/sites\/default\/files {\n    try_files $uri $uri.html $uri\/index.html =404;\n    root \/var\/www\/vhosts\/website-tome;\n  }\n\n  location ~ ^\/themes\/custom\/opdavies {\n    try_files $uri $uri.html $uri\/index.html =404;\n    root \/var\/www\/vhosts\/website-tome;\n  }\n}<\/code><\/pre><p>This is the same approach as <a href=\"http:\/\/default\/daily\/2025\/04\/17\/incrementally\">upgrading incrementally<\/a> from old versions of software to new versions or different software.<\/p><p>Neither site knows about the other and they work independently.<\/p><p>My Nginx configuration is managed within <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/nix-config\/src\/commit\/a994777ba631cf95a16e2bb8f71e344a50bc11f3\/hosts\/nixedo\/modules\/nginx\/www.oliverdavies.uk\/default.nix#L11-L39\">my NixOS configuration<\/a>, so you can see the whole configuration for my website and how I've leveraged the Nix language to simplify the process of migrating new paths to Tome.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json b/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json
index e61b3e777..cc2cbc548 100644
--- a/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json
+++ b/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I rediscovered my hardware knowledge and fixed my son's laptop - a Lenovo ThinkPad X390.<\/p>\n\n<p>Some keys weren't working when pressed, only to have the characters appear a few seconds later.<\/p>\n\n<p>Fun fact: I started my career refurbishing and repairing laptop computers.<\/p>\n\n<p>My first job was for a local laptop company that refurbished ex-business laptops for resale, followed by working for Panasonic where I'd repair laptops from blue chip clients across Europe.<\/p>\n\n<p>I used to build custom PCs, but have done little to no hardware work since I started in software development in 2010.<\/p>\n\n<p>Today, though, I took the laptop apart and after checking the motherboard and keyboard were OK, I reseated the keyboard and cleaned any dust from inside the casing.<\/p>\n\n<p>It worked!<\/p>\n\n<p>If I'd have returned it to a manufacturer or taken it to a local computer repair shop, I'd have had to pay for them to diagnose and (hopefully) resolve the issue.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Most laptops and phones today are sealed units and not as modular, repairable or upgradable as the devices I used to work on.<\/p>\n\n<p>In some cases, you can't upgrade or repair them yourself.<\/p>\n\n<p>Similar to <a href=\"http:\/\/default\/daily\/2024\/12\/13\/gitea\">having control and ownership of my own data<\/a>, I like the ability to repair a keyboard myself or to add more memory or storage to my laptop.<\/p>\n\n<p>As well as installing and running my own software, <a href=\"http:\/\/default\/daily\/2024\/12\/01\/homelabbing-with-nixos\">starting a homelab<\/a> has also reignited my interest in hardware and being able to upgrade and repair my own devices.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7935da166360b58eee6cda5b341491bc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json b/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json
index 9143adbc2..703b7cde9 100644
--- a/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json
+++ b/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something interesting that <a href=\"https:\/\/www.daveliddament.co.uk\">Dave Liddament<\/a> and I discussed was the use of value objects in application code.<\/p>\n\n<p>Instead of using a primitive type, such as <code>string<\/code>, you can create a new value object for a specific type of string, such as an <code>EmailAddress<\/code> or, in my side project, a <code>LicenceKey<\/code>.<\/p>\n\n<p>Both are strings, but using value objects of specific types can make the code more readable and its intent clearer.<\/p>\n\n<p>A value object can contain additional logic, such as validation to execute an ensure the value object is valid, such as making sure a string is not empty, is a specific length or only contains valid characters.<\/p>\n\n<p>This an approach that I'm going to use more going forward.<\/p>\n\n<p>I also found <a href=\"https:\/\/www.youtube.com\/watch?v=yJpvObzKewY\">a lighting talk by Dave<\/a> at a PHPSW meetup where he explains this further and, of course, you can listen to the podcast episode after it's been released.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "60b18ba23e94d04d883b816e371d3836",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json b/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json
index 0454b98e5..0b0977605 100644
--- a/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json
+++ b/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something that I hear often is \"self-documenting code\", and that code should be easy to understand without comments.<\/p>\n\n<p>If you need to write a comment explaining what something does, move the code into a new class or function and have its name describe what it does.<\/p>\n\n<p>I agree with this, but I still think there is a place for comments within the code as long as they add value.<\/p>\n\n<h2 id=\"what-comments-shouldn%27t-be\">What comments shouldn't be<\/h2>\n\n<p>Comments shouldn't just repeat what the code says.<\/p>\n\n<p>If the comment says \"Returns false\", and I can read that from the code, the comment isn't adding any value.<\/p>\n\n<p>I use types a lot in PHP and TypeScript, and if docblocks are just repeating the native types, I'd rather not include them and keep the code minimal.<\/p>\n\n<p>Comments like \"Constructor\" and \"This shouldn't happen\" add no context.<\/p>\n\n<h2 id=\"what-comments-should-be\">What comments should be<\/h2>\n\n<p>Comments need to add value by adding extra information or explaining why the code does what it does.<\/p>\n\n<p>I will add comments like \"This class decorates ... so that ...\" and \"This returns ... if ...\". These comments add value and make the code easier to read and understand. The downside is that you then need to maintain the comments, make sure they remain correct, and if the functionality changes the comment is also changed.<\/p>\n\n<p>If a static analysis tool requires me to provide more information in a docblock that describes some parameters or a return type, I'll do that. It makes the code quality better, reduces bugs, and makes the Developer experience better. As I'm improving the native types by providing more information, I'm not just repeating them so this is OK with me.<\/p>\n\n<p>Comments should make the code easier to read, understand, and work with for yourself and other team members.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2527d9b10a1752a2435693a747d98027",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json b/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json
index eaa699ce2..8963794ef 100644
--- a/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json
+++ b/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday's email was about the LocalGov Drupal distribution that I've been looking at, but I glossed over what a Drupal distribution is.<\/p>\n\n<p>It's an interesting topic for me, having <a href=\"https:\/\/www.linuxjournal.com\/content\/speed-your-drupal-development-using-installations-and-distributions\">written an article for Linux Journal<\/a> about it in 2012.<\/p>\n\n<p>Distributions are pre-configured versions of Drupal that include additional modules, themes, or configuration than you'd get if you installed a standard version of Drupal core.<\/p>\n\n<p>By default, LocalGov includes content types for service pages, service landing pages and sub-pages, and additional menus and taxonomies, a different administration theme and a base theme to use for custom themes, and multiple additional modules that add alert banners, events, content reviews, search, media types, and sub-sites. This is all in addition to what Drupal core itself provides, and can be extended further with additional contrib or custom modules.<\/p>\n\n<p>Commerce Kickstart was a distribution for Drupal 7 that added eCommerce functionality such as product and order types, shipping and payment methods, stock levels and discounts. Again, this could be extended further by adding more contrib or custom modules.<\/p>\n\n<p>A few months ago, I started developing a distribution for managing meetup group websites, like PHP South Wales.<\/p>\n\n<p>If you're starting a new Drupal website, there could be a distribution that exists that could provide some or all of the functionality that you need, and if new features or fixes are added, then they benefit everyone who uses it.<\/p>\n\n<p>There are 1,430 distributions listed on https:\/\/www.drupal.org\/project\/project_distribution so take a look there and see if anything matches your needs.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0a69c3b2809135b0b34a0adb490b0aba",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json b/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json
index 1bc13bb75..fe65feb26 100644
--- a/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json
+++ b/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When learning to code, one of the most confusing things was using short variable names in documentation and other people's code.<\/p>\n\n<p>Things like <code>$k<\/code> and <code>$v<\/code> instead of <code>$key<\/code> and <code>$value<\/code> within loops, <code>$i<\/code> instead of <code>$index<\/code>, or <code>$e<\/code> when working with Exceptions.<\/p>\n\n<p>I've also seen slightly better names, such as <code>$idx<\/code> for index or <code>$ctx<\/code> for context.<\/p>\n\n<p>But what does this achieve?<\/p>\n\n<p>Why not write the full variable name and clarify what it refers to?<\/p>\n\n<p>It would be easier to read and understand for anyone reading the code, including Junior Developers and people new to your team or application.<\/p>\n\n<p>There are no limitations - at least in the languages I use - to force this, such as a maximum number of characters in a file, so why not write the full variable name?<\/p>\n\n<p>The only reason I can think of is to save time by pressing fewer keys, but code is read more than written, so it should be optimised for readability.<\/p>\n\n<p>Your tests and CI pipeline don't have a preference.<\/p>\n\n<p>The people reading the code will.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cfa95fab36c01cd4b2f5e179c30c8d76",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json b/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json
index 7b2f296fb..737c58409 100644
--- a/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json
+++ b/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Ansible is a tool for automating IT tasks. It's one of my preferred tools to use, and one that I've written about and <a href=\"http:\/\/default\/talks\/deploying-php-ansible-ansistrano\">presented talks on<\/a> previously.<\/p>\n\n<p>It's typically thought of as a tool for managing configuration on servers. For example. you have a new VPS that you want to use as a web server, so it needs Nginx, MySQL, PHP, etc to be installed - or whatever your application uses. You define the desired state and run Ansible, which will perform whatever tasks are needed to get to that state.<\/p>\n\n<p>Ansible though does include modules for interacting with services like Amazon AWS and DigitalOcean to create the servers and resources, and not just configure them.<\/p>\n\n<p>It also doesn't just work on servers. I use Ansible to configure my local development environment, to ensure that dependencies and tools are installed, and requirements like my SSH keys and configuration are present and correct.<\/p>\n\n<p>Lastly, I use Ansible to deploy application code onto servers and automatically run any required steps, ensuring that deployments are simple, robust and repeatable.<\/p>\n\n<p>In the next few emails, I'll explain how I've been able to utilise Ansible for each of these situations.<\/p>\n\n<hr>\n\n<p>Want to learn more about how I use Ansible? <a href=\"http:\/\/default\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c777affc63c0cf359d64d0b1d6b7a2b7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json b/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json
index 88313eef3..5fefe48a2 100644
--- a/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json
+++ b/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since <a href=\"http:\/\/default\/daily\/2025\/01\/13\/patches\">patching ThePrimeagen's tmux-sessionizer script<\/a>, I've started to think of more situations where patching would be useful.<\/p>\n\n<p>I've been using Nick Janetakis' notes script for creating and managing notes files and wanted it to generate daily files instead of monthly, which it did in a previous version.<\/p>\n\n<p>Rather than locking myself to using an older version, <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/dotfiles\/commit\/3e9a27874a8110f5e6af2afff3de6efbc5b71e8f\">I patched the script<\/a> to include my changes and create the files with the names I want.<\/p>\n\n<p>If Nick releases a new version, I'll get the updates and I'll keep my changes as the patch is applied automatically by Nix.<\/p>\n\n<p>As I mentioned before, the suckless.org projects follow this approach and expect users to create and apply patches to their software to configure and customise them.<\/p>\n\n<p>As someone who creates and maintains open source software, and develops applications with open source projects like Drupal, knowing how to use patches to fix and extend them can be very useful in some situations.<\/p>\n\n<p>P.S. If you want to hear a conversation between Nick and myself about Docker, course creation and more, listen to the <a href=\"http:\/\/default\/podcast\/12-nick-janetakis-docker\">episode with Nick on the Beyond Blocks podcast<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "15848211557ccf2961d0bab3eb078103",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json b/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json
index 791ca4676..d4d95a8da 100644
--- a/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json
+++ b/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I enjoy writing and working with open-source software, starting back to when I started working with PHP and Drupal in 2007.<\/p>\n\n<p>Since then, I've written and maintained a number of Drupal modules and themes, PHP libraries, npm packages, Ansible roles and Docker images - all of which are available on my GitHub and Drupal.org pages.<\/p>\n\n<p>Just over a year ago, <a href=\"http:\/\/default\/blog\/going-full-vim\">I switched to using Neovim full-time<\/a> for my development and DevOps work, and last week, I wrote my first Neovim plugin, written in Lua.<\/p>\n\n<p>I've used Lua to configure Neovim but this is the first time that I've written and open-sourced a standalone Neovim plugin.<\/p>\n\n<p>It's called <a href=\"https:\/\/github.com\/opdavies\/toggle-checkbox.nvim\">toggle-checkbox.nvim<\/a> and is used toggle checkboxes in Markdown files - something that I use frequently for to-do lists.<\/p>\n\n<p>For example, this a simple list containing both checked and unchecked checkboxes:<\/p>\n\n<pre><code class=\"markdown\">-   [x] A completed task\n-   [ ] An incomplete task\n<\/code><\/pre>\n\n<p>To toggle a checkbox, the <code>x<\/code> character needs to be either added or removed, depending on whether we're checking or unchecking it.<\/p>\n\n<p>This is done by calling the <code>toggle()<\/code> function within the plugin.<\/p>\n\n<p>In my Neovim configuration, I've added a keymap to do this:<\/p>\n\n<pre><code class=\"lua\">vim.keymap.set(\n  \"n\",\n  \"&lt;leader&gt;tt\",\n  \"require('toggle-checkbox').toggle()\"\n)\n<\/code><\/pre>\n\n<p>This means that I can use the same keymap by running <code>&lt;leader&gt;tt<\/code> to check or uncheck a checkbox. I could use Vim's replace mode to do this, but I really wanted to have one keymap that I could use for both.<\/p>\n\n<p>As it's my first Neovim plugin, I decided to keep it simple.<\/p>\n\n<p>The main <code>toggle-checkbox.lua<\/code> file is currently only 41 lines of code, and whilst there is an existing Vim plugin that I could have used, I was excited to write my own plugin for Neovim, to start contributing to the Neovim ecosystem, and add a Neovim plugin to my portfolio of open-source projects.<\/p>\n\n<p>You can view the plugin at <a href=\"https:\/\/github.com\/opdavies\/toggle-checkbox.nvim\">https:\/\/github.com\/opdavies\/toggle-checkbox.nvim<\/a>, as well as my Neovim configuration (which is also written in Lua) as part of <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/tree\/main\/roles\/neovim\/files\">my Dotfiles repository<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "da50f1968f98fdd321596a74d98b2ec4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json b/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json
index a141ae555..9293cd4b6 100644
--- a/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json
+++ b/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I spoke with <a href=\"https:\/\/mark.ie\">Mark Conroy<\/a> for an upcoming episode of the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a>.<\/p>\n\n<p>We discussed his approach to removing front-end build tools from projects, including the LocalGov Drupal base theme.<\/p>\n\n<p>Doing this removes dependencies such as Sass and tools like Webpack but also makes it easier for others to contribute as there's less to learn.<\/p>\n\n<p>The barrier to entry is lower.<\/p>\n\n<p>This is a big advantage in the open-source space and for companies and project teams.<\/p>\n\n<p>Having simpler code and fewer tools makes it easier for others to understand and work on your codebase, making them productive sooner.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "680c0fd0f51522dacede739c63e5cc66",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json b/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json
index c45c86835..0f42a14a1 100644
--- a/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json
+++ b/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/build-configs\">Build Configs<\/a> is a tool I wrote and recently <a href=\"http:\/\/default\/presentations\/building-build-configs\">gave a lightning talk about<\/a> at the PHP South West meetup in Bristol, UK.<\/p>\n\n<p>It's a command-line tool that creates customised per-project configuration files from a set of reusable templates.<\/p>\n\n<p>It's a Symfony project using components such as Console, Validator, and Twig for templating.<\/p>\n\n<p>But why did I build it?<\/p>\n\n<h2 id=\"what-was-i-doing-before%3F\">What was I doing before?<\/h2>\n\n<p>When starting a new project, I'd copy configuration files from an existing project and alter them as needed.<\/p>\n\n<p>If a project uses a <code>docroot<\/code> directory instead of <code>web<\/code>, a different version of PHP, or Caddy instead of Nginx, I'd need to change the files manually for the new project, add any required features, or fix any bugs.<\/p>\n\n<h2 id=\"what-was-the-issue-with-this%3F\">What was the issue with this?<\/h2>\n\n<p>It took time to set up new projects, and there would be drift between them.<\/p>\n\n<p>I may have added a feature to one project, but it wouldn't exist in the one I was working on.<\/p>\n\n<p>If I needed to move a feature from one project to another, I needed to do it manually.<\/p>\n\n<h2 id=\"how-does-build-configs-solve-the-issue%3F\">How does Build Configs solve the issue?<\/h2>\n\n<p>Now, I have a canonical set of template files.<\/p>\n\n<p>Instead of making ad-hoc changes to each project, I can add new features and fix bugs in the templates, and re-generate the configuration files for each project.<\/p>\n\n<p>I don't need to worry about drift between projects because they're all in sync and generated automatically.<\/p>\n\n<p>It's quicker to create and onboard projects using existing configurations instead of copying files and making manual changes.<\/p>\n\n<p>If you want to see an example, <a href=\"https:\/\/www.youtube.com\/watch?v=LkhsdmxReUc\">watch this video<\/a> where I set up a new Drupal 10 project from nothing to running website in less than a minute.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1ee4600295e86488919b3420dfa02534",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json b/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json
index 4e3ded332..c1f4cb96c 100644
--- a/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json
+++ b/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Regardless of <a href=\"http:\/\/default\/daily\/2024\/12\/23\/how-many-environments-do-you-need\">how many environments your application has<\/a>, you need to be able to move changes between them reliably.<\/p>\n\n<p>You don't want to configure each environment and make every change by hand.<\/p>\n\n<p>You want to automate this as much as possible so your changes are the same every time.<\/p>\n\n<p>In Drupal 7, the Features module was used to export changes once and apply them again using a <code>features revert<\/code> command - although its original use case was to extract reusable features for different applications.<\/p>\n\n<p>I've also written a lot of update of update hooks, like <code>mymodule_update_8001<\/code> to apply changes when database updates are applied.<\/p>\n\n<p>Since Drupal 8, we've had configuration management - a first-class way to export and import configuration changes - which I think was one of the best additions to Drupal 8, and something not available in some other CMSes, frameworks and applications.<\/p>\n\n<p>There's an ecosystem around configuration management, including Config Split for per-environment configurations and Config Ignore to ignore sensitive information or changes you don't want to manage via imported configuration.<\/p>\n\n<p>I recently worked on a project where we didn't have a CI pipeline running configuration imports on each change and things were very difficult to manage. Once that was in place, though, things were much easier, more consistent and changes were quicker to release.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "edb67464b9188fe49c1cef46dfa04ac8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json b/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json
index e8527c4c4..9ba606c1f 100644
--- a/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json
+++ b/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, Solomon Hykes (@solomonstre on Twitter) said:<\/p>\n\n<blockquote>\n  <p>Your CI\/CD pipeline should start on the developer's laptop. If it only starts after a git push, you're slowing your team down and throwing money down the drain.<\/p>\n<\/blockquote>\n\n<h2 id=\"what-does-this-mean%3F\">What does this mean?<\/h2>\n\n<p>My interpretation of this is that if a pipeline is going to fail, and fail for something that could been easily tested locally, then it should have been tested and fixed locally rather than waiting to push the changes to a CI pipeline, watch it fail there, and then need to push a fix and go through the process again.<\/p>\n\n<p>In PHP projects, a common CI pipeline failure after working on a change is that PHPCS (code style) or PHPStan (static analysis) checks will fail - even though the feature, fix or refactor is working. If those checks can be run locally to shorten the feedback loop and allow the error to be fixed before the pipeline runs, it would be better to do so.<\/p>\n\n<h2 id=\"my-preferred-solution\">My preferred solution<\/h2>\n\n<p>My approach for this is using Git hooks - specifically on a pre-push event.<\/p>\n\n<p>These are scripts that run automatically before the commits are pushed, and if it fails, it prevents the push and allows you to fix the issue.<\/p>\n\n<p>They're easy to enable using a command like <code>git config core.hooksPath .githooks<\/code> (assuming the scripts are in a directory called <code>.githooks<\/code>), and whilst I wouldn't run everything that I would in a CI pipeline, I would run tasks like PHPCS and PHPStan checks, and maybe the unit and integration tests if they're fast to run.<\/p>\n\n<p>Anything that would take a longer time to run, like functional or behavioural tests, would only be executed within the pipeline, but for common failures like PHPCS and PHPStan errors, these can be quickly fixed locally and not pushed to a CI pipeline at all.<\/p>\n\n<p><a href=\"https:\/\/twitter.com\/solomonstre\/status\/1649118014594502656\">Here is Solomon's original tweet<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ad8edfa32b635972a3fba18023827d89",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json b/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json
index 770505f03..911506cea 100644
--- a/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json
+++ b/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A while ago, I started to build <a href=\"https:\/\/bootstrap-with-tailwind.oliverdavies.uk\">some of Bootstrap's example components<\/a> with Tailwind CSS.<\/p>\n\n<p>Because it's a lower-level framework with less-opinionated classes, you can use Tailwind classes to make different looking UIs.<\/p>\n\n<p>There is no \"Tailwind-looking website\" as there is with component-level frameworks like Bootstrap and Bulma.<\/p>\n\n<p>You can also see this in the <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">other UIs I've rebuilt with Tailwind<\/a> - some of which I show in my <a href=\"http:\/\/default\/presentations\/sculpin\">Taking Flight with Tailwind CSS talk<\/a>.<\/p>\n\n<p>I've created the Album and Pricing card examples so far, but may do more soon.<\/p>\n\n<p>I've recently ported this website to be <a href=\"http:\/\/default\/presentations\/sculpin\">a Sculpin-powered website<\/a>, so if you want to see another Sculpin example, you can take a look <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/bootstrap-with-tailwind\">at the source code<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ba45cf6bd571c26a3efb9057e7bc5fd3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json b/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json
index ef6709a2e..ad9d20338 100644
--- a/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json
+++ b/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I saw that my Drupal.org profile is showing that I\u2019ve been on that website for 14 years.<\/p>\n\n<p><img src=\"https:\/\/www.oliverdavies.uk\/assets\/images\/14-drupalorg.jpg\" alt=\"A screenshot of my Drupal.org profile showing &quot;On Drupal.org for 14 years 1 hour&quot;.\"><\/p>\n\n<p>Drupal.org is the online home of the open-source Drupal CMS project, and where I registered to ask questions on the forums as I started to learn Drupal. More recently, it\u2019s been where I\u2019ve uploaded and maintain my own contributed projects and contribute patches to others, including Drupal core.<\/p>\n\n<p>I even spent time working for the Drupal Association on Drupal.org itself.<\/p>\n\n<p>I've talked about T-shaped Developers in a previous email, and whilst I've added complementary skills to my toolkit over the years, Drupal has been my main specialism and what I focused on when I started freelancing and later switched careers into software development.<\/p>\n\n<p>With Drupal 10 just around the corner, I'm looking forward to seeing how Drupal continues to evolve and develop.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1777ed82a3c678a09b17f1c159f7b5cd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json b/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json
index 92199e58a..809213840 100644
--- a/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json
+++ b/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as test-driven development (TDD), I also like README-driven development - a.k.a. documentation-driven development.<\/p>\n\n<p>In short, you write the documentation first, followed by the code.<\/p>\n\n<p>Like writing tests in TDD, it allows you to think about how your code will work, what functions and methods it will contain, how they'll interact together and how you expect people to use your code.<\/p>\n\n<p>This can also contain flowcharts, diagrams, example code snippets and anything else that would be useful.<\/p>\n\n<p>If you like, you could have a colleague review it in a pull\/merge request before progressing.<\/p>\n\n<p>Once the README file is written and you're happy with its contents, you can start coding.<\/p>\n\n<p>Also, documentation is commonly missed or skipped in projects, so moving it forward in the development process ensures it will be done and, as it's being written nearer to the writing of the code, it's more likely to be correct instead of writing it all once the code has been written.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d42eb72698b1793f4f2c361ad4470d81",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json b/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json
index 7e78d9db2..060715891 100644
--- a/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json
+++ b/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Next week, I'll be presenting a lightning talk at the North West Drupal user group (NWDUG)'s August meetup.<\/p>\n\n<p>It'll be a crash course into automated testing and test-driven development with Drupal, in which I plan to show how to get started by writing and running your first automated tests whilst exploring the different types of tests that are available.<\/p>\n\n<p>It's an online event, so if you'd like to see this and other lightning talks on the 8th of August, RSVP at <a href=\"https:\/\/www.meetup.com\/nwdrupal\/events\/293429104\">https:\/\/www.meetup.com\/nwdrupal\/events\/293429104<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "770e300e666c4816b8e8fc9943555225",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json b/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json
index c33e19b55..591a522aa 100644
--- a/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json
+++ b/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When writing code, it's common to suffix the class name with the type of class it is.<\/p>\n\n<p>I do this often for most types of classes, such as Controllers, EventListeners, Factories, Repositories and Builders.<\/p>\n\n<p>However, I don't always for value objects and data transfer objects (DTOs).<\/p>\n\n<p>Also, I don't always suffix interfaces with <code>Interface<\/code>.<\/p>\n\n<p>I've been re-reading the documentation for the Symfony Serializer component, which references both <code>NameConverterInterface<\/code> and <code>MyDto::class<\/code>.<\/p>\n\n<p>Whilst it does make the names more verbose, it does clarify what the class is used for.<\/p>\n\n<p>Symfony's coding standards and Drupal's PHP coding standards have conventions for this, but what do you think?<\/p>\n\n<p>Do you add suffixes to your class or interface names, or do you prefer the simplified versions?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5c2783e9ca75aee09edea870a5cf5f42",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.84ede6fa-2682-4edf-8b22-ee603de0b8c7.json b/content/node.84ede6fa-2682-4edf-8b22-ee603de0b8c7.json
index 5eec4c4a9..bc3ca1a7e 100644
--- a/content/node.84ede6fa-2682-4edf-8b22-ee603de0b8c7.json
+++ b/content/node.84ede6fa-2682-4edf-8b22-ee603de0b8c7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday I wrote about <a href=\"http:\/\/default\/daily\/2025\/01\/13\/patches\">how I used a patch file to customise a project in my Nix configuration<\/a>.<\/p>\n\n<p>I'm familiar with patch files from my Drupal contributions, when we used to create and upload patch files and attach them to issues to contribute changes.<\/p>\n\n<p>Although patches aren't used to contribute to Drupal any more, you can still apply patches to Drupal code in your own projects if you need to.<\/p>\n\n<p>If there's a customisation or fix you need you need to apply, instead of altering and \"hacking\" the source files, you can apply changes with patch files.<\/p>\n\n<p>Instead of Nix, I use <a href=\"https:\/\/github.com\/cweagans\/composer-patches\">composer-patches<\/a> to automatically apply patches when running <code>composer install<\/code>.<\/p>\n\n<p>For example, in my composer.json file, I can add something like this:<\/p>\n\n<pre><code class=\"json\">\"extra\": {\n    \"patches\": {\n        \"drupal\/default_content\": {\n            \"Issue #2698425: Do not reimport existing entities (https:\/\/www.drupal.org\/project\/default_content\/issues\/2698425#comment-15593214)\":  \"patches\/default_content-2698425-do-not-reimport-196.patch\",\n            \"Issue #3160146: Add a Normalizer and Denormalizer to support Layout Builder (https:\/\/www.drupal.org\/project\/default_content\/issues\/3160146#comment-14814050)\": \"patches\/default_content-3160146-53.patch\"\n        }\n    },\n},\n<\/code><\/pre>\n\n<p>This will apply these two patch files to the Default Content module (which are the same as running <code>git diff<\/code> between two commits), which I needed to do for a recent project.<\/p>\n\n<p>If the upstream issue is fixed and the patch is no longer needed, they can be removed and the module can be updated to the latest version.<\/p>\n\n<p>And this works for core and contrib projects.<\/p>\n\n<p>The same as the tmux-sessionizer example, this approach means I can apply any changes without needing to duplicate or alter the code, and it makes it easy to contribute by testing other people's patches or applying and contributing your own.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "64930ff9734d8caf5d32c9d3840e4b0a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json b/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json
index 59a118826..63160d052 100644
--- a/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json
+++ b/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've used Drush - the Drupal shell - to interact with my Drupal applications on the command line since I started around 2008.<\/p>\n\n<p>It's always been part of my Drush experience.<\/p>\n\n<p>From installing Drupal and performing routine actions such as enabling modules and clearing caches to, in newer Drupal versions, performing migrations and generating Storybook stories.<\/p>\n\n<p>Many projects I work on have custom Drush commands to perform tasks from the command line.<\/p>\n\n<p>This week, I created a new Drupal 11 project for a client using the <a href=\"https:\/\/github.com\/drupal\/core-recommended\">drupal\/core-recommended<\/a> package and initially forgot to install Drush so I could install Drupal.<\/p>\n\n<p>I'm surprised Drush isn't in Drupal core or a dependency of the recommended package.<\/p>\n\n<p>There is a basic Drupal CLI at <a href=\"https:\/\/git.drupalcode.org\/project\/drupal\/-\/blob\/94bc96150ca726fc667be51c8176f90b56e492df\/core\/scripts\/drupal\">core\/scripts\/drupal<\/a>, but I wonder if we'll see a fully-featured CLI tool like Drush included with Drupal core, similar to Symfony's console or Laravel's artisan commands.<\/p>\n\n<p>For me, including Drush would be an obvious choice.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ef470110690cdf26694bb4a29a3c1255",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json b/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json
index e258be281..4ecaafa17 100644
--- a/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json
+++ b/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I previously worked on a project where, after a code change had been reviewed and merged, it was pushed to a UAT environment for the client to test.<\/p>\n\n<p>This usually resulted in a group of changes pushed to the UAT environment, waiting for the client to test them.<\/p>\n\n<p>They would, and then decide which changes they wanted to be moved to production.<\/p>\n\n<p>Maybe changes 1, 2 and 4 would be asked to be deployed, but not 3 or 5.<\/p>\n\n<p>Someone would then cherry pick the relevant commits onto the mainline branch and deploy them to production.<\/p>\n\n<p>But, if the code isn't the same as on that UAT environment, how do you know it still works?<\/p>\n\n<p>Could a commit have been missed or could not including a non-selected commit have caused a regression or unintended side effects?<\/p>\n\n<p><code>git cherry-pick<\/code> isn't a command I use often, and definitely not in this scenario.<\/p>\n\n<p>If you want to select which changes go live, feature flags are a better option as you don't need to change the commits or code you're pushing.<\/p>\n\n<p>You push all the commits from UAT to production and enable the feature flags for the things you want to release.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bbdb6758f1c4bd5875133b5b5a4314a5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json b/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json
index cdf3ecd5a..80cc6d503 100644
--- a/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json
+++ b/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was recently working on a feature over a few mob programming sessions.<\/p>\n\n<p>After the session, we implemented part of the feature but couldn't merge it as it wasn't complete.<\/p>\n\n<p>After working on other things that day, I'd need to rebase my local commits and push the last-but-one commit to the remote repository to keep the incomplete feature only in my local repository (I forgot a few times and almost pushed it accidentally).<\/p>\n\n<p>The commit prevented me from following continuous integration - where everyone commits and pushes their code a minimum of once daily.<\/p>\n\n<p>What if someone else wanted to look at that code between mob sessions? They couldn't, as it was only on my laptop.<\/p>\n\n<p>If I'd made a temporary branch, it would be outdated and behind other changes to our mainline branch.<\/p>\n\n<h2 id=\"feature-flags-to-the-rescue\">Feature flags to the rescue<\/h2>\n\n<p>As this commit was part of a larger change, it couldn't be merged, so we added a feature flag around it.<\/p>\n\n<p>The values were set to null and hidden by default, and populated by the new changes and displayed if the flag was enabled.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This meant we could safely push the commit, make the changes available to everyone and enable the feature on the environments we wanted - preventing it from showing on production.<\/p>\n\n<p>This allowed us to get back to our usual working practices, and I didn't need to worry about accidentally pushing the commit and prematurely showing our changes in production.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9014cd6aad9e046cc2bea06ae3204989",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json b/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json
index 843390287..74f1b6b1b 100644
--- a/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json
+++ b/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few days ago, I asked <a href=\"http:\/\/default\/daily\/2024\/02\/25\/why-do-people-still-use-git-flow\">why people are still using Git Flow in 2024<\/a>.<\/p>\n\n<p>I moved to trunk-based development two years ago and haven't looked back.<\/p>\n\n<h2 id=\"why-did-i-do-that%3F\">Why did I do that?<\/h2>\n\n<p>Only having a single branch instead of separate <code>main<\/code> and <code>develop<\/code> branches and branches for each feature and fix is much simpler.<\/p>\n\n<p>I don't get merge conflicts when trying to merge branches together, as everything is on a single branch.<\/p>\n\n<p>A couple of years ago, I was working on two features for a project. I was demoing them to a client and broke my local environment when switching branches from feature A to feature B.<\/p>\n\n<p>It was embarrassing, and it took me time to resolve the issues before I could continue working.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Working mostly on a single branch avoids merge conflicts, saves time, and simplifies my workflow.<\/p>\n\n<p>No more confusion, merge conflicts or broken demos.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8704d7b04d607a1f28ca76b40770dae4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json b/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json
index 1d69d4f65..9cc4a22c5 100644
--- a/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json
+++ b/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>With the focus being on Drupal 7's potential end-of-life this November, it's also worth being aware that Drupal 9 (released in June 2020) will also be unsupported as of November 2023.<\/p>\n\n<p>This is because of its dependency on Symfony 4, which is ending its security support in November.<\/p>\n\n<p>Drupal 10 was released in December 2022 and will be the main version until Drupal 11 is released in 2024.<\/p>\n\n<p>Luckily, major upgrades of Drupal are much easier these days, with no large code rewrite or data migration required.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dbe97e5743e2c4d9c4744f379dcd2428",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json b/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json
index 3e8beb616..68bf526cb 100644
--- a/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json
+++ b/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've often heard and advocated for not \"putting logic\" in template files and having a separation of concerns.<\/p>\n\n<p>The templates should be as simple to read and change as possible, and any complicated logic should be moved elsewhere.<\/p>\n\n<p>There can be presentational logic - such as a simple if condition to determine if a value should be shown or looping over a list of items, but business logic should be within custom code - ideally within Service, Action or Command classes - and injected into the templates.<\/p>\n\n<p>As well as making the templates simpler and cleaner, this logic can be tested separately with automated tests to ensure it works as expected. If the logic is within a template, this can be done for some things using Functional tests, such as whether some text appears on a page, but testing whether it appears in a certain order, for example, is much harder. This is best done within kernel or unit tests.<\/p>\n\n<p>As well as being more testable, extracting the logic from a template makes it more reusable. You can use a service from multiple places within your website without duplicating it, making your website code smaller and easier to maintain.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2bb59d5691c8de6da82be10d5c3b871c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json b/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json
index 6dbf6a615..7966c7696 100644
--- a/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json
+++ b/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Agile and Scrum have become standard approaches in software development.<\/p>\n\n<p>Work is planned and organised into iterations\/cycles\/sprints, usually lasting two weeks.<\/p>\n\n<p>As one sprint is being worked on, the next is usually already planned and the following one is being discussed.<\/p>\n\n<p>It's common for code deployments and releases to follow the same pattern.<\/p>\n\n<p>When a sprint is finished, the changes are released.<\/p>\n\n<p>But that means if a task is worked on at the start of the sprint, it won't be available for at least two weeks.<\/p>\n\n<p>It may be longer if the sprint is longer or if there are steps like manual testing that also happen.<\/p>\n\n<p>What if a change is needed or a bug is found?<\/p>\n\n<p>Is that going to be at least another two weeks before it can be addressed?<\/p>\n\n<p>Do you need to start using hotfixes and dealing with multiple branches and <a href=\"http:\/\/default\/daily\/2025\/02\/18\/conflicts\">merge conflicts<\/a>?<\/p>\n\n<p>I suggest separating your planning and work schedules from your deployments.<\/p>\n\n<p>Deploy as often as possible, even during a sprint.<\/p>\n\n<p>You want your feedback loop to be as small and quick as possible.<\/p>\n\n<p>But, importantly, <a href=\"http:\/\/default\/daily\/2023\/06\/21\/deployments-or-releases\">deploying code is different to releasing features<\/a>.<\/p>\n\n<p>If you need to do manual testing, use feature flags to <a href=\"http:\/\/default\/daily\/2022\/12\/07\/separating-releases-from-deployments-with-feature-flags\">separate deploying the code from releasing the feature<\/a>.<\/p>\n\n<p>Then, when it's ready to go live, you only need to enable the feature flag - no code deployment needed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "45f407c2e5e4e066da156bd49eb7991a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json b/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json
index da1805614..a22d69f5d 100644
--- a/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json
+++ b/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently saw articles and videos about an AI service telling people to put glue on pizza and gave a recommended number of rocks to eat every day.<\/p>\n\n<p>From my understanding, the service had indexed some satirical articles and then returned the information within responses to questions and searches.<\/p>\n\n<p>As well as the obvious issues with AI returning incorrect or dangerous information in general, this applies to software development as a number of Developers using AI services as coding assistants or pair programming partners, or having it provide AI-powered code completion.<\/p>\n\n<p>My experience of using AI hasn't been great with it suggesting broken solutions or to use functionality that doesn't exist, so I don't use it often.<\/p>\n\n<p>If you do, make sure to double-check the results it gives you and use what it gives you as a starting point instead of just copying and pasting it into your code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bbe07c03d6666a63b4f31aef9e1ef5d3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json b/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json
index c7ab6e391..20fcd7a99 100644
--- a/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json
+++ b/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The last few days' emails have been about using Ansible to create and configure infrastructure, but it can also be used to deploy application code.<\/p>\n\n<p>The simplest way being that an artifact is built locally - e.g. a directory of static HTML pages from a static site generator - and uploaded onto the server, and for this you could use Ansible's <code>synchronize<\/code> module.<\/p>\n\n<p>It's a wrapper around the <code>rsync<\/code> command and makes it as simple as specifying <code>src<\/code> and <code>dest<\/code> values for the local and remote paths.<\/p>\n\n<p>For more complicated deployments, I like to use a tool called Ansistrano - an Ansible port of a deployment tool called Capistrano.<\/p>\n\n<p>It creates a new directory for each release and updates a <code>current<\/code> symlink to identify and serve the current release, and can share files and directories between releases.<\/p>\n\n<p>As well as being able to configure settings such as the deployment strategy, how many old releases to keep, and even the directory and symlink names, there are a number of hooks that you can listen for an add your own steps as playbooks so you can install dependencies, generate assets, run migrations, or rebuild a cache as part of each deployment.<\/p>\n\n<p>If you're running your applications in Docker, you could use Ansible to pull the latest images and restart your applications.<\/p>\n\n<p>For more information and examples, I've given a talk on Ansible at various PHP events, which covers some Ansible basics before moving on to <a href=\"http:\/\/default\/talks\/deploying-php-ansible-ansistrano\">deploying applications with Ansistrano<\/a>.<\/p>\n\n<hr>\n\n<p>Want to learn more about how I use Ansible? <a href=\"http:\/\/default\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "77a04f54c7ca12e8f95a6282d7667d35",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8b3f37aa-64aa-4d89-8593-52cbf781b713.json b/content/node.8b3f37aa-64aa-4d89-8593-52cbf781b713.json
index 96efe88e7..91924ad9d 100644
--- a/content/node.8b3f37aa-64aa-4d89-8593-52cbf781b713.json
+++ b/content/node.8b3f37aa-64aa-4d89-8593-52cbf781b713.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I saw a <a href=\"https:\/\/www.linkedin.com\/posts\/petermorlion_refactoring-technicaldebt-softwaredevelopment-activity-7054378097051095040-I545\">LinkedIn post by Peter Morlion<\/a>, in which he describes micro-refactoring - very small and safe refactors like renaming a variable, moving a method in a file to a more logical place, or adding a comment.<\/p>\n\n<p>He says that micro-refactors are safer than big refactors and have less chance of introducing a regression, are easy to do, improve the code quality over time, make larger refactorings easier later, increase the readability of your code, and reduce technical debt bit by bit.<\/p>\n\n<h2 id=\"what%27s-the-issue%3F\">What's the issue?<\/h2>\n\n<p>I agree with what Peter says and also encourage people to make small refactors to the code they're working on and follow the \"<a href=\"http:\/\/default\/daily\/2022\/12\/22\/the-boy-scout-rule\">Boy Scout rule<\/a>\".<\/p>\n\n<p>The main blocker to this I've seen is Git workflows that require people to work in separate branches that need to be reviewed before being merged, as this slows down the process.<\/p>\n\n<p>As Peter also says, micro-refactorings can be done anytime while working on other tasks. This is hard to do if each refactor requires its own branch and pull request, and the number of pull requests would quickly become unmanageable and take time to review.<\/p>\n\n<p>If I know that a micro-refactor like renaming a variable is going to take hours, days or weeks to be reviewed and merged, I'd probably be less likely to do the refactor in the first place. Not to mention having to update my working code once it's been merged.<\/p>\n\n<h2 id=\"what-do-i-prefer-to-do%3F\">What do I prefer to do?<\/h2>\n\n<p>I prefer to follow trunk-based development where everyone commits to a single branch and continuous integration where everyone is committing, pushing and pulling changes often - removing the need for merging branches and merge conflicts.<\/p>\n\n<p>Instead of asynchronous code review, I prefer to pair- or mob-program or to rely on automation with CI\/CD pipelines.<\/p>\n\n<p>If the commit before my change is passing the pipeline checks, and they're still passing after my change, they're good to deploy.<\/p>\n\n<p>Making the process as frictionless as possible encourages people to make small changes and micro-refactors, and to make codebases better a small piece at a time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5c4a4fd75b5b1c31d731d1445a90003d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json b/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json
index 44e0b4534..a7518de24 100644
--- a/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json
+++ b/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It's been almost a year and a half since I last pushed a feature branch, created a pull request, and waited for it to be reviewed and (hopefully) merged and deployed.<\/p>\n\n<p>On the majority of teams and projects that I've worked on, this was how things were done.<\/p>\n\n<p>Tasks would be worked on in separate branches which would need to be reviewed by one or more other Developers before being merged.<\/p>\n\n<p>I'm an advocate for continuous integration and trunk-based development (both I plan on writing about in more depth) in which there is no formal code review step, but instead, I encourage people to pair program as much as possible.<\/p>\n\n<p>Pair or mob (group) programming, for me, is like a real-time code review where you can discuss and make changes instantly, rather than waiting until the work is complete and someone reviewing it after the fact. If a bug is spotted as you're typing it or something could be named better, you can update it there and then.<\/p>\n\n<p>But there are other benefits too.<\/p>\n\n<p>Instead of one person writing some code, and others reviewing it after the fact, multiple people have written it together and the knowledge is shared amongst those people.<\/p>\n\n<p>As you've worked together, you don't need to ask or wait for someone to set time aside to review your changes, so it's quicker for them to be merged and deployed. It's already been reviewed, so as long as any automated checks pass, the code can be merged.<\/p>\n\n<p>I've worked in pairs where I've taught someone how to write automated tests and do test-driven development, which I suspect wouldn't have been quite the same if they'd just read the finished code afterwards.<\/p>\n\n<p>Of course, some Developers and teams will prefer the typical code review process - it's worked well for me and projects that I've worked on in the past - but personally, I like the speed, agility, mentoring and learning, and social benefits that I can get more easily from pair programming.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a4dd64d8e6ca0ab3625278ad7028abfa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json b/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json
index 7d6de5bf1..e98e6aa4d 100644
--- a/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json
+++ b/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been a Nix user for about a year, starting with its package manager on my previously installed Linux distribution.<\/p>\n\n<p>I started to use Home Manager for my user configuration and dotfiles and later switched to the NixOS operating system.<\/p>\n\n<h2 id=\"using-nix-for-software-development\">Using Nix for software development<\/h2>\n\n<p>I've also been using Nix Flakes for per-project configuration.<\/p>\n\n<p>A Flake file is a simple file written in the Nix language that defines the project's dependencies and installs them from the Nix package manager.<\/p>\n\n<p>Here is an example Flake for a PHP CLI application:<\/p>\n\n<pre><code class=\"nix\">{\n&nbsp; inputs.nixpkgs.url = \"github:NixOS\/nixpkgs\/nixos-unstable\";\n\n&nbsp; outputs = inputs@{ flake-parts, ... }:\n&nbsp; &nbsp; flake-parts.lib.mkFlake { inherit inputs; } {\n&nbsp; &nbsp; &nbsp; systems = [ \"x86_64-linux\" ];\n\n&nbsp; &nbsp; &nbsp; perSystem = { config, self', inputs', pkgs, system, ... }: {\n&nbsp; &nbsp; &nbsp; &nbsp; devShells = {\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; default = pkgs.mkShell {\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; buildInputs = with pkgs; [ php82 php82Packages.composer ];\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; };\n&nbsp; &nbsp; &nbsp; &nbsp; };\n&nbsp; &nbsp; &nbsp; };\n&nbsp; &nbsp; };\n}\n<\/code><\/pre>\n\n<p>It declares that PHP 8.2 and Composer are available, even if I have different versions installed globally.<\/p>\n\n<h2 id=\"will-nix-replace-docker%3F\">Will Nix replace Docker?<\/h2>\n\n<p>Nix and Flakes have replaced Docker for me on some projects.<\/p>\n\n<p>If I have a simple setup and need a specific version of PHP or Node and some additional programs, I can get those from the Flake.<\/p>\n\n<p>I don't know if it'll replace Docker for me completely and work on more complex projects, but it's working well for me where I'm using it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7f55d425fa5b0836f5c8d0f6980cc54e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json b/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json
index 193deb86a..61499f04f 100644
--- a/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json
+++ b/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tailwind offers the @apply directive that you can use to extract components in your CSS by applying the styles the classes would have added.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"css\">\/* Input *\/\n\n.btn {\n  @apply inline-block rounded-3xl bg-blue-500 px-8 py-3 text-lg text-white hover:bg-blue-800 focus:bg-blue-800;\n}\n\n\/* Output *\/\n\n.btn {\n  --tw-bg-opacity: 1;\n  --tw-text-opacity: 1;\n  background-color: rgb(59 130 246 \/ var(--tw-bg-opacity));\n  border-radius: 1.5rem;\n  color: rgb(255 255 255 \/ var(--tw-text-opacity));\n  display: inline-block;\n  font-size: 1.125rem;\n  line-height: 1.75rem;\n  padding-bottom: 0.75rem;\n  padding-left: 2rem;\n  padding-right: 2rem;\n  padding-top: 0.75rem;\n}\n\n.btn:hover {\n  --tw-bg-opacity: 1;\n  background-color: rgb(30 64 175 \/ var(--tw-bg-opacity));\n}\n\n.btn:focus {\n  --tw-bg-opacity: 1;\n  background-color: rgb(30 64 175 \/ var(--tw-bg-opacity));\n}\n<\/code><\/pre>\n\n<p>Whilst this works and reduced duplication, I prefer to handle this within my HTML instead.<\/p>\n\n<p>All templating engines I've used have ways to loop over or map through items and including separate files such as separate partials or different components.<\/p>\n\n<p>The main benefit of this is that you get the HTML structure of the component and not just the styling. If you extract a .btn component, it may depend on a span or other element within it to display correctly but as this isn't obvious, it may be missed when writing an implementation of it in HTML - this can't happen when working inside a loop or importing a canonical version.<\/p>\n\n<p>Also, by working just in the HTML markup, we continue to get the lower cognitive load and speed benefits that we're used to when styling with utility classes rather than switching between multiple files.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "de94dc72634b64860368d368dd1b936a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json b/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json
index 16ff39f14..d19cca962 100644
--- a/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json
+++ b/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I <a href=\"https:\/\/twitter.com\/opdavies\/status\/1767846980250714261\">posted a tweet<\/a> with a screenshot of some code.<\/p>\n\n<p>When previously working on the <a href=\"http:\/\/default\/daily\/2024\/02\/19\/introducing-versa\">Versa CLI tool<\/a>, I had a TODO comment saying \"What if there are multiple languages?\".<\/p>\n\n<p>Versa is a tool for standardising commands between different languages and frameworks, but some projects, like my personal website, use multiple languages.<\/p>\n\n<p>The website is powered by Sculpin, a static site generator written in PHP (so there is a composer.json file) and node to compile the front-end assets (so there is also a package.json file).<\/p>\n\n<h2 id=\"what-problem-am-i-trying-to-solve%3F\">What Problem Am I Trying to Solve?<\/h2>\n\n<p>Depending on the language, commands like <code>versa install<\/code> will need to execute a different command - e.g., composer install<code>or<\/code>npm install` (or an equivalent node package manager).<\/p>\n\n<p>I added PHP support first, so if a composer.json file is found, the PHP command is run as the default.<\/p>\n\n<p>What I thought was for projects with multiple languages, to prompt the user to select the language when running the command if no explicit language is set.<\/p>\n\n<p>This led me to do a spike of using Symfony Console's <code>choice<\/code> method to see what that would look like so I could add a screenshot to the GitHub issue.<\/p>\n\n<p>Once I'd finished with the spike, rather than deleting the code, I wrapped it in an <code>if (false)<\/code> condition so it wouldn't be executed, but I could still re-enable it in the future.<\/p>\n\n<p>The screenshot in the tweet showed this, along with the text \"Minimum viable feature flag.\"<\/p>\n\n<p>This is only supposed to be there for a short time until I revisit the code and implement the feature I was spiking on.<\/p>\n\n<p>If it would be a long time before I looked at it again, I'd take a different approach.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the Thing<\/h2>\n\n<p>One of the main rules of using feature flags is that they should be short-lived.<\/p>\n\n<p>It's less than ideal to read through a codebase and see it scattered with feature flags that are no longer needed and were used to release a feature several months ago, but the flag hasn't been removed.<\/p>\n\n<p>A feature flag is a temporary solution for separating the deployment of code from the release of a change.<\/p>\n\n<p>Once it's been released, the flag should be removed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5433ca25d20eea02dd4ac8345d46c026",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json b/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json
index c6b9af28f..7e13906db 100644
--- a/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json
+++ b/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whilst speaking with Dave Liddament last week, I remembered a slide I've seen in some of his previous presentations, such as <a href=\"https:\/\/www.daveliddament.co.uk\/talks\/effective-code-review\">Effective Code Review<\/a>.<\/p>\n\n<p>On the slide is a graph that shows the amount of time needed to fix a bug at different stages of the development lifecycle.<\/p>\n\n<p>Fixing a bug is the quickest and simplest when writing code.<\/p>\n\n<p>It's harder when being code reviewed or QA or client tested, more so when it's being released, and the most difficult and expensive once it's in the maintenance phase.<\/p>\n\n<p>Once it's live in the production environment, there's additional cleanup work to do which adds to the time and cost, and potentially damages your reputation.<\/p>\n\n<p>The sooner you can find a bug, the better.<\/p>\n\n<p>This is where tools such as automated testing, static analysis and CI pipelines shine and make it easier for you to find and fix potential bugs sooner.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4b09fa0814819f49425fd0eb6bf68e75",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json b/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json
index 87f580fc0..59187f22c 100644
--- a/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json
+++ b/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A couple of weeks ago, I wrote that <a href=\"http:\/\/default\/daily\/2024\/08\/17\/types-add-context\">using types adds context to code<\/a>, making it easier to read and understand.<\/p>\n\n<p>Something else that also adds context is <a href=\"https:\/\/www.php.net\/manual\/en\/functions.arguments.php#functions.named-arguments\">named arguments<\/a>, which were introduced to PHP in version 8.0.0.<\/p>\n\n<p>I particularly like them when making assertions within tests, where getting the expected and actual values in the wrong order can create some confusing output.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">self::assertSame(expected: 'My Drupal website', actual: $node-&gt;label());\n<\/code><\/pre>\n\n<p>While I can tell from the assertion that I'm checking two values are the same, adding the argument names makes it clear which is the expected value and which is the actual value.<\/p>\n\n<p>In fact, if you use named arguments, the order no longer matters, so I can put them in whichever order I want and it will work the same way.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a4594c6103d2d62b9550cde5004820f8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json b/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json
index 7aa8864ea..f966f2137 100644
--- a/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json
+++ b/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Just because I consider some code to be simpler, that doesn't necessarily mean there's less code.<\/p>\n\n<p>It's possible to write a whole function or class on one line, but that doesn't mean it's simple to read or understand.<\/p>\n\n<p>The opposite is also true.<\/p>\n\n<p>I can extract business logic from Controller classes into different service classes, commands or actions.<\/p>\n\n<p>I can use data transfer objects (DTOs), value objects and Collection classes to give names and meanings to things instead of always using generic strings, arrays or objects.<\/p>\n\n<p>I can follow design patterns and implement Repositories, Decorators, Factories and Builders to better organise code and make it easier to use and update.<\/p>\n\n<p>I can write tests that act as examples and executable documentation for people to see how to use the code I've written.<\/p>\n\n<p>This can all make code easier to read, understand and use - even though there is more of it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e59143196c70adc39a01487205db060b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json b/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json
index 8c2f2d2a1..e649eaec3 100644
--- a/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json
+++ b/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm always working on various personal and client projects, and they contain a lot of the same configuration files. I exclusively use Docker and Docker Compose on all projects, I use a <code>justfile<\/code> for running tasks, and for PHP projects, I need configuration files for tools like PHPStan, PHPCS and PHPUnit.<\/p>\n\n<p>The majority of those files are the same with some slight configuration for each project - such as whether it uses <code>web<\/code> or <code>docroot<\/code>, or which paths are checked with static analysis or for coding standards issues.<\/p>\n\n<p>I've given a talk called <a href=\"http:\/\/default\/presentations\/working-with-workspace\">Working with Workspace<\/a> - a tool that we used at an agency I worked at. It had two functions - to execute project tasks and to generate configuration files from templates.<\/p>\n\n<p>I use a <code>justfile<\/code> to execute tasks and commands but needed to write my own tool to generate the configuration files.<\/p>\n\n<p>The result is that I can add one YAML file to a project, enter the values that it needs and when I run the CLI tool, it will generate all of the files the project needs.<\/p>\n\n<p>As well as being faster to set up a project, like a <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/tree\/main\/drupal-localgov\">LocalGov Drupal Docker example<\/a>, having a canonical set of templated configuration files I can enhance and maintain by adding new features and fixes and they'll be added to every project when I next generate its files.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0eeef7ecb5ae126ae9d82df72eb13277",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.90791de2-4132-43e3-94ea-41609f317429.json b/content/node.90791de2-4132-43e3-94ea-41609f317429.json
index 1396d3714..773f1db9b 100644
--- a/content/node.90791de2-4132-43e3-94ea-41609f317429.json
+++ b/content/node.90791de2-4132-43e3-94ea-41609f317429.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I re-watched Revolution OS - a 2001 documentary about the history of Linux, open source and the free software movement.<\/p>\n\n<p>I was also explaining to my son about how software used to be distributed on CD-ROMs.<\/p>\n\n<p>This got me thinking.<\/p>\n\n<p>What if we still primarily distributed software on physical media like CD-ROMs?<\/p>\n\n<p>What if every release to your software project had to be burned to a disc, transported and inserted into a server to be installed.<\/p>\n\n<p>This may take days or weeks instead of seconds or minutes.<\/p>\n\n<p>Once a version is distributed, it isn't quick or easy to fix a bug or release a feature.<\/p>\n\n<p>You can't simply update the version on every CD that was distributed with some hardware or attached to a computing magazine.<\/p>\n\n<p>How would you change writing software if you worked this way?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ec8d13cd01af70105278b0ff6c81493c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json b/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json
index 45de69e72..478935fe8 100644
--- a/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json
+++ b/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few months ago, I started doing some <a href=\"https:\/\/www.youtube.com\/@opdavies\/livhttps:\/\/www.youtube.com\/watch?v=Wlkcf1PLWN8e\">live coding sessions on YouTube<\/a> again.<\/p>\n\n<p>As well as <a href=\"http:\/\/default\/daily\/2024\/03\/16\/adding-tests-to-the-content-access-by-path-module\">writing automated tests for the Content Access by Path module<\/a>, I <a href=\"https:\/\/www.youtube.com\/watch?v=Wlkcf1PLWN8\">started to re-learn Behat<\/a> - a behavioural testing tool for PHP.<\/p>\n\n<p>I've used Behat before but mainly use PHPUnit in Drupal to write my automated tests, so I thought I'd try it again in my <a href=\"http:\/\/default\/build-configs\">Build Configs<\/a> tool written in Symfony.<\/p>\n\n<p>In that stream, I was able to install it, do some research to refresh my memory, and get some initial tests running.<\/p>\n\n<p>I've been busy finishing some client development projects recently (and still have some availability for Q3 projects), but I will pick up the live streaming again soon!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "da87df7942e8c7bb996fcc8856ebaf7a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json b/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json
index fe14883ca..202cc1411 100644
--- a/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json
+++ b/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2024\/07\/22\/there-isnt-just-one-way-to-do-something\">there not being one right answer<\/a> when developing software, things aren't always perfect.<\/p>\n\n<p>You don't always need to strive for the \"ideal\" solution.<\/p>\n\n<p>Sometimes, what you have is good enough and can be released and can be iterated on later, if needed.<\/p>\n\n<p>The focus should be on whether it achieves what it's supposed to.<\/p>\n\n<p>There isn't always an ideal or perfect solution.<\/p>\n\n<p>Sometimes, the icky solution is the right one.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "df97490d71b0f6f78a149c80f0c301f5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json b/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json
index b4fce1bec..c420ea844 100644
--- a/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json
+++ b/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In February 2012, I saw a tweet from Tim Millwood asking if anyone wanted to maintain or co-maintain a Drupal module called <a href=\"https:\/\/www.drupal.org\/project\/override_node_options\">Override Node Options<\/a>.<\/p>\n\n<p>It had more than 9,200 active installations at that time, with versions for Drupal 5, 6 and 7.<\/p>\n\n<p>I said yes and became the module\u2019s maintainer.<\/p>\n\n<p>The module now has versions for Drupal 7, 8 and 9, with (at the latest count, according to Drupal.org) 32,292 active installations - which makes it currently the 197th most installed module.<\/p>\n\n<p>There have been two main things that come to mind with this module, related to automated testing.<\/p>\n\n<p>Before I become the maintainer, a feature request had been created, along with a large patch file, to add some new permissions to the module. There were some large merge conflicts that stopped me from just committing the changes but I was able to fix them manually and, because the tests still passed, ensure that the original functionality still worked. There weren\u2019t tests for the new permissions but I committed the patch and added the tests later.<\/p>\n\n<p>Without the tests to ensure that the original functionality still worked, I probably wouldn\u2019t have committed the patch and would have just closed the issue.<\/p>\n\n<p>More recently, a friend and ex-colleague and I decided to refactor some of the module's code.<\/p>\n\n<p>We wanted to split the <code>override_node_options.module<\/code> file so that each override was in its own file and its own class. This would make them easier to edit and maintain, and if anyone wanted to add a new one, they\u2019d just need to create a new file for it and add it to the list of overrides.<\/p>\n\n<p>Without the tests ensuring that the module still worked after the refactor, we probably wouldn\u2019t have done it as it was used on over 30,000 sites that I didn't want to break.<\/p>\n\n<p>When I was learning about testing, I was working on projects where I was writing the code during the day and the tests in the evening on my own time.<\/p>\n\n<p>I remember once when my manual testing had been fine, but when writing the test, I found that I\u2019d used an incorrect permission name in the code that was causing the test to fail. This was a bug that, rather than waiting for a QA Engineer or the client to discover and report, I was able to fix it locally before I'd even committed the code.<\/p>\n\n<p>I also worked on an event booking and management website, where we had code responsible for calculating the number of available spaces for an event based on orders, determining the correct price based on the customer's status and the time until the event, creating voucher codes for new members and event leaders, and bulk messaging event attendees. All of the custom functionality was covered by automated tests.<\/p>\n\n<p>The great thing about testing is that it gives you confidence that everything still works how you expect - not only when you wrote the code, but also in the future.<\/p>\n\n<p>I've talked about this, and how to get started with automated testing in Drupal, in a presentation called <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">TDD - Test-Driven Drupal<\/a>. If you want to find out more, the slides and a video recording are embedded there.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6b0fad90dfe0aa71566d4a773bb78d7a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json b/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json
index 831020997..c710d06ea 100644
--- a/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json
+++ b/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Most open source projects have a BDFL (Benevolent dictator for life) who makes the ultimate decisions for the project.<\/p>\n\n<p>The ones who spring to mind are Dries, Fabien and Taylor for Drupal, Symfony and Laravel respectively.<\/p>\n\n<p>But what about your codebase?<\/p>\n\n<p>Who is the BDFL for your application?<\/p>\n\n<p>Who decides how features should be implemented or what standards to follow?<\/p>\n\n<p>Who ensures the codebase is consistent regardless of the feature being delivered or the file being read?<\/p>\n\n<p>If you don't have one, you should.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "222b248251326ba2fe44041d0e2f159a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json b/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json
index 96ec3ffc1..608b07e02 100644
--- a/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json
+++ b/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Almost all Drupal projects have multiple environments - production and one or more pre-production environments.<\/p>\n\n<p>A lot have development and staging, some have QA or UAT, or an environment per feature or sprint.<\/p>\n\n<p>Each Developer has their own local environment to work on.<\/p>\n\n<p>As new things are added, such as content types, fields and views, they need to be present on all environments.<\/p>\n\n<p>When I started using Drupal, I needed to perform the same steps to manually recreate the changes on each environment.<\/p>\n\n<p>Later, people started to use the Features module to export configuration into modules that could be committed and deployed as code.<\/p>\n\n<p>This was accompanied by \"deploy\" modules that included update hooks to revert features or perform other tasks.<\/p>\n\n<p>Since version 8, Drupal has had the Configuration Synchronization module.<\/p>\n\n<p>Developers make changes once and export them to files using a simple command like <code>drush config:export<\/code>.<\/p>\n\n<p>Once the code has been deployed to each environment, run <code>drush config:import<\/code> to import the changes.<\/p>\n\n<p>This will synchronise the configuration on the environment, making it the same as the exported configuration in an automated way - the same way every time.<\/p>\n\n<p>Much quicker and more robust than doing it manually.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a689477a80adb90fdbe7160be7d2450e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json b/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json
index cb4985573..25c369bce 100644
--- a/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json
+++ b/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When writing a test, something that I like to do is start by writing the first assertion first, and then work backwards.<\/p>\n\n<p>My first assertion might be <code>self::assertTrue($result)<\/code>.<\/p>\n\n<p>If I ran this test, it would fail because of the undefined <code>$result<\/code> variable - but it's clear to me what I need next by asking, \"Where does <code>$result<\/code> come from?\".<\/p>\n\n<p>If I need to call a method on another class and get the result, I'll add it before the assertion. Then I repeat the process and ask, \"What do I need for this to work?\".<\/p>\n\n<p>Maybe I need to create some users or content in the application for the class to query and return a result based on it, so I'll create those.<\/p>\n\n<p>With this approach, I'm not making any assumptions about the test's prerequisites, and I usually find that I end up with cleaner and more focused tests.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "05685b54939905d0714bbd9c928bd011",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json b/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json
index 8b726d5f6..f85dbaceb 100644
--- a/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json
+++ b/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I was in Birmingham for a hackathon event organised by the School of Code, who I've been a Bootcamp mentor for for the last few cohorts.<\/p>\n\n<p>At the event, I was mentoring a team of three Bootcamp graduates to plan and build a Christmas-themed application.<\/p>\n\n<p>We decided on a Christmas walking application where people can view upcoming walks, log in and book a place.<\/p>\n\n<p>After designing some initial pages, such as the Home page with a login form, a registration form, a list of walks and a walk detail page, we started to code them.<\/p>\n\n<p>Naturally, we started with the Home page, the login form and the login functionality.<\/p>\n\n<p>But, is that the most valuable part of the application?<\/p>\n\n<p>What differentiates it from other applications, such as the ones being built by other squads at the event?<\/p>\n\n<p>In this case, it's the page showing the list of walks and, if you click one, the details about that walk.<\/p>\n\n<p>The squad needed to give a presentation and demo of the application by the end of the day, so we needed to prioritise.<\/p>\n\n<p>We refocused on the walk pages and built them before moving back to the other pages to complete the user journey so it could be shown.<\/p>\n\n<p>Similarly, we didn't need a fully functional user login and registration system for the demo. We just needed to show the forms we'd built, demo the user journey and show how someone would find and register for an event.<\/p>\n\n<p>When I'm building an application, I identify the most valuable part and focus on it rather than other unrelated functionality that could likely be done manually or another way until that functionality is available.<\/p>\n\n<p>The beginning of the user journey isn't always the best first thing to start developing.<\/p>\n\n<p>It was a great day, our squad won the prize for the event, and I look forward to attending more events and continuing to work with the School of Code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "afd0a9a1478406d663af9a2abb8eedae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json b/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json
index 645b0b302..ba5c12606 100644
--- a/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json
+++ b/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Most of my work uses the Drupal framework, and I've given talks and workshops on automated testing and building custom Drupal modules with test-driven development. Today, I wanted to see how quickly I could get a working test suite on a new Drupal project.<\/p>\n\n<p>I cloned a fresh version of my <a href=\"https:\/\/github.com\/opdavies\/docker-examples\">Docker Examples repository<\/a> and started the Drupal example.<\/p>\n\n<p>I ran <code>mkdir -p web\/modules\/custom\/example\/tests\/src\/Functional<\/code> to create the directory structure that I needed, and then <code>touch web\/modules\/custom\/example\/tests\/src\/Functional\/ExampleTest.php<\/code> to create a new test file and populated it with some initial code:<\/p>\n\n<pre><code class=\"language-php\">&lt;?php\n\nnamespace Drupal\\Tests\\example\\Functional;\n\nuse Drupal\\Tests\\BrowserTestBase;\nuse Symfony\\Component\\HttpFoundation\\Response;\n\nclass ExampleTest extends BrowserTestBase {\n\n  protected $defaultTheme = 'stark';\n\n}\n<\/code><\/pre>\n\n<p>For the simplest test, I decided to test some existing Drupal core functionality - that an anonymous user can view the front page:<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\npublic function the_front_page_loads_for_anonymous_users() {\n  $this-&gt;drupalGet('&lt;front&gt;');\n\n  $this-&gt;assertSession()-&gt;statusCodeEquals(Response::HTTP_OK);\n}\n<\/code><\/pre>\n\n<p>To execute the test, I ran <code>SIMPLETEST_DB=sqlite:\/\/localhost\/\/dev\/shm\/test.sqlite SIMPLETEST_BASE_URL=http:\/\/web phpunit -c web\/core web\/modules\/custom<\/code>. The environment variables could be added to a <code>phpunit.xml.dist<\/code> file but I decided to add them to the command and use Drupal core's PHPUnit configuration file.<\/p>\n\n<p>As this is existing functionalty, the test passes. I can change either the path or the response code to ensure it also fails when expected.<\/p>\n\n<p>With the first test working, it's easy to add more for other functionality, such as whether different users should be able to access administration pages:<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\npublic function the_admin_page_is_not_accessible_to_anonymous_users() {\n  $this-&gt;drupalGet('admin');\n\n  $this-&gt;assertSession()-&gt;statusCodeEquals(Response::HTTP_FORBIDDEN);\n}\n\n\/** @test *\/\npublic function the_admin_page_is_accessible_by_admin_users() {\n  $adminUser = $this-&gt;createUser([\n    'access administration pages',\n  ]);\n\n  $this-&gt;drupalLogin($adminUser);\n\n  $this-&gt;drupalGet('admin');\n\n  $this-&gt;assertSession()-&gt;statusCodeEquals(Response::HTTP_OK);\n}\n<\/code><\/pre>\n\n<p>Hopefully, this shows how quickly you can get tests running for a Drupal module. If you'd like to see more, the slides and video recording of my <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">Test-Driven Drupal talk<\/a> are online.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "00dc66fc251e796aa7a1f167673d4f33",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json b/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json
index 7defeac6e..19af167e2 100644
--- a/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json
+++ b/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A popular approach to writing clean code is to avoid the \"else\" keyword and, if possible, avoid nesting <code>if<\/code> statements within other <code>if<\/code> statements.\nIf I look at some code, I want to see as few indentation levels as possible, making the code easier to read and understand.<\/p>\n\n<h2 id=\"what-should-i-do-instead%3F\">What should I do instead?<\/h2>\n\n<p>Instead, you check for a condition; if that isn't met, you return early.\nFor&nbsp;example, here is some code I saw recently during a meetup talk:<\/p>\n\n<pre><code class=\"language-php\">$callingClass = $scope-&gt;getClassReflection()-&gt;getName();\n\nif ($callingClass === TextMessageQueueProcessor::class) {\n&nbsp; &nbsp; return [];\n}\n\n$type = $scope-&gt;getType($node-&gt;var);\n\nforeach ($type-&gt;getReferencedClasses() as $targetClass) {\n&nbsp; &nbsp; if ($targetClass === TextMessageSender::class) {\n&nbsp; &nbsp; &nbsp; &nbsp; return [\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RuleErrorBuilder::message(\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; sprintf(\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; \"Can not call %s from %s\",\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $targetClass,\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $callingClass\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; )\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; )-&gt;build()\n&nbsp; &nbsp; &nbsp; &nbsp; ];\n&nbsp; &nbsp; }\n}\n\nreturn [];\n<\/code><\/pre>\n\n<p>There are no <code>else<\/code> statements.<\/p>\n\n<p>If the calling class isn't of the required type, it returns immediately with no violations, and we continue, knowing the calling class must be what we need.<\/p>\n\n<p>If the target class is one where the code shouldn't be called from, it returns immediately with the&nbsp;violation.<\/p>\n\n<p>Finally, if no violations were found within the referenced classes, it returns an empty array.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The code always returns an array of rule violations but does so as soon as possible at each point.<\/p>\n\n<p>The code is clean and readable, and I can understand it, knowing once each condition is passed, I don't need to continue thinking about it.<\/p>\n\n<p>Whilst there are some situations to use <code>else<\/code>, most of the time I've found that I can use an early return instead.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d2e8d39f68f4ae6ba0c9ffab688585b7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json b/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json
index 6062f660c..7e273f3b0 100644
--- a/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json
+++ b/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Imagine this scenario.<\/p>\n\n<p>You have two options on how frequently you can deploy code changes to your application.<\/p>\n\n<p>Option 1: Every day.<\/p>\n\n<p>Option 2: Once a quarter.<\/p>\n\n<p>No more, no less.<\/p>\n\n<p>I'd choose daily.<\/p>\n\n<p>I much prefer to deploy changes as often as possible rather than waiting.<\/p>\n\n<p>I'm much more confident when releasing small changes - even if it's a small refactor, such as changing a variable name or extracting a small helper method.<\/p>\n\n<p>It might even seem too small to release.<\/p>\n\n<p>But the smaller the release is, the easier it is to find and fix any issues, and knowing that the next release would only be the following day makes it easier to fix forward instead of rolling back a large release with months of changes.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Whilst it may seem counterintuitive initially, it's much less risky to release small changes often compared to large changes infrequently.<\/p>\n\n<p>Which option would you choose?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "60c7b0989070ede0d263c59ede0bc4d4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json b/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json
index d2b571dab..dfa65e324 100644
--- a/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json
+++ b/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since Drupal 10.2, the framework has started to adopt PHP attributes - a new feature since PHP 8 - as an alternative to annotations when defining plugins, such as blocks and queues.<\/p>\n\n<p>From the 10.2 release notes:<\/p>\n\n<blockquote>\n  <p>Drupal core has started adopting PHP attributes, a modern PHP language feature, to provide better developer experience for plugin annotations. Contributed and custom code can begin adopting this improved API for their plugins, and Block and Action plugins can all be converted to the new API.<\/p>\n<\/blockquote>\n\n<p>It seems that what's been added so far is the first phase of converting the core's plugins, with more to follow in future versions.<\/p>\n\n<p>There are also discussions about supporting both attributes and annotations in Drupal 11.<\/p>\n\n<p>I love to see Drupal continuing to evolve and adopt new features from the PHP language and Symfony framework (such as autowiring and autoconfiguration), and I'm looking forward to using attributes in my projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e1820905156cf1adfe5f3e7514f30eb2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json b/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json
index 369ab4bc5..eac00a6a4 100644
--- a/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json
+++ b/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently been improving my typing.<\/p>\n\n<p><img src=\"https:\/\/www.oliverdavies.uk\/assets\/images\/daily-emails\/typing.png\" alt=\"A screenshot of a typing test.\"><\/p>\n\n<p>My speed is usually good, but my accuracy is not where I'd like it to be (it's usually around 95%, and I'd like it to be nearer 99%).<\/p>\n\n<p>It may seem counterintuitive, but I need to slow down to get faster.<\/p>\n\n<p>But not focusing on the speed and prioritising accuracy, I'll still get faster as I'm not mistyping as many keys.<\/p>\n\n<p>It's the same when I run.<\/p>\n\n<p>My first few kilometres are slower as I get into the run, find my pace, focus on breathing, etc.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The same can also be said for automation and automated testing.<\/p>\n\n<p>They require some time investment initially but will save time as a project evolves and becomes more complex.<\/p>\n\n<p>You need to slow down initially to go faster later.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b9eb71111ebc108eadaa0b9fae7d84ff",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json b/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json
index 3b23f8860..619ba1e6c 100644
--- a/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json
+++ b/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When I start a new project, and sometimes when I join an existing project, there are no CI (continuous integration) pipelines, no automated tests, and sometimes no local environment configuration.<\/p>\n\n<p>In that case, where should you start when adding a CI pipeline?<\/p>\n\n<p>I like to start with the simplest solution to get a passing build and to prove the concept - even if it's a \"Hello, world\" message. I know that the pipeline is configured correctly and runs when expected, and gives the output that I expect.<\/p>\n\n<p>I like to use Docker for my development environments, partly because it's very easy to reuse the same set up within a CI pipeline just by running <code>docker image build<\/code> or <code>docker compose build<\/code>.<\/p>\n\n<p>Having a task that ensures the project builds correctly is a great next step.<\/p>\n\n<p>Within a Dockerfile, I run commands to validate my lock files, download and install dependencies from public and private repositories, and often apply patch files to third-party code. If a lock file is no longer in sync with its composer.json or package.json file, or a patch no longer applies, this would cause Docker and the CI pipeline to fail and the error can be caught and fixed within the pipeline.<\/p>\n\n<p>Next, I'd look to run the automated tests. If there aren't any tests, I'd create an example test that will pass to prove the concept, and expect to see the number of tests grow as new features are added and as bugs are fixed.<\/p>\n\n<p>The big reason to have automated tests running in a pipeline is that all the tests are run every time, ensuring that the test suite is always passing and preventing regressions across the codebase. If any test fails, the pipeline fails. This is knows as continuous delivery - ensuring that code is always in a releasable state.<\/p>\n\n<p>From there, I'd look to add additional tasks such as static analysis and code linting, as well as anything else to validate, build or deploy the code and grow confidence that a passing CI pipeline means that the code is releasable.<\/p>\n\n<p>As more tasks are added to the pipeline, and the more of the code the tasks cover (e.g. test coverage) the more it can be replied upon.<\/p>\n\n<p>If there is a failure that wasn't caught in the CI pipeline, then the pipeline itself should be iterated on and improved.<\/p>\n\n<p>Having a CI pipeline allows you to identify issues sooner and fix them quicker, encourages best practices like automated testing and test-driven development, and enables continuous deployment where code is automatically deployed after a passing build.<\/p>\n\n<p>If you have a project without a CI pipeline, I'd encourage you to add one, to start small, and continuously iterate on it over time - adding tasks that are useful and valuable, and that build confidence that you can safely release when you need to.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c3c98eabf22507f37576fbd83774fdc3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json b/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json
index 6840f0ed9..71d69094c 100644
--- a/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json
+++ b/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In one of the lessons in my <a href=\"http:\/\/default\/atdc\">free automated testing in Drupal email course<\/a>, I explain how I create configuration that I need within my tests, such as adding a custom field:<\/p>\n\n<blockquote>\n  <p>But how do you know what to name the configuration files and what content to put in them?<\/p>\n  \n  <p>Rather than trying to write them by hand, I create the configuration I need, such as fields, within a Drupal site and then export and edit the files I need.<\/p>\n<\/blockquote>\n\n<p>As well as creating the fields in the Drupal UI, I was also using it to export the configuration files I needed:<\/p>\n\n<blockquote>\n  <p>Once Drupal is installed and the configuration has been created, you can go to - \/admin\/config\/development\/configuration\/single\/export and select the configuration type and name.<\/p>\n  \n  <p>The filename is shown at the bottom of the page, and you can copy the content into files within your module.<\/p>\n<\/blockquote>\n\n<h2 id=\"there%27s-another-way\">There's another way<\/h2>\n\n<p>After reading that lesson, somene replied and reminded me that there's a <code>--destination<\/code> option you can use with the <code>drush config:export<\/code> command.<\/p>\n\n<p>Instead of exporting to the standard configuration directory, I can do it to a temporary directory:<\/p>\n\n<pre><code class=\"language-shell\">run drush cex --destination \/app\/.ignored\/config\n<\/code><\/pre>\n\n<p>Everyhing in a <code>.ignored<\/code> direcotry is automatically ignored by Git, and to get the files I need, I can use Linux's <code>find<\/code> command to find any files that contain the field name and copy them into my test module directory:<\/p>\n\n<pre><code class=\"language-shell\">find .ignored\/config \\\n  -type f \\\n  -name \\*drupal_project\\* \\\n  -exec cp -r {} web\/modules\/custom\/foo\/modules\/foo_test\/config\/install \\;\n<\/code><\/pre>\n\n<p>I still need to edit the files to remove the <code>uuid<\/code> and <code>_core<\/code> values, but this approach means less clicking in the Drupal UI which makes me more productive.<\/p>\n\n<p>I used this approach when <a href=\"http:\/\/default\/daily\/2024\/02\/16\/keep-logic-within-tests-for-as-long-as-you-can\">writing my SaaS code yesterday<\/a> and it worked well.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c22cd0a275dfae98de9b0fedf7c17fd2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json b/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json
index 67fa12809..afce158a7 100644
--- a/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json
+++ b/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as using <a href=\"http:\/\/default\/daily\/2024\/12\/07\/open-source\">free and open source software for my homelab<\/a>, I develop software applications for clients using open source software, such as PHP, Drupal, Symfony and Sculpin.<\/p>\n\n<p>I also use open source software to do this.<\/p>\n\n<p>I use <a href=\"http:\/\/default\/daily\/2024\/09\/08\/my-laptop-died\">NixOS as the operating system on my laptop<\/a>.<\/p>\n\n<p>I use Alacritty as my terminal emulator and tmux as a terminal multiplexer to have different sessions, windows and tabs for each project.<\/p>\n\n<p>I write my code in Neovim and use various additional plugins.<\/p>\n\n<p>I use Git for source control and tools like PHPStan, PHPUnit and Pest to run checks on my code.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/11\/30\/using-nix-for-local-application-development\">I use Nix and devenv<\/a> to run the applications locally and host them on Linux servers running Nginx.<\/p>\n\n<p>I also use OBS, Kdenlive and GIMP to record and edit my content, which are all also open source projects.<\/p>\n\n<p>I run an open source business, using open source tools and projects and contribute to and <a href=\"http:\/\/default\/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">maintain my own open source software projects<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cb55832959bd5f053aa3c4766a247f91",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json b/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json
index d1549a04c..6623e41d2 100644
--- a/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json
+++ b/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I often do before writing new code is to write out what it needs to do, either in a README file or as code comments.<\/p>\n\n<p>It could be paragraphs of text explaining the problem I'm solving, or a short checklist of what the code needs to do.<\/p>\n\n<p>This clarifies the situation and the approach and allows uncovering any potential questions or issues.<\/p>\n\n<p>It takes time, but I can complete the task quicker as I've made the decisions and answered any questions upfront.<\/p>\n\n<p>I'll either remove the comments as I write the code or, if they still add value, I'll keep them to add more context and information.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a23f721f43c2ea925dd0e3d1b57188c9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json b/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json
index bc54cd600..74c7dc395 100644
--- a/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json
+++ b/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>With unit tests, you need to mock <strong>everything<\/strong>.<\/p>\n\n<p>If what you're testing has a dependency, you need to create and use a mock version.<\/p>\n\n<p>If the mock has its own dependencies, you need to mock those, too.<\/p>\n\n<p>I've written unit tests with mocks and accidentally only tested the mocks instead of the functionality I intended.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>With integration tests, you can use and test the real dependencies.<\/p>\n\n<p>Whilst they may be slightly slower to run, I prefer the simpler setup, less need for mocks, and knowing the real services work - not just the mocked versions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b38408f033b23dc55649c0a05a3af78b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json b/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json
index de1b14835..577069cde 100644
--- a/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json
+++ b/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently installed an application called Gitea <a href=\"http:\/\/default\/daily\/2024\/12\/01\/homelabbing-with-nixos\">on my homelab<\/a>.<\/p>\n\n<p>It's a service for hosting and managing Git repositories, similar to GitHub, GitLab and Bitbucket, but I'm hosting it on my own hardware and I'm in full control of my data.<\/p>\n\n<p>I've moved all of my client project code from private repositories in the Cloud to my Gitea instance, as well as some of my own private repositories for work-in-progress or archived projects.<\/p>\n\n<p>I plan to keep my open source project repositories on GitHub and Drupal.org, and use Gitea for personal and client project code, but I may move more to Gitea - like my website code and dotfiles - as time goes on.<\/p>\n\n<p>And, because I use NixOS for my homelab, installing Gitea was as easy as <code>services.gitea.enable = true<\/code>.<\/p>\n\n<p>There is also a Docker Compose image and Gitea Cloud, but running something like Gitea for your private code is something I'd like to see more Developers and agencies do.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ec1b7c6047417070fb9d7336a9849a98",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json b/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json
index 98c2b02ed..543cf1748 100644
--- a/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json
+++ b/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently saw a post with a screenshot of some code they'd written using Tailwind CSS.<\/p>\n\n<p>Reading the comments, it had the usual \"re-inventing the wheel\" and \"just use inline styles\" comments, which, to me, didn't seem very helpful and not the point of the post.<\/p>\n\n<p>When I've given a <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">talk on Tailwind CSS<\/a>, I've acknowledged that people have common initial reactions and suggested people try it for a week or so and see how it works for them before making up their minds.<\/p>\n\n<p>Someone did after a conference and posted this on Twitter:<\/p>\n\n<blockquote>\n  <p>I saw a talk on tailwind at a conference. Spent 15 minutes afterwards \"discussing\" with the presenter how it was horrible and against the neat way of CSS and so on. But promised to try it just once as he said it feels better than it looks.<\/p>\n  \n  <p>He was right. It's so freeing.<\/p>\n<\/blockquote>\n\n<p>The same approach applies to many other things, such as pair programming, automated testing, test-driven development, static analysis, Scrum, Linux and Vim - to name a few.<\/p>\n\n<p>If you use it and don't like it, don't continue and return to what you did before.<\/p>\n\n<p>Whether you keep it or not, you better understand what you're evaluating and not dismiss it out of hand.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "859a0b5a56a896a9cc602a3a1bbc3bae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json b/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json
index e9d3450d5..10e573f24 100644
--- a/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json
+++ b/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I often see Drupal projects where people have put raw HTML code into their body or other rich-text fields.<\/p>\n\n<p>Whilst it can be useful for short-term prototyping, I don't think it should be done for content that will be reused or kept for a period of time.<\/p>\n\n<p>If you have structured HTML code in multiple nodes, you can't make changes without editing each instance.<\/p>\n\n<p>What if you need to fix a bug and have hundreds or thousands of instances?<\/p>\n\n<p>If you have inline styles, they won't be updated or affected by changes to your stylesheets, such as changing colour or font family.<\/p>\n\n<p>Instead, create first-class components that use templates that are easier to change and maintain and have a single source of truth that adheres to your design system.<\/p>\n\n<p>In Drupal, use structured data in fields with Paragraphs or Layout Builder and build the templates around them.<\/p>\n\n<p>This makes it easier to maintain and also for people to add and edit content.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c81fcb760babf4b27ac37f42d606aade",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json b/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json
index 436580e9a..0be2baad3 100644
--- a/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json
+++ b/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>No one writes code, commits it and pushes it to production without checking it works.<\/p>\n\n<p>Everyone tests their code, but they usually do it manually. They switch from the code to a browser or terminal, run the code and evaluate the result.<\/p>\n\n<p>This takes time, you need to switch contexts, and the test is only valid for that time.<\/p>\n\n<p>There's no guarantee it will still work in the future.<\/p>\n\n<p>Automated testing, however, means you can write your code and run the tests without leaving your IDE or text editor.<\/p>\n\n<p>The tests can also be run in the future to ensure the functionality works without needing to re-test it manually.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "26af65ffd563616c16d70721cbce516d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json b/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json
index 77377bea6..8855a9ddd 100644
--- a/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json
+++ b/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few days ago, I wrote about <a href=\"http:\/\/default\/daily\/2024\/06\/07\/not-invented-here\">where Drupal used to be<\/a>, and some of the things that Drupal predates - such as Git, GitHub and Composer.<\/p>\n\n<p>With Drupal 8, Drupal changed and switched from \"not invented here\" to \"proudly found elsewhere\" and started use and embrace third-party code.<\/p>\n\n<p>Now, we use Composer to manage Drupal core's dependencies, as well as for individual Drupal projects - a tool widely used and central to the PHP community and its projects.<\/p>\n\n<p>This allowed us to include and use third-party code within Drupal, including Symfony components, Twig templates, Doctrine libraries, Guzzle and more - using tried and tested solutions instead of writing everything from scratch.<\/p>\n\n<p>We use PHPUnit for our automated tests and PHPStan for static analysis.<\/p>\n\n<p>We use Rector, a PHP tool to automate code updates and refactorings, to automatically create updates for modules to make them compatible with the next major Drupal version.<\/p>\n\n<p>Drupal.org have migrated its code repositories to GitLab, now support merge requests instead of patch files, and will soon be migrating issues, too, making Drupal easier to maintain and contribute to.<\/p>\n\n<p>As well as the code, we've also been influenced by approaches, such as the modern Drupal release cycle and version management - following semantic versioning, backwards compatibility policies, twice-yearly feature releases and no \"rewrite everything\" major version upgrades.<\/p>\n\n<p>Looking back, a lot has improved since 2015 which makes Drupal a very interesting place to be.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6f566971a35889eee0927fe88991b9e9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json b/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json
index 8f95b8e6d..dd64ed2a6 100644
--- a/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json
+++ b/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm refactoring some code on a client project - creating a Repository class to centralise some logic before implementing the next feature.<\/p>\n\n<p>The repository class is responsible for finding and returning any nodes with a specified field value and some base conditions (it must be the correct node type, published, etc.).<\/p>\n\n<h2 id=\"adding-a-custom-assertion\">Adding a custom assertion<\/h2>\n\n<p>I'm using PHPUnit's native assertions to check it returns a Collection (I regularly include the <code>illuminate\/collections<\/code> library from Laravel in other projects) and that each item is an instance of a <code>NodeInterface<\/code>, but there isn't an assertion to check each node is of the correct type.<\/p>\n\n<p>My initial implementation was to loop over each node and use <code>assertSame<\/code> on its bundle before refactoring to create an array of unique bundle names and comparing it to my expected names:<\/p>\n\n<pre><code class=\"language-php\">self::assertSame(\n  expected: [$nodeType],\n  actual: $haystack\n    -&gt;map(fn (NodeInterface $item): string =&gt; $item-&gt;bundle())\n    -&gt;unique()\n    -&gt;toArray(),\n);\n<\/code><\/pre>\n\n<h2 id=\"why-write-a-custom-assertion%3F\">Why write a custom assertion?<\/h2>\n\n<p>Whilst this works, it likely won't be clear in the future what it's testing.<\/p>\n\n<p>My initial thought was to add a comment describing it, but then I decided to wrap it in a custom assertion - <code>assertContainsOnlyNodesOfType<\/code> - a private static function within my test class that wraps the native assertions.<\/p>\n\n<p>This approach makes the test more readable now and in the future and more domain-focused by giving it a descriptive name.<\/p>\n\n<p>It can be easily reused within the same test case or elsewhere.<\/p>\n\n<p>Although I only perform one assertion in this case, I can combine multiple assertions and perform any other required steps.<\/p>\n\n<p>Finally, I can contain any implementation details within the custom assertion. Here, I'm matching the result against an array of expected values, not just a single node type which is what I want. This detail can be contained within the assertion, making it easier to read and reuse in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "850f3e0675f0598a361d17b99f568768",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json b/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json
index 2dc639861..839c50c67 100644
--- a/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json
+++ b/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently <a href=\"http:\/\/default\/daily\/2024\/12\/18\/self-hosting-podcast\">switched to self hosting<\/a> the MP3 files for the episodes of the Beyond Blocks podcast.<\/p>\n\n<p>The first step was to upload the files, followed by <a href=\"http:\/\/default\/daily\/2024\/12\/19\/working-iteratively\">updating the player<\/a> on the episode pages to use the HTML audio element.<\/p>\n\n<p>As I didn't want the player to switch immediately, I wrapped the new code in a feature flag (or feature toggle) to keep the original player active.<\/p>\n\n<p>Later, I could swap the player by enabling the feature flag.<\/p>\n\n<h2 id=\"how-i-did-it\">How I did it<\/h2>\n\n<p>Feature flagging is a straight forward concept.<\/p>\n\n<p>You isolate the code you want to be togglable within a conditional - i.e. an <code>if<\/code> statement - that you can easily change in the future.<\/p>\n\n<p>My website built with Sculpin, so I can add <code>self_host_podcast_episodes: false<\/code> to my sculpin_site.yml file.<\/p>\n\n<p>This will be available as <code>site.self_host_podcast_episodes<\/code>  and I can use this in my code to show the appropriate player.<\/p>\n\n<p>Something like:<\/p>\n\n<pre><code class=\"twig\">{% if site.self_host_podcast_episodes %}\n  Show the new player.\n{% else %}\n  Show the old player.\n{% endif %}<\/code><\/pre>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I like feature flags as you can separate deploying a feature from releasing it.<\/p>\n\n<p>The code can be deployed but not active until the feature is enabled.<\/p>\n\n<p>It's easy to enable, and easy to revert if needed.<\/p>\n\n<p>In Drupal applications, I use the <a href=\"https:\/\/www.drupal.org\/project\/feature_toggle\">Feature Toggle module<\/a>, so I can toggle feature flags by logging in and updating a checkbox.<\/p>\n\n<p>I also <a href=\"https:\/\/www.drupal.org\/project\/feature_toggle_twig\">wrote a module<\/a> with a Twig function so I can check if a feature toggle is enabled directly in a Twig template - the same as I'm doing in Sculpin.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "15704c55f5e3b5d6531dc8c8e9ae0182",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json b/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json
index 2c6f0986b..28d02df77 100644
--- a/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json
+++ b/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common thing I see when reading posts or watch videos where people are using Git is using the <code>-m<\/code> option when committing changes.<\/p>\n\n<p><code>-m<\/code> allows you to specify the commit message inline or, more specifically, the first line of the commit message.<\/p>\n\n<p>If you think of a commit message as an email, the first line is the subject line which is followed by the body of the message.<\/p>\n\n<p>If you don't use <code>-m<\/code>, Git will open an editor and you can type the full commit message into a file and save it.<\/p>\n\n<p>This includes the subject line and, more importantly, the body of the message where you can include as much additional information as you want.<\/p>\n\n<p>The subject line summarises the change, but the body can be used to explain why it was needed.<\/p>\n\n<p>You can describe the issue or requirements in more detail (don't just link to the issue or enter the issue number).<\/p>\n\n<p>You can describe any other approaches you considered or tried.<\/p>\n\n<p>You can describe any anticipated effects or consequences of this commit, any manual deployment steps or follow up tasks that will need to be created.<\/p>\n\n<p>You can include any additional information you were aware of at the time of making the commit that could be useful to yourself or others in the future.<\/p>\n\n<p>Think what information would you like to see when you next run <code>git log<\/code>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "60ee5cbd523e01444113724332b468eb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json b/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json
index fcd0342a1..69d0ba6e9 100644
--- a/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json
+++ b/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I used to work for the <a href=\"https:\/\/www.drupal.org\/association\">Drupal Association<\/a> - the non-profit organisation that supports the Drupal project, organises DrupalCon, and maintains Drupal.org.<\/p>\n\n<p>I improved Drupal.org, fixed Drupal 8 release blockers, improved user profiles, helped make the Drupal.org theme responsive, and assisted with new websites like Drupal Events and Jobs.<\/p>\n\n<p>At DrupalCon, one of the keynote speakers said, \"The Drupal Association is a small but mighty team\".<\/p>\n\n<p>On the <a href=\"https:\/\/www.drupal.org\/association\/staff\">Association staff page<\/a>, there are 15 staff members listed, including only five people in the Engineering team.<\/p>\n\n<p>I've been in the Drupal community for a long time and worked for various companies that make money from Drupal - a free and open-source project.<\/p>\n\n<p>However, it's \"free as in puppies\". You can have the puppy for free, but it costs time and money to look after it.<\/p>\n\n<p>There are programs like the Supporting Partners program which provide funding to the DA, but, at least when I worked there, a large amount of income was from event revenue from DrupalCon.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>As someone who works mainly on Drupal consulting and development projects, I'm pledging to commit a fixed percentage from my Drupal-related services and products to the Drupal Association, including my new <a href=\"http:\/\/default\/team-coaching\">team coaching<\/a> service.<\/p>\n\n<p>If the Association or Drupal weren't there, I wouldn't be able to provide those products and services, so it's in my interest to support the Drupal project and the Drupal Association. Maybe others will do the same.<\/p>\n\n<p><strong>Work with me and support the Drupal Association.<\/strong><\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "20f663e70965fc6a0abdf47d7dcc5c90",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json b/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json
index 437bffdbc..edc06f833 100644
--- a/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json
+++ b/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are multiple ways I've seen people write their test method names.<\/p>\n\n<p>This is the standard PSR-compliant camel-case method name:<\/p>\n\n<pre><code class=\"php\">public function testSomethingHappensWhenYouGoToThePage()\n<\/code><\/pre>\n\n<p>Some people find long camel-case names hard to read and prefer to use snake-case names:<\/p>\n\n<pre><code class=\"php\">public function test_something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>This still works as the method name still starts with the word <code>test<\/code>, but you'd need to add some overrides to phpcs for it not to complain about using snake-case words.<\/p>\n\n<p>Another option is to remove the <code>test<\/code> prefix and use an annotation:<\/p>\n\n<pre><code class=\"php\">\/** @test *\/\npublic function something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>And in newer PHPUnit versions, you can also use an attribute:<\/p>\n\n<pre><code class=\"php\">#[Test]\npublic function something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>Whilst this makes the method name shorter, you need to add an additional line before each test method for the annotation or attribute.<\/p>\n\n<p>Each has pros and cons, and people have their own preferences.<\/p>\n\n<p>Which do you do?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "74d7fe2b760e2005106513cfa1b4cae7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json b/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json
index 5be85c988..54109ff69 100644
--- a/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json
+++ b/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week on the Beyond Blocks podcast, I spoke with Tim Lehnen - CTO and former colleague at the Drupal Association.<\/p>\n\n<p>We discussed what the Drupal Association is and what it does, how companies and individuals can contribute and support the Association, some recent and upcoming improvements to Drupal.org, Drupal 7's end-of-life, and more.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/9-tim-lehnen\">Listen now<\/a><\/p>\n\n<p>This Friday, I'm releasing an episode with Ryan Weaver from SymfonyCasts.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2a00495abcb2b4fb956be9ee3bf4582e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json b/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json
index c9ae1381f..f3f51099b 100644
--- a/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json
+++ b/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Test-driven development as a concept is easy.<\/p>\n\n<p>Before you write any code, you write a failing test and then write enough code to get it to pass.<\/p>\n\n<p>But implementing test-driven development is harder.<\/p>\n\n<p>As well as overcoming the initial reluctance to write the tests first, it takes time to learn how to use it well.<\/p>\n\n<p>Code katas are great for practising TDD, but it can take time to progress from that to using it in a full application with more pieces.<\/p>\n\n<p>As with many things, practice and perseverance are key.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "59a601afa0b33fe6c4acdffa4bbb1e64",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json b/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json
index d23e96e1b..9a9b239f1 100644
--- a/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json
+++ b/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the most recent episode of Beyond Blocks, I discuss LEGO, robotics, teaching kids to code and open-source software with Andy Hoang, who runs a company called \"Beyond Blocks\".<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/18-andy-hoang\">Listen to the episode here<\/a>.<\/p>\n\n<p>Next week, Sam Mortenson and I discuss single file components in Drupal.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5608e282cfbf2d9573fec34289172c58",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json b/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json
index 5a7399971..e7117e190 100644
--- a/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json
+++ b/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Marian Kostadinov (<a href=\"https:\/\/twitter.com\/stochnagara\">stochnagara on Twitter<\/a>) replied to Friday's email about DTOs and value objects to tell me about <code>readonly<\/code> classes, which can be done in PHP 8.2.<\/p>\n\n<p>Looking at the previous class:<\/p>\n\n<pre><code class=\"language-php\">class AccountDetails {\n\n  public function __construct(\n    public readonly string $accountNumber,\n    public readonly string $sortCode,\n  ) {}\n\n}\n<\/code><\/pre>\n\n<p>Instead of setting each property as <code>readonly<\/code>, the whole class can instead be marked as <code>readonly<\/code>:<\/p>\n\n<pre><code class=\"language-php\">readonly class AccountDetails {\n\n  public function __construct(\n    public string $accountNumber,\n    public string $sortCode,\n  ) {}\n\n}\n<\/code><\/pre>\n\n<p>Thanks for the suggestion, Marian!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9297110388cf153de83397c7246c18c5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json b/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json
index 21ead8d3f..6dd601c10 100644
--- a/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json
+++ b/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>With test-driven development, you start with a failing test and focus on getting it to pass.<\/p>\n\n<p>But what do you do once it's passing?<\/p>\n\n<p>You either repeat the process, adding more assertions to the same test until you generate the next failure or write the next failing test, or take the opportunity to refactor the code.<\/p>\n\n<p>Is there something you'd like to change within the implementation or test code? You can do that whilst the tests are passing.<\/p>\n\n<p>You may want to extract a new class or method to improve the implementation or create some test helpers to reduce duplication within the tests.<\/p>\n\n<p>You just need to keep the tests passing to ensure the code still works. If something breaks, you fix it as soon as possible, either by fixing the code or reverting to the previously passing code.<\/p>\n\n<p>Then, once you've completed the refactoring, move back into the red\/green phase with the next test failure.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5c4e15d5b064e06491b78bb0021c82a7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json b/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json
index 082d552a3..54dd43206 100644
--- a/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json
+++ b/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When most people think of \"Don't repeat yourself\" or DRY, they probably think about not duplicating logic in code.<\/p>\n\n<p>If you've written some functionality once, you should avoid writing it again.<\/p>\n\n<p>I was recently browsing the code for an open source package and saw this:<\/p>\n\n<pre><code class=\"php\">\/**\n * Flush everything.\n *\/\npublic function flush(): void;\n\n\/**\n * Sets the formatter.\n *\/\npublic function setFormatter(FormatterInterface $formatter): void;\n\n\/**\n * Gets the formatter.\n *\/\npublic function getFormatter(): FormatterInterface;\n<\/code><\/pre>\n\n<p>This is another instance of repetition.<\/p>\n\n<p>The docblocks are just repeating what the code already tells me.<\/p>\n\n<p>I can understand from the method names what each function does, and I can see what parameters they have and their types.<\/p>\n\n<p>I can see if each method returns anything and, if so, what type it returns - e.g. <code>getFormatter<\/code> returns a <code>FormatterInterface<\/code>.<\/p>\n\n<p>I think these docblocks aren't needed and in my projects, would suggest they be removed.<\/p>\n\n<p>Unless they're adding more information, such as <a href=\"http:\/\/default\/daily\/2025\/03\/21\/phpdoc\">PHPStan PHPDoc types<\/a>, there's no need to repeat what the code already says.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0dcfb92613016648b8799e1ee65ada87",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json b/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json
index 6913bf562..59bc7ca04 100644
--- a/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json
+++ b/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Are you near London and want to learn about automated testing in Drupal?<\/p>\n\n<p>I'll be presenting a session and Q&amp;A on automated testing and test-driven development in Drupal.<\/p>\n\n<p>This is one of my favourite topics to present and teach, so I'm looking forward to this event.<\/p>\n\n<p>If you want to attend, <a href=\"https:\/\/www.meetup.com\/london-drupal-user-group\/events\/303500889\">RSVP on the meetup event page<\/a>.<\/p>\n\n<p>If you can't, check out my <a href=\"http:\/\/default\/atdc\">free Drupal testing email course<\/a> or <a href=\"http:\/\/default\/call\">book a 1-on-1 consulting call<\/a> and I'll get you started.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d1af70181dbb0fa7bc1126c999977ec5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json b/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json
index 1ebef18d9..94f13470a 100644
--- a/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json
+++ b/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently started <a href=\"http:\/\/default\/daily\/2024\/12\/18\/self-hosting-podcast\">self-hosting the episodes for the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>Instead of hosting the episodes on a third party service, the MP3 files are hosted on my server and played using the HTML5 audio element.<\/p>\n\n<p>The first step was to add the files to my website codebase and deploy them to the server. This was the smallest deployable iteration of this project.<\/p>\n\n<p>The second iteration was to change the player on the episode page.<\/p>\n\n<p>This is still a work-in-progress as I need to finish building the podcast feed to submit to iTunes, Spotify, etc.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I didn't need to wait to finish this before I could change the player, and I didn't need to do that before uploading the MP3 files.<\/p>\n\n<p>Each was its own deployable step, and this is how I like to approach tasks.<\/p>\n\n<p>I like to break things down as much as possible to find the smallest piece of task that can be committed and deployed.<\/p>\n\n<p>Deploying features iteratively is less risky that deploying everything at once.<\/p>\n\n<p>You're deploying changes in smaller parts, making it less likely for something to go wrong, and easier to identify and resolve any issues.<\/p>\n\n<p>And, if you need to roll back or revert a change, you can affect only the part you need instead of everything.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bd5f1ef86b1ea8d5f9af419bd836ded3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9ecc8bf3-5bf6-4713-9868-c6059db4d432.json b/content/node.9ecc8bf3-5bf6-4713-9868-c6059db4d432.json
index 09e77b378..9a883b734 100644
--- a/content/node.9ecc8bf3-5bf6-4713-9868-c6059db4d432.json
+++ b/content/node.9ecc8bf3-5bf6-4713-9868-c6059db4d432.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something that I've recently added to my PHP projects is <a href=\"https:\/\/github.com\/paratestphp\/paratest\">Paratest<\/a>.<\/p>\n\n<p>It adds parallel testing to PHPUnit, so your tests will be run in parallel instead of sequentially.<\/p>\n\n<p>For the example module in my <a href=\"http:\/\/default\/atdc\">automated testing in Drupal email course<\/a>, using Paratest reduces the execution time from ~16 seconds to ~8 seconds.<\/p>\n\n<p>In a client project with 136 tests, it reduces the time from four and a half minutes to less than two minutes.<\/p>\n\n<p>This is a big improvement just from running a single Composer command to add Paratest.<\/p>\n\n<p>There's also <a href=\"https:\/\/www.drupal.org\/project\/drupal\/issues\/2781123\">an open issue<\/a> for using it for Drupal core's tests, which is something I'll keep an eye on and will look to contribute to.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d6723cf0326f529b61786870511d23ff",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json b/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json
index d4ef5baff..96390bce0 100644
--- a/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json
+++ b/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After seeing it on some recent live streams and YouTube videos, I've recently been trying out the Nix package manager and looking into how I might use it for my local environment setup - potentially replacing some of my current Ansible configuration.<\/p>\n\n<p>Separate from the NixOS operating system, Nix is a cross-platform package manager, so instead of using <code>apt<\/code> on Ubuntu and <code>brew<\/code> on macOS, you could run Nix on both and install from the 80,000 packages listed on https:\/\/search.nixos.org\/packages.<\/p>\n\n<p>There is a community project called Home Manager which can be installed alongside Nix which, similar to Stow or what I'm doing with Ansible, can manage your dotfiles or even create them from your Home Manager configuration, and can manage plugins for other tools such as ZSH and tmux.<\/p>\n\n<p>There's also a Nix feature called \"Flakes\" which allow you to separate configuration for different operating systems. I currently have a flake for Pop!_OS which installs all of my packages and a minimal flake for my WSL2 environment as some of the packages are installed in Windows instead of Linux.<\/p>\n\n<p>I can see Ansible still being used to set up my post-setup tasks such as cloning my initial projects, but the majority of my current Ansible setup where I'm installing and configuring packages I think could be moved to Nix.<\/p>\n\n<p>I have a work-in-progress Nix-based version <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/tree\/7c3436c553f8b81f99031e6bcddf385d47b7e785\">in my dotfiles repository<\/a> where you can also see <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/blob\/7c3436c553f8b81f99031e6bcddf385d47b7e785\/home-manager\/modules\/git.nix\">how I've configured Git with Home Manager<\/a>.<\/p>\n\n<p>I may install NixOS on an old laptop to test that out too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "951d2d9e9835481f997f95a29b18efdf",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json b/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json
index 9e6170113..51ac92935 100644
--- a/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json
+++ b/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I started coding in 2007 to build a website for a Tae Kwon-Do School I used to train at.<\/p>\n\n<p>It was written with HTML and CSS and only contained a few small pages.<\/p>\n\n<p>When I wanted to add more dynamic content, such as news articles and events, I started to expand and started to use PHP and MySQL.<\/p>\n\n<p>PHP was a great first programming language for me (ignoring HTML and CSS), and it's gone through so many improvements since 2007, as well as the PHP content management systems and frameworks.<\/p>\n\n<p>I think a lot of new coders only learn or are taught JavaScript and I can understand why if they've only got a short time, such as on a bootcamp, but I also think there is a benefit to learning another language - such as PHP.<\/p>\n\n<p>PHP has Composer to manage dependencies, various robust content management systems and frameworks, PHPUnit and Pest for automated testing, PHPStan and Psalm for static analysis, and much more.<\/p>\n\n<p>I'd definitely recommend taking a look at PHP if you haven't already.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e69a1241f2245a8193f94d701b369c7c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json b/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json
index b5f1d5c28..a6b211661 100644
--- a/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json
+++ b/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When does it make sense not to write automated tests?<\/p>\n\n<p>Tests prevent regressions in codebases that are changed and updated over time.<\/p>\n\n<p>So, if you're working on a short-term project, such as a marketing campaign website that will only be live for a few months, you won't get as much benefit from having tests, especially if you may not even change it once it's live.<\/p>\n\n<p>Likewise, tests are useful for projects on which you want to avoid downtime and outages, especially if you sell products via your website or it contains important information. For other websites, such as personal blogs, that are less critical, testing may be less beneficial.<\/p>\n\n<p>Also, one of Drupal's key benefits is that you can build websites within the Drupal UI, without needing to write custom code.<\/p>\n\n<p>If you're going down this route, there is no custom code to test and a separate tool that checks URLs exist and returns the correct response code would be a better fit.<\/p>\n\n<p>If you then need to add any custom code and functionality, you may want to add tests.<\/p>\n\n<p>Whilst there are some situations where not writing tests is reasonable, there are more reasons and situations when you should, compared to not.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9e2e450ab9a61ff98aa475086eedc78f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json b/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json
index 6dca79ed6..0ccf27cc3 100644
--- a/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json
+++ b/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When creating accessible websites, as well as hover states for focusable elements, such as buttons, you also need to add focus styles that apply when users navigate the page using a keyboard and focusing on an element.<\/p>\n\n<p>With Tailwind, that can mean a lot of duplication if your hover and focus states are similar or the same, as the same classes need to be added with both the <code>:hover<\/code> and <code>:focus<\/code> variants.<\/p>\n\n<p>One of Tailwind's best features is its extensibility, which means I can create a new interaction state - <code>:hocus<\/code> - that works for both.<\/p>\n\n<p>It's very easy to do by adding this code to your <code>tailwind.config.js<\/code> or <code>tailwind.config.ts<\/code> file:<\/p>\n\n<pre><code class=\"javascript\">const plugin = require(\"tailwindcss\/plugin\");\n\nmodule.exports = plugin(({ addVariant }) =&gt; {\n&nbsp; addVariant(\"hocus\", [\"&amp;:hover\", \"&amp;:focus\"]);\n});\n<\/code><\/pre>\n\n<p>Or, use <a href=\"https:\/\/www.npmjs.com\/package\/tailwindcss-plugin-hocus-state\">the Tailwind CSS plugin I wrote<\/a>.<\/p>\n\n<p>Get more accessible websites and less duplication today!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "71b652d23e3a8bf54a1a5586877f67ca",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json b/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json
index 9138559ac..35252d32f 100644
--- a/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json
+++ b/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common approach I see on software projects is where Developers create separate Git branches for each task they work on.<\/p>\n\n<p>This commonly matches issues or ticket on a sprint board or issue tracker.<\/p>\n\n<p>Each ticket is worked on independently and merged into a long-lived mainline branch once complete.<\/p>\n\n<p>This type of approach is commonly called Git Flow or GitHub Flow.<\/p>\n\n<p>It's something <a href=\"http:\/\/default\/presentations\/git-flow\">I've given presentations<\/a> on in the past.<\/p>\n\n<p>A common downfall is that different branches can conflict with each other - either due to a merge conflict where the same lines are changed in different branches, or incompatible code is written that works separately but not when merged together.<\/p>\n\n<p>I used to work this way, even when working on projects as the only Developer.<\/p>\n\n<p>One time, I was demoing two features to a client and needed to switch branches and doing so broke what it was trying to show.<\/p>\n\n<p>These days, I avoid conflicts between branches by not branching.<\/p>\n\n<p>Everyone works on a single branch and pulls and pushes changes regularly.<\/p>\n\n<p>If you're <a href=\"http:\/\/default\/daily\/2025\/02\/17\/ci-cd\">doing continuous integration<\/a>, that should be once a day as an absolute minimum.<\/p>\n\n<p>I do <a href=\"http:\/\/default\/atdc\">test-driven development<\/a> and usually commit after each passing test.<\/p>\n\n<p>If you work on a single branch and pull and push changes regularly, you're much less likely to get merge conflicts and Developers can focus on pushing code instead of fixing merge conflicts.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6adab48b4653c69ec584429dd988b39d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json b/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json
index af246cc42..1b7f76968 100644
--- a/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json
+++ b/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Which PHPStan level should you use?<\/p>\n\n<p>PHPStan has different levels.<\/p>\n\n<p>When you run it on your code, the errors you see will depend on what level you set.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2023\/11\/27\/finding-the-best-test-base\">In yesterday's email<\/a>, the first example code block didn't generate an error until level 5 was used.<\/p>\n\n<p>So, how do you know which level to use?<\/p>\n\n<h2 id=\"for-greenfield-projects\">For greenfield projects<\/h2>\n\n<p>For new (greenfield) code, install and configure PHPStan before you write any code and have and have it run automatically as part of a CI pipeline.<\/p>\n\n<p>If you work on a team, speak with the other members and decide how strict you want PHPStan to be.<\/p>\n\n<p>Read the rule levels and decide which are the most valuable for your team.<\/p>\n\n<p>If you haven't used PHPStan or static analysis before, maybe start with a lower level.<\/p>\n\n<p>For me, typehints and return type checking are a must, though I like to use as high a level as possible.<\/p>\n\n<p>The more information you can provide to PHPStan, the more it will understand your code, give better results and be more likely to find potential bugs or issues.<\/p>\n\n<h2 id=\"for-brownfield-projects\">For brownfield projects<\/h2>\n\n<p>For existing (brownfield) code, start at the lowest level, which will give you the least number of errors.<\/p>\n\n<p>Fix any errors, exclude any rules you want to ignore or generate a baseline containing any existing errors.<\/p>\n\n<p>If you like, increase the level and repeat the process.<\/p>\n\n<p>Keep increasing the level as long as you feel comfortable, and PHPStan gives you meaningful results.<\/p>\n\n<p>Again, if you haven't used PHPStan or static analysis before, maybe stick with a lower level.<\/p>\n\n<p>If you start with a lower level, you can increase it later.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6225796a12956da7eebd27198ca6be4b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json b/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json
index 3a8a35479..bf2941031 100644
--- a/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json
+++ b/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week's guest on Beyond Blocks is <a href=\"http:\/\/default\/podcast\/10-ryan-weaver-symfonycasts\">Ryan Weaver<\/a>.<\/p>\n\n<p>Ryan is a Symfony Developer, Symfony core team member and writer for SymfonyCasts.<\/p>\n\n<p>We discussed recent developments in Twig templates, SymfonyCasts, release cycles, and similarities between the Drupal and Symfony projects and communities.<\/p>\n\n<p>I've been a long-time subscriber of SymfonyCasts and it was a big help when I was learning Drupal 8 for Twig and object-orientated PHP, so it was great to speak with Ryan.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "77a251bc42faf5a39bab63cacb3bb1bb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json b/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json
index cf736183a..d5a0dd312 100644
--- a/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json
+++ b/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal offers a few different types of tests you can use, but how do you know which one to pick?<\/p>\n\n<p>This is how I decide based on what I need to test by asking these questions:<\/p>\n\n<h2 id=\"do-i-need-to-test-http-requests-and-responses%3F\">Do I need to test HTTP requests and responses?<\/h2>\n\n<p>Do I need to make GET or POST requests to a URL and check its response code, e.g. to check the endpoint exists, that I get an expected \"Page not found\" or \"Forbidden\" message, or to check if an item was created or updated?<\/p>\n\n<p>If so, use a <code>Functional<\/code> test like <code>BrowserTestBase<\/code>.<\/p>\n\n<h2 id=\"do-i-need-to-test-with-javascript%3F\">Do I need to test with JavaScript?<\/h2>\n\n<p><code>BrowserTestBase<\/code> doesn't include JavaScript, so use a <code>FunctionaJavaScript<\/code> test if needed.<\/p>\n\n<h2 id=\"do-i-need-to-retrieve-services-from-the-service%2Fdependency-injection-container%3F\">Do I need to retrieve services from the service\/Dependency Injection container?<\/h2>\n\n<p>If I don't need to make HTTP requests but need access to the service container, I use a Kernel test such as <code>KernelTestBase<\/code>.<\/p>\n\n<p>There's more setup for kernel tests compared to functional tests, such as installing the required configuration and creating schema tables in the database. However, having less installed means the tests run faster.<\/p>\n\n<p>There are different base classes, such as <code>EntityKernelTestBase<\/code>, that can be used depending on the situation to simplify the setup.<\/p>\n\n<h2 id=\"can-i-test-the-code-in-isolation-without-the-service-container%3F\">Can I test the code in isolation without the service container?<\/h2>\n\n<p>If I can test the code without needing the service container and mock simple dependencies, then use a <code>Unit<\/code> test.<\/p>\n\n<p>These are very fast to run, but you can overuse mocks and sometimes test the mocks instead of the code you intended to test.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>As well as the regular unit test type, Drupal offers various types of test that can be used depending on the situation.<\/p>\n\n<p>I like to start with functional tests first and switch to kernel or unit tests when needed. They're slower to run but easier to write as they need less setup and arguably provide the most value.<\/p>\n\n<p>If you're just getting started with testing, they're probably the quickest to learn too.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1f85e49caa14c4e4bd7344bf54c9f094",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json b/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json
index 6521fb130..83ecfa7c0 100644
--- a/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json
+++ b/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the latest episode of the Beyond Blocks podcast, Ed Crompton and I discuss his case study of upgrading 15 websites for Oxfam on how to build and test a multilingual, multisite Drupal migration.<\/p>\n\n<p>We discussed focussing on delivering value, prioritising based on usefulness to users and stakeholders, Agile vs agile, and how they pivoted from a \"big bang\" approach to delivering rapid increments in smaller batches.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/4-ed-crompton-oxfam-case-study\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8d2c1d450d37e19beaa381c50da20645",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json b/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json
index 4c6ad27dc..d09042c52 100644
--- a/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json
+++ b/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you don't write automated tests or do test-driven development, you might move quickly to begin with - writing code and doing small amounts of manual testing.<\/p>\n\n<p>But, once you start changing the code to add new features or fix bugs, things will begin to slow down.<\/p>\n\n<p>You'll have more to test and need to ensure you don't break the existing functionality as well as your new code works.<\/p>\n\n<p>Whilst it may be faster initially, skipping tests will cause problems later.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b438edc4ee7e47b4c5ab1fe45e9f8be5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json b/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json
index 94ab280b2..5b4f2727e 100644
--- a/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json
+++ b/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Have you written a file like test.php or scratch.php whilst developing?<\/p>\n\n<p>Do you have files like this committed to your codebase?<\/p>\n\n<p>These are often temporary files that are written by a Developer to test the code they're writing.<\/p>\n\n<p>They could include some test data, load a service or perform an action and then dump the result to the screen so they can verify the code they're writing works as expected.<\/p>\n\n<p>The same could be done with a test.js file that uses a <code>console.log<\/code> to output to the console.<\/p>\n\n<p>The issue is that they are only valid at the time they were written and now the code has been written and been tested, the file is likely out of date and either won't or can't be run again.<\/p>\n\n<p>A better approach is to write tests using a framework like PHPUnit, Pest or Jest instead and to stop writing temporary test files.<\/p>\n\n<p>Automated tests contain the same arrange, act and assert steps, but they can be run repeatedly.<\/p>\n\n<p>They can be run by every other Developer in the team.<\/p>\n\n<p>They can be run automatically in a CI pipeline.<\/p>\n\n<p>They can be run for every future commit and push so you know that the functionality still works as it did when it was written.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3c945c89786eebbad100646cd316dfae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json b/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json
index 2ed39f095..0375ad3c5 100644
--- a/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json
+++ b/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Following last week's email on <a href=\"http:\/\/default\/daily\/2024\/01\/27\/gitignore-inclusive-or-exclusive\">different ways to write .gitignore files<\/a>, friend of the list, Daniel Harper, sent me this reply (shared with permission):<\/p>\n\n<blockquote>\n  <p>I had a debate once about this topic and we settled on ignore as the filename explicitly describes what it should be doing ie. It's not .gitallow \ud83d\ude06<\/p>\n<\/blockquote>\n\n<p>This is a good point.<\/p>\n\n<p>What do people expect to see in a <code>.gitignore<\/code> file?<\/p>\n\n<p>A list of directories and files to be ignored or allowed?<\/p>\n\n<p>Based on the filename, it should be the former.<\/p>\n\n<p>This would be clearer for people when they first open the file.<\/p>\n\n<p>However, if you decide to use the allow approach instead, document it in an <a href=\"http:\/\/default\/daily\/2022\/09\/23\/adrs-technical-design-documents\">ADR or design document<\/a> and why you decided to do it that way and provide context for people working on the codebase in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8c32951c32d678ca2fe6bac26a108dcb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json b/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json
index 91e604fc1..9387fb7b3 100644
--- a/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json
+++ b/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As someone <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">who has been using Tailwind CSS<\/a> since before 1.0, I'm looking forward to the next major version - Tailwind CSS v4.<\/p>\n\n<p>A main difference compared to previous versions is that it will be configured in CSS using CSS variables (aka custom properties).<\/p>\n\n<p>No more <code>tailwind.config.js<\/code> configuration files, just variables like <code>--color-blue-100<\/code>.<\/p>\n\n<p>As I <a href=\"http:\/\/default\/daily\/2024\/07\/15\/the-power-of-arbitrary-classes\">already use CSS variables in some situations<\/a>, I like that it will make it easier to re-use them within Tailwind and give a more consistent experience.<\/p>\n\n<p>As well as simple variables, such as colours and spacing, I'm interested to see how everything else will translate to the new configuration approach in Tailwind v4, as well as anything else new that will be included.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "38f60865df47fe3136bab0faff10ad7c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json b/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json
index de0c77c38..d61bc88cb 100644
--- a/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json
+++ b/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Over the last few days, I've written a few emails about static websites and static site generators before I <a href=\"http:\/\/default\/presentations\/sculpin\">speak about Sculpin<\/a> at PHP Thames Valley.<\/p>\n\n<p>They are <a href=\"http:\/\/default\/daily\/2025\/03\/12\/easy\">easy to build<\/a> and deploy and <a href=\"http:\/\/default\/daily\/2025\/03\/13\/deploy\">cheap to host<\/a>.<\/p>\n\n<p>As a PHP Developer, I use Sculpin as it uses Symfony components, is extendable by writing my own PHP code and uses Twig for templating.<\/p>\n\n<p>As a Drupal Developer, I like the power of Drupal's out of the box functionality and additional modules like Pathauto and Redirect, but I'd like to deploy it as a static website for it to be faster and more secure.<\/p>\n\n<p>Enter Tome, <a href=\"https:\/\/www.drupal.org\/project\/tome\">a Drupal module to create static websites<\/a>.<\/p>\n\n<p>You build the website the same as you would locally and export the content and files to a static website - the same you would generate with a static site generator like Sculpin or writing the files by hand.<\/p>\n\n<p>Sam Mortenson (the creator of Tome) and I discussed it on <a href=\"http:\/\/default\/podcast\/19-sam-mortenson\">episode 19 of the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>So, if you like Drupal and the benefits of static sites, Tome may be a good solution for you.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c2ab309fc48ad7634f3e37920943b3e3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json b/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json
index 5b8a4331c..9421fcf66 100644
--- a/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json
+++ b/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the common initial concerns of utility classes and Tailwind CSS is its maintainability.<\/p>\n\n<p>How you manage all the classes within the HTML and how easy is it to make changes?<\/p>\n\n<p>Today, <a href=\"https:\/\/twitter.com\/mauro_codes\/status\/1615726036737576960\">I saw this tweet<\/a>:<\/p>\n\n<blockquote>\n  <p>You can say whatever you want about @tailwindcss, but I just opened a legacy project with tailwind 0.7 that I didn't touch for almost three years... and I was able to update the whole branding in 30 minutes.<\/p>\n<\/blockquote>\n\n<p>One of my earliest Tailwind projects was the <a href=\"https:\/\/phpsw.uk\">PHP South West website<\/a>. We <a href=\"https:\/\/twitter.com\/opdavies\/status\/934488762276564993\">worked on this in November 2017<\/a> and it still uses Tailwind CSS 0.5.<\/p>\n\n<p>These are the classes used on the main menu:<\/p>\n\n<p><code>bg-grey-lightest hidden absolute z-20 w-full border border-grey-lighter sm:flex sm:relative sm:w-auto sm:border-none<\/code><\/p>\n\n<p>Even though Tailwind CSS is now on version 3.2.4, I can still read this and know exactly what the classes do, and I'm confident that I could easily make changes to this or any other element on the website.<\/p>\n\n<p>That probably isn't something that I could say for other projects that use different approaches to styling, and definitely an advantage of styling with small, reusable utility classes.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "75e1224b8adc36f5f0da6bcd13fc44d5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json b/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json
index 066101e5d..78433910b 100644
--- a/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json
+++ b/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>All software has bugs, but each has a different cost depending on when and where it's found.<\/p>\n\n<h2 id=\"in-production\">In production<\/h2>\n\n<p>If a bug was found in production, it was probably found by a user, will time to replicate, diagnose and fix, and could have caused some reputational or financial damage.<\/p>\n\n<p>You'd need to create a ticket and schedule the work, meaning you're not working on something else.<\/p>\n\n<p>Cost: High<\/p>\n\n<h2 id=\"in-a-pre-production-environment\">In a pre-production environment<\/h2>\n\n<p>It's likely found by a test analyst or product owner but hidden from the end users and customers.<\/p>\n\n<p>It will still take time to replicate, diagnose and fix, and you'd still need to create a ticket and schedule the work, as well as the bug potentially blocking releases to production until it's resolved.<\/p>\n\n<p>Cost: High<\/p>\n\n<h2 id=\"in-a-ci-pipeline\">In a CI pipeline<\/h2>\n\n<p>This is likely to be a static analysis or a test failure. It should be quicker to fix though it will need to be done quickly or reverted if you're doing trunk-based development to unblock other Developers.<\/p>\n\n<p>If you're doing code reviews, you'll need to ensure that the pipeline passes before the review and continues to pass after making any changes.<\/p>\n\n<p>Cost: Medium<\/p>\n\n<h2 id=\"locally\">Locally<\/h2>\n\n<p>If an automated check fails in CI, why not run it locally before you commit and push the change?<\/p>\n\n<p>If it's a coding standards issue or static analysis failure, you could configure your text editor or IDE to show you issues in real time. Then they can be fixed immediately and not even committed and pushed to a CI pipeline.<\/p>\n\n<p>If you were working in a pair or mob, could someone else have spotted the issue and suggested a fix?<\/p>\n\n<p>Cost: Low<\/p>\n\n<p>The sooner you can find a bug, the less time and cheaper it is to fix, and we can use tools like automated tests and static analysis to help us write fewer bugs and to fix them sooner and faster.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "144ff924864b048d704deeedcd9f2389",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json b/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json
index 42425c769..2c086c01c 100644
--- a/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json
+++ b/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal 8 was a major turning point for Drupal when it was released in 2015.<\/p>\n\n<p>Moving from \"not invented here\" to \"proudly found elsewhere\" and \"getting off the island\", Drupal 8 introduced Composer to Drupal core and several of the Symfony PHP components.<\/p>\n\n<p>Following Drupal 8's release, Drupal core started to follow semantic versioning and, six months later, released Drupal 8.1.0 with new features.<\/p>\n\n<p>In comparison, Drupal 7, with non-semantic versioning, is now on version 7.99.<\/p>\n\n<p>The approach to having fixed release dates instead of feature-based release dates is also used in Symfony, which makes it much easier to plan for.<\/p>\n\n<p>The differences between major versions, such as Drupal 9 and 10, is the removal of deprecated code - making it much easier than ever before to upgrade to the new major version of Drupal core. Sometimes, you won't need to update any custom code - especially if it's been maintained and updated during the minor releases.<\/p>\n\n<p>I've been pleased to see Symfony features such as autowiring and autoconfiguration start to be used within Drupal, as well as discussions around using PHP attributes to replace annotations and docblocks.<\/p>\n\n<p>Most recently, when writing my <a href=\"http:\/\/default\/atdc\">automated testing email course<\/a>, I saw a number of aliases have been added to core's <code>core.services.yml<\/code> file, which means I can use the fully qualified class name as the service name without adding aliases to my own services files.<\/p>\n\n<p>Drupal and Symfony are separate projects, and Drupal uses more than just Symfony components, but as someone who uses Drupal and Symfony, I'm happy to see them learning from and inspiring each other.<\/p>\n\n<p>I'm looking forward to seeing the next thing - <a href=\"http:\/\/default\/podcast\/10-ryan-weaver-symfonycasts\">Twig components<\/a>, maybe - in Drupal.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c855be3a314644488f7547bb4b62da5c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json b/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json
index 1adee0c1d..a15c781ce 100644
--- a/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json
+++ b/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As Drupal 11 uses PHPUnit 10, we can now use the <code>#[Test]<\/code> attribute instead of the <code>\/** @test *\/<\/code> annotation for our test methods.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"php\">\/\/ Before.\n\n\/** @test *\/\npublic function it_returns_the_endpoint()\n\n\/\/ After.\n\n#[Test]\npublic function it_returns_the_endpoint()\n<\/code><\/pre>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/04\/04\/php-attributes--coming-soon-to-a-drupal-version-near-you\">Annotations have started to be replaced<\/a> in parts of Drupal since 10.2, so it's nice to be able to do it with tests, too.<\/p>\n\n<p>Which do you prefer?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "302417948921bd4d3e2cf53132a91a19",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json b/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json
index 3b0ac034e..b8ad15ddf 100644
--- a/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json
+++ b/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal distributions are pre-built versions of Drupal for specific use cases.<\/p>\n\n<p>Need an eCommerce store? Use Commerce Kickstart.<\/p>\n\n<p>Are you a local council looking for a new website? Look at LocalGov Drupal.<\/p>\n\n<p>Contenta CMS is an API-first Drupal distribution for headless and decoupled content.<\/p>\n\n<p>There are numerous others - each containing a list of pre-installed and configured modules to give you more functionality out of the box.<\/p>\n\n<p>If you're starting a new project, try starting with an appropriate distribution instead of starting from scratch with a standard installation of Drupal core and save yourself time and effort.<\/p>\n\n<p>Don't know if using a distribution could help for you? <a href=\"http:\/\/default\/call\">Book a 1-on-1 consulting call<\/a>, and I'll help you out.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0985c190c212466315018728f90d1b46",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json b/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json
index 94e2c3bda..9b2c370a8 100644
--- a/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json
+++ b/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Now <a href=\"http:\/\/default\/daily\/2024\/06\/23\/drupal-10-3-released\">Drupal 10.3 has been released<\/a>, and <a href=\"http:\/\/default\/daily\/2024\/06\/29\/countdown-to-drupal-11\">websites need to be updated to 10.3 before Drupal 11<\/a>, it's time to start updating your Drupal 10 websites.<\/p>\n\n<p>Luckily, with Composer, upgrading is one simple command.<\/p>\n\n<p>There's no need to download .tar.gz or .zip files or update version numbers in a Drush Make file any more.<\/p>\n\n<p>If you want to update everything, a simple <code>composer update<\/code> will do.<\/p>\n\n<p>If you want to only update Drupal core, then you'll need to run something like <code>composer update drupal\/core<\/code> or <code>composer update drupal\/core-*<\/code>, or something slightly different if you're using a distribution like Commerce Kickstart or LocalGov Drupal.<\/p>\n\n<p>I think adopting Composer was one of the best decisions the Drupal project made - not only <a href=\"http:\/\/default\/daily\/2024\/06\/09\/proudly-found-elsewhere\">to include third-party code<\/a>, such as Symfony components, but it also makes applications so much easier to update.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "26e535d4da7da307150526e7fbbdabe2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a564439d-3102-47dc-8f4b-70b080383552.json b/content/node.a564439d-3102-47dc-8f4b-70b080383552.json
index e094ed89d..0c98fd16f 100644
--- a/content/node.a564439d-3102-47dc-8f4b-70b080383552.json
+++ b/content/node.a564439d-3102-47dc-8f4b-70b080383552.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There's only one year before support for Drupal 7 support ends, but there are still more than 337,000 Drupal 7 websites, according to <a href=\"https:\/\/www.drupal.org\/project\/usage\/drupal\">https:\/\/www.drupal.org\/project\/usage\/drupal<\/a>.<\/p>\n\n<p>Even though there's a year left, if you've got a Drupal 7 website, you need to start upgrading now!<\/p>\n\n<p>Unlike upgrading from Drupal 8 to 9 or 9 to 10, upgrading from Drupal 7 requires major changes to your code for it to be compatible. This will take time to do and test.<\/p>\n\n<p>Most websites have some or many custom modules and at least one custom theme that must be upgraded.<\/p>\n\n<p>Most use a large number of community-contributed modules.<\/p>\n\n<p>Many of these are abandoned or minimally maintained as their maintainers have focused on newer Drupal versions or a module has been marked as unsupported in favour of another.<\/p>\n\n<p>If they do have supported versions, it is likely that they haven't had a release for some time. If that's the case, they're essentially unsupported.<\/p>\n\n<p>Because of this, there may not be the same modules available with the same functionality for Drupal 10.<\/p>\n\n<p>Depending on the available modules, your functionality may need to change, or the old functionality will need to be written within a new custom module.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Depending on the complexity, it will take a number of months to complete an upgrade.<\/p>\n\n<p>Rather than wait until 2025, you want to do the work now whilst Drupal 7 is still supported rather than waiting and being vulnerable to security exploits if running an outdated and unsupported version.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9d62f0394c3edfda3c7091efc05827b8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json b/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json
index 3c046bbe2..e78c86661 100644
--- a/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json
+++ b/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In this week's Beyond Blocks podcast episode, I spoke to <a href=\"https:\/\/x.com\/jessarchercodes\">Jess Archer<\/a> - Engineering Team Lead at Laravel.<\/p>\n\n<p>We discuss Laravel Prompts which was released at Laracon US last year and added to Drush 13, but also about PHP, Laravel, Neovim, working in the terminal and bullet journaling.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/25-jess-archer-drush-laravel-prompts\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "69a24b089347581b24758ee7c7f6d739",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json b/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json
index 52c647467..d92a14934 100644
--- a/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json
+++ b/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've worked on many software projects with a lot of custom code.<\/p>\n\n<p>Not all the code is specific to that client or project, and often, code is identified as it can be extracted from the project and open-sourced as a Drupal module, PHP or JavaScript library, or Tailwind CSS plugin.<\/p>\n\n<p>Usually, the code is written as custom code initially, with the best intentions to revisit it once the project is complete and open-source it.<\/p>\n\n<p>But this rarely happens, as there's always the next sprint or project waiting.<\/p>\n\n<p>It takes too long to extract the code as it usually needs to be tidied or refactored beforehand.<\/p>\n\n<p>It may have been written with the client or project name within the code, which needs changing.<\/p>\n\n<p>My suggestion is to avoid this step.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Instead of writing it as custom code and hopefully extracting it later, start it as a separate module, library or plugin, and use Composer or npm to add it to your project as another dependency.<\/p>\n\n<p>Whilst it's a slightly smaller overhead, it's better and less risky than rewriting or refactoring code later and it's already open-sourced.<\/p>\n\n<p>Plus, you may get some issues, testing and improvements from others along the way.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1489f86d52518013ecedf7b402c2c07e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json b/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json
index cdad0f30b..78c51ff81 100644
--- a/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json
+++ b/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you're performing a task as there's already a convention on how to do it, stick to it.<\/p>\n\n<p>If the codebase follows a particular coding standard, use it.<\/p>\n\n<p>If a project uses repository classes instead of interacting directly with a database, do that with your code too.<\/p>\n\n<p>If you use a framework with a service container and uses dependency injection, do that instead of manually creating classes.<\/p>\n\n<p>If you need additional functionality for a Drupal project and there's an established and well-known module that adds it, use it. Unless it doesn't meet your needs, in which case, document why that's the case and why you used a different module or wrote a custom implementation.<\/p>\n\n<p>If you need to create a content listing page, use the Views module, which is a standard approach. If not, document why and then explore other solutions.<\/p>\n\n<p>If you don't follow a convention, it will be harder for you or others to work on it in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6450282a1b4fe2e23ac91ffacb7cd5c1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json b/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json
index 8e9b91b3b..52fad2f8e 100644
--- a/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json
+++ b/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've maintained the Override Node Options module for Drupal since early 2012.<\/p>\n\n<p>I've maintained the Drupal 7 version and written new versions for Drupal 8 onwards.<\/p>\n\n<p>At the time of writing, the module is used on at least 36,244 active Drupal websites.<\/p>\n\n<p>I don't want to break 36,000 websites, and automated testing is my way of avoiding that.<\/p>\n\n<p>I have three examples of how automated testing helped me when working on this module.<\/p>\n\n<h2 id=\"upgrading-to-drupal-8\">Upgrading to Drupal 8<\/h2>\n\n<p>When writing the initial Drupal 8 version of the module, as I started re-writing a feature, the first thing I did was recreate the tests from the Drupal 7 version.<\/p>\n\n<p>Then, I followed a test-driven development approach to get the test passing using the Drupal 7 code for reference.<\/p>\n\n<p>When the whole test suite was in place and passing, I knew there was feature parity between the two versions.<\/p>\n\n<h2 id=\"resolving-a-large-merge-conflict\">Resolving a large merge conflict<\/h2>\n\n<p>I was reviewing a feature request that had been open for some time, which included a large patch file with the code changes to implement it.<\/p>\n\n<p>However, the patch no longer applied to the code, which caused various merge conflicts.<\/p>\n\n<p>There were no additional tests within the patch, but I was able to use the existing tests to ensure the original functionality worked once the merge conflicts were resolved and there were no regressions caused by committing the patch.<\/p>\n\n<p>I did later add tests for the new functionality, but without the original test suite, I would have likely not have accepted the patch and not committed the feature.<\/p>\n\n<h2 id=\"refactoring-the-code\">Refactoring the code<\/h2>\n\n<p>A few years ago, a colleague and I wanted to refactor the module code to make it more maintainable and easier to work on.<\/p>\n\n<p>Then, the module was used on around 30,000 websites, so this could have been risky.<\/p>\n\n<p>However, we had the test suite to ensure the functionality still worked and that our refactors were successful.<\/p>\n\n<p>If we broke something and introduced a regression, a test would fail, and we could fix it.<\/p>\n\n<p>Following the release containing the refactored code, there were no reported issues or regressions from the community.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Automated testing is about providing confidence.<\/p>\n\n<p>Confidence the software works as expected and is releasable, either to clients for custom software or consumers of open-source software.<\/p>\n\n<p>With a passing test suite, you can add and change code with confidence and without worrying about breaking it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "29be860248a883db12a44b89149e1392",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json b/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json
index 1f9a2162c..2cff75123 100644
--- a/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json
+++ b/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as my recent session at PHP South Wales, I've also been involved with a lot more mob programming recently with members of my team.<\/p>\n\n<p>We recently added a new feature to our codebase that we completed over a couple of mob sessions - starting by describing the problem and some potential solutions within a <a href=\"http:\/\/default\/daily\/2022\/09\/23\/adrs-technical-design-documents\">technical design document<\/a> before moving on to the implementation.<\/p>\n\n<p>I was already familiar with the existing code that we needed to extend, so had some ideas of how to approach parts of the solution which we discussed - but there were other parts that I hadn't thought of.<\/p>\n\n<p>What was very interesting was that an approach was suggested that I probably wouldn't have thought of myself, which become part of the final solution. This is an advantage of pair programming and is multiplied when working in groups - that you get to include everyone's thoughts, experience and perspective, and collectively decide on the best approach to take in real-time.<\/p>\n\n<p>As a side effect, we had continuous code review from members of the group, and if we need to work on this code again in the future, everyone will already be familiar with it.<\/p>\n\n<p>As it was already reviewed, we didn't need to wait before pushing the feature to production so it was delivered quickly and providing value by fixing an issue that someone was experiencing.<\/p>\n\n<p>We're already working on the next feature as a group, and if you haven't tried pair or mob programming before, I'd recommend that you give it a try.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "062a427093fb899d8a3761083c1927f4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json b/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json
index 743c33af8..cf72aa113 100644
--- a/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json
+++ b/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Are you unsure what task to start with tomorrow?<\/p>\n\n<p>Do you sometimes forget where you were in a task after taking a break or the start of a new workday or week?<\/p>\n\n<p>If you write a failing test, you can run your test suite and be find out what you were doing and know your next step.<\/p>\n\n<p>Get that test to pass.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c3643649d3f3d1af84fc1912e1eefae4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json b/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json
index 9ed1c50ac..e4e89ef41 100644
--- a/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json
+++ b/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since first setting it first during Simon Vrachliotis' workshops, I've started evaluating <a href=\"https:\/\/astro.build\">Astro<\/a> as an option for building static websites alongside PHP options like Sculpin and Jigsaw, and used it to rebuild <a href=\"https:\/\/www.oliverdavies.uk\">my personal website<\/a>.<\/p>\n\n<p>As well as being a good opportunity to get more experience with JavaScript, TypeScript and JSX templating, Astro includes a number of features that were useful for my website, such as code syntax highlighting and markdown support out of the box, as well as integrations to set up Tailwind CSS, sitemaps and images that I needed.<\/p>\n\n<p>Its file-based routing is very familiar to what I'd been working with in Next.js, including dynamic and nested routes such as my Blog, Talks, and email archive pages.<\/p>\n\n<p>A static HTML version of the site can be generated which can be uploaded to a web server - like with other static site generators - with the advantage that Astro includes no JavaScript by default.<\/p>\n\n<p>As well as my personal website, I've been using Astro for some other mini-projects including <a href=\"http:\/\/default\/daily\/2023\/01\/22\/building-bootstrap-css-examples-with-tailwind\">building Bootstrap components with Tailwind<\/a>, and I'm using it for the updated examples for my Tailwind CSS talk at nor(DEV):con in a couple of weeks time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b7a974fdb8e406115add89a29605c35c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json b/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json
index 5d4490018..8c823c833 100644
--- a/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json
+++ b/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently listened to a podcast that discussed Elon Musk and quoted something like, \"If 20% of attempts aren't failing, you aren't taking enough risk\".<\/p>\n\n<p>In a software context, I'm not advocating that one in five production releases should fail, but I like trying new ideas and approaches.<\/p>\n\n<p>If you're releasing small changes regularly or practising continuous deployment, changes are easy to revert if there's a problem or the smaller the deployment and the more recently the code was written, then it should be easier to resolve the issue and \"fix forward\" instead of rolling back.<\/p>\n\n<p>Using feature flags lets you quickly turn off a feature flag while investigating and resolving the issue without needing another deployment.<\/p>\n\n<p>If you have an appropriate plan to follow in the case of an issue, that mitigates the risk and minimises the impact of a potential issue - making it quicker to resolve and restore the service.<\/p>\n\n<p>Two of the DORA metrics refer to failure rate and restoration time:<\/p>\n\n<ul>\n<li>Deployment frequency<\/li>\n<li>Lead time for changes<\/li>\n<li>Change failure rate<\/li>\n<li>Time to restore service<\/li>\n<\/ul>\n\n<p>Then, it depends on your organisation's tolerance for risk and what's acceptable.<\/p>\n\n<p>But, the more frequent the releases, the lower the failure rate and the quicker it will be to restore the service if there is an issue.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2a2b5c587a4d8d90d889a8595926719e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json b/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json
index d07b0cd95..1081161af 100644
--- a/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json
+++ b/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been using the Nix package manager for some time.<\/p>\n\n<p>The first commit of a flake.nix file to my <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/nix-config\">nixos-config repository<\/a> (formerly my dotfiles repository) was on the 26th of September 2022.<\/p>\n\n<p>The following month, I started to experiment with NixOS - the operating system built on the Nix language and the package manager.<\/p>\n\n<p>Rarely have I found a package missing within the 120,000+ available, but I have added some missing Vim plugins and some custom packages to my own configuration.<\/p>\n\n<p>But I hadn't tried to contribute any package definitions back to nixpkgs until today.<\/p>\n\n<p>I've submitted <a href=\"https:\/\/github.com\/NixOS\/nixpkgs\/pull\/395028\">my first pull request to nixpkgs<\/a> to add a small script that I've added to my own configuration.<\/p>\n\n<p>It's always nerve-racking contributing to a new projects, but let's see how it goes.<\/p>\n\n<p>I'm thinking of it as <a href=\"http:\/\/default\/daily\/2024\/05\/14\/free-code-reviews\">a free code review<\/a>.<\/p>\n\n<p>If it goes well, I can see me contributing more packages in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0e6a565b98631d7f71c7e8d4d68d0d26",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json b/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json
index 2386a31aa..d85fc2aa4 100644
--- a/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json
+++ b/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Listening to podcasts and watching videos where Developers talk about their personal or side projects, sometimes they say that they skip writing automated tests.<\/p>\n\n<p>They'd write tests for their client or work projects, but not necessarily for their own projects.<\/p>\n\n<p>I wonder why this is.<\/p>\n\n<p>Presumably they see the benefits of testing on other projects, so why wouldn't they write tests for their own projects?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5b75b1651825917b5ebfb2b16179254d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json b/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json
index 6d2876073..d9e7dd401 100644
--- a/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json
+++ b/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As I said in <a href=\"http:\/\/default\/daily\/2023\/12\/08\/dont-just-rewrite\">yesterday's email<\/a>, I'm discussing with a team how to implement their new website design.<\/p>\n\n<p>Their website has been live for a couple of years, and now they want to refresh its look and feel.<\/p>\n\n<p>The current theme includes a lot of technical debt and legacy code, such as using an older CSS framework and build tools that need unsupported versions of packages to compile it and generate the scripts and stylesheets.<\/p>\n\n<p>There are two ways they could approach this:<\/p>\n\n<p>They could continue to iterate on the current theme, making and releasing small changes to move forward in small steps and slowly repaying the technical debt.<\/p>\n\n<p>Alternatively, they could create a new theme from scratch.<\/p>\n\n<p>This would allow them to start with new build tools, a modern CSS framework and small and simple stylesheets.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>There are advantages and disadvantages to both approaches.<\/p>\n\n<p>Iterating on the original theme allows for continuous improvement, but it would take longer to remove the old frameworks and build tools - if that would be possible at all.<\/p>\n\n<p>Rebuilding and re-inventing would mean immediately avoiding the technical debt and legacy tools, but it comes with its own risks, and you'd need to wait until the whole theme was completed before it could be launched.<\/p>\n\n<p>There isn't a right and wrong answer, and it will depend on the thoughts and objectives of the team and business.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6e14d379a00279e23ff3a43b65e78390",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json b/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json
index bd2759d63..fa7cd03af 100644
--- a/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json
+++ b/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the significant changes that I've found and that's benefitted me whilst developing is to commit and push something every day.<\/p>\n\n<p>It doesn't need to be a whole feature. It could be a new class with its passing tests, but it isn't used anywhere yet, so it won't affect the existing functionality, or it could be a new test for some existing functionality that was missing previously.<\/p>\n\n<p>It could be a small refactor - renaming a variable or class name that makes some code easier to read or removing some commented-out code that isn't doing anything other than adding visual clutter.<\/p>\n\n<p>It could be updating some documentation or <a href=\"http:\/\/default\/daily\/2022\/09\/23\/adrs-technical-design-documents\">writing a technical document<\/a>; if you keep those in your version control repository, that would help you implement the following change or to make the documentation clearer for the next reader - whether that's you or someone else.<\/p>\n\n<p>Committing something at least once a day creates a different mindset to \"I'll write everything and push it when it's done\".<\/p>\n\n<p>It makes you break up large tasks into multiple smaller ones and set mini-deadlines for yourself. I used to do the same when I commuted to work on a train and had a task for a freelance project to complete before I arrived. I used to think, \"What can I start, finish and commit before I get there?\" instead of leaving something incomplete.<\/p>\n\n<p>You don't need to push your change to mainline. If you use the <a href=\"http:\/\/default\/daily\/2022\/11\/30\/ship-show-or-ask\">\"Ship, Show, Ask\" approach<\/a> then you could commit to a temporary branch that you either merge yourself once you know it passes the checks, or to show or get feedback from other team members.<\/p>\n\n<p>Practicing this becomes a habit, and if you're doing test-driven development and committing after every passing test or refactor, you'll find yourself pushing numerous changes a day.<\/p>\n\n<p>This became my normal approach instead of having long-lived feature branches or lots of unpushed local commits.<\/p>\n\n<p>I much prefer making as small charges as possible and pushing them as often as I can.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e26c9b7ab7102d2ec454810073cf9ab4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json b/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json
index 7f3e7d2f8..ec0917d43 100644
--- a/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json
+++ b/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A common response I get when debating topic branches is \"I regularly pull <code>develop<\/code> or <code>main<\/code> and get the latest changes.<\/p>\n\n<p>But if everyone is working on individual topic branches instead of the mainline branch, where do the changes come from?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "27ff386b427be3114468f0a592aa2363",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json b/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json
index e2aa5aa70..0b139a515 100644
--- a/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json
+++ b/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As a solo Developer and Consultant, I rely a lot on automation to get my tasks done.<\/p>\n\n<p>I use tools like <a href=\"http:\/\/default\/daily\/2023\/03\/09\/in-what-language-should-i-write-my-automation\">Pulumi, Ansible and Terraform<\/a> to automate creating and configuring infrastructure - recently creating new client GitHub repositories using a standard configuration with Pulumi.<\/p>\n\n<p>I use Nix and Home Manager to automate my local development environment, install packages I need and create files like <code>.gitconfig<\/code> for my needs. These are reusable and stored in my <a href=\"https:\/\/github.com\/opdavies\/dotfiles\">dotfiles<\/a> repository.<\/p>\n\n<p>For projects, I use tools like Docker, Docker Compose and Nix flakes for consistency.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2023\/03\/04\/why-i-built-a-tool-to-generate-configuration-files\">I wrote a tool for generating configuration files for each project<\/a> - reducing the time it takes me to set up, configure and maintain standard files for tools like Docker and Docker Compose that I always use. If I need to add a new feature or fix a bug in a configuration file, I can do that in my templated version and re-generate each project's files rather than making the same change manually.<\/p>\n\n<p>Today, I wrote a script that loops over all projects where I commit those files to GitHub, clones a fresh version of it, re-generates the files and pushes any new files or changes back to the repository. This means that any changes will be automatically applied and all of my projects will remain in sync.<\/p>\n\n<p>Automating all of these things reduces the time that I need to spend on them - allowing me to focus on delivering value and solving problems for my clients.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5d675721f871790eee2c4073770babdd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json b/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json
index af54d9cac..a02f82920 100644
--- a/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json
+++ b/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I've seen, both with contributed Drupal modules and other open-source projects, over the past few years is they spend a lot of time in the 0.x versions or releasing alpha and beta versions rather than releasing a 1.0 or stable version.<\/p>\n\n<p>I presume it's a concern around backward compatibility and maintaining that once a stable version is released.<\/p>\n\n<p>But, if you want people to use your module or upgrade it to the latest version, that's much easier to do once there's a stable version.<\/p>\n\n<p>Some organisations prohibit using alpha or unstable versions of projects so, if there isn't a stable version, they wouldn't be able to use it.<\/p>\n\n<p>Personally, if I'm using one of my open-source modules, plugins or libraries in production, there should be a stable 1.0 version tagged.<\/p>\n\n<p>Once it's in production, I'm already making an implied commitment that it's going to be stable and I won't break everything in the next release, so why not make that explicit and tag a stable release?<\/p>\n\n<p>Version numbers are free and nothing is stopping you from deprecating code and releasing a new major version with breaking changes in the future, so go ahead and tag that stable version.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2a53a326fece4691a606a104cf3ec76c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json b/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json
index 24f7ab533..2087ace94 100644
--- a/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json
+++ b/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whether it's writing code or a technical design document, diagnosing an issue, or working on a blog post or a presentation deck, sometimes, the hardest part for me is getting started.<\/p>\n\n<p>When this happens, I try to find the smallest thing I can do to start the task and get the ball rolling.<\/p>\n\n<p>This could be just opening Neovim or Notion and finding the smallest task I can do to get going.<\/p>\n\n<p>In code, it could be making the smallest change to start on the task or committing a small refactoring on another part of the code to get into the flow.<\/p>\n\n<p>With a technical design document, once I've written the first heading, \"What problem are we trying to solve?\" and started to describe the problem, it's easy to continue writing the rest of the document.<\/p>\n\n<p>For a blog post or presentation, I've found that writing the headings first is a good starting point, adds structure and makes it easier to add the main content.<\/p>\n\n<p>Things are great once the ball is rolling; the question sometimes is, \"what is the simplest thing I can do to start it?\".<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5cafd2e757ac9170c91b0e8184d0ee39",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json b/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json
index f84138d2b..a1508194f 100644
--- a/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json
+++ b/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After recently speaking at a PHP user group, I've been invited to be a guest speaker and speak to a group of students at Reading College.<\/p>\n\n<p>It will be a group of around 40 students who are currently studying Computing and IT with a current focus on web development.<\/p>\n\n<p>I'm planning to speak about my background in both hardware and software, how I started in software development and with open source, and some of the opportunities that I've had from that, including work opportunities, public speaking and mentoring.<\/p>\n\n<p>I'm also going to talk about the hobby side of computing for me - using ThinkPad laptops, Linux and managing a homelab and home server, which I think will be interesting and relevant to a group of Computing and IT students.<\/p>\n\n<p>I have a two hour slot, which I'm sure it will involve some demos, live coding and group programming, which usually happens when I'm giving presentations.<\/p>\n\n<p>This will be a bit different to all the talks and workshops I've done so far, but I'm looking forward to it and I'm sure will be open to doing similar presentations in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "745510ed0044be6758cbc74729ab3d08",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json b/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json
index 85e5636b8..6eed1b1e2 100644
--- a/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json
+++ b/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/02\/07\/running-tests-in-parallel-with-paratest\">In yesterday's email<\/a>, I mentioned parallel testing and speeding up your tests by running them in parallel.<\/p>\n\n<p>Something else I've been experimenting with recently in architectural testing with PHPat.<\/p>\n\n<p>For example, ensuring classes within a namespace are <code>final<\/code> or not, that Controller classes all extend <code>ControllerBase<\/code> and have the Controller suffix in their names.<\/p>\n\n<p>Going forward, I'd like to ensure that each Drupal module only uses its own classes and is separated, as I recently had an issue where I deleted a class method in one module only to find it was used in a different module.<\/p>\n\n<p>Here's what I have so far for my <a href=\"http:\/\/default\/atdc\">testing course codebase<\/a>:<\/p>\n\n<pre><code class=\"language-php\">final class ArchitectureTest {\n\n  public function test_classes_should_be_final(): Rule {\n  return PHPat::rule()\n    -&gt;classes(Selector::inNamespace('Drupal\\atdc'))\n    -&gt;shouldBeFinal();\n  }\n\n  public function test_controllers_should_extend_ControllerBase(): Rule {\n  return PHPat::rule()\n    -&gt;classes(Selector::inNamespace('Drupal\\atdc\\Controller'))\n    -&gt;shouldExtend()\n    -&gt;classes(Selector::classname(ControllerBase::class));\n  }\n\n  public function test_controllers_should_have_the_Controller_suffix(): Rule {\n  return PHPat::rule()\n    -&gt;classes(Selector::inNamespace('Drupal\\atdc\\Controller'))\n    -&gt;shouldBeNamed(\n      classname: '\/Controller$\/',\n      regex: TRUE,\n    );\n  }\n\n}\n<\/code><\/pre>\n\n<p>I plan to continue expanding this configuration as I become more familiar with PHPat, and because it's a PHPStan extension, it's already available to run within my projects locally and within the CI pipeline.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "455ff869c592cdd12244b2264b5b2dff",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json b/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json
index ddb681ef7..75f965ce4 100644
--- a/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json
+++ b/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If it looks like a duck, walks like a duck, and quacks like a duck, it must be a duck.<\/p>\n\n<p>If I pass a parameter into a function, as long as it works with the code within the function - it is of the correct type and has the expected properties and methods - it will work, although nothing is enforcing that the correct thing is passed in.<\/p>\n\n<p>If not, you'd get an error that the method or property doesn't exist when trying to invoke or access it.<\/p>\n\n<p>This is the opposite of strict typing, where you'd get a Type error if you passed the wrong thing.<\/p>\n\n<p>Both are valid approaches, though I prefer to use types and get specific error messages and leverage tools like static analysis, which work better the more it understands your code.<\/p>\n\n<p>In particular when writing and using open-source code that anyone can use however they like, I'd suggest leveraging types and type-checking, but it depends on what you, your team or your community prefer.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4880370cb27dce1a6abccc2c014baeae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json b/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json
index 72c874523..9ebcedca8 100644
--- a/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json
+++ b/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I heard this on a non-tech podcast but it applies to tech too:<\/p>\n\n<blockquote>\n  <p>It's only a bad situation if you fail to learn from it<\/p>\n<\/blockquote>\n\n<p>Whether its a missed deadline, a failed deployment, a production outage or pushing a bug to production, there are opportunities to learn and improve.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1d08162ec930721f889a571b47fde853",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json b/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json
index 8ebf0b4f1..d5ba786da 100644
--- a/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json
+++ b/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After <a href=\"http:\/\/default\/daily\/2024\/03\/27\/hotfixing-without-branches\">Wednesday's email<\/a>, someone said, \"It sounds like you and I use git very differently.\" So, I wanted to explain what my typical Git workflow is.<\/p>\n\n<p>I used to use Git Flow, but now, I almost never create a new branch when starting a new task.<\/p>\n\n<p>I keep my workflow as simple as possible by using trunk-based development and working on a single branch as much as I can.<\/p>\n\n<p>Before I start, I make sure any uncommitted changes are committed or reset and that the automated tests, static analysis, coding standards checks, etc., are passing so I know I'm starting from a good place.<\/p>\n\n<p>Then, I start working on the task.<\/p>\n\n<p>I like to work in small steps and make small, regular commits, but I don't always push each individual commit to the remote repository.<\/p>\n\n<p>Sometimes, I'll make a number of \"work in progress\" commits and squash them into one before pushing them.<\/p>\n\n<p>I want the time between making and pushing the commit to be as short as possible, and I want each commit to be deployable.<\/p>\n\n<p>If I'm doing test-driven development, I'll typically commit each time a test is passing - whether it's adding a new test or extending one.<\/p>\n\n<p>I run any tests often whilst writing code to ensure they pass, either using a watch command or a keybinding in Neovim.<\/p>\n\n<p>I won't push a commit that would cause the code to not work, a test to fail, or block any other (potentially more urgent) changes from being pushed to production.<\/p>\n\n<p>If I push a commit that breaks the CI pipeline, I'll fix it quickly, which is usually possible as the changes are small.<\/p>\n\n<p>If not, I'll revert the commit to get back to a deployable state as quickly as possible.<\/p>\n\n<p>If I'm going to add a feature flag, I'll usually know that in advance and avoid rushing to add one later if a more urgent task comes in.<\/p>\n\n<p>By keeping each commit in a working and deployable state, a change can be feature flagged and deployed but not activated until the feature flag is enabled.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1fdb0bb1e22238ec9d831d2b2a3af864",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json b/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json
index 855d3fd95..52ca45d93 100644
--- a/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json
+++ b/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are many good resources and interesting articles online about how to write good messages when committing changes to a Git repository.<\/p>\n\n<p>The post I often refer to is <a href=\"https:\/\/cbea.ms\/git-commit\">How to Write a Git Commit Message<\/a> by Chris Beams.<\/p>\n\n<p>In his post, he explains why good commit messages matter and gives these seven rules:<\/p>\n\n<blockquote>\n  <ul>\n  <li>Separate the subject from body with a blank line.<\/li>\n  <li>Limit the subject line to 50 characters.<\/li>\n  <li>Capitalize the subject line.<\/li>\n  <li>Do not end the subject line with a period.<\/li>\n  <li>Use the imperative mood in the subject line.<\/li>\n  <li>Wrap the body at 72 characters.<\/li>\n  <li>Use the body to explain what and why vs. how.<\/li>\n  <\/ul>\n<\/blockquote>\n\n<p>I'd recommend reading the article to get the full context.<\/p>\n\n<p>Rules two and six suggest lengths for the subject line and body which is another reason <a href=\"http:\/\/default\/daily\/2025\/04\/02\/commit\">why I rarely use <code>-m<\/code><\/a> when committing changes.<\/p>\n\n<p>Whilst you can create multi-line commit messages on the command line, by opening it in my preferred editor (Neovim for me), I can see where the lines should end and be warned if I exceed them.<\/p>\n\n<p>I can even include Chris' rules in my commit message template so I see them whenever I'm about to commit something.<\/p>\n\n<p>This additional feedback helps me create my commit messages how I intend.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7430242f1d716198aa6fb01f727d1f9a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json b/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json
index 7d82ab2a6..3ee53aaa6 100644
--- a/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json
+++ b/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since <a href=\"http:\/\/default\/blog\/going-full-vim\">July 2021<\/a>, I've used Neovim full-time for my development work and writing.<\/p>\n\n<p>Whilst Vim and Neovim are minimal by default, its functionality can be extended by adding plugins.<\/p>\n\n<p>I use nvim-lspconfig along with Intelephpense and Phpactor to add code actions and functionality like \"go to definition\" for PHP code.<\/p>\n\n<p>I use null-ls to apply code formatting and add diagnostic messages for PHPCS and PHPStan so I can see them on the appropriate lines.<\/p>\n\n<p>I use nvim-dap and nvim-dap-ui to leverage the debug adapter protocol to do step debugging with Xdebug.<\/p>\n\n<p>Along with others like dadbod.vim for databases, rest.nvim for making HTTP requests, Gitsigns and Fugitive for Git, and Telescope for fuzzy searching, I have all of the functionality that I've previously had in other browsers with the benefit that it's open source and I can add more plugins or write my own if I need to add anything else.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dec79bc6053758566e617ed059c1fc37",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json b/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json
index ac3cbf7cf..49a0bee7d 100644
--- a/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json
+++ b/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently been helping my son to learn to code in Python.<\/p>\n\n<p>I've also bought a portable scanner so I can scan documents and add them to Paperless which is <a href=\"http:\/\/default\/daily\/2024\/12\/01\/homelabbing-with-nixos\">running on my homelab<\/a>.<\/p>\n\n<p>I've been explaining to my son why he needs to read the error messages to understand why something isn't working, such as a syntax error or an undefined variable.<\/p>\n\n<p>After plugging in my scanner and wondering why it wasn't showing in the gscan2pdf application, I found a switch to toggle an auto start setting.<\/p>\n\n<p>If auto start is enabled, the scanner only works with its own software.<\/p>\n\n<p>Once I disabled it, the scanner appeared.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Both of these situations were solved by doing the same thing.<\/p>\n\n<p>RTFM.<\/p>\n\n<p>Reading The \"Friendly\" Manual.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6a9ee2d1506c2929307940f3c4d71d0f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json b/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json
index 7c6817aca..263d4a4f9 100644
--- a/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json
+++ b/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was reading a Twitter thread recently that <a href=\"https:\/\/twitter.com\/allenholub\/status\/1594786089994067969\">started with this tweet<\/a>.<\/p>\n\n<p>TL;DR:<\/p>\n\n<blockquote>\n  <p>\"Measuring output (e.g. velocity) is a waste of time. It's outcomes you care about - customer happiness.\"<\/p>\n<\/blockquote>\n\n<p>This is definitely something that I agree with.<\/p>\n\n<p>I can't remember the last time I looked at an output burndown chart or a velocity score.<\/p>\n\n<p>I'd rather focus on what outcomes have been delivered and adding value to clients and customers.<\/p>\n\n<p>What features did we release, what bugs did we fix, and what impact and value did that provide?<\/p>\n\n<p>What increased revenue or improved a customer's experience?<\/p>\n\n<p>I may have a sprint or cycle where I only deliver one or two large tasks, but those are major features that have been requested, a bug affecting a user's experience, or a task that unblocks future tasks.<\/p>\n\n<p>In that situation, my velocity may not be good and could be improved by working on multiple smaller tasks, but which outcomes provide the most value?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ead1c8b01bd5cd04cfb3c0a1d516473b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json b/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json
index c449c1cfa..5e28227a9 100644
--- a/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json
+++ b/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When doing test-driven development, you start by writing a failing test and then write the code to make it pass.<\/p>\n\n<p>This is the design phase where you ask questions and decide how you want the code to work.<\/p>\n\n<ul>\n<li>Are you going to use a global function or a method on a class?<\/li>\n<li>Will you create a new class or add a method to an existing class?<\/li>\n<li>What will it be called?<\/li>\n<li>Will you use a named method or make the class invokable like a single-method Controller or Action?<\/li>\n<li>Will it accept any parameters?<\/li>\n<li>If so, what will the parameters be, what will they be named, and will they take any default values?<\/li>\n<li>Will it return a value?<\/li>\n<li>Should it throw an Exception?<\/li>\n<\/ul>\n\n<p>You might iterate on the design and change it as you write more assertions or tests, but take the opportunity to decide how you want the code to work at this point before you start writing the implementation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3f5e1ce616fb6f602be9eb2c287dc4b3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ac349786-bc86-465d-9374-a277d15a892c.json b/content/node.ac349786-bc86-465d-9374-a277d15a892c.json
index ac21dc2cd..5fcb0af19 100644
--- a/content/node.ac349786-bc86-465d-9374-a277d15a892c.json
+++ b/content/node.ac349786-bc86-465d-9374-a277d15a892c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tonight I was lucky to speak at the first <a href=\"https:\/\/www.meetup.com\/south-wales-tech\/events\/291092930\">Bristol Software Development Meetup event<\/a>, organised by South Wales Tech.<\/p>\n\n<p>Following a great talk from Tom Vaughan, I gave an updated version of my <a href=\"http:\/\/default\/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS<\/a> talk.<\/p>\n\n<p>It's a talk that I first gave in January 2018 and one that I need to continuously update so that it's up to date with the latest version of the framework. The last time I gave this talk was in February 2021 so there was quite a lot of new things to cover.<\/p>\n\n<p>I was also able to show my recent <a href=\"https:\/\/bootstrap-with-tailwind.oliverdavies.uk\">Tailwind versions of Bootstrap components<\/a> as a demonstration at the end of the talk.<\/p>\n\n<p>I'm glad to have had the opportunity to test out the updated version before <a href=\"https:\/\/nordevcon.com\">Norfolk Developers conference<\/a> next week and I'm looking forward to attending more South Wales Tech events in Swansea and Bristol in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f0773074647747f68f82e4db2924323f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json b/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json
index d0c19b14e..99b711753 100644
--- a/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json
+++ b/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you write simple code, it is quicker and easier to read, extend and change.<\/p>\n\n<p>If you need to work on that code in the future - either tomorrow or in months or years - it will be easier to add the new feature or fix the bug.<\/p>\n\n<p>It will also be easier for others who didn't write it, so they must understand what it does (or doesn't do) before making changes.<\/p>\n\n<p>It will also likely be easier to debug with tools like Xdebug and PHPStan or upgrade with tools like Rector.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "01e0bd9d4c8ad64c6ea1a3f3563d37a3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json b/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json
index dece3ed38..8bc77c698 100644
--- a/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json
+++ b/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>\"Deployments\" and \"releases\" are often used interchangeably but mean different things.<\/p>\n\n<p>A deployment moves a change from one place to another, such as some updated code from a staging environment to production.<\/p>\n\n<p>A release is when the change made is available to users.<\/p>\n\n<p>They can happen at the same time, or you can use feature flags to separate them, deploying the code in advance, and the change is only released (or unreleased) by toggling the feature flag.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b418347cf60efb3abda4a93b884ed151",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json b/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json
index 25c490f17..0e6f9311b 100644
--- a/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json
+++ b/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I think that test-driven development (TDD) makes you productive.<\/p>\n\n<p>Firstly, you save time by not needing to switch from your code to a terminal or browser to test it.<\/p>\n\n<p>But, just as importantly, TDD reduces procrastination. It's much clearer to see what the next steps are.<\/p>\n\n<p>You're either thinking and designing your code when writing a failing test or fixing the test failures in the implementation code to get the test to pass. You can focus on each failure and message separately and get them to pass instead of thinking about the whole feature or the rest of the application.<\/p>\n\n<p>Once you have a working test, you can focus on refactoring any code or moving on to writing the next assertion or the next test.<\/p>\n\n<p>I think that achieving small tasks with short feedback loops using test-driven development makes it much easier to remain productive and focussed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d8c18f8667771c2497ae722e5849f6fc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json b/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json
index d13152f7b..3d038164c 100644
--- a/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json
+++ b/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2023\/12\/04\/writing-contrib-modules-as-glue-between-your-custom-code\">In yesterday's email<\/a>, I mentioned the Private Message Queue module - a contributed Drupal module we wrote for a project as part of a contribution-first workflow.<\/p>\n\n<p>In our experience, doing that and releasing Private Message Queue as its own open-source project encouraged more open-source contributions.<\/p>\n\n<p>We started to ask questions like, \"Which user should the messages be sent from?\".<\/p>\n\n<h2 id=\"system-users\">System Users<\/h2>\n\n<p>This led us to create the <a href=\"https:\/\/www.drupal.org\/project\/system_user\">System User module<\/a>.<\/p>\n\n<p>Inspired by system users in Linux, it provides a way to identify and retrieve system users that aren't tied to individuals' accounts and without relying on \"magic\" user IDs.<\/p>\n\n<p>But what if a website doesn't have a system user?<\/p>\n\n<h2 id=\"null-users\">Null Users<\/h2>\n\n<p>This led to the <a href=\"https:\/\/www.drupal.org\/project\/null_user\">Null User module<\/a>.<\/p>\n\n<p>Following the Null object pattern, if there isn't a system user, instead of returning <code>NULL<\/code> or <code>FALSE<\/code>, you return a null user that you use in the same way, though they'll have default empty values and won't perform any actions.<\/p>\n\n<p>This pattern simplifies your code as you don't need to check for <code>NULL<\/code> or <code>FALSE<\/code> values.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>If I remember correctly, as part of the project, we created and released around ten new contributed modules to Drupal.org.<\/p>\n\n<p>We were able to move straight onto the next phase of the project.<\/p>\n\n<p>We didn't need to clean them up or refactor them beforehand. We didn't need to dedicate any additional time as they were already released.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "11107beced548217d0455b4197564141",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json b/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json
index 2205ea2a8..325d5ad91 100644
--- a/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json
+++ b/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You're or a new&nbsp;team member are&nbsp;onboarded to a project to make some CSS changes.<\/p>\n\n<p>The project uses Sass, Less or another preprocessor.<\/p>\n\n<p>Not knowing this, the generated CSS files are changed instead of the Sass files.<\/p>\n\n<p>The changes are committed and pushed, but because they weren't added to the Sass files, they will be lost when the&nbsp;CSS files are re-generated in the future.<\/p>\n\n<p>Or, if the Sass and CSS files become too out of sync, everyone will be too worried about losing changes to use the Sass files, so they will be abandoned&nbsp;and not used.<\/p>\n\n<p>What if you change the&nbsp;correct files but don't know the magic command to generate the assets for that project?<\/p>\n\n<p>I've seen things like this happen on numerous projects and is an example of why the \"no build\" approach is appealing.<\/p>\n\n<p>Especially with enhancements to CSS, such as custom properties (variables) and nesting, a lot of the functionality from preprocessors can now be done with normal CSS.<\/p>\n\n<p>This means the front-end build steps can be simplified&nbsp;or removed entirely, reducing the technical overhead and dependency cost, and it's easier for new Developers to get started.<\/p>\n\n<p>Win, win!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "247a1b12455fa21f13c5bcd13b69f5c7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.afe43360-ecca-472a-b501-062f898650a5.json b/content/node.afe43360-ecca-472a-b501-062f898650a5.json
index 0bd03a10a..22b0b07f0 100644
--- a/content/node.afe43360-ecca-472a-b501-062f898650a5.json
+++ b/content/node.afe43360-ecca-472a-b501-062f898650a5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, I had to debug a regression in a codebase.<\/p>\n\n<p>Something was working at the last release but is now broken.<\/p>\n\n<p>There have been around 20 commits to the mainline branch since the last release, and the first step to fixing the issue is to determine which commit caused the regression.<\/p>\n\n<p>Git has a great tool for this - <code>git bisect<\/code>.<\/p>\n\n<p>You tell Git what the last known working commit was, such as the tag of the last release, and it will start to split the commits and prompt you to tell it whether the commit is good or bad.<\/p>\n\n<p>If there are 20 commits, it may pick commit number 10, and based on whether the commit is good or bad, it may pick commit 5 or 15.<\/p>\n\n<p>Based on your answers, Git will then tell you which the first bad commit is.<\/p>\n\n<p>Even better, if it's something that you can script or is covered with an automated test, <code>git bisect<\/code> can run a command for you and find the failure automatically rather than a human needing to check manually.<\/p>\n\n<p>Once you've found the commit that breaks, you can view it and find and fix the bug.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6fbd09cf55994352dfe3e9a6fae9be71",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json b/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json
index 448e00991..db44be2f4 100644
--- a/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json
+++ b/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A great quote I recently heard whilst watching a conference talk was \"No-one is paying us to do <em>something<\/em>, but we need to do it to work effectively\".<\/p>\n\n<p>This talk was about decoupling, but the same quote could be re-used for various topics.<\/p>\n\n<p>A common one is automated tests and test-driven development.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2025\/02\/23\/line-item\">Tests aren't a line item<\/a> that should be billed for separately and clients and customers just want their software to work.<\/p>\n\n<p>Generally, they aren't concerned that there are automated tests or whether the tests were written before the code.<\/p>\n\n<p>If I need to give an estimate, I always include time to write automated tests.<\/p>\n\n<p>It's part of my software development process.<\/p>\n\n<p>Whether people know they're paying for me to write automated tests as part or not, I can work more effectively when I have tests and am doing test-driven development.<\/p>\n\n<p>Both when writing the code, but also if it needs to be <a href=\"http:\/\/default\/daily\/2024\/10\/20\/test-then-refactor\">refactored or changed in the future<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4b75b46173ea0fe84b24f6e4c3cfcdb5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json b/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json
index 199c85ef8..dbd912d1e 100644
--- a/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json
+++ b/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Working on software development tasks is like going to the Dentist.<\/p>\n\n<p>Releasing new features, bug fixes, dependency updates, and refactoring is better and less painful when done regularly.<\/p>\n\n<p>Doing these changes in small and regular batches is less risky than less frequent and larger releases.<\/p>\n\n<p>It's easier to identify the cause of any issues and correct course if things aren't going to plan.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "81b20fc691ca055821b1bd306f13d303",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json b/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json
index bbcb15cc4..def6ecad6 100644
--- a/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json
+++ b/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/04\/12\/drupal-rector-and-the-project-update-bot\">Yesterday's email<\/a> was about using Drupal Rector and the Automated Project Update bot to update contributed modules.<\/p>\n\n<p>But what about custom modules within your application?<\/p>\n\n<p>To do this, I use the <code>drupal-check<\/code> tool, which is built on PHPStan, and the Upgrade Status module.<\/p>\n\n<p>They scan your custom modules and themes and report any deprecated code within your custom projects - i.e. code that will be removed in a future major version - and tell you what new code to use instead.<\/p>\n\n<p>Once you've removed any deprecations, your module or theme will be ready for the next major version of Drupal.<\/p>\n\n<p>This is the approach I've used to upgrade numerous websites between major modern versions of Drupal, making small updates to existing code instead of having to rewrite it from scratch.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "62c9b3575536aedbe5b6aa6eec541fe7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json b/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json
index 3464208f1..ee5b7198d 100644
--- a/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json
+++ b/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was in a pair programming session today, working on some Twig components with Tailwind CSS.<\/p>\n\n<p>We knew what we needed to implement and did so based on an example from a Tailwind component library and some additional styles.<\/p>\n\n<p>After implementing the feature, we could review the classes we added and review what each did.<\/p>\n\n<p>We could easily move or remove a class and see what effect it had.<\/p>\n\n<p>Something nice is that the Tailwind classes usually relate to what CSS they're applying, such as <code>block<\/code> and <code>flex<\/code> for <code>display<\/code> and <code>relative<\/code> and <code>absolute<\/code> for positioning.<\/p>\n\n<p>This makes Tailwind a great way to learn CSS compared to other frameworks that give you prebuilt HTML and expect you to add a generic class like <code>card<\/code>.<\/p>\n\n<p>In that case, the knowledge is hidden within a stylesheet the Developer doesn't see, which makes it harder to read and learn from.<\/p>\n\n<p>Other utility-class frameworks have shorter class names that are less readable.<\/p>\n\n<p>Tailwind strikes the perfect balance, in my opinion.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7b51105f14f48cc301c0e7b3db261bab",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json b/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json
index 5855312ff..9b5f22d39 100644
--- a/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json
+++ b/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal 9 is end-of-life and no longer supported.<\/p>\n\n<p>Drupal 10 is the current stable version, and the development branch for Drupal 11 has just been started.<\/p>\n\n<p>But what will be in Drupal 11?<\/p>\n\n<p>Well, we don't know yet.<\/p>\n\n<p>Drupal's release schedule is based on fixed dates and not on features.<\/p>\n\n<p>Whatever is ready on the release date will be included. If something isn't ready, it'll be in a future version.<\/p>\n\n<p>If something is ready sooner, it'll be in a minor 10 version, such as Drupal 10.2 or 10.3. We've seen it recently with various UI improvements in 10.1 - with more in 10.2.<\/p>\n\n<p>We saw new features, such as Layout Builder, added to Drupal core within the Drupal 8 lifecycle, and there's still time to add more to Drupal 10.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>But, like Drupal 9 and 10, Drupal 11 won't mean a major rewrite to your code.<\/p>\n\n<p>Drupal 11 is based on Drupal 10, so the modules and themes you use will be able to work with both, allowing you to upgrade incrementally.<\/p>\n\n<p>While there isn't a definitive list of new features or changes for Drupal 11, based on things I saw and learned about at DrupalCon, I'm excited to see what makes it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d0230fb0c7af7c9de0491edbea342ca1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json b/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json
index f68b5bdce..c5df387e9 100644
--- a/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json
+++ b/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I spoke with <a href=\"https:\/\/www.daveliddament.co.uk\">Dave Liddament<\/a> to record an upcoming episode of <a href=\"http:\/\/default\/podcast\">the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>In that conversion, we started to talk about conventions, specifically unwritten conventions used within projects.<\/p>\n\n<p>Dave mentioned on some of his projects, they have a convention for when to use <code>get<\/code> or <code>find<\/code> method prefix names.<\/p>\n\n<p>For example, in a <code>UserRepository<\/code> class, a method like <code>findUserByEmail()<\/code> implies that a matching user may not be found.<\/p>\n\n<p>Alternatively, <code>getUserByEmail()<\/code> implies that you're getting a user and will always be one found and returned.<\/p>\n\n<p>This interested me and I <a href=\"https:\/\/tuhrig.de\/find-vs-get\">found a blog post by Thomas Uhrig<\/a> on find vs. get, which I've read since the recording.<\/p>\n\n<p>In the context of the episode, we discussed how conventions like this can be codified and written down and checkable with static analysis tools, but it got me thinking about conventions I've consciously or unconsciously followed, as well as the impact of changing a small word in a method name on its behaviour.<\/p>\n\n<p>What about you?<\/p>\n\n<p>Do you have similar conventions that you follow in your applications?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ae03e717e78fc1762f27dc32a8918c04",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json b/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json
index 04fc90ced..47ff0ec98 100644
--- a/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json
+++ b/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, the 2nd of August 2024, Drupal 11 was released.<\/p>\n\n<p>The next major version of the Drupal content management system and the newest major version since Drupal 10 on the 15th of December 2022.<\/p>\n\n<p>There are some requirement changes, such as newer versions of PHP and MySQL, and updated PHP dependencies, such as a newer version of Symfony, PHPUnit and Twig.<\/p>\n\n<p>Several Drupal core modules have been moved to contrib modules, making Drupal core simpler and leaner.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The same as from 8 to 9 and 9 to 10, it's simple to upgrade to Drupal 11.<\/p>\n\n<p>I did it with my <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\/commit\/f4aa3d8a68464327489c884358b2ba8f6212dad0\">Docker Drupal example<\/a> my changing a few files and running <code>composer update<\/code>.<\/p>\n\n<p>To read more about the Drupal 11 release, go to https:\/\/www.drupal.org\/project\/drupal\/releases\/11.0.0.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "568c4c9322b2426b006acfbbde0b6261",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json b/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json
index a2d425a15..999c6a338 100644
--- a/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json
+++ b/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of the most common responses to why people don't write tests is, \"We don't have time\".<\/p>\n\n<p>So, people don't write tests to save time.<\/p>\n\n<p>While you write less code, it takes longer to test everything manually during development, and more bugs will likely be found, which also takes longer to diagnose, fix, and deal with any knock-on effects.<\/p>\n\n<p>Bugs in production add more administrative overhead as new tickets need to be created and managed, prevent other tickets from being worked on whilst they're fixed, and require more communication with clients and customers.<\/p>\n\n<p>If you save ten minutes not writing a test but spend hours later fixing bugs, you didn't save time - you spent more time in the end.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2cbe50d2773f58c7252205ff19b112c5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b38b290a-1ce1-481d-987b-9683245740da.json b/content/node.b38b290a-1ce1-481d-987b-9683245740da.json
index 9455da58e..ea71aebc6 100644
--- a/content/node.b38b290a-1ce1-481d-987b-9683245740da.json
+++ b/content/node.b38b290a-1ce1-481d-987b-9683245740da.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>My most recent guest on the Beyond Blocks podcast is PHP Developer, public speaker and PHP South West organiser, Dave Liddament.<\/p>\n\n<p>We discuss using PHPStan and static analysis in PHP projects as well as taking some trips down memory lane, including when we wrote the most recent PHP website with Tailwind CSS version 0.4. That is not a typo!<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/22-dave-liddament\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "499b1aaa68d51e78b79ff4e1e163550a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json b/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json
index fbed512c6..75d576c8c 100644
--- a/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json
+++ b/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I noticed that Drupal's Experience Builder project <a href=\"https:\/\/www.drupal.org\/project\/experience_builder\/issues\/3454669\">has adopted architectural decision records<\/a>.<\/p>\n\n<p>From the issue:<\/p>\n\n<blockquote>\n  <p>I proposed [...] to start adopting ADRs to document decisions that were made. That\u2019d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.\n  \u2026 or so I think.\n  Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.<\/p>\n<\/blockquote>\n\n<p>I like this decision and have adopted and <a href=\"http:\/\/default\/daily\/2024\/06\/12\/recording-architectural-decisions\">written about ADRs before<\/a>.<\/p>\n\n<p>I also like that the documents <a href=\"https:\/\/git.drupalcode.org\/project\/experience_builder\/-\/tree\/0.x\/docs\/adr?ref_type=heads\">are stored as markdown files in the repository<\/a>, alongside the code, making it easy for everyone to view or change.<\/p>\n\n<p>As the work on Experience Builder continues, new contributors can read these documents and understand why previous decisions were made, which is extremely valuable.<\/p>\n\n<p>I'm interested to see how ADRs work for the Experience Builder project and whether they're adopted more widely in other parts of the Drupal ecosystem.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9553ccae6f298ace5c5f247750bea8a2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json b/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json
index 8e05657ab..39ad7b09d 100644
--- a/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json
+++ b/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you're trying to <a href=\"http:\/\/default\/daily\/2024\/09\/20\/be-consistent\">keep your code consistent<\/a>, such as following the same coding style or following conventions such as <a href=\"http:\/\/default\/daily\/2024\/09\/05\/find-vs-get\">find vs get<\/a> or design systems such as repositories or builder classes, instead of relying on manual code review and taking the time of a colleague, you can leverage automation to run checks for you.<\/p>\n\n<p>You can run tools such as phpcs or eslint to enforce a coding style and use Git hooks or a CI pipeline to run them automatically or integrate them into your text editor or IDE so you can see and resolve issues as the code is being written.<\/p>\n\n<p>You can use static analysis tools such as PHPStan to find potential bugs but also enforce conventions by <a href=\"http:\/\/default\/daily\/2024\/09\/22\/writing-custom-phpstan-rules-for-drupal-projects\">writing custom rules for your project<\/a> or using architectural testing tools such as PHPat.<\/p>\n\n<p>By automating checks, you'll have a consistent result every time and don't need to wait for someone else to find small issues you could have fixed quickly.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7c09b32f259965b0c8e9be189b768902",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json b/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json
index a29a3d461..4c32332c8 100644
--- a/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json
+++ b/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few times in the last couple of years, I've come across companies or agencies writing their own CMSes or frameworks.<\/p>\n\n<p>Not as a learning exercise, which I think every Developer does at some point as part of their learning, but to host production applications.<\/p>\n\n<p>With so many free and open source options - there are Drupal, WordPress, Symfony and Laravel just in the PHP ecosystem - why would people use custom or proprietary CMSes or frameworks?<\/p>\n\n<p>One reason is <a href=\"http:\/\/default\/daily\/2024\/12\/30\/domain-names\">vendor lock-in<\/a>.<\/p>\n\n<p>If someone is locked into your CMS, framework or hosting platform, it's difficult for them to move away.<\/p>\n\n<p>That's one of the main benefits of open source software.<\/p>\n\n<p>There isn't just one company that provides services for it and customers can choose who they want to work with.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "482bccba295c563b929e0709bade80e5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json b/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json
index 6f54c6b7b..527c027fa 100644
--- a/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json
+++ b/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As of today, Drupal 9 is end-of-life and no longer supported.<\/p>\n\n<h2 id=\"why%3F\">Why?<\/h2>\n\n<p>Drupal 9 relies on several other software projects, including Symfony, CKEditor, and Twig.<\/p>\n\n<p>With Symfony 4's end of life, CKEditor 4's end of life, and Twig 2's end of life all coming up soon, Drupal 9 went end of life on November 1st, 2023.<\/p>\n\n<h2 id=\"what-do-i-do-next%3F\">What do I do next?<\/h2>\n\n<p>There will be no further releases of Drupal 9 so you need to upgrade.<\/p>\n\n<p>If you're stuck on Drupal 9, 8, or 7, get unstuck with a <a href=\"http:\/\/default\/drupal-upgrade\">Drupal upgrade roadmap<\/a> and get directions how to upgrade to Drupal 10.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6e4460ba8f2e7ef1df4c709299bfb0a6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json b/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json
index f852ce22d..18f95d8de 100644
--- a/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json
+++ b/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you work on software projects that use a database, you need a convenient way to connect, inspect, and query them.<\/p>\n\n<p>Some IDEs like PhpStorm have an integrated database client, which I've recently added to my Neovim setup and working with Docker and Docker Compose.<\/p>\n\n<h2 id=\"configuring-docker-compose\">Configuring Docker Compose<\/h2>\n\n<p>A local port needs to be exposed from the database container that Neovim can connect to.<\/p>\n\n<p>I usually do this with a <code>docker-compose.override.yaml<\/code> file:<\/p>\n\n<pre><code class=\"language-yaml\">services:\n  database:\n    ports:\n      - 3307:3306\n<\/code><\/pre>\n\n<p>Docker Compose recognises this by default, extends the normal <code>docker-compose.yaml<\/code> file and adds a port forwarding to the <code>database<\/code> service.<\/p>\n\n<h2 id=\"configuring-neovim\">Configuring Neovim<\/h2>\n\n<p>The two plugins I'm using are tpope\/vim-dadbod and kristijanhusak\/vim-dadbod-ui, and should work with Vim and Neovim. Thanks to both of these project maintainers.<\/p>\n\n<p>Once installed, run <code>:DBUIAddconnection<\/code> to add a database connection.<\/p>\n\n<p>Here is an example connection string:<\/p>\n\n<pre><code>mysql:\/\/drupal:drupal@localhost:3307\/drupal?protocol=tcp\n<\/code><\/pre>\n\n<p>Using the local port mapping, this connects to a MySQL database within the <code>database<\/code> service.<\/p>\n\n<p>Then run <code>:DBUI<\/code> to toggle the UI and see a list of databases in the left-hand sidebar.<\/p>\n\n<p>You can enter <code>&lt;leader&gt;R<\/code> to refresh databases or <code>r<\/code> to rename or update connection details for a specific database.<\/p>\n\n<p>Once connected, you can enter and save queries, using table and column name completion, which are executed every time the query is saved.<\/p>\n\n<p>I like not needing to switch contexts and leave my editor in order to query a database, and feel a lot more productive being able to write, execute and save queries within this UI.<\/p>\n\n<p>If you're a Vim or Neovim user, I'd suggest trying this setup and seeing if it works for you.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "795dc7516651db80b6d0231ec717952b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json b/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json
index a295f9c45..cf7a398d5 100644
--- a/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json
+++ b/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whilst discussing <a href=\"http:\/\/default\/daily\/2025\/02\/14\/drupalisms\">de-jargoning Drupal and Drupalisms<\/a> with Emma Horrell and Luke McCormick, I started thinking about pieces of jargon I come across regularly.<\/p>\n\n<p>Common ones are CI and CD.<\/p>\n\n<p>CI (or continuous integration) is not about whether you have a CI pipeline and use a tool like Jenkins, GitHub Actions or GitLab CI (despite how some of these tools are named).<\/p>\n\n<p>Continuous integration is how often code is integrated together.<\/p>\n\n<p>If it's been more than a day since you last merged your code into your mainline branch, you're not doing continuous integration.<\/p>\n\n<p>The less often you merge code, the more likely it is there will be conflicts or incompatibilities with other code that's been worked on - whether it's someone else's code, or code that you're writing in a different branch for a different task.<\/p>\n\n<p>CD stands for is continuous deployment or continuous delivery.<\/p>\n\n<p>When is the last time you deployed changes to production?<\/p>\n\n<p>If it's been more than a day, you're not doing continuous deployment.<\/p>\n\n<p>I've worked on teams and projects when it's been months between production releases.<\/p>\n\n<p>I much prefer releasing small, iterative and continuous improvements to production instead of doing large and risky deployments.<\/p>\n\n<p>Developers get their changes released sooner, end users get fixes and new features sooner, and it's easier to identify and resolve issues when releases are smaller and more frequent.<\/p>\n\n<p>How about you?<\/p>\n\n<p>Are you doing CI or CD?<\/p>\n\n<p>What other Drupal or techy jargon terms do you see regularly?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "431bef314ddeb1827fe0a9654609412d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json b/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json
index 0ac34f22f..0991c30f4 100644
--- a/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json
+++ b/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As the name suggests, <a href=\"http:\/\/phpunit.de\">PHPUnit<\/a> is a unit testing framework for PHP.<\/p>\n\n<p>It's the defacto PHP testing framework used by the major PHP projects, such as Drupal, Symfony, Laravel.<\/p>\n\n<p>But unit testing isn't all that PHPUnit can do.<\/p>\n\n<p>These frameworks extend PHPUnit to give it more functionality.<\/p>\n\n<p>Drupal allows you to run functional\/browser tests to make requests to pages, check the response codes and content, as well as integration\/kernel tests to test real services instead of relying on mocking within unit tests.<\/p>\n\n<p>Symfony does the same with its web and kernel test cases.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>If you use a framework and want to more than unit testing, intsead of including another testing framework, try using some of the PHPUnit extensions that are provided by the framework.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ebb678e6bfb989f0b14c1f494c92a1af",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json b/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json
index 13430fbaf..33f674f71 100644
--- a/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json
+++ b/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Back in <a href=\"http:\/\/default\/podcast\/11-mark-conroy\">episode 11 of the Beyond Blocks podcast<\/a>, my guest was Mark Conroy and we discussed various things including his <a href=\"https:\/\/runningplangenerator.com\">Running Plan Generator<\/a> and the <a href=\"https:\/\/www.drupal.org\/project\/content_access_by_path\">Content Access By Path Drupal module<\/a>.<\/p>\n\n<p>Written for the LocalGov Drupal distribution, as its name suggests, the module allows for setting permissions to maintain content based on its path.<\/p>\n\n<p>I had a quick look at the module whilst recording and mentioned there were no automated tests, and I was invited to write and contribute some.<\/p>\n\n<p>I did, <a href=\"https:\/\/www.youtube.com\/live\/XTpliKd47Lg\">live on YouTube<\/a>, and <a href=\"https:\/\/www.drupal.org\/project\/content_access_by_path\/issues\/3428680\">created a merge request<\/a> for the module for review.<\/p>\n\n<p>Today, that merge request was approved and the tests were added to the module, so I'm officially a contributor to that module.<\/p>\n\n<p>I also added GitLab configuration, so the tests will automatically run for every change and help avoid regressions in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f3ba6520289a5b3dda2c70904d92968f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json b/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json
index 73ce9110f..e17ec01ca 100644
--- a/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json
+++ b/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm currently working on a project, building the initial components and pages in Fractal - a component library tool.<\/p>\n\n<p>The templates are written in Twig (or twig.js, as Fractal is written in JavaScript), and my JavaScript is using Stimulus.<\/p>\n\n<p>So far, I've been writing the data attributes Stimulus needs, such as <code>data-controller=\"timeline<\/code> and <code>data-timeline-closed-by-default-value=\"true\"<\/code> by hand but, yesterday I decided to write some custom Stimulus functions for this - inspired by the ones in the Symfony UX bundle.<\/p>\n\n<p>After a few hours, I had them working and, although they weren't feature comparable with Symfony's, they were good enough to use in my codebase and I migrated the Stimulus code I'd written so far.<\/p>\n\n<p>Today, I removed them and reverted my code.<\/p>\n\n<h2 id=\"causing-obscurity-through-abstraction\">Causing obscurity through abstraction<\/h2>\n\n<p>Here's an example of some code with and without a helper function:<\/p>\n\n<pre><code class=\"html\">\n{# With the helper function. #}\n&lt;div {{ stimulus_controller(\"timeline\", { closedByDefault: true, closeOtherItems: true }) }}&gt;\n\n{# Without the helper function. #}\n&lt;div\n  data-controller=\"timeline\"\n  data-timeline-close-other-items-value=\"true\"\n  data-timeline-closed-by-default-value=\"true\"\n&gt;\n\n<\/code><\/pre>\n\n<p>Although it's less code, I prefer to be able to see and understand the generated code.<\/p>\n\n<p>I don't have to remember the parameters of the helper function, so there's less mental overhead.<\/p>\n\n<p>I can debug this easily as I can find the same code that's in the generated HTML.<\/p>\n\n<p>If I need to find <code>closed-by-default<\/code>, it doesn't exist in the template if I'm using the helper function as keys are written in camel-case and converted to kebab-case. This would be likely to cause me an issue in the future if I forgot, and could cause confusion if I needed to explain it to other Developers.<\/p>\n\n<h2 id=\"fewer-dependencies\">Fewer dependencies<\/h2>\n\n<p>To convert keys from camel case in Twig for kebab case in HTML attributes, I installed a library that I no longer need. This means I can remove that dependency.<\/p>\n\n<h2 id=\"less-code-to-maintain\">Less code to maintain<\/h2>\n\n<p>Now I've removed those functions, I no longer need to maintain them and I can focus on completing the code for my client and moving forward with the project.<\/p>\n\n<p>The functions weren't feature comparable with Symfony's and would have needed more development and potential bug fixes in the future. By removing them, I'm no longer responsible for maintaining and extending it and the codebase is leaner.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>It was an interesting experiment, but, after thinking about it and trying it out, I decided not to keep the helper functions on this project.<\/p>\n\n<p>The abstraction wasn't providing value and I prefer to keep the code as simple and easy to work on as possible.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d262aceb56149a2882d4619968502736",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json b/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json
index 06b7aca60..59cce2707 100644
--- a/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json
+++ b/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently read a post by Derek Sivers about <a href=\"https:\/\/sive.rs\/plaintext\">why he only writes in plain text files<\/a>.<\/p>\n\n<p>I've been doing some digital cleanup and moved my notes from different online systems to plain text files.<\/p>\n\n<p>The main advantages from Derek's post are:<\/p>\n\n<ul>\n<li>Portable: plain text files are easy to migrate between computers or store in the cloud and can be opened and edited anywhere.<\/li>\n<li>Uncommercial: you're not locked in to a proprietry or service-specific text format and not restricted by the number of notes you can have or have unwanted features pushed upon you.<\/li>\n<li>Offline: plain text files can be accessed offline if they're stored locally without needing to go via a website.<\/li>\n<li>No dependencies: you can edit plain text files in any editor and don't need to use heavy or bulky programs.<\/li>\n<li>Easy to convert: plain text can be converted into anything else.<\/li>\n<\/ul>\n\n<p>I'd also add that plain text files are easy to search and grep to find content and can be version controlled and, in software projects, easily stored alongside the code it relates to.<\/p>\n\n<p>This is why, although I work mostly with Drupal, I also like static site generators and use tools such as rst2pdf and Marp to develop presentation slides from plain text files.<\/p>\n\n<p>From the conclusion of Derek's post:<\/p>\n\n<blockquote>\n  <p>Reliable, flexible, portable, independent, and long-lasting. Plain text files will be readable by future generations, hundreds of years from now.<\/p>\n  \n  <p>I especially enjoy the tranquility of their offline, non-commercial nature. They\u2019re quiet. They\u2019re focused. (As I aim to be.)<\/p>\n<\/blockquote>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "247980cbd242cc2ccdbfcc15a30390c8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json b/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json
index 3c4d95791..9d992dd50 100644
--- a/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json
+++ b/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I attended the relaunched PHP Oxford user group meetup this evening, organised by Humand Talent.<\/p>\n\n<p>I gave the short version of my talk on the <a href=\"http:\/\/default\/build-configs\">Build Configs<\/a> tool I've built and used to manage multiple projects' configuration files.<\/p>\n\n<p>As it was a shorter talk, I didn't show the internals slides I did remotely for PHP Muninch on Tuesday evening.<\/p>\n\n<p>However, if anyone wants to see the full slides that show some of the Build Configs code, <a href=\"http:\/\/default\/talks\/building-build-configs\">they are online<\/a>.<\/p>\n\n<p>As well as the Drupal, Fractal, Drupal Commerce Kickstart and Drupal LocalGov examples on GitHub, I created Symfony and Laravel examples that are still unreleased in private repositories. I plan on reviewing those, making them public soon and continuing to iterate on and improve the Build Configs tool itself - making it more valuable to me and my customers and clients.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8f7fe4481187e913f2e5fc1042f5b712",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json b/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json
index 87c0af949..852046d70 100644
--- a/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json
+++ b/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I mentioned during my <a href=\"http:\/\/default\/podcast\/7-mike-karthauser-testing-legacy\">podcast episode with Mike Karthauser<\/a> is a quote I saw recently:<\/p>\n\n<blockquote>\n  <p>Code is a liability, not an asset.<\/p>\n<\/blockquote>\n\n<p>The more code you write, the more you have to maintain.<\/p>\n\n<p>The more complex the code is, the harder it is to maintain.<\/p>\n\n<p>For example, when adding a new page to a Drupal application, should you write a custom route, a Controller, and a Repository and write accompanying tests, or should you use the Views module?<\/p>\n\n<p>Both can give the same result.<\/p>\n\n<p>One involves writing and maintaining custom code; the other uses a no-code approach available in Drupal, which creates the page and output based on your selections.<\/p>\n\n<p>There isn't a correct answer.<\/p>\n\n<p>The option you choose will depend on what problem you're solving, what deadlines you're working to, and any precedents set within the project.<\/p>\n\n<p>It also depends on whether you want to maintain the code you write over time, fix any bugs, refactor it, and upgrade it as part of major Drupal version upgrades.<\/p>\n\n<p>Like a house, car or pet, any code you write will need ongoing care and maintenance in the future - not just now.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "46a1df14b13ff412272180103b18543b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json b/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json
index 993e80225..3536eef41 100644
--- a/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json
+++ b/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I was at another School of Code hackathon event, mentoring a team of three Developers as they planned and built an application within a day.<\/p>\n\n<p>During the day, we looked at some example documentation that included variable names like <code>err<\/code>, <code>req<\/code>, and <code>res<\/code>.<\/p>\n\n<p>I don't like short variable names like this.<\/p>\n\n<p>I'd suggest calling them what they are - <code>error<\/code>, <code>request<\/code> and <code>response<\/code>.<\/p>\n\n<p>This makes the code clearer and easier to read and understand, particularly if you aren't using types and need additional context.<\/p>\n\n<p>Readability is important as <a href=\"http:\/\/default\/daily\/2024\/08\/07\/people-read-more-code-than-they-write\">people read more code than they write<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1a2697516ded656f685248cde9ddc09e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json b/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json
index 880616be4..1ce3181c0 100644
--- a/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json
+++ b/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, I released a new version of the <a href=\"https:\/\/www.drupal.org\/project\/override_node_options\">Override Node Options module<\/a> - version 8.x-2.9.<\/p>\n\n<p>This version makes the module compatible with Drupal 11 and, as there are no breaking changes, it's still compatible with Drupal 9 and 10.<\/p>\n\n<p>It's great to see the module used on many Drupal 8+ websites and distributions such as <a href=\"http:\/\/default\/daily\/2024\/11\/17\/override-node-options-used-by-localgov-drupal\">LocalGov Drupal<\/a>.<\/p>\n\n<p>Whilst <a href=\"http:\/\/default\/daily\/2024\/11\/16\/an-interesting-thing-i-spotted-about-the-override-node-options-module\">the overall number of installations has been consistent<\/a>, the number of Drupal 7 installations has decreased whilst the Drupal 8+ version installations have increased.<\/p>\n\n<p>With a Drupal 11-compatible version now available, I hope it continues to increase.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b386cfa88fcc78b52277d0eb4bc4f76d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json b/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json
index 67f6a075b..3aaf6c491 100644
--- a/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json
+++ b/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The talk that I gave last week at PHP Stoke was <a href=\"http:\/\/default\/presentations\/things-you-should-know-about-php\">Things to know about PHP<\/a> - a talk that I was originally asked to give at the Swansea Software Development Meetup (SSDC) in January 2019, and this was the second time that I've been asked to give this talk at a PHP meetup.<\/p>\n\n<p>Originally to give a group of various Software Developers an introduction to PHP, I didn't want the talk to be focused just on the language itself and be a walkthough the PHP manual.<\/p>\n\n<p>Whilst there is some code in the talk so demonstrate what it can do, the other half of the talk is about the other parts of the PHP ecosystem such as tooling and the community. I talk about tools like Composer, PHPStan, Xdebug, PHPUnit and Pest, the CMSes and frameworks that are available, and the various online learning tools like SymfonyCasts and Laracasts as well as certification programs that are available.<\/p>\n\n<p>It's great to give this talk at meetups as that's where the community starts, where people come to share and learn, and what larger conferences like PHP UK, php[tek] and others are built on. I love attending meetups and events and meeting other members of the PHP community.<\/p>\n\n<p>Oh, and elePHPants!<\/p>\n\n<p>The latest versions of the slides are on the Talks section of my website (the link is at the top of the email).<\/p>\n\n<p>If you'd like me to come and speak at your meetup or conference, please get in touch!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "05ba98327bf894b02b9686a1f5c9b14f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json b/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json
index e644ef2ec..d1936d188 100644
--- a/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json
+++ b/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json
@@ -87,6 +87,5 @@
             "processed": "<p>This week, I was excited to welcome Luke McCormick back to the Beyond Blocks podcast.<\/p><p>We discussed his Simplify Drupal project and using AI tools, such as the Cursor editor, for web browsing.<\/p><p>Luke recently gave a talk about this at the Stanford WebCamp conference, so it was great to discuss this further and learn how he's been using AI in his development workflow.<\/p><p><a href=\"http:\/\/default\/podcast\/28-using-ai-tools-web-coding\">Listen to the episode here<\/a>.<\/p><p>I have a few new guests lined up, so expect more episodes of the Beyond Blocks podcast in the coming weeks.<\/p><p>If you want to be a guest on a future episode, reply to this email and let me know.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json b/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json
index b4b4748a4..8cf25302d 100644
--- a/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json
+++ b/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I refactored some code on a client's Drupal project I've been working on.<\/p>\n\n<p>This is what the commit says:<\/p>\n\n<blockquote>\n  <p>Showing 92 changed files with 885 additions and 156 deletions<\/p>\n<\/blockquote>\n\n<p>So, it's not a small refactor.<\/p>\n\n<p>As I worked on the custom modules needed for the site, I noticed that some common functionality was spread over multiple modules. This refactor moved that functionality into its own module, which is now a dependency of the others.<\/p>\n\n<p>The code is better, and the responsibilities of the modules are clearer.<\/p>\n\n<p>Whilst a large amount of those additions are adding test modules with test configuration, it's not a small refactor.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is what it says at the bottom of the CI pipeline output:<\/p>\n\n<blockquote>\n  <p>OK (79 tests, 565 assertions)<\/p>\n<\/blockquote>\n\n<p>This is the same number of passing tests and assertions I had before I started the refactor, so I know the functionality still works.<\/p>\n\n<p>If I didn't have those tests, I wouldn't have done the refactor.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bc73a47b4554b36af87f142a939076a9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json b/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json
index 34db12fb1..1fce05232 100644
--- a/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json
+++ b/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In a recent private coaching session with <a href=\"https:\/\/jonathanstark.com\">Jonathan Stark<\/a>, he said, \"Don't be perfect, be useful\".<\/p>\n\n<p>He meant it relating to giving a presentation, like a talk or workshop, but I thought about how the same quote applies to some of the software development topics I cover in these emails.<\/p>\n\n<p>You don't need a perfect test suite with 100% coverage. One test is better than no tests, and some tests are better than one.<\/p>\n\n<p>You don't need to run static analysis on all your code at the highest level. If you run it on some of your code, maybe the newer code or the most crucial parts of your application, that's better than not running it at all, and it will catch many issues even at the lower levels.<\/p>\n\n<p>You don't need to know and implement all the design patterns within your code. The objective is to deliver working software for your customers and clients. Do this first and refactor later when needed.<\/p>\n\n<p>You don't need always to be pair or mob programming. Do it when it works for the people and situation.<\/p>\n\n<p>These tools and techniques are useful.<\/p>\n\n<p>They don't need to be perfect.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f14adb13d3ae7905d6bc55853f2ce7ae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json b/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json
index d6d20c53c..7067af643 100644
--- a/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json
+++ b/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It can take time to write automated tests and do test-driven development, but it is an investment in a project's future stability.<\/p>\n\n<p>Spending time to write tests upfront will save time as the project progresses, make the code easier to change, and result in better software, fewer bugs, and quicker changes.<\/p>\n\n<p>Even though it takes time, it's time well spent.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b535eb52679173284d48e852e1dd8e86",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json b/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json
index 8c480a4c3..bf8fb3bef 100644
--- a/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json
+++ b/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Now <a href=\"http:\/\/default\/daily\/2025\/02\/28\/preprocessors\">CSS supports variables<\/a> (aka custom properties) and <a href=\"http:\/\/default\/daily\/2024\/07\/16\/tailwind-css-v4--with-even-more-css\">Tailwind CSS v4 is configured using CSS<\/a> instead of JavaScript, I've been making heavy use of CSS variables in my front-end code.<\/p>\n\n<p>I still use Tailwind to do the heavy lifting, but I can use CSS variables to extract themeable classes with variables like <code>--color-primary<\/code> that can change value based on a data attribute or by something else.<\/p>\n\n<p>These variables can still use Tailwind's core variables by doing <code>--color-primary: var(--color-red-500)<\/code>, rather than having to recreate all its colors, spacing or whatever variables I need to use.<\/p>\n\n<p>Tailwind has a arbitrary syntax to easily use CSS variables - e.g. <code>bg-(--color-primary)<\/code> - and you can define one-off variables with <code>[--box-spacing:30px]<\/code> or <code>[--box-spacing:--spacing(3)]<\/code> and using the standard arbitrary class syntax.<\/p>\n\n<p>CSS variables aren't specific to Tailwind CSS, so if I wasn't using Tailwind in a codebase, I'd use the new native CSS features <a href=\"http:\/\/default\/daily\/2024\/05\/26\/is-it-time-to-stop-writing-sass\">instead of a preprocessor like Sass<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5a6518d8c14841bf4d760dcc8afd3399",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json b/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json
index b59ce7be3..d9c83f51f 100644
--- a/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json
+++ b/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In my <a href=\"http:\/\/default\/daily\/2024\/01\/09\/using-tailwind-css-is-a-great-way-to-learn-css\">recent pair programming session<\/a>, building components with Tailwind CSS, we experienced another benefit of styling with utility classes.<\/p>\n\n<p>CSS usually has a global scope, but utility classes change it to a local scope.<\/p>\n\n<p>For example, having a card component with a <code>card<\/code> class on it, any changes to the styles will affect all instances of any card component that uses the <code>card<\/code> class.<\/p>\n\n<p>How do you know you haven't broken something in a different component without re-checking every component manually?<\/p>\n\n<p>How do you easily modify or extend it as requirements change or add more card types?<\/p>\n\n<p>If you need to make a change in the future, you're likely to add more styles and modifiers and add to the CSS, causing it to grow rather than change the existing styles - in fear of breaking something else.<\/p>\n\n<p>With utility classes, such as the ones generated by Tailwind CSS, you can see and understand what styles are applied to the HTML.<\/p>\n\n<p>This also makes it easier to change, and because the classes and styles are added directly to that element, you don't need to worry about breakages elsewhere.<\/p>\n\n<p>If you need to add a new class to that card type, you can do so knowing that it won't affect all card styles globally in your application - just the one you're working on.<\/p>\n\n<p>This means you can change things more easily in the future but also work quicker now as you don't need to worry about all that additional context.<\/p>\n\n<p>You can focus on what you're working on right now.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6dfe7f8c27fa0a23fdab4a3d3adf0676",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json b/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json
index 5c5dc747b..c60e46ecd 100644
--- a/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json
+++ b/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>It was announced at DrupalCon that Drupal 7 support was being extended one final time until January 2025.<\/p>\n\n<p>But if you have a Drupal 7 website, does that mean you should wait to start upgrading it?<\/p>\n\n<p>I recommend starting the process as soon as possible.<\/p>\n\n<p>Even though Drupal core support is extended, I've looked at projects that use modules marked as unsupported by their maintainers for some time as they focus on versions for Drupal 8, 9 or 10.<\/p>\n\n<p>In that case, those modules will have no new features, bug fixes or security updates, although Drupal core support has been extended.<\/p>\n\n<p>You may have a lot of custom code that needs to be ported to Drupal 10 or a complex data structure that needs to be migrated, These things will take time, so it's best not to leave it until the last minute.<\/p>\n\n<p>If you're stuck on Drupal 7, book an <a href=\"http:\/\/default\/call\">upgrade consultation call<\/a> with me or purchase an <a href=\"http:\/\/default\/drupal7\">upgrade roadmap for your project<\/a> and I'll get you unstuck.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "49f172d2f1fab5d643988eb42ef695ee",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json b/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json
index 13dfef537..de6b028ab 100644
--- a/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json
+++ b/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Decide, automate, document<\/p>\n\n<p>Here are three steps to making decisions, such as introducing new tools and processes:<\/p>\n\n<p>Decide.<\/p>\n\n<p>Automate.<\/p>\n\n<p>Document.<\/p>\n\n<p>First of all, a decision needs to be made about what you will introduce.<\/p>\n\n<p>It could be whether to write automated tests, use static analysis, choose which coding standard to use, or make architecture decisions about how you want to build your application.<\/p>\n\n<p>Once you've decided and added the tool or process, automate it if you can.<\/p>\n\n<p>A CI pipeline or Git Hooks can run tests and checks automatically to know if the code complies with what was agreed upon rather than relying on this being done manually.<\/p>\n\n<p>Finally, document it so that it's available for others to read and reference, including new team members.<\/p>\n\n<p>Ensure to document why this was added, what problem it solves, any alternatives that were considered and any side effects or consequences. Technical design documents and ADRs (architectural decision records) are great for this!<\/p>\n\n<p>In the future, you may want to revisit the decision and decide if it's still correct, and you'll appreciate having the information documented.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4f6b35edac4d89b8fb13a0be63f410ac",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json b/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json
index 54af6a02b..5f5f3bc4e 100644
--- a/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json
+++ b/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've always thought companies should contribute to open-source software.<\/p>\n\n<p>Whether it's financial or contributing time, if companies use free, open-source software (and especially if they're directly making money from it).<\/p>\n\n<p>Contributing to the software you use will improve the software, whether adding new features, fixing a bug, or contributing translations.<\/p>\n\n<p>Having contributors to the software is a great way to differentiate your company from the competition, and the knowledge gained from contributing will result in better code for your projects.<\/p>\n\n<p>If you organise or sponsor events such as conferences and meetups, you also get exposure from the event and help support the event and community.<\/p>\n\n<h2 id=\"here%27s-the-thing...\">Here's the thing...<\/h2>\n\n<p>I've recently pledged to donate a percentage of income from Drupal-related services to the Drupal Association and would like to see others do the same if they can.<\/p>\n\n<p>I also sponsor several individuals and organisations on GitHub who build software and create content I use so I get better tools and knowledge for myself and my projects.<\/p>\n\n<p>If your company can contribute to open-source, I'd encourage them to do so and help support open-source software projects and communities.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fb6dc9480f15426adce25a251aaa7947",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json b/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json
index b08668ac9..066ccec33 100644
--- a/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json
+++ b/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Just because Drupal core is supported, it doesn't mean that all of the other modules your project uses are still also supported or actively worked on.<\/p>\n\n<p>Since the Drupal 8 release in 2015, I've seen numerous examples of modules that haven't been updated for some time as maintainers focus on writing and maintaining the versions for Drupal 8 and now 9 and 10.<\/p>\n\n<p>Whilst it isn't marked as unsupported, it isn't being updated either.<\/p>\n\n<p>I recently explained to a client that their site uses a module last released in 2014. It\u2019s buggy, but there\u2019s no newer version to use and issues in the queue are no longer being fixed or triaged.<\/p>\n\n<p>Override Node Options - a popular module I maintain - is in a similar situation. The most recent Drupal 9\/10 version was in February 2023, whereas the last Drupal 7 release was in March 2018.<\/p>\n\n<p>I don't have any official figures to support this, but feel the contribution rate for Drupal 7 projects (as in modules, themes and distributions) has been slowing for some time.<\/p>\n\n<p>Meanwhile, Drupal 7 core is still supported, at least for now.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "18539948fc2de002752220934a543e9c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json b/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json
index fcd873c76..814fd48b9 100644
--- a/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json
+++ b/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Over a year ago, I posted that I was <a href=\"http:\/\/default\/blog\/going-full-vim\">switching to using Neovim full-time<\/a> for my development work.<\/p>\n\n<p>I'd used Vim one file at a time on remote servers, and added Vim plugins in other IDEs and editors, so I was already familiar with a lot of the key bindings and motions before I decided to use it full-time.<\/p>\n\n<p>Still, it was tough to begin with, but once I'd learned how to configure Neovim, I also learned that being able to customise and extend it as much as you need to is one of its main advantages compared to other IDEs and code editors.<\/p>\n\n<p>TJ DeVries - a Neovim core team member - has recently coined the term \"PDE\" (a personalised development environment) which, for me, describes Neovim perfectly.<\/p>\n\n<p>Currently, I have a fuzzy-finder to quickly open files (as well as many other things), an LSP client to add code intelesense, auto-completion, refactoring tools, custom snippets, and very recently, a database client and a HTTP client.<\/p>\n\n<p>Just as important to me, I've found a growing community of other Neovim users who stream on Twitch, post YouTube videos, write blog posts, or publish their dotfiles for others to see and reference.<\/p>\n\n<p>I've learned Lua. Not just for my own Neovim configuration, but I recently wrote and open-sourced my own simple plugin.<\/p>\n\n<p>Like Git, I enjoy and prefer using tools that I can configure and adapt to my workflow.<\/p>\n\n<p>Given Neovim's flexibility and configurability, its expanding feature set both in core and community plugins, and the growing community, I think that Neovim is going to be something that I continue to use and adapt for a long time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fd61209df55f98bd0ca56ce044f36294",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json b/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json
index ab632aff4..efed657fd 100644
--- a/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json
+++ b/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Build Configs - the tool I wrote to generate build configuration files for projects - is <a href=\"https:\/\/github.com\/opdavies\/build-configs\">now released as open-source software on GitHub<\/a>.<\/p>\n\n<p>I wrote it to generate configuration files, such as PHPUnit, PHPStan and PHPCS files, Dockerfiles, Docker Compose files and others, for personal and client projects - namely Drupal, Symfony and Sculpin projects - instead of writing them by hand every time and making them easier to maintain.<\/p>\n\n<p>I've used it for my <a href=\"https:\/\/github.com\/opdavies?tab=repositories&amp;q=docker-example-\">Docker examples on GitHub<\/a> done <a href=\"https:\/\/www.youtube.com\/watch?v=Wlkcf1PLWN8\">live streams where I've re-explored Behat<\/a> and <a href=\"http:\/\/default\/talks\/building-build-configs\">given talks on the project<\/a>, so it made sense to open-source it and release it publicly.<\/p>\n\n<p>There are still more I'd like to do with it, including improving documentation and adding examples, but if you'd like to contribute to it, contributions and pull requests are welcome.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f6fe2ba6a57a493e184303e55e02f271",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json b/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json
index 176368c56..1074b24aa 100644
--- a/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json
+++ b/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few months ago, TJ DeVries (a Neovim core team member) coined the phrase \"Personalised Development Environment\" or PDE.<\/p>\n\n<p><a href=\"http:\/\/default\/blog\/going-full-vim\">I've been using Neovim full-time<\/a> since July 2021 - starting with no configuration to configuring it with Vimscript and later with Lua - setting options like line numbers and relative numbers, tabs and spaces, and indent and fold levels.<\/p>\n\n<p>I evaluated and installed some initial plugins to add functionality that I needed. Some of them I still use, and some I've replaced with alternative plugins or built-in solutions that have been included in newer versions of Neovim.<\/p>\n\n<p>I added my own keymaps that made sense to me that either, in my opinion, improved on default keymaps or created new ones that made sense to me or configured a plugin that I'd added.<\/p>\n\n<p>Recently, I found and added plugins that added a <a href=\"https:\/\/github.com\/rest-nvim\/rest.nvim\">HTTP client<\/a> and a <a href=\"https:\/\/github.com\/kristijanhusak\/vim-dadbod-ui\">database connection manager<\/a> to Neovim - two pieces of functionality that I'd used in other IDEs or separate applications.<\/p>\n\n<p>I also <a href=\"https:\/\/github.com\/opdavies\/toggle-checkbox.nvim\">wrote my own Neovim plugin<\/a> for toggling checkboxes within Markdown lists.<\/p>\n\n<p>Like Drupal and other open-source solutions that I use, I love being able to add or edit functionality as needed.<\/p>\n\n<p>In the last year or so, I've definitely been able to personalise my Neovim setup to meet my needs, and have it work as a fully-fledged solution for PHP and JavaScript development, DevOps work, and technical writing (including this email).<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "74468b0353a980f541a60ac6ae7d8670",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json b/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json
index 89dfb25e1..1cb7cc009 100644
--- a/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json
+++ b/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I've said when <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css.md\">speaking about Tailwind CSS<\/a> and also during <a href=\"http:\/\/default\/daily\/2024\/11\/19\/tailwind-css-v4-is-so-easy-to-set-up\">my recent consulting engagement<\/a>, is that you can build dramatically different-looking UIs even though you're using the same class names.<\/p>\n\n<p>For example, I've rebuilt <a href=\"https:\/\/rebuilding-bartik.oliverdavies.uk\">the Bartik theme<\/a>, <a href=\"https:\/\/rebuilding-acquia.oliverdavies.uk\">the Acquia hosting dashboard<\/a> and <a href=\"https:\/\/rebuilding-bristol-js.oliverdavies.uk\">various other UIs<\/a> for talk demos - none of which look the same or are even similar.<\/p>\n\n<p>This website is themed with Tailwind CSS.<\/p>\n\n<p>As the classes are very low-level, there is no \"Tailwind-looking website\" like there is with other CSS frameworks.<\/p>\n\n<p>And, when you move to other application, the same classes are there and available to use.<\/p>\n\n<p>You just need to customise them, use what you need and ignore what you don't.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5b4b4815f291bc6b2a7f37552c3d1102",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json b/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json
index 95a5641e5..21838c344 100644
--- a/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json
+++ b/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday's email was about repository-specific .gitignore files and different ways to write them.<\/p>\n\n<p>But there's a setting that most people don't know about, where you can configure a global <code>.gitignore<\/code> file.<\/p>\n\n<h2 id=\"what-i-use-it-for\">What I use it for<\/h2>\n\n<p>Whilst it doesn't replace repository-specific files, it's good for operating system-specific files - such as <code>.DS_Store<\/code> files on macOS.<\/p>\n\n<p>I have a convention where I have a <code>.ignored<\/code> directory in a project, and everything in it should be ignored by Git.<\/p>\n\n<p>Instead of adding this to every <code>.gitignore<\/code> file, and because it's specific to me, it's a good choice for a global ignore file.<\/p>\n\n<p>Anything that affects multiple users - such as ignoring <code>vendor<\/code> or <code>node_modules<\/code> should still be set in each repository.<\/p>\n\n<h2 id=\"how-do-you-add-it%3F\">How do you add it?<\/h2>\n\n<p>Add this to your <code>~\/.gitconfig<\/code> or <code>~\/.config\/git\/config<\/code> file to set the path for your global ignore file:<\/p>\n\n<pre><code class=\"language-plain\">[core]\n  excludesFile = \"~\/.config\/git\/ignore\"\n<\/code><\/pre>\n\n<p>Then, create the file and add what you want to ignore everywhere.<\/p>\n\n<p>Just remember this is specific to you, and if others have something you've ignored globally and they haven't, they could still add and commit it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f8e98c50f5284056cf311cfa9f72e1b7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json b/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json
index 1b4a22bcd..ac1274605 100644
--- a/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json
+++ b/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Once you have a passing test and you're confident your code works as expected, what do you do next?<\/p>\n\n<p>Do you keep refactoring and changing it, or is it good enough?<\/p>\n\n<p>Do you need to extract additional classes and methods now, or as the test is passing, do you move on to the next task?<\/p>\n\n<p>The main objective is to ship the change and for it to provide value to users, not to have a perfect or \"gold-plated\" solution.<\/p>\n\n<p>Once it's shipped, because you have tests, you can confidently refactor it in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9d6904a98395f98154e7daf42e53b658",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json b/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json
index 4883bf539..9ad0968c8 100644
--- a/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json
+++ b/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Instead of a single Developer working individually on a task and submitting it for a code review once complete, try pair or mob programming.<\/p>\n\n<p>As well as extra benefits, such as knowledge sharing and shared responsibility for the code, it's continuously reviewed and improved during the session.<\/p>\n\n<p>Questions from \"Why are we doing it this way?\" to \"What's the best name for this variable?\" can be asked, and decisions and changes can be made in real time.<\/p>\n\n<p>So, why wait until the task is complete and the code is harder to change to review it?<\/p>\n\n<p>Why not have it reviewed as it's written?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "21005af8fae35fe0bce3fc916d1c0bc8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json b/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json
index e7caa29a8..8522bcfe0 100644
--- a/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json
+++ b/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/blog\/renaming-gray-grey-tailwind-css\">I previously wrote<\/a> about how to change <code>gray<\/code> to <code>grey<\/code> in Tailwind CSS.<\/p>\n\n<p>So, instead of writing <code>bg-gray-200<\/code>, I could write <code>bg-grey-200<\/code>.<\/p>\n\n<p>This would be the correct spelling, as I live in the UK.<\/p>\n\n<p>But I recently realised that I don't change <code>text-center<\/code> or <code>items-center<\/code> when 'centre' would also be the correct spelling.<\/p>\n\n<p>So, what value is there to renaming <code>gray<\/code>?<\/p>\n\n<p>It adds inconsistency as it mixes US and UK English in this project and inconsistencies between different projects.<\/p>\n\n<p>It doesn't match the CSS colour name.<\/p>\n\n<p>And, if I'm working with others on a project, they also need to be aware of this as it's different from the default configuration and could cause some confusion and affect productivity.<\/p>\n\n<p>Keeping it the default value would make it easier to work on, collaborate on and maintain.<\/p>\n\n<p>Maybe, I'll leave it as <code>gray<\/code> in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ca4c680e0cbb4095fc2e8350b85a012f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json b/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json
index 9870285bc..3c0a4997c 100644
--- a/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json
+++ b/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I enjoy and advocate for pair and mob programming, and the benefits they offer when working in a team - sharing knowledge whilst onboarding and upskilling the team members, whilst also getting continuous real-time feedback and review of the code that's being written.<\/p>\n\n<p>I'm also an open-source maintainer and contributor.<\/p>\n\n<p>I've contributed code to Drupal core.<\/p>\n\n<p>I've written and maintain Drupal projects, such as the Override Node Options module and the Tailwind CSS starter kit theme.<\/p>\n\n<p>I've been a mentor for first-time contributors at several DrupalCon events, helping them get started contributing to Drupal core.<\/p>\n\n<p>Usually, the initial problems are finding an issue to work on and how to get started.<\/p>\n\n<p>Something I've been considering organising are <strong>online Drupal mob contribution sessions<\/strong>, where people can work on tasks together in a mob programming approach.<\/p>\n\n<p>Not working on Drupal applications (although, I offer <a href=\"http:\/\/default\/pair\">paid pair programming sessions<\/a>), this would be for contributing to Drupal core, contrib projects, or initiatives like Starshot or LocalGov Drupal.<\/p>\n\n<p>If you have ideas or feedback, or if this is something you'd be interested in attending, reply and let me know!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ac98176315a9e1cccd237bcf0260a3a5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json b/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json
index 66244a35c..a5fccaf4e 100644
--- a/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json
+++ b/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm happy to be speaking again at <a href=\"https:\/\/www.meetup.com\/php-sw\/events\/298880313\">PHP South West<\/a> next week for my 98th talk or workshop and eighth at PHPSW.<\/p>\n\n<p>This talk will be on <a href=\"https:\/\/sculpin.io\">Sculpin<\/a> - a static site generator written in PHP.<\/p>\n\n<p>I first presented a Sculpin talk at <a href=\"http:\/\/default\/presentations\/test-drive-twig-with-sculpin\">DrupalCamp North in July 2015<\/a> while learning Twig before Drupal 8.<\/p>\n\n<p>If you'd like a sneak peek of the demo site I'm building, <a href=\"https:\/\/github.com\/opdavies\/phpsw-sculpin-demo\">it's on GitHub<\/a>, and I posted a screenshot on <a href=\"https:\/\/twitter.com\/opdavies\/status\/1754629305575874738\">Twitter<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f2fb7d74b91a13b51ff0fd8910e6c614",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json b/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json
index c16394aa1..c2d7a5a14 100644
--- a/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json
+++ b/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been watching the new \"Cosmic Coding with Symfony 7\" series on SymfonyCasts, and today's video was about Stimulus - a \"modest JavaScript framework for the HTML you already have\".<\/p>\n\n<p>As I'm comfortable with other frameworks, such as Vue.js and Alpine.js, I've usually skipped videos about Stimulus, but today, it caught my eye.<\/p>\n\n<p>I was intrigued by it and experimented with it by refactoring a component from a project I am working on.<\/p>\n\n<p>I like the organisation Stimulus provides by using JavaScript classes and controllers while keeping things simple in the HTML code.<\/p>\n\n<p>I initially did this in Fractal but then created <a href=\"https:\/\/github.com\/opdavies\/stimulus-esbuild-example\">an example project<\/a> using Stimulus with esbuild. It's now on my GitHub profile and includes other tools such as Nix, just, and Tmuxinator.<\/p>\n\n<p>After this short evaluation, I like Stimulus and will use it on other components in this project, maybe using third-party Stimulus controllers - either directly or for inspiration.<\/p>\n\n<p>Hat tip to Ryan Weaver and SymfonyCasts for showing Stimulus and Nick Janetakis for showing me esbuild.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5e83d222e9f351c117ad6d2c908c0af2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json b/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json
index 0aaf995ce..26760daf5 100644
--- a/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json
+++ b/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Joel Clermont <a href=\"https:\/\/twitter.com\/jclermont\/status\/1690872089878691840\">replied to a previous email on Twitter<\/a>:<\/p>\n\n<blockquote>\n  <p>I once toyed around with the idea of charging MORE to do it without tests. Had a client pushing back very hard when I mentioned testing (what I thought they\u2019d perceive as a benefit). Ended up not pursuing it, but was a fun idea at the time.<\/p>\n<\/blockquote>\n\n<p>It's an interesting idea.<\/p>\n\n<p>How much more would you charge not to write tests?<\/p>\n\n<p>How much more would make you feel comfortable and confident that the application works as expected, and would cover the additional time for finding and fixing the bugs caused by not writing tests?<\/p>\n\n<p>As Joel said, it was a fun idea, though it seems counter-intuitive to me, as the a client would be paying more for worse software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a7a87d14263d9b3f3b9db35811001884",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json b/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json
index 704a8c857..853f33d31 100644
--- a/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json
+++ b/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>But once a feature has been enabled, how do you know if you can remove its flag?<\/p>\n\n<p>A simple suggestion I've heard is to add a \"Remove when...\" comment above where the flag is used and detail what conditions need to be in place before the flag can be removed.<\/p>\n\n<p>It might be a period of time or after another feature has been shipped, but it will give some clarity when you see the flag in the code to if or when it can be removed.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "41c6635bf0b850f244bdf48de16fe27a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json b/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json
index e6d2d59c0..93b783166 100644
--- a/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json
+++ b/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I have availability to work with a small number of software development teams in the new year and help them ship better software, faster, using tools and techniques like automated testing, test-driven development and static analysis.<\/p>\n\n<p>Would you like to work with me?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6708362766a6d90506b1782d1cc56c17",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json b/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json
index 7b88ae50c..de88a15bf 100644
--- a/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json
+++ b/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In this week's episode of the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a>, I'm joined by Chris Ballard to discuss generative AI in PHP following his talk at PHP South West.<\/p>\n\n<p>We also talked about attending and speaking at meetups and live coding, and I spoke about some of the AI-related content I saw presented at DrupalCon Barcelona.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/24-chris-ballard-generative-ai\">Listen to the episode now<\/a>.<\/p>\n\n<p>If you'd like to be a guest on the podcast or want to suggest a topic, reply and let me know!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "04fbbf59f12e449ba66ad5ff6d0fb063",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json b/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json
index 94a36ceae..103c30c70 100644
--- a/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json
+++ b/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In <a href=\"http:\/\/default\/daily\/2023\/04\/30\/will-we-see-drupal-7-100\">April 2023<\/a>, I wondered if we'd see a 7.100 release of Drupal.<\/p>\n\n<p>I just noticed that we did.<\/p>\n\n<p>It was released on the 6th of March.<\/p>\n\n<p>From the release notes:<\/p>\n\n<blockquote>\n  <p>Maintenance release of the Drupal 7 series. Includes bug fixes and small API\/feature improvements only (no major, non-backwards-compatible new functionality). Unusually, this release does include a new core module.<\/p>\n<\/blockquote>\n\n<p>This is also the first Drupal release to be affected by the Year 2000 problem, a.k.a. the Y2K problem, or the Millennium Bug:<\/p>\n\n<blockquote>\n  <p>Note that this is the first Drupal 7 release with 3 digits. If you receive a report that your version of Drupal is over a decade out of date, see https:\/\/en.wikipedia.org\/wiki\/Year_2000_problem.<\/p>\n<\/blockquote>\n\n<p>According to the usage figures on Drupal.org, there are at least 316,843 active Drupal 7 websites and, with only 243 days left until D7 is end-of-life, hopefully most of them will be upgrading to Drupal 10 (or 11) soon.<\/p>\n\n<p>If you're stuck on Drupal 7, I can help! Reply to this email and let's start a conversation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5805ba311b8e79cc68de1b251dd3b2ff",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json b/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json
index ccdc7456d..6f5e5363d 100644
--- a/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json
+++ b/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After sending <a href=\"http:\/\/default\/daily\/2023\/10\/28\/can-you-move-faster-without-tests\">yesterday's email<\/a>, Dave Hall replied <a href=\"https:\/\/www.linkedin.com\/feed\/update\/urn:li:activity:7124401304315027456\">with a LinkedIn comment<\/a> I liked and wanted to share (done with permission):<\/p>\n\n<blockquote>\n  <p>In theory I can drive my car on the motorway, blind folded while not wearing a seat belt. It sounds really exciting and loads of fun. When something goes wrong it gets really messy.<\/p>\n  \n  <p>I tend to think of skipping automated tests in the same way.<\/p>\n<\/blockquote>\n\n<p>Just because you can do something, it doesn't mean you should.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "45269d5f607bea54f9ddd23fd5c84611",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json b/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json
index c7dee1a93..366f00c44 100644
--- a/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json
+++ b/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few years ago, I worked on an event booking and management website for a charity in the UK.<\/p>\n\n<p>One required piece of functionality was to allow event organisers to send a private message to all attendees of an event.<\/p>\n\n<p>We decided to use the <a href=\"https:\/\/www.drupal.org\/project\/private_message\">Private Message module<\/a> but were concerned about hitting memory limits or timeouts, as some events had several hundred attendees.<\/p>\n\n<p>We decided that we needed to use a queue and have it process and send the messages.<\/p>\n\n<p>This split the feature into three parts:<\/p>\n\n<ul>\n<li>The UI for event organisers to enter and send their messages.<\/li>\n<li>The queue that stores and processes pending messages in the background.<\/li>\n<li>The Private Message module that would create and send each message, provide an inbox for each user, and provide notifications.<\/li>\n<\/ul>\n\n<p>The UI for event organisers was specific to the project and had to be custom code and not open-sourced.<\/p>\n\n<p>The Private Message module is already a contributed module, but what about the queue part?<\/p>\n\n<p>This is why the <a href=\"https:\/\/www.drupal.org\/project\/private_message_queue\">Private Message Queue module<\/a> was created.<\/p>\n\n<p>Instead of keeping it within the project's custom code, we created it as an open-source module on Drupal.org.<\/p>\n\n<p>It contains no customer or project-specific information and only adds generic functionality - it creates a queue to hold private messages to be processed in the background.<\/p>\n\n<p>It provides the glue between our custom UI and the Private Message module.<\/p>\n\n<p>As there was no reason why we needed to keep it private, we made it public and developed it as its own project from the beginning instead of planning and hoping to do so later.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7b3d0e69e978e096200c927b708f8adf",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json b/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json
index ed16489dc..1296f39e1 100644
--- a/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json
+++ b/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was surprised to see this week that it\u2019s only two months until Drupal 10 is released (14th December 2022).<\/p>\n\n<p>I\u2019m starting a new Drupal development project in December so will be looking to get that on Drupal 10 as soon as possible.<\/p>\n\n<p>From the client\u2019s perspective, getting their new project on Drupal 10 and them not needing to upgrade from D9 in the future is a big plus, even if the code differences between D9 and D10 are not that big - similar to Drupal 8 and 9.<\/p>\n\n<p>As a module maintainer, it\u2019s been great to again see issues being created with automated Drupal 10 compatibility patches - thanks to Rector.<\/p>\n\n<p>It\u2019s great to see these regular updates and new versions of Drupal, but also for the PHP language, with PHP 7 being end-of-life next month.<\/p>\n\n<p>It\u2019s a big difference compared to the long-term releases that we had for Drupal 6 and 7, and PHP 5, but one that I definitely prefer.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "44047cd2087198d6d3e858acb4075cc2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json b/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json
index aaed9c62d..b5f11fa45 100644
--- a/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json
+++ b/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I built my <a href=\"http:\/\/default\/build-config\">Build Configs<\/a> tool because I only wanted to write a file once and re-use it instead of writing it over again or copying and pasting between projects.<\/p>\n\n<p>Having standardised templates for different languages and project types, I can easily set up new projects and get them running in a few minutes.<\/p>\n\n<p>If I need to add a feature or fix a bug, I can do it once in the Build Configs tool and easily regenerate the configuration files for all projects, and they'll all get the updated files.<\/p>\n\n<p>There's no \"I need to copy this feature from project A or this bug fix from project B.\" when starting on project C.<\/p>\n\n<p>As I only work on fixed-price engagements, it's in my interest to be able to create and maintain projects in a fast and efficient manner.<\/p>\n\n<p>The Build Configs tool enables me to do that.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a700ecf2a857dac7a210989faa80eb4d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json b/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json
index 8c9a2a91c..6fd478b30 100644
--- a/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json
+++ b/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently been writing a new custom module for a Drupal application.<\/p>\n\n<p>I needed to create a form populated with options from an API endpoint, submitted the form values to another API endpoint and display some results to the user.<\/p>\n\n<p>I'd architected and planned the steps I was going to need and knew how I was going to approach adding this new functionality.<\/p>\n\n<p>My first objective was to make it work.<\/p>\n\n<p>To get all the functionality in place so it was working as soon as possible with minimal distractions.<\/p>\n\n<p>This meant I would find any issues sooner rather than later and what I'd created could be reviewed and tested by stakeholders, regardless of how it looked.<\/p>\n\n<p>If needed, it could have been released at this point.<\/p>\n\n<p>It was working.<\/p>\n\n<p>Next, I did a second pass to make it good.<\/p>\n\n<p>I updated the markup and styled it to match the provided designs.<\/p>\n\n<p>I made small updates to terminology and messaging to ensure the tone of voice was correct and consistent with the rest of the application and various other small tweaks and improvements.<\/p>\n\n<p>I could do all this knowing the functionality was already working, and I could focus on making it good.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2bfadaccd342e33a28413aca4bbe6414",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json b/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json
index cca43def6..e66b97d32 100644
--- a/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json
+++ b/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There used to be a saying:<\/p>\n\n<p>If you want to build a website, use <enter cms name here>. If you want to build <cms name>, use Drupal.<\/cms><\/enter><\/p>\n\n<p>I think I've heard it used with all the other content management systems, and it isn't about saying one is better.<\/p>\n\n<p>It highlights that Drupal isn't just a content management system - it's a content management framework.<\/p>\n\n<p>A framework you use to build your content management system to meet your needs.<\/p>\n\n<p>Straight away after installing Drupal, you can create as many content types as you want with as many fields as you want to build as simple or complex a content model as you need.<\/p>\n\n<p>You aren't restricted to the default page and article content types or a fixed set of fields.<\/p>\n\n<p>That, along with Views - a built-in query builder to build pages and blocks of your content, user login and registration, and JSON:API to allow other applications, such as mobile apps, to access your data, to name a few things, makes Drupal a very powerful option.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "09e70a063c30cc59ead229e026e00f13",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json b/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json
index 14c560639..86320448b 100644
--- a/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json
+++ b/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2025\/02\/18\/conflicts\">causing merge conflicts<\/a>, feature branches slow the delivery of new features.<\/p>\n\n<p>Someone needs to be responsible for merging the branches once they've been reviewed and approved, and any further merges into release branches.<\/p>\n\n<p>This is typically the Lead Developer on the project, but this person then becomes a bottleneck.<\/p>\n\n<p>They need to oversee all the branches and merges, and know what needs to be merged and where it needs to be deployed.<\/p>\n\n<p>This slows down the speed of delivery.<\/p>\n\n<p>In a trunk-based environment, there's only one branch and everyone can commit and push to it.<\/p>\n\n<p>And, if you're <a href=\"http:\/\/default\/daily\/2025\/02\/17\/ci-cd\">doing continuous delivery<\/a>, any changes will be automatically deployed.<\/p>\n\n<p>No more bottleneck.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "abfbb6e640ea537c7cb537b44b7994ab",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json b/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json
index f1d0ebc76..0143844bd 100644
--- a/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json
+++ b/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After a trip away with the family earlier this week, I was happy to speak at the PHP London meetup yesterday evening.<\/p>\n\n<p>Following on from my previous \"Working from Workspace\" talk, I spoke about my current development setup for my personal and work laptops with Nix and NixOS, Linux, Neovim, tmux, just, Docker and more!<\/p>\n\n<p>Of course, I spoke about PHP, Drupal, and Symfony too as well as some of the work that we're doing at Transport for Wales.<\/p>\n\n<p>I learned that the call for papers for the PHP UK conference 2024 is already open so I'll definitely be submitting some proposals for next year's conference. Hopefully, I'll be back in London again before that.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "75435477d7a227a083c9be5742e6fd8e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json b/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json
index de6e769dd..126457804 100644
--- a/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json
+++ b/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>With Drupal 9 almost being end-of-life and unsupported, I've recently been doing a lot of Drupal 9 to 10 upgrade work.<\/p>\n\n<p>As it's a major version update, there are breaking changes that mean you may need to change your code.<\/p>\n\n<p>Here's an example of an error caused by a breaking change:<\/p>\n\n<blockquote>\n  <p>Drupal\\Core\\Entity\\Query\\QueryException: Entity queries must explicitly set whether the query should be access checked or not. See Drupal\\Core\\Entity\\Query\\QueryInterface::accessCheck().<\/p>\n<\/blockquote>\n\n<p>To fix this, you need to call the <code>accessCheck()<\/code> method before executing a query and specify whether it should be checked.<\/p>\n\n<p>But how do you know if it should be checked?<\/p>\n\n<p>If you have automated tests that pass beforehand and still pass afterwards, you picked the correct option.<\/p>\n\n<p>If the test passes before and fails afterwards, you found the bug and can fix it immediately to ensure the functionality works as before.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e6ccad714f421e19ca6bf59a5f2c224c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json b/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json
index e68d43bdb..46a507b9b 100644
--- a/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json
+++ b/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tailwind CSS is based on the \"utility-first\" approach, where the majority of styling is done using utility CSS classes. You can still add additional custom styles if needed if there is something that can't be achieved with utilities or would be better placed in a custom CSS stylesheet.<\/p>\n\n<p>Utility-last is the opposite approach, where a small number of utilities are used alongside other CSS styles or another framework. This is common when <a href=\"http:\/\/default\/daily\/2023\/01\/05\/adding-tailwind-to-an-existing-project\">adding a utility-based framework like Tailwind CSS<\/a> to an existing project and you want to use it for a new page or component whilst keeping the existing styles.<\/p>\n\n<p>This is what I did when I started learning Tachyons, and later Tailwind CSS. My project already had styling from another CSS framework, I started using utility classes and over time refactored until only utilities were used and the other styles could be removed.<\/p>\n\n<p>You could do the opposite too, and refactor groups of utilities into a CSS component, either by using Tailwind's <code>@apply<\/code> directive or <a href=\"http:\/\/default\/daily\/2023\/01\/03\/tailwind-css-extensibility-is-one-of-its-best-features\">writing a plugin<\/a>.<\/p>\n\n<p>If you did want to use Tailwind for a small number of utilities, by default, it will only generate classes that are used within HTML or template files, but it can also be configured to only use the core modules that you specify - preventing Developers from using unwanted utility based on the rules for that project.<\/p>\n\n<p>You could, of course, write your own utilities, or they're becoming common in other frameworks now too for things like padding, margin and colours.<\/p>\n\n<p>Do you typically do styling utility-first or utility-last, or are you transitioning from one to the other?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e15b57a5fdb50483f2e7b2a23d0fbf8c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json b/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json
index 63777d5f2..4f8c9476d 100644
--- a/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json
+++ b/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In January, I wrote about <a href=\"http:\/\/default\/daily\/2025\/01\/03\/todotxt\">using plain text files for to-do lists<\/a> instead of larger and more complex project management tools.<\/p>\n\n<p>I found an example of this in the code repository for st, <a href=\"https:\/\/st.suckless.org\">the simple terminal from suckless.org<\/a>.<\/p>\n\n<p>They have a <a href=\"https:\/\/git.suckless.org\/st\/file\/TODO.html\">TODO.html file<\/a> which is a plain text list of todo tasks.<\/p>\n\n<p>There are <a href=\"https:\/\/github.com\/search?q=path%3Atodo.txt+OR+path%3Atodo.md+OR+path%3Atodo.html&amp;type=code\">a lot of examples on GitHub<\/a>, too.<\/p>\n\n<p>Something I like in st's file is this command:<\/p>\n\n<pre><code class=\"plain\">grep -nE 'XXX|TODO' st.c\n<\/code><\/pre>\n\n<p>This finds TODO comments in the st.c file so those can be included.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dce9edad7a35465af5401069bf3d75cd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json b/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json
index 0170e8196..14d111edb 100644
--- a/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json
+++ b/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Similar to \"a method should only have one return statement\", I've seen similar advice when working with tests: \"Tests should only have a single assertion\".<\/p>\n\n<p>I don't think this is true, and in my experience, you need multiple assertions to have a thorough test.<\/p>\n\n<p>And, whilst similar assertions add some duplication, they can make the intent clearer and give better error messages.<\/p>\n\n<p>Instead, I focus on one test case per test.<\/p>\n\n<p>If I'm testing the following:<\/p>\n\n<ul>\n<li>A blog page exists.<\/li>\n<li>Only post nodes are visible.<\/li>\n<li>Only published posts are visible,<\/li>\n<li>Posts are returned in a specified order.<\/li>\n<\/ul>\n\n<p>These will be split into separate tests - making it easier to read and maintain the code and have faster execution times by running only the tests I want with the minimum amount of code in each - regardless of how many assertions are in each.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2961539db053ecb851f7ff74172acc9b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json b/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json
index 268989508..617705b6e 100644
--- a/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json
+++ b/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In my <a href=\"http:\/\/default\/talks\/tdd-test-driven-drupal\">Test-Driven Drupal talk slides<\/a>, I show a screenshot of a tweet from February 2012 by Tim Millwood asking if anyone wanted to maintain the Override Node Options module.<\/p>\n\n<p>I said yes and took over maintainership.<\/p>\n\n<p>In April 2012, the module was installed on 9,212 Drupal websites - just over 7,000 Drupal 6 websites and just over 2,000 Drupal 7 websites.<\/p>\n\n<p>Before DrupalCon Lille, the module was used on 38,096 websites and was 173rd in the most used modules.<\/p>\n\n<p>As of the 3rd of March, the Override Node Options module is used on 40,624 Drupal websites and is up to the 169th most used module.<\/p>\n\n<p>That's pretty cool!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ee421350e08042bf1dc38655f1c7358b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json b/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json
index 13ef2daaa..97b7db6d5 100644
--- a/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json
+++ b/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been a Developer for 15 years and one thing that I've always focussed on is to always keep learning.<\/p>\n\n<p>From starting as a self-taught Developer, initially learning HTML and CSS, to later learning PHP and Drupal as well as other languages, frameworks and tools.<\/p>\n\n<p>For the last couple of days, I've been experimenting with Next.js - a React-based web framework. I hadn't used React before and have typically reached for Vue.js or sometimes Alpine.js based on what I needed to do. However, I'm always looking for opportunities to learn and implement new things, and see how I can use them in any of my projects.<\/p>\n\n<p>This afternoon, I started a new Next.js and TypeScript project, and refactored a small codebase that used a static site generator to create a small number of landing pages from Markdown files.<\/p>\n\n<p>It took me a short time to set up a Docker environment for it based on some of my Vue.js projects, ported across the application to recreate the pages, and finally, updated the CI pipeline that generated the static pages and uploaded them to an S3 bucket.<\/p>\n\n<p>The end result is the same - the same HTML pages are generated and uploaded - but, for me, trying and experimenting with new things keeps my work interesting and my knowledge fresh, which benefits me as well as my colleagues and clients.<\/p>\n\n<p>As I said in a previous email, one of the great things about software development is that there's always something new to learn.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a0bc3463255d3adc14c37179d7838fec",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json b/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json
index c18dc3b55..e3fc98fc4 100644
--- a/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json
+++ b/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Rarely you're going to find a module that does exactly what you need out of the box.<\/p>\n\n<p>Usually there will be some configuration options, or it will get you to 80% or 90% and you need to fill in any gaps.<\/p>\n\n<p>If you need to extend, overwrite or customise a module, have its Developers made it possible or easy to do that?<\/p>\n\n<p>Good code should be easy to change or extend.<\/p>\n\n<p>Are there hooks you can implement or events you can subscribe to and run your own code?<\/p>\n\n<p>Are there Interfaces and base classes you can implement or extend that allow you to use design patterns such as the Decorator pattern?<\/p>\n\n<p>Are there public services you can use instead of re-writing and duplicating existing functionality?<\/p>\n\n<p>Is there documentation or examples showing how to extend the module?<\/p>\n\n<p>Is it a stable foundation for you to build on?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8e4c0c829c59ed32febbb0b3c5be9acf",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json b/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json
index 301132468..aea363241 100644
--- a/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json
+++ b/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>\"Modular monolith\" has been a popular phrase in the PHP community recently with talks, podcast episodes and courses released on the topic.<\/p>\n\n<p>The idea is that instead of all the code being in one namespace, like App, it's split into different modules such as for payments or a blog - whatever is relevant and appropriate for that application.<\/p>\n\n<p>Each module contains its own classes and structure instead of everything being mixed together.<\/p>\n\n<p>If you want to change something about payments, you go to the payments module and you don't need to worry about anything else.<\/p>\n\n<p>What's interesting is that this is how I've always built Drupal applications.<\/p>\n\n<p>Each includes Drupal core and any contributed modules installed via Composer, and a specific directory for application-specific custom modules.<\/p>\n\n<p>These modules can be separate and standalone or they can interact and have dependencies and sub-modules.<\/p>\n\n<p>Each has its own routes, services, tests and more, making them easy to organise and maintain compared to having all the custom code in one large monolithic namespace or module.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "839ad892ec2adbc5d9a97cf4d798231f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json b/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json
index 88535316a..0c5de54c4 100644
--- a/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json
+++ b/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The answer to \"<a href=\"http:\/\/default\/daily\/2023\/05\/01\/should-drupal-7-support-be-extended-again\">Should Drupal 7 support be extended again?<\/a>\" might depend on who you ask.<\/p>\n\n<p>If you ask a Developer or agency, the answer would likely be that it shouldn't be extended again, and D7 should be sunsetted.<\/p>\n\n<p>Clients and end-users who haven't yet upgraded would likely say it should be extended.<\/p>\n\n<p>But if it's extended - and maybe again next year and the next - where's the incentive to upgrade?<\/p>\n\n<p>Some people won't upgrade regardless and will continue until their site breaks.<\/p>\n\n<p>That would be messy (and costly) to fix, though!<\/p>\n\n<p>P.S. Are you still using Drupal 7 and don\u2019t know what\u2019s involved to upgrade to Drupal 10? Book a <a href=\"http:\/\/default\/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "74278f8a549e0bdb4602dfed3099d077",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json b/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json
index 6759ea359..c0706dabb 100644
--- a/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json
+++ b/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In software development, there are usually multiple ways to achieve the same result.<\/p>\n\n<p>There is no one \"right\" answer.<\/p>\n\n<p>You can make a website look the same if you write the CSS by hand or use a framework.<\/p>\n\n<p>When writing backend code, you could use design patterns and follow good clean code practices or not.<\/p>\n\n<p>How you approach a solution depends on your experience and perspective, but one approach isn't wrong when compared to another if they achieve the same result.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>This is why I like pair and mob programming.<\/p>\n\n<p>Everyone involved can discuss, plan and contribute to a solution in real-time.<\/p>\n\n<p>You're more likely to get a better and more thought-out and robust solution from the collective perspective and experience compared to working individually, with the added benefit that more than one person understands the solution if it needs to be extended or changed in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "43c6e609caa1eda4abbb11aab70e8141",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json b/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json
index 58c102a98..ca877d65d 100644
--- a/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json
+++ b/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How do you release a new project?<\/p>\n\n<p>Do you build everything and release everything at once?<\/p>\n\n<p>I've used the strategy of building and releasing it a page at a time and running two versions simultaneously.<\/p>\n\n<p>The main live version stays running, and you use a tool like NGINX or Cloudflare as a gatekeeper to direct traffic to the correct application - either the current one or the new one - based on the requested page.<\/p>\n\n<p>When a page is ready, you add it to the list of pages to serve from the new application to put it live.<\/p>\n\n<p>If there's an issue, it is also easy to revert to the original page.<\/p>\n\n<p>I've used this approach with my website and for client Drupal upgrade projects, where some pages are on Drupal 7 and some on Drupal 10.<\/p>\n\n<p>It's not the right approach for every situation, but it's a useful one to have in the toolkit.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2362356e8d2f3a9cef83ebd18dc9bf11",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json b/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json
index f1bdce5d5..85af6d680 100644
--- a/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json
+++ b/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Here's another <code>run<\/code> file example, this time relating to Git worktrees...<\/p>\n\n<p>One project that I work on is a multilingual Drupal application that needs to work in both English and Welsh. As I'm cloning a fresh version today, I'm doing it as a bare repository so I can use worktrees.<\/p>\n\n<p>To work on it locally, just like in production, I need to use a different URL for each language so that Drupal can identify it and load the correct content and configuration.<\/p>\n\n<p>For fixed environments like production or staging, the URLs are set in configuration files, but for ad-hoc environments such as local worktrees, I thought that the best approach was to override them as needed per worktree using Drush (a Drupal CLI tool).<\/p>\n\n<p>I could do this manually each time or I could automate it in a <code>run<\/code> command. :)<\/p>\n\n<p>Here's the function that I came up with:<\/p>\n\n<pre><code class=\"bash\">function drupal:set-urls-for-worktree {\n  # Set the site URLs based on the current Git worktree name.\n  local worktree_name=\"$(basename $PWD)\"\n\n  local cy_url=\"cy-projectname-${worktree_name}.docker.localhost\"\n  local en_url=\"projectname-${worktree_name}.docker.localhost\"\n\n  # Update the URLs.\n  drush config:set language.negotiation url.domains.cy -y $cy_url\n  drush config:set language.negotiation url.domains.en -y $en_url\n\n  # Display the domains configuration to ensure that they were set correctly.\n  drush config:get language.negotiation url.domains\n}\n<\/code><\/pre>\n\n<p>It builds the worktree URL for each language based on the directory name, executes the configuration change, and finally displays the updated configuration so I can confirm that it's been set correctly.<\/p>\n\n<p>This is a good example of why I like using <code>run<\/code> files and how I use them to automate and simplify parts of my workflow.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1d0346a7d6dd5cac3b65b148563e58b2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json b/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json
index ce36d2c6d..97e217262 100644
--- a/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json
+++ b/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The Boy Scout rule is \"Always leave the campground cleaner than you found it\".<\/p>\n\n<p>From a programming perspective, \"Always leave the code better than you find it\".<\/p>\n\n<p>If you're working on some code and see some commented-out lines or unused variables, once you've finished with your changes, remove them too.<\/p>\n\n<p>If there's a variable that could have a more descriptive name, change it.<\/p>\n\n<p>If there are any other refactors you can do, do them and leave the code better than before and easier for the next Developer (whether it's you or someone else) to work with.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f37cca5f2692bfc4e92b042590c4cab1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json b/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json
index 7b6ceef71..344302e90 100644
--- a/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json
+++ b/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've written emails before about continuous delivery and continuous deployment, but there's another \"continuous\" I like to follow.<\/p>\n\n<p>Continuous <strong>improvement<\/strong>.<\/p>\n\n<p>Always focusing on improving, whether learning new things or getting better with things I already know.<\/p>\n\n<p>If you haven't written automated tests or done test-driven development before, try it.<\/p>\n\n<p>Try using static analysis tools if you haven't before.<\/p>\n\n<p>If your tools or approaches are outdated, try something more modern.<\/p>\n\n<p>Can you reduce the time your CI pipeline takes to run, or write better documentation?<\/p>\n\n<p>You may not like everything you try, but what works will pay dividends over time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "805afbbb39c5208d4da98592167360a8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json b/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json
index 2c72a7831..cc70c8d4b 100644
--- a/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json
+++ b/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I had some early presents this month and have been accepted to present talks at the new PHP Stoke meetup and the Norfolk Developers Conference.<\/p>\n\n<h2 id=\"php-stoke\">PHP Stoke<\/h2>\n\n<p>The first PHP Stoke meetup will be held at Genr8 Smithfield Works on the 12th of January. I'll be presenting \"<a href=\"http:\/\/default\/presentations\/things-you-should-know-about-php\">Things you should know about PHP<\/a>\". It'll be great to be the first speaker at this new meetup.<\/p>\n\n<h2 id=\"nordev%3Acon\">nor(DEV):con<\/h2>\n\n<p>The Norfolk Developers conference is in Norwich on the 23rd and 24th of February.<\/p>\n\n<p>I'll be presenting \"<a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">Taking Flight about Tailwind CSS<\/a>\". It's been a while since I last gave this talk so I'm looking forward to updating it with the latest changes and new features in Tailwind CSS.<\/p>\n\n<p>It'll be great to be speaking at these events and hopefully others in 2023.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ec096cce9917022d9b2ba1ebcdde5a0e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json b/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json
index 553b3ec5c..02d9cd73a 100644
--- a/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json
+++ b/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few days ago, I mentioned <a href=\"http:\/\/default\/daily\/2025\/02\/03\/testable\">a method that was over 150 lines long<\/a>.<\/p>\n\n<p>It had too many responsibilities, nested conditions, no dependency injection and no tests.<\/p>\n\n<p>Changing it would be risky, so how would I go about it?<\/p>\n\n<p>Let's assume I have this PHP method that contains the existing logic:<\/p>\n\n<pre><code class=\"php\">function doSomething() {\n  \/\/ 150 lines of legacy code...\n}\n<\/code><\/pre>\n\n<p>I can create a new class that's clean and simple, with whatever automated tests and checks I want.<\/p>\n\n<p>Let's say it has an <code>execute()<\/code> method that returns a boolean value:<\/p>\n\n<pre><code class=\"php\">class NewService {\n\n  public function execute() {\n    return TRUE;\n  }\n\n}\n<\/code><\/pre>\n\n<p>Because it's been tested in isolation, we can be confident it works as needed, so I can use it in the legacy function.<\/p>\n\n<p>I want to try and find a seam where I can use the new service and check for a result.<\/p>\n\n<p>Ideally, this would be as soon as possible within the function:<\/p>\n\n<pre><code class=\"php\">function doSomething() {\n  $newResult = $this-&gt;newService-&gt;execute();\n\n  if ($newResult) {\n    return $newResult;\n  }\n\n  \/\/ 150 lines of legacy code...\n}\n<\/code><\/pre>\n\n<p>If the new service returns a result, use it and return early, and don't execute the legacy code.<\/p>\n\n<p>Otherwise, run the original code as it would have been before, falling back to the original logic and result.<\/p>\n\n<p>Over time, more logic can be migrated into the new service until the legacy code is no longer used and can be removed.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Writing tests for legacy code can be difficult or sometimes impossible.<\/p>\n\n<p>This approach means new code can be written using tests and test-driven development, dependency injection and whatever else you want without being limited by the existing code.<\/p>\n\n<p>You can incrementally migrate to the new approach and refactor out the old code, making it less risky than an all or nothing approach.<\/p>\n\n<p>Do you do the same thing or do you handle legacy code in a different way?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "18f69e8494cd5de71961a506175181f4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json b/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json
index b94f84008..4e1f1e080 100644
--- a/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json
+++ b/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This is a common question from people starting to write automated tests in PHP:<\/p>\n\n<blockquote>\n  <p>Should I use PHPUnit or Pest PHP?<\/p>\n<\/blockquote>\n\n<p>I've used both.<\/p>\n\n<p>They both have pros and cons.<\/p>\n\n<p>If you're familiar with JavaScript and Jest, Pest would probably be a natural fit.<\/p>\n\n<p>If you're used to writing classes in PHP, PHPUnit may feel more familiar.<\/p>\n\n<p>Use whichever appeals to you.<\/p>\n\n<p>Maybe try both and see which you prefer.<\/p>\n\n<p>The main benefit will be you have tests, whichever you decide to use.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "863a73768ac75bc3880484ce14aa5d49",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json b/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json
index ae080f6d2..5a7150d47 100644
--- a/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json
+++ b/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Software should be designed, written, and deployed in small batches.<\/p>\n\n<p>This is the first line from a blog post by Eric Ries and is something that gets discussed with a guest in an upcoming episode of the Beyond Blocks podcast.<\/p>\n\n<p>In the post, Eric continues by saying, \"Of all of the insights I've contributed to the companies I've worked at over the years, the one I am most proud of is the importance of working in small batches\".<\/p>\n\n<p>Small batches mean faster feedback, more localised problems as there are fewer changes, and reduced risk and overhead.<\/p>\n\n<p>If you work in small batches and make smaller changes, merge them regularly into the mainline branch (ideally, at least once a day), and often deploy changes to production, the releases will be quicker and less stressful, and clients and customers will be happy as their changes will be available sooner.<\/p>\n\n<p>I've worked this way, and with long-lived feature branches and large, infrequent deployments, I prefer to work in small batches and deploy often.<\/p>\n\n<p>The full blog post is found at <a href=\"http:\/\/www.startuplessonslearned.com\/2009\/02\/work-in-small-batches.html\">http:\/\/www.startuplessonslearned.com\/2009\/02\/work-in-small-batches.html<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8c51b1ac3a2223e3279ac9e4bcc51f58",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json b/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json
index 298af4987..a3bce68a9 100644
--- a/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json
+++ b/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I've been asked before is \"Do you need permission to write automated tests or do Test-Driven Development?\".<\/p>\n\n<p>A response I heard recently was \"Does a surgeon ask if they can wash their hands before operating?\".<\/p>\n\n<p>The same as when I take my car to a garage, I expect the mechanic to do the appropriate diagnostic, repair work and testing to make it's working correctly and safely.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d03c32cba85beb76c8e0e111e3ae1d52",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json b/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json
index 8ff272c7d..fe3cacff0 100644
--- a/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json
+++ b/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whenever you need to start a new task in a codebase, I think it's important to always try to start with a clean slate.<\/p>\n\n<p>This is having an empty staging area and no lingering or uncommitted changes from previous tasks.<\/p>\n\n<p>I do this to avoid having contaminated commits that contain multiple changes. Each commit should be related to one change.<\/p>\n\n<p>You can use <code>git add -p<\/code> to <a href=\"http:\/\/default\/daily\/2024\/10\/25\/always-review-your-changes\">review, stage and commit parts of your changes<\/a>, but as the uncommitted changes grow, you're less likely to do that and more likely to commit them at once with a generic commit message that offers no value when viewed in the commit log.<\/p>\n\n<p>You're more likely to create better and more valuable commits and write better commit messages if you break them into chunks and commit the changes as you make them.<\/p>\n\n<p>If you have extra files you don't want to commit, add them to a <code>.gitignore<\/code> file or <code>.git\/info\/exclude<\/code> so they're ignored.<\/p>\n\n<p>If you have uncommitted changes that you want to hide for now but re-add later, <a href=\"http:\/\/default\/daily\/2024\/10\/24\/git-stash-is-underrated\">git stash is your friend<\/a>.<\/p>\n\n<p>If you want your changes to be completely separate, maybe <a href=\"http:\/\/default\/daily\/2022\/08\/12\/git-worktrees-docker-compose\">git worktrees are for you<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1b329f24d5fcdb46e236911745ece2dc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json b/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json
index 272ef8486..4fd6c44ee 100644
--- a/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json
+++ b/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, <a href=\"http:\/\/default\/daily\/2022\/08\/29\/why-like-drupal\">I shared some of the reasons<\/a> why I like Drupal and why I use it for the majority of my projects. But, as I said, I don't use it exclusively and for some projects I used various different tools.<\/p>\n\n<p>Essentially, I always try to recommend and use the best tool for the job.<\/p>\n\n<p>I previously interviewed for a job and was asked to complete a coding test. The role was mostly Drupal-focussed, but as the test asked for a command-line application, I completed it using Symfony and Symfony Console, and was able to discuss why I'd made that decision. In my opinion, it was the best choice based on the requirements.<\/p>\n\n<p>This is the same approach that I use when making recommendations for a new project.<\/p>\n\n<p>I've delivered projects using other tools like the Symfony framework or a static site generator, as long as it fitted the requirements.<\/p>\n\n<p>If there's a SaaS solution that can be used instead, or an off-the-shelf tool that can be integrated instead of writing a custom solution, then that should be evaluated.<\/p>\n\n<p>There may be other constraints like budgets or deadlines to consider - maybe something can be delivered faster or cheaper using a particular technology, even if it's not the final solution.<\/p>\n\n<p>There are situations though where a tool may be the best choice even though it's not the ideal fit based purely on the technical requirements. Maybe the client is already familiar with publishing content in Drupal, or an in-house development team is used to working with a certain tool or language. In that case, those things should be considered too.<\/p>\n\n<p>Also, for me, having a chance to evaluate other technologies and explore what's happening outside of the Drupal ecosystem is a good opportunity. A lot of what I've learned about automated testing, for example, is from the wider PHP and JavaScript communities, as well as tools like <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">Tailwind CSS<\/a> and <a href=\"http:\/\/default\/presentations\/using-illuminate-collections-outside-laravel\">Illuminate Collections<\/a> that I've been able to bring back into my other Drupal projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "61a5f029b181771294db67f4654ec590",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json b/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json
index c0d863f32..7e4fb7150 100644
--- a/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json
+++ b/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Recently, when speaking with prospective clients, instead of focusing on the features they want, I like to ask questions like:<\/p>\n\n<p>What's wrong with what you have now?<\/p>\n\n<p>Why not fix what you have instead of rebuilding?<\/p>\n\n<p>What problem are you trying to solve?<\/p>\n\n<p>Why write software for this at all?<\/p>\n\n<p>Why not do it manually?<\/p>\n\n<p>Why do you need to do this now?<\/p>\n\n<p>What results would you expect to see after this project?<\/p>\n\n<p>If they can answer these types of questions and explain the business outcomes they're looking to achieve and what value I can add, those are the projects I want to work on.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e52d296563e9560ea0b8d1060cc77506",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json b/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json
index 0e5344de2..2627496ff 100644
--- a/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json
+++ b/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In yesterday's email, I wondered <a href=\"http:\/\/default\/daily\/2024\/11\/07\/should-drush-be-in-drupal-core\">whether Drush should be added to Drupal core<\/a>.<\/p>\n\n<p>I've used Drush for as long as I've used Drupal so, to me, it would be an obvious thing to consider.<\/p>\n\n<p>The Pathauto module is another thing that I use on every Drupal project and could be another good candidate.<\/p>\n\n<p>With the recent Starshot initiative and recently-named \"Drupal CMS\" project, could we see things like these added to that if not to Drupal core?<\/p>\n\n<p>It'll be interesting to see how both the Drupal and Drupal CMS projects evolve, what will be the same and what will be different.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e58c1b76ed53979d349c848dc1c6d475",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json b/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json
index b8e76639e..c4efc63f3 100644
--- a/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json
+++ b/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Over the last few days, I've written about watchers and running commands such as automated tests when files are changed.<\/p>\n\n<p>Some tools have this built in, whilst others don't.<\/p>\n\n<p>I've used different tools to do this and recently switched to <code>entr<\/code>.<\/p>\n\n<p>The previous one wasn't showing me the output from running Drupal automated tests, which <code>entr<\/code> does.<\/p>\n\n<p>I also like that it follows the UNIX philosophy of doing one thing well and working well with other programs.<\/p>\n\n<p>For example, to run my automated tests when I change a file, I need to run <code>find web\/modules\/custom | entr .\/run test<\/code>.<\/p>\n\n<p><code>entr<\/code> isn't concerned with how to find the list of files to watch - only what to do with them.<\/p>\n\n<p>To get the list of files, I use the <code>find<\/code> command and provide the files to <code>entr<\/code>.<\/p>\n\n<p>I also like to do this with my application code. I like to write small modules and libraries with clear boundaries and responsibilities, do their tasks well, and work well with other parts of the application.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "56cd66100b039fcf69f6ebcd06176a9b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json b/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json
index 2b75486d6..6648812bf 100644
--- a/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json
+++ b/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, Drupal 10.3 was released.<\/p>\n\n<p>It's the final feature release of Drupal 10, with Drupal 11 to be released this year.<\/p>\n\n<p>As it's a minor release, it provides improvements and new functionality and does not break backward compatibility (BC) for public APIs, so it should be easy to upgrade from Drupal 10.2.<\/p>\n\n<p>An interesting change is that you <strong>need to upgrade to Drupal 10.3 prior to upgrading to Drupal 11<\/strong>. This is similar to Symfony's upgrade cycle and will make upgrading to Drupal 11, which will be refined version of Drupal 10 with a very similar public API, much easier.<\/p>\n\n<h2 id=\"what-about-drupal-10.4\">What about Drupal 10.4<\/h2>\n\n<p>There will still be a Drupal 10.4 release in December, and will be the first maintenance minor version, receiving limited forward-compatible and security fixes only, and will be supported until the release of Drupal 12 in 2026.<\/p>\n\n<p>It's great to see the project evolve, and I'm looking forward to upgrading my projects to Drupal 10.3 and then 11 in the near future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9ab0b186e8be83ec48f221f864037954",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json b/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json
index 661473b2b..894b26560 100644
--- a/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json
+++ b/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A question I ask before starting a task, whether I'm working solo or as part of a team is \"What is your plan?\".<\/p>\n\n<p>How am I going to approach the task I'm about to start working on?<\/p>\n\n<p>What information do I need?<\/p>\n\n<p>What approach am I going to take and which am I not going to take?<\/p>\n\n<p>What will some of the&nbsp;puzzle pieces be? Will I need a route, a Controller, a Service, a Command, a Value Object?<\/p>\n\n<p>Asking these questions and making these initial decisions upfront greatly reduces my implementation time as I only need to focus on delivering what I've already planned.<\/p>\n\n<p>And I can <a href=\"http:\/\/default\/daily\/2023\/11\/09\/readme-driven-development\">capture these decisions in a README file<\/a> <a href=\"http:\/\/default\/daily\/2024\/09\/04\/diagram-driven-development\">or diagram<\/a>, that's ideal.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9c34aa974d9627eacb1aee7476f85467",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json b/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json
index 4abee67db..de71fee1a 100644
--- a/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json
+++ b/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you're adding Tailwind CSS to your existing project or can't use atomic\/utility classes straight away, the <code>@apply<\/code> directive might be an option.<\/p>\n\n<p>It's a way to extract components within CSS using the same classes you'd add to the element.<\/p>\n\n<p>Here's a quick example:<\/p>\n\n<pre><code class=\"css\">.btn {\n  @apply py-3 px-6 bg-red text-white hover:bg-green focus:bg-green;\n}\n<\/code><\/pre>\n\n<p>It works with interaction states, such as hover and focus states, too.<\/p>\n\n<p>It's not something I use or recommend often, but it could be a good way to get started.<\/p>\n\n<p>Just don't overuse it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cd5a2930ef6ca83b078b4effc46de01f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json b/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json
index a125ad8ee..fd1d88aed 100644
--- a/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json
+++ b/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The other day, <a href=\"http:\/\/default\/daily\/2024\/05\/21\/which-commit-has-the-largest-message\">I posted about a script I'd written<\/a> that found the longest commit message in a repository.<\/p>\n\n<p>As I couldn't find a native way to do this with Git, the script loops over each commit in the repository, calculates its length and stores the length and commit SHA in a file.<\/p>\n\n<p>The lines in the file are sorted so the longest commit is first.<\/p>\n\n<p>Whilst I commonly use short parameters, such as <code>git add -p<\/code> when typing commands, in scripts, I prefer to use the equivalent longer parameters, where possible.<\/p>\n\n<p>For example, in the script, I execute this command to sort the lines:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" --reverse --numeric-sort --output \"${result_file}\"\n<\/code><\/pre>\n\n<p>This could be re-written as:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" -rn -o \"${result_file}\"\n<\/code><\/pre>\n\n<p>Whilst the original is more verbose and longer to type, I prefer its verbosity which makes it easier for me or others to read and understand in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "345a3eeaf689f5cb4490ec578563ae9f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json b/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json
index c9bd1427a..c81202b49 100644
--- a/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json
+++ b/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The video of the most recent version of my <a href=\"http:\/\/default\/presentations\/building-static-websites-sculpin\">Building static websites with PHP and Sculpin<\/a> from February's PHP South West meetup <a href=\"https:\/\/youtu.be\/axy6ltc9meA?si=FtR4DZ5BVi_Se60J\">has been released<\/a>.<\/p>\n\n<p>In the talk, I explain what Sculpin is and how it works before a live demo where I rebuild part of the PHPSW website (which I worked on originally).<\/p>\n\n<p>If you have any feedback or questions, reply to this email and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a8eb871985cb8c2f459c3aa07acaacb5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json b/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json
index da6bc0a7f..f0c3f85e8 100644
--- a/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json
+++ b/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When you start a new project, when should you start writing tests and doing test-driven development?<\/p>\n\n<p>Is it before you write any code, or is it something you can start later?<\/p>\n\n<p>When starting <a href=\"http:\/\/default\/daily\/2024\/02\/19\/introducing-versa\">versa<\/a>, I was only scaffolding the console commands and running some basic commands such as \"composer install\" and \"phpunit\".<\/p>\n\n<p>At that point, there wasn't any business logic to test.<\/p>\n\n<p>The first versions only supported PHP, so there was no complexity around which language the project used.<\/p>\n\n<p>There was no logic to determine which language or package manager was used.<\/p>\n\n<p>Now I've started to add this functionality - such as determining the project type from its composer.json or package.json file - there is logic to test, and I've started to write tests and do test-driven development.<\/p>\n\n<p>At this phase, I can see the value, which I couldn't when setting up the application to begin with, and different have any logic worth testing.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1579ff874773390b1129bfc1dc1f1c57",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json b/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json
index e4e988948..26fde0e9c 100644
--- a/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json
+++ b/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I wrote how to create <a href=\"http:\/\/default\/daily\/2025\/03\/29\/collections\">dependency free Collection classes in PHP<\/a> (thanks to Dan Leech).<\/p>\n\n<p>I said that <a href=\"http:\/\/default\/blog\/using-laravel-collections-drupal\">I've written blog posts<\/a> and <a href=\"http:\/\/default\/presentations\/using-illuminate-collections-outside-laravel\">given talks<\/a> on using Collection classes.<\/p>\n\n<p>But why do I like Collections and why may you want to use them instead of native arrays?<\/p>\n\n<p>The first reason is that I can add extra functionality to Collections, because they're objects.<\/p>\n\n<p>Whether it's a generic action such as filtering or sorting the items, or something more specific like returning a list of station codes from a collection of train stations, this can be added to specific collection classes.<\/p>\n\n<p>I'll usually have an <code>AbstractCollection<\/code> that has the generic methods and is extended by specific Collection types with methods more specific methods.<\/p>\n\n<p>Having specific types of Collection objects also gives my code more context.<\/p>\n\n<p>Instead of an array that could contain anything, by reading the code and seeing which Collection types are used, I know what the collection contains and what I can do with it.<\/p>\n\n<p>This is also why I like value objects.<\/p>\n\n<p>Giving objects specific names instead of relying on the language's primitive types makes the code more robust and easier to read and understand.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9ed6c1d39227210765b7041449aae5f5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json b/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json
index 6e6beff20..02d163dd4 100644
--- a/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json
+++ b/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I'm starting my own podcast - <a href=\"http:\/\/default\/podcast\">Beyond Blocks<\/a>.<\/p>\n\n<p>I'll be interviewing different people in every week, focussing on Drupal and related software development topics.<\/p>\n\n<p>I have the first guests lined up, including some speakers from last month's DrupalCon Europe conference, where we can discuss their topics in more detail.<\/p>\n\n<p>If you'd like to be a guest, <a href=\"https:\/\/forms.gle\/wdVqmEyQSWUx8cnm8\">get in touch<\/a> and let me know what you'd like to discuss.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d8d0de266333d29f23f7994cb8acb4d0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json b/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json
index 95f041a2d..5200ea598 100644
--- a/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json
+++ b/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This is how I first started writing automated tests.<\/p>\n\n<p>I was working at a well-known digital agency, so I didn't want it to affect my output and cause me to deliver work late.<\/p>\n\n<p>I wanted to give myself a less pressured opportunity to learn and experiment with different options and approaches.<\/p>\n\n<p>So, when creating custom modules, I wrote the implementation code during billable work hours and the tests during the evening on my own time.<\/p>\n\n<p>I was investing time in learning a new skill and one that I knew would pay dividends.<\/p>\n\n<h2 id=\"how-did-it-go%3F\">How did it go?<\/h2>\n\n<p>As I'd already written the implementation code, I wasn't doing test-driven development, so most of the tests were confirming what I'd written was correct with a passing test and being able to make it fail in expected ways.<\/p>\n\n<p>One time, though, I found a bug I'd written that day. I think it was an incorrect permission name I'd typed.<\/p>\n\n<p>I was able to fix it before it was submitted for quality assurance checks and client testing.<\/p>\n\n<p>This saved the time and effort of creating another issue and branch, fixing it, going through the development cycle again and having it re-tested.<\/p>\n\n<p>After that, for me, there was no going back.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "400db55c8a1b2bec187c987a57a19658",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json b/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json
index 808f48a99..9e20e71a9 100644
--- a/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json
+++ b/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been looking for a solution for storing and backing up the videos from <a href=\"https:\/\/youtube.com\/@opdavies\">my YouTube channel<\/a>.<\/p>\n\n<p>Then, I found Peertube.<\/p>\n\n<p>A distributed platform for hosting and sharing videos - similar to Mastodon.<\/p>\n\n<p>I've found Peertube instances created by other YouTubers like <a href=\"https:\/\/videos.lukesmith.xyz\">lukesmithxyz<\/a> and <a href=\"https:\/\/tinkerbetter.tube\">Veronica Explains<\/a>.<\/p>\n\n<p>Now <a href=\"http:\/\/default\/homelab\">my homelab is up and running<\/a> and I'm self-hosting production services like this website and my Forgejo instance, I wanted to host my own Peertube instance to back up my videos and provide an alternative place for people to watch them.<\/p>\n\n<p>I'm using NixOS for my homelab, which has options for Peertube, so setting it up was easily.<\/p>\n\n<p>My homelab configuration is public in my <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/nix-config\">nix-config<\/a> directory, so you can see how I have configured it.<\/p>\n\n<p>You can also see the videos on my Peertube at <a href=\"https:\/\/videos.oliverdavies.uk\">https:\/\/videos.oliverdavies.uk<\/a>.<\/p>\n\n<p>I plan on doing more videos and live streams soon, which will also be uploaded to my Peertube.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "49162664e5c715f580f3bfe1499494f8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json b/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json
index 85b0e397c..250eaff69 100644
--- a/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json
+++ b/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Two of the worst phrases I've heard when working with new development teams is \"We've always done it this way\" or \"We've never needed to do this before\".<\/p>\n\n<p>Whether it's writing automated tests, using static analysis, having a CI pipeline or using a specific framework or tool, this mindset prevents experimentation, growth and improvement.<\/p>\n\n<p>Instead, try to think about what benefits alternative approaches could offer and how they could improve any situations you're currently experiencing.<\/p>\n\n<p>You don't need to do it forever. Decide on something you want to try on a trial basis and set an end date.<\/p>\n\n<p>Then, when the trial is finished, you can decide if it achieved what you wanted, and if you want to continue with it.<\/p>\n\n<p>Even if you don't continue with it, you still learned something by trying.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ff423bb2508f4873bd03521220ecb749",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json b/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json
index b366697f7..7671a15f1 100644
--- a/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json
+++ b/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As I said in yesterday's email, I developed my first website project on Drupal. It allowed me to take a static HTML and CSS website and convert it into something that was much easier and quicker for me to update, and allowed me to create more users with permissions to do those tasks too.<\/p>\n\n<p>I worked on various Drupal projects, and my first full-time job was on an in-house team where we maintained and enhanced a Drupal 6 website.<\/p>\n\n<p>I've since used Drupal for projects of all shapes and sizes with different levels of complexity. Everything from a simple brochure website to large and complex, multilingual, API-driven projects.<\/p>\n\n<p>I've been able to build eCommerce websites with Drupal using Ubercart and Drupal Commerce. I've built traditional stores where customers purchase physical products, a photography competition website with custom judging functionality, a site for purchasing commercial and residential property and land searches, and a fully-fledged events booking and management platform.<\/p>\n\n<p>Whatever the size and complexity of the project, Drupal is flexible enough to fit it.<\/p>\n\n<p>I've loved some of the ecosystem improvements within the last few years. Moving to object-orientated code by default, integrating code from other projects like Symfony, shipping new features every six months as part of the new release cycle, and embracing tools like Composer, PHPStan and Rector.<\/p>\n\n<p>I also love being part of the Drupal community. Collaborating on tasks, speaking on Slack, and attending events like DrupalCon where I've been lucky enough to attend, speak and mentor.<\/p>\n\n<p>Although Drupal is my specialty and the tool that I've used the most, I don't use it exclusively. I'll talk more about this in tomorrow's email.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "10d16646b00062b7c85b51e5adc54370",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json b/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json
index 68c59bbe8..15100da27 100644
--- a/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json
+++ b/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One of my favourite Drupal phrases is \"Come for the software, stay for the community\".<\/p>\n\n<p>I started using Drupal so I could build a website for the Tae Kwon-Do school I was training at, and then started to get involved with the community online and at events, such as local meetups and conferences, such as DrupalCamps and DrupalCon.<\/p>\n\n<p>I started to contribute code to Drupal core and contrib projects and was a contribution mentor at my first DrupalCon in Prague in 2017 as well as others since, helping first time Drupal contributors.<\/p>\n\n<p>I've got jobs and projects from my involvement with the community, including working for the Drupal Association itself.<\/p>\n\n<p>I've met people and travelled to places I otherwise wouldn't have because of the Drupal community, as well as the wider PHP, open source and software development communities,<\/p>\n\n<p>I came to Drupal for the code, and stayed for the code and the community.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b2429e68b50db27a25afc2c94ecfd957",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json b/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json
index b549e06d6..1a54f233b 100644
--- a/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json
+++ b/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Automated testing is where you write tests to ensure that your code works as expected, which can be re-run as needed and executed automatically without user input.<\/p>\n\n<p>Test-driven development (TDD) is when you write the tests before the production code. You see the tests fail and write code until they pass, and then repeat the process. However, TDD is not just about the tests - it's about the design of the code.<\/p>\n\n<p>By writing the tests first, you guarantee that the code that you write will be testable, which isn't something that you can't do if the production code is written first.<\/p>\n\n<p>You may need to refactor your initial working implementation before it can be tested - which means that you could also break it during that time and need to spend time debugging and fixing any regressions. Ideally, you want the tests in place first before any refactoring, so if something breaks, you'll know because of the failing test.<\/p>\n\n<p>TDD keeps your code cleaner and simpler, as you only write enough code to make the tests pass. Once a test is passing, you stop writing code, so you'll end up with less, simpler code as it's easy to know when to stop.<\/p>\n\n<p>If you don't write the tests first, you may be tempted to skip writing them completely, leaving untested code or adding <code>TODO: add test<\/code> comments that may never get reviewed.<\/p>\n\n<p>Also, where's the fun in writing tests for code that you've already written, that you know are going to pass?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "83b11c57e9b106b547608123735755d3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json b/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json
index 03b6aded8..79ecdf9cf 100644
--- a/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json
+++ b/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This is a follow-up to Friday's email on generic commit messages.<\/p>\n\n<p>In it, I discussed seeing commit messages like <code>Week 20 development<\/code> in project codebases and why you should write specific commit messages for each change.<\/p>\n\n<p>The other thing is, if you only commit once a week, you can only deploy once a week.<\/p>\n\n<p>That's assuming that, on this project, the changes were committed and pushed weekly. It could have been fortnightly, monthly, or longer.<\/p>\n\n<p>As well as increasing the time between deployments, it also makes them larger and riskier as they include more changes.That commit changed 106 files, added 3,453 lines and removed 17 lines, including custom module and theme changes, contrib module updates and library updates.<\/p>\n\n<p>If the dependencies were committed and deployed first, followed by a series of small custom module and theme changes, even though it would have resulted in more deployments, each one would have been smaller and less risky as there were fewer changes and easier to debug any issues and fail forward.<\/p>\n\n<p>I recommend that everyone commits and pushes their changes at least daily and use trunk-based development so everyone's changes apply and work together and are not separated on feature branches.<\/p>\n\n<p>I recommend that they're pushed live daily, too, or as often as possible - reducing the chance of errors and getting the changes providing value for customers and clients.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a73cc355613964dd5fbafe455fb3ed71",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json b/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json
index 730576f18..09dda961d 100644
--- a/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json
+++ b/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently had Ryan Szrama as a guest on the <a href=\"http:\/\/default\/podcast\/13-ryan-szrama-centarro\">Beyond Blocks podcast<\/a>.<\/p>\n\n<p>Ryan is the CEO of Centarro - the company behind Drupal Commerce, the eCommerce platform built on the Drupal CMS.<\/p>\n\n<p>I've used Drupal Commerce for a number of projects since it was released in 2011, as well as Ubercart before that.<\/p>\n\n<p>One of the major things I like about it is its flexibility.<\/p>\n\n<p>The Commerce Kickstart distribution is a great way to create a demo Drupal Commerce project that shows a typical eCommerce store selling everything from books to hats, furniture and inflatable flamingos.<\/p>\n\n<p>I've used Drupal Commerce for these typical scenarios but also for some non-typical ones.<\/p>\n\n<p>I created a multi-site Drupal Commerce store for a gadget insurance company, dealing with many products and product variations. I built a custom Vue.js form that created an order with the required items before passing customers to a Drupal Commerce checkout flow.<\/p>\n\n<p>I created a yearly photography competition website that photographers can enter by purchasing a product and uploading their photographs to the order. I built custom judging functionality, which allows jurors to score each entry and the site owner to see the totals and which submission won the competition.<\/p>\n\n<p>I created an events management and booking website where each event was a product with different variations based on the different prices - early bird, regular and last minute. Each event had a maximum number of places and, potentially, a waitlist.<\/p>\n\n<p>This website also included a loyalty scheme for event organisers and attendees, who received coupons after organising or attending a certain number of events.<\/p>\n\n<p>Drupal Commerce can do a lot and isn't just selling t-shirts, hats, books or furniture.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0628dc31f17c91dcb60ca2d028116ec0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json b/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json
index dbec4e923..567229d40 100644
--- a/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json
+++ b/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you have multiple implementations of a service, as I <a href=\"http:\/\/default\/daily\/2023\/08\/23\/dont-use-third-party-services-directly\">mentioned in yesterday's email<\/a>, you need to ensure they all provide the same functionality.<\/p>\n\n<p>You need to be able to run the same tests against each implementation and have them pass.<\/p>\n\n<h2 id=\"how-do-you-do-this%3F\">How do you do this?<\/h2>\n\n<p>In PHP, I use a trait that contains the test methods and then have a test class for each implementation that uses the trait and sets up any test data.<\/p>\n\n<p>Then, each test class will run the methods from the contract test trait and ensure they all provide the same behaviour, regardless of how it does so - whether it communicates with an API, uses an SDK, or returns fake values.<\/p>\n\n<p>If one implementation doesn't return the same result as the others, its test will fail.<\/p>\n\n<p>If you add a new implementation, you create a new test class, use the trait and get the tests to pass.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "385f47a0206ed77604fb346a64e36688",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json b/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json
index c64445be4..fb26deba3 100644
--- a/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json
+++ b/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Because <a href=\"http:\/\/default\/daily\/2022\/09\/20\/why-like-trunk-based-development\">I do trunk-based development<\/a>, I typically don't create branches in Git.<\/p>\n\n<p>If I do, I usually want to keep the commit messages, but there are some situations where I want to squash everything into a single commit with a simple message.<\/p>\n\n<p>Typically, I'd do this using a rebase command like <code>git rebase -i main<\/code> and get an output like this, showing the commits:<\/p>\n\n<pre><code class=\"plain\">pick d21fafc Remove encrypted disk configuration\npick ffc1296 Update mount location for media directories\npick 58f645e Add multigrep from TJ's video\npick bbd5052 Revert \"Remove encrypted disk configuration\"\npick 8280c49 Show more generations on boot\npick d3b0c48 Revert \"Add encrypted media drive\"\npick 8cdc6a5 Add paperless-ngx\npick 73d801d Add Nick Janetakis' `notes` script\npick 99b6e3b Set options for text files\n<\/code><\/pre>\n\n<p>I can change <code>pick<\/code> to <code>squash<\/code> or <code>fixup<\/code> and decide what to do for each commit.<\/p>\n\n<p><code>squash<\/code> combines the commit with the previous one, including the commit messages.<\/p>\n\n<p><code>fixup<\/code> uses the previous commit message and discards the current one.<\/p>\n\n<p>Once the file is saved, the rebase is performed and the actions are executed.<\/p>\n\n<h2 id=\"there-is-another-way\">There is another way<\/h2>\n\n<p>If you don't want any of the commit messages, you can also use <code>git merge --squash<\/code>.<\/p>\n\n<p>This will automatically squash all the commits - ready for you to run <code>git commit<\/code> and provide the final message.<\/p>\n\n<p>There's no option to merge or combine the previous messages, though.<\/p>\n\n<p>If you want to do that, you can still use the rebase approach.<\/p>\n\n<p>If not, use <code>git merge --squash<\/code>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "67caaeda05aacc7008f9a07114af9b7f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json b/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json
index 5bfd7856a..2dd1d84d0 100644
--- a/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json
+++ b/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <h2 id=\"what-are-code-katas%3F\">What are code katas?<\/h2>\n\n<p>Code katas are programming exercises which, like katas in martial arts, use practice and repetition to improve your skills.<\/p>\n\n<p>Common katas are Fizzbuzz, the Bowling score calculator, and the Gilded Rose.<\/p>\n\n<p>Each gives you the criteria of what the kata should do before it can be considered complete along with any specific information, and some websites will also give you a suite of failing tests to make pass - though I prefer to write my own and follow a test-driven development approach.<\/p>\n\n<p>Once you have completed the solution and the criteria is satisfied, the kata is complete.<\/p>\n\n<h2 id=\"why-i-do-code-katas\">Why I do code katas<\/h2>\n\n<p>As I said, doing code katas improves your skills by solving problems and identifying patterns that you may see when working in your project code.<\/p>\n\n<p>Different katas focus on different patterns. For example, the Fibonacci Number kata focuses on recursion, whereas the Gilded Rose kata is all about refactoring complex legacy code.<\/p>\n\n<p>Doing code katas keeps your skills sharp and gives you a different perspectives as you work through different katas. You can then use and apply these within your main projects.<\/p>\n\n<p>If you want to learn a new programming language then working on a kata that you've already solved in a language that you're familiar with allows you to focus on the syntax and features of the new language. I've been working on some code katas in TypeScript as I've been working with that recently, and would like to do some in Go.<\/p>\n\n<p>If you work as part of a team or a part of a meetup, code katas can be worked on as a group and can introduce new skills like automated testing and test-driven development as well as providing some opportunities for team-building and socialising. If you're trying to introduce pair or mob programming, then working on code katas could be a good first step.<\/p>\n\n<p>If you're just getting started with programming, working on code katas will help you learn the fundamentals and problem solving, but I'd also encourage you to put the code on GitHub and blog about each kata that you complete. Doing so will help and encourage others and also look good when applying for roles.<\/p>\n\n<p>P.S. There are lists of code katas at https:\/\/github.com\/gamontal\/awesome-katas and https:\/\/codingdojo.org\/kata, and online versions at https:\/\/www.codewars.com\/join and https:\/\/exercism.org\/tracks. There are many others - if you have a favourite, reply to this email and let me know.<\/p>\n\n<p>I have <a href=\"https:\/\/github.com\/opdavies?tab=repositories&amp;q=katas\">some GitHub repositories for my code kata solutions<\/a> and will continue to build these as I do more.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "69d1afc409380b8667d60251a88e9505",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json b/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json
index 5700a2d68..04c830ab7 100644
--- a/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json
+++ b/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"http:\/\/default\/blog\/going-full-vim\">I switched to using Neovim full time<\/a> in July 2021.<\/p>\n\n<p>More recently, I've used a script that creates and attaches to tmux sessions based on the directories in my Code directory, making it easy to switch between projects.<\/p>\n\n<p>It was based on others by <a href=\"http:\/\/default\/podcast\/25-jess-archer-drush-laravel-prompts\">Jess Archer<\/a> and ThePrimeagen, although Prime recently created a new version of his as its own project, so I decided to switch to his version.<\/p>\n\n<p>But there was one issue - the paths to search for directory names is hard-coded and don't match mine.<\/p>\n\n<p>I started by duplicating his and changing the paths, but that would mean missing any future updates and having to maintain my version separately.<\/p>\n\n<p>Until I realised I could use his version and apply patches to it for my changes and customisations.<\/p>\n\n<p>This is something I'm familiar with from my Drupal contributions, as we used to attach patch files to issues before moving to GitLab and merge requests.<\/p>\n\n<p>I was able to make my changes and easily <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/dotfiles\/commit\/5fd27efa502bd48eb7d897acec8aa3344bef2247\">apply the patch easily as part of my Nix derivation<\/a>.<\/p>\n\n<p>This means I'll get any future updates to the script, keep my changes and Nix will automatically apply my patch whenever I rebuild my system.<\/p>\n\n<p>I really like this approach, as I'm no longer duplicating the script and don't have the maintenance overhead whilst still making any customisations I need.<\/p>\n\n<p>In fact, there are Linux applications such as dwm, dmenu and st (a simple terminal), all written by suckless.org, that use this approach as the main method of configuration and customisation.<\/p>\n\n<p>They release the core package and people write and contribute patch files to customise it as they need.<\/p>\n\n<p>Although patches are no longer used on Drupal.org, they're still a great way to customise and contribute to open source software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e5fa9a4299d210679c2b24528450155b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json b/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json
index 147e0a58e..28eefa5bd 100644
--- a/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json
+++ b/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>On Sunday, the Drupal project turned 22 years old.<\/p>\n\n<p>I've personally been working with Drupal primarily for almost 15 years <a href=\"https:\/\/www.drupal.org\/u\/opdavies\">according to my Drupal.org profile<\/a>, self teaching and working on personal and freelance projects since 2007, and in full-time roles since 2010 when I started at Horse and Country TV to work on their Drupal 6 website.<\/p>\n\n<p>Last month, I started my first Drupal 10 project for a client.<\/p>\n\n<p>I'm proud that over a year of that time was spent working for the Drupal Association where I improved the Drupal.org websites and resolved issues that would have blocked the Drupal 8 release in 2015.<\/p>\n\n<p>I'm also happy to have <a href=\"http:\/\/default\/presentations\">presented talks and workshops<\/a> at events like DrupalCamps, Drupal Developer Days and twice at DrupalCon. I've also organised Drupal events such as the Drupal Bristol meetup and DrupalCamp Bristol conference.<\/p>\n\n<p>I've had opportunities to contribute to open-source by having patches committed to Drupal core and maintaining modules and themes like <a href=\"https:\/\/www.drupal.org\/project\/override_node_options\">Override Node Options<\/a> and the <a href=\"https:\/\/www.drupal.org\/project\/tailwindcss\">Tailwind CSS starter kit<\/a>. I've also mentored and helped others to get their first commits to Drupal core and open-source.<\/p>\n\n<p>I plan to continue working with Drupal and being part of the community for a long time, hopefully for at least another 22 years.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "046eae44685470305d623da38d6189e3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json b/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json
index d21f9a9f1..138bf4517 100644
--- a/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json
+++ b/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I saw a post that asked the question:<\/p>\n\n<blockquote>\n  <p>Have you ever spent three days on an issue that should have taken 2 hours?<\/p>\n<\/blockquote>\n\n<p>My thought was, \"Who said it should have taken two hours?\".<\/p>\n\n<p>In my experience, tasks take as long as they take.<\/p>\n\n<p>Even something that seems simple can end up being something complex.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c80c0a0daeda9ac2879e1a8706bfad5e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json b/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json
index 3c514e8ad..93e0cdabb 100644
--- a/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json
+++ b/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Every project has its own set of commands that need to be run regularly.<\/p>\n\n<p>From starting a local server or the project's containers with Docker or Docker Compose, running tests or clearing a cache, or generating the CSS and JavaScript assets, these commands can get quite complicated and time-consuming and error-prone to type over and over again.<\/p>\n\n<p>One common way to simplify these commands is using a <code>Makefile<\/code>.<\/p>\n\n<p>A Makefile contains a number of named targets that you can reference, and each has one or more commands that it executes.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"language-language-yaml\"># Start the project.\nstart:\n    docker-compose up -d\n\n# Stop the project.\nstop:\n    docker-compose down\n\n# Run a Drush command.\ndrush:\n    docker-compose exec php-fpm drush $(ARGS)\n<\/code><\/pre>\n\n<p>With this Makefile, I can run <code>make start<\/code> to start the project, and <code>make stop<\/code> to stop it.<\/p>\n\n<p>Makefiles work well, but I don't use the full functionality that they offer, such as dependencies for targets, and passing arguments to a command - like arguments for a Drush, Symfony Console, or Artisan command, doesn't work as I originally expected.<\/p>\n\n<p>In the example, to pass arguments to the <code>drush<\/code> command, I'd have to type <code>ARGS=\"cache:rebuild\" make drush<\/code> for them to get added and the command to work as expected.<\/p>\n\n<p>An agency that I worked for created and open-sourced their own Makefile-like tool, written in PHP and built on Symfony Console. I gave a talk on it called <a href=\"http:\/\/default\/presentations\/working-with-workspace\">Working with Workspace<\/a> and used it on some of my own personal and client projects.<\/p>\n\n<h2 id=\"what-i%27m-using-now\">What I'm using now<\/h2>\n\n<p>The solution that I'm using now is a <code>run<\/code> file, which is something that I learned from Nick Janetakis' blog and YouTube channel.<\/p>\n\n<p>It's a simple Bash file where you define your commands (or tasks) as functions, and then execute them by typing <code>.\/run test<\/code> or <code>.\/run composer require something<\/code>.<\/p>\n\n<p>Here's the Makefile example, but as a <code>run<\/code> script:<\/p>\n\n<pre><code class=\"bash\">#!\/usr\/bin\/env bash\n\nfunction help() {\n  # Display some default help text.\n  # See examples on GitHub of how to list the available tasks.\n}\n\nfunction start {\n  # Start the project.\n  docker-compose up -d\n}\n\nfunction stop {\n  # Stop the project.\n  docker-compose down\n}\n\nfunction drush {\n  # Run a Drush command with any additional arguments.\n  # e.g. \".\/run drush cache:rebuild\"\n  docker-compose exec php-fpm drush \"${@}\"\n}\n\n# Execute the command, or run \"help\".\neval \"${@:-help}\"\n<\/code><\/pre>\n\n<p>As it's Bash, I can just use <code>$1<\/code>, <code>$2<\/code> etc to get specific arguments, or <code>$@<\/code> to get them all, so <code>.\/run drush cache:rebuild<\/code> works as expected and any additional arguments are included.<\/p>\n\n<p>You can group tasks by having functions like <code>test:unit<\/code> and <code>test:commit<\/code>, and tasks can run other tasks. I use this for running groups of commands within a CI pipeline, and to extract helper functions for tasks like running <code>docker-compose exec<\/code> within the PHP container that other commands like <code>drush<\/code>, <code>console<\/code> or <code>composer<\/code> could re-use.<\/p>\n\n<p>As well as running ad-hoc commands during development, I also use the run file to create functions that run Git pre-commit or pre-push hooks, deploy code with Ansible, or build, push or pull the project's latest Docker images.<\/p>\n\n<p>I also use one within my Talks repository to generate PDF files using rst2pdf, present them using phdpc, and generate thumbnail images.<\/p>\n\n<p>For examples of <code>run<\/code> files that I use in my open-source code, <a href=\"https:\/\/github.com\/search?l=Shell&amp;q=user%3Aopdavies+filename%3Arun&amp;type=Code\">you can look in my public GitHub repositories<\/a>, and for more information, here is <a href=\"https:\/\/nickjanetakis.com\/blog\/replacing-make-with-a-shell-script-for-running-your-projects-tasks\">Nick's blog post where I first found the idea<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "15a1f14b232babef6136f4cc242315c0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json b/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json
index 0296227d6..72c5fe46f 100644
--- a/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json
+++ b/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Every codebase has \"icky\" code.<\/p>\n\n<p>Code that works but is difficult to read and understand, that most people will avoid working on.<\/p>\n\n<p>It could be fragile and occasionally return different results or error.<\/p>\n\n<p>It could be a suboptimal implementation.<\/p>\n\n<p>I mention in <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">my test-driven drupal talk<\/a> when I wrote some code that worked locally but didn't work because of the hosting setup and I had to rewrite the code in a different and less optimal way.<\/p>\n\n<p>How do you build confidence around this code?<\/p>\n\n<p>Write more automated tests around it.<\/p>\n\n<p>This will make it easier to understand what the code does as the tests will act like examples and, as you find situations where the code can break, you can write tests to ensure it works as expected once fixed and will continue to work.<\/p>\n\n<p>Once there are tests, the code will be easier to add to, change, refactor, read and understand.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b0767502ae62064308bde448678dfb0b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json b/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json
index d90435096..d10e7f68b 100644
--- a/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json
+++ b/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you want people to do things, you need to make them as simple as possible.<\/p>\n\n<p>If you need to need to switch to a different window or tab to run your tests, you'll be less likely to run them.<\/p>\n\n<p>I have keybindings in Neovim to run the current test, the previous test or the entire test file, which means I can easily run a test with a couple of key presses and without needing to change applications or to a different terminal.<\/p>\n\n<p>I do the same when working on presentation slides, and need to compile the reStructuredText document into a PDF <a href=\"http:\/\/default\/talks\/building-presenting-slide-decks-rst2pdf\">using rst2pdf<\/a>.<\/p>\n\n<p>I also use watchers with <code>entr<\/code> - commands that watch for changes, such as a file being saved, and running a command. This means I can also have my tests run automatically whenever I change a file.<\/p>\n\n<p>I have snippets to generate complex code or commands I need to run often, saving me time and reducing errors.<\/p>\n\n<p>The more frictionless and easy I can make running a task, the more likely I am and others are to do them.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "88540be172808effd2faba79bbb514ad",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json b/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json
index 0e1e26c3b..3c3a02eda 100644
--- a/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json
+++ b/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've worked for agencies who, as well as building or developing web applications, will purchase domain names and manage hosting for clients.<\/p>\n\n<p>I've worked at agencies who insisted on hosting applications they built.<\/p>\n\n<p>This is probably easier for clients initially, but things were harder on any project that needed transferring a domain name or migrating to a new hosting environment.<\/p>\n\n<p>I do this for myself, but I don't get involved with domain names or hosting for clients.<\/p>\n\n<p>I'm happy to give recommendations based on my experience using platform as a service (PaaS) offering and self hosting, but I want the client to set this up themselves.<\/p>\n\n<p>That means it's their account and they can contact someone if there is an issue, but mainly because they're in control.<\/p>\n\n<p>I want clients to work with me because they want to and not because they're locked in as I manage their domain name or hosting.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7d159eec4f78f48020571cf370ef6853",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json b/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json
index d7909fdcd..1b635c2b0 100644
--- a/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json
+++ b/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>One piece of criteria for whether some software is good is whether it's easy to write automated tests for.<\/p>\n\n<p>I recently worked on a method that was more than 150 lines.<\/p>\n\n<p>It was difficult to understand, had too many responsibilities and didn't use dependency injection.<\/p>\n\n<p>This made it difficult to test.<\/p>\n\n<p>If it was split into several smaller methods or classes, each could be responsible for different aspects and have clear responsibilities.<\/p>\n\n<p>Each new method or class could have its own tests to verify its own functionality works.<\/p>\n\n<p>It would be easy to understand and identify and fix any issues.<\/p>\n\n<p>If dependency injection was used, things can be mocked or changed as needed to make the logic testable.<\/p>\n\n<p>If everything is in one large function, the code isn't testable.<\/p>\n\n<p>Even if it works now, it will be difficult to change in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3ebf30f7b8a2b03f2ba95b73683d6184",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json b/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json
index a1f38ca18..a435b6992 100644
--- a/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json
+++ b/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've used a lot of issue trackers and project management tools since I started doing software development in 2007.<\/p>\n\n<p>Many come with a lot of features I don't use or make the software overcomplicated.<\/p>\n\n<p>I prefer simple software that does it's thing well.<\/p>\n\n<p>I manage my projects with a simple todo.txt file in the project directory that contains a list of my current and upcoming tasks.<\/p>\n\n<p>I can quickly open or add to it as I work and don't need to open a browser and click through multiple screens to find what I need.<\/p>\n\n<p>It works offline, so I don't need an Internet connection if I'm travelling or somewhere where there's no wifi or mobile connectivity.<\/p>\n\n<p>I will use a more complicated tool if needed but a simple text file will always be my preferred option.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b173e5b02c2560a97cc2ef428412e78e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json b/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json
index a5685be57..0e6c2a241 100644
--- a/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json
+++ b/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Code reviews are something that happens after the code has been written.<\/p>\n\n<p>Usually, a task is assigned to someone who completes it and makes the code available to their team members before it's merged.<\/p>\n\n<p>The problem is that if the implementation is wrong, it's already been written, which costs time and money.<\/p>\n\n<p>If the change needed to be rewritten or majorly changed before it could be merged, as well as being an awkward conversation, it would cost more time and money to do.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Instead of reviewing the code after it's been written, invest more time into planning how the implementation should work upfront.<\/p>\n\n<p>What potential solutions exist, and which would work best in this situation?<\/p>\n\n<p>Write technical design documents and, if needed, create a small proof of concept.<\/p>\n\n<p>Do this as a team and decide on the approach before any code is written and time or effort is spent.<\/p>\n\n<p>Then, the person working on the task will have a clearer path, and if you still want to review the code afterwards, you have something to compare it to.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "838c549a95c0f1257910cb56a6ab9ebe",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json b/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json
index 95ceb978e..d838057ce 100644
--- a/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json
+++ b/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">One of my earliest daily emails was about <code>run<\/code> files<\/a> - files that contain Bash functions that combine or simplify project-specific tasks.<\/p>\n\n<p>In Drupal projects, these could be to execute Composer or Drush commands, connect to the database, or run automated tests.<\/p>\n\n<p>For my CI pipelines, I like to use a function called <code>ci:test<\/code> that contains all the commands to run in the pipeline.<\/p>\n\n<p>This keeps the pipeline configuration as simple and agnostic as possible.<\/p>\n\n<p>It also makes it easy for people to read and, because it's a bash file, it will run anywhere without any additional tools.<\/p>\n\n<p>For an example, <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\/blob\/d18bf2242fba1291cabf1e16a5badb6fda7ce509\/run#L16-L35\">see my Drupal Docker example repository<\/a>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The main advantage, though, is being able to run the pipeline locally, if you need to.<\/p>\n\n<p>Maybe you need to debug a failure in the pipeline or you want to test a change to the pipeline locally before pushing it.<\/p>\n\n<p>By using a command in a <code>run<\/code> file, doing so is as simple as running that one command.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3e61ae665c2eec6ae6c753e53475f4eb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json b/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json
index 8d7c5f750..768f55b0a 100644
--- a/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json
+++ b/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Let's start at the beginning.<\/p>\n\n<p>If we want to automate our infrastructure then we first need to create it. This could be done manually or we can automate it.<\/p>\n\n<p>Popular tools for this include Terraform and Pulumi, but Ansible also includes modules to interface with hosting providers such as Amazon Web Services, Microsoft Azure, DigitalOcean, and Linode.<\/p>\n\n<p>By using one of these tools, you can programatically provision a new, blank server that is ready for you to be configered.<\/p>\n\n<p>For example, to <a href=\"https:\/\/docs.ansible.com\/ansible\/latest\/collections\/community\/digitalocean\/digital_ocean_module.htm\">create a DigitalOcean droplet<\/a>:<\/p>\n\n<pre><code class=\"language-yaml\">---\n- community.digitalocean.digital_ocean_droplet:\n    image: ubuntu-20-04-x64\n    name: mydroplet\n    oauth_token: \"...\"\n    region: sfo3\n    size: s-1vcpu-1gb\n    ssh_keys: [ .... ]\n    state: present\n    wait_timeout: 500\n  register: my_droplet\n<\/code><\/pre>\n\n<p>Running this playbook will create a new Droplet with the specified name, size, and operating system, and within the specified region.<\/p>\n\n<p>If you needed to create a separate database server or another server for a new environment, then the file can be updated and re-run.<\/p>\n\n<p><a href=\"https:\/\/docs.ansible.com\/ansible\/latest\/collections\/amazon\/aws\/ec2_instance_module.html#ansible-collections-amazon-aws-ec2-instance-module\">Creating an Amazon EC2 instance<\/a> looks very similar:<\/p>\n\n<pre><code class=\"language-yaml\">---\n- amazon.aws.ec2_instance:\n    image_id: ami-123456\n    instance_type: c5.large\n    key_name: \"prod-ssh-key\"\n    name: \"public-compute-instance\"\n    network:\n      assign_public_ip: true\n    security_group: default\n    vpc_subnet_id: subnet-5ca1ab1e\n<\/code><\/pre>\n\n<p>This doesn't apply just to servers - you can also use Ansible to create security groups and S3 buckets, manage SSH keys, firewalls, and load balancers.<\/p>\n\n<p>Once we have our infrastructure in place, we can start using Ansible to set and manage its configuration, which we'll do in tomorrow's email.<\/p>\n\n<hr>\n\n<p>Want to learn more about how I use Ansible? <a href=\"http:\/\/default\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "095fcb0d0aa1a515bcda00c6f0fcebe8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json b/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json
index 96dc72348..015b6f61c 100644
--- a/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json
+++ b/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/05\/17\/why-i-dont-commit-with--m\">Yesterday<\/a>, I mentioned the 50\/72 rule when writing Git commit messages.<\/p>\n\n<p>The first line in the commit message is the subject line and should be no longer than 50 characters.<\/p>\n\n<p>Any additional lines are the message body and should be wrapped at 72 characters.<\/p>\n\n<p>As I said, I have Neovim configured to format my commit messages based on these rules, although they're more like guidelines.<\/p>\n\n<p>There's no hard limit on the number of characters in the subject line or the number of characters in the body.<\/p>\n\n<p>The commit will work and not be rejected when pushing to your remote repository.<\/p>\n\n<p>There are likely post-commit <a href=\"http:\/\/default\/daily\/2022\/08\/16\/what-are-git-hooks-why-are-they-useful\">Git hooks<\/a> to do this, but by default, things will work.<\/p>\n\n<p>A commit message to Drupal core today was 178 characters long, including the issue ID and contributors.<\/p>\n\n<p>When working on project teams, ideally, everyone would follow the 50\/72 rule, but if they don't consistently, I don't think it's an issue.<\/p>\n\n<p>I'd rather they focused on writing a good and descriptive commit message and if it's formatted correctly, that's a bonus.<\/p>\n\n<p>Whilst I could automate checks for this, I don't think it's the best use of everyone's time and, especially for Junior Developers who already have enough to learn already, not where their focus should be.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9217d539c0fc267a1534cb9e166f41ee",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d0ee1aae-f2fc-49d2-8865-d4912209eeea.json b/content/node.d0ee1aae-f2fc-49d2-8865-d4912209eeea.json
index deb322c87..534ec5fc5 100644
--- a/content/node.d0ee1aae-f2fc-49d2-8865-d4912209eeea.json
+++ b/content/node.d0ee1aae-f2fc-49d2-8865-d4912209eeea.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I sometimes work on projects that already has an existing environment configuration, usually using a tool like DDEV.<\/p>\n\n<p>Similar to using Nix, DDEV makes environments more consistent by standardising versions of PHP, nodejs, etc for each project.<\/p>\n\n<p>This is great, but how do you know everyone has the same version of DDEV?<\/p>\n\n<p>Different people having different versions of DDEV could introduce its own issues and bugs, such as pulling different images with different default package versions.<\/p>\n\n<h2 id=\"enter-nix\">Enter Nix<\/h2>\n\n<p>The Nix package manager has over 100,000 packages, including DDEV.<\/p>\n\n<p>This means I can install DDEV via Nix and because of the flake.nix file, anyone using the same configuration will get the same version of DDEV.<\/p>\n\n<p>Here's a simple <code>flake.nix<\/code> file to install DDEV:<\/p>\n\n<pre><code class=\"nix\">{\n  inputs.nixpkgs.url = \"github:NixOS\/nixpkgs\/nixos-unstable\";\n\n  outputs =\n    { nixpkgs, ... }:\n    let\n      system = \"x86_64-linux\";\n      pkgs = nixpkgs.legacyPackages.${system};\n    in\n    {\n      devShells.${system}.default = pkgs.mkShell {\n        buildInputs = with pkgs; [ ddev ];\n      };\n    };\n}\n<\/code><\/pre>\n\n<p>This approach also means I can have different versions of DDEV installed at once so I can use different versions for different projects as needed.<\/p>\n\n<p>I also don't need it installed globally, so this only makes it available to the projects that need it.<\/p>\n\n<p>It's a bit meta, but it works.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "562ee3b079f3db7e10cc08cfdda26292",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json b/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json
index 5fb29a523..d2340869b 100644
--- a/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json
+++ b/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A blog post appeared on my feed this morning, titled <a href=\"https:\/\/www.nomensa.com\/blog\/how-to-be-t-shaped\">How to be T-Shaped<\/a>.<\/p>\n\n<p>\"T-shaped Developers\" is a term that I've also used before. Being T-shaped means that you have a deep knowledge in one particular area and a breadth of knowledge in other areas.<\/p>\n\n<p>I would say that I'm T-shaped.<\/p>\n\n<p>My main area of knowledge is PHP and Drupal software development - they're the programming language and content management system that I've used throughout most of my career so far, since I started in 2007.<\/p>\n\n<p>As I worked on my own personal and client projects, I needed to learn more complementary skills.<\/p>\n\n<p>I needed to learn how to style websites and build themes so I started to learn front-end development with CSS and frameworks like Bootstrap, Bulma and Tailwind CSS, and JavaScript frameworks like Angular, Vue.js and Alpine, as well as TypeScript.<\/p>\n\n<p>I also needed to host these projects somewhere, which introduced me to Linux servers, virtual hosts, (S)FTP and SSL, web servers like Apache, Nginx and Caddy, MySQL and MariaDB databases, and as projects got more complicated, I started using tools like Vagrant and Puppet, Ansible, and Docker for configuring environments to work in.<\/p>\n\n<p>I don't use Drupal for every project. I've used static site generators and frameworks like Symfony based on the project's requirements, and have projects that use several different technologies at the same time.<\/p>\n\n<p>The main benefits are that I can either deliver entire projects or projects with more complicated architectures, or work across different teams - mentoring a team of Front-End Developers in Drupal theming, or working with System Administrators to start hosting PHP applications. Having these additional skills is definitely valuable to employers and clients.<\/p>\n\n<p>I've said that one of the best and worst things about software development is that there's always something new to learn!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "204bc5dcd32cb6884423a2b2c71f81aa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json b/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json
index 734f16ecd..a1f057bec 100644
--- a/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json
+++ b/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>For my first time in the podcast host chair, I interviewed Matt Glaman - Principal Software Engineer at Acquia.<\/p>\n\n<p>I initially knew Matt from his work on Drupal Commerce, but I wanted to learn about his new project, Retrofit - a tool to make it easier to upgrade from Drupal 7 (which will be end of life in January 2025) to Drupal 10.<\/p>\n\n<p>We also talked briefly about PHPStan Drupal and drupal-check, which are some of Matt's other projects and contributions to the Drupal community.<\/p>\n\n<p>Thank you, Matt, for being the first guest on the Beyond Blocks podcast.<\/p>\n\n<p>I have other guests booked for this week, so the episode with Matt will be <a href=\"http:\/\/default\/podcast\">published soon<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a813d4b849fdced0618aa5694a3bdadd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json b/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json
index 0564a5958..f38ecd497 100644
--- a/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json
+++ b/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Here are some snippets from my Git configuration file.<\/p>\n\n<p>These days, I use a much simpler workflow and configuration since doing more trunk-based development, but in general, I rebase instead of merging by default, and prefer to use fast-forward merges that doesn't create a merge commit.<\/p>\n\n<p><code>branch.autosetuprebase = always<\/code> and <code>pull.rebase = true<\/code> configure Git to always rebase instead of pull. It does this for all branches, though I might override this for <code>main<\/code> branches.<\/p>\n\n<p><code>pull.ff = only<\/code> and <code>merge.ff = only<\/code> prevents creating a merge commit and will prevent the merge if it would create one. If I needed to override this, I could by using the <code>--no-ff<\/code> option on the command line.<\/p>\n\n<p>I use <code>checkout.defaultRemote = origin<\/code> to ensure that the <code>origin<\/code> remote is used if I have multiple remotes configured, and <code>push.default = upstream<\/code> to set the default remote to push to.<\/p>\n\n<p><code>merge.autoStash<\/code> allows for running merges on a dirty worktree by automatically creating and re-applying a stash of the changes, and <code>fetch.prune<\/code> will automatically prune branches on fetch - keeping things tidy.<\/p>\n\n<p>I also have and use a number of aliases.<\/p>\n\n<p>Some like <code>pl = pull<\/code> and <code>ps = push<\/code> are shorter versions of existing commands, and some like <code>aa = add --all<\/code>, <code>fixup = commit --fixup<\/code> and some additional arguments to commands.<\/p>\n\n<p>I also have some like <code>current-branch = rev-parse --abbrev-ref HEAD<\/code> and <code>worktrees = worktree list<\/code> which add simple additional commands, and some like <code>repush = !git pull --rebase &amp;&amp; git push<\/code> which use execute shell commands to execute more complex commands or combine multiple commands.<\/p>\n\n<p>This is a snapshot of my Git configuration. The <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/blob\/7e935b12c09358adad480a566988b9cbfaf5999e\/roles\/git\/files\/.gitconfig\">full version is on GitHub<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c064efff8a7c26a4e05fee32b076e0b2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json b/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json
index 656fcf68c..5c882fda2 100644
--- a/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json
+++ b/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>While writing yesterday's email, I saw this on my Drupal.org profile (https:\/\/www.drupal.org\/u\/opdavies):<\/p>\n\n<blockquote>\n  <p>Credited on 200 fixed issues<\/p>\n<\/blockquote>\n\n<p>This is not the number of commits I've made to projects and doesn't include issues on other websites like GitHub, but that I've been tagged as a contributor in 200 fixed issues on Drupal.org - aka \"contribution credits\".<\/p>\n\n<p>It includes issues for projects I maintain, like Override Node Options and the Tailwind CSS starter kit, as well as contributions for events I've spoken at, like DrupalCon Europe and BADCamp, and modules for Drupal.org itself that I worked on whilst at the Drupal Association.<\/p>\n\n<p>It also includes contrib projects others maintain, such as the Feature Toggle module and Drupal Commerce, and distributions like Commerce Kickstart and Open Atrium.<\/p>\n\n<p>In particular, I'm proud of the 17 issues for Drupal core - some for patches I've contributed, some I've reviewed, and some whilst I've mentored at events like DrupalCons and DrupalCamps.<\/p>\n\n<p>I've been allocating more open-source time recently, so expect the number of contributions on Drupal.org and GitHub to continue.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "40f6813369f442150f84b87eab9b30ed",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json b/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json
index dfa7c2c20..2c103a446 100644
--- a/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json
+++ b/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><code>git stash<\/code> is one of the commands I use the most.<\/p>\n\n<p>Maybe because I do trunk-based development so I very rarely create new branches, or because I intentionally make and push small atomic commits, I often find myself using <code>git stash<\/code> whilst debugging something or if I need to switch contexts quickly whilst in the middle of another task and I don't want to lose my changes.<\/p>\n\n<p>If it's not something I'm going to unstash and bring back almost immediately, I can create a new branch or create a named stash with <code>git stash save &lt;name&gt;<\/code>.<\/p>\n\n<p>If I don't need to stash everything, it supports the <code>-p<\/code> or <code>--patch<\/code> option and I can decide what to stash and what to keep.<\/p>\n\n<p>If you haven't used <code>git stash<\/code>, I recommend giving it a try.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3b3fc896ed9c2c1970c93dce0d903cac",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json b/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json
index 222a4856a..25943c128 100644
--- a/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json
+++ b/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I watched a webinar recently, and one of the panellists asked, \"How much refactoring should I be doing?\".<\/p>\n\n<p>The reply was, \"More than you're doing now.\".<\/p>\n\n<p>It was quite tongue-in-cheek, but I agree that, in general, code isn't refactored enough.<\/p>\n\n<p>One main reason is a fear of introducing regressions, and to avoid that, you need a good automated test suite.<\/p>\n\n<p>If you break the existing functionality whilst refactoring, you want the test suite to fail so you can identify and fix the regression.<\/p>\n\n<p>If the test suite passes, you can release the new code.<\/p>\n\n<p>How many tests and how much coverage do you need? There's no specfic answer - enough for you to be confident everything still works.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e1706194e7328831ad93ed4122decea1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json b/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json
index 9cb72b36c..40a9fa980 100644
--- a/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json
+++ b/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I like the <a href=\"http:\/\/default\/presentations\/sculpin\">Sculpin static site generator<\/a> - a tool I've used for various personal and client projects where a full content management system like Drupal isn't need.<\/p>\n\n<p>It's written in PHP and uses several Symfony components, including Twig for templating.<\/p>\n\n<p>These are the same as Drupal and, of course, the Symfony framework. Two tools I'm very familiar with.<\/p>\n\n<p>A big reason why I decided to learn Sculpin in 2015 was to learn Twig and other Drupal 8 concepts before it was released.<\/p>\n\n<p>You don't need to write PHP code to use Sculpin, but you can easily extend it with PHP code if you need to.<\/p>\n\n<p>You can write custom service classes - the same as in Drupal or Symfony - and move complex logic there and out of your template files.<\/p>\n\n<p>This also means you can write automated tests with PHPUnit.<\/p>\n\n<p>I've added <code>src<\/code> and <code>tests<\/code> directories to <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/src\/commit\/f21bb125c5b01a9e5cd572c77dca0e8d5cc13849\">my website repository<\/a>, which contain my custom Twig extensions that add new functions for counting the number of presentations I've given and my years of experience.<\/p>\n\n<p>There are a lot of choices for static site generators, including several PHP-based ones, but the familiarity and customisability of Sculpin make it a good choice for me.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cd05e2a441bf25694103bede108b3e8b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json b/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json
index 8ccd1c5d3..51cc2bec1 100644
--- a/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json
+++ b/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whether it's Drupal modules, PHP libraries, npm packages or Tailwind CSS plugins, what's the smallest number you can have in a project?<\/p>\n\n<p>I have a list of Drupal modules and other projects that I commonly use, but I try to keep it to as few as possible.<\/p>\n\n<p>The fewer dependencies there are, the less will need to be updated and maintained.<\/p>\n\n<p>There's no guarantee each dependency will continue to be supported by its maintainers in the future, and each dependency added is an opportunity to introduce potential bugs and security vulnerabilities.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I'm not suggesting you need to write everything by hand as this would be ignoring a major benefit of open-source software, but consider if you need each dependency or if you can achieve the project's goals without it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6afaa3344e6ec1907672718a56f00a9c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json b/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json
index 823b3e936..27fd3d95c 100644
--- a/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json
+++ b/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Many people are very for or against Git hooks - scripts that run automatically on events such as pre-commit and pre-push.<\/p>\n\n<p>Commonly, they are used for running tasks such as altering a commit message or running before committing automated tests and static analysis before pushing a commit.<\/p>\n\n<p>I'm on the fence.<\/p>\n\n<p>I've used them and added support for them to Build Configs, but I don't feel strongly about them.<\/p>\n\n<p>They are awkward to set up (you need to edit the configuration for them to work) and can be easily disabled or bypassed.<\/p>\n\n<p>Some people think it's the Developer's responsibility to run the tasks before pushing changes or that they'll be run in a CI pipeline, so why would they need to be run locally?<\/p>\n\n<p>As I write many small commits and push changes regularly, I can find hooks irritating and prefer to use watchers instead with tools like <code>watchexec<\/code> and <code>entr<\/code>.<\/p>\n\n<p>There are also tools like Captain Hook that are built to manage Git hooks. Maybe, I should investigate it more.<\/p>\n\n<p>What do you think? Are you yay or nay for Git hooks?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8740e9029c98140ce8609709977e5145",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json b/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json
index 97cb04d61..6a6b5652b 100644
--- a/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json
+++ b/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A convention I like from the Laravel framework is to avoid adding boolean arguments to methods.<\/p>\n\n<p>For example, if I have this function:<\/p>\n\n<pre><code class=\"php\">public function getPosts() { ... }\n<\/code><\/pre>\n\n<p>If I wanted to only get published posts, one way would be to add a boolean argument:<\/p>\n\n<pre><code class=\"php\">public function getPosts(boolean $onlyPublished) { ... }\n<\/code><\/pre>\n\n<p>Then, I'd need to use that within the method body to add another condition (this is referred to as control coupling, where one method affects another).<\/p>\n\n<p>The non-boolean approach would be to create a separate method with its own distinct name.<\/p>\n\n<p>For example, <code>getPosts()<\/code> could be named <code>getAllPosts()<\/code> and there could be a separate <code>getPublishedPosts()<\/code> method for only getting published posts:<\/p>\n\n<pre><code class=\"php\">public function getAllPosts() { ... }\n\npublic function getPublishedPosts() { ... }\n<\/code><\/pre>\n\n<p>Whilst we have two methods now instead of one, it's much clearer what each does and there aren't any random <code>true<\/code> or <code>false<\/code>s wherever the method is used.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e20e2bce0a560bd0261032201f0cacd5",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json b/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json
index e455d8a2f..7f2645783 100644
--- a/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json
+++ b/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, I was investigating a CSS issue.<\/p>\n\n<p>It's a known issue due to some legacy code in the website's CSS that I'd fixed before but now needed to extend.<\/p>\n\n<p>Instead of blindly following the same path and extending my previous fix, I decided to rethink the problem and my approach.<\/p>\n\n<p>I re-read my documentation and re-reviewed potential solutions I'd evaluated previously.<\/p>\n\n<p>I decided to take a different approach to solving the problem and found an open-source plugin that someone else had written that gave me the functionality I needed instead of writing it from scratch.<\/p>\n\n<p>I read the code and did a short spike to see if it worked with the existing configuration.<\/p>\n\n<p>After some experimentation, I got it to work and added it to the project.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the Thing<\/h2>\n\n<p>The plugin I used was only 34 lines of code, but these are lines I didn't need to write or will need to maintain.<\/p>\n\n<p>If it works, why would I write it myself?<\/p>\n\n<p>I'd rather use what someone else has written and contribute if I find a bug or need a new feature.<\/p>\n\n<p>That's the benefit of open-source software, and why I use Drupal, PHP, Sculpin, Tailwind CSS, Nix, and others.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "82cd165f20dd5a6540c140be3cb646c9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json b/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json
index 26880bd5a..c6257342a 100644
--- a/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json
+++ b/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/podcast\/11-mark-conroy\">I recently spoke with Mark Conroy<\/a>, Director of Development at Annertech, on the Beyond Blocks podcast.\nWe discussed building something useful in a day and building design systems with web components.<\/p>\n\n<p>Inspired by that conversation, I spent this afternoon experimenting with web components and seeing how I could use them within a design system we're building, as I think they can solve a particular need we have.<\/p>\n\n<p>Following that, I thought I'd see how I could build my own design system and decided to do it with Symfony and see what I could achieve within a few hours.<\/p>\n\n<p>It was a great opportunity to take Symfony 7 for a spin and explore and test some things that <a href=\"http:\/\/default\/podcast\/10-ryan-weaver-symfonycasts\">Ryan Weaver and I discussed in our episode<\/a>, such as Symfony UX and Twig components.<\/p>\n\n<p>Each component is a Twig component with its own PHP class and Twig template, which is rendered when I visit its URL, and I can use the HTML-like <code>&lt;twig:Logo \/&gt;<\/code> syntax to include child components.<\/p>\n\n<p>You can <a href=\"https:\/\/github.com\/opdavies\/symfony-design-system\">view the code on GitHub<\/a>, and it may be something I use and work on in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6306217afe87f3d8cd659f6d4c55923d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json b/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json
index e8381d823..dbf948a0d 100644
--- a/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json
+++ b/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There's a famous programming quote (and variations of it):<\/p>\n\n<blockquote>\n  <p>Always code as if the (person) who ends up maintaining your code will be a\n  violent psychopath who knows where you live. Code for readability.<\/p>\n<\/blockquote>\n\n<p>I believe <a href=\"https:\/\/groups.google.com\/g\/comp.lang.c++\/c\/rYCO5yn4lXw\/m\/oITtSkZOtoUJ\">it comes from this Google thread<\/a>.<\/p>\n\n<p>I'm currently working on some Drupal 7 code I first committed to in May 2014.<\/p>\n\n<p>That person could also be you!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "74b3eda982231a0b291c52c67ee09063",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d421a5a4-8025-4809-8a30-68c723e46af6.json b/content/node.d421a5a4-8025-4809-8a30-68c723e46af6.json
index 10d8460cb..f812baf83 100644
--- a/content/node.d421a5a4-8025-4809-8a30-68c723e46af6.json
+++ b/content/node.d421a5a4-8025-4809-8a30-68c723e46af6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Continuing with yesterday's data transfer object (DTO) example, something that can be done since PHP 8.1 is to make properties read-only:<\/p>\n\n<pre><code class=\"language-php\">class AccountDetails {\n\n  public function __construct(\n  public readonly string $accountNumber,\n  public readonly string $sortCode,\n  ) {}\n\n}\n<\/code><\/pre>\n\n<p>This means the public properties can be read and used without the need for getter methods, but cannot be overridden - making the DTO immutable.<\/p>\n\n<p>Without <code>readonly<\/code>, a DTO can be created and the property values can be changed:<\/p>\n\n<pre><code class=\"language-php\">$accountDetails = new AccountDetails('12345678', '00-00-00');\n$accountDetails-&gt;accountNumber = 'banana';\n<\/code><\/pre>\n\n<p>With <code>readonly<\/code> set, you'd get a fatal error instead:<\/p>\n\n<blockquote>\n  <p>Fatal error: Uncaught Error: Cannot modify readonly property AccountDetails::$accountNumber in \/home\/opdavies\/tmp\/example.php:13<\/p>\n<\/blockquote>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "40e9fa32eee6340942e24d365e4890fa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d487d829-d35c-4c4f-b4e8-af804b29463e.json b/content/node.d487d829-d35c-4c4f-b4e8-af804b29463e.json
index 58a303ada..6b5893318 100644
--- a/content/node.d487d829-d35c-4c4f-b4e8-af804b29463e.json
+++ b/content/node.d487d829-d35c-4c4f-b4e8-af804b29463e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I like skills and technologies that I can re-use.<\/p>\n\n<p>If there's a solution that's only available in one framework and another that is framework-agnostic, I'll use the agnostic one, if possible.<\/p>\n\n<p>I'd rather invest my time learning something I'll be able to re-use and get the most benefit from.<\/p>\n\n<p>Automated testing is an example of something re-usable.<\/p>\n\n<p>Regardless of the CMS, framework or language, how to write and structure automated tests is the same, and you still get the benefits from writing them and\/or doing test-driven development.<\/p>\n\n<p>Whilst the syntax can be different, even in the PHP space comparing PHPUnit, Pest and Behat, the fundamentals and approaches are the same.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5b190bfabbdf6ba7e6db2bf0b5e381b8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json b/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json
index 373cd62a2..f8ce5889b 100644
--- a/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json
+++ b/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I use Gmail\/Google Apps for my email address, and I used to use a LOT of filters.<\/p>\n\n<p>Inspired by a Ruby gem, I created a PHP library that allows me to declare my filters in PHP and create them in XML.<\/p>\n\n<p>I could import the generated XML into Gmail to create the filters.<\/p>\n\n<h2 id=\"gmail-filter-buider\">Gmail Filter Buider<\/h2>\n\n<p>The project is <a href=\"https:\/\/github.com\/opdavies\/gmail-filter-builder\/tree\/3.x\">Gmail Filter Builder<\/a>, and the last commit was in July 2020.<\/p>\n\n<p>It was based on PHP 7 (unsupported since November 2022) and uses five Symfony components and several other packages.<\/p>\n\n<p>Today, as I looked at my current Gmail filters, I decided to revisit and update Gmail Filter Builder.<\/p>\n\n<h2 id=\"updating-the-project\">Updating the project<\/h2>\n\n<p>I set PHP 8.1 as the minimum required version and used a Nix Flake to ensure this was available.<\/p>\n\n<p>I updated the Symfony components from the 3.x versions to 6.x, the latest versions compatible with PHP 8.1. I also updated the other PHP packages to their compatible versions.<\/p>\n\n<p>After some small changes to the application's code, it worked with PHP 8.1 and generated filters.<\/p>\n\n<p>Once it worked, I updated <a href=\"https:\/\/github.com\/opdavies\/gmail-filter-builder\/tree\/3.x\/examples\">the examples<\/a>.<\/p>\n\n<p>Whilst it wasn't a difficult process in this instance, having a test suite I could rely on helped me to know it worked as expected during the upgrade.<\/p>\n\n<p>I don't know if I'll continue to use or maintain Gmail Filter Builder again, but it was an interesting exercise to do this morning.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "edf363d6ea23096050f54141a8e16bdc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json b/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json
index 59b94a1c0..f5a58602a 100644
--- a/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json
+++ b/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last month, I released the <a href=\"http:\/\/default\/podcast\/11-mark-conroy\">Beyond Blocks podcast episode<\/a> where I spoke with Mark Conroy.<\/p>\n\n<p>We spoke about a number of things, including the 'Content Access by Path' Drupal module he wrote, and I promised I'd write some automated tests for it as there weren't any at the time.<\/p>\n\n<p><a href=\"https:\/\/www.youtube.com\/live\/XTpliKd47Lg?si=o4-my-XHGvcM_mWS\">Yesterday on my Friday live stream<\/a>, I installed the module and learnt how it works whilst writing some automated tests.<\/p>\n\n<p>As is common, the first test took a little while to do as I got the setup steps working and learned how the module worked. Once that was passing, adding the others was fairly straight forward.<\/p>\n\n<p>After the stream, I <a href=\"https:\/\/www.drupal.org\/project\/content_access_by_path\/issues\/3428680\">created an issue<\/a> with a merge request to add the tests I wrote and enabling GitLab CI so they'll be automatically run for any other changes.<\/p>\n\n<p>Hopefully, it'll be reviewed soon, but I've done what I promised, contributed to more open-source software, learned more about a new module and, hopefully, others will have learned things from the stream too.<\/p>\n\n<p><a href=\"https:\/\/www.youtube.com\/@opdavies\">Subscribe to my YouTube channel<\/a> to be notified of future live streams!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "206e422b01263cdaf2eb41de25c44fc8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json b/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json
index 0858b10d4..f06828230 100644
--- a/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json
+++ b/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>There have been many discussions and videos recently asking if people still need to use TypeScript.<\/p>\n\n<p>There have also been large open-source projects moving from TypeScript back to plain JavaScript.<\/p>\n\n<p>The popular approach is using JSDoc comments - similar to PHP docblocks - to replicate some of TypeScript's features, such as autocompletion in IDEs and text editors.<\/p>\n\n<p>The suggested benefits are cleaner code and no build step, making it easier to work with and contribute to the code.<\/p>\n\n<p>I like using types in PHP and using static analysis tools such as PHPStan so, naturally, I gravitated to TypeScript.<\/p>\n\n<p>I wrote a custom form with TypeScript and Vue.js that was an entrypoint to a Drupal Commerce application - populating data from Drupal using an API endpoint and determining and creating a cart with the correct items based on the customer's selections.<\/p>\n\n<p>Whilst doing so, I found TypeScript very beneficial and I'll probably continue to use it in the future.<\/p>\n\n<p>But, leveraging JSDoc more in situations where I can't use TypeScript, such as writing Tailwind plugins and Stimulus applications, is great to know and to get the best of both.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f230560d474c0edb4725863e286d1ae8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json b/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json
index 2a0f6e3e7..77497bf0f 100644
--- a/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json
+++ b/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Upgrading from Drupal 7 to 8, 9 or 10 is a large task.<\/p>\n\n<p>You must create a new empty site, migrate your configuration and data, manually recreate anything else and rewrite any custom modules and themes.<\/p>\n\n<p>Since Drupal 8, things have been different.<\/p>\n\n<p>You can upgrade your site in place.<\/p>\n\n<p>No large code rewrite or data migration.<\/p>\n\n<p>Many contributed modules support multiple major Drupal versions simultaneously, so they may not need upgrading.<\/p>\n\n<p>Others may need small changes to remove deprecated code or be compatible with breaking changes, and some tools can automate some or all of the changes.<\/p>\n\n<p>The same applies to upgrading from Drupal 9 to 10, which will be the same for Drupal 11 next year.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "062455710dfbfed24f6c650fa013d504",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json b/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json
index ac90647c2..b32d3bd0e 100644
--- a/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json
+++ b/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After registering as an attendee, I've been upgraded to a speaker for next week's event and the first in-person Symfony UK meetup in two years.<\/p>\n\n<p>I'll be speaking about my experiences so far with mob programming - something that I spoke about at a PHP South Wales meetup last year.<\/p>\n\n<p>If you're interested and in London on the 11th of May, <a href=\"https:\/\/www.meetup.com\/symfony\/events\/293153957\">find out more and register<\/a>.<\/p>\n\n<p>Also, Happy Star Wars Day!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8077a02b9c896a424fb902f6e03884fd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json b/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json
index 5bb8d2cae..116429688 100644
--- a/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json
+++ b/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json
@@ -87,6 +87,5 @@
             "processed": "<p>How often do you use functions like <code>var_dump<\/code>, <code>dump<\/code>, <code>dd<\/code> or <code>console.log<\/code> to debug an issue?<\/p><p>You want to check the type or value of something, so you add the debug code and reload the page.<\/p><p>If you don't resolve it on the first attempt, you change it or add more debugging lines which, hopefully, you'll remember to clean up before committing your code.<\/p><p>This is a time-consuming process, especially if the code you're debugging isn't easy to trigger.<\/p><p>Maybe it only happens when you've submitted a long form, so you need to manually complete the form each time you want to debug it, if certain steps have already happened or the application state is a certain way.<\/p><p>Instead, consider writing an automated test.<\/p><p>They can be run when needed without needing to manually fill in forms or complete complex steps, and become a permanent part of the codebase rather than something that's only added temporarily whilst debugging.<\/p><p>They can be run manually by Developers, automatically in a CI pipeline and serve as documentation and examples.<\/p><p>Don't dump. Test.<\/p><p>P.S. If you want to learn how to write automated tests in Drupal, subscribe to <a href=\"http:\/\/localhost:8888\/atdc\">my free 10-day email course<\/a>.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json b/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json
index 1d04a1af3..603e94482 100644
--- a/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json
+++ b/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday I explained that Nix, or specifically NixOS, <a href=\"http:\/\/default\/daily\/2024\/11\/27\/nix-as-an-operating-system\">can be used to manage your entire operating system<\/a> in a declarative and reproducible way.<\/p>\n\n<p>My initial experience was running it on my laptop as a replacement for another Linux distribution, which I use to configure everything about my laptop and development environment, including my i3 window manager, Neovim and tmux configurations.<\/p>\n\n<p>I recently also started to use it on a new VPS to host several static websites, including this one and <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">various examples I've created as demos<\/a> or for presentations.<\/p>\n\n<p>Similarly to my laptop, I was able to declaratively install any required utilities, enable the Nginx web server, open firewall ports, add my virtual hosts and create and apply the required SSL certificates.<\/p>\n\n<p>And I can do this locally using <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/tree\/ec2767adfb6667184f884080a4f9b5d2a388a03d\/nix\/hosts\/hetznix\">the same NixOS configuration files<\/a> and applying it to the remote server.<\/p>\n\n<p>Now I'm running NixOS everywhere!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e7631b334d9daafcfa47e2f3cd60def6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json b/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json
index c565caf72..8a605cead 100644
--- a/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json
+++ b/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Static site generators <a href=\"http:\/\/default\/presentations\/sculpin\">like Sculpin<\/a> don't have a database like Drupal.<\/p>\n\n<p>The files are the database.<\/p>\n\n<p>In [my website repository][3], the <code>source\/_presentations<\/code> directory contains the files for my presentation pages, so these could be considered the presentations table and rows.<\/p>\n\n<p>But, because my content is in plain text files, they're very easy and quick to search in a text editor or on the command line using tools like <code>grep<\/code>.<\/p>\n\n<p>It's very easy and fast for me to find an old daily email, blog post or article I've written when I need to.<\/p>\n\n<p>This is also why I use <a href=\"http:\/\/default\/presentations\/rst2pdf\">rst2pdf for my presentation slides<\/a> and write them in reStructured text. It's very fast to find and re-use content.<\/p>\n\n<h2 id=\"counting-my-presentations\">Counting my presentations<\/h2>\n\n<p>Another example is being able to quickly count the number of presentations I've given.<\/p>\n\n<p>Here's an example of the front matter section from one of my presentations:<\/p>\n\n<pre><code class=\"markdown\">events:\n  - name: PHP South West\n    date: 2024-02-14\n    location: Bristol, UK\n    urls:\n      video: https:\/\/www.youtube.com\/watch?v=axy6ltc9meA\n      demo: https:\/\/phpsw-sculpin-demo.oliverdavies.uk\n  - name: BrumPHP\n    date: 2024-05-23\n    location: Birmingham, UK\n    url: https:\/\/www.eventbrite.com\/e\/brumphp-23rd-may-2024-tickets-803037766577\n  - name: PHP Berkshire\n    date: 2024-08-28\n    location: Reading, UK\n    urls:\n      slides: \/files\/presentations\/sculpin\/php-berkshire.pdf\n      website: https:\/\/www.meetup.com\/php-berkshire\/events\/301850284\n  - name: PHP Thames Valley\n    date: 2026-03-20\n    location: Oxford, UK\n    urls:\n      slides: \/files\/presentations\/sculpin\/php-thames-valley.pdf\n      code: https:\/\/code.oliverdavies.uk\/opdavies\/sculpin-demo\/src\/branch\/php-thames-valley\n      website: https:\/\/www.meetup.com\/php-thames-valley\/events\/305915971\n<\/code><\/pre>\n\n<p>Each presentation has a list of events, as most presentations I've given multiple times.<\/p>\n\n<p>Each event has a <code>date<\/code> that I can extract with <code>grep<\/code>:<\/p>\n\n<pre><code class=\"plain\">grep -r \"date:\" source\/_presentations\/*.md\n\nsource\/_presentations\/tdd-test-driven-drupal.md:    date: 2020-12-08\nsource\/_presentations\/tdd-test-driven-drupal.md:    date: 2023-10-17\nsource\/_presentations\/tdd-test-driven-drupal.md:    date: 2024-05-10\nsource\/_presentations\/tdd-test-driven-drupal.md:    date: 2024-11-20\nsource\/_presentations\/test-drive-twig-with-sculpin.md:    date: 2015-07-25\nsource\/_presentations\/things-you-should-know-about-php.md:    date: 2019-01-28\nsource\/_presentations\/things-you-should-know-about-php.md:    date: 2022-03-09\nsource\/_presentations\/things-you-should-know-about-php.md:    date: 2023-01-12\nsource\/_presentations\/upgrading-your-site-drupal-9.md:    date: 2020-09-02\nsource\/_presentations\/upgrading-your-site-drupal-9.md:    date: 2020-09-23\nsource\/_presentations\/upgrading-your-site-drupal-9.md:    date: 2021-04-22\nsource\/_presentations\/using-illuminate-collections-outside-laravel.md:    date: 2017-12-21\nsource\/_presentations\/using-illuminate-collections-outside-laravel.md:    date: 2018-08-28\nsource\/_presentations\/working-without-workspace.md:    date: 2023-04-06\nsource\/_presentations\/working-with-workspace.md:    date: 2020-08-11\nsource\/_presentations\/working-with-workspace.md:    date: 2020-09-09\nsource\/_presentations\/working-with-workspace.md:    date: 2021-02-02\n<\/code><\/pre>\n\n<p>To count them, I can add <code>| wc -l<\/code> to count the number of lines.<\/p>\n\n<p>But what if I have presentations in the future I don't want to count?<\/p>\n\n<p>To show just the dates, I can pipe the output to <code>awk<\/code> and only print the last item:<\/p>\n\n<pre><code class=\"plain\">grep -r \"date:\" source\/_presentations\/*.md | awk '{ print $NF }'\n\n2020-12-08\n2023-10-17\n2024-05-10\n2024-11-20\n2015-07-25\n2019-01-28\n2022-03-09\n2023-01-12\n2020-09-02\n2020-09-23\n2021-04-22\n2017-12-21\n2018-08-28\n2023-04-06\n2020-08-11\n2020-09-09\n2021-02-02\n<\/code><\/pre>\n\n<p>I can sort them by adding <code>| sort<\/code>, but that doesn't matter in this case.<\/p>\n\n<p>To remove any future presentations, I can pass the current date to <code>awk<\/code>, filter based on the date and count the number of lines in the result:<\/p>\n\n<pre><code class=\"plain\">grep -r \"date:\" source\/_presentations\/*.md | awk -v today=\"$(date +%Y-%m-%d)\" '{ if ($NF &lt; today) print $NF }' | wc -l\n\n104\n<\/code><\/pre>\n\n<p>This isn't how I'm calculating this on my website (I'm using a <a href=\"http:\/\/default\/daily\/2025\/05\/02\/extend\">custom Twig extension in Sculpin<\/a> for that), but this is an example of how multiple command line utilities can work together to perform a task - made possible using the static files from my website.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d941624a5b449961e856801045bb330f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json b/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json
index 79add9df9..bb732f46a 100644
--- a/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json
+++ b/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/06\/23\/drupal-10-3-released\">With Drupal 10.3 released<\/a>, Drupal 11 will be the next major version.<\/p>\n\n<p>There will be a Drupal 10.4, which will be the first minor maintenance version and supported until Drupal 12's release in 2026.<\/p>\n\n<p>According to <a href=\"https:\/\/www.drupal.org\/about\/core\/policies\/core-release-cycles\/schedule#current\">the current development cycle<\/a>, Drupal 11 will be released in a month's time on the 29th of July, with 11.1 in December alongside 10.4.<\/p>\n\n<p>Drupal 7 will be unsupported as of January 2025.<\/p>\n\n<p>With Drupal 10 websites needing to be upgraded to 10.3 before 11, it gives people the chance to test their applications on the latest Drupal 10 before upgrading to 11 - a refined version of 10 without the deprecated code.<\/p>\n\n<p>It also gives module and theme maintainers the opportunity to make their projects compatible before making any breaking changes, meaning upgrades should be more stable as the main changes can be done beforehand.<\/p>\n\n<p>I'm looking forward to upgrading my applications and projects to Drupal 11, and seeing what's to come in 11.1 and beyond.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0f4b0d278153b12d1d47eab4f90b1830",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json b/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json
index 0ba1bad8b..c71c37f3f 100644
--- a/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json
+++ b/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as <a href=\"http:\/\/default\/daily\/2022\/09\/04\/using-ansible-for-server-configuration\">configuring servers<\/a>, you can use Ansible to configure your own local machine and development environment.<\/p>\n\n<p>The change that you need to make is within the <code>hosts.ini<\/code> file:<\/p>\n\n<pre><code>127.0.0.1 ansible_connection=local\n<\/code><\/pre>\n\n<p>Instead of the server's IP address or hostname, use the localhost IP address and set <code>ansible_connection<\/code> to <code>local<\/code> to tell Ansible to run locally instead of using an SSH connection.<\/p>\n\n<p>Another way to do this is to set <code>hosts: 127.0.0.1<\/code> and <code>connection: true<\/code> in your playbook.<\/p>\n\n<p>Once this is done, you can run tasks, roles, and collections to automate tasks such as installing software, adding your SSH keys, configuring your project directories, and anything else that you need to do.<\/p>\n\n<p>For an example of this, you can see <a href=\"https:\/\/github.com\/opdavies\/dotfiles\">my dotfiles repository on GitHub<\/a>.<\/p>\n\n<hr>\n\n<p>Want to learn more about how I use Ansible? <a href=\"http:\/\/default\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "471a590b0815f9d675396ac79f411d89",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json b/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json
index 222585f4c..61ce6da3b 100644
--- a/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json
+++ b/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the majority of my <code>flake.nix<\/code> files, such as the one <a href=\"http:\/\/default\/daily\/2025\/01\/19\/minimum-viable-development-environment\">I've been experimenting with for Drupal projects<\/a>, I use <code>nixpkgs-unstable<\/code> as my primary input.<\/p>\n\n<p>The nixpkgs package manager has two major releases a year, in May and November, which would be 24.05 and 24.11 for 2024 respectively.<\/p>\n\n<p>Using <code>nixpkgs-unstable<\/code>, I get the latest packages and NixOS options and don't need to wait for the next major stable release.<\/p>\n\n<p>But doesn't that make things more likely to break when updating?<\/p>\n\n<p>The number of backwards incompatible changes and breakages on unstable are minimal, but I'd rather deal with small issues and updates regularly rather than only twice a year.<\/p>\n\n<p>Small updates more often are better, in my opinion.<\/p>\n\n<p>But, what if there is an issue with a package that I'm using, such as a build issue, regression or incompatibility?<\/p>\n\n<p>With flakes, I can import multiple versions of nixpkgs in the same configuration and use them where the configuration I need to.<\/p>\n\n<p>I need to in one project, I've added an input with nixpkgs pinned to a specific Git commit in the nixpkgs repository as some packages are using outdated versions and are no longer present in the latest releases.<\/p>\n\n<p>It's not all or nothing, I can pick which packages to be unstable and which I want to use stable or use older versions.<\/p>\n\n<p>See <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/dotfiles\/src\/commit\/a5c1c891020c5026ca1c2d83afd6cbe8002a136c\/flake.nix\">my dotfiles repository<\/a> for an example, where I have four versions of nixpkgs imported - including unstable and master, which is even newer.<\/p>\n\n<p>Every input is still locked in the <code>flake.lock<\/code> file, so everything is still reproducible whichever versions of nixpkgs I decide to use.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0c86a05ca569c1a814e9706841378658",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d783263e-b457-4785-b15c-ce631faf3192.json b/content/node.d783263e-b457-4785-b15c-ce631faf3192.json
index 1ff214095..c73d77cbc 100644
--- a/content/node.d783263e-b457-4785-b15c-ce631faf3192.json
+++ b/content/node.d783263e-b457-4785-b15c-ce631faf3192.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Once you start testing\/TDD, you can't go back<\/p>\n\n<p>Once you start writing automated tests or doing test-driven development, you can't go back to not doing it.<\/p>\n\n<p>When adding a new feature, you'd need to test every situation and use case manually in a browser or command line - and, very likely, do so multiple times.<\/p>\n\n<p>When fixing a bug, you'd need to follow the exact steps to replicate it and see it before attempting a fix. Again, you'd also need to test it manually.<\/p>\n\n<p>Also, because it passes a manual test, there's no guarantee it won't break unexpectedly in the future.<\/p>\n\n<p>While refactoring code without tests, bugs and regressions could be introduced as there's no test suite to run and ensure they're still passing.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When you're used to writing tests and doing test-driven development, you get used to the quick feedback loops and the confidence to make changes.<\/p>\n\n<p>It's easier to create a test that proves a bug exists and shows it'safixed because the test passes.<\/p>\n\n<p>Once you have these things, you can't stop and go back to not having tests.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fb71e18ebe99ec55d0c2fe23152a48ed",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json b/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json
index 6720b89e1..145c8c8ed 100644
--- a/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json
+++ b/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as using static data like Astro components and Markdown files, Astro allows you to pull in data from external APIs even if you're generating a static website.<\/p>\n\n<p>Astro's <a href=\"https:\/\/docs.astro.build\/en\/guides\/data-fetching\">Data Fetching documentation<\/a> shows how to do this using the global <code>fetch<\/code> function. This is the same approach that I've been using to build <a href=\"https:\/\/github.com\/opdavies\/oliverdavies.uk\/blob\/39314de34ce22b14cf85f816e4469cc4d6fb822c\/website\/src\/pages\/open-source.astro\">a page of my open-source projects<\/a>. I'm still working on it, but it fetches project information from both Drupal.org and GitHub and displays them on a page.<\/p>\n\n<p>This is also makes Astro a good option to be used as a front-end for decoupled projects that use a separate back-end CMS like Drupal to store and manage the content which it fetches and uses when generating the site.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "82e659503662822ad611232083fb7ed4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json b/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json
index 824519b8c..5a9a70a91 100644
--- a/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json
+++ b/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How do you update your environments?<\/p>\n\n<p>I've done it in two different ways on different projects.<\/p>\n\n<p>The most common way is to download a database from another environment and import it.<\/p>\n\n<p>The downside is that there needs to be a blessed database for everyone to use and someone needs to maintain and update.<\/p>\n\n<p>It can also contain user data, such as usernames, email addresses, passwords and webform submissions that you should sanitise or remove.<\/p>\n\n<p>The other option is to install the application from scratch.<\/p>\n\n<p>For Drupal projects, this means installing using the existing configuration to re-create the content types, fields, views, block types, etc.<\/p>\n\n<p>This confirms the configuration is installable or it will fail.<\/p>\n\n<p>As it's a fresh installation, it can be run by anyone without needing to maintain an blessed database and doesn't contain any user data.<\/p>\n\n<p>Then you can recreate any data, such as users or content, that you need or seed the database with standard data.<\/p>\n\n<p>For Drupal, <a href=\"http:\/\/default\/daily\/2024\/09\/16\/experimenting-with-the-default-content-module\">I've been using the Default Content module<\/a> for this, which has been working very well.<\/p>\n\n<p>If I can, I much prefer the install approach rather than importing.<\/p>\n\n<p>Which do you do, or do you do something else?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e320d92eee616c932a9a3fe26b35047c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json b/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json
index 2007226a0..c92904f0a 100644
--- a/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json
+++ b/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whether I'm doing test-driven development or not, I focus on making the feature work or fixing the bug in the simplest way possible.<\/p>\n\n<p>Then, once this is done, I can pass through the code again and refactor it as needed.<\/p>\n\n<p>I can split code into separate files, move logic from the Controller into separate services, ensure that patterns like dependency injection are followed, and checks like coding standards and static analysis are passing.<\/p>\n\n<p>I might deploy a change in its passing state and leave TODO comments or create follow-up issues to describe potential refactors or changes to be addressed later.<\/p>\n\n<p>The main goal is to get the application working and providing value for its users.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4830962fbdad357d03b6e3606bb1df38",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json b/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json
index 6f12280ce..7f0293120 100644
--- a/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json
+++ b/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, Beyond Blocks - <a href=\"http:\/\/default\/podcast\">the podcast I started last year<\/a> and has 20 published episodes - passed 1,000 total downloads.<\/p>\n\n<p>I've had some great guests on the show and discussed some interesting topics so far and I have others recorded and guests lined up for future episodes.<\/p>\n\n<p>This week's episode will be with Eirik Morland again - the first returning guest - where we discuss the improvements and changes that have been made to Violinist.io since we spoke in January.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/8-eirik-morland-violinist\">The first episode with Erik is here<\/a> if you want to listen to it beforehand.<\/p>\n\n<p>Thanks to all the guests and listeners of the podcast, and if you'd like to be a guest or suggest a topic, reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "421e5b39dd224c7b86dc375cf5539d56",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e.json b/content/node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e.json
index 968dd57ce..b046a2c99 100644
--- a/content/node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e.json
+++ b/content/node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e.json
@@ -87,6 +87,5 @@
             "processed": "<p><a href=\"https:\/\/dora.dev\/guides\/dora-metrics-four-keys\">The DORA metrics<\/a> are four key metrics used to indicate the velocity and stability of software development.<\/p><p>They are:<\/p><ul><li>Deployment frequency - how often you successfully releases to production.<\/li><li>Lead time for changes - the amount of time it takes for a commit to get into production.<\/li><li>Change failure rate - the percentage of deployments causing a failure in production.<\/li><li>Time to restore service - the amount of time it takes to recover from a failure in production.<\/li><\/ul><p>If you had an issue after a release to production, how long would it take you to recover?<\/p><p>If the amount of changes is small and it hasn't been long since the last release, it could be easy to revert the code change and re-deploy.<\/p><p>If it's been a while since the last release or the release contains large changes, this will be harder.<\/p><p>If you use feature flags, can you disable a flag and stop the code that's causing the issue?<\/p><p>What if you need to recreate the whole environment?<\/p><p>How old is your most recent backup? Have you verified the backup works and can be used to restore a database, the user-uploaded files or the whole environment?<\/p><p>A backup is only good if it is recent and can be restored. Otherwise, it's useless.<\/p><p>But, restoring from backups can take time and lose data, so this should be the last option.<\/p><p>Releasing small changes often and using tools like feature flags will help minimise the downtime from an issue and allow service to be restored as quickly as possible.<\/p>",
             "summary": ""
         }
-    ],
-    "feeds_item": []
+    ]
 }
\ No newline at end of file
diff --git a/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json b/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json
index bc8f32f97..2844e6930 100644
--- a/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json
+++ b/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Contrary to what many think (at least to begin with), releasing small, incremental changes often - maybe daily or weekly - is less risky than larger releases containing weeks or months of changes.<\/p>\n\n<p>If there is an issue after a large release, diagnosing and fixing it can take longer than a smaller release with fewer changes.<\/p>\n\n<p>You might have to revert and roll back to the previous release instead of being able to push a fix for a small change.<\/p>\n\n<p>With a small change, the risk of an issue is much lower as it has less chance to impact any other part of the application and is much easier for others to read, understand and debug.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ffb02a8c9c8b7c10c1db4f1162b1bfee",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json b/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json
index 0ccfe6289..c60a4cbf2 100644
--- a/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json
+++ b/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Here's a snippet of some Drupal code that I wrote last week. It's responsible for converting an array of nodes into a Collection of one of it's field values.<\/p>\n\n<pre><code class=\"language-php\">return Collection::make($stationNodes)\n  -&gt;map(fn (NodeInterface $station): string =&gt; $station-&gt;get('field_station_code')-&gt;getString())\n  -&gt;values();\n<\/code><\/pre>\n\n<p>There are two issues with this code.<\/p>\n\n<p>First, whilst I'm implicitly saying that it accepts a certain type of node, because of the <code>NodeInterface<\/code> typehint this could accept any type of node. If that node doesn't have the required field, the code will error - but I'd like to know sooner if an incorrect type of node is passed and make it explicit that only a certain type of node can be used.<\/p>\n\n<p>Second, the code for getting the field values is quite verbose and is potentially repeated in other places within the codebase. I'd like to have a simple way to access these field values that I can reuse anywhere else. If the logic for getting these particular field values changes, then I'd only need to change it in one place.<\/p>\n\n<h2 id=\"introducing-a-value-object\">Introducing a value object<\/h2>\n\n<p>This is the value object that I created.<\/p>\n\n<p>It accepts the original node but checks to ensure that the node is the correct type. If not, an Exception is thrown.<\/p>\n\n<p>I've added a helper method to get the field value, encapsulating that logic in a reusable function whilst making the code easier to read and its intent clearer.<\/p>\n\n<pre><code class=\"language-php\">namespace Drupal\\mymodule\\ValueObject;\n\nuse Drupal\\node\\NodeInterface;\n\nfinal class Station implements StationInterface {\n\n  private NodeInterface $node;\n\n  private function __construct(NodeInterface $node) {\n    if ($node-&gt;bundle() != 'station') {\n      throw new \\InvalidArgumentException();\n    }\n\n    $this-&gt;node = $node;\n  }\n\n  public function getStationCode(): string {\n    return $this-&gt;node-&gt;get('field_station_code')-&gt;getString();\n  }\n\n  public static function fromNode(NodeInterface $node): self {\n    return new self($node);\n  }\n\n}\n<\/code><\/pre>\n\n<h2 id=\"refactoring-to-use-the-value-object\">Refactoring to use the value object<\/h2>\n\n<p>This is what my code now looks like:<\/p>\n\n<pre><code class=\"language-php\">return Collection::make($stationNodes)\n  -&gt;map(fn (NodeInterface $node): StationInterface =&gt; Station::fromNode($node))\n  -&gt;map(fn (StationInterface $station): string =&gt; $station-&gt;getStationCode())\n  -&gt;values();\n<\/code><\/pre>\n\n<h1>&lt;&lt;&lt;&lt;&lt;&lt;&lt; HEAD:website\/source\/_daily_emails\/2022-10-03.md<\/h1>\n\n<blockquote>\n  <blockquote>\n    <blockquote>\n      <blockquote>\n        <blockquote>\n          <blockquote>\n            <blockquote>\n              <p>b9cea6d (chore: replace Sculpin with Astro):website\/src\/pages\/daily-emails\/2022-10-03.md\n              I've added an additional <code>map<\/code> to convert the nodes to the value object, but the second map can now use the new typehint - ensuring better type safety and also giving us auto-completion in IDEs and text editors. If an incorrect node type is passed in, then the Exception will be thrown and a much clearer error message will be shown.<\/p>\n            <\/blockquote>\n          <\/blockquote>\n        <\/blockquote>\n      <\/blockquote>\n    <\/blockquote>\n  <\/blockquote>\n<\/blockquote>\n\n<p>Finally, I can use the helper method to get the field value, encapsulating the logic within the value object and making it intention clearer and easier to read.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7ee7cb63765e8fc082bb197e047a1b09",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json b/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json
index 37575ccae..7260a37d2 100644
--- a/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json
+++ b/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Did you know Git remotes can have multiple URLs, so when you run a command like <code>git push origin main<\/code>, it can update more than one Git repository?<\/p>\n\n<p>I have a few situations where I thought this would be useful, where I need to mirror code between my and my client's Git repositories, or from my repository to a hosting environment to deploy a change.<\/p>\n\n<p>Originally I used <code>git remote add<\/code> to add a second named remote, such as <code>client<\/code> or <code>hosting<\/code>, but this needed me to push twice - once to <code>origin<\/code> and once to the second remote.<\/p>\n\n<p>Sometimes, this meant the repositories were out of sync until the second push was done and, if someone forgot to do it, code someone else was expecting to be on the second remote wasn't available.<\/p>\n\n<p>Adding a second URL to <code>origin<\/code> seemed like a good fix.<\/p>\n\n<p>Pushing once would update both remotes and everything would be in sync.<\/p>\n\n<p>But, it wasn't always the case.<\/p>\n\n<p>If the first push to <code>origin<\/code> failed, Git doesn't stop.<\/p>\n\n<p>It continues to push to the second repository, meaning there would be commits in one remote and not the other.<\/p>\n\n<p>This needed remedial work, such as manually running <code>git pull<\/code> and <code>git merge<\/code> to sync everything up again - and also creating merge commits, which I'm not a fan of.<\/p>\n\n<p>There's also no opportunity to check the CI pipeline checks passed before pushing to a hosting environment.<\/p>\n\n<p>Having to do a manual push allows you to check the pipeline run was successful and the tests, etc, passed before pushing potentially broken code to the hosting environment.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>There are pros and cons to both approaches and the right option will depend on each person's and team's situation.<\/p>\n\n<p>For now, I'm switching back to having separate remotes and doing two pushes.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "366cf3181f0d0907a5bca82e961c730d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json b/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json
index ecc7e9a08..4467708ac 100644
--- a/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json
+++ b/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2023\/09\/13\/which-type-of-test-should-i-use\">In yesterday's email<\/a>, I described the different types of tests available in Drupal and how to determine which test I should use.<\/p>\n\n<p>I start with functional tests and move to kernel or unit tests when needed, so I usually have more functional tests, some kernel tests and a few unit tests.<\/p>\n\n<p>This is the outside-in approach to testing.<\/p>\n\n<p>The opposite is inside-out testing when you start with unit tests and have fewer functional tests.<\/p>\n\n<p>Tests written outside-in are slower to run as they need to perform tasks like HTTP requests and interact with the database, compared to unit tests, which are fast to run but do reply on mocking dependencies rather than using real services and content.<\/p>\n\n<p>Which do you prefer? Reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "135db619112384902229409c9c646b9f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json b/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json
index cfe6c11b6..485a5d389 100644
--- a/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json
+++ b/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In the last few posts, I've talked about using Ansible for configuring servers and local environments, during both of which, you're likely to have some sensitive or secret values. These could be database credentials within your application and on your server, and your SSH private keys within your local environment.<\/p>\n\n<p>Rather than committing these to a code repository in plain text, Ansible includes the <code>ansible-vault<\/code> command to encrypt values.<\/p>\n\n<p>To see this working, run <code>ansible-vault encrypt_string my-secret-password<\/code>, enter a password, and then you should see something like this:<\/p>\n\n<pre><code>!vault |\n  $ANSIBLE_VAULT;1.1;AES256\n  33353031663366313132333831343930643830346531666564363562666136383838343235646661\n  6336326637333230396133393936646636346230623932650a333035303265383437633032326566\n  38616262653933353033376161633961323666366132633033633933653763373539613434333039\n  6132623630643261300a346438636332613963623231623161626133393464643634663735303664\n  66306433633363643561316362663464646139626533323363663337363361633333\n<\/code><\/pre>\n\n<p>This is the encrypted version of that password, and this could be committed and pushed to a code repository.<\/p>\n\n<p>You can use it within a playbook, and you'll be prompted to re-enter the password so that Ansible can decrypt and use it.<\/p>\n\n<p>Rather than a single string, you could have a file of variables that you want to encrypt. You can do this by running <code>ansible-vault encrypt vault.yml<\/code> and include it as before. Again, you'll be prompted by Ansible so that it can decrypt and use the values.<\/p>\n\n<p>For an example of how I'm using Ansible Vault, see <a href=\"https:\/\/github.com\/opdavies\/dransible\/tree\/986ba5097d62ff4cd0e637d40181bab2c4417f2e\/tools\/ansible\">the Dransible repository<\/a> on GitHub or my <a href=\"http:\/\/default\/presentations\/deploying-php-ansible-ansistrano\"> Deploying PHP applications with Ansible, Ansible Vault and Ansistrano<\/a> talk.<\/p>\n\n<hr>\n\n<p>Want to learn more about how I use Ansible? <a href=\"http:\/\/default\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1ac2b400239670e99f97edf6edae6a39",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json b/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json
index c0e1104cf..3298cd360 100644
--- a/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json
+++ b/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been re-watching a livestream series from a few years ago, showing a SaaS product being built.<\/p>\n\n<p>The series was created from two full-day live streams to create a minimum viable product (MVP) version of the application.<\/p>\n\n<p>Several times, things like this were said:<\/p>\n\n<ul>\n<li>This will eventually need to be customisable.<\/li>\n<li>When we have multiple users, but now we only have one.<\/li>\n<li>Let's hard-code this for now and refactor it later.<\/li>\n<li>This isn't pixel-perfect, but let's move on.<\/li>\n<\/ul>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>As they focused on creating an MVP version, they added these things to a to-do list or wrote comments in the code to revisit it later rather than slowing down the initial development and pre-optimising the code for use cases that didn't exist yet.<\/p>\n\n<p>If there's only one user, there's no need to write code to handle multiple users.<\/p>\n\n<p>Later, once the application is launched, that feature can be added.<\/p>\n\n<p>And, because they were writing automated tests, they'd be able to refactor and extend the code and not worry about breaking it as the tests would confirm that the functionality still worked.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "86193996441d0e9ec3a4d46be5b79eb2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json b/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json
index ffa9da57b..524a6a4bb 100644
--- a/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json
+++ b/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Writing custom assertions is a great way to clean up your test code.<\/p>\n\n<p>Here's an example from one of my client Drupal projects:<\/p>\n\n<pre><code class=\"language-php\">private static function assertProductVariationHasPrice(ProductVariationInterface $productVariation, string $expectedPrice): void {\n  self::assertSame(\n    actual: $productVariation-&gt;getPrice()-&gt;getNumber(),\n    expected: $expectedPrice,\n  );\n}\n<\/code><\/pre>\n\n<p>This one wraps a single assertion, but they could also include multiple assertions or additional steps.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>A custom assertion is a simple function but it makes the test code more readable and less repetitive.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a7a933ef1250a866505ee7da5f99d039",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json b/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json
index 4940be490..29a137f2a 100644
--- a/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json
+++ b/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Automated test suites don't tell you everything works - they tell you what you've tested isn't broken.<\/p>\n\n<p>Having tests doesn't mean your code is bug-free. There could be edge cases or scenarios you haven't tested for that contain bugs, even though your test suite is passing.<\/p>\n\n<h2 id=\"what-do-we-do%3F\">What do we do?<\/h2>\n\n<p>When you find a bug, try replicating it within an automated test before attempting to fix it.<\/p>\n\n<p>Once you have a failing test and can replicate the issue, go ahead and fix it.<\/p>\n\n<p>If the test passes, you know you've fixed the bug and solved the issue.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Now you have this test, you cannot re-add the bug again without the test failing. You've prevented anyone from accidentally re-introducing it in the future and increased your test coverage.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bee10cd012e328234f493c6d52a62c57",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json b/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json
index 2c21f778d..8f6597934 100644
--- a/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json
+++ b/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When running commands like <code>git log<\/code> or viewing pull requests, you can see the number of lines that have been added, edited or removed.<\/p>\n\n<p>When adding new features, it's likely you'll be adding code.<\/p>\n\n<p>If you're refactoring code, you may have less code than before.<\/p>\n\n<p>I like commits like this.<\/p>\n\n<p>It's not true that having fewer lines of code means the code is better, but having less code makes it easier to maintain and more secure.<\/p>\n\n<p>You don't need to upgrade and maintain code that you aren't using, so why not remove it?<\/p>\n\n<p>Why have old TODO comments, <code>dd()<\/code>, <code>var_dump()<\/code> or <code>console.log()<\/code> functions in the code?<\/p>\n\n<p>If they're not used, they can be removed.<\/p>\n\n<p>I recently read a post that suggested there were 5 to 10 bugs in each 1,000 lines of production code as a general rule, so the less code there is, the fewer places there are for bugs to hide.<\/p>\n\n<p>In general, for production code, less is more.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4050be034c1d59312fb930c3290468db",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json b/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json
index e25df29d0..ed2dbecd8 100644
--- a/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json
+++ b/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When writing object-orientated code, particularly in PHP, you usually write method names using camel-case letters - such as:<\/p>\n\n<pre><code class=\"language-php\">public function doSomething(): void {\n  \/\/ ...\n}\n<\/code><\/pre>\n\n<p>This is also true when writing methods within a test class - only that the method name is prefixed with the word <code>test<\/code>:<\/p>\n\n<pre><code class=\"language-php\">public function testSomething(): void {\n}\n<\/code><\/pre>\n\n<p>This is probably expected and complies with the PSR code style standards like PSR-12.<\/p>\n\n<p>Something that I've seen some PHP developers and some frameworks prefer is to write their test methods using snake-case letters and  commonly removing the <code>test<\/code> prefix in favour of using an annotation:<\/p>\n\n<pre><code class=\"language-php\">\/** @test *\/\npublic function the_api_should_return_a_200_response_code_if_everything_is_ok(): void {\n  \/\/ ...\n}\n<\/code><\/pre>\n\n<p>This is something that I've done myself for a while, but now I'm starting to reconsider both options.<\/p>\n\n<p>Whilst it's more readable, especially for longer test names (which I like to write), it's not consistent with method names in non-test files or non-test methods in test files; it looks odd if I need to add another annotation (do I keep a single annotation on one line, or just those with multiple annotations on the separate lines), and to do this, I need to disable some code sniffer rules for code to pass the PHPCS checks.<\/p>\n\n<p>If I used camel-cased names, I wouldn't need the PHPCS overrides, the annotations would be simpler, and the code would be more consistent - so I think I'll try that way again in the next tests that I write and see how it feels.<\/p>\n\n<p>Which do you prefer, and which would you expect to see in your project?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "142789ac0ec97b452b470ffc7dfb962c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dab13df7-2835-407a-90c5-f5574585718b.json b/content/node.dab13df7-2835-407a-90c5-f5574585718b.json
index 292164156..884087930 100644
--- a/content/node.dab13df7-2835-407a-90c5-f5574585718b.json
+++ b/content/node.dab13df7-2835-407a-90c5-f5574585718b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You've heard of README-driven development, where you start by writing a README and documenting what you're going to code you start coding.<\/p>\n\n<p>I've recently been doing diagram-driven development, where I start with a diagram and build a flow chart of the functionality, what pieces I'll need and what the information flow or user journey looks like.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/08\/18\/mermaid-markdown-for-charts\">I've been using Mermaid<\/a>, so the diagrams are easy and quick to create, are version-controlled and a stored in the same code repository.<\/p>\n\n<p>You can see an example in the <a href=\"https:\/\/github.com\/opdavies\/build-configs\/tree\/f02fce7ff5b5cff202ec8b893a4b3c7e7c56f3c4\/docs\">Build Configs repository<\/a>, which is <a href=\"http:\/\/default\/daily\/2024\/08\/27\/build-configs-is-open-source\">now public and open-source<\/a>.<\/p>\n\n<p>Similar to writing the README first, creating a diagram upfront helps me clarify what I'm going to build and how I'm going to do it.<\/p>\n\n<p>And using Mermaid means I can create it and push a temporary branch or create a pull or merge request to share it with colleagues to review before I start.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "79d80b699a527736bd9685bbb68dad9e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json b/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json
index c9f924f61..1bf92acbc 100644
--- a/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json
+++ b/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently developed a new custom module for a Drupal project.<\/p>\n\n<p>It pulls in an initial set of data from an API, builds a block that includes a form, makes another API request based on the form selections and displays the result to the user.<\/p>\n\n<p>Part of the API base URL is <code>v1<\/code> so I assume that, at some point, there could be breaking changes in the API response and the endpoint will change to be <code>v2<\/code>.<\/p>\n\n<p>If this happens, I don't to have to change the existing code to make it work with a new version of the API.<\/p>\n\n<p>I want to be able to write new code to work with the new version.<\/p>\n\n<p>For the version 1 of the API, I've written a <code>V1ApiClient<\/code> that makes and processes the response from the v1 endpoint.<\/p>\n\n<p>If we move to version v2, I'll write a <code>V2ApiClient<\/code> that will work with the version 2 response.<\/p>\n\n<p>Each implementation will have its own logic but implement a <code>ClientInterface<\/code> to ensure both have the same required methods to make them interchangeable.<\/p>\n\n<p>Then I can switch between implementations as needed and not have to change the existing code.<\/p>\n\n<p>Similar to feature toggles, this allows me to deploy new code without making it immediately active.<\/p>\n\n<p>I don't need to hold back merging changes until I'm ready to change the API version.<\/p>\n\n<p>The same approach works in other situations, like payment gateways.<\/p>\n\n<p>What if you need to switch to a different payment gateway or map service?<\/p>\n\n<p>Instead of tightly coupling to one implementation, creating different implementations and strategies makes the code more flexible and easier if you need to change implementations or support multiple implementations at once.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "03586d61c309592caca993fa7b3f584c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json b/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json
index 591030226..ee5a7c2e7 100644
--- a/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json
+++ b/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few days ago, I said it's been 8 years since I started my dotfiles repository and kept my configuration files in version control.<\/p>\n\n<p>But why do this?<\/p>\n\n<p>It makes it easy to share the same configuration across multiple computers, such as personal and work or different setups for clients.<\/p>\n\n<p>It's also a backup of my configuration. If I need to reinstall my system or start fresh, I don't need to configure everything again manually.<\/p>\n\n<p>If you work on a team, you can share your configuration with colleagues, find things that work well for the team, and anything that could cause issues.<\/p>\n\n<p>I can experiment with settings and programs and then revert them again if I want to.<\/p>\n\n<p>If I add or remove a program or change a setting, I have the Git commit log to refer to, and I can document why I made that change and what problem it solves in the message body.<\/p>\n\n<p>I can review it in the future in case I need it again or want to re-evaluate it.<\/p>\n\n<p>Like on other projects, capturing the why is important. The what can be seen in the diff and speaks for itself, but it doesn't explain why I made the change and won't help if I look at that commit in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d5ed61ce59348374630aa49fea8f3709",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json b/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json
index aed33515a..52a286382 100644
--- a/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json
+++ b/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I remember seeing a talk or listening to a podcast during which they mentioned Travis, as in the CI pipeline tool, and some of the things they were using it for.<\/p>\n\n<p>They also said that their client thought Travis was a person on their team.<\/p>\n\n<p>In some ways, having a CI pipeline performing automated checks and tests is like having another team member.<\/p>\n\n<p>Instead of waiting for a person to manually check code styles, run tests and spot potential bugs, why not automate them and run them in the CI pipeline every time code changes are pushed?<\/p>\n\n<p>You'll get results sooner than waiting for a person do check the code by hand and, arguably, more consistent results.<\/p>\n\n<p>Then, if you do peer code reviews, you know the basics are already done and the reviewer can focus on other things.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "58c9da441a16db434c006de482ddb439",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json b/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json
index 365983c2c..455fc4a97 100644
--- a/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json
+++ b/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A key takeaway from Rob Allen's Domain-Driven Design talk was defining ubiquitous language and avoiding the phrase \"That's not what I meant\".<\/p>\n\n<p>Even a simple table or glossary that lists business and domain-specific terms and their agreed meaning is very helpful to ensure everyone in the discussion is on the same page and means the same thing.<\/p>\n\n<p>Rob's example was using the words \"policy\" and \"risk\" when dealing with insurance clients.<\/p>\n\n<p>A common issue I've seen is where people are referred to as customers by the business and users within the software.<\/p>\n\n<p>Ideally, these should be consistent, and the code should match the business terminology.<\/p>\n\n<p>This can be complicated further by different areas of the business, such as a marketing team that may refer to people as subscribers.<\/p>\n\n<p>Without the ubiquitous language being defined, the requirements are more likely to be misunderstood and the wrong solution delivered, resulting in \"that's not what I meant.\".<\/p>\n\n<p>This then means the work needs to be re-done and delayed, which can be expensive and time-consuming.<\/p>\n\n<p>Another approach is to work in small batches, which is something I've written about before, and getting feedback from customers as early and often as possible so, if there is a misunderstanding, the minimum amount of time has been spent before it's realised and rectified.<\/p>\n\n<p>Rob, of course, covered a lot more about DDD in his talk, and I'm looking forward to re-watching it once the video from the meetup is released.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bbd5da09465e121b021023b291b56bcd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json b/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json
index 2958e9f39..50f3c3b34 100644
--- a/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json
+++ b/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>On the 5th of January, Drupal 7 will be end of life and have no further updates.<\/p>\n\n<p><a href=\"https:\/\/www.drupal.org\/blog\/drupal-70-is-released\">Released in January 2011<\/a>, Drupal 7 will be 14 years old in January and will have outlived Drupal 8 and 9 which are already unsupported.<\/p>\n\n<p>There are a lot of Drupal 7 sites still in production, but it's been interesting to see usage numbers for the Override Node Options module <a href=\"http:\/\/default\/daily\/2024\/11\/16\/an-interesting-thing-i-spotted-about-the-override-node-options-module\">decrease for Drupal 7 and increase for Drupal 8+<\/a> over the last year.<\/p>\n\n<p>I'm excited to see Drupal usage continue to move towards the newer versions so everyone can benefit from the new features and improvements in Drupal 10 and 11 and the new Drupal CMS project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e93df0be19a187ce2cfa64f7e7f55371",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json b/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json
index 2603124bd..af05ab48d 100644
--- a/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json
+++ b/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently recorded an episode of <a href=\"http:\/\/default\/podcast\">Beyond Blocks<\/a> with Yuri Gerasymov, who runs Diffy.<\/p>\n\n<p>He and I discussed visual regression testing, why you'd use it, and some features Diffy offers.<\/p>\n\n<p>I usually write a combination of browser, kernel and unit tests within an application framework like Drupal and Symfony or behavioural tests with Behat.<\/p>\n\n<p>These validate that my logic works as expected and that functions return the correct results or pages return the correct response codes and content.<\/p>\n\n<p>There are types of issues, though, such as breakages within the page layout or structure, which these tests won't discover but can be identified by visual regression tests that compare before and after screenshots.<\/p>\n\n<p>I added to my website during the recording and can see what value it offers as an additional layer of testing on top of the tests I already write.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2b01095ab8d31f34c714ec27f276817e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json b/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json
index ed8ead349..4aeff7fca 100644
--- a/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json
+++ b/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've seen a lot on social media and posts and videos recently about Laravel Pipelines - functionality that's been present in Laravel and used within the framework for some time - but there was only documentation added for it last month as part of the Laravel 10 release.<\/p>\n\n<p>This is an example from the new documentation:<\/p>\n\n<pre><code class=\"language-php\">$user = Pipeline::send($user)\n    -&gt;through([\n        GenerateProfilePhoto::class,\n        ActivateSubscription::class,\n        SendWelcomeEmail::class,\n    ])\n    -&gt;then(fn (User $user) =&gt; $user);\n<\/code><\/pre>\n\n<p>Once a user has registered, it is passed through different classes - each performing a task and calling the next class in the list, similar to middleware. Once finished, a final action is performed or a value is returned.<\/p>\n\n<p>As someone who doesn't use Laravel often but does use standalone components - like <code>illuminate\/collections<\/code> - in other PHP projects, I'm interested to see how I can use this via <code>illuminate\/pipeline<\/code> to refactor some of my existing code.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f662b53b72b350d04041ab2dc4b49ad0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json b/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json
index a2c4e86bc..784982ee0 100644
--- a/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json
+++ b/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week's guest on the Beyond Blocks podcast is Nick Janetakis - a Software Developer, Docker Captain and Teacher who focuses on building and deploying web apps.<\/p>\n\n<p>I'm a long-time consumer of Nick's content via his blog, YouTube channel and courses, so it was great to discuss Docker, content creation and more with him.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/12-nick-janetakis-docker\">Listen to the episode<\/a><\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3890d1a3914bf410eda6c0659d3df851",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json b/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json
index 579a56f6b..2b334f15b 100644
--- a/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json
+++ b/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The purpose of any pre-production version of your website or application (any version that isn't the public live one) is to mimic the production version and as a test run for deployments.<\/p>\n\n<p><strong>If I deploy this feature, will it break the website?<\/strong><\/p>\n\n<p>The issue with most staging and other pre-production environments is that they differ from what's on production. It may have been some time since the latest data was added, and its value is only as good as how close to production it is and how likely it is to find potential issues in production.<\/p>\n\n<p>If they differ greatly, the staging environment offers no value.<\/p>\n\n<p>It's not a true comparison, and instead of being a test run for a deployment to production, you're only reviewing the deployment to the staging environment itself.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The best situation I've experienced is where a sanitised snapshot was synced to all pre-production environments every night.<\/p>\n\n<p>I knew that my environment was, at most, a single day out of date, and I was confident that my changes would work in production if they did there.<\/p>\n\n<p>In that situation, the staging site works and testing it has value, but if it's weeks or months out of date, it doesn't, as there are too many differences for it to be an accurate representation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "07c1e92a060647818b3b343a1a9f7df4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json b/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json
index 83275cc28..33c4da82f 100644
--- a/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json
+++ b/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When doing test-driven development, once you've written a failing (a.k.a. red) test, the main objective is to get to a green (a.k.a. passing) test as quickly as possible via the simplest method.<\/p>\n\n<p>Even if that means returning a hard-coded value.<\/p>\n\n<p>Once the test passes, it or the code it's testing can be refactored.<\/p>\n\n<p>Or you can move on to the next test and, if you need to change the hard-coded value to get both tests to pass, then it is the right time to do so.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1ae8abd3b43dffe1b4f702b6060f9213",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json b/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json
index b78c74821..4c8285e05 100644
--- a/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json
+++ b/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>To do test-driven development, you start by writing a test which, because you're testing code that doesn't exist, will fail.<\/p>\n\n<p>The objective is to get the get the test to pass.<\/p>\n\n<p>You want to write just enough code to get the test to pass.<\/p>\n\n<p>It can be the simplest and naive code possible as long as it gets the tests to pass.<\/p>\n\n<p>Once the test passes, you can refactor and change the code in any way you want.<\/p>\n\n<p>This may be changing from a <code>foreach<\/code> loop to using a function like <code>array_map<\/code> or <code>array_reduce<\/code>, or splitting logic into separate classes.<\/p>\n\n<p>You may refactor your refactor and decide that a name or approach isn't correct and change it.<\/p>\n\n<p>You may split your code into service classes and then decide to use commands or actions.<\/p>\n\n<p>You can make whatever changes you want as long as the tests continue to pass.<\/p>\n\n<p>The implementation can change, but the outcome stays the same.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "903c2f153f561fe50422411d38fba8cd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json b/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json
index 46df845cb..cd39e478e 100644
--- a/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json
+++ b/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After writing about <a href=\"http:\/\/default\/daily\/2024\/11\/10\/write-plain-text-files\">using text files for my personal wiki<\/a>, I've found others who do the same.<\/p>\n\n<ul>\n<li>Derek Sivers wrote a blog post about <a href=\"https:\/\/sive.rs\/plaintext\">why he uses text files<\/a>.<\/li>\n<li>Ricky Kresslein read Derek's blog post and migrated his notes, <a href=\"https:\/\/kressle.in\/txt\">wrote a blog post<\/a> and recorded a video.<\/li>\n<li>Sebastian Daschner recorded a video about <a href=\"https:\/\/www.youtube.com\/watch?v=-afP8cpBpXU\">a simple knowledge system<\/a> using plain-text files and asciidoc.<\/li>\n<li>Nick Janetakis, a former guest <a href=\"http:\/\/default\/podcast\/nick-janetakis-docker\">on the Beyond Blocks podcast<\/a>, wrote a small Bash script to maintain his plain text files, which I've <a href=\"https:\/\/github.com\/opdavies\/dotfiles\/commit\/73d801d7acf53d82f341f738c655fb6a2fcdcd70\">added to my NixOS configuration<\/a>.<\/li>\n<\/ul>\n\n<p>Do you know anyone else who uses plain text files for their notes?<\/p>\n\n<p>If you don't, I'd recommend it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1dee6b9fb013248db22e14f83b12d176",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json b/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json
index 0bc6c277c..5ec88cb29 100644
--- a/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json
+++ b/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as my consulting and development work, and educational content such as my <a href=\"http:\/\/default\/atdc\">automated testing email course<\/a>, I'd like to release something as a project people can use or a SaaS product for people to purchase.<\/p>\n\n<p>One of my original ideas was to build a website for speakers to upload and manage their presentations, but I found <a href=\"https:\/\/symposiumapp.com\">Symposium<\/a>.<\/p>\n\n<p>I was building a hosted dashboard for multiple Drupal applications so people could see all their projects and available updates in one place, but someone made me aware of <a href=\"https:\/\/www.drupal-remote-dashboard.com\">Drupal Remote Dashboard<\/a>. Whilst it's not exactly the same, the idea is similar, so I'm thinking whether to continue with this.<\/p>\n\n<p>I have a short list of other ideas, but if you have one, reply and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "14bc4a0b3a6ff96445c7195431abf9ff",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json b/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json
index c2dafd9e0..ed6c6e572 100644
--- a/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json
+++ b/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/presentations\/git-flow\">The first conference talk I gave<\/a> was at DrupalCamp London 2014.<\/p>\n\n<p>The talk was about Git Flow - a popular branching scheme I was using to manage a project, where there are different branches for development and production versions of the software and separate branches for features, releases and hotfixes.<\/p>\n\n<p>It's been a standard approach as I've worked on different projects and teams, usually with pull or merge requests and code reviews.<\/p>\n\n<p>But why do people still use it?<\/p>\n\n<p>I was conducting technical interviews recently and every candidate explained how they used Git Flow or something inspired by it, and GitHub and GitLab have their own simplified versions.<\/p>\n\n<p>Vincent Driessen wrote the original Git Flow blog post in January 2010, though he updated it in March 2020 to add this note of reflection:<\/p>\n\n<blockquote>\n  <p>This model was conceived in 2010, now more than 10 years ago, and not very long after Git itself came into being. In those 10 years, git-flow (the branching model laid out in this article) has become hugely popular in many a software team to the point where people have started treating it like a standard of sorts \u2014 but unfortunately also as a dogma or panacea.<\/p>\n  \n  <p>During those 10 years, Git itself has taken the world by a storm, and the most popular type of software that is being developed with Git is shifting more towards web apps \u2014 at least in my filter bubble. Web apps are typically continuously delivered, not rolled back, and you don't have to support multiple versions of the software running in the wild.<\/p>\n  \n  <p>This is not the class of software that I had in mind when I wrote the blog post 10 years ago. If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.<\/p>\n  \n  <p>If, however, you are building software that is explicitly versioned, or if you need to support multiple versions of your software in the wild, then git-flow may still be as good of a fit to your team as it has been to people in the last 10 years. In that case, please read on.<\/p>\n  \n  <p>To conclude, always remember that panaceas don't exist. Consider your own context. Don't be hating. Decide for yourself.<\/p>\n<\/blockquote>\n\n<p>Since adopting trunk-based development and continuous integration and delivery, I've worked faster and avoided merge conflicts, which wasn't the case before, even when I was the only one working on a codebase.<\/p>\n\n<p>It's a simpler workflow.<\/p>\n\n<p>I don't need to think about whether this branch is a feature or a hotfix, and I've rarely seen release and hotfix branches used as described in the original blog post.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Do what works best for you and your team, but don't adopt something because it's the \"standard\" approach.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9b0cfa53767098dc8873acdefd4d5eba",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.defbeab8-28ca-4444-b09b-5121de794602.json b/content/node.defbeab8-28ca-4444-b09b-5121de794602.json
index 3055506c8..a8740c4aa 100644
--- a/content/node.defbeab8-28ca-4444-b09b-5121de794602.json
+++ b/content/node.defbeab8-28ca-4444-b09b-5121de794602.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I once joined a project that had some automated tests and quality checks which were run automatically in a CI pipeline whenever code was pushed.<\/p>\n\n<p>The problem was that one of the checks were failing which caused the pipeline to fail.<\/p>\n\n<p>Because it was failing, it was ignored.<\/p>\n\n<p>But if it's already failing and being ignored, how do you know you haven't broken something unexpectedly?<\/p>\n\n<p>This is the value you get from automated tests that are run regularly, but if failures are being ignored, they aren't adding value or confidence the code works.<\/p>\n\n<p>In the end, it was a small fix to get the tests and CI pipeline passing again and we made sure to keep it passing as much as possible once it was.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d1ab27d91583fa59d50cb8b6676b29d7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json b/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json
index ee35eb358..c9bff7732 100644
--- a/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json
+++ b/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you're doing trunk-based development where multiple people are committing and pushing work to the same branch, what do you do if you've pushed a commit that fails the checks and breaks the pipeline?<\/p>\n\n<p>This is a bad state and needs to be solved as soon as possible as it's causing a problem for everyone else.<\/p>\n\n<p>If the pipeline is failing, someone else could push a change and have it fail for a different reason, but wouldn't know.<\/p>\n\n<p>The responsibility is on the person who pushed the failing commit to resolve it and get the pipeline passing again as soon as possible.<\/p>\n\n<p>You break it, you bought it.<\/p>\n\n<p>Hopefully, the changes in the failing commit are small and it's something you can resolve quickly and push a fixed commit.<\/p>\n\n<p>If you can't fix it within a few minutes, revert the failing commit and try again.<\/p>\n\n<p>What if someone's pushed a failing commit and hasn't fixed it in a timely manner?<\/p>\n\n<p>Revert it for them, fix the pipeline and unblock the rest of the team.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "59d38746fc261bf6e7575946a0fea245",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json b/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json
index f88993e98..5fa8d1884 100644
--- a/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json
+++ b/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>\"If you comment everything, people won't read them.\"<\/p>\n\n<p>\"As soon as one comment is incorrect, the result will be ignored.\"<\/p>\n\n<p>These are two comments I heard recently referring to code comments.<\/p>\n\n<p>If there are too many comments, people will get lost in the information. They won't be able to differentiate boilerplate comments from valuable ones, and as soon as one comment is incorrect, people will assume that others could likely be incorrect too and ignore them.<\/p>\n\n<p>A solution to these is to only comment what needs to be commented.<\/p>\n\n<p>Only write comments that add value, and if there are fewer comments, they are easier to read and maintain - making it more likely they will be incorrect.<\/p>\n\n<p>This is an example from an open source pull request:<\/p>\n\n<pre><code class=\"language-php\">\/**\n * An interface for field access override.\n *\/\ninterface FieldAccessOverrideInterface {\n<\/code><\/pre>\n\n<p>In my opinion, this doesn't add any value or additional context as it repeats what's already there.<\/p>\n\n<p>Something I put in my project configuration files is to tweak the coding standards to not check, for example, for class and method docblocks - allowing me to add them where I want and where I think they're needed and add value.<\/p>\n\n<p>I think this is better than having comments everywhere, and I can focus on the ones that matter.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3153413157ef5cd139bceebefc51bf52",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json b/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json
index f4e3e5912..8eaec9570 100644
--- a/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json
+++ b/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Instead of running the same commands over and over again, some of the command-line tools that I use have a <code>watch<\/code> mode and will automatically re-run when files are changed, however, not all do.<\/p>\n\n<p>Instead of doing this manually, I can achieve the same thing though using a tool called <code>nodemon<\/code> - a script monitor for node projects, but it can work with non-node projects too.<\/p>\n\n<p>Here's an example where I'm automatically re-running my PHPUnit tests using a <code>just test<\/code> recipe each time a file within my custom modules directory changes:<\/p>\n\n<pre><code>nodemon \\\n  --watch web\/modules\/custom \\\n  --ext '*' \\\n  --exec \"just test --stop-on-failure --colors=always\"\n<\/code><\/pre>\n\n<p>I specify the files or directories I want to watch, which file extensions should trigger a restart (in this case, I've enabled all extensions), and the command to execute.<\/p>\n\n<p>This watches all files and run all of the tests, but I can filter either if I need to.<\/p>\n\n<p>As well as PHP tools like PHPUnit and PHPStan, I also use this for other things such as when creating presentation slides with rst2pdf where I can automatically re-generate the PDF whenever I update the rst file.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a773ef0f61d9a98ee69ac78735c23bbb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json b/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json
index ca0dc953c..998eee545 100644
--- a/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json
+++ b/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something that came up in my discussion with Dave Liddament for the Beyond Blocks podcast was that there seem to be two ways of writing PHP code.<\/p>\n\n<p>One is writing strict code by enabling strict typing, using parameter and return types, and leveraging tools like PHPStan at a high level to analyze code.<\/p>\n\n<p>The other is no not use types and to use a more \"duck typing\" approach.<\/p>\n\n<p>The term \"visual debt\" came from a video discussing the pros and cons of these approaches.<\/p>\n\n<p>The same can be said for JavaScript and TypeScript, but PHP can do both and gives the Developer the choice of how they write their code.<\/p>\n\n<p>I prefer writing strict code and for my code to be as explicit as possible, but I appreciate not everyone does and I like that PHP caters for both.<\/p>\n\n<p>How do you write your PHP code?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1f560ca61cb72b1c394c162cff4811a1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json b/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json
index 179ea38ad..3af7694a2 100644
--- a/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json
+++ b/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/03\/21\/git-hooks---yay-or-nay\">In yesterday's email<\/a>, I mentioned that I use watch commands such as <code>nodemon<\/code>, <code>watchexec<\/code> and <code>entr<\/code> whilst developing to run commands automatically when I change code.<\/p>\n\n<p>For example, running <code>find web\/modules\/custom | entr .\/run test<\/code> will re-run my test suite when any custom module changes.<\/p>\n\n<p>This works well for tests, but for other checks, such as static analysis with PHPStan or coding standards with PHPCS, I have integrations in Neovim, and I get real-time feedback as I code.<\/p>\n\n<p>If a line fails static analysis or coding standards, a diagnostic message is shown so I can fix it immediately, and I don't need to use a watcher or wait for my CI pipeline to fail.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a7668c39a4177091d20aeb7c9d86cdd2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json b/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json
index 127bd045e..10b2add35 100644
--- a/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json
+++ b/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as the code changes, such as adopting Symfony components and other third-party code, one of my favourite things about Drupal since D8 is the new release cycle.<\/p>\n\n<p>Instead of \"It'll be ready when it's ready.\", since Drupal 8, Drupal releases new versions on fixed dates.<\/p>\n\n<p>If a feature is ready by that date, it will be included.<\/p>\n\n<p>If not, it will be included in a later&nbsp;version.<\/p>\n\n<p>As well as regular bug fixes and security updates, there is a new feature release every six months.<\/p>\n\n<p>Drupal 8.1 included features like the Layout Builder, which wasn't included in 8.0.<\/p>\n\n<p>In earlier Drupal versions, it would have been deferred to the next major version, making it longer before users get its benefits.<\/p>\n\n<p>A fixed release schedule makes it easier for users and Developers to plan their updates and prepare to upgrade to the major version.<\/p>\n\n<p>As Ryan said on a <a href=\"http:\/\/default\/podcast\/10-ryan-weaver-symfonycasts\">recent episode of Beyond Blocks<\/a>, \"It takes the drama out of open-source\".<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7b0e016e1d34348675c648d525c9e63f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json b/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json
index c6a233ad6..381b5a2e0 100644
--- a/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json
+++ b/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>\"Ship \/ Show \/ Ask\" describes itself as a self-described modern branching strategy that combines the features of pull or merge requests with the ability to keep shipping changes.<\/p>\n\n<p>Each change is either a \"Ship\", \"Show\", or \"Ask\".<\/p>\n\n<h2 id=\"ship\">Ship<\/h2>\n\n<p>\"Ship\" changes are what I most commonly do with continuous integration and trunk-based development projects. Changes are committed directly to the main branch and shipped - assuming that the CI pipeline and any other automated checks pass. There is no blocking code review or pull request for \"Ship\" changes.<\/p>\n\n<h2 id=\"show\">Show<\/h2>\n\n<p>\"Show\" changes are made on a temporary branch instead of the mainline. This branch is then used to create a pull request which is closed once the CI checks pass without any code review.<\/p>\n\n<p>Once the pull request is merged, the change is deployed, but the pull request is still available as somewhere to have feedback and conversation about the change.<\/p>\n\n<p>This is something that I did today after starting to write a new feature by implementing the Decorator design pattern, and wanted others to be aware of this approach and ask any questions.<\/p>\n\n<p>Another reason for this approach is if someone wants to ensure that the CI checks will pass before merging to mainline. Some Developers worry about breaking the CI pipeline with a trunk-based approach and blocking others, so want to know that the pipeline will continue to work and they aren't disrupting other team members.<\/p>\n\n<h2 id=\"ask\">Ask<\/h2>\n\n<p>This is how I've worked on most projects before, and still with some clients where they want to review changes before merging, or maybe I want to have a discussion and review a change beforehand.<\/p>\n\n<p>This is also common when new Developers join a project or need to change some code they haven't worked on before.<\/p>\n\n<h2 id=\"conclusion\">Conclusion<\/h2>\n\n<p>I like the flexibility and balance of this approach. I prefer to work on \"mostly ship\" projects, and most of the show and ask conversations happen during pair or mob programming sessions.<\/p>\n\n<p>Some of my clients where I work with teams are \"mostly ask\" and work in a more Git Flow-type way and want to review any changes before they're merged and deployed.<\/p>\n\n<p>But if you're working on a \"mostly ask\" project and want to move to \"mostly ship\", then aiming to move to \"mostly show\" is a good intermediate step and a way to reduce shipping time or develop and build confidence in the CI pipeline before moving to trunk-based development and removing the manual review step.<\/p>\n\n<p>The full article with more information is at https:\/\/martinfowler.com\/articles\/ship-show-ask.html.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3cbb18db43461716704cf4d74f02adff",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json b/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json
index de05dc0b1..ce749ca1a 100644
--- a/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json
+++ b/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json
@@ -87,14 +87,5 @@
             "processed": "\n          <h2 id=\"what-are-docblocks%3F\">What are docblocks?<\/h2>\n\n<p>Docblocks are comment blocks that describe a class or method and document its parameters and return types.<\/p>\n\n<p>Unfortunately, they're often overused and are outdated compared to the code they're describing, or repeat the same information again.<\/p>\n\n<p>For example, here's some PHP code:<\/p>\n\n<pre><code class=\"language-php\">function sayHello(string $name, array $options = ['shout' =&gt; false]): void {\n&nbsp;&nbsp;&nbsp;&nbsp; echo 'Hello, ' . $name;\n}\n\nsayHello('');\nsayHello('Oliver', ['shout2' =&gt; true]);\nsayHello('Oliver', ['shout' =&gt; 'banana']);\n<\/code><\/pre>\n\n<p>It's readable and understandable.<\/p>\n\n<p>It has types.<\/p>\n\n<p>We know that the name needs to be a string and that an array of options can be passed.<\/p>\n\n<p>This is how I like to write my code. In a clear and readable way with minimal comments.<\/p>\n\n<p>This code works, but there are issues with it.<\/p>\n\n<p>Do we want the name to potentially be an empty string?<\/p>\n\n<p>What if different options are passed in?<\/p>\n\n<h2 id=\"step-1\">Step 1<\/h2>\n\n<p>If you use PHPStan (a PHP static analysis tool), you won't get any errors until you test against level 6.<\/p>\n\n<p>Then you'll get this error:<\/p>\n\n<blockquote>\n  <p>Function sayHello() has parameter $options with no value type specified in iterable type array.<\/p>\n<\/blockquote>\n\n<p>Now, we can use a docblock to provide more information to PHPStan to describe the structure of the <code>$options<\/code> array and that it has strings for keys and boolean values.<\/p>\n\n<pre><code class=\"language-php\">\/**\n&nbsp;* @param array&lt;string, bool&gt; $options\n&nbsp;*\/\n<\/code><\/pre>\n\n<p>Although it's not erroring, we can add the <code>$name<\/code> parameter and declare it as a <code>string<\/code>.<\/p>\n\n<pre><code class=\"language-php\">\/**\n&nbsp;* @param string $name\n&nbsp;* @param array&lt;string, bool&gt; $options\n&nbsp;*\/\n<\/code><\/pre>\n\n<p>Now, the docblock adds some context and value but essentially repeats the defined types.<\/p>\n\n<h2 id=\"step-2\">Step 2<\/h2>\n\n<p>We can do more with the docblock and tell PHPStan more about what we want the values to be.<\/p>\n\n<p>We don't want an empty string for a name and want the correct options and values.<\/p>\n\n<p>Let's change the docblock to this:<\/p>\n\n<pre><code class=\"language-php\">\/**\n&nbsp;* @param non-empty-string $name\n&nbsp;* @param array{shout: bool} $options\n&nbsp;*\/\n<\/code><\/pre>\n\n<p>This specified the name cannot be an empty string and the shape of the options array.<\/p>\n\n<p>With this, we get these errors that weren't included before:<\/p>\n\n<ul>\n<li>Parameter #1 $name of function sayHello expects non-empty-string, '' given.<\/li>\n<li>Parameter #2 $options of function sayHello expects array{shout: bool}, array{shout2: true} given.<\/li>\n<li>Parameter #2 $options of function sayHello expects array{shout: bool}, array{shout: 'banana'} given.<\/li>\n<\/ul>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>While I like to write minimal, readable and \"self-documenting\" code and not overuse docblocks by adding them everywhere, I only add them and comments where needed and provide value, either to someone reading the code in the future or to tools like PHPStan that help me make the code better.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d4fd1c5b9efd845282526403295dacbd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json b/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json
index 51f4682a5..12e6f0910 100644
--- a/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json
+++ b/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently read a post where the writer said automated testing, test-driven development, continuous integration, trunk-based development, etc, are difficult.<\/p>\n\n<p>I'm familiar with them and have been using them for some time, but I think trunk-based development is easier as there's only a single branch instead of many.<\/p>\n\n<p>Continuous integration is&nbsp;pulling everyone else's code at least once daily and pushing yours to ensure it doesn't conflict.<\/p>\n\n<p>Test-driven development is writing failing tests before any implementation code and refactoring once it passes.<\/p>\n\n<p>I don't think these are technically difficult, but they do require an open mind, a willingness to learn, evaluate and consider alternative approaches and, in some cases, change existing behaviour.<\/p>\n\n<p>Change can be the difficult part, not which brand you commit to, how often you push your code or when you write your tests.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0a86c42026e6ba3f312a5db3e6383a25",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json b/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json
index 8c9aaa557..9ad245e1a 100644
--- a/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json
+++ b/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal 7, which was released in 2011, was originally supposed to be end-of-life in November 2022.<\/p>\n\n<p>This would mean there would be no more Drupal 7 versions and there would be no further support or bug fixes from the core Developer team.<\/p>\n\n<p>However, in February 2022, support was extended until November 2023 with a potential for it to be extended by another 12 months, which would be announced by July 2023.<\/p>\n\n<p>There are still over 425,000 active Drupal 7 websites according to <a href=\"https:\/\/www.drupal.org\/project\/usage\/drupal\">https:\/\/www.drupal.org\/project\/usage\/drupal<\/a> - almost 100,000 fewer than Feburary 2022. That's still a lot of websites!<\/p>\n\n<p>Should support be extended again or should Drupal 7 be marked as end-of-life and unsupported?<\/p>\n\n<p>If so, those websites will continue to work, and an argument could be made that there's been enough time to upgrade projects since Drupal 8's first release in 2015.<\/p>\n\n<p>That said, it's a tricky upgrade - migrating data into a new Drupal website and re-writing custom modules and themes to make them compatible.<\/p>\n\n<p>It's definitely work upgrading, in my opinion, as the updates between Drupal 8, 9 and 10 are much simpler and quicker, and don't involve large rewrites or data migrations.<\/p>\n\n<p>Hit reply and let me know what you think.<\/p>\n\n<p>P.S. Are you still using Drupal 7 and don\u2019t know what\u2019s involved to upgrade to Drupal 10? Book a <a href=\"http:\/\/default\/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "32e42c2ad69b53ec2591f07e14479344",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json b/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json
index eff247047..9b251bb10 100644
--- a/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json
+++ b/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>How many TODO comments do you have in your codebase?<\/p>\n\n<p>After posting <a href=\"http:\/\/default\/daily\/2025\/05\/07\/st\">the grep command from the st repository<\/a>, I decided to check a project I'm working on.<\/p>\n\n<p>Here's the command I ran:<\/p>\n\n<pre><code class=\"plain\">grep -rnE TODO web\/modules\/custom | wc -l\n<\/code><\/pre>\n\n<p>Different to the original, this command finds the number of TODO comments recursively in the custom modules directory and counts them using the <code>wc<\/code> command.<\/p>\n\n<p>This gave me a result of 29 TODOs.<\/p>\n\n<p>Some were added recently.<\/p>\n\n<p>Some were added by Developers who no longer work on the project.<\/p>\n\n<p>This is something I'll often do in the future to review the number of TODOs, fix them in-place or move them into a ticketing system.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "536d18a2fcc971be2e7320233cacb1fc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json b/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json
index 8b40a5a8b..7b9b10ee0 100644
--- a/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json
+++ b/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm aware of the ongoing changes to the issue queues on Drupal.org, I haven't contributed or committed as much recently, so I haven't had to use the new approaches, such as issue forks and GitLab merge requests.<\/p>\n\n<p>Yesterday, though, I was able to do that whilst submitting <a href=\"http:\/\/default\/daily\/2024\/03\/16\/adding-tests-to-the-content-access-by-path-module\">the tests I wrote to the Content Access by Path module<\/a>.<\/p>\n\n<p>I've made many contributions to projects on Drupal.org, including Drupal core and Drupal.org itself, so I'm very familiar with how the issue queues and the patch workflow work.<\/p>\n\n<p>When I first started contributing, we were using CVS, and before the \"Great Git Migration\".<\/p>\n\n<p>I'm also familiar with the pull or merge request approach from working on open-source and team projects on GitHub, GitLab and Bitbucket.<\/p>\n\n<p>I can see how a merge request-based workflow on Drupal.org will lower the barriers for new contributors, which seemed to be the case at DrupalCon Lille.<\/p>\n\n<p>I look forward to adapting and using it more now that the patch workflow is deprecated and will soon no longer work as everything will switch to merge requests and leverage more of GitLab's features.<\/p>\n\n<p>Another step forward for Drupal.org and the Drupal project.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "146ae12ea9007bdc9e974f9967897038",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json b/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json
index 608e95912..65df3f64c 100644
--- a/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json
+++ b/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I've been working on a particular component that processes and displays live data from APIs.<\/p>\n\n<p>As the data is live, it's constantly changing and it's unlikely I'll see all the different states and use-cases that the data could be in.<\/p>\n\n<p>There's also no guarantee the API will be available and I also may need to work offline with no Internet access to connect to the API.<\/p>\n\n<p>I'm reminded of the quote by Kent Beck:<\/p>\n\n<blockquote>\n  <p>For each desired change, make the change easy (warning: this may be hard), then make the easy change.<\/p>\n<\/blockquote>\n\n<p>In this case, to make the change easy, I need the data to be consistent, to see all the use-cases and permutations and to be available offline.<\/p>\n\n<p>To make the change easy, I created a fake version of the service class that returns static data I can work with.<\/p>\n\n<p>I can add whatever data I need to give me the examples and situations to work with and by implementing the same methods as the real service class, I can swap them without changing any other code.<\/p>\n\n<p>Now I can make the easy change.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "4284e8bf5254c92b4ec97575e0b82116",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json b/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json
index 254634224..8037ac009 100644
--- a/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json
+++ b/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've been <a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">speaking about and advocating for Tailwind CSS<\/a> and utility-first CSS for a long time.<\/p>\n\n<p>In my slide deck, I show screenshots of websites that are all built with Tailwind CSS - including some <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">rebuilds of existing websites<\/a>.<\/p>\n\n<p>I do this to show that the same approach and framework can be used to create different-looking designs because the classes are atomic and can be reused and combined as needed.<\/p>\n\n<p>This isn't the case with other CSS frameworks that focus on components first.<\/p>\n\n<p>As an experiment, some time ago I decided to <a href=\"https:\/\/bootstrap-with-tailwind.oliverdavies.uk\">rebuild some of the Bootstrap example components using Tailwind CSS<\/a>.<\/p>\n\n<p>I've only done a pricing grid and album, but I may do more in the future.<\/p>\n\n<p>I originally built the examples with Astro but have ported them to Sculpin, which I'm more familiar with.<\/p>\n\n<p>If you want to see how I've built these components or how for an example of building a static website with Sculpin, <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/bootstrap-with-tailwind\">check out the source code<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e38c49ae0796baf36f3a37341052d155",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json b/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json
index 14fecd1b5..dd5fe947b 100644
--- a/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json
+++ b/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A recent discussion has started about which testing framework should be the default one used in Laravel.<\/p>\n\n<p>PHPUnit or Pest.<\/p>\n\n<p>I've used both, and I like both.<\/p>\n\n<p>I'm more familiar with classes, object-orientated code and PHPUnit, but for people who are more familiar with JavaScript and the Jest testing framework, Pest may be the better option.<\/p>\n\n<p>Its expectation API, where you can chain multiple assertions on the same expectation, is helpful, although I don't mind some repetition in PHPUnit tests.<\/p>\n\n<p>Pest tests can become abstract, especially with some of their one-line example tests.<\/p>\n\n<p>Whether you pick PHPUnit, Pest or another framework like Behat or Codeception, the main thing is you're taking the time to write automated tests for your code, which is valuable whichever testing tool you use.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1ed822840535da7f16ffd29dace80ede",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json b/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json
index dd9b104bb..c83b6be10 100644
--- a/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json
+++ b/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I prefer writing and working with strictly typed code.<\/p>\n\n<p>One of the major improvements in PHP has been the option to enable strict types.<\/p>\n\n<p>For example, this code will usually not error and give the result:<\/p>\n\n<pre><code class=\"php\">function add(int $a, int $b): void\n{\n    var_dump($a + $b);\n}\n\nadd(1, '1');\n<\/code><\/pre>\n\n<p>However, I'd prefer if it failed as I'm passing the function an integer and a string, but specifying they should both be integers.<\/p>\n\n<p>Fixing this is simple, by adding this line to the top of the file:<\/p>\n\n<pre><code class=\"php\">declare(strict_types=1);\n<\/code><\/pre>\n\n<p>I add this to every PHP file by default.<\/p>\n\n<p>I want my code to be as strict and predictable as possible, and to error when I want it to and make any bugs more explicit and easier to find and fix.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "07d6a599d591e31580f215b484e9ae34",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json b/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json
index e8258cc59..5bf46d163 100644
--- a/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json
+++ b/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As announced in the Drupal 7 end-of-life announcement, changes have been made to the Drupal 7 security support policies - effective the 1st of August.<\/p>\n\n<p>In summary:<\/p>\n\n<ul>\n<li>The Drupal Security Team may post moderately critical and less critical issues affecting Drupal 7 in the public issue queue, as long as they are not mass-exploitable.<\/li>\n<li>Drupal 7 branches of unsupported modules and themes are no longer eligible for new maintainership.<\/li>\n<li>PHP 5.5 and below will no longer be supported on Drupal 7 (PHP 5.5 was end-of-life in July 2016).<\/li>\n<li>Security fixes will no longer be provided for Drupal 7 Windows-only issues.<\/li>\n<\/ul>\n\n<p><a href=\"https:\/\/www.drupal.org\/psa-2023-06-07\">There is more information in the announcement<\/a>, but if you're still on Drupal 7, now is the time to upgrade before its end-of-life date in five months.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "37b746e93ec56556229b8c0a758a28cf",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json b/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json
index 5491dd065..b50f1ee74 100644
--- a/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json
+++ b/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Another great thing about open source software is anyone can use it, contribute to it or provide services for it.<\/p>\n\n<p>You don't need to be a large company like Acquia or Red Hat.<\/p>\n\n<p>I was a self-taught solo hobbyist Developer when I started building a website for my local Tae Kwon-Do club in 2007 with PHP.<\/p>\n\n<p>In 2008, I started learning Drupal, built my own website and started doing freelance Drupal development and consulting work.<\/p>\n\n<p>I became a full-time Drupal Developer in 2010 and haven't looked back since.<\/p>\n\n<p>I was able to this for free using open source software.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3523efa30025b9ea53133ab91ddb3086",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json b/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json
index 4f69725c9..d1643b250 100644
--- a/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json
+++ b/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today is the day!<\/p>\n\n<p>Fourteen years after its original release, Drupal 7 is now end-of-life and will not receive any more security or compatibility updates.<\/p>\n\n<p>I remember building my first Drupal 7 website while working as a Junior Developer at an agency and have built a lot of Drupal 7 websites since 2011.<\/p>\n\n<p>I maintained the Override Node Options module and contributed to other projects, including Drupal Commerce, Commerce Kickstart and Drupal 7 core.<\/p>\n\n<p>I cut my teeth with automated testing and test-driven development in Drupal 7 with SimpleTest.<\/p>\n\n<p>It's been a big part of my career.<\/p>\n\n<p>But I'm looking forward to seeing Drupal continue to evolve and what's to come in Drupal CMS later this month.<\/p>\n\n<p>So long, Drupal 7.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "427e5da306c0b08b7e6ba695b5a3017b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json b/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json
index 70d9b9c14..7db670176 100644
--- a/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json
+++ b/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal is typically called a CMS (content management system) - somewhere you add and edit the content for your website.<\/p>\n\n<p>However, unlike some other CMSes, unless a Drupal website uses only the default page and article content type, no Drupal websites are the same. Each will have its specific content model with different content types and fields.<\/p>\n\n<p>Instead of being a content management system, Drupal can be described as a content management framework (CMF) - a framework for building a content management system specific to each application.<\/p>\n\n<p>But as well as a content management framework, Drupal could also be considered an application framework like Symfony or Laravel.<\/p>\n\n<p>As well as building the content model, you can extend Drupal's functionality with custom modules and add custom themes to make it visually different.<\/p>\n\n<p>But, there's a lot of functionality in Drupal core itself - such as user accounts, authentication, a query builder (Views), JSON:API endpoints, and a visual page editor (Layout Builder) - to name a few things!<\/p>\n\n<p>Drupal offers much more than just managing content.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "868ebc7b4844fbd04025c16a9cfb16e9",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json b/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json
index 5bb3d4dda..348c37c44 100644
--- a/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json
+++ b/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Is having automated tests a prerequisite for refactoring a piece of code?<\/p>\n\n<p>Without passing tests for that code, any changes made could introduce a regression, and bugs can be accidentally introduced.<\/p>\n\n<p>When refactoring with tests, you run them before making any changes to ensure they pass. The tests are rerun after every change to ensure that they still pass and that the change didn't introduce a regression that caused the test to fail. If a test fails, the change is reverted and re-attempted.<\/p>\n\n<p>If I need to refactor some code without tests, the first thing that I'll do is add some initial tests before the main work.<\/p>\n\n<p>Whilst nothing is stopping me from refactoring without the tests, the risk isn't something that I'd want to take on, and I'd much prefer to have some tests in place - just in case!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6f362b9d79b81b8f344cb774a1638e59",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json b/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json
index 5736e7760..d406cc09a 100644
--- a/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json
+++ b/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday, <a href=\"http:\/\/default\/daily\/2024\/11\/26\/the-nix-language\">I showed some of the Nix programming language<\/a> and how to use it to perform tasks such as installing and configuring packages.<\/p>\n\n<p>I like this declarative approach as you know everything installed on your system and its configuration.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2024\/11\/23\/no-more-random-packages\">There are no random or leftover packages or configuration files<\/a>.<\/p>\n\n<p>The Nix package manager can be installed on Linux or macOS, but you can also use Nix to configure your whole operating system in a declarative way thanks to NixOS.<\/p>\n\n<p>As well as installing and configuring packages, you can define your firmware version, boot loader, disk partitioning, user accounts and more.<\/p>\n\n<p>I used to do this type of automation with Ansible but switched to NixOS soon after trying Nix on another Linux distribution.<\/p>\n\n<p>If I need to work on a different laptop, like when mine recently died, I can apply the same configuration and get all the same programs and configurations as before.<\/p>\n\n<p>If you want to see my current NixOS setup, you can <a href=\"https:\/\/github.com\/opdavies\/dotfiles\">see it on my GitHub<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1c553d5a90092cb35e635bb87120d74a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json b/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json
index 6019e9d4e..13b0de5ae 100644
--- a/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json
+++ b/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Having a passing test suite doesn't mean everything in your application is working.<\/p>\n\n<p>It means the functionality you previously tested is working.<\/p>\n\n<p>There may be edge cases you haven't covered or whole tests you haven't written yet, which may be working or could be broken.<\/p>\n\n<p>If you have tests that were passing that are now failing, you know you've broken something.<\/p>\n\n<p>Something that was previously working is broken and shouldn't be deployed.<\/p>\n\n<p>That's why having tests is important - they give you the ability to identify and fix regressions before they are released.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ee9c7fdfadc92a583c9a83309b14f644",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json b/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json
index cee30006c..b52658b8c 100644
--- a/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json
+++ b/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Instead of writing a whole test and then attempting to make it pass, only write enough code to get the test to fail.<\/p>\n\n<p>This could be by starting with a failing assertion that is fixed with a hard-coded value and then iterating on the test to introduce the next failure before repeating the process.<\/p>\n\n<p>This allows you to keep the feedback loop small and not write more code than is needed, to focus on the objective of the test, and not code yourself into a corner.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8b2ab9118da9393b9e5398111f66ff1f",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json b/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json
index bde2706ab..666efd647 100644
--- a/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json
+++ b/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whether you're writing tests before the implementation code or not, the first test is always the hardest to write.<\/p>\n\n<p>What will the arrange and act phases look like?<\/p>\n\n<p>What dependencies will you need?<\/p>\n\n<p>What do you need to mock or create fakes of?<\/p>\n\n<p>In a Drupal test, what other modules and configuration do you need to install?<\/p>\n\n<p>What installation profile and default theme do you need to use?<\/p>\n\n<p>What other unknown or complicated setup steps are there?<\/p>\n\n<p>Do you need to configure your environment to run the tests and get the expected output?<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The hardest part is getting the arrange\/setup phase working and getting to when the test is running your business logic.<\/p>\n\n<p>Once you've got the first test running, adding more for similar use cases will be much easier.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9932561d0945f63746a1bb5ddd951b0a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json b/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json
index a5ed61e4d..94fe0b2e4 100644
--- a/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json
+++ b/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few years ago, \"decoupled\" or \"headless\" Drupal was a popular approach, leveraging Drupal's built-in JSON:API module to expose its data via an API which can be consumed by a separate front-end application.<\/p>\n\n<p>The front-end application would retrieve the data from Drupal via the API and generate the appropriate HTML.<\/p>\n\n<p>It's an approach I've used in the past and <a href=\"http:\/\/default\/presentations\/decoupling-drupal-vuejs\">spoken about at conferences<\/a>, but it comes with pros and cons.<\/p>\n\n<p>In theory, as the Drupal (or back-end application) and front-end are completely separate, there can be two separate and independent teams working on them.<\/p>\n\n<p>This adds overhead and complexity and I've found that one team will commonly be blocking the other instead of both being able to work in parallel.<\/p>\n\n<p>As I said yesterday, <a href=\"http:\/\/default\/daily\/2025\/01\/26\/layout-builder\">previewing content in Drupal can be an issue<\/a> - particularly with a decoupled approach which needs a front-end to be rebuilt before the changes can be seen.<\/p>\n\n<p>If you have a separate front-end, you'll need to create everything from scratch, such as writing accessible HTML markup and othe standard features that would normally be provided by Drupal and, because you've got two separate front-end and back-end applications, you've got twice the amount of maintenance.<\/p>\n\n<p>You could also be excluding yourself from any new features that will be available in future versions of Drupal or Drupal CMS, such as the new Experience Builder.<\/p>\n\n<p>Whilst decoupled\/headless builds are a viable option and can work well in some situations, it's not something I recommend often.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "780bda0044c53e6e45fb49f2037ac82e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json b/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json
index 66a63c663..069615b5e 100644
--- a/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json
+++ b/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When fixing a bug or adding a new feature using test-driven development, it's important to see the test fail first.<\/p>\n\n<p>You should write your test so it doesn't pass by default or accidentally.<\/p>\n\n<p>When creating data, such as users or nodes within tests, do so in a way that will force the test to fail, such as explicitly setting the title or published date into a non-default order.<\/p>\n\n<p>When fixing a bug, write a test that represents the expected outcome when the bug is fixed. This confirms the bug exists and can be replicated.<\/p>\n\n<p>Then, once the tests pass, you know the feature or fix is working and that it's because of your changes and not for any other reason.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c165a71ff34130f10b8bbd674b2708a6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json b/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json
index f888e414e..952a34552 100644
--- a/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json
+++ b/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/08\/31\/make-it-work-then-make-it-good\">Once you have working code<\/a>, you can refactor it to make it better.<\/p>\n\n<p>You can rename variables, extract new functions or classes, ensure the code is styled and formatted correctly - anything to make the code easier to read, understand or maintain.<\/p>\n\n<p>But, the key thing is the code still needs to work.<\/p>\n\n<p>You don't want to break working code and introduce a regression, even if it is messy or difficult to read.<\/p>\n\n<p>The best way I know to approach this is by having automated tests covering this code, and ensure they are working and passing before starting to refactor.<\/p>\n\n<p>Then you can run the tests again and ensure they still pass.<\/p>\n\n<p>If they pass, the code still works and the refactoring was successful.<\/p>\n\n<p>If not, the code is broken and you need to revert the changes and start again.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c4f9c5744c27b541d231076231201427",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json b/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json
index 8eeec6e88..31a8e4aa7 100644
--- a/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json
+++ b/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>You deploy a code change but it creates an issue.<\/p>\n\n<p>Maybe it breaks a feature, adds a bug or takes down an environment completely.<\/p>\n\n<p>How do you resolve it?<\/p>\n\n<p>Larger releases will sometimes have a roll back plan that details how to revert to the previous release.<\/p>\n\n<p>This can be difficult, especially for large releases and ones that change the database schema or values.<\/p>\n\n<p>Because of the amount of change, diagnosing an issue in a large release can take time.<\/p>\n\n<p>If it's been a while since the prior release, it can be some time since the code that introduced the issue was worked on - making it harder to fix.<\/p>\n\n<p>I prefer to do small releases and do them often.<\/p>\n\n<p>Some releases contain a single commit which was made only minutes since the previous release.<\/p>\n\n<p>This makes it easier to identify the issue, fix it and deploy a new version.<\/p>\n\n<p>No rolling back database changes or reverting to previous releases.<\/p>\n\n<p>Small, iterative deployments are less risky than large infrequent ones, easier to fix and make changes available to end users sooner.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bd41bad48401d8b39626d1b4c1fa46a3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json b/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json
index 7bbd18e36..fe3437c7b 100644
--- a/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json
+++ b/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/05\/17\/why-i-dont-commit-with--m\">I write and advocate for others to write<\/a> detailed Git commit messages within the subject body to provide context and information about why the commit was needed, what other options were considered, any consequences or knock-on effects there could be, or even code snippets or pseudo code.<\/p>\n\n<p>Recently, I was curious to know which commit in a repository has the longest commit message, what code has changed in that commit, and who wrote it.<\/p>\n\n<p>I was hoping for a command like <code>git shortlog --summary --all<\/code> (which shows all authors to a codebase and their number of commits), but couldn't find one, so <a href=\"https:\/\/github.com\/opdavies\/git-commit-length-counter\">I wrote a script to do it<\/a>.<\/p>\n\n<p>It's a bash script that loops over the commits in the repo, calculates the length of each message, sorts them and shows the commit with longest message.<\/p>\n\n<p>It was an interesting task and shows examples of using various UNIX commands and Linux coreutils, such as <code>find<\/code>, <code>cut<\/code>, <code>sort<\/code> and <code>wc<\/code> in combination with Git.<\/p>\n\n<p>The longest in this website's code base is <a href=\"https:\/\/github.com\/opdavies\/oliverdavies.uk-drupal\/commit\/cbd1417b24a608df8b451a3ab5c9f888de41e758\">546 characters<\/a>, which is fairly small compared to some of my messages in other projects.<\/p>\n\n<p>What's the longest commit message in the repository you're working in?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "508bce081c6ebd69e4dc32058f9c788e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json b/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json
index 0151b8924..d125848a6 100644
--- a/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json
+++ b/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>What is the leanest and most minimal local environment for software development?<\/p>\n\n<p>I think if you use Linux, the most minimal approach is to install the packages you need, such as PHP and MySQL directly in your operating system.<\/p>\n\n<p>There's no overhead or complexity added by tools like containers so things will run as quick and efficiently as possible.<\/p>\n\n<p>This is great if you only work on one project and you can easily keep your installation in sync with production.<\/p>\n\n<p>But what if you work on multiple projects or with a team of Developers?<\/p>\n\n<p>You need a way for everyone to have the same software and package versions, and to be able to configure them for each project.<\/p>\n\n<p>These are the reasons why tools like Vagrant, Docker and Podman became popular, as they made it possible for environments to be easily repeatable and customisable.<\/p>\n\n<h2 id=\"what-about-nix%3F\">What about Nix?<\/h2>\n\n<p>Another tool that can be used to install software is Nix - a package manager with over 100,000 software packages.<\/p>\n\n<p>I can use it to install the required software for each project and share the files with any team members so they have the same configuration.<\/p>\n\n<p>This is the <code>flake.nix<\/code> file that I've been testing with a Drupal codebase:<\/p>\n\n<pre><code class=\"nix\">{\n  inputs.nixpkgs.url = \"github:nixos\/nixpkgs\/nixos-unstable\";\n\n  outputs =\n    { nixpkgs, ... }:\n    let\n      system = \"x86_64-linux\";\n      pkgs = nixpkgs.legacyPackages.${system};\n    in\n    {\n      devShells.${system}.default = pkgs.mkShell {\n        buildInputs = with pkgs; [\n          mariadb\n          php82\n          php82Packages.composer\n        ];\n      };\n    };\n}\n<\/code><\/pre>\n\n<p>This installs PHP 8.2, Composer and MariaDB, and nothing else.<\/p>\n\n<p>It also generates a <code>flake.lock<\/code> file so everyone gets exactly the same package versions.<\/p>\n\n<p>The downside is that, if everyone isn't using NixOS which handles services, I need to configure the database server for each project, running commands like <code>mysql_install_db<\/code> and <code>mysqld<\/code> before creating the database and user to put in the <code>settings.php<\/code> file.<\/p>\n\n<p>It's not complicated but <a href=\"http:\/\/default\/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">devenv is a great option<\/a> if you want something more fully featured and opinionated that does more out of the box.<\/p>\n\n<p>Once the database server is running and Drupal is installed, I can run <code>drush runserver<\/code> to run the website - no need for Apache, Caddy or Nginx.<\/p>\n\n<p>If you want to see another example, see the <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk\/src\/commit\/4350852406e9556b63a1df448f225abbd7883651\/flake.nix\">flake.nix file for this website<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "80b28c3ecc0b1a024878f575f11385d3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json b/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json
index ff1ae00d5..eefd8821f 100644
--- a/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json
+++ b/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I watched a video recording of a session by Ond\u0159ej Mirtes - the creator of PHPStan - on writing custom rules for PHPStan.<\/p>\n\n<p>After explaining how to write them, he showed some examples of custom rules - one of which was ensuring a <code>Person<\/code> class couldn't be created outside of a <code>PersonRepository<\/code> class.<\/p>\n\n<p>This seemed straightforward&nbsp;so I thought about how I could do something similar within my <a href=\"http:\/\/default\/atdc\">Drupal automated testing email course<\/a> to check my Drupal code.<\/p>\n\n<p>Similar to Ond\u0159ej's example, I wondered if I could enforce that no post nodes should be created outside of the <code>PostBuilder<\/code> class by searching&nbsp;for any code like <code>Node::create(['type' =&gt; 'post'])<\/code>.<\/p>\n\n<p>I was able to get a version working quickly and have <a href=\"https:\/\/gist.github.com\/opdavies\/a2f9d92cf3b67db6a64b9fca4e4e6697\">posted it as a gist<\/a>.<\/p>\n\n<p>I'm sure some improvements can be made, but it was a successful experiment and something I can see me using more in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7fd7688e20aec257116644fad8d96aac",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json b/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json
index 4275f7a58..4a93ceddd 100644
--- a/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json
+++ b/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few months ago, <a href=\"http:\/\/default\/podcast\/6-dan-leech-php-tui\">Beyond Blocks podcast guest Dan Leech<\/a> give another talk at the PHP South West user group.<\/p>\n\n<p>This talk was about <a href=\"https:\/\/www.youtube.com\/watch?v=UpyVAcWGQhg\">building an expression language from scratch<\/a>, but in one part of the talk, Dan showed how he creates Collection classes.<\/p>\n\n<p>I use Collection classes a lot, have <a href=\"http:\/\/default\/presentations\/using-illuminate-collections-outside-laravel\">given talks about them<\/a> and <a href=\"https:\/\/www.drupal.org\/project\/collection_class\">wrote a Collections module for Drupal 7<\/a>.<\/p>\n\n<p>In Dan's talk, instead of using a Collection from Laravel or Doctrine, <a href=\"https:\/\/github.com\/dantleech\/onehourexpr\/blob\/8c4ee4a3c1680455118e16a3e1be2a08418ab207\/src\/Tokens.php\">he created his own<\/a>.<\/p>\n\n<p>His extended PHP's <code>IteratorAggregate<\/code> class so had no external dependencies.<\/p>\n\n<p>He could then add whatever additional methods and functionality he needed.<\/p>\n\n<p>Looking at other repositories on GitHub, I was able to find other examples.<\/p>\n\n<p>I've done this on projects since Dan's talk and like taking the minimalist approach - avoiding adding a dependency to my project and only adding the functionality I need and functionality that's more specific to my domain.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "94b06833489046a4c26442548eee3ca2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json b/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json
index cd3c7384c..eef68624e 100644
--- a/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json
+++ b/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Something I commonly used to see, and did myself, was running code formatting tools, such as PHP CS Fixer or prettier, automatically their CI pipeline.<\/p>\n\n<p>And not using it as a check to fail the pipeline if your code isn't formatted correctly.<\/p>\n\n<p>Running it, fixing any code and committing any updates.<\/p>\n\n<p>It wasn't long before I stopped doing this.<\/p>\n\n<p>Firstly, I wasn't comfortable with a CI pipeline have write access to my codebase. It's fine to be able to clone it and run checks against it, but making changes to my code and pushing it makes me nervous.<\/p>\n\n<p>Particularly if you're doing trunk-based development and everyone works on the same branch.<\/p>\n\n<p>This also causes additional upstream commits, because the pipeline has committed a change. If you don't remember to pull those commits, you can <a href=\"http:\/\/default\/daily\/2024\/07\/25\/only-have-one-url-per-git-remote\">end up in a tricky situation<\/a>.<\/p>\n\n<p>I'm also not a fan of having a lot of <code>php-cs-fixer fixes<\/code> or <code>prettier fixes<\/code> commits. I'd prefer the commits be correct when they're pushed, if possible, which is why I usually do micro commits locally and tidy things before pushing them.<\/p>\n\n<p>If you're working on a topic branch and creating a pull or merge request, you can squash commits when merging, but <a href=\"http:\/\/default\/daily\/2024\/05\/11\/don-t-delete-my-commit-messages\">I'm not a fan of squashing commits<\/a>, either.<\/p>\n\n<p>Instead of relying on a CI pipeline to run code formatting, <a href=\"http:\/\/default\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">make it easy to run those tasks locally<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d54ad8e941f721ec3bbb3abacd9ca123",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ec6af399-d960-4715-92c5-760fce33d803.json b/content/node.ec6af399-d960-4715-92c5-760fce33d803.json
index 4b5205d21..41c130aa7 100644
--- a/content/node.ec6af399-d960-4715-92c5-760fce33d803.json
+++ b/content/node.ec6af399-d960-4715-92c5-760fce33d803.json
@@ -87,14 +87,5 @@
             "processed": "\n          <h2 id=\"architectural-decision-records\">Architectural Decision Records<\/h2>\n\n<p>Architectural Decision Records (ADRs) are documents to record software design choices. They could be saved in your code repository as plain-text or Markdown files, or stored in Confluence or a wiki - wherever your team stores its documentation.<\/p>\n\n<p>They usually consist of the sections:<\/p>\n\n<ul>\n<li>Status - is it proposed, accepted, rejected, deprecated, superseded, etc.?<\/li>\n<li>Context - what is the issue that is causing the decision or change?<\/li>\n<li>Decision - what is the change that's being done or proposed?<\/li>\n<li>Consequences - what becomes easier or more difficult to do?<\/li>\n<\/ul>\n\n<p>Any change that is architecturally significant should require an ADR to be written, after which it can be reviewed and potentially actioned.<\/p>\n\n<p>These will remain in place to form a decision log, with specific ADRs being marked as superseded if a newer ADR replaces it.<\/p>\n\n<h2 id=\"technical-design-documents\">Technical Design Documents<\/h2>\n\n<p>A similar type of document are Technical Design Documents (TDDs), that I first saw on TheAltF4Stream. I like to think of these as lightweight ADRs.<\/p>\n\n<p>The first heading is always \"What problem are we trying to solve?\", or sometimes just \"The problem\".<\/p>\n\n<p>Similar to the Context heading in an ADR, this should include a short paragraph describing the issue.<\/p>\n\n<p>Unlike ADRs, there are no other set headings but these are some suggested ones:<\/p>\n\n<ul>\n<li>What is the current process?<\/li>\n<li>What are any requirements?<\/li>\n<li>How do we solve this problem?<\/li>\n<li>Alternative approaches<\/li>\n<\/ul>\n\n<p>I like after describing the problem, being able to move straight into describing what's appropriate and relevant for this task and ignore sections that aren't needed.<\/p>\n\n<p>When I started writing ADRs, they all had the 'Accepted' status as I was either writing them for myself or in a pair or mob. As wasn't adding any value, I've removed it since switching to writing TDDs.<\/p>\n\n<p>Whether you use ADRs, TDDs or another approach, it's very useful to have a log of all of your architectural design decisions, both looking back in the future to remember why something was done in a certain way, or before you start implementing a solution to review the problem, evaluate the requirements and all potential solutions and document the selected one any why it was selected.<\/p>\n\n<p><a href=\"https:\/\/adr.github.io\">Find our more about ADRs<\/a> or <a href=\"https:\/\/altf4.wiki\/t\/how-do-i-write-a-tdd\/21\">find out more about TDDs<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ce0fd785eeded51305f4d32749a7ce65",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json b/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json
index f212d25a4..53991cfcf 100644
--- a/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json
+++ b/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I\u2019m happy to have had a conference talk proposal accepted for what will be my first in-person conference since DrupalCamp London in February 2020.<\/p>\n\n<p>I\u2019ll be giving my \"<a href=\"http:\/\/default\/presentations\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS<\/a>\" talk for the first time since February 2021, and in front of an in-person audience since June 2019.<\/p>\n\n<p>The talk itself will need some updating. The last time I gave it, Tailwind CSS was on version 2.0.3. It\u2019s now on version 3.2.2 and includes features like the just-in-time engine, arbitrary values and variants, container queries, and a load of new utility classes.<\/p>\n\n<p>I gave a lot of talks at online events in 2020, so after taking a bit of a break last year, it will be nice to speak in front of an in-person conference audience again.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d5154e6cb6c11f4bc95c35ff8fc596bd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json b/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json
index ff620e136..cbeb38751 100644
--- a/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json
+++ b/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tomorrow is the first day of cohort 17 of School of Code - a free 16-week software development bootcamp - and I'm happy to be mentoring a student again for my third time.<\/p>\n\n<p>I also mentored the winning team at a hack day event in January and <a href=\"http:\/\/default\/presentations\/communities-contribution\">spoke at the TechConnect meetup<\/a> last year.<\/p>\n\n<p>Last week, I spoke with George Gordon - a recent School of Code graduate who I met at the hack day and later at another meetup I was speaking at.<\/p>\n\n<p>We discussed his experience with coding bootcamps, getting into the software industry and involved with community events and how he found his first Developer job!<\/p>\n\n<p>It will be released soon on <a href=\"http:\/\/default\/podcast\">the Beyond Blocks podcast page<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0133e2d8424efefed5ed2aa8915ee1c6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json b/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json
index f582388ba..8511fe3ff 100644
--- a/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json
+++ b/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>While dependency injection is a good practice - i.e., passing dependencies into a class, usually via a constructor method - you want to be aware of how many dependencies you inject into each class.<\/p>\n\n<p>There's no hard and fast rule, but I usually notice when I get to three dependencies and rarely inject more than four or five into a class.<\/p>\n\n<p>Having too many dependencies suggests that the class is doing too much and has too many responsibilities and that another class may be needed.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Having smaller and simpler classes makes them easier to read, maintain and review. Ideally, each class should only have one responsibility, so it adheres to the Single Responsibility Principle (the \"S\" in SOLID).<\/p>\n\n<p>Creating classes is cheap, so why not split one large and difficult-to-maintain class with many dependencies into multiple smaller and easier-to-work-with ones?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b40abd231dda53a740949b3e5d5ac434",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json b/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json
index 6dc5649f1..738821683 100644
--- a/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json
+++ b/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Following yesterday's email about input validation, guard clauses and assertion libraries, these can be used to compliment PHP's native types and checking.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"language-php\">function createJourney(string $from, string $to, int $duration): void {\n  var_dump($from, $to, $duration);\n}\n<\/code><\/pre>\n\n<p>In this code, each parameter has a type, but there's no validation on the values.<\/p>\n\n<p>If I run this:<\/p>\n\n<pre><code class=\"language-plain\">createJourney('', '', -10);\n<\/code><\/pre>\n\n<p>I would get this output:<\/p>\n\n<pre><code class=\"language-plain\">string(0) \"\"\nstring(0) \"\"\nint(-10)\n<\/code><\/pre>\n\n<p>This is probably not what you want.<\/p>\n\n<p>I expect <code>$to<\/code> and <code>$from<\/code> to be not empty and the duration to be greater than zero.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I can use an assertion library or throw my own Exceptions if the values pass the type checks but aren't what I need.<\/p>\n\n<p>For example:<\/p>\n\n<pre><code class=\"language-php\">function createJourney(string $from, string $to, int $duration): void {\n  Assert::stringNotEmpty($from);\n  Assert::stringNotEmpty($to);\n  Assert::positiveInteger($duration);\n\n  var_dump($from, $to, $duration);\n}\n<\/code><\/pre>\n\n<p>Now, if an empty string or negative duration is passed - in my implementation or test code - an Exception will be thrown.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7a9179502a50a3f6f3443cdebef1a615",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json b/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json
index 2aedc919a..332da1891 100644
--- a/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json
+++ b/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, I was at the Norfolk Developer's Conference, aka <code>nor(DEV):con<\/code> - my first in-person conference since DrupalCamp London in February 2020.<\/p>\n\n<p>I've been excited about this conference since I received the acceptance email in November, inviting me to give my <a href=\"http:\/\/default\/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS<\/a> talk.<\/p>\n\n<p>The talk itself went well and included some changes following the Bristol Software Development meetup last month. The last time I gave this talk prior to that was remotely for Nashville PHP in February 2021 and a lot of new things have been added to Tailwind CSS since then for me to include.<\/p>\n\n<p>My next talk will be at the PHP London meetup next month (subject TBC) as I continue working towards my hundredth presentation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e15720a4ab8c5005c73431fcac145c86",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json b/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json
index 3b5607c6f..b50dbace9 100644
--- a/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json
+++ b/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you've experienced issues or are worried about deploying changes to production, <a href=\"http:\/\/default\/daily\/2024\/09\/11\/do-you-deploy-on-fridays\">on a Friday or another day<\/a>, when did you last deploy something?<\/p>\n\n<p>Can you make deployments smaller and more frequent?<\/p>\n\n<p>Deploying regularly makes each deployment less risky and having a smaller changeset makes it easier to find and fix any issues that arise.<\/p>\n\n<p>I'm much happier deploying to production if I've already done so that day, or at least that week.<\/p>\n\n<p>Any time more than that, or if the changeset is large, the more likely there will be issues and the longer it will take to resolve them.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e4e7b3f159846b99658730ca08899088",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json b/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json
index 192eef472..021131149 100644
--- a/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json
+++ b/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Drupal comes with a lot of features available out of the box.<\/p>\n\n<p>It has a flexible system to create complex content models with different content types and fields, rich media management and Views - a visual query builder - to create lists of content.<\/p>\n\n<p>It has the JSON:API module to expose your content via an API for use by other systems, such as mobile apps.<\/p>\n\n<p>It has user management, authentication, password resets, roles and permissions.<\/p>\n\n<p>It has configuration management to easily manage settings and configuration between environments and to provide traceability.<\/p>\n\n<p>It has the Layout Builder to create page layouts with a drag and drop interface and a built-in WYSIWYG editor for entering rich content.<\/p>\n\n<p>These are just some of the features I could mention.<\/p>\n\n<p>Running cloc on Drupal's <code>core<\/code> directory shows 18,289 files and 1,095,970 lines of code.<\/p>\n\n<p>If you were to get someone to build a CMS from scratch with the same features, how long would that take?<\/p>\n\n<p>How much would it cost?<\/p>\n\n<p>This is what you get for free by using free and open source software like Drupal.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3b2f48d28cdda255b884d631a4a170ad",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json b/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json
index ed3260aa0..371b7996a 100644
--- a/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json
+++ b/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As I said yesterday, there is no perfect solution or approach for every situation.<\/p>\n\n<p>However, when doing test-driven development, there is a best solution.<\/p>\n\n<p>The simplest thing that gets a failing test to pass.<\/p>\n\n<p>Whether it's hard-coding a return value or putting the initial logic in a Controller, that's the objective.<\/p>\n\n<p>Once the test is passing, you can refactor the code or continue writing tests, which will each have their own best solution.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f999f40729d1c4017022ac0e4fd81a1d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json b/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json
index 74113145b..271850a1e 100644
--- a/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json
+++ b/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As well as taking longer to fix than locally or in a failed CI pipeline, shipping buggy software to production causes reputational damage.<\/p>\n\n<p>If an application goes down or doesn't run as expected, it could get noticed by your customers, clients, or your clients' customers.<\/p>\n\n<p>You want your customers and clients to be assured you're writing the correct software based on their needs and requirements, and doing so with as few bugs and issues as possible.<\/p>\n\n<p>While there are always bugs in software and occasional unexpected downtime, having these happen regularly can damage your and, if applicable, your client's reputation.<\/p>\n\n<p>Therefore, it's in everyone's interest to write high-quality and well-tested software.<\/p>\n\n<p>There will be fewer bugs, and by following practices such as feature flags and continuous integration and delivery, they can be fixed faster.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0fe766113c492410fc331b3c40f82f8e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.eef4147e-e47a-411e-a7de-eb67638dc6bb.json b/content/node.eef4147e-e47a-411e-a7de-eb67638dc6bb.json
index 0426cff14..706416b9c 100644
--- a/content/node.eef4147e-e47a-411e-a7de-eb67638dc6bb.json
+++ b/content/node.eef4147e-e47a-411e-a7de-eb67638dc6bb.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I like to keep my code simple.<\/p>\n\n<p>I only write the code I need to add the functionality I need, and I only include the current requirements.<\/p>\n\n<p>There's no benefit to writing code for additional requirements that may never be needed or used.<\/p>\n\n<p>I also think this when adding new modules or packages, or implementing a design pattern.<\/p>\n\n<p>Do I really need this?<\/p>\n\n<p>What value does it add?<\/p>\n\n<p>Is there a simpler way to achieve the same thing?<\/p>\n\n<p>If so, I'm happy to call YAGNI on it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d55547f4588464a67252a7743560b0b3",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json b/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json
index 93feeb82f..fb598d300 100644
--- a/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json
+++ b/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>An important thing when using a tool like <a href=\"http:\/\/default\/daily\/2023\/01\/23\/debugging-with-git-bisect\">git bisect<\/a> as well as reviewing pull\/merge requests and commits is to have small (aka \"atomic\") commits.<\/p>\n\n<p>Commits with small changes make them easier to review and, if needed, to revert and debug with bisect. If a commit has ten new or changed lines, it's much easier to see and fix a bug than if the commit had a hundred lines.<\/p>\n\n<p>If you're doing code reviews or \"Showing\" in a Ship\/Show\/Ask format, you'll likely get better and more valuable feedback if the commits are smaller and only doing one thing.<\/p>\n\n<p>If you're submitting a change for review, commit a failing test first so that it can be seen failing before committing the code to make it pass. This makes it easier to see that the code is actually making the test pass.<\/p>\n\n<p>Also take some time to write good, informative commit messages.<\/p>\n\n<p>As well as the short one-line subject, you can add as much detail as you need to the body of the message about the change that's being committed, why it's needed, what other approaches were considered or tried, as well as links to supporting documentation such as ADRs, technical design documents or diagrams.<\/p>\n\n<p>Having as much information as possible makes it much easier when someone needs to review or fix a specific commit. I like to use the <a href=\"http:\/\/default\/daily\/2022\/09\/01\/conventional-commits-changelogs\">conventional commits specification<\/a>, though the main objective is to have all of the information documented so it's available in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ef62cb3ca57e2e9ff518c139412e1563",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json b/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json
index 408476732..79ab44588 100644
--- a/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json
+++ b/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently been going through my YouTube \"Watch Later\" list and watching (or rewatching) videos of conference and meetup talks that I saved to watch later.<\/p>\n\n<p>Today's talk was by Matt Stauffer at one of the previous Laracon conferences.<\/p>\n\n<p>I've quoted Matt previously when explaining what to test on applications. The answer: \"The thing you'd lose your job for if it broke\".<\/p>\n\n<p>In this talk, Matt has a slide that goes further into this, titled \"Test to save your job\".<\/p>\n\n<h2 id=\"what-matt-said\">What Matt said<\/h2>\n\n<p>The best place to start your tests is by asking yourself: \"What part of this app, if broken, would make me worried for my job?\"<\/p>\n\n<ul>\n<li>What's most likely to break?<\/li>\n<li>What do I have the least control over?<\/li>\n<li>What are we about to refactor?<\/li>\n<li>What would make my clients stress out?<\/li>\n<li>What would make me stressed out?<\/li>\n<\/ul>\n\n<h2 id=\"what-about-you%3F\">What about you?<\/h2>\n\n<p>Do you have any other ways to decide what code to test? Reply and let me know, as I'd love to know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "c2095c4a1278959cfff849fb4f819ace",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json b/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json
index f7a1bee8c..9d3400338 100644
--- a/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json
+++ b/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After <a href=\"http:\/\/default\/daily\/2022\/10\/24\/looking-at-localgov-drupal\">previously looking at the LocalGov Drupal distribution<\/a>, today I added a LocalGov Drupal example to my <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/tree\/main\/drupal-localgov\">Docker Examples repository<\/a>.<\/p>\n\n<p>Based on the Drupal 10 example, the LocalGov Drupal example used Composer's <code>create-project<\/code> command to scaffold the project plus some additional configuration files such as the <code>Dockerfile<\/code>, <code>docker-compose.yaml<\/code> and a <code>justfile<\/code>.<\/p>\n\n<p>A feature on my list is to add to both examples is to install Drupal automatically instead of opening the installation screen or having to run an install command. Once that's in place, it'll remove a manual step and allow people to see the application more quickly.<\/p>\n\n<p>I have some issues for examples and enhancements to add within <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/issues\">the repository's issue queue<\/a> and would welcome any suggestions or questions.<\/p>\n\n<p>For LocalGov itself, I hope to find more opportunities to use and contribute to it in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "23799429878e6da040e6b839e960f525",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json b/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json
index bdcd0f9ef..a25c35a2a 100644
--- a/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json
+++ b/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Instead of using tools like Docker or nvm to manage dependencies for your projects, you can use Nix instead.<\/p>\n\n<p>Creating a Nix shell or flake for each project with its dependencies will install everything without needing containers and with the benefit of everything being locked to specific versions, <a href=\"http:\/\/default\/daily\/2024\/11\/12\/why-consistency-and-reproducibility-are-important\">making environments reproducible<\/a>.<\/p>\n\n<p>If you need a specific version of PHP or node for a project, it will be available and different versions can be used for other projects.<\/p>\n\n<p>And if you need services like MySQL and you're not using NixOS, you can also use devenv to manage services, tasks and processes for each project.<\/p>\n\n<p>For me, Nix and devenv have <a href=\"http:\/\/default\/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">replaced Docker and Docker Compose<\/a> on my development projects.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "461f987d1bc88b97e125becc82a9fd46",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json b/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json
index 8cc89eae9..9376a8d36 100644
--- a/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json
+++ b/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I saw a Twitter poll - \"Poll: Imagine your team has to build a project with either types or tests. You can't have both.\".<\/p>\n\n<p>The results were:<\/p>\n\n<ul>\n<li>Types - 50.9%<\/li>\n<li>Tests - 49.1%<\/li>\n<\/ul>\n\n<p>I was surprised by this.<\/p>\n\n<p>If I can't add type declarations (type hints) or return types, I can still write tests to check what happens when different types are used.<\/p>\n\n<p>I can also perform checks and throw errors or Exceptions if something isn't what I'd expect.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I use types heavily, but I'd be more confident that my application would work if I had tests and that's the main objective when writing code for myself or clients and for my clients' customers.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "1ea9de41ddc7b8f9fcdc10618e2ae56b",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json b/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json
index e6eda1191..028ebdae8 100644
--- a/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json
+++ b/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2025\/01\/19\/minimum-viable-development-environment\">In yesterday's email<\/a>, I showed how I've been using Nix and flake files to build reproducible and shareable development environments for Drupal applications.<\/p>\n\n<p>The reason it's reproducible is the <code>flake.lock<\/code> file.<\/p>\n\n<p>Similar to <code>composer.lock<\/code> or <code>package-lock.json<\/code>, it captures the exact versions of the packages installed from the nixpkgs repository.<\/p>\n\n<p>This file, along with <code>flake.nix<\/code>, can be committed alongside the application code and anyone with Nix installed can run <code>nix develop<\/code> to get a shell with the same packages and dependencies.<\/p>\n\n<p>This isn't the same as other solutions, where you add something like <code>FROM php:8.2<\/code> but, because there's no lockfile, there's no guarantee the same package versions will be installed so there could be mismatches that cause errors.<\/p>\n\n<p>With <code>flake.lock<\/code>, the environment isn't just repeatable - it's completely reproducible.<\/p>\n\n<p>Locally, in a CI pipeline or in production.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "53ca25f2417162597931bed0d3c8cb57",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json b/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json
index b545fc901..70ebc3ad7 100644
--- a/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json
+++ b/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/04\/22\/building-websites-with-php-and-sculpin\">In February<\/a>, I spoke at the PHP South West meetup about Sculpin - a static site generator written in PHP.<\/p>\n\n<p>Sculpin uses Twig, HTML and Markdown to generate static HTML files that you can upload to any web server.<\/p>\n\n<p>You don't need PHP or a database server - making it simpler and cheaper to host compared to a CMS-powered site.<\/p>\n\n<p>There's also no database for people to hack into and, as they're just static HTML pages, they are very quick to load.<\/p>\n\n<p>The downside is that files need to be created and edited locally or editing Git files on GitHub, etc, as there's no CMS to log into.<\/p>\n\n<p>Still, for some projects, static site generators are a great option.<\/p>\n\n<p>For Drupal, there's Tome - a module that creates a static website from a Drupal installation, and something I plan to investigate.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f8ddff544e9f6f9a874ffeb914537a12",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json b/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json
index 202c97f4c..d51e2fc46 100644
--- a/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json
+++ b/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Next Wednesday evening, I'm going to be speaking remotely at the Drupal London meetup.<\/p>\n\n<p>I was originally going to attend in person, but after injuring my foot last week, I can't travel so will have to join remotely.<\/p>\n\n<p>I'm going to be giving a talk and demo of <a href=\"http:\/\/default\/presentations\/tdd-test-driven-drupal\">automated testing and test-driven development with Drupal<\/a> as well as some Q&amp;A and pair programming, if time allows and we're able to do so remotely.<\/p>\n\n<p>RSVPs are still open for the event and hopefully I'll get to attend Drupal London in person in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9400b956833d34cef7783e6b4ae755bd",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json b/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json
index bfd7a3ab3..f7dafb951 100644
--- a/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json
+++ b/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Once you have a deployment that's run using Ansible, rather than running it manually, it's easy to automate it as part of a continuous integration pipeline and have your changes pushed automatically by tools like GitHub Actions and GitLab CI.<\/p>\n\n<p>You'll need to configure SSH by adding a known hosts file and a private key so the tool can connect to your server, but after that, it's just running the same Ansible commands.<\/p>\n\n<p>If you're using Ansistrano or other roles, you can install dependencies by using <code>ansible-galaxy<\/code>, and <code>ansible-vault<\/code> to decrypt and use any encrypted variables - securely storing the Vault password and any other secrets as environment variables within your pipeline.<\/p>\n\n<p>Here's an example using GitHub Actions:<\/p>\n\n<pre><code>- name: Download Ansible roles\n  run: ansible-galaxy install -r requirements.yml\n\n- name: Export the Ansible Vault password\n  run: echo $ANSIBLE_VAULT_PASS &gt; .vault-pass.txt\n  env:\n    ANSIBLE_VAULT_PASS: $\n\n- name: Deploy the code\n  run: &gt;\n    ansible-playbook deploy.yml\n    -i inventories\/$INVENTORY_FILE.ini\n    -e \"project_git_branch=$GITHUB_SHA\"\n    --vault-password-file=.vault-pass.txt\n\n- name: Remove the Ansible Vault password file\n  run: rm .vault-pass.txt\n<\/code><\/pre>\n\n<p>Before these steps, I've added the SSH key and determined which inventory file to use by the updated branch. The Vault password is exported and then removed once it has been used.<\/p>\n\n<p>Automated tests and other code quality checks can be run in prior job, ensuring that the deployment only happens if those checks pass, but assuming that all is good, the playbook will be run and the changes will be deployed automatically.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0ef60547dc24a30bc29205ee7fee1f5a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f343899f-5778-4b23-a97e-bda411656646.json b/content/node.f343899f-5778-4b23-a97e-bda411656646.json
index b5e8f855c..9f40203f5 100644
--- a/content/node.f343899f-5778-4b23-a97e-bda411656646.json
+++ b/content/node.f343899f-5778-4b23-a97e-bda411656646.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Everyone tests their code.<\/p>\n\n<p>No one writes code and ships it to production before testing it works.<\/p>\n\n<p>It's just that most Developers test their code manually.<\/p>\n\n<p>They write the code, switch to a browser or terminal, and run it.<\/p>\n\n<p>It might be a quick task, such as reloading a page or executing a command, or it could be complex and time-consuming, such as filling in a long form and checking the results.<\/p>\n\n<p>In this case, automated testing is a good option.<\/p>\n\n<p>Instead of filling in the form, have the tests do it for you.<\/p>\n\n<p>It will be quicker and more reliable than doing it manually.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "60134faa8ccecf50d1f6520e1f849b0c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json b/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json
index 432360de7..368bf308f 100644
--- a/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json
+++ b/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm currently working on a Vue.js application that I started building in Vue 2 before starting to use the Composition API, and then moved it to Vue 3.<\/p>\n\n<p>In the original version, I was using Vuex for state management within the application, and interacting with Vuex directly within my Vue components - calling <code>getters<\/code> and <code>dispatch<\/code> to retrieve and update data.<\/p>\n\n<p>As part of moving to Vue 3, I wanted to evaluate any new options, like Pinia which is now the default state management library for Vue.<\/p>\n\n<p>But because I was integrating with Vuex directly, switching to an alternative would mean changing code within my components.<\/p>\n\n<h2 id=\"defining-a-store-interface\">Defining a Store interface<\/h2>\n\n<p>This is a situation that often occurs in back-end development - where you may need to switch to a different type of database or a different payment provider in an eCommerce application.<\/p>\n\n<p>In that situation, you need a generic interface that can be used by different implementations. Because they have consistent methods, one implementation can be replaced with another or multiple can be added at the same time. This is called the Strategy design pattern, and related to the open-closed principle in SOLID.<\/p>\n\n<p>This is what I did by adding a <code>Store<\/code> interface:<\/p>\n\n<pre><code class=\"javascript\">export default interface Store {\n  actions: {\n    addRow(): void;\n    init(): void;\n    removeRow(index: Number): void;\n  };\n\n  state: {\n    isLoading: boolean;\n    selection: {\n      items: [];\n    };\n  };\n}\n<\/code><\/pre>\n\n<p>Any store that I want to work with needs to have these defined actions and state values, so I can use them within my components knowing that they will always be available.<\/p>\n\n<h2 id=\"creating-a-native-vue-store\">Creating a native Vue store<\/h2>\n\n<p>This is one implementation of the <code>Store<\/code> interface, using just Vue's <code>reactive<\/code> function from the Composition API:<\/p>\n\n<pre><code class=\"javascript\">let state = reactive({\n  isLoading: false,\n  selection: {\n    items: [],\n  },\n});\n\nlet actions = {\n  addRow(): void {\n    state.selection.items.push({\n      \/\/ ...\n    });\n  },\n\n  init(): void {\n    state.isLoading = true;\n\n    \/\/ ...\n  },\n\n  removeRow(index: number): void {\n    state.selection.items.splice(index, 1);\n  },\n};\n\nconst vueStore: Store = {\n  actions,\n  state: readonly(state),\n};\n\nexport default vueStore;\n<\/code><\/pre>\n\n<p>If I needed to add a Pinia version or another library, I can create another implementation that complies with same interface.<\/p>\n\n<p>Each implementation being responsible for any specifics for that library - extracting that logic from the component code making it more flexible and reusable.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f746e5178d11a55b0a3eed164216d25a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json b/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json
index 5050b8762..3c0e7c96b 100644
--- a/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json
+++ b/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In my last email, I mentioned that I maintain several Drupal websites for a client using the same codebase, but how do I do that?<\/p>\n\n<p>The sites use Drupal's multisite functionality to have a separate directory for each site, each with its own settings file and files, and potentially modules and themes. Whilst there are some downsides to this approach, and we did evaluate alternatives, this approach allows us to keep one hosting account and save the client money compared to hosting each site separately.<\/p>\n\n<p>Each site has a separate database and configuration files, so out of the box, I can customise what functionality is needed on each site by turning modules on and off. Whilst this is fine for larger pieces of functionality, for smaller pieces I like to use feature flags.<\/p>\n\n<p>I use feature flags on single-site projects to separate deploying code from releasing a change, but I can also use them here to toggle something per-site. This could be using a module like <a href=\"https:\/\/www.drupal.org\/project\/feature_toggle\">Feature toggle<\/a> or another way like a checkbox on a settings form. Anything that I can use to say \"Do this if that is enabled\".<\/p>\n\n<p>Settings such as setting an endpoint URL or storing some API credentials would be set in an admin form and stored as configuration per site.<\/p>\n\n<p>I've tried various iterations of this - initially duplicating the custom code and having several near-identical versions of the same modules (this wasn't good for maintenance). We also used environment variables. However, this didn't scale as I added more sites and needed to create a new set of environment variables every time.<\/p>\n\n<p>This approach has worked well for the last few years on their original websites and should continue to work well as I upgrade and migrate them to their next versions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "00bb8f11007795b6fe1e9ad3728526ae",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json b/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json
index 98ee2f427..a44c52758 100644
--- a/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json
+++ b/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>A few days ago, I asked <a href=\"http:\/\/default\/daily\/2024\/12\/23\/how-many-environments-do-you-need\">how many pre-production environments<\/a> you have for your software application.<\/p>\n\n<p>But did you include each Developer's local environment?<\/p>\n\n<p>Each developer will have a development environment - either on their computer or a development server - to write and initially test their code before it's deployed to a test, staging or production environment.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Each Developer's local or development site is an environment too.<\/p>\n\n<p>They also <a href=\"http:\/\/default\/daily\/2024\/12\/24\/moving-changes\">need to be easily updatable<\/a> and consistent with the other environments, but they are often overlooked or forgotten.<\/p>\n\n<p>When was the last time you or your Developers updated your local environment?<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ccf6ad9403289a3e6790c1f35b1ec8a0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json b/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json
index f45bb1591..82d19a81d 100644
--- a/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json
+++ b/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Since switching to Nix and NixOS, I've been looking for opportunities to use Nix more in addition to managing my laptop and server configurations and creating development shells for projects.<\/p>\n\n<p>Nix is a build tool, so I've started to use it to build my slide decks which I create using rst2pdf.<\/p>\n\n<p>I write the rst (reStructuredText) file and compile it to a PDF file.<\/p>\n\n<p>I had a flake.nix file to add rst2pdf, pdfpc and other tools to my shell, but the compilation to a PDF file was done in a bash script which I've since removed.<\/p>\n\n<p>Here's how my flake.nix file looks now:<\/p>\n\n<pre><code class=\"nix\">{\n  inputs.nixpkgs.url = \"github:NixOS\/nixpkgs\/nixos-unstable\";\n\n  outputs = { nixpkgs, ... }:\n    let\n      system = \"x86_64-linux\";\n      pkgs = import nixpkgs { inherit system; };\n\n      inherit (nixpkgs.lib) makeOverridable;\n      inherit (pkgs.stdenvNoCC) mkDerivation;\n\n      shared = mkDerivation {\n        name = \"talks-shared\";\n        src = .\/src;\n\n        installPhase = ''\n          runHook preInstall\n\n          mkdir $out\n          cp -r fonts styles $out\n\n          runHook postInstall\n        '';\n      };\n\n      commonBuildInputs = with pkgs; [\n        (python310.withPackages (p: with p; [ rst2pdf ]))\n      ];\n\n      mkTalk = makeOverridable ({ src }: mkDerivation {\n        inherit shared src;\n\n        name = builtins.head (builtins.attrNames talks);\n\n        buildInputs = commonBuildInputs;\n\n        buildPhase = ''\n          runHook preBuild\n\n          mkdir $out\n\n          rst2pdf slides.rst \\\n            --break-level 1 \\\n            --fit-background-mode scale \\\n            --font-path \"${toString shared}\/fonts\" \\\n            --output \"$out\/slides.pdf\" \\\n            --stylesheets bw,\"${toString shared}\/styles\/opdavies-light\"\n\n          runHook postBuild\n        '';\n      });\n\n      talks = {\n        build-configs = mkTalk { src = .\/src\/building-build-configs; };\n        sculpin = mkTalk { src = .\/src\/building-static-websites-sculpin; };\n        tailwind-css = mkTalk { src = .\/src\/taking-flight-with-tailwind-css; };\n        test-driven-drupal = mkTalk { src = .\/src\/test-driven-drupal; };\n      };\n    in\n    {\n      devShells.${system}.default = with pkgs; mkShell {\n        packages = with pkgs; commonBuildInputs ++ [\n          ghostscript\n          just\n          pdfpc\n          texliveMedium # includes pdfjam\n        ];\n      };\n\n      packages.${system} = {\n        inherit shared;\n      } \/\/ talks;\n    };\n}\n<\/code><\/pre>\n\n<p>Each talk is its own derivation, so I can run <code>nix run .#test-driven-drupal<\/code> and it will generate the appropriate PDF file for me to present or share.<\/p>\n\n<p>The source code is available at <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/talks\">https:\/\/code.oliverdavies.uk\/opdavies\/talks<\/a> if you want to see how I use rst2pdf to create my presentations and I've even <a href=\"http:\/\/default\/presentations\/building-presenting-slide-decks-rst2pdf\">given a presentation about how I create presentations<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "83515e94d744b93f13eb7b8a56283bcc",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json b/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json
index eb54bd6df..f5676bff5 100644
--- a/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json
+++ b/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I released <a href=\"http:\/\/default\/podcast\/1-retrofit\">the first episode of the \"Beyond Blocks\" podcast<\/a>.<\/p>\n\n<p>I spoke with Matt Glaman - Principal Software Engineer at Acquia and author of Retrofit.<\/p>\n\n<p>Retrofit makes it easier to upgrade from Drupal 7 by adding compatibility layers to run your legacy code within Drupal 10 - giving you more time to port it to the modern approaches and standards.<\/p>\n\n<p>I've been aware of Matt and his work for some time, including his work on Drupal Commerce, so it was great to speak with him and for him to be the first guest on the podcast.<\/p>\n\n<p>Future episodes will be <a href=\"http:\/\/default\/podcast\">published online<\/a> weekly, so feel free to subscribe and let me know if you have feedback, suggestions for future guests and topics, or want to be a guest.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cfe4233208f6139cd05fc4319defd268",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json b/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json
index 693cdc3d6..bd68dc799 100644
--- a/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json
+++ b/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>\"Vim is my lightsaber\" is the final chapter of Jess Archer's Neovim course on Laracasts.<\/p>\n\n<p>In this summary, Jess explains that some Star Wars characters have lightsabers customised to their preferences and fighting style.<\/p>\n\n<p>Vim is her lightsaber - her personalised tool to develop software. It works how she wants it to, with the features she needs.<\/p>\n\n<p>I've written before about mastering your tools and thought this was a nice spin on it.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "cab67b9a1e9754bab69a7eb6e764fc33",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json b/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json
index 26bd17646..83a82093a 100644
--- a/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json
+++ b/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Do you want to make it easier to keep your PHP code up to date with the latest standards and using the latest features?<\/p>\n\n<p>Rector is a tool for refactoring PHP code and it has presets for different versions of PHP.<\/p>\n\n<p>It can refactor your code to follow best practices such as using early returns, having private methods by default and enabling strict typing - making code cleaner whilst using the latest PHP features.<\/p>\n\n<p>Once installed, it can be executed and will make changes to your files, but what about keeping it up to date going forward?<\/p>\n\n<p>Why not add <code>rector --dry-run<\/code> to your CI pipeline and have it checked automatically?<\/p>\n\n<p>Then, if code is committed that doesn't match the latest standards, the pipeline will fail and the code can be updated.<\/p>\n\n<p>This will ensure the code is always up to date and you won't be stuck on old or unsupported PHP versions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b8c389b3b092927696ab5949cecfe240",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json b/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json
index 40f8367c0..3972e880e 100644
--- a/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json
+++ b/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I've been watching the new <a href=\"https:\/\/symfonycasts.com\/screencast\/symfony7-upgrade\">Upgrading &amp; What's in Symfony 7<\/a> video course on SymfonyCasts.<\/p>\n\n<p>The first video - <a href=\"http:\/\/default\/podcast\/10-ryan-weaver-symfonycasts\">recent podcast guest Ryan Weaver<\/a> - explains how Symfony's release cycle works.<\/p>\n\n<p>New feature releases that contain new features are every six months.<\/p>\n\n<p>Along with the x.4 release - such as Symfony 6,4 - there is also a new major release - in this case, Symfony 7.<\/p>\n\n<p>They are essentially identical, except for code that was deprecated in Symfony 6, which has been removed.<\/p>\n\n<p>So, updating from Symfony 6.4 to 7 means you just need to remove any deprecated code from your application and make it work in the Symfony 7 way.<\/p>\n\n<p>This is also how Drupal releases new versions, too.<\/p>\n\n<p>New releases, like Layout Builder, are added in minor versions like 8.1, and Drupal 9 is Drupal 8 without its deprecated code.<\/p>\n\n<p>Because the code in major versions is so similar, <strong>contributed modules and themes can support multiple major versions at the same time<\/strong>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>When upgrading projects from Drupal 8 to 9 and 9 to 10, the majority of the work can be done beforehand by keeping up to date with module releases and updating custom code to remove any deprecations.<\/p>\n\n<p>This means the upgrade can be split over several weeks or months to reduce the risk.<\/p>\n\n<p>Then, finally, you <em>just<\/em> update to the next major version.<\/p>\n\n<p>All the hard work has already been done.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f974bdb7342e7a84aac0ceb4a74dbdfa",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json b/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json
index cfa16c7e9..27dcf22de 100644
--- a/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json
+++ b/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><code>git cherry-pick<\/code> is a command that allows you to re-apply changes from existing commits - typically moving commits from one branch to another. Whilst it's good for some use-cases, I believe that it's generally an anti-pattern.<\/p>\n\n<p>As I mostly do trunk-based development so only have a single branch, it's not a command that I'd run often - but I have seen it used in a Git Flow-type scenario where there are multiple long-lived branches and various other short-lived ones. Commits can be cherry-picked between a long-term branch like <code>develop<\/code> onto a feature branch rather than merging or rebasing, or to re-apply a hotfix from the <code>main<\/code> branch.<\/p>\n\n<p>The main issue that I've seen with <code>cherry-pick<\/code> is where a number of changes have been merged into a branch which is being used for user acceptance testing by a client or product owner. They decide to approve some of the changes but not all, and the approved commits are cherry-picked onto a production branch and deployed.<\/p>\n\n<p>In my opinion, this is very risky as there's no guarantee that the cherry-picked changes will work without the others, and as the artifact that's pushed to production is different to what was tested against, it arguably affects the value of doing the testing at all. Ideally, once the release has been tested and approved, the same artifact will be deployed - ensuring consistency and reducing the risk of any errors.<\/p>\n\n<p>Potentially, the cherry-picked changes could be moved onto a release branch and tested again together without the other changes, but this would increase the testing overhead and the time for the changes to release production.<\/p>\n\n<p>A good automated test suite would help, ensuring that the tests still pass once the cherry picking is done.<\/p>\n\n<p>In this situation, I'd rather use feature flags (also known as \"feature toggles\"). This would mean that the code between the two environments would be the same, and allow for functionality to be enabled or disabled as needed. If a feature wasn't selected to be released, then it's feature flag would be disabled until it's approved.<\/p>\n\n<p>A feature flag would also allow a feature to be switched off if it was causing errors without the need for a code deployment. If a change did need a code change, if you're following continuous integration and delivery, it would be easy to apply and push a fix.<\/p>\n\n<p>These are the use-cases that I can think of or have seen for <code>git cherry-pick<\/code>. If you know of any others or use <code>cherry-pick<\/code> in your workflow in another way, reply to the email and let me know.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2306bfa479659b451bdcfa4124aac8ed",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json b/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json
index bcd332d01..b38940744 100644
--- a/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json
+++ b/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2023\/11\/28\/which-phpstan-level-should-you-use\">Yesterday's email<\/a> introduced the different levels that PHPStan offers and which you may want to use on your codebase.<\/p>\n\n<p>In the same way as having a single test is better than none, even if you run PHPStan at the lowest level, it's better than not running it at all.<\/p>\n\n<p>Level 0 includes:<\/p>\n\n<blockquote>\n  <p>Basic checks, unknown classes, unknown functions, unknown methods called on $this, wrong number of arguments passed to those methods and functions, always undefined variables<\/p>\n<\/blockquote>\n\n<p>P.S. If you want to utilise PHPStan and static analysis on your development team and get fewer bugs, I have <a href=\"http:\/\/default\/team-coaching\">availability for team coaching<\/a>. I'll show you how!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d436cc2ce8cace5ee48ba43b332aee65",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json b/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json
index 9308913e6..79286c306 100644
--- a/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json
+++ b/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><code>tldr<\/code> is a command-line tool that I've been using a lot recently.<\/p>\n\n<p>Usually, on the command line, you'd use the <code>man<\/code> command to show a manual page for a certain command - like <code>man ls<\/code>.<\/p>\n\n<p><code>tldr<\/code> is \"a collection of simplified and community-driven man pages\".<\/p>\n\n<p>After installing it, run <code>man tldr<\/code> or even <code>tldr tldr<\/code> to learn more about it.<\/p>\n\n<p>Then, run a command like <code>tldr ls<\/code> to get output for a specific command.<\/p>\n\n<p>I like that it shows a short description of what the command does, followed by a link to find out more information and then several valuable examples demonstrating the various options, flags, and arguments the command takes.<\/p>\n\n<p>For <code>ls<\/code>, it shows how to list one file per line, list hidden files, use a long format list, show human-readable size units, long format sorted by size or modification date, and only show directories.<\/p>\n\n<p>For commands like <code>tar<\/code>, <code>rsync<\/code>, and <code>scp<\/code> that I don't use that often or can't remember all of the different options, I like being able to see these examples and figure out what I need at that time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f8b9fce72ec35d462c229ed98873a255",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json b/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json
index 533f1256e..1b1f266d9 100644
--- a/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json
+++ b/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>The Null Object pattern is one of my favourite ways to DRY up code and reduce duplication.<\/p>\n\n<p>I wrote the <a href=\"https:\/\/www.drupal.org\/project\/system_user\">System User module<\/a> for a client project a number of years ago, which also included the <a href=\"https:\/\/www.drupal.org\/project\/null_user\">Null User module<\/a>.<\/p>\n\n<p>If no system user is found, it returns a null (empty) user instead that returns null or empty values by default.<\/p>\n\n<p>Today, <a href=\"https:\/\/x.com\/opdavies\/status\/1829183673725284772\">I posted<\/a> <a href=\"https:\/\/mastodon.social\/@opdavies\/113046773292848198\">and tooted<\/a> a screenshot of some code from a side project I'm working on, which I realised would be another good time to use the Null User module.<\/p>\n\n<p>In the code, I search for a user with a given licence key.<\/p>\n\n<p>If a user is found, it is returned.<\/p>\n\n<p>If not, instead of returning FALSE or NULL, I return a null user object that I can treat the same as a real user.<\/p>\n\n<p>Now, when I create the node and assign an owner, I can just use <code>$account-&gt;id()<\/code> and it will always work if a user was found or not.<\/p>\n\n<p>This makes the code cleaner, simpler and easier to test and maintain.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b0f5d618c19973d6f434cb0ac0614fdb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json b/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json
index 3ce985671..8b4a4cb65 100644
--- a/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json
+++ b/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you're stuck on Drupal 7, why should you upgrade to Drupal 10 instead of moving to another platform?<\/p>\n\n<h2 id=\"familarity\">Familarity<\/h2>\n\n<p>Although there is a new admin theme, it works in the same way as it did in earlier versions of Drupal, so it will be familiar to anyone who is used to using or developing in it.<\/p>\n\n<p>And whilst there have been differences since Drupal 8, creating modules and themes should seem familiar too with similar concepts such as <code>.info<\/code> files (now <code>.info.yml<\/code> files), hooks, preprocess functions and templates.<\/p>\n\n<h2 id=\"code-reuse\">Code reuse<\/h2>\n\n<p>If you have existing custom modules, you should be able to reuse some of its code in newer versions of Drupal. It might need to be restructured or refactored and will depend on how tightly coupled your business logic is to your Drupal code, but if, for example, you have a custom module that creates a node programmatically, the same can be done in newer Drupal versions.<\/p>\n\n<h2 id=\"built-in-migration-tools\">Built-in migration tools<\/h2>\n\n<p>Whilst you do need to migrate your data from Drupal 7 into Drupal 10, the newer versions come with built-in migration tools that recreate your content types etc first as well as moving the data so you don't need to start from scratch.<\/p>\n\n<h2 id=\"new-versions-of-existing-modules\">New versions of existing modules<\/h2>\n\n<p>Many modules and themes you use in Drupal 7 will either have equivalent versions for Drupal 10 or a nominated alternative (such as Field Collection to Paragraphs), so you don't need to look for a new solution if there's an updated version of something you already use.<\/p>\n\n<h2 id=\"conclusion\">Conclusion<\/h2>\n\n<p>These are the initial things that I thought of, but there are many other reasons to upgrade to Drupal 10 instead of moving to something else.<\/p>\n\n<p>TLDR - you don't need to start from scratch if you can re-use parts of your existing code, and you can use the built-in modules to handle the data migration.<\/p>\n\n<p>If you have a reason, reply to let me know, and I'll post another list.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "0b974200c82916119ed21b25b854c421",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json b/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json
index 5568c2ae2..a6d1bafbc 100644
--- a/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json
+++ b/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've recently added several custom search blocks and pages to a client project.<\/p>\n\n<p>Each requires a results page, a list of autocomplete suggestions for users to select from, a custom form, and a block to place it on the required pages.<\/p>\n\n<p>For each search, I'm first testing the results page, ensuring it exists and contains the correct results before testing the autocomplete results, creating the block and form, and linking everything together.<\/p>\n\n<h2 id=\"thinking-small\">Thinking small<\/h2>\n\n<p>This could seem like a large and daunting task, but with test-driven development, I can break everything into smaller, more manageable tasks.<\/p>\n\n<p>My objective is either to write the next failing test and then get it to pass or to refactor what I've written.<\/p>\n\n<p>I can focus on these small steps and make progress towards the end goal, guided by the tests I'm writing, instead of needing to focus always on one large and complex task.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9266f4bfd35bc443765c6c434bc5975e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json b/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json
index c2db77c50..20bd28c7c 100644
--- a/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json
+++ b/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If you need to provide estimates for your tasks and intend to write tests, include the time for the tests within the estimate.<\/p>\n\n<p>Don't provide different estimates for testing and the implementation, or with tests and without tests - give one estimate that includes both.<\/p>\n\n<p>Writing tests and testable code will take longer to begin with, but practice makes perfect and will save time in the long run.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8aa785b28b32f4d7c1b6db80b6b763a2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json b/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json
index bc83d4d15..d1439fc56 100644
--- a/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json
+++ b/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Next week is DrupalCon in Barcelona.<\/p>\n\n<p>I'm not speaking this year but if you're there and want to discuss automated testing, test-driven development, static analysis, Sculpin, Tailwind CSS, Nix, or anything else, I'll be there all week and would love to meet up and chat.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "d1416da5c89de0128a5e492e9ddafdfb",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json b/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json
index 5df496915..b925aee3a 100644
--- a/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json
+++ b/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I upgraded my <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/tree\/main\/drupal\">Drupal Docker example<\/a> to Drupal 10.<\/p>\n\n<p>Admittedly, it's a simple project, but upgrading from Drupal 9 to 10 was a straightforward process.<\/p>\n\n<p>I had to remove the Examples module as there's no Drupal 10 compatible version yet, but updating to Drupal 10 only needed me to change the version constraints in the <code>composer.json<\/code> file and run the <code>composer update<\/code> command.<\/p>\n\n<p>After completing a number of Drupal 7 upgrade projects which involve migrating content, rewriting custom modules, and rebuilding themes, it's great to be able to upgrade between major modern versions with a few simple commands.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7648009a474298b1a14504ba7a413f7e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json b/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json
index 891355ccf..f1248730e 100644
--- a/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json
+++ b/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Yesterday's email was about shortening the feedback loop of a CI pipeline by running some of the checks like PHPCS and PHPStan locally and dealing with any errors before they get pushed to the code repository.<\/p>\n\n<p>What's even better than writing and committing code and then waiting until just before pushing it to test it? Seeing the errors in real-time and being able to fix them immediately.<\/p>\n\n<p>In my Neovim setup (I talked about this at the PHP London meetup recently), I have the Intelephense language server configured to add IDE-like features such as code completion, go-to definition, symbol renaming, etc.<\/p>\n\n<p>I also have another plugin - <code>null-ls.nvim<\/code> - that adds errors from command-line tools to Neovim's diagnostics list.<\/p>\n\n<p>So, if I try to do something that would cause a PHPStan failure, such as using an unknown variable or missing a return type, I can see that and fix it immediately and not even wait for a Git hook to run.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ce828fb0f1512107c9cbf2309c3d5b96",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json b/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json
index 1e5c580bf..0bd37417d 100644
--- a/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json
+++ b/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>In Sunday's email, I said not to estimate separately for testing and implementation.<\/p>\n\n<p>But you can't do this anyway if you're doing test-driven development.<\/p>\n\n<p>With TDD, you aren't writing all of your tests and all of the implementation code or vice versa.<\/p>\n\n<p>You're continuously switching back and forth, starting by writing a failing test and then enough implementation code for it to pass.<\/p>\n\n<p>Then you write more test code, whether expanding the same test or writing a new one until you have a new failure.<\/p>\n\n<p>You get it to pass, refactor, and repeat the process until the task is complete.<\/p>\n\n<p>It's all part of the same task and the same estimate.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "07d86990b8ff8b2156a15058bc92d8e4",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json b/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json
index 520d18715..36c0537e6 100644
--- a/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json
+++ b/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I'm now self-hosting my website, the other static websites I maintain and <a href=\"https:\/\/code.oliverdavies.uk\">my Forgejo instance<\/a> that contains my Git repositories.<\/p>\n\n<p>These were previously on a VPS (virtual private server) but now are running on my homelab - an old laptop that I've been using to run Jellyfin and other software.<\/p>\n\n<p>It's great to know I have full control over my data and to not pay a recurring monthly cost forever to host my website. Later, if I decide my current homelab laptop needs an upgrade, I can do that.<\/p>\n\n<p>With NixOS, the transition from the Cloud to my home server was simple and just a case of moving some configuration files from one directory to another as I've set it up in a modular way.<\/p>\n\n<p>I've also switched back to Nginx which was also easy to migrate my configuration and redirects using the Nix language and NixOS configuration options.<\/p>\n\n<p>My website is a static website, mostly <a href=\"http:\/\/default\/presentations\/sculpin\">generated by Sculpin<\/a> but there are some pages generated by Tome - <a href=\"http:\/\/default\/daily\/2025\/04\/18\/static-drupal\">a static site generator for Drupal<\/a>.<\/p>\n\n<p>I'm migrating my email list archive and daily pages first and will later move my presentations, podcast episodes and old blog posts, but I'm <a href=\"http:\/\/default\/daily\/2025\/04\/17\/incrementally\">doing it incrementally based on the path<\/a> so I can do pieces as I can around client work.<\/p>\n\n<p>If you like, you can <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/nixos-configuraton\">see my NixOS configuration<\/a> that includes my laptop and homelab and <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/oliverdavies.uk-tome\">my Tome repository<\/a> and keep track as I migrate things across.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "8afd6c68260de0b67d4d42f8c66d87b0",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json b/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json
index 0c26d743a..a6f9c131c 100644
--- a/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json
+++ b/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I've been looking at <a href=\"https:\/\/localgovdrupal.org\">LocalGov<\/a> - a Drupal distribution for building council websites, with a focus on code reuse and collaboration.<\/p>\n\n<p>After a few small changes, I was able to get it running based on my <a href=\"https:\/\/github.com\/opdavies\/docker-examples\">Docker Examples<\/a> repository.<\/p>\n\n<p>As someone who has worked with one of the Councils who are now using the platform, and was involved in early similar discussions around code reuse and collaboration between Councils, this has been something that I've been keen to try for a while.<\/p>\n\n<p>I was able to get a basic site running after a fresh installation, and was interested to explore how some of the functionality was built. I've recently been looking at implementing similar functionality to LocalGov's alert banners onto a project and will be able to gain some inspiration from that or will look into the LocalGov version could be used.<\/p>\n\n<p>I was happy to find some initial ways to contribute back. I had an error during the installation which I was able to fix and assist with in the <a href=\"https:\/\/www.drupal.org\/project\/localgov\/issues\/3307516#comment-14759989\">LocalGov issue queue on Drupal.org<\/a> by answering a support request, and after spotting a potential issue within the alert banner styling, <a href=\"https:\/\/github.com\/localgovdrupal\/localgov_alert_banner\/pull\/225\">submitted a pull request with a fix<\/a>.<\/p>\n\n<p>I like what the project is doing and agree with its goals, so hopefully I'll get an opportunity to use and contribute more in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e547ef3248356cce84c15e924b59db53",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json b/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json
index f878243c0..5889d987d 100644
--- a/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json
+++ b/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I assume that, like many other Developers, when I started learning front-end development, I wrote normal, plain CSS and later discovered and adopted pre-processors like Less and Sass that added features such as variables and nesting to my stylesheets.<\/p>\n\n<p>This was the case when I first saw what became Tailwind CSS, which were some stylesheets written in Less and ported manually between projects.<\/p>\n\n<p>I remember watching one of those streams, and a fellow viewer suggested PostCSS, which Tailwind CSS would later be written in.<\/p>\n\n<p>PostCSS, a CSS post-processor rather than a pre-processor, has become my preferred way of writing CSS because of Tailwind.<\/p>\n\n<p>When I started using Tailwind in my projects, I was layering it on top of another CSS framework or styles that were written using Less or Sass, so I needed to pre-process them into CSS first and then run PostCSS - essentially running two build steps and adding to the build time.<\/p>\n\n<p>I moved to use PostCSS by default - removing one of the build steps.<\/p>\n\n<p>What I liked about it, as well as the quicker build times, was that I could start with plain CSS and add the extra features I needed. I didn't use all of Sass and Less' features, and now, if I needed nesting or real-time imports, I could add it via a PostCSS plugin or write my own.<\/p>\n\n<p>It's also quick and easy to use, using the PostCSS CLI tool and without more complex tools like Webpack.<\/p>\n\n<p>If you haven't tried PostCSS, I recommend taking a look.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "df6cac0e06b78b0e457c5d6f45c51e64",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json b/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json
index 7c3d95ae0..0188e5c59 100644
--- a/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json
+++ b/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After my lightning talk for NWDUG on automated testing with Drupal, the question was asked how to find time for testing.<\/p>\n\n<p>I've written about whether you need to ask for permission to write tests (you don't), and if you need to estimate tasks, you include the time and effort for writing tests as part of the estimate.<\/p>\n\n<p>As someone who only offers fixed prices for development work and covers all work with a bug-free guarantee, I want to provide well-written, stable and tested software to my customers so I'm not always fixing bugs for free.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e82c83bb7af903eba4da99cc5f669d1d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json b/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json
index 956e05b5c..eaa86a50b 100644
--- a/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json
+++ b/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This is the 600th daily email I've sent to this list, containing my software developments thoughts, tips and updates.<\/p>\n\n<p>I'd like to thank all of the subscribers to the email list, including those who send me replies with their thoughts and opinions on what I write.<\/p>\n\n<p>It's been great to speak to subscribers at in-person events and conferences too, and to hear how some of my thoughts and approaches have helped others.<\/p>\n\n<p>I want to continue growing the email list and the community of subscribers, so please forward any emails that you find useful or insightful, or share them on social media so others can find them, and I'll look forward to getting to 1,000 emails and beyond.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "2c51bf00b628c3b44ddf21e8b65a3ba1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json b/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json
index 5dac2fb30..984b1715c 100644
--- a/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json
+++ b/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>This week, I spoke with Eirik Morland again on the <a href=\"http:\/\/default\/podcast\">Beyond Blocks podcast<\/a> about recent improvements to violinist.io, such as team\/multi-user subscriptions.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/21-eirik-morland-violinist-2\">Listen to the episode now<\/a>.<\/p>\n\n<p>I was great to speak to Eirik again and for him to be the first returning guest on the podcast.<\/p>\n\n<p><a href=\"http:\/\/default\/podcast\/8-eirik-morland-violinist\">Listen to the first episode with Eirik<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9fd4322d892e0fd4d10bb06c6e4377b1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json b/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json
index 5c8bd6a9e..c83efffc2 100644
--- a/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json
+++ b/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/10\/01\/not-all-legacy-code-is-technical-debt\">Technical debt is usually referred to negatively<\/a>, but technical debt isn't always bad.<\/p>\n\n<p>The key thing is to know when and why you're taking on technical debt and when it will be addressed.<\/p>\n\n<p>If you have a goal or deadline to meet, you may decide to take on technical debt to release a feature sooner or a simpler version is released now and a more complex version will come later.<\/p>\n\n<p>I've done this on multi-site Drupal projects before, where I've hard-coded a background image URL as part of a minimum-viable version and made it changeable only when it needed to be - i.e. when the second website was introduced.<\/p>\n\n<p>For the initial version, that approach was good enough and meant we could move forward.<\/p>\n\n<p>The client and I decided to take on this technical debit in advance so we could release it sooner, and we knew when and how we were going to address it and pay it back.<\/p>\n\n<p>This was a good situation, not a bad one.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "bdc8ca32430b3dba88a75ebc24a7def1",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json b/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json
index 771447d23..758dfd66f 100644
--- a/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json
+++ b/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently added a custom <code>wrapper<\/code> class within a Tailwind CSS project.<\/p>\n\n<p>It combined the <code>max-w-6xl<\/code>, <code>mx-auto<\/code> and <code>px-4<\/code> classes using <code>@apply<\/code>, which I rarely use.<\/p>\n\n<p>I added it so we didn't have to add the same classes multiple times.<\/p>\n\n<p>The advantage was it removed some duplication, but people needed to switch from the Twig template to the CSS file to remember what the <code>wrapper<\/code> class did.<\/p>\n\n<p>This undoes some of the advantages of Tailwind CSS and utility classes - the ability to stay in one file without needing to context switching, and easily reading what classes are on an element and immediately knowing what styles are applied to it.<\/p>\n\n<p>Everything is a trade-off.<\/p>\n\n<p>You need to decide which option feels right for you.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "5a98269cbc13fc0777b9ad007d4e327d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json b/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json
index 7729e1e68..4e89f8638 100644
--- a/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json
+++ b/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Which do you do more?<\/p>\n\n<p>Read code or write code?<\/p>\n\n<p>If you include colleagues' code, logs and CI pipeline output, open-source software, books, courses, tutorials, examples, videos, live streams, meetup and conference talks and blog posts (just to think of some), you definitely read more code than you write.<\/p>\n\n<p>Which is why it's important to <a href=\"http:\/\/default\/daily\/2024\/08\/06\/computers-dont-care\">optimise for readability<\/a>.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "ccf8c14e44b64bd2a73b57d71ad81ca6",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fb679f64-e559-4319-9a36-b508bc870415.json b/content/node.fb679f64-e559-4319-9a36-b508bc870415.json
index 31af8628f..ac6ae4610 100644
--- a/content/node.fb679f64-e559-4319-9a36-b508bc870415.json
+++ b/content/node.fb679f64-e559-4319-9a36-b508bc870415.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I've worked on a lot of Drupal projects and there have been times when previous Developers have \"hacked\" Drupal core or contrib modules by editing them to add or change functionality.<\/p>\n\n<p>This is a short-sighted approach, as any changes to third-party code such as Drupal core or contrib modules would be lost when a new version is downloaded.<\/p>\n\n<p>Most of the time, changes can be made within custom code that won't be overwritten and accidentally lost.<\/p>\n\n<p>But in cases where the source code needs to be changed, <a href=\"http:\/\/default\/daily\/2025\/01\/14\/patching-drupal\">you can patch files instead<\/a>.<\/p>\n\n<p>You can commit the patch file to your project to save the changes, but you're responsible for maintaining it and ensuring it applies to any future updates of the code.<\/p>\n\n<p>If you can, commit the changes upstream.<\/p>\n\n<p>Then you won't need to patch files and others will benefit from the contribution.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7ea5ffe7f98df1811de34c43a7caca75",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json b/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json
index d586e2e71..d140ba5e6 100644
--- a/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json
+++ b/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Last week, Mike Karthauser - Senior Software Developer at Huboo - <a href=\"http:\/\/default\/podcast\/7-mike-karthauser-testing-legacy\">joined me on the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>Mike also gave a talk recently at the PHP South West meetup on \"Testing Legacy\" which explained how he works with and tests legacy applications.<\/p>\n\n<p>In the episode, we discuss e-commerce, legacy code, technical debt, automated testing, test-driven development, refactoring, code vs. no-code solutions.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e88c0190551b13355521158f21adce62",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json b/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json
index 9675f0587..d729699b5 100644
--- a/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json
+++ b/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Although I've been using Linux for work computers for a lot longer, a few years ago, I switched from macOS and an Apple MacBook Pro to using Linux full-time on my personal computers.<\/p>\n\n<p>My current daily driver laptop is a Tuxedo InfinityBook that I've installed NixOS on.<\/p>\n\n<p>NixOS, as the name suggests, is a Linux operating system based on the Nix package manager. It has access to the 80,000+ packages in the <code>nixpkgs<\/code> repository and can still install and manage them, but also does a lot more including managing hardware.<\/p>\n\n<p>For user-level configuration, I use Home Manager. I can configure my home directory including user-specific packages and manage my dotfiles, creating files like <code>.gitconfig<\/code> and linking them to the required destination.<\/p>\n\n<p>Home Manager can be a NixOS module or a standalone tool - it can be added to NixOS or installed on any Linux distribution, even in WSL2, so I have the same packages that I need installed on every machine as well as having my dotfiles in the correct place and ready to be used.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9298791e0940f0ff8c997aae39008767",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json b/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json
index 033ab091d..9599a3e04 100644
--- a/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json
+++ b/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>As a continuous learner, I always try to learn and incorporate new things into my development workflow.<\/p>\n\n<p>To keep track of them, I recently started to add them to a TIL.txt file.<\/p>\n\n<p>It's a simple plain-text file in my wiki directory that I append to when I learn something new, and that I can reference in the future.<\/p>\n\n<p>Whether it's a useful Drupal module, some API documentation, a Git command or something else, my TIL file is becoming a collection of small but valuable pieces of information.<\/p>\n\n<p>Here's one I added today:<\/p>\n\n<blockquote>\n  <p>When adding links in Drupal's menu UI, as well as using <code>&lt;nolink&gt;<\/code> to create an empty link, you can also use <code>&lt;button&gt;<\/code> to create a keyboard-accessible button. #drupal<\/p>\n<\/blockquote>\n\n<p>I may have learned this before and forgotten it, but, now it's in my TIL file, I have somewhere to keep it.<\/p>\n\n<p>Always be learning!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "f5036af047c759046d5ac11623982bad",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json b/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json
index 742cb8406..a261b9b9d 100644
--- a/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json
+++ b/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I was working on a project and made a one-line change that updated a single value within an API response.<\/p>\n\n<p>Unexpectedly, it caused a test to fail. The API response returned a 500 status code instead of the expected 201 code.<\/p>\n\n<p>I reverted the change locally and ensured that the test passed again, so I knew it was causing the failure.<\/p>\n\n<h2 id=\"fixing-the-failure\">Fixing the failure<\/h2>\n\n<p>The change was removing a hard-coded part of a URL to a dynamic one, using Drupal's <code>Settings<\/code> class.<\/p>\n\n<p>I was retrieving a value from it, but as there was no value being set within the test, it was returning a null value and causing the 500 error code.<\/p>\n\n<h2 id=\"how-does-the-settings-class-work%3F\">How does the Settings class work?<\/h2>\n\n<p>To fix the test failure, I needed to learn how to set a Settings value within a test.<\/p>\n\n<p>To do this, I looked for and found the test for the Settings class itself. I saw how it was being set there, did the same in my test, fixed the failure and got my test passing again.<\/p>\n\n<h2 id=\"tests-are-living-documentation\">Tests are living documentation<\/h2>\n\n<p>As well as verifying things work when they are written, tests also act as long-term documentation. They can be run at any point to ensure that they still pass and are a reference to other developers on how the code should work.<\/p>\n\n<p>Rather than a Confluence page, a README file or code comments which can become out of date, if a test becomes outdated, it will fail and make developers aware, as well as break any CI pipeline that it runs in.<\/p>\n\n<p>By writing tests, you're ensuring that your code works as expected and documenting it at the same time.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "fd83c2fde1dc9ee8eddd826af1ec88b8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json b/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json
index e3467fad0..970202e58 100644
--- a/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json
+++ b/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>If your team wants or needs to do code reviews, but you don't want it to slow down development, you could implement non-blocking code reviews.<\/p>\n\n<p>Instead of creating a topic branch for a feature or fix, creating a pull or merge request and waiting for it to be reviewed before merging, the commit is merged, and the code is reviewed afterwards.<\/p>\n\n<p>The ticket workflow could look like this:<\/p>\n\n<p>To Do -&gt; Doing -&gt; Merged -&gt; Reviewed -&gt; Tested -&gt; Deployed<\/p>\n\n<p>Or:<\/p>\n\n<p>To Do -&gt; Doing -&gt; Merged -&gt; Deployed -&gt; Tested -&gt; Reviewed<\/p>\n\n<p>The focus is getting the update to production, and the review is deferred.<\/p>\n\n<p>The same CI pipeline rules apply - it must be passing before the code can be deployed, so the same quality checks are run.<\/p>\n\n<p>With this approach, the code is still reviewed, either in the pull or merge request or by the commits on the mainline branch if doing trunk-based development. It's just done later.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9913b8499ed48ffb98e6df624b87e485",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json b/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json
index 174380ad7..98518362a 100644
--- a/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json
+++ b/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Whilst a number of classes that Tailwind CSS generates are single-value utility classes such as <code>.block { display: block; }<\/code> and <code>.relative { position: relative; }<\/code>, it also includes additional things such as <a href=\"https:\/\/tailwindcss.com\/docs\/font-size#setting-the-font-size\">setting a default line height with a font size<\/a>, adding variants for <a href=\"https:\/\/tailwindcss.com\/docs\/hover-focus-and-other-states#styling-based-on-parent-state\">group-hover<\/a> and <a href=\"https:\/\/tailwindcss.com\/docs\/hover-focus-and-other-states#focus-within\">focus-within<\/a> (as well as various other pseudo states).<\/p>\n\n<p>It includes utilities for adding <a href=\"https:\/\/tailwindcss.com\/docs\/space#add-horizontal-space-between-children\">horizontal or vertical space<\/a> or <a href=\"https:\/\/tailwindcss.com\/docs\/divide-style\">styling dividers between elements<\/a>.<\/p>\n\n<p>As well prefixing a class using a screen modifier, such as <code>md:flex<\/code>, you can stack them and set a maximum screen value. For example, <code>md:max-lg:flex<\/code> will only flex between the <code>md<\/code> and <code>lg<\/code> breakpoints.<\/p>\n\n<p>If has official plugins for typography styles, forms, line-clamp (truncating text) and aspect ratios, as well as numerous community plugins and supports arbitrary values if you need them.<\/p>\n\n<p>If you take a look at the <a href=\"https:\/\/tailwindcss.com\/docs\">Tailwind CSS documentation<\/a>, you'll definitely find some interesting and useful things.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e964b8ae6d3a589e9ec7419ffe0d83bf",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json b/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json
index c1948becf..f12aab0c5 100644
--- a/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json
+++ b/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>After writing about <a href=\"http:\/\/default\/daily\/2024\/11\/10\/write-plain-text-files\">making notes in text files<\/a>, I came across <a href=\"https:\/\/youtu.be\/NasPBjSev88?si=nSaCxdtXuznQ_YYb\">a video by Nick Janetakis<\/a> (previous <a href=\"http:\/\/default\/podcast\/12-nick-janetakis-docker\">Beyond Blocks podcast guest<\/a>), showing a simple Bash application he'd written to manage his own plain text notes.<\/p>\n\n<p>I thought I'd try it, but it wasn't available in the nixpkgs store so I wasn't able to install it.<\/p>\n\n<p>Some of the Vim and Neovim plugins I use also aren't available and I've added those to my configuration myself and wanted to do the same for this.<\/p>\n\n<p>Here's the Nix derivation I wrote:<\/p>\n\n<pre><code class=\"nix\">{ pkgs, ... }:\n\npkgs.stdenv.mkDerivation rec {\n  pname = \"notes\";\n  version = \"0.3.0\";\n\n  src = pkgs.fetchFromGitHub {\n    owner = \"nickjj\";\n    repo = \"notes\";\n    rev = \"v${version}\";\n    sha256 = \"gyrsTWPT8w4DsRim3jlbjvpXwX\/y+7SwLaM+3LVOJdU=\";\n  };\n\n  buildInputs = with pkgs; [ bash ];\n\n  installPhase = ''\n    mkdir -p $out\/bin\n    cp $src\/notes $out\/bin\/notes\n    chmod +x $out\/bin\/notes\n  '';\n}\n<\/code><\/pre>\n\n<p>I defined the GitHub repository name and owner, the version number and the required installation steps, and was able to add it to my configuration for use in NixOS and Home Manager.<\/p>\n\n<p>Now, I can type <code>notes<\/code> and easily capture whatever I wanted to document in the appropriate text file..<\/p>\n\n<hr>\n\n<p>FYI, there is an existing <code>notes<\/code> program in nixpkgs, but I overwrote it with Nick's, which is another great thing about using Nix!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3a10f1e0d9065c216ecf8696911485c8",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json b/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json
index 91824e3bc..e39040bb9 100644
--- a/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json
+++ b/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today, I met my new mentee from the Drupal Career Online program.<\/p>\n\n<p><a href=\"http:\/\/default\/daily\/2022\/09\/21\/being-drupal-contribution-mentor\">As well as mentoring at events like DrupalCamps and DrupalCons<\/a>, I enjoy mentoring and working with new Developers going through bootcamps and training programmes like Drupal Career Online, some who are experienced Developers who are learning a new skill, and some who are learning how to code and are taking their first steps into programming.<\/p>\n\n<p>I've talked about <a href=\"http:\/\/default\/daily\/2022-08-28\/how-started-programming\">how I got started programming<\/a>, but as self-taught Developer, it would have been great to have had a mentor to ask questions of, to help me get me started, and to make sure that I was going down the right track and learning the correct things.<\/p>\n\n<p>Maybe this is more applicable these days with more people learning and working from home since COVID-19?<\/p>\n\n<p>Similar to helping mentees at a contribution sprint work towards their first commits to Drupal, it's great to be able to introduce new Developers to a open-source project and community such as Drupal, help develop their skills, and hopefully enable them to get the new job and career that they want.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "51f79d0262a9b959e58c9e60f716db6c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fe407991-a896-410c-9223-51a7ad43d4d2.json b/content/node.fe407991-a896-410c-9223-51a7ad43d4d2.json
index 12f67742e..0a33c9429 100644
--- a/content/node.fe407991-a896-410c-9223-51a7ad43d4d2.json
+++ b/content/node.fe407991-a896-410c-9223-51a7ad43d4d2.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p><a href=\"http:\/\/default\/daily\/2024\/10\/24\/git-stash-is-underrated\">In yesterday's email<\/a> where I wrote about <code>git stash<\/code>, I mentioned the <code>-p<\/code> or <code>--patch<\/code> options.<\/p>\n\n<p>When stashing changes, this allows you to interactively select which changes you want to stash and what you don't.<\/p>\n\n<p>This is supported by other Git commands, including <code>git add<\/code>.<\/p>\n\n<p>I always use <code>git add -p<\/code> when adding changes as it gives me the chance to review them before committing them.<\/p>\n\n<p>If I left any stray comments, debug code, trailing spaces or anything I don't want to commit, I can remove them.<\/p>\n\n<p>If I was working on multiple changes (which I avoid), I can select the appropriate changes and create commits related to each change to keep the history clean and useful.<\/p>\n\n<p>I also use <code>git diff<\/code> and <code>git diff --staged<\/code> to review changes as well as <code>git show<\/code> to review commits.<\/p>\n\n<p>By doing this, I know my commits will be in the best state for others to review now or for me to review if I need to in the future.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "3659e1bc52d94b014aa5474c24745dd2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json b/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json
index 5ab6467f5..53d32c8dc 100644
--- a/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json
+++ b/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>I recently watched a YouTube video of someone working on their software.<\/p>\n\n<p>Everything was working locally, but things were breaking in their CI pipeline.<\/p>\n\n<p>The issue was their CI environment had different versions of the software than the one they were using locally.<\/p>\n\n<p>To get the same results locally and in CI, you need your dependencies to be the same.<\/p>\n\n<p>The same versions of languages, such as PHP and nodejs, and packages like PHPStan, PHPUnit, Jest or eslint.<\/p>\n\n<p>Dependencies should be installed with a package manager that generates a lock file like composer.lock or package-lock.json, so use these versions instead of installing versions globally that may be different.<\/p>\n\n<p>For PHP or nodejs, I'd suggest using Docker or Nix, <a href=\"http:\/\/default\/daily\/2025\/01\/20\/reproducible\">which has its own lock file<\/a>, to make your environment as reproducible and consistent as possible.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "b60d151157449fcffc7aa384bd9a81c7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json b/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json
index 093296e7a..dae7da1b5 100644
--- a/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json
+++ b/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Usually, failing fast in software development refers to errors in code, but another interpretation of this is \"What's the quickest and simplest way to validate or prove an idea\"?<\/p>\n\n<p>If it's fixing a bug or architecting a new feature, what's the simplest thing that can be done to achieve that? It could be writing a technical document or creating a simple proof of concept rather than building the entire feature.<\/p>\n\n<p>If it fails, your sunk cost is low as you've not invested much time, money or energy.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "602cd7fb7a99f9a56adc2966737aa2ab",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json b/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json
index 8780a9e72..c5192ad24 100644
--- a/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json
+++ b/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>When you first start a new application, adding new features is quick and easy.<\/p>\n\n<p>There's no existing code, and everything is written from scratch.<\/p>\n\n<p>As the project progresses, you need to account for and, in some cases, work around the existing code - ensuring the existing functionality continues to work.<\/p>\n\n<p>Even if a sole Developer is working on the project, inconsistencies start to be introduced.<\/p>\n\n<p>One feature was implemented in one way and the next in a different way.<\/p>\n\n<p>One follows a particular design pattern, and the other does not.<\/p>\n\n<p>There is code within the application that isn't used and is no longer needed but hasn't been removed - creating confusion and uncertainty.<\/p>\n\n<p>It can't be removed, just in case it does something and removing it breaks something elsewhere.<\/p>\n\n<p>A task that would have taken hours to complete when the application started now takes days, weeks or longer.<\/p>\n\n<p>Having automated tests, using tools like static analysis, and minimising technical debt helps to minimise this, as does having written technical design documents, ADRs or flow charts to ensure consistency and to document the \"why\" for future Developers.<\/p>\n\n<p>P.S. Is your New Year's resolution to deliver better software faster? <a href=\"http:\/\/default\/team-coaching\">I have availability for team coaching<\/a> starting in January 2024 and can help you avoid issues like this in your applications.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "e858790e868fcce3898b265b59a58a8d",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json b/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json
index c023c0886..a2d368d59 100644
--- a/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json
+++ b/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Open-source projects like Drupal and Symfony have their own published coding standards and conventions.<\/p>\n\n<p>For example, from <a href=\"https:\/\/symfony.com\/doc\/current\/contributing\/code\/standards.html\">Symfony's coding standards<\/a>:<\/p>\n\n<ul>\n<li>Prefix all abstract classes with <code>Abstract<\/code> except PHPUnit <code>*TestCase<\/code>.<\/li>\n<li>Suffix interfaces with <code>Interface<\/code>;<\/li>\n<li>Suffix traits with <code>Trait<\/code>;<\/li>\n<\/ul>\n\n<p>And from <a href=\"https:\/\/www.drupal.org\/docs\/develop\/standards\/php\/php-coding-standards\">Drupal's<\/a>:<\/p>\n\n<ul>\n<li>Use an indent of 2 spaces, with no tabs.<\/li>\n<li>Lines should have no trailing whitespace at the end.<\/li>\n<li>Variables should be named using lowercase, and words should be separated either with uppercase characters (example: <code>$lowerCamelCase<\/code>) or with an underscore (example: <code>$snake_case<\/code>). Be consistent; do not mix camelCase and snake_case variable naming inside a file.<\/li>\n<\/ul>\n\n<p>But what about within custom applications?<\/p>\n\n<p>Do you have your own agreed coding standards and conventions to keep the code consistent?<\/p>\n\n<p>Do you explicitly follow the published coding standards, customise them, or follow something else?<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>Do you know where to put new custom modules, how to name them and what conventions to follow when writing code?<\/p>\n\n<p>Do you know where to add a new stylesheet to your theme?<\/p>\n\n<p>If not, or it's implied, it's worth writing it down and being explicit - either within your project's or company's documentation or publicly.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "dd3142bbe9347b6efceca91355af4c1e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file
diff --git a/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json b/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json
index f091d43d8..6de85b278 100644
--- a/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json
+++ b/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json
@@ -87,14 +87,5 @@
             "processed": "\n          <p>Before fixing <a href=\"http:\/\/default\/daily\/2024\/01\/30\/tdd-doesnt-mean-you-know-everything-upfront\">yesterday's bug<\/a>, because I'd written automated tests, I ran them to ensure they were all passing.<\/p>\n\n<p>Then, I was able to focus solely on adding the new use case - starting with a failing test to replicate the issue and then getting it to pass.<\/p>\n\n<p>Because it was already tested, I didn't need to worry about breaking any other functionality and introducing regressions.<\/p>\n\n<p>When the new test was passing, I could run the whole test suite and ensure they still passed and things continued to work.<\/p>\n\n<p>Without the tests, I'd either need to check everything else manually (which takes time) or worry that something could potentially be broken.<\/p>\n\n<p>Having tests meant I could be confident that the new and existing functionality worked.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "abcc748af8e6e888fd2ed7c8b02d7911",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }
\ No newline at end of file