From 7a52afab5f66deea4c8f715f2fff94a9eaec8c30 Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.uk>
Date: Fri, 30 May 2025 02:14:32 +0100
Subject: [PATCH] tome export

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

diff --git a/config/sync/core.entity_view_display.media.image.media_library.yml b/config/sync/core.entity_view_display.media.image.media_library.yml
index 4f0963667..dee6577e8 100644
--- a/config/sync/core.entity_view_display.media.image.media_library.yml
+++ b/config/sync/core.entity_view_display.media.image.media_library.yml
@@ -20,8 +20,8 @@ content:
     type: image
     label: hidden
     settings:
-      image_style: medium
       image_link: ''
+      image_style: medium
       image_loading:
         attribute: lazy
     third_party_settings: {  }
diff --git a/content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json b/content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json
index 118a25957..b52cd60bd 100644
--- a/content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json
+++ b/content/feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76.json
@@ -67,7 +67,7 @@
     ],
     "item_count": [
         {
-            "value": 820
+            "value": 0
         }
     ]
 }
\ No newline at end of file
diff --git a/content/media.00e90d0a-0d8f-4579-8022-be91f2449149.json b/content/media.00e90d0a-0d8f-4579-8022-be91f2449149.json
index b1d654997..afe1da0bc 100644
--- a/content/media.00e90d0a-0d8f-4579-8022-be91f2449149.json
+++ b/content/media.00e90d0a-0d8f-4579-8022-be91f2449149.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.034364f8-2e16-4ec9-8148-5af2c070c038.json b/content/media.034364f8-2e16-4ec9-8148-5af2c070c038.json
index d570f0b33..6514558d8 100644
--- a/content/media.034364f8-2e16-4ec9-8148-5af2c070c038.json
+++ b/content/media.034364f8-2e16-4ec9-8148-5af2c070c038.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.04897b7d-6d74-491c-935f-65051be149fd.json b/content/media.04897b7d-6d74-491c-935f-65051be149fd.json
index 9f7a1879e..0f82cb868 100644
--- a/content/media.04897b7d-6d74-491c-935f-65051be149fd.json
+++ b/content/media.04897b7d-6d74-491c-935f-65051be149fd.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.0aabd501-3b1b-4352-a5c3-60b01c295311.json b/content/media.0aabd501-3b1b-4352-a5c3-60b01c295311.json
index b9dca3bb5..85863d8ba 100644
--- a/content/media.0aabd501-3b1b-4352-a5c3-60b01c295311.json
+++ b/content/media.0aabd501-3b1b-4352-a5c3-60b01c295311.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.0c37e975-e240-4834-acbb-f9ea19dee13f.json b/content/media.0c37e975-e240-4834-acbb-f9ea19dee13f.json
index e45693a06..6b424eb38 100644
--- a/content/media.0c37e975-e240-4834-acbb-f9ea19dee13f.json
+++ b/content/media.0c37e975-e240-4834-acbb-f9ea19dee13f.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.14a032ba-cd66-4fbf-b45e-5c6851eead80.json b/content/media.14a032ba-cd66-4fbf-b45e-5c6851eead80.json
index 0e9be0a06..9d1e5e322 100644
--- a/content/media.14a032ba-cd66-4fbf-b45e-5c6851eead80.json
+++ b/content/media.14a032ba-cd66-4fbf-b45e-5c6851eead80.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.22221e8c-d072-40ba-a032-b34b0c964a57.json b/content/media.22221e8c-d072-40ba-a032-b34b0c964a57.json
index d653eda01..9813db1c3 100644
--- a/content/media.22221e8c-d072-40ba-a032-b34b0c964a57.json
+++ b/content/media.22221e8c-d072-40ba-a032-b34b0c964a57.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.292a3bd1-0ac0-4f1d-81b7-74bb96be1ee9.json b/content/media.292a3bd1-0ac0-4f1d-81b7-74bb96be1ee9.json
index 2326de0c0..0529b833f 100644
--- a/content/media.292a3bd1-0ac0-4f1d-81b7-74bb96be1ee9.json
+++ b/content/media.292a3bd1-0ac0-4f1d-81b7-74bb96be1ee9.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.29435a22-668d-415d-b8b0-6bc76fd92ef3.json b/content/media.29435a22-668d-415d-b8b0-6bc76fd92ef3.json
index 46a232021..b25941a16 100644
--- a/content/media.29435a22-668d-415d-b8b0-6bc76fd92ef3.json
+++ b/content/media.29435a22-668d-415d-b8b0-6bc76fd92ef3.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.33ccb3cb-1247-45e4-a43b-078d74034320.json b/content/media.33ccb3cb-1247-45e4-a43b-078d74034320.json
index 25619aaa7..a9122feae 100644
--- a/content/media.33ccb3cb-1247-45e4-a43b-078d74034320.json
+++ b/content/media.33ccb3cb-1247-45e4-a43b-078d74034320.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8.json b/content/media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8.json
index a78bac66b..313087734 100644
--- a/content/media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8.json
+++ b/content/media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.3877e696-9620-44de-b941-3ebb42c1244b.json b/content/media.3877e696-9620-44de-b941-3ebb42c1244b.json
index e0c38af86..2f6b2cfa0 100644
--- a/content/media.3877e696-9620-44de-b941-3ebb42c1244b.json
+++ b/content/media.3877e696-9620-44de-b941-3ebb42c1244b.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5.json b/content/media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5.json
index f66c6b0eb..565742997 100644
--- a/content/media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5.json
+++ b/content/media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90.json b/content/media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90.json
index 6633d4c48..22dce8da6 100644
--- a/content/media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90.json
+++ b/content/media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.4aa1060c-6977-4c35-b946-64f4cce860dd.json b/content/media.4aa1060c-6977-4c35-b946-64f4cce860dd.json
index b93e946a6..d4bd0ab3b 100644
--- a/content/media.4aa1060c-6977-4c35-b946-64f4cce860dd.json
+++ b/content/media.4aa1060c-6977-4c35-b946-64f4cce860dd.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.4bec5c04-dd0a-415d-9cd2-9bf76435a983.json b/content/media.4bec5c04-dd0a-415d-9cd2-9bf76435a983.json
index d650c9424..c60984f5a 100644
--- a/content/media.4bec5c04-dd0a-415d-9cd2-9bf76435a983.json
+++ b/content/media.4bec5c04-dd0a-415d-9cd2-9bf76435a983.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.52d13a35-d686-46a7-ac8a-b0e1219e4583.json b/content/media.52d13a35-d686-46a7-ac8a-b0e1219e4583.json
index 76c8374ae..88abc9a46 100644
--- a/content/media.52d13a35-d686-46a7-ac8a-b0e1219e4583.json
+++ b/content/media.52d13a35-d686-46a7-ac8a-b0e1219e4583.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.6cad1384-e45d-48f9-86b4-c8f9efac72d6.json b/content/media.6cad1384-e45d-48f9-86b4-c8f9efac72d6.json
index d88fda820..a18d34e2f 100644
--- a/content/media.6cad1384-e45d-48f9-86b4-c8f9efac72d6.json
+++ b/content/media.6cad1384-e45d-48f9-86b4-c8f9efac72d6.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.85934919-d843-4503-93e6-e871644bb46c.json b/content/media.85934919-d843-4503-93e6-e871644bb46c.json
index 726c755c3..c988b50a6 100644
--- a/content/media.85934919-d843-4503-93e6-e871644bb46c.json
+++ b/content/media.85934919-d843-4503-93e6-e871644bb46c.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.883096d9-5f02-445f-8db9-ad75362da9cc.json b/content/media.883096d9-5f02-445f-8db9-ad75362da9cc.json
index e0024dcbc..fac63568e 100644
--- a/content/media.883096d9-5f02-445f-8db9-ad75362da9cc.json
+++ b/content/media.883096d9-5f02-445f-8db9-ad75362da9cc.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.9d524fe7-830a-475f-b131-d4a0c874102e.json b/content/media.9d524fe7-830a-475f-b131-d4a0c874102e.json
index 9b7400b5d..5dce693e3 100644
--- a/content/media.9d524fe7-830a-475f-b131-d4a0c874102e.json
+++ b/content/media.9d524fe7-830a-475f-b131-d4a0c874102e.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.a45a3074-779f-4238-b97c-d4d7146f8a59.json b/content/media.a45a3074-779f-4238-b97c-d4d7146f8a59.json
index 005ae9ba2..94b777af3 100644
--- a/content/media.a45a3074-779f-4238-b97c-d4d7146f8a59.json
+++ b/content/media.a45a3074-779f-4238-b97c-d4d7146f8a59.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.a587aa47-64ee-4454-a822-da2a3fd44147.json b/content/media.a587aa47-64ee-4454-a822-da2a3fd44147.json
index c2af51d0c..039aa563d 100644
--- a/content/media.a587aa47-64ee-4454-a822-da2a3fd44147.json
+++ b/content/media.a587aa47-64ee-4454-a822-da2a3fd44147.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab.json b/content/media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab.json
index 32521fadf..7ea5bf921 100644
--- a/content/media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab.json
+++ b/content/media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2.json b/content/media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2.json
index 929820bae..61474456a 100644
--- a/content/media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2.json
+++ b/content/media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0.json b/content/media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0.json
index 5a4a20234..5b7c1f93b 100644
--- a/content/media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0.json
+++ b/content/media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.f18dde63-4721-4837-8c16-4449ef5611ee.json b/content/media.f18dde63-4721-4837-8c16-4449ef5611ee.json
index 8c4b61099..ebe7c7af0 100644
--- a/content/media.f18dde63-4721-4837-8c16-4449ef5611ee.json
+++ b/content/media.f18dde63-4721-4837-8c16-4449ef5611ee.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.f8784685-be7e-48b8-9c86-f205c7e9d981.json b/content/media.f8784685-be7e-48b8-9c86-f205c7e9d981.json
index 14767e8cc..8a526f046 100644
--- a/content/media.f8784685-be7e-48b8-9c86-f205c7e9d981.json
+++ b/content/media.f8784685-be7e-48b8-9c86-f205c7e9d981.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/media.f9a0267d-cec0-44fd-abf6-fe569cde3b19.json b/content/media.f9a0267d-cec0-44fd-abf6-fe569cde3b19.json
index ad016f11e..1a1aaaddb 100644
--- a/content/media.f9a0267d-cec0-44fd-abf6-fe569cde3b19.json
+++ b/content/media.f9a0267d-cec0-44fd-abf6-fe569cde3b19.json
@@ -43,8 +43,8 @@
         {
             "alt": "",
             "title": null,
-            "width": 180,
-            "height": 180,
+            "width": null,
+            "height": null,
             "target_type": "file",
             "target_uuid": "565ea6d1-39f8-4179-979e-f012fcb264af"
         }
diff --git a/content/meta/index.json b/content/meta/index.json
index 834116345..93ee2df97 100644
--- a/content/meta/index.json
+++ b/content/meta/index.json
@@ -14,6 +14,12 @@
     "crop.c54aafc0-df7d-4e4a-a3eb-4d1a957c8b18": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
+    "crop.49e2f9ad-4739-478a-ae41-332d79fde879": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "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"
     ],
@@ -32,14 +38,252 @@
     "file.c92327fa-f288-445e-8441-b9506933d6b8": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
-    "menu_link_content.daf937a0-f3cf-485d-aba7-b31832450637": [],
-    "menu_link_content.0aba67d1-f37a-4b10-80ec-b18f02eafc66": [],
-    "menu_link_content.b541a408-2a31-451a-9ef4-88d30a6bc243": [],
-    "menu_link_content.5334a2f4-3e6a-4575-b29a-cc2eb9cf3af3": [],
-    "menu_link_content.b8a5229a-dc0f-48be-9052-25b7077ecb2b": [],
-    "menu_link_content.b71a03e9-5723-45e1-81ef-a4b2fbbc2eba": [],
-    "menu_link_content.e89b24d4-9d98-4b22-a603-23aaabd19f0b": [],
+    "file.85ac0ba1-80de-478e-a3f4-9bd1f003348e": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.565ea6d1-39f8-4179-979e-f012fcb264af": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.7f65da75-c4fb-4e12-920f-b3538cacf3b2": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.5f4a9e0d-57e0-4e84-b8ba-9b641955c102": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.4f4b0b2d-c1bf-4a6b-a234-9f1fd72bd110": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.843cc6fb-9e67-43c7-96a2-a566b2e6c0f2": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.3c2c7139-187d-4b24-b9af-6b8656d96ce3": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.07bc5ab4-a33f-404f-8686-da4a9f2bc910": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.72d32f1d-6662-45ed-bb8f-efd28bcc3aef": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.c4807834-918a-4421-9177-5a1f95900ca5": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.7cea60ab-cd20-42cb-b995-fa470fc393f5": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.67a1977e-b9e3-45ad-bddf-5058a80414f9": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.8c712d15-f3f1-463f-9cbb-f4338db22a27": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.2b87b13a-05e0-4f03-9760-517085f673ff": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.40f8d8c1-1f63-4180-81c0-42edd8e84a9f": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.1ffeab5a-4395-4ee9-bf05-bac394a588fd": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.45eba0ef-3846-4f3b-8147-d0ad5509c665": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.21385f14-1910-4388-bf1a-200964fa73b1": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.e65a89ea-4eac-4562-9156-e3487cf1cbdd": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.06f032ff-a1bc-4f98-9964-40c7278e885f": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.943c945f-8081-4bfd-92f9-302f5ddaf90f": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.32c08f1a-4b4d-4ef7-b1eb-08a8cc9871dc": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.a6e24803-104a-4b74-b016-242b77185b9e": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.4084d1f3-6c8c-4976-86f7-68ea491ee3bf": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.4a9d5a98-845c-45d1-98ca-2cd038d99326": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.b809880e-834b-4a64-8051-6a96e207f11e": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.bc1169a7-d6b0-46d8-ae22-d921682b88f6": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.a2680e95-a118-48e8-8a89-fc608326c0e0": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.32935ed5-d928-413e-824c-3c44e5ccd5d8": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.49873c79-708c-4e0c-bc4c-adde4414165e": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "file.b17eae76-e417-4f22-8290-da16366ebb24": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "media.883096d9-5f02-445f-8db9-ad75362da9cc": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.b17eae76-e417-4f22-8290-da16366ebb24"
+    ],
+    "media.292a3bd1-0ac0-4f1d-81b7-74bb96be1ee9": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.7f65da75-c4fb-4e12-920f-b3538cacf3b2"
+    ],
+    "media.0c37e975-e240-4834-acbb-f9ea19dee13f": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.5f4a9e0d-57e0-4e84-b8ba-9b641955c102"
+    ],
+    "media.f9a0267d-cec0-44fd-abf6-fe569cde3b19": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.4f4b0b2d-c1bf-4a6b-a234-9f1fd72bd110"
+    ],
+    "media.a45a3074-779f-4238-b97c-d4d7146f8a59": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.843cc6fb-9e67-43c7-96a2-a566b2e6c0f2"
+    ],
+    "media.33ccb3cb-1247-45e4-a43b-078d74034320": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.3c2c7139-187d-4b24-b9af-6b8656d96ce3"
+    ],
+    "media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.07bc5ab4-a33f-404f-8686-da4a9f2bc910"
+    ],
+    "media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.72d32f1d-6662-45ed-bb8f-efd28bcc3aef"
+    ],
+    "media.f18dde63-4721-4837-8c16-4449ef5611ee": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.c4807834-918a-4421-9177-5a1f95900ca5"
+    ],
+    "media.9d524fe7-830a-475f-b131-d4a0c874102e": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.7cea60ab-cd20-42cb-b995-fa470fc393f5"
+    ],
+    "media.4bec5c04-dd0a-415d-9cd2-9bf76435a983": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.67a1977e-b9e3-45ad-bddf-5058a80414f9"
+    ],
+    "media.29435a22-668d-415d-b8b0-6bc76fd92ef3": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.8c712d15-f3f1-463f-9cbb-f4338db22a27"
+    ],
+    "media.0aabd501-3b1b-4352-a5c3-60b01c295311": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.2b87b13a-05e0-4f03-9760-517085f673ff"
+    ],
+    "media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.40f8d8c1-1f63-4180-81c0-42edd8e84a9f"
+    ],
+    "media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.1ffeab5a-4395-4ee9-bf05-bac394a588fd"
+    ],
+    "media.14a032ba-cd66-4fbf-b45e-5c6851eead80": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.45eba0ef-3846-4f3b-8147-d0ad5509c665"
+    ],
+    "media.6cad1384-e45d-48f9-86b4-c8f9efac72d6": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.21385f14-1910-4388-bf1a-200964fa73b1"
+    ],
+    "media.52d13a35-d686-46a7-ac8a-b0e1219e4583": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.e65a89ea-4eac-4562-9156-e3487cf1cbdd"
+    ],
+    "media.3877e696-9620-44de-b941-3ebb42c1244b": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.06f032ff-a1bc-4f98-9964-40c7278e885f"
+    ],
+    "media.04897b7d-6d74-491c-935f-65051be149fd": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.943c945f-8081-4bfd-92f9-302f5ddaf90f"
+    ],
+    "media.4aa1060c-6977-4c35-b946-64f4cce860dd": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.32c08f1a-4b4d-4ef7-b1eb-08a8cc9871dc"
+    ],
+    "media.00e90d0a-0d8f-4579-8022-be91f2449149": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.a6e24803-104a-4b74-b016-242b77185b9e"
+    ],
+    "media.034364f8-2e16-4ec9-8148-5af2c070c038": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.4084d1f3-6c8c-4976-86f7-68ea491ee3bf"
+    ],
+    "media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.4a9d5a98-845c-45d1-98ca-2cd038d99326"
+    ],
+    "media.a587aa47-64ee-4454-a822-da2a3fd44147": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.b809880e-834b-4a64-8051-6a96e207f11e"
+    ],
+    "media.85934919-d843-4503-93e6-e871644bb46c": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.bc1169a7-d6b0-46d8-ae22-d921682b88f6"
+    ],
+    "media.22221e8c-d072-40ba-a032-b34b0c964a57": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.a2680e95-a118-48e8-8a89-fc608326c0e0"
+    ],
+    "media.f8784685-be7e-48b8-9c86-f205c7e9d981": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.32935ed5-d928-413e-824c-3c44e5ccd5d8"
+    ],
+    "media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
+        "file.49873c79-708c-4e0c-bc4c-adde4414165e"
+    ],
     "menu_link_content.6ca73647-c2e0-45c6-95aa-c96ff3b17c44": [],
+    "menu_link_content.e89b24d4-9d98-4b22-a603-23aaabd19f0b": [],
+    "menu_link_content.b71a03e9-5723-45e1-81ef-a4b2fbbc2eba": [],
+    "menu_link_content.b8a5229a-dc0f-48be-9052-25b7077ecb2b": [],
+    "menu_link_content.5334a2f4-3e6a-4575-b29a-cc2eb9cf3af3": [],
+    "menu_link_content.b541a408-2a31-451a-9ef4-88d30a6bc243": [],
+    "menu_link_content.0aba67d1-f37a-4b10-80ec-b18f02eafc66": [],
+    "menu_link_content.daf937a0-f3cf-485d-aba7-b31832450637": [],
     "node.00e9d07f-479d-4a4d-8a13-ad6cf44c0454": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
@@ -181,6 +425,42 @@
     "node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
     ],
+    "node.1579b5cf-889e-4a7b-98a7-59918359def9": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.45636e82-61b1-4298-a28c-34f139b9a559": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.fbf99373-91c3-420e-af68-6ccda249f639": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.d5d38a64-f226-42e0-8691-6c1b128435bf": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.4c9fd2d9-307a-43a1-8993-d422261eabd7": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.38535020-c00e-4720-8534-73346ff7cb0d": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.0e1fbc03-a045-4ca4-8925-69e39b67d893": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.298d7816-0b4a-449e-a78d-fcf973f24bf0": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.22f6723d-c781-4548-a2cf-3b642e91b4ad": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "node.81676cf3-0b30-4619-a922-12ff3e16ba76": [
+        "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"
@@ -3461,12 +3741,6 @@
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
         "feeds_feed.90c85284-7ca8-4074-9178-97ff8384fe76"
     ],
-    "node.1579b5cf-889e-4a7b-98a7-59918359def9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "node.45636e82-61b1-4298-a28c-34f139b9a559": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
     "node.530c4270-2e61-4e03-af91-4969a5ac9b01": [
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
         "file.c92327fa-f288-445e-8441-b9506933d6b8"
@@ -3487,8 +3761,276 @@
         "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
         "file.bf5bcd01-5c93-46fb-897d-5dc69c3cbc7f"
     ],
-    "node.fbf99373-91c3-420e-af68-6ccda249f639": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    "node.b71f8b90-7636-4e13-b31a-e7ba42eb94f7": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "file.85ac0ba1-80de-478e-a3f4-9bd1f003348e"
+    ],
+    "node.7fe05b4e-044a-4426-8fce-538781450976": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.883096d9-5f02-445f-8db9-ad75362da9cc",
+        "taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47"
+    ],
+    "node.13daae68-e5f9-4295-a6ff-908aae12f012": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.0c37e975-e240-4834-acbb-f9ea19dee13f",
+        "taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af",
+        "taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47"
+    ],
+    "node.773bab66-561e-4954-9689-a7d817cbbb35": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.f9a0267d-cec0-44fd-abf6-fe569cde3b19",
+        "taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7"
+    ],
+    "node.deefc5f9-12d4-46a5-a647-4522de0e5e63": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.a45a3074-779f-4238-b97c-d4d7146f8a59",
+        "taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9"
+    ],
+    "node.5c296c46-30d9-4ec8-93e4-837330c833b0": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.33ccb3cb-1247-45e4-a43b-078d74034320",
+        "taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43"
+    ],
+    "node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8",
+        "taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d"
+    ],
+    "node.487866ab-71b2-407e-9911-c6207dbccd80": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2",
+        "taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf"
+    ],
+    "node.d0cc3427-9501-4857-93e4-d2153b18ebe5": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.f18dde63-4721-4837-8c16-4449ef5611ee",
+        "taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b"
+    ],
+    "node.19efa1df-9e8a-4c65-b1e8-55248ac520ed": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.9d524fe7-830a-475f-b131-d4a0c874102e",
+        "taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6"
+    ],
+    "node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.4bec5c04-dd0a-415d-9cd2-9bf76435a983",
+        "taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32"
+    ],
+    "node.058eb05f-cec1-43bd-a4e1-0b09630662e9": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.29435a22-668d-415d-b8b0-6bc76fd92ef3",
+        "taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f"
+    ],
+    "node.7fab23fc-6ea7-432b-86da-ec32dfc008ab": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.0aabd501-3b1b-4352-a5c3-60b01c295311",
+        "taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2"
+    ],
+    "node.84decda9-d30b-4cd0-b468-937a7e47776b": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5",
+        "taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2"
+    ],
+    "node.6ed95c44-c301-4f53-8f87-6d33de758f7e": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0",
+        "taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e"
+    ],
+    "node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.14a032ba-cd66-4fbf-b45e-5c6851eead80",
+        "taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980"
+    ],
+    "node.33ea9079-3c84-410b-b568-eeff8c70a41f": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.6cad1384-e45d-48f9-86b4-c8f9efac72d6",
+        "taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6"
+    ],
+    "node.eedbf764-01b3-48e8-9de4-b8d23caa8efd": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.52d13a35-d686-46a7-ac8a-b0e1219e4583",
+        "taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df"
+    ],
+    "node.8a979843-907c-49d9-abaf-a21b0432e648": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.3877e696-9620-44de-b941-3ebb42c1244b",
+        "taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7"
+    ],
+    "node.1d491da6-0523-4709-aa35-17df110f5506": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.04897b7d-6d74-491c-935f-65051be149fd",
+        "taxonomy_term.c0470b91-e700-4602-9e93-07705681d679"
+    ],
+    "node.6dac7a82-aecd-4bd2-9303-0383d77f4a88": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.4aa1060c-6977-4c35-b946-64f4cce860dd",
+        "taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9"
+    ],
+    "node.62d158a4-17c2-488c-990c-d852eb7e3f7c": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.00e90d0a-0d8f-4579-8022-be91f2449149",
+        "taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b"
+    ],
+    "node.5a8df3bf-d501-47ae-978b-ef6219c68c60": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.034364f8-2e16-4ec9-8148-5af2c070c038",
+        "taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538"
+    ],
+    "node.5cc36ded-e301-49de-88eb-c218c980707f": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab",
+        "taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b"
+    ],
+    "node.9e094927-a767-437b-b3b7-90a5bea35da0": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.a587aa47-64ee-4454-a822-da2a3fd44147",
+        "taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4"
+    ],
+    "node.d473b252-b668-40bc-b744-68ea259702fc": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.85934919-d843-4503-93e6-e871644bb46c",
+        "taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95"
+    ],
+    "node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.22221e8c-d072-40ba-a032-b34b0c964a57",
+        "taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d"
+    ],
+    "node.16846795-5fd0-4a67-a080-edfaa8e20cd8": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.f8784685-be7e-48b8-9c86-f205c7e9d981",
+        "taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09"
+    ],
+    "node.25347778-fdbf-4a8e-80f9-2d7e655391fe": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
+        "media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90",
+        "taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6"
+    ],
+    "path_alias.799ccead-b473-474a-9131-d0c36db8c194": [
+        "node.00e9d07f-479d-4a4d-8a13-ad6cf44c0454"
+    ],
+    "path_alias.458f6c04-7cf5-4011-a386-a240d552ad0e": [
+        "node.720227fb-2539-4f99-8a3a-097ad7fbea5b"
+    ],
+    "path_alias.e16afff1-7e4f-486d-8c15-9daaa90ae2c2": [
+        "node.76b39ff6-103e-4ebf-b4c2-de6c369a7a65"
+    ],
+    "path_alias.c3a908a9-70cd-45f8-b1b8-e9889c8ac645": [
+        "node.d60d49f4-3d4f-4dd1-bcb8-1e75f74032c1"
+    ],
+    "path_alias.46cf208b-0fc4-429f-9787-fbdf70da76be": [
+        "node.91228b97-e4df-43c9-8f1e-6aaa6998b6c7"
+    ],
+    "path_alias.05c8d8d4-a8c1-4956-9348-80367df00108": [
+        "node.872ee6d1-ddeb-4b85-a443-c5cf2d9f864d"
+    ],
+    "path_alias.e64f35a6-b476-448c-8043-171e772aabca": [
+        "node.00cbe903-afbd-4074-867d-4499873f3ec9"
+    ],
+    "path_alias.f8a5a912-19db-4c22-9157-4583e9f356c8": [
+        "node.8db50e55-72a9-4957-97c7-8a5ae127eeaa"
+    ],
+    "path_alias.1df69675-92fc-4238-b3ee-57263243e395": [
+        "node.e83b2be0-560c-43a0-b22c-4d11898e2591"
+    ],
+    "path_alias.b7908c26-3b98-444f-968c-7cb5be66d88c": [
+        "node.11ff7528-5853-4557-bab4-190e6edab4a5"
+    ],
+    "path_alias.c0bde3ce-d3c3-4bd6-b2a1-064b535ca308": [
+        "node.bbdaeb7f-4154-4919-a1e6-1dcc33c3ac87"
+    ],
+    "path_alias.5f139ec9-b1ab-4613-b00d-19cc03fd1d6f": [
+        "node.b3371f53-7540-46da-b9dd-0247c0042c60"
+    ],
+    "path_alias.be37fc6c-bf65-4b4d-b652-84d163b0d666": [
+        "node.67e872b0-38b9-4bf8-9ca2-82b6e2cd488b"
+    ],
+    "path_alias.5aa1fdcc-aaaf-4b96-98d9-a76945ca4d3b": [
+        "node.d31d81e0-5591-424a-b89f-e38a0b35ff25"
+    ],
+    "path_alias.24b6f8bc-e00b-498e-9a03-754f85e4ee0b": [
+        "node.7646b8ce-4388-4b19-9ef6-73439442c359"
+    ],
+    "path_alias.e7160989-275c-4054-a4f2-2c0efce42985": [
+        "node.3e86a978-80ed-4e0d-9e93-93001f1d52ad"
+    ],
+    "path_alias.2bea11d0-9783-4f4d-b8af-cb2ae20ea43b": [
+        "node.dbb09dcc-ad50-4ec0-9567-1d799292107f"
+    ],
+    "path_alias.289c6203-bf95-4f18-a285-482337c510b7": [
+        "node.9478a73a-b12b-426e-abcf-f007d544d244"
+    ],
+    "path_alias.8c4d45a2-b6d5-4567-bf3e-220bd8bfb393": [
+        "node.29a792d3-f83c-4802-95cf-ce39109dd96a"
+    ],
+    "path_alias.dac815a5-e23f-4f3b-a249-b9391d5ed4d0": [
+        "node.2b4c5ae7-3754-44ae-a0c0-40a24a64fc2f"
+    ],
+    "path_alias.37bcce63-122c-4aa3-ade9-fa96b9f24e22": [
+        "node.67967073-f8ca-4253-b806-a570806f18ee"
+    ],
+    "path_alias.a1b87f39-0fbb-46dc-b81a-1e0f11f942ac": [
+        "node.d46b09ba-3534-422c-b897-05619490a269"
+    ],
+    "path_alias.abdc82a8-fbb9-412c-bb91-e0ca0566e8ef": [
+        "node.7cc21bad-5b2e-450c-86b4-19b79f4b21c1"
+    ],
+    "path_alias.0ccd4c97-8c36-4030-bd02-d1a24eace52b": [
+        "node.4eec6b8d-0376-4b5f-84a9-cdc2fca2395e"
+    ],
+    "path_alias.603fe8b8-cabd-44e3-8914-949f8d58f59a": [
+        "node.4229ad32-8ef7-4315-ad6d-c7fea0157f7f"
+    ],
+    "path_alias.56615246-6c0a-4995-b2e5-05410aeb9f85": [
+        "node.6d9734c9-2165-4b6c-8617-1dcb5af116bb"
+    ],
+    "path_alias.9a227a05-5717-4b6a-9eb8-3ab05d1e8077": [
+        "node.fd961f16-2935-474b-af7e-99885bd38a5b"
+    ],
+    "path_alias.193a146a-4b87-4cb7-8139-f612fb3656ef": [
+        "node.4d1aa9fa-091a-425a-941a-102e6f17e768"
+    ],
+    "path_alias.5a0eee15-1d56-43d0-8539-3bd406e48749": [
+        "node.ef95ec60-773e-44ce-a0aa-5e009112f8f4"
+    ],
+    "path_alias.3c27c0fe-1a53-4073-92c0-edded050d127": [
+        "node.3424c5e4-6b60-4ba4-b9f1-37b964cbcb91"
+    ],
+    "path_alias.1013ac37-0c26-4453-9529-d9678bea6bb4": [
+        "node.c88b1c71-9bf2-4055-820b-6f9377ed31af"
+    ],
+    "path_alias.3deea84a-b1d1-4a20-8fe6-ce809fb116c4": [
+        "node.32df4c3d-0719-49eb-8dde-0d04ea746de8"
+    ],
+    "path_alias.b7e67401-20ff-46b7-89e6-0022c6bd1e35": [
+        "node.e2353e18-0a03-4448-a8db-728dbd4146e8"
+    ],
+    "path_alias.224b7887-6730-4987-b23c-7b4f61f1b549": [
+        "node.9b87c047-0a3b-4a66-8ea8-f8a1981f686c"
+    ],
+    "path_alias.e2b23961-024e-4223-94db-5a9cb626bcc3": [
+        "node.28e7dab2-8990-43ca-8f69-16608eae051f"
+    ],
+    "path_alias.bf67d703-6cbb-4272-b81c-2ab8ca1dd96b": [
+        "node.478e9266-742d-4c7d-92fb-0f6797b0da9e"
+    ],
+    "path_alias.76645bbb-c487-499f-a485-e8a3cd431539": [
+        "node.261e86dc-ffbb-4274-a61a-8ddd9fadff5e"
+    ],
+    "path_alias.25233bfe-544a-4842-87d7-afcd27779476": [
+        "node.622123fa-d820-4372-a68d-a049f9ceb348"
+    ],
+    "path_alias.5f1f98b4-b422-4633-ba2d-1036ad9bbefb": [
+        "node.f9b17889-2531-4e1e-b120-a0f0e27fed83"
+    ],
+    "path_alias.cf11b483-34f2-4e6b-9e28-75ea679c1a55": [
+        "node.93689f20-8355-413a-8c23-5096802fbd65"
+    ],
+    "path_alias.d266b885-54c2-4d7a-89a3-828fb7f8ff88": [
+        "node.209ce05d-6831-47b2-b069-c4e31f698885"
+    ],
+    "path_alias.1ccfde63-a91b-48aa-a890-5a5891815d0d": [
+        "node.5a9c3a99-84f4-4dc3-8ddc-d05e0469f9b9"
     ],
     "path_alias.28c02053-6cf9-4e1f-bed3-163c28e2ea7b": [
         "node.00e9d07f-479d-4a4d-8a13-ad6cf44c0454"
@@ -3871,6 +4413,39 @@
     "path_alias.53c80a2f-365c-403f-8e07-5f82311df5a4": [
         "node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1"
     ],
+    "path_alias.987be1d9-1ccd-4a4e-898e-207172cd39a0": [
+        "node.1579b5cf-889e-4a7b-98a7-59918359def9"
+    ],
+    "path_alias.6f154ca6-12e7-47fc-893e-a5c094487f21": [
+        "node.45636e82-61b1-4298-a28c-34f139b9a559"
+    ],
+    "path_alias.8941a0dc-4d03-4a42-a647-8d20898ac224": [
+        "node.d5d38a64-f226-42e0-8691-6c1b128435bf"
+    ],
+    "path_alias.3a7a13f5-0525-4037-a9a1-c9be77e0bd6a": [
+        "node.4c9fd2d9-307a-43a1-8993-d422261eabd7"
+    ],
+    "path_alias.9bbfe0c4-7942-40e3-8e83-eaa5df854298": [
+        "node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e"
+    ],
+    "path_alias.c6c581ce-f776-47a6-ab45-1e56e1593594": [
+        "node.38535020-c00e-4720-8534-73346ff7cb0d"
+    ],
+    "path_alias.4b0cf0d7-3421-4559-a405-c016e11c1970": [
+        "node.0e1fbc03-a045-4ca4-8925-69e39b67d893"
+    ],
+    "path_alias.950ec3e2-a41f-4da8-a54e-456156941219": [
+        "node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13"
+    ],
+    "path_alias.b1705270-e583-405b-a7b4-6ae30059706f": [
+        "node.298d7816-0b4a-449e-a78d-fcf973f24bf0"
+    ],
+    "path_alias.9d87323f-c40a-4737-943e-c8f48cb37bd3": [
+        "node.22f6723d-c781-4548-a2cf-3b642e91b4ad"
+    ],
+    "path_alias.678f29fc-1b63-4450-8689-7d0949a2779b": [
+        "node.81676cf3-0b30-4619-a922-12ff3e16ba76"
+    ],
     "path_alias.ff7cee19-0667-4d4e-a7b7-41e45ab6b622": [
         "node.ca7093b6-288d-4326-b755-cc96e0c262dc"
     ],
@@ -6331,12 +6906,125 @@
     "path_alias.ce6b9ad5-376f-4bdd-b650-2d15d190f1b9": [
         "node.5c793601-f8ea-470d-8c64-3e669226e651"
     ],
-    "path_alias.987be1d9-1ccd-4a4e-898e-207172cd39a0": [
-        "node.1579b5cf-889e-4a7b-98a7-59918359def9"
+    "path_alias.94eab8eb-be76-4fad-afac-3e50e3d1e1b5": [
+        "node.7fe05b4e-044a-4426-8fce-538781450976"
     ],
-    "path_alias.6f154ca6-12e7-47fc-893e-a5c094487f21": [
-        "node.45636e82-61b1-4298-a28c-34f139b9a559"
+    "path_alias.0e885b9c-0124-4521-a450-b4702c51a5ba": [
+        "node.13daae68-e5f9-4295-a6ff-908aae12f012"
     ],
+    "path_alias.be39dc41-6c80-4be3-ac25-f20011d65c54": [
+        "node.773bab66-561e-4954-9689-a7d817cbbb35"
+    ],
+    "path_alias.84fe08d5-7a51-4a66-be94-3b0eda19e962": [
+        "node.deefc5f9-12d4-46a5-a647-4522de0e5e63"
+    ],
+    "path_alias.7589fe0f-4e02-4640-b317-4b659a8702ea": [
+        "node.5c296c46-30d9-4ec8-93e4-837330c833b0"
+    ],
+    "path_alias.89855544-a29f-4a69-9717-de7dd29ee92c": [
+        "node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0"
+    ],
+    "path_alias.bb03c9a3-1968-4fe2-8362-fa68ed28e5ea": [
+        "node.487866ab-71b2-407e-9911-c6207dbccd80"
+    ],
+    "path_alias.40cfe58e-9ab3-4fc7-8544-8faab73d810d": [
+        "node.d0cc3427-9501-4857-93e4-d2153b18ebe5"
+    ],
+    "path_alias.fbca963d-93c3-486f-b9d9-c2092000c188": [
+        "node.19efa1df-9e8a-4c65-b1e8-55248ac520ed"
+    ],
+    "path_alias.094decee-bee6-4953-9834-9eff4207a802": [
+        "node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b"
+    ],
+    "path_alias.ee21faa4-0c25-40b1-846d-4b3bf2b0c353": [
+        "node.058eb05f-cec1-43bd-a4e1-0b09630662e9"
+    ],
+    "path_alias.8b415f79-73dd-4d21-b0e7-b9b74cf324ba": [
+        "node.7fab23fc-6ea7-432b-86da-ec32dfc008ab"
+    ],
+    "path_alias.c33e1b1a-6fed-4ca8-9241-5d1eefa6f7e7": [
+        "node.84decda9-d30b-4cd0-b468-937a7e47776b"
+    ],
+    "path_alias.ef8eecc0-5a61-48de-b30c-d15e48459249": [
+        "node.6ed95c44-c301-4f53-8f87-6d33de758f7e"
+    ],
+    "path_alias.1f043e2e-99c3-4a6b-8c85-7f8cb652bb71": [
+        "node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18"
+    ],
+    "path_alias.f83c3ec3-ea20-4e20-883c-8aa2bd09126f": [
+        "node.33ea9079-3c84-410b-b568-eeff8c70a41f"
+    ],
+    "path_alias.4623a53c-319d-4bb7-ae65-5a8eed2d4fc5": [
+        "node.eedbf764-01b3-48e8-9de4-b8d23caa8efd"
+    ],
+    "path_alias.103e1a16-2b12-430e-9946-0f77e25b4e11": [
+        "node.8a979843-907c-49d9-abaf-a21b0432e648"
+    ],
+    "path_alias.2c981801-8454-4517-81c7-f8b9cbfecc36": [
+        "node.1d491da6-0523-4709-aa35-17df110f5506"
+    ],
+    "path_alias.705f9177-84d1-407b-9657-01fe314d52e1": [
+        "node.6dac7a82-aecd-4bd2-9303-0383d77f4a88"
+    ],
+    "path_alias.bee3f597-8c0d-4ad3-9ac6-0729a0356302": [
+        "node.62d158a4-17c2-488c-990c-d852eb7e3f7c"
+    ],
+    "path_alias.eba0fc97-ab0a-4059-aee4-f8195f8bc41b": [
+        "node.5a8df3bf-d501-47ae-978b-ef6219c68c60"
+    ],
+    "path_alias.9b61fa71-0eef-4864-86bc-eb99dc31ab30": [
+        "node.5cc36ded-e301-49de-88eb-c218c980707f"
+    ],
+    "path_alias.a3d49a94-32b6-4288-8b7d-ea072ec7e0d4": [
+        "node.9e094927-a767-437b-b3b7-90a5bea35da0"
+    ],
+    "path_alias.0b47c099-a0e8-49bb-b94b-8a0377a2882a": [
+        "node.d473b252-b668-40bc-b744-68ea259702fc"
+    ],
+    "path_alias.b8ad3cf0-b3ad-44b0-93b5-c12d76ff935d": [
+        "node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191"
+    ],
+    "path_alias.1a1125ef-0203-4471-a376-e6322b8c0511": [
+        "node.16846795-5fd0-4a67-a080-edfaa8e20cd8"
+    ],
+    "path_alias.e07a9581-a98a-4acf-b878-492b260fde28": [
+        "node.25347778-fdbf-4a8e-80f9-2d7e655391fe"
+    ],
+    "redirect.bfacd4d2-3e91-4845-bec5-4f6d7558788d": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "redirect.8f837f21-5631-490d-b4f4-a8cc65cfafae": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "shortcut.91b0a545-47e6-47f6-8c91-312400be7975": [],
+    "shortcut.45ca7a46-646c-4ae4-83ff-0a7630e48ca6": [],
+    "shortcut.81d560f9-aa02-4691-b078-766110a08554": [],
+    "taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47": [],
+    "taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af": [],
+    "taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7": [],
+    "taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9": [],
+    "taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43": [],
+    "taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d": [],
+    "taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf": [],
+    "taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b": [],
+    "taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6": [],
+    "taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32": [],
+    "taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f": [],
+    "taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2": [],
+    "taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2": [],
+    "taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e": [],
+    "taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980": [],
+    "taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6": [],
+    "taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df": [],
+    "taxonomy_term.c0470b91-e700-4602-9e93-07705681d679": [],
+    "taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9": [],
+    "taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538": [],
+    "taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b": [],
+    "taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4": [],
+    "taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95": [],
+    "taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d": [],
+    "taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09": [],
+    "taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6": [],
     "user.42bd662a-80da-4069-9fb8-14db3a77bb8c": [],
     "user.b8966985-d4b2-42a7-a319-2e94ccfbb849": [],
     "paragraph.e8a7c3c3-c07a-4545-8387-ab03b8f7f47a": [],
@@ -6347,567 +7035,5 @@
     "paragraph.81b18409-0f9d-49de-a8ff-c75c7c4852c0": [],
     "paragraph.e89e2456-b6b5-4c5f-922f-9f34f6e77e68": [],
     "paragraph.2f7f892b-75ff-48a0-9034-b9af048efd84": [],
-    "paragraph.c4f743d0-4cf5-40ea-96e5-8fe5dd1092fa": [],
-    "file.85ac0ba1-80de-478e-a3f4-9bd1f003348e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "crop.49e2f9ad-4739-478a-ae41-332d79fde879": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "node.b71f8b90-7636-4e13-b31a-e7ba42eb94f7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.85ac0ba1-80de-478e-a3f4-9bd1f003348e"
-    ],
-    "node.d5d38a64-f226-42e0-8691-6c1b128435bf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.8941a0dc-4d03-4a42-a647-8d20898ac224": [
-        "node.d5d38a64-f226-42e0-8691-6c1b128435bf"
-    ],
-    "node.4c9fd2d9-307a-43a1-8993-d422261eabd7": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.3a7a13f5-0525-4037-a9a1-c9be77e0bd6a": [
-        "node.4c9fd2d9-307a-43a1-8993-d422261eabd7"
-    ],
-    "node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.9bbfe0c4-7942-40e3-8e83-eaa5df854298": [
-        "node.d7d864f9-d3b6-4682-8e86-8d1f7c6f774e"
-    ],
-    "node.38535020-c00e-4720-8534-73346ff7cb0d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.c6c581ce-f776-47a6-ab45-1e56e1593594": [
-        "node.38535020-c00e-4720-8534-73346ff7cb0d"
-    ],
-    "node.0e1fbc03-a045-4ca4-8925-69e39b67d893": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.4b0cf0d7-3421-4559-a405-c016e11c1970": [
-        "node.0e1fbc03-a045-4ca4-8925-69e39b67d893"
-    ],
-    "node.7fe05b4e-044a-4426-8fce-538781450976": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.883096d9-5f02-445f-8db9-ad75362da9cc",
-        "taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47"
-    ],
-    "taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47": [],
-    "path_alias.94eab8eb-be76-4fad-afac-3e50e3d1e1b5": [
-        "node.7fe05b4e-044a-4426-8fce-538781450976"
-    ],
-    "file.7f65da75-c4fb-4e12-920f-b3538cacf3b2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "file.565ea6d1-39f8-4179-979e-f012fcb264af": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "crop.87fbc4e4-490e-4de5-a34f-c11e859cdd2d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.292a3bd1-0ac0-4f1d-81b7-74bb96be1ee9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.7f65da75-c4fb-4e12-920f-b3538cacf3b2"
-    ],
-    "taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af": [],
-    "node.13daae68-e5f9-4295-a6ff-908aae12f012": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.0c37e975-e240-4834-acbb-f9ea19dee13f",
-        "taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af",
-        "taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47"
-    ],
-    "path_alias.0e885b9c-0124-4521-a450-b4702c51a5ba": [
-        "node.13daae68-e5f9-4295-a6ff-908aae12f012"
-    ],
-    "file.5f4a9e0d-57e0-4e84-b8ba-9b641955c102": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.0c37e975-e240-4834-acbb-f9ea19dee13f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.5f4a9e0d-57e0-4e84-b8ba-9b641955c102"
-    ],
-    "file.4f4b0b2d-c1bf-4a6b-a234-9f1fd72bd110": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.f9a0267d-cec0-44fd-abf6-fe569cde3b19": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.4f4b0b2d-c1bf-4a6b-a234-9f1fd72bd110"
-    ],
-    "taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7": [],
-    "path_alias.be39dc41-6c80-4be3-ac25-f20011d65c54": [
-        "node.773bab66-561e-4954-9689-a7d817cbbb35"
-    ],
-    "node.773bab66-561e-4954-9689-a7d817cbbb35": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.f9a0267d-cec0-44fd-abf6-fe569cde3b19",
-        "taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7"
-    ],
-    "file.843cc6fb-9e67-43c7-96a2-a566b2e6c0f2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.a45a3074-779f-4238-b97c-d4d7146f8a59": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.843cc6fb-9e67-43c7-96a2-a566b2e6c0f2"
-    ],
-    "taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9": [],
-    "path_alias.84fe08d5-7a51-4a66-be94-3b0eda19e962": [
-        "node.deefc5f9-12d4-46a5-a647-4522de0e5e63"
-    ],
-    "node.deefc5f9-12d4-46a5-a647-4522de0e5e63": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.a45a3074-779f-4238-b97c-d4d7146f8a59",
-        "taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9"
-    ],
-    "file.3c2c7139-187d-4b24-b9af-6b8656d96ce3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.33ccb3cb-1247-45e4-a43b-078d74034320": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.3c2c7139-187d-4b24-b9af-6b8656d96ce3"
-    ],
-    "taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43": [],
-    "path_alias.7589fe0f-4e02-4640-b317-4b659a8702ea": [
-        "node.5c296c46-30d9-4ec8-93e4-837330c833b0"
-    ],
-    "node.5c296c46-30d9-4ec8-93e4-837330c833b0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.33ccb3cb-1247-45e4-a43b-078d74034320",
-        "taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43"
-    ],
-    "file.07bc5ab4-a33f-404f-8686-da4a9f2bc910": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.07bc5ab4-a33f-404f-8686-da4a9f2bc910"
-    ],
-    "taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d": [],
-    "path_alias.89855544-a29f-4a69-9717-de7dd29ee92c": [
-        "node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0"
-    ],
-    "node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.36dadcca-36f4-4f14-9f4f-8c0e1c33acc8",
-        "taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d"
-    ],
-    "file.72d32f1d-6662-45ed-bb8f-efd28bcc3aef": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.72d32f1d-6662-45ed-bb8f-efd28bcc3aef"
-    ],
-    "taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf": [],
-    "path_alias.bb03c9a3-1968-4fe2-8362-fa68ed28e5ea": [
-        "node.487866ab-71b2-407e-9911-c6207dbccd80"
-    ],
-    "node.487866ab-71b2-407e-9911-c6207dbccd80": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.d50c069b-e2a8-4e8d-b46b-13de499ba5f2",
-        "taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf"
-    ],
-    "file.c4807834-918a-4421-9177-5a1f95900ca5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.f18dde63-4721-4837-8c16-4449ef5611ee": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.c4807834-918a-4421-9177-5a1f95900ca5"
-    ],
-    "taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b": [],
-    "path_alias.40cfe58e-9ab3-4fc7-8544-8faab73d810d": [
-        "node.d0cc3427-9501-4857-93e4-d2153b18ebe5"
-    ],
-    "node.d0cc3427-9501-4857-93e4-d2153b18ebe5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.f18dde63-4721-4837-8c16-4449ef5611ee",
-        "taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b"
-    ],
-    "file.7cea60ab-cd20-42cb-b995-fa470fc393f5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.9d524fe7-830a-475f-b131-d4a0c874102e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.7cea60ab-cd20-42cb-b995-fa470fc393f5"
-    ],
-    "taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6": [],
-    "path_alias.fbca963d-93c3-486f-b9d9-c2092000c188": [
-        "node.19efa1df-9e8a-4c65-b1e8-55248ac520ed"
-    ],
-    "node.19efa1df-9e8a-4c65-b1e8-55248ac520ed": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.9d524fe7-830a-475f-b131-d4a0c874102e",
-        "taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6"
-    ],
-    "file.67a1977e-b9e3-45ad-bddf-5058a80414f9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.4bec5c04-dd0a-415d-9cd2-9bf76435a983": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.67a1977e-b9e3-45ad-bddf-5058a80414f9"
-    ],
-    "taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32": [],
-    "path_alias.094decee-bee6-4953-9834-9eff4207a802": [
-        "node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b"
-    ],
-    "node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.4bec5c04-dd0a-415d-9cd2-9bf76435a983",
-        "taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32"
-    ],
-    "file.8c712d15-f3f1-463f-9cbb-f4338db22a27": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.29435a22-668d-415d-b8b0-6bc76fd92ef3": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.8c712d15-f3f1-463f-9cbb-f4338db22a27"
-    ],
-    "taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f": [],
-    "path_alias.ee21faa4-0c25-40b1-846d-4b3bf2b0c353": [
-        "node.058eb05f-cec1-43bd-a4e1-0b09630662e9"
-    ],
-    "node.058eb05f-cec1-43bd-a4e1-0b09630662e9": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.29435a22-668d-415d-b8b0-6bc76fd92ef3",
-        "taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f"
-    ],
-    "file.2b87b13a-05e0-4f03-9760-517085f673ff": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.0aabd501-3b1b-4352-a5c3-60b01c295311": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.2b87b13a-05e0-4f03-9760-517085f673ff"
-    ],
-    "taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2": [],
-    "path_alias.8b415f79-73dd-4d21-b0e7-b9b74cf324ba": [
-        "node.7fab23fc-6ea7-432b-86da-ec32dfc008ab"
-    ],
-    "node.7fab23fc-6ea7-432b-86da-ec32dfc008ab": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.0aabd501-3b1b-4352-a5c3-60b01c295311",
-        "taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2"
-    ],
-    "file.40f8d8c1-1f63-4180-81c0-42edd8e84a9f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.40f8d8c1-1f63-4180-81c0-42edd8e84a9f"
-    ],
-    "taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2": [],
-    "path_alias.c33e1b1a-6fed-4ca8-9241-5d1eefa6f7e7": [
-        "node.84decda9-d30b-4cd0-b468-937a7e47776b"
-    ],
-    "node.84decda9-d30b-4cd0-b468-937a7e47776b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.3e58e66f-f8b2-4c97-8192-4d983d39f9a5",
-        "taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2"
-    ],
-    "file.1ffeab5a-4395-4ee9-bf05-bac394a588fd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.1ffeab5a-4395-4ee9-bf05-bac394a588fd"
-    ],
-    "taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e": [],
-    "path_alias.ef8eecc0-5a61-48de-b30c-d15e48459249": [
-        "node.6ed95c44-c301-4f53-8f87-6d33de758f7e"
-    ],
-    "node.6ed95c44-c301-4f53-8f87-6d33de758f7e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.e8ccf4dc-fdc3-4902-87fb-7f0153597ef0",
-        "taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e"
-    ],
-    "file.45eba0ef-3846-4f3b-8147-d0ad5509c665": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.14a032ba-cd66-4fbf-b45e-5c6851eead80": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.45eba0ef-3846-4f3b-8147-d0ad5509c665"
-    ],
-    "taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980": [],
-    "path_alias.1f043e2e-99c3-4a6b-8c85-7f8cb652bb71": [
-        "node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18"
-    ],
-    "node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.14a032ba-cd66-4fbf-b45e-5c6851eead80",
-        "taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980"
-    ],
-    "file.21385f14-1910-4388-bf1a-200964fa73b1": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.6cad1384-e45d-48f9-86b4-c8f9efac72d6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.21385f14-1910-4388-bf1a-200964fa73b1"
-    ],
-    "taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6": [],
-    "path_alias.f83c3ec3-ea20-4e20-883c-8aa2bd09126f": [
-        "node.33ea9079-3c84-410b-b568-eeff8c70a41f"
-    ],
-    "node.33ea9079-3c84-410b-b568-eeff8c70a41f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.6cad1384-e45d-48f9-86b4-c8f9efac72d6",
-        "taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6"
-    ],
-    "file.e65a89ea-4eac-4562-9156-e3487cf1cbdd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.52d13a35-d686-46a7-ac8a-b0e1219e4583": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.e65a89ea-4eac-4562-9156-e3487cf1cbdd"
-    ],
-    "taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df": [],
-    "path_alias.4623a53c-319d-4bb7-ae65-5a8eed2d4fc5": [
-        "node.eedbf764-01b3-48e8-9de4-b8d23caa8efd"
-    ],
-    "node.eedbf764-01b3-48e8-9de4-b8d23caa8efd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.52d13a35-d686-46a7-ac8a-b0e1219e4583",
-        "taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df"
-    ],
-    "file.06f032ff-a1bc-4f98-9964-40c7278e885f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.3877e696-9620-44de-b941-3ebb42c1244b": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.06f032ff-a1bc-4f98-9964-40c7278e885f"
-    ],
-    "path_alias.103e1a16-2b12-430e-9946-0f77e25b4e11": [
-        "node.8a979843-907c-49d9-abaf-a21b0432e648"
-    ],
-    "node.8a979843-907c-49d9-abaf-a21b0432e648": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.3877e696-9620-44de-b941-3ebb42c1244b",
-        "taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7"
-    ],
-    "file.943c945f-8081-4bfd-92f9-302f5ddaf90f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.04897b7d-6d74-491c-935f-65051be149fd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.943c945f-8081-4bfd-92f9-302f5ddaf90f"
-    ],
-    "taxonomy_term.c0470b91-e700-4602-9e93-07705681d679": [],
-    "path_alias.2c981801-8454-4517-81c7-f8b9cbfecc36": [
-        "node.1d491da6-0523-4709-aa35-17df110f5506"
-    ],
-    "node.1d491da6-0523-4709-aa35-17df110f5506": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.04897b7d-6d74-491c-935f-65051be149fd",
-        "taxonomy_term.c0470b91-e700-4602-9e93-07705681d679"
-    ],
-    "file.32c08f1a-4b4d-4ef7-b1eb-08a8cc9871dc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.4aa1060c-6977-4c35-b946-64f4cce860dd": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.32c08f1a-4b4d-4ef7-b1eb-08a8cc9871dc"
-    ],
-    "taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9": [],
-    "path_alias.705f9177-84d1-407b-9657-01fe314d52e1": [
-        "node.6dac7a82-aecd-4bd2-9303-0383d77f4a88"
-    ],
-    "node.6dac7a82-aecd-4bd2-9303-0383d77f4a88": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.4aa1060c-6977-4c35-b946-64f4cce860dd",
-        "taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9"
-    ],
-    "file.a6e24803-104a-4b74-b016-242b77185b9e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.00e90d0a-0d8f-4579-8022-be91f2449149": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.a6e24803-104a-4b74-b016-242b77185b9e"
-    ],
-    "path_alias.bee3f597-8c0d-4ad3-9ac6-0729a0356302": [
-        "node.62d158a4-17c2-488c-990c-d852eb7e3f7c"
-    ],
-    "node.62d158a4-17c2-488c-990c-d852eb7e3f7c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.00e90d0a-0d8f-4579-8022-be91f2449149",
-        "taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b"
-    ],
-    "file.4084d1f3-6c8c-4976-86f7-68ea491ee3bf": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.034364f8-2e16-4ec9-8148-5af2c070c038": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.4084d1f3-6c8c-4976-86f7-68ea491ee3bf"
-    ],
-    "taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538": [],
-    "path_alias.eba0fc97-ab0a-4059-aee4-f8195f8bc41b": [
-        "node.5a8df3bf-d501-47ae-978b-ef6219c68c60"
-    ],
-    "node.5a8df3bf-d501-47ae-978b-ef6219c68c60": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.034364f8-2e16-4ec9-8148-5af2c070c038",
-        "taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538"
-    ],
-    "file.4a9d5a98-845c-45d1-98ca-2cd038d99326": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.4a9d5a98-845c-45d1-98ca-2cd038d99326"
-    ],
-    "taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b": [],
-    "path_alias.9b61fa71-0eef-4864-86bc-eb99dc31ab30": [
-        "node.5cc36ded-e301-49de-88eb-c218c980707f"
-    ],
-    "node.5cc36ded-e301-49de-88eb-c218c980707f": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.ce691434-fc21-4ad1-8e7d-61d472f9c2ab",
-        "taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b"
-    ],
-    "file.b809880e-834b-4a64-8051-6a96e207f11e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.a587aa47-64ee-4454-a822-da2a3fd44147": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.b809880e-834b-4a64-8051-6a96e207f11e"
-    ],
-    "taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4": [],
-    "path_alias.a3d49a94-32b6-4288-8b7d-ea072ec7e0d4": [
-        "node.9e094927-a767-437b-b3b7-90a5bea35da0"
-    ],
-    "node.9e094927-a767-437b-b3b7-90a5bea35da0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.a587aa47-64ee-4454-a822-da2a3fd44147",
-        "taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4"
-    ],
-    "file.bc1169a7-d6b0-46d8-ae22-d921682b88f6": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.85934919-d843-4503-93e6-e871644bb46c": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.bc1169a7-d6b0-46d8-ae22-d921682b88f6"
-    ],
-    "taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95": [],
-    "path_alias.0b47c099-a0e8-49bb-b94b-8a0377a2882a": [
-        "node.d473b252-b668-40bc-b744-68ea259702fc"
-    ],
-    "node.d473b252-b668-40bc-b744-68ea259702fc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.85934919-d843-4503-93e6-e871644bb46c",
-        "taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95"
-    ],
-    "file.a2680e95-a118-48e8-8a89-fc608326c0e0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.22221e8c-d072-40ba-a032-b34b0c964a57": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.a2680e95-a118-48e8-8a89-fc608326c0e0"
-    ],
-    "taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d": [],
-    "path_alias.b8ad3cf0-b3ad-44b0-93b5-c12d76ff935d": [
-        "node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191"
-    ],
-    "node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.22221e8c-d072-40ba-a032-b34b0c964a57",
-        "taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d"
-    ],
-    "file.32935ed5-d928-413e-824c-3c44e5ccd5d8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.f8784685-be7e-48b8-9c86-f205c7e9d981": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.32935ed5-d928-413e-824c-3c44e5ccd5d8"
-    ],
-    "taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09": [],
-    "path_alias.1a1125ef-0203-4471-a376-e6322b8c0511": [
-        "node.16846795-5fd0-4a67-a080-edfaa8e20cd8"
-    ],
-    "node.16846795-5fd0-4a67-a080-edfaa8e20cd8": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.f8784685-be7e-48b8-9c86-f205c7e9d981",
-        "taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09"
-    ],
-    "file.49873c79-708c-4e0c-bc4c-adde4414165e": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.49873c79-708c-4e0c-bc4c-adde4414165e"
-    ],
-    "taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6": [],
-    "path_alias.e07a9581-a98a-4acf-b878-492b260fde28": [
-        "node.25347778-fdbf-4a8e-80f9-2d7e655391fe"
-    ],
-    "node.25347778-fdbf-4a8e-80f9-2d7e655391fe": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "media.4a1c5fbf-83ad-406f-b39b-32a3fd2d0d90",
-        "taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6"
-    ],
-    "node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.950ec3e2-a41f-4da8-a54e-456156941219": [
-        "node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13"
-    ],
-    "redirect.bfacd4d2-3e91-4845-bec5-4f6d7558788d": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "shortcut.81d560f9-aa02-4691-b078-766110a08554": [],
-    "shortcut.45ca7a46-646c-4ae4-83ff-0a7630e48ca6": [],
-    "shortcut.91b0a545-47e6-47f6-8c91-312400be7975": [],
-    "node.298d7816-0b4a-449e-a78d-fcf973f24bf0": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.b1705270-e583-405b-a7b4-6ae30059706f": [
-        "node.298d7816-0b4a-449e-a78d-fcf973f24bf0"
-    ],
-    "file.b17eae76-e417-4f22-8290-da16366ebb24": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "media.883096d9-5f02-445f-8db9-ad75362da9cc": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849",
-        "file.565ea6d1-39f8-4179-979e-f012fcb264af",
-        "file.b17eae76-e417-4f22-8290-da16366ebb24"
-    ],
-    "node.22f6723d-c781-4548-a2cf-3b642e91b4ad": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.9d87323f-c40a-4737-943e-c8f48cb37bd3": [
-        "node.22f6723d-c781-4548-a2cf-3b642e91b4ad"
-    ],
-    "redirect.8f837f21-5631-490d-b4f4-a8cc65cfafae": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "node.81676cf3-0b30-4619-a922-12ff3e16ba76": [
-        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
-    ],
-    "path_alias.678f29fc-1b63-4450-8689-7d0949a2779b": [
-        "node.81676cf3-0b30-4619-a922-12ff3e16ba76"
-    ]
+    "paragraph.c4f743d0-4cf5-40ea-96e5-8fe5dd1092fa": []
 }
\ No newline at end of file
diff --git a/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json b/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json
index fb793e145..43bf9461c 100644
--- a/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json
+++ b/content/node.0001428e-621c-49ca-83d3-4323ea446f48.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "71938847a402f6b5af7c2e34bca063d3",
             "target_type": "feeds_feed",
diff --git a/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json b/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json
index 9c4ee442e..247ab866a 100644
--- a/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json
+++ b/content/node.001f3ebb-79dc-43ad-a363-6dc668d06a0c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a1a228d3231ffab8895ec0cbd78f0b1d",
             "target_type": "feeds_feed",
diff --git a/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json b/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json
index 639e393e6..a62ed3e85 100644
--- a/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json
+++ b/content/node.00497277-4b40-4d36-a473-8d8e1a187c18.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A side effect of <a href=\"/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        ",
+            "value": "\n          <p>A side effect of <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A side effect of <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "aacb745c094cf5a9f668c64b15000f49",
             "target_type": "feeds_feed",
diff --git a/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json b/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json
index b67142502..666cc01eb 100644
--- a/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json
+++ b/content/node.00d62e94-80d1-4792-bdea-88a064f6bf65.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3bf8b7e44f82bf7d6ad5ce1fda692ae6",
             "target_type": "feeds_feed",
diff --git a/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json b/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json
index a6484dfb1..de3e280a4 100644
--- a/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json
+++ b/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "957251b7baf05530d91b2a9731016317",
             "target_type": "feeds_feed",
diff --git a/content/node.01230324-62b5-442b-80e4-09268a31819b.json b/content/node.01230324-62b5-442b-80e4-09268a31819b.json
index 5399f1b0d..89862fa7a 100644
--- a/content/node.01230324-62b5-442b-80e4-09268a31819b.json
+++ b/content/node.01230324-62b5-442b-80e4-09268a31819b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3baa147faae6a26ac886bb26940c8f43",
             "target_type": "feeds_feed",
diff --git a/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json b/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json
index 6c10fd87a..827b38a4e 100644
--- a/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json
+++ b/content/node.01893784-8f45-4466-8586-17df23e7e4b5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/22-dave-liddament\">episode 22 of the Beyond Blocks podcast<\/a> with Dave Liddament.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/22-dave-liddament\">episode 22 of the Beyond Blocks podcast<\/a> with Dave Liddament.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/22-dave-liddament\">episode 22 of the Beyond Blocks podcast<\/a> with Dave Liddament.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9a7b258b69b97c51304c0aa8d6b87263",
             "target_type": "feeds_feed",
diff --git a/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json b/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json
index 69f19a7ac..f8f2080b6 100644
--- a/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json
+++ b/content/node.018bf894-2d3e-4130-b0bd-43450ef5753a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cdd9ab25b0351a9082e1580898e5ecbc",
             "target_type": "feeds_feed",
diff --git a/content/node.01f3b831-e981-471f-aef9-076b054e3495.json b/content/node.01f3b831-e981-471f-aef9-076b054e3495.json
index 0401c2466..4e026dd42 100644
--- a/content/node.01f3b831-e981-471f-aef9-076b054e3495.json
+++ b/content/node.01f3b831-e981-471f-aef9-076b054e3495.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "60c550711c51c2b739051e4640eba954",
             "target_type": "feeds_feed",
diff --git a/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json b/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json
index 5f49c46e6..b771a7ad5 100644
--- a/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json
+++ b/content/node.0209ee07-9e17-4c85-ae5e-d14ae42bb22a.json
@@ -84,7 +84,7 @@
         {
             "value": "<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=\"\/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=\"\/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>",
             "format": "basic_html",
-            "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=\"\/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=\"\/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>",
+            "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": ""
         }
     ],
diff --git a/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json b/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json
index 91d786f2c..70b549196 100644
--- a/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json
+++ b/content/node.021e00c1-b813-4edd-8064-71285bc3647d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bc11c3125e2e228f16b76f91b749c764",
             "target_type": "feeds_feed",
diff --git a/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json b/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json
index 11714b3c5..2db8fb91d 100644
--- a/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json
+++ b/content/node.0231b26c-ac28-44e8-a2bf-cc7c86984e7e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "54447bfd288cd6e71d4b06bd0646502d",
             "target_type": "feeds_feed",
diff --git a/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json b/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json
index d8610d918..1726a3422 100644
--- a/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json
+++ b/content/node.024f2c81-68af-4eef-bea5-1b1d43bd1b39.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "18e7b8e123a0c299bb44600a75b56d9e",
             "target_type": "feeds_feed",
diff --git a/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json b/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json
index 7788ee3c0..8c2c5f37c 100644
--- a/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json
+++ b/content/node.025f0dde-748b-44f4-93e2-4e0602d30104.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b663fb9c5e0257d2fdece24454ad3bfd",
             "target_type": "feeds_feed",
diff --git a/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json b/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json
index 7f6a0bd23..941036510 100644
--- a/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json
+++ b/content/node.02777730-3fe8-4eba-8a16-e847042b7351.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "891d018e5d9b5fa68288878004365cce",
             "target_type": "feeds_feed",
diff --git a/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json b/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json
index 92da12627..d8951f2b1 100644
--- a/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json
+++ b/content/node.02bd7b93-43c7-453f-8af9-0be875b27f82.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f671ea961bdda4e275277b04dc159c79",
             "target_type": "feeds_feed",
diff --git a/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json b/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json
index 0a08b7f57..aac457b30 100644
--- a/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json
+++ b/content/node.02c9e148-b98f-42ae-80f1-d19a6d3fcfb2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c50e363614371738c421f8a32ee763f3",
             "target_type": "feeds_feed",
diff --git a/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json b/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json
index 925ab1f83..80d7a01d6 100644
--- a/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json
+++ b/content/node.0300b4ea-e71b-4f9c-b4f2-f04f98e92d6c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0f37079942ad6ce63ae32e8ea7c57c79",
             "target_type": "feeds_feed",
diff --git a/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json b/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json
index faf8a4586..20c3e8880 100644
--- a/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json
+++ b/content/node.0316dfcf-b709-47e1-9622-9355b5ece6d9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "021827be7bf3f083020a0f2ff11066d8",
             "target_type": "feeds_feed",
diff --git a/content/node.0318e249-a9a8-476f-9bd4-432544369917.json b/content/node.0318e249-a9a8-476f-9bd4-432544369917.json
index c51f1edeb..abd9d7501 100644
--- a/content/node.0318e249-a9a8-476f-9bd4-432544369917.json
+++ b/content/node.0318e249-a9a8-476f-9bd4-432544369917.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/daily\/2025\/01\/14\/patching-drupal\">patching is the only option<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p><a href=\"\/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=\"\/daily\/2025\/01\/14\/patching-drupal\">patching is the only option<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/daily\/2025\/01\/14\/patching-drupal\">patching is the only option<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e1882c079f5b933697958ec2ac91a1b7",
             "target_type": "feeds_feed",
diff --git a/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json b/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json
index 5e473f299..833ae8771 100644
--- a/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json
+++ b/content/node.033f0b46-69f9-4ea0-9706-d930e67dd5d8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cc353a3343b4a9ed6dc01850a09c8f76",
             "target_type": "feeds_feed",
diff --git a/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json b/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json
index cce3451ee..ee4d0661d 100644
--- a/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json
+++ b/content/node.036a8839-c5f9-4206-a979-201e9dac1557.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7256a5bb0e6800a548d88e2979344646",
             "target_type": "feeds_feed",
diff --git a/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json b/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json
index 632536ae6..8dfe76d70 100644
--- a/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json
+++ b/content/node.037796b8-42d8-4ea4-abec-f8c8de0d97e8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4ddf140ca0555c2028d2bb2db394282f",
             "target_type": "feeds_feed",
diff --git a/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json b/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json
index f560cb967..85d82b9d0 100644
--- a/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json
+++ b/content/node.03bbb03d-5963-477a-a904-19e2c1f1a581.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a3ea19c23705f4574c9b1455cc2169bc",
             "target_type": "feeds_feed",
diff --git a/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json b/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json
index 724881b2a..2bc2585d5 100644
--- a/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json
+++ b/content/node.03c0a713-f32d-445b-9397-add68fbf2fe5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/daily\/2024\/11\/27\/nix-as-an-operating-system\">my laptop configuration<\/a>, <a href=\"/daily\/2024\/11\/30\/using-nix-for-local-application-development\">local development environments<\/a> and <a href=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/daily\/2024\/11\/27\/nix-as-an-operating-system\">my laptop configuration<\/a>, <a href=\"\/daily\/2024\/11\/30\/using-nix-for-local-application-development\">local development environments<\/a> and <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/daily\/2024\/11\/27\/nix-as-an-operating-system\">my laptop configuration<\/a>, <a href=\"/daily\/2024\/11\/30\/using-nix-for-local-application-development\">local development environments<\/a> and <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ddffb71cbb4982c0c4d9ca78fecdcd4c",
             "target_type": "feeds_feed",
diff --git a/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json b/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json
index 23b66dafb..d73539315 100644
--- a/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json
+++ b/content/node.042e4d0c-f835-47dd-8075-745df0a7f8f2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4d3892ad51836bdd33e47e7043615d75",
             "target_type": "feeds_feed",
diff --git a/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json b/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json
index f7f003338..be9ace625 100644
--- a/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json
+++ b/content/node.04ccaf9c-a0e4-4ca9-b96b-d32e3fc7f384.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "137f467c7894dcf4d534ab6c7572567a",
             "target_type": "feeds_feed",
diff --git a/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json b/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json
index 158e904c8..f86304c1f 100644
--- a/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json
+++ b/content/node.050525d7-3275-486e-8f0e-9548aa81a156.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "54fdebe3f9556a6d18a8f24c72f72652",
             "target_type": "feeds_feed",
diff --git a/content/node.050a5113-59bc-461e-ac78-420e16055303.json b/content/node.050a5113-59bc-461e-ac78-420e16055303.json
index f35e3b833..1132b0225 100644
--- a/content/node.050a5113-59bc-461e-ac78-420e16055303.json
+++ b/content/node.050a5113-59bc-461e-ac78-420e16055303.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week on the <a href=\"/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=\"/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        ",
+            "value": "\n          <p>This week on the <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>This week on the <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3cc8c054a1675b2ab1a1ec63dd5f49ad",
             "target_type": "feeds_feed",
diff --git a/content/node.05232b81-d945-4112-99bf-d1adb2552428.json b/content/node.05232b81-d945-4112-99bf-d1adb2552428.json
index a210e7b52..0ae10181f 100644
--- a/content/node.05232b81-d945-4112-99bf-d1adb2552428.json
+++ b/content/node.05232b81-d945-4112-99bf-d1adb2552428.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "91a7ebf19cb056c110911fc721129f1a",
             "target_type": "feeds_feed",
diff --git a/content/node.058eb05f-cec1-43bd-a4e1-0b09630662e9.json b/content/node.058eb05f-cec1-43bd-a4e1-0b09630662e9.json
index 53ebe2eeb..e8957e22d 100644
--- a/content/node.058eb05f-cec1-43bd-a4e1-0b09630662e9.json
+++ b/content/node.058eb05f-cec1-43bd-a4e1-0b09630662e9.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "f9b1ec5f-2fdb-438c-a266-082a86a6d94f"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 4ed8f334e..33ee76c7b 100644
--- a/content/node.0610a25f-884a-48b6-8be0-e969749d316a.json
+++ b/content/node.0610a25f-884a-48b6-8be0-e969749d316a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "838a5e92a344c70d064478815bc8dd16",
             "target_type": "feeds_feed",
diff --git a/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json b/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json
index ecbfaf9ca..6320964b7 100644
--- a/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json
+++ b/content/node.062c06ac-6ca0-4b03-8d5e-63a84eb8b9c2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "957b36c5f9d9b70a87a9a60d1f31f9ab",
             "target_type": "feeds_feed",
diff --git a/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json b/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json
index 8910b9fc7..8f731db06 100644
--- a/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json
+++ b/content/node.066297b1-ab00-4769-afe1-d3831ed2a654.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3bdc81d1ff8f05f8b1beb3069dfdd370",
             "target_type": "feeds_feed",
diff --git a/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json b/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json
index df58f71b0..1628a42c1 100644
--- a/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json
+++ b/content/node.06b8d0b3-318a-4a06-902c-f42ce169774b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2955d4cb562bc0a9ba0456bc040c629b",
             "target_type": "feeds_feed",
diff --git a/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json b/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json
index 6646cbdcd..aac618038 100644
--- a/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json
+++ b/content/node.079f2e09-0827-458e-91d3-6dd5b8b80c56.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>It's shown in the examples of the <a href=\"/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        ",
+            "value": "\n          <p>It's shown in the examples of the <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>It's shown in the examples of the <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1029a860138fe970164e891ad1617d01",
             "target_type": "feeds_feed",
diff --git a/content/node.08209d64-40fa-4771-9415-c23e962a5028.json b/content/node.08209d64-40fa-4771-9415-c23e962a5028.json
index 803e799a9..04714395d 100644
--- a/content/node.08209d64-40fa-4771-9415-c23e962a5028.json
+++ b/content/node.08209d64-40fa-4771-9415-c23e962a5028.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f40826212e5c798e718edd8ad155d3c0",
             "target_type": "feeds_feed",
diff --git a/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json b/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json
index 6f4f26678..8bb3fa25d 100644
--- a/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json
+++ b/content/node.0843614b-645e-4d55-9e70-f960d504cadb.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/presentations\/things-you-should-know-about-php\">latest version of my slides are online<\/a> as well <a href=\"/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=\"/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        ",
+            "value": "\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=\"\/presentations\/things-you-should-know-about-php\">latest version of my slides are online<\/a> as well <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/presentations\/things-you-should-know-about-php\">latest version of my slides are online<\/a> as well <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c6186e7dbf6c19f8512dc083f70d7840",
             "target_type": "feeds_feed",
diff --git a/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json b/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json
index 6da50d104..8d0dcb4d1 100644
--- a/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json
+++ b/content/node.09073a81-2a1b-4200-905b-98b43152fe37.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "48855aeeae21e4c8f58c4898ddd9fea4",
             "target_type": "feeds_feed",
diff --git a/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json b/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json
index 7f9b0fb98..43b434b79 100644
--- a/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json
+++ b/content/node.09097ac1-03ea-456c-a1bd-49bdc2bb9499.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1c6afa84bf0230b6fc71cdc42239c6e2",
             "target_type": "feeds_feed",
diff --git a/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json b/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json
index 9920eb2ed..d5d079ef0 100644
--- a/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json
+++ b/content/node.098d8367-a714-4e16-97b5-44f42a2a1cc2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6e7b86e1b92a964e048c10b4a1bb65da",
             "target_type": "feeds_feed",
diff --git a/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json b/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json
index 62ea4b5cd..ea39a1563 100644
--- a/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json
+++ b/content/node.09d6a39f-ac99-44fc-b660-4f976132d813.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2b68ef78311dde7624d8a9f3bf2aecd5",
             "target_type": "feeds_feed",
diff --git a/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json b/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json
index 6a6b32ea0..d7680363a 100644
--- a/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json
+++ b/content/node.09dff532-7bc4-4949-bfdf-7c4a6e59097a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6878d25dc442270921c029ddd00724c8",
             "target_type": "feeds_feed",
diff --git a/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json b/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json
index b16264f69..f2ee22d67 100644
--- a/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json
+++ b/content/node.09f421c4-eff1-4b5c-a692-45dfbd837758.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2a66b63393fa72ffccd1e378ef840bca",
             "target_type": "feeds_feed",
diff --git a/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json b/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json
index 06dd9de26..0824072c3 100644
--- a/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json
+++ b/content/node.0a04ac23-4d64-40e8-8e94-ead3cab7129d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "44876b1c656f7fa3e4611f4f47e7c361",
             "target_type": "feeds_feed",
diff --git a/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json b/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json
index eda68702d..0b6fc8df2 100644
--- a/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json
+++ b/content/node.0a2a3238-42ea-46de-8140-94e74f381916.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "666722719a2759d76794a08b3c2837fa",
             "target_type": "feeds_feed",
diff --git a/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json b/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json
index 745556ca6..c78cc7e4e 100644
--- a/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json
+++ b/content/node.0a3bf034-7203-45c2-aae5-74f9211929fa.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "af41a18ab3e2e252ab86e7243333ad9f",
             "target_type": "feeds_feed",
diff --git a/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json b/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json
index 06d4e3fce..84ff4a80e 100644
--- a/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json
+++ b/content/node.0a3c28cf-0365-40a7-bc3d-074e90bb28ce.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "aa56bdd02fef215659f339a51ad72312",
             "target_type": "feeds_feed",
diff --git a/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json b/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json
index 3f05dc578..a325627f7 100644
--- a/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json
+++ b/content/node.0a4f05ae-4240-476b-bb57-bcf3d3a598a3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>If <a href=\"/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=\"/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=\"/daily\/2025\/02\/19\/back-or-forward\">without needing to roll back to the previous version<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>If <a href=\"\/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=\"\/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=\"\/daily\/2025\/02\/19\/back-or-forward\">without needing to roll back to the previous version<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>If <a href=\"/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=\"/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=\"/daily\/2025\/02\/19\/back-or-forward\">without needing to roll back to the previous version<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "118c906a95ca0d083c79dec04035d210",
             "target_type": "feeds_feed",
diff --git a/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json b/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json
index bef3910f3..488519dd7 100644
--- a/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json
+++ b/content/node.0ab79b3f-c48b-4e56-a50f-d39baf2df02e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Instead of <a href=\"/daily\/2024\/05\/31\/putting-glue-on-pizza\">using AI to autocomplete code<\/a> or <a href=\"/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        ",
+            "value": "\n          <p>Instead of <a href=\"\/daily\/2024\/05\/31\/putting-glue-on-pizza\">using AI to autocomplete code<\/a> or <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Instead of <a href=\"/daily\/2024\/05\/31\/putting-glue-on-pizza\">using AI to autocomplete code<\/a> or <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e41c8f0126dd0649815f7d2f25e91bbc",
             "target_type": "feeds_feed",
diff --git a/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json b/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json
index 4546b5522..265d4a56d 100644
--- a/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json
+++ b/content/node.0bb8a36a-3c0e-4545-bbc6-b6c5b80b0ee6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3d0846676f872cb7c1f67b9afcb995ac",
             "target_type": "feeds_feed",
diff --git a/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json b/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json
index 00ba7485e..833ad0ad6 100644
--- a/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json
+++ b/content/node.0be950c9-3eaf-4ac1-9833-8b3f3fde5a0f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d138c01e7e0e6b18b39148606ce5111a",
             "target_type": "feeds_feed",
diff --git a/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json b/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json
index cc6098835..b0c147eed 100644
--- a/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json
+++ b/content/node.0c1ee324-e522-440a-85bf-e91847091ec9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4f660d322ca2ed3306e781c6c10053a1",
             "target_type": "feeds_feed",
diff --git a/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json b/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json
index 5b012c925..81952507b 100644
--- a/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json
+++ b/content/node.0c899647-4916-4ad6-bde0-5ae1f397cc13.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I've recently decided I'm going to open source <a href=\"/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=\"/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        ",
+            "value": "\n          <p>I've recently decided I'm going to open source <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I've recently decided I'm going to open source <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a38ce17b89e3700c2d33876324be5747",
             "target_type": "feeds_feed",
diff --git a/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json b/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json
index cc3a8d22b..5da138e98 100644
--- a/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json
+++ b/content/node.0cc877ae-0361-456e-be2c-73c322fe1780.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "afe58adbc88026446b4472112f8ea2a7",
             "target_type": "feeds_feed",
diff --git a/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json b/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json
index 2f26b85ce..4dc6abd1d 100644
--- a/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json
+++ b/content/node.0ce2a823-c7ad-475b-9cca-29e1b1702e77.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "00288ea28683ef7e8d770a0109344500",
             "target_type": "feeds_feed",
diff --git a/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json b/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json
index d961ed6e5..d951b54dd 100644
--- a/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json
+++ b/content/node.0cedee86-a2d2-4325-a662-a7399be15d44.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ed9692196aea3236ab447bca233fd4bc",
             "target_type": "feeds_feed",
diff --git a/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json b/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json
index 7a0633081..4d8245e34 100644
--- a/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json
+++ b/content/node.0d65cf74-92ad-4d03-a7d1-90a63c8a2823.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e760bef0560b6cb431513a24b2eb0212",
             "target_type": "feeds_feed",
diff --git a/content/node.0d707bca-be14-4504-b500-9e44abebab44.json b/content/node.0d707bca-be14-4504-b500-9e44abebab44.json
index 63487b66a..1fa8cccd0 100644
--- a/content/node.0d707bca-be14-4504-b500-9e44abebab44.json
+++ b/content/node.0d707bca-be14-4504-b500-9e44abebab44.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ef1660e036d0cc4b520bdd563fad7f86",
             "target_type": "feeds_feed",
diff --git a/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json b/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json
index 3f5b73444..21200a29f 100644
--- a/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json
+++ b/content/node.0da14ab3-af09-42cf-9813-877a7a66cf87.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e3227fd692a43f0f5a3b4f9afed9df94",
             "target_type": "feeds_feed",
diff --git a/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json b/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json
index 81be409c9..a39640de0 100644
--- a/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json
+++ b/content/node.0db2d25b-3e50-4f36-abe1-f84b938c21db.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "22be20101f09fc0d4e10cd3c6b867b76",
             "target_type": "feeds_feed",
diff --git a/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json b/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json
index 054b3e467..e6fa47566 100644
--- a/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json
+++ b/content/node.0dc691fb-cba3-4dce-b9ad-94fd84b7ca7f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d9902d3f03d57f8eef7e67d29133f05f",
             "target_type": "feeds_feed",
diff --git a/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json b/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json
index 09befb13e..9bf4cfb38 100644
--- a/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json
+++ b/content/node.0dcdf3e3-9f83-426e-9dfa-ab7a28c63951.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8a79fcd4efce6727224214430cc26505",
             "target_type": "feeds_feed",
diff --git a/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json b/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json
index 3c5283a97..c1e02dfda 100644
--- a/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json
+++ b/content/node.0dd5ea9d-9d43-4a2a-92f5-c140738ffedd.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f378ea534b4141dc8290191f8941df2c",
             "target_type": "feeds_feed",
diff --git a/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json b/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json
index a450abd33..98508dec3 100644
--- a/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json
+++ b/content/node.0e1fbc03-a045-4ca4-8925-69e39b67d893.json
@@ -76,8 +76,7 @@
     ],
     "path": [
         {
-            "alias": "",
-            "pid": null,
+            "alias": "\/daily\/2025\/05\/20\/why-write-your-own-cms",
             "langcode": "en"
         }
     ],
diff --git a/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json b/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json
index ee21c8df4..39dd61f07 100644
--- a/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json
+++ b/content/node.0e2dc3d6-4054-495b-9c8c-bad2475a0c13.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cba5205b68a6ba553b9b34ef661692d2",
             "target_type": "feeds_feed",
diff --git a/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json b/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json
index 8d1397105..f9ba1ccbd 100644
--- a/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json
+++ b/content/node.0f327d3d-33ce-498a-9234-6c1fe9f51d6a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b412bcd2d4532d309472dae5c82e8109",
             "target_type": "feeds_feed",
diff --git a/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json b/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json
index 72039c1ef..5416ece86 100644
--- a/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json
+++ b/content/node.0f349fae-6a04-42b4-979f-ed8428e97a2b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently had <a href=\"/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=\"/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        ",
+            "value": "\n          <p>I recently had <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently had <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6d7fff29a7d69d2505863bd126857e30",
             "target_type": "feeds_feed",
diff --git a/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json b/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json
index f1b6642e6..f30d7a3dc 100644
--- a/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json
+++ b/content/node.0f64feba-0a96-41e4-b8e3-10358e4c86c6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Last week, I asked <a href=\"/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        ",
+            "value": "\n          <p>Last week, I asked <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Last week, I asked <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0fa771c1556974be2eeabf42a87e75c4",
             "target_type": "feeds_feed",
diff --git a/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json b/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json
index 7c4af7fa7..62af6d530 100644
--- a/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json
+++ b/content/node.0fb30729-fd3e-4e76-9c02-d7b97a6d3b9c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e9efe0920d1be12d60386b0f70dfbd4b",
             "target_type": "feeds_feed",
diff --git a/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json b/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json
index e3b2a6e7c..39e3d00d9 100644
--- a/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json
+++ b/content/node.0fb3ebe0-46c3-4e9c-9961-e62aa512fab3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Note: The numbers within this post are taken from my <a href=\"/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        ",
+            "value": "\n          <p>Note: The numbers within this post are taken from my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Note: The numbers within this post are taken from my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ae450dbfadd5cdf2b2b209019173a073",
             "target_type": "feeds_feed",
diff --git a/content/node.1007a975-f818-4568-8560-9532e96c4577.json b/content/node.1007a975-f818-4568-8560-9532e96c4577.json
index 89b3850c1..f515375ba 100644
--- a/content/node.1007a975-f818-4568-8560-9532e96c4577.json
+++ b/content/node.1007a975-f818-4568-8560-9532e96c4577.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4c40524b5ba4570cdb941cb4e59e0508",
             "target_type": "feeds_feed",
diff --git a/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json b/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json
index c1def5e88..ef5851242 100644
--- a/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json
+++ b/content/node.10105b0a-c18f-4b77-8ac9-bec3250e37b7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0747677b2ea7269056a31e78221a91aa",
             "target_type": "feeds_feed",
diff --git a/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json b/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json
index 9170c1829..971d5c9ec 100644
--- a/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json
+++ b/content/node.10b3608a-50f6-4178-9ae2-d07f353a9c23.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bb3e2c953c9fc62ba7bde1aa86085a2d",
             "target_type": "feeds_feed",
diff --git a/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json b/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json
index ff10e83d1..aae9e05c1 100644
--- a/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json
+++ b/content/node.10d399d8-6247-48ef-a1b2-d777ecca827d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "674a5bd2088bccaaabc0533c88ba62f8",
             "target_type": "feeds_feed",
diff --git a/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json b/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json
index f6bc4a171..330ecadd5 100644
--- a/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json
+++ b/content/node.112ace31-6c57-405a-8c91-a2a19364fa20.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3579f9c1128a7333aacc2788d9b130b3",
             "target_type": "feeds_feed",
diff --git a/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json b/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json
index b4a05264f..fa798aa74 100644
--- a/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json
+++ b/content/node.113e4367-2915-402c-887f-f7dafdb28c86.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "51b7b1bae4312428d8b9e7a4c5ac11ea",
             "target_type": "feeds_feed",
diff --git a/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json b/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json
index 0bf84af0d..44a3f5887 100644
--- a/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json
+++ b/content/node.11b6429c-7f14-436c-a3cc-f5cfad7b63c0.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dbf68a40071443f9943fde754f0bddb3",
             "target_type": "feeds_feed",
diff --git a/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json b/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json
index 017d443ee..b9b097f1f 100644
--- a/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json
+++ b/content/node.123f0530-1218-4db1-b8ce-aecf38d8ec41.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c787c2846b67f55a45525ab52acd36c1",
             "target_type": "feeds_feed",
diff --git a/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json b/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json
index cebc3d3e3..e4ee68199 100644
--- a/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json
+++ b/content/node.1254f835-445d-4a54-a831-2fc179b3d15c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cf37bf626cc98ddb264219b228efc723",
             "target_type": "feeds_feed",
diff --git a/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json b/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json
index 4e58e619e..5cdfef152 100644
--- a/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json
+++ b/content/node.12950855-9231-4731-9ccc-e8bc9f61e170.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "41ef4a1e143c80e2836519ef5da477d0",
             "target_type": "feeds_feed",
diff --git a/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json b/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json
index e7a162f7e..c816b286d 100644
--- a/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json
+++ b/content/node.12b405e6-2827-4279-b85a-7f06475a69a4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I wanted to make a breaking change to my <a href=\"/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        ",
+            "value": "\n          <p>Yesterday, I wanted to make a breaking change to my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I wanted to make a breaking change to my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "12cfe483b3ce1a78d111407418450b62",
             "target_type": "feeds_feed",
diff --git a/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json b/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json
index cea8fd9c0..d4571aa94 100644
--- a/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json
+++ b/content/node.12fb6cce-1f55-4359-b189-700c8ba16935.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f43fe44d7a6115a84e3ad56bda9fb804",
             "target_type": "feeds_feed",
diff --git a/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json b/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json
index d6e872877..71561018e 100644
--- a/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json
+++ b/content/node.13312da0-7cf4-4825-ac6e-eb35c673e63e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/11-mark-conroy\">Listen to the podcast episode with Mark Conroy<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/11-mark-conroy\">Listen to the podcast episode with Mark Conroy<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/11-mark-conroy\">Listen to the podcast episode with Mark Conroy<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "00668a369ffa2c0cb637d1b9d53bbfb4",
             "target_type": "feeds_feed",
diff --git a/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json b/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json
index 384311f25..30f01ba24 100644
--- a/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json
+++ b/content/node.13aced92-5b3d-407d-b242-fb8187a78dd7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "35beb2b86a757c4691d2b49f4d652b0c",
             "target_type": "feeds_feed",
diff --git a/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json b/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json
index 622f00478..5fe678591 100644
--- a/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json
+++ b/content/node.13c70679-77d6-404e-9b4d-ca214713e315.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7fae72b5dced45dcf868b050b1fa5bc8",
             "target_type": "feeds_feed",
diff --git a/content/node.13daae68-e5f9-4295-a6ff-908aae12f012.json b/content/node.13daae68-e5f9-4295-a6ff-908aae12f012.json
index 6733275de..c44059030 100644
--- a/content/node.13daae68-e5f9-4295-a6ff-908aae12f012.json
+++ b/content/node.13daae68-e5f9-4295-a6ff-908aae12f012.json
@@ -76,7 +76,7 @@
     ],
     "path": [
         {
-            "alias": "\/podcast\/27-discussing-drupalisms-emma-horrell-and-luke-mccormick",
+            "alias": "\/podcast\/27-discussing-drupalisms",
             "langcode": "en"
         }
     ],
@@ -108,5 +108,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "306b315a-03c4-4f06-a396-cf0906676d47"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 78da3c8ed..bba85c00f 100644
--- a/content/node.13e1b1ea-a0df-43b2-8f1b-e8340bb62df8.json
+++ b/content/node.13e1b1ea-a0df-43b2-8f1b-e8340bb62df8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fec65b7e84bf75434bce2cbc5521ace3",
             "target_type": "feeds_feed",
diff --git a/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json b/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json
index 80020b1af..3687a575a 100644
--- a/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json
+++ b/content/node.140628f4-5b97-4b01-8a55-ca68cf49c635.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dea295dc493bba491afadc1db32d16fe",
             "target_type": "feeds_feed",
diff --git a/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json b/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json
index 187ea346d..ee80fa96f 100644
--- a/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json
+++ b/content/node.141f3c86-ae34-430f-9cba-d1278047fe0d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a09433a4fbfd96fc58654fe54aeeb036",
             "target_type": "feeds_feed",
diff --git a/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json b/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json
index fba09d869..51f96f405 100644
--- a/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json
+++ b/content/node.1420a8f0-0482-4fa6-86ec-876d84c27255.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "506ce77f679ad7914294ef3ac3d0201c",
             "target_type": "feeds_feed",
diff --git a/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json b/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json
index a59c7e681..4123a9171 100644
--- a/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json
+++ b/content/node.1486a3bc-3bf6-436c-a6b9-1dc36dcb505d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1f2cab06d1412951184ea5c3b5d74edb",
             "target_type": "feeds_feed",
diff --git a/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json b/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json
index dd3b41d27..f74692a23 100644
--- a/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json
+++ b/content/node.15237599-15e7-496b-a7e0-c02fddae26f8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fff5236abf836cd7767bdeeb7e9ba028",
             "target_type": "feeds_feed",
diff --git a/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json b/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json
index 1566a161e..1762feb23 100644
--- a/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json
+++ b/content/node.1550e619-abd2-4efe-b941-fd4e42507d51.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dd52b641b6c5a3e8eb19c47343f766c3",
             "target_type": "feeds_feed",
diff --git a/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json b/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json
index 79ca31f11..181099f4f 100644
--- a/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json
+++ b/content/node.1579b5cf-889e-4a7b-98a7-59918359def9.json
@@ -84,7 +84,7 @@
         {
             "value": "<p>I have recently <a href=\"\/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=\"\/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=\"\/atdc\">my free 10-day email course<\/a>.<\/p>",
             "format": "basic_html",
-            "processed": "<p>I have recently <a href=\"\/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=\"\/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=\"\/atdc\">my free 10-day email course<\/a>.<\/p>",
+            "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": ""
         }
     ],
diff --git a/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json b/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json
index 59eae49e5..e83f8130d 100644
--- a/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json
+++ b/content/node.1583ba2e-e791-4f4d-be82-4c59fe51f1b5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "84286e59b43f96ea62a57ef17279149e",
             "target_type": "feeds_feed",
diff --git a/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json b/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json
index e58f83bdd..00618d415 100644
--- a/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json
+++ b/content/node.162509c1-9ef9-4647-9ae5-843e6b214cce.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b2a503f52e0d13b65158e0770ce490d5",
             "target_type": "feeds_feed",
diff --git a/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json b/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json
index fe2c73f46..c31ac1cdc 100644
--- a/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json
+++ b/content/node.166d5baa-74b2-498c-b2cf-a15ddf4df6a0.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "02610d24642398171de58810a96abcd6",
             "target_type": "feeds_feed",
diff --git a/content/node.16846795-5fd0-4a67-a080-edfaa8e20cd8.json b/content/node.16846795-5fd0-4a67-a080-edfaa8e20cd8.json
index 82138cdd0..50c9d8284 100644
--- a/content/node.16846795-5fd0-4a67-a080-edfaa8e20cd8.json
+++ b/content/node.16846795-5fd0-4a67-a080-edfaa8e20cd8.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "a6331245-d56d-44dd-9496-936284f1bc09"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 9b07c1dae..a04f993d4 100644
--- a/content/node.168c59ab-cadd-4dfc-8c72-de82d6578885.json
+++ b/content/node.168c59ab-cadd-4dfc-8c72-de82d6578885.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "238cdb2a724852497414bcfd508b5a90",
             "target_type": "feeds_feed",
diff --git a/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json b/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json
index 97b4aed66..a7bcac25d 100644
--- a/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json
+++ b/content/node.16dc23db-86e4-4c5d-b479-3f92828dae12.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c46666fe3bbd6c27133967d0e0f292cb",
             "target_type": "feeds_feed",
diff --git a/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json b/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json
index c2f314863..d3ca5a1de 100644
--- a/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json
+++ b/content/node.16ed92b5-de67-44e4-b11a-7474081a00d2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/talks\/tdd-test-driven-drupal\">I have a talk about that<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/talks\/tdd-test-driven-drupal\">I have a talk about that<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/talks\/tdd-test-driven-drupal\">I have a talk about that<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f7cd5903bb37498e5fec20b1ac28f287",
             "target_type": "feeds_feed",
diff --git a/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json b/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json
index c6806cf74..350233c1b 100644
--- a/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json
+++ b/content/node.172b603f-fddb-46cc-ac9e-0cd90a339c77.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "896df6011c053cbdee1b18906879608e",
             "target_type": "feeds_feed",
diff --git a/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json b/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json
index 135508711..16fbb6fb3 100644
--- a/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json
+++ b/content/node.178c6bab-7e28-413a-9055-24fac0de0d0a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f438aefd37b258b1946af9f1abcf9bed",
             "target_type": "feeds_feed",
diff --git a/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json b/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json
index 47e5e3ad7..4094c88a0 100644
--- a/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json
+++ b/content/node.179c3eed-b723-4f44-b9d4-398b90b916e7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5f836cbcedf162cecbf20a6f752387dd",
             "target_type": "feeds_feed",
diff --git a/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json b/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json
index 1ac620d59..fdd292906 100644
--- a/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json
+++ b/content/node.17a436ab-84f0-4c0a-9305-b04a9e1883ee.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9fe14e0414ae452819b91e9a2abc8403",
             "target_type": "feeds_feed",
diff --git a/content/node.18cac962-eefd-4506-8efd-cd584f027369.json b/content/node.18cac962-eefd-4506-8efd-cd584f027369.json
index bc9588192..2cbd552bb 100644
--- a/content/node.18cac962-eefd-4506-8efd-cd584f027369.json
+++ b/content/node.18cac962-eefd-4506-8efd-cd584f027369.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "221517dc07bba403f3df3cb3e605aab2",
             "target_type": "feeds_feed",
diff --git a/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json b/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json
index b0b7a2082..2b7283963 100644
--- a/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json
+++ b/content/node.190e33fc-0d42-49fd-8f4d-1cfd174b988a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2b4eb1f8e6b76d78d911e2cbd7350312",
             "target_type": "feeds_feed",
diff --git a/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json b/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json
index 918515210..0a42a4574 100644
--- a/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json
+++ b/content/node.192c6112-5287-46c9-9fed-5260db08a41c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/blog\/uis-ive-rebuilt-tailwind-css\">examples of UIs that I've rebuilt<\/a> and some websites that I show in my <a href=\"/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        ",
+            "value": "\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=\"\/blog\/uis-ive-rebuilt-tailwind-css\">examples of UIs that I've rebuilt<\/a> and some websites that I show in my <a href=\"\/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        ",
             "format": "full_html",
-            "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=\"/blog\/uis-ive-rebuilt-tailwind-css\">examples of UIs that I've rebuilt<\/a> and some websites that I show in my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "942ef7d759d47a0c58947ce472a9986a",
             "target_type": "feeds_feed",
diff --git a/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json b/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json
index 21163f7a4..5e958862c 100644
--- a/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json
+++ b/content/node.19376fcb-fc7a-4b4a-9fea-6865e423519e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a738fae17df1cd911b70ef29ae3283c8",
             "target_type": "feeds_feed",
diff --git a/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json b/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json
index c6976ef10..c55c899b4 100644
--- a/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json
+++ b/content/node.19a48fd0-5e10-496b-b08c-1ed47ad6b2a9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In yesterday's email, I wrote about why <a href=\"/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        ",
+            "value": "\n          <p>In yesterday's email, I wrote about why <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In yesterday's email, I wrote about why <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "227626df1c8fc0c0d8c11465862dad57",
             "target_type": "feeds_feed",
diff --git a/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json b/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json
index 271ae6f7c..d165fac8f 100644
--- a/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json
+++ b/content/node.19ca1b40-02cf-45de-b4bd-4d9a5b5ce7e7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4f25a7d5fdd045a4a767afa851b0d6f0",
             "target_type": "feeds_feed",
diff --git a/content/node.19efa1df-9e8a-4c65-b1e8-55248ac520ed.json b/content/node.19efa1df-9e8a-4c65-b1e8-55248ac520ed.json
index f67e80f94..77eb17c1d 100644
--- a/content/node.19efa1df-9e8a-4c65-b1e8-55248ac520ed.json
+++ b/content/node.19efa1df-9e8a-4c65-b1e8-55248ac520ed.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "9e99db9e-83af-4d55-9c98-ba53ab2c2ab6"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 aa0df3377..1e2a19bb0 100644
--- a/content/node.1a024983-b73b-4b2c-a350-db9152de27a9.json
+++ b/content/node.1a024983-b73b-4b2c-a350-db9152de27a9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "de98c57a7d583eb2f17a08ed813ccc09",
             "target_type": "feeds_feed",
diff --git a/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json b/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json
index bd333570a..24cb5d3c2 100644
--- a/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json
+++ b/content/node.1aa7a4d1-08a8-4cb0-99ba-62e279517b4b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ded9b2a6eb8ff4129f9653ceb3555f58",
             "target_type": "feeds_feed",
diff --git a/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json b/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json
index 70746c31a..8552fc709 100644
--- a/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json
+++ b/content/node.1b73b0cd-a0e3-443a-bc6a-edfcbc8d5481.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1a79c3d8c5b39c15a45407dd2f8915dd",
             "target_type": "feeds_feed",
diff --git a/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json b/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json
index a382984cb..9b9f40104 100644
--- a/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json
+++ b/content/node.1bac9c8b-18bd-4f09-a8ae-867c43798762.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "40970926a00c3a7ef56c821881cbbc63",
             "target_type": "feeds_feed",
diff --git a/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json b/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json
index 5dfe5ad9d..9009d87b2 100644
--- a/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json
+++ b/content/node.1c0ccb4b-9b26-4078-94bb-31e98017e8f2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/atdc\">free email course on automated testing in Drupal<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/atdc\">free email course on automated testing in Drupal<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/atdc\">free email course on automated testing in Drupal<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "70254b7f809c1c35bcb40109b901f96e",
             "target_type": "feeds_feed",
diff --git a/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json b/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json
index 3f6583517..fc96cfe6a 100644
--- a/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json
+++ b/content/node.1c357f25-ed1e-406f-9899-ec9017548800.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "620e6d173305d1f917ba7bae4ae3d704",
             "target_type": "feeds_feed",
diff --git a/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json b/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json
index 2e86ca34c..c5f346b51 100644
--- a/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json
+++ b/content/node.1c57b2eb-1206-4833-afb0-a65ec3f432a0.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "99c8f2f1d316c939a4a59c03a17de896",
             "target_type": "feeds_feed",
diff --git a/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json b/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json
index e03b03982..a738246d7 100644
--- a/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json
+++ b/content/node.1cfd5a5b-cd0f-4a6e-8108-c16bda75ebee.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6b223577d98aafcacf18ecbf423a3497",
             "target_type": "feeds_feed",
diff --git a/content/node.1d491da6-0523-4709-aa35-17df110f5506.json b/content/node.1d491da6-0523-4709-aa35-17df110f5506.json
index ecf731fae..d2d5a3c56 100644
--- a/content/node.1d491da6-0523-4709-aa35-17df110f5506.json
+++ b/content/node.1d491da6-0523-4709-aa35-17df110f5506.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "c0470b91-e700-4602-9e93-07705681d679"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 49f093b8e..514872018 100644
--- a/content/node.1d61b9ee-e6de-4db6-8782-68eba42d357a.json
+++ b/content/node.1d61b9ee-e6de-4db6-8782-68eba42d357a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Last month, I wrote an email explaining <a href=\"/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=\"/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=\"/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        ",
+            "value": "\n          <p>Last month, I wrote an email explaining <a href=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Last month, I wrote an email explaining <a href=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4bbe23be0133c280a8c7e9fe479570ad",
             "target_type": "feeds_feed",
diff --git a/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json b/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json
index 01f6fdb1e..edc9ab693 100644
--- a/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json
+++ b/content/node.1d8c474a-de0c-417c-bc05-179eef2e9bfb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "44eace8ddc51bab34e23bb1cc0825908",
             "target_type": "feeds_feed",
diff --git a/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json b/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json
index e397981c3..95eda3da2 100644
--- a/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json
+++ b/content/node.1d8e5d0f-d0d9-4e9d-8c05-87ab91016bd5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "290ba77a217288ad367ab07bf02a2265",
             "target_type": "feeds_feed",
diff --git a/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json b/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json
index d01ed07a4..e4fd0c4f2 100644
--- a/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json
+++ b/content/node.1e0a6a6f-1fd8-43fa-9cbe-dc5e7a42ab89.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "765bdd698c2180895d0727169bf613cb",
             "target_type": "feeds_feed",
diff --git a/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json b/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json
index 9df9afbd5..c31e453eb 100644
--- a/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json
+++ b/content/node.1e59e156-0e2c-4f6d-a828-030d1322fde6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In <a href=\"/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        ",
+            "value": "\n          <p>In <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "630fb2a05269acd6616e9f0d51b2c360",
             "target_type": "feeds_feed",
diff --git a/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json b/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json
index e015d77d0..0268e6088 100644
--- a/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json
+++ b/content/node.1f3f5a8f-412f-4da1-8e7a-4303962079d1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p><a href=\"\/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=\"\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "316effd21316b7cbda5678cf691fc683",
             "target_type": "feeds_feed",
diff --git a/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json b/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json
index 258c6858b..1eda3d0f2 100644
--- a/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json
+++ b/content/node.1f9686d7-f067-4253-88a6-639125a625a6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "37e18d6b3d8c61b4ed2592c0d3ede8c2",
             "target_type": "feeds_feed",
diff --git a/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json b/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json
index 5c4e3a4be..f2874169a 100644
--- a/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json
+++ b/content/node.1f99779d-11cb-4679-9a0e-fce1be58f6b7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a039f34850bd65b5d0ce42db6cc13f1b",
             "target_type": "feeds_feed",
diff --git a/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json b/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json
index 4c38493c7..4d3ae95ba 100644
--- a/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json
+++ b/content/node.1fd87ecf-4269-4874-859e-d49c238694bf.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "db65f35f5c7767e34b717942905448f4",
             "target_type": "feeds_feed",
diff --git a/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json b/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json
index 6116d1959..89e8c1b69 100644
--- a/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json
+++ b/content/node.20010c04-2f30-4772-9041-6f7e836158f8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/\/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        ",
+            "value": "\n          <p><a href=\"\/\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/\/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b758f9153177dd2e50122508bd8103c6",
             "target_type": "feeds_feed",
diff --git a/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json b/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json
index 73c063b52..7b2c53af4 100644
--- a/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json
+++ b/content/node.207113dd-f0f6-4e8a-ab98-6c6b4a53c032.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "920f52af5b2ff64ff720e6726ce03219",
             "target_type": "feeds_feed",
diff --git a/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json b/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json
index 429c65338..e1239776a 100644
--- a/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json
+++ b/content/node.2142e27d-5c96-4c16-9650-dc47b2b85888.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "898a4ca4ca6f3d15e2c342efb0420bee",
             "target_type": "feeds_feed",
diff --git a/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json b/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json
index 1e2db751b..9a5765b88 100644
--- a/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json
+++ b/content/node.216f7a7d-663b-42a6-b430-3817a1180dbd.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5d155c99bbf381198855ff0d06445dcc",
             "target_type": "feeds_feed",
diff --git a/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json b/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json
index 085b1e092..3eb3f32ab 100644
--- a/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json
+++ b/content/node.217616ab-32cb-4c7f-b51c-7da3974de4e2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "03e072b02f75cb69315b1b458f6b6e71",
             "target_type": "feeds_feed",
diff --git a/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json b/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json
index 398823512..c8341089c 100644
--- a/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json
+++ b/content/node.21a60676-e555-4b27-9cc6-3fdd14f5d3cb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "75d576395418eeee1ebec49730c22762",
             "target_type": "feeds_feed",
diff --git a/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json b/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json
index 0206da4d0..5207f5e52 100644
--- a/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json
+++ b/content/node.21f3f75a-e37f-44b6-81f5-337cc11e5eac.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d5f31c0bb830b46174ae9f0b2d15e7ea",
             "target_type": "feeds_feed",
diff --git a/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json b/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json
index e42191fb9..8968af69f 100644
--- a/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json
+++ b/content/node.2234ff18-11e6-4689-9316-cae9fb3f0579.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6779f3fdf5c222d23fde37cb0801d08c",
             "target_type": "feeds_feed",
diff --git a/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json b/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json
index 94b7fcc62..5ff3f5ea6 100644
--- a/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json
+++ b/content/node.225110fb-82d3-4056-a394-0612d80e37ec.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As someone who develops with open-source software such as Drupal, Symfony, and Sculpin and uses Linux to <a href=\"/daily\/2024\/11\/28\/running-nixos-in-the-cloud\">host my applications<\/a> and <a href=\"/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=\"/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        ",
+            "value": "\n          <p>As someone who develops with open-source software such as Drupal, Symfony, and Sculpin and uses Linux to <a href=\"\/daily\/2024\/11\/28\/running-nixos-in-the-cloud\">host my applications<\/a> and <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As someone who develops with open-source software such as Drupal, Symfony, and Sculpin and uses Linux to <a href=\"/daily\/2024\/11\/28\/running-nixos-in-the-cloud\">host my applications<\/a> and <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "826ea7f42a178becea87291123dedc78",
             "target_type": "feeds_feed",
diff --git a/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json b/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json
index a477b97f0..71826fa9d 100644
--- a/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json
+++ b/content/node.2258201f-7beb-4b2a-8a52-ea31c09de73f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0d32d809ef0473c3b8fd336040076cae",
             "target_type": "feeds_feed",
diff --git a/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json b/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json
index 02de1cd3b..aeffd6092 100644
--- a/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json
+++ b/content/node.22cf1c29-6d70-49ea-87b4-0dd2bcdb9952.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "31f3de322f3c108fbaf235ca30453bf5",
             "target_type": "feeds_feed",
diff --git a/content/node.22e50919-7f11-45ed-881e-31482670f416.json b/content/node.22e50919-7f11-45ed-881e-31482670f416.json
index 43198b4d4..13d9a9144 100644
--- a/content/node.22e50919-7f11-45ed-881e-31482670f416.json
+++ b/content/node.22e50919-7f11-45ed-881e-31482670f416.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c91a13187040e9edc5a979e4742e7619",
             "target_type": "feeds_feed",
diff --git a/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json b/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json
index ceed5a4cc..ec7400802 100644
--- a/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json
+++ b/content/node.22f6723d-c781-4548-a2cf-3b642e91b4ad.json
@@ -76,16 +76,15 @@
     ],
     "path": [
         {
-            "alias": "",
-            "pid": null,
+            "alias": "\/daily\/2025\/05\/27\/using-ai-web-coding-luke-mccormick-re-uploaded",
             "langcode": "en"
         }
     ],
     "body": [
         {
-            "value": "<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=\"/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>",
+            "value": "<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=\"\/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>",
             "format": "basic_html",
-            "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=\"/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>",
+            "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": ""
         }
     ],
diff --git a/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json b/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json
index 9d6c5d6a7..e36341006 100644
--- a/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json
+++ b/content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a3e94e918c387456f8b5d5871cf5e306",
             "target_type": "feeds_feed",
diff --git a/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json b/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json
index e99b079fc..8b7bee7cf 100644
--- a/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json
+++ b/content/node.23bff06b-34e8-4f9a-ae67-4405393c874c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e95a217380424b7821a1a9e61d048019",
             "target_type": "feeds_feed",
diff --git a/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json b/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json
index 116755317..154a74d0b 100644
--- a/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json
+++ b/content/node.2492a986-0932-437a-a7b4-414dbebb4a2a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0c8202093b9bab15e532858ca4d09169",
             "target_type": "feeds_feed",
diff --git a/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json b/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json
index 804241053..d6bdc1d63 100644
--- a/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json
+++ b/content/node.251a41b5-0dfe-4c7b-abe4-9b28d0a52a22.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/building-static-websites-sculpin\">building websites with Sculpin<\/a> which I may submit to some upcoming conferences.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/building-static-websites-sculpin\">building websites with Sculpin<\/a> which I may submit to some upcoming conferences.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/building-static-websites-sculpin\">building websites with Sculpin<\/a> which I may submit to some upcoming conferences.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6b0cc2a798390fc93ca034bf92dc6df9",
             "target_type": "feeds_feed",
diff --git a/content/node.25294346-8919-49c4-affa-d87616ed3df5.json b/content/node.25294346-8919-49c4-affa-d87616ed3df5.json
index e6ced3e5a..71a1d3dbe 100644
--- a/content/node.25294346-8919-49c4-affa-d87616ed3df5.json
+++ b/content/node.25294346-8919-49c4-affa-d87616ed3df5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fde61ed0e072a1110a954bab54a9eb1a",
             "target_type": "feeds_feed",
diff --git a/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json b/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json
index ba010de74..13782508d 100644
--- a/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json
+++ b/content/node.2530ef2e-0df9-4364-8e08-5d872cd9621e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8a91a1475b9f9764550b81c084c64421",
             "target_type": "feeds_feed",
diff --git a/content/node.25347778-fdbf-4a8e-80f9-2d7e655391fe.json b/content/node.25347778-fdbf-4a8e-80f9-2d7e655391fe.json
index d49199afc..a6670519b 100644
--- a/content/node.25347778-fdbf-4a8e-80f9-2d7e655391fe.json
+++ b/content/node.25347778-fdbf-4a8e-80f9-2d7e655391fe.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 9d878e424..2011f33ac 100644
--- a/content/node.25833838-38b9-414d-bca6-de0bf5c2ac28.json
+++ b/content/node.25833838-38b9-414d-bca6-de0bf5c2ac28.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a75b22468e6abeb329819fa5a65c2bc1",
             "target_type": "feeds_feed",
diff --git a/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json b/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json
index ab6e3c5db..23e404d17 100644
--- a/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json
+++ b/content/node.26335c09-8a6a-461d-85c7-f0dbe37bb890.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b60d333d6f7149040d0e846c6f1c03b5",
             "target_type": "feeds_feed",
diff --git a/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json b/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json
index bf43d84d5..aff1ff837 100644
--- a/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json
+++ b/content/node.266918e6-af3d-48f8-89d4-657ff2214626.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2023\/12\/14\/save-time-and-effort-with-drupal-distributions\">drupal distribution<\/a><\/p>\n\n        ",
+            "value": "\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=\"\/daily\/2023\/12\/14\/save-time-and-effort-with-drupal-distributions\">drupal distribution<\/a><\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2023\/12\/14\/save-time-and-effort-with-drupal-distributions\">drupal distribution<\/a><\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e35818bb9ede99b340e53301552fc08c",
             "target_type": "feeds_feed",
diff --git a/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json b/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json
index 296bdb1db..b82177553 100644
--- a/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json
+++ b/content/node.26e4ff33-b5fd-47b4-926e-fc5b78677c88.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a5dc3593db0a86eecc10e4b173ce6607",
             "target_type": "feeds_feed",
diff --git a/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json b/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json
index dc13db524..ec1e0c0dc 100644
--- a/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json
+++ b/content/node.26f6be13-6309-441d-977f-eb84684b8a2f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>The <a href=\"/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        ",
+            "value": "\n          <p>The <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>The <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "393d67cc8b24f5363cab347c90d38206",
             "target_type": "feeds_feed",
diff --git a/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json b/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json
index 8ba69002d..fa744dce1 100644
--- a/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json
+++ b/content/node.27159a73-e3ac-4fa9-b18c-2f70157e31d7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0e6ead78bb287e96b7e18dc6b884ec14",
             "target_type": "feeds_feed",
diff --git a/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json b/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json
index 01b378773..63a45db53 100644
--- a/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json
+++ b/content/node.274408ed-379c-4eaf-914d-7f5599f513d3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f0ce2f69b9db5c6cc971459f685e5a9c",
             "target_type": "feeds_feed",
diff --git a/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json b/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json
index bbc9bab5c..7c62d1468 100644
--- a/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json
+++ b/content/node.278813c0-1c8b-4558-bf13-3c2f03acaeb6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "18059b58dd6e070d2ab12d72dcee5cd6",
             "target_type": "feeds_feed",
diff --git a/content/node.27926937-f426-490f-ac0a-454d9d2def37.json b/content/node.27926937-f426-490f-ac0a-454d9d2def37.json
index ae1ef9f99..dde878648 100644
--- a/content/node.27926937-f426-490f-ac0a-454d9d2def37.json
+++ b/content/node.27926937-f426-490f-ac0a-454d9d2def37.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f97cc46c7cd91b966de8bd195077270d",
             "target_type": "feeds_feed",
diff --git a/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json b/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json
index d51f023f8..94bbf5ea0 100644
--- a/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json
+++ b/content/node.283e9379-f264-4191-8bbd-2cd8393c395b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/27-drupalisms\">Listen to the episode here<\/a>.<\/p>\n\n<p>If you want to be a guest on the <a href=\"/podcast\">Beyond Blocks podcast<\/a>, reply and let me know.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/27-drupalisms\">Listen to the episode here<\/a>.<\/p>\n\n<p>If you want to be a guest on the <a href=\"\/podcast\">Beyond Blocks podcast<\/a>, reply and let me know.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/27-drupalisms\">Listen to the episode here<\/a>.<\/p>\n\n<p>If you want to be a guest on the <a href=\"/podcast\">Beyond Blocks podcast<\/a>, reply and let me know.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "67a1fcf34fe0816f85b2a62cf901f80c",
             "target_type": "feeds_feed",
diff --git a/content/node.2885a415-17fb-4374-8070-0be55407af6c.json b/content/node.2885a415-17fb-4374-8070-0be55407af6c.json
index 2e0c74781..115ff9127 100644
--- a/content/node.2885a415-17fb-4374-8070-0be55407af6c.json
+++ b/content/node.2885a415-17fb-4374-8070-0be55407af6c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Since I posted about <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Since I posted about <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Since I posted about <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "df04ab02769a8e43f0227ca122c3d48c",
             "target_type": "feeds_feed",
diff --git a/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json b/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json
index fdd707273..db968cc6e 100644
--- a/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json
+++ b/content/node.290e62f9-ffc1-4420-91f7-decda6410276.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>When you're working on a task - <a href=\"/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        ",
+            "value": "\n          <p>When you're working on a task - <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>When you're working on a task - <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a06b7f39d8e65a002d540490d71af34c",
             "target_type": "feeds_feed",
diff --git a/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json b/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json
index c34113988..c20836d0c 100644
--- a/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json
+++ b/content/node.294ea660-e93e-4596-ad81-5a53d2ba2555.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a791b47a1f23adb15571ee034ecf7976",
             "target_type": "feeds_feed",
diff --git a/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json b/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json
index 3214e2396..b5d007c18 100644
--- a/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json
+++ b/content/node.2959438c-8c12-49c7-84a2-d9ea9bf338e6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As I said <a href=\"/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        ",
+            "value": "\n          <p>As I said <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As I said <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9244db868e27ad48ece974399c743c82",
             "target_type": "feeds_feed",
diff --git a/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json b/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json
index dbe7df21e..cff40dda6 100644
--- a/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json
+++ b/content/node.298d7816-0b4a-449e-a78d-fcf973f24bf0.json
@@ -82,9 +82,9 @@
     ],
     "body": [
         {
-            "value": "<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=\"/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>",
+            "value": "<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=\"\/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>",
             "format": "basic_html",
-            "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=\"/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>",
+            "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": ""
         }
     ],
diff --git a/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json b/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json
index a9fe5b5eb..0252f7ebc 100644
--- a/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json
+++ b/content/node.29a700d5-082c-4f6b-bafd-f4c4e1486624.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "58a70b657ecf7c7093121dc7fa471790",
             "target_type": "feeds_feed",
diff --git a/content/node.29ab0d54-5f71-4615-b391-164735cada18.json b/content/node.29ab0d54-5f71-4615-b391-164735cada18.json
index d0f287a32..90a84c9e0 100644
--- a/content/node.29ab0d54-5f71-4615-b391-164735cada18.json
+++ b/content/node.29ab0d54-5f71-4615-b391-164735cada18.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/20-george-gordon\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/20-george-gordon\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/20-george-gordon\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6ec6e1f6816951ce4fdbbb57c251fbf6",
             "target_type": "feeds_feed",
diff --git a/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json b/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json
index ede2dfc2b..4013d9e39 100644
--- a/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json
+++ b/content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6b4f2625c11b6774d4cd0648c3870116",
             "target_type": "feeds_feed",
diff --git a/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json b/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json
index 08424d603..2afef307e 100644
--- a/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json
+++ b/content/node.2a816ad4-7e24-4082-83c3-b93490294170.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2f6f3299f4d4c9892dbdc2a885fcef62",
             "target_type": "feeds_feed",
diff --git a/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json b/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json
index 5c2d747fd..12a534d8d 100644
--- a/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json
+++ b/content/node.2a8afca0-9193-4e69-86bb-8d1d3639d6e1.json
@@ -84,7 +84,7 @@
         {
             "value": "<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=\"\/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=\"\/daily\/2025\/04\/17\/incrementally\">migrating incrementally<\/a> and switching more sections to Tome.<\/p>",
             "format": "basic_html",
-            "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=\"\/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=\"\/daily\/2025\/04\/17\/incrementally\">migrating incrementally<\/a> and switching more sections to Tome.<\/p>",
+            "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": ""
         }
     ],
diff --git a/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json b/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json
index a732ea624..8a69f6180 100644
--- a/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json
+++ b/content/node.2ae805e1-cc34-42b5-9dae-7b3c189fdec5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "87cacdc5c22db3ecc6f35586d0a72902",
             "target_type": "feeds_feed",
diff --git a/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json b/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json
index 5e26c7975..95ec8a84c 100644
--- a/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json
+++ b/content/node.2aed4449-60c0-45a6-884d-73eee930eed8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f39decae02bf9939850675018c7bda4b",
             "target_type": "feeds_feed",
diff --git a/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json b/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json
index aab8c443d..4ea4bc22f 100644
--- a/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json
+++ b/content/node.2b55b7dd-2287-462d-a951-62603ce334bd.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c2e765d3c10eb420e55c4f3c307a115f",
             "target_type": "feeds_feed",
diff --git a/content/node.2b747510-63ea-489c-88de-af7995d94d45.json b/content/node.2b747510-63ea-489c-88de-af7995d94d45.json
index 5c3bccdee..9482caf15 100644
--- a/content/node.2b747510-63ea-489c-88de-af7995d94d45.json
+++ b/content/node.2b747510-63ea-489c-88de-af7995d94d45.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4ebd7a5d82aef0e0b2dc79ae2d389b04",
             "target_type": "feeds_feed",
diff --git a/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json b/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json
index 93accb2bc..29825ffeb 100644
--- a/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json
+++ b/content/node.2be6f96b-eecb-4205-9ca9-b364196535ab.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "19f4733147fd635802fdcc6ed648d534",
             "target_type": "feeds_feed",
diff --git a/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json b/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json
index ccb3f640c..02051cac6 100644
--- a/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json
+++ b/content/node.2bf48b4d-12c8-43be-9f95-c4c54fe34712.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f1921114d6e52e6b1147419cd0c37c8c",
             "target_type": "feeds_feed",
diff --git a/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json b/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json
index e73bd16eb..286233263 100644
--- a/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json
+++ b/content/node.2c022817-6bf1-4a2f-809e-8895c72a0e03.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Before <a href=\"/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        ",
+            "value": "\n          <p>Before <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Before <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cd0913ec770f5778cd0c8fc66aca2797",
             "target_type": "feeds_feed",
diff --git a/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json b/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json
index 3e3462021..d3a0820b0 100644
--- a/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json
+++ b/content/node.2c5bbb3d-d8f4-496c-ae72-b739f5b1a90c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">other contributed projects on Drupal.org<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">other contributed projects on Drupal.org<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">other contributed projects on Drupal.org<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "31597e09d4634a2345186aa8fe52bac9",
             "target_type": "feeds_feed",
diff --git a/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json b/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json
index 7b99eb45e..91d195c61 100644
--- a/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json
+++ b/content/node.2c83980a-deb6-4e52-95a8-a87155cc3e2a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b0878912a8e161c77d109a47fd2b797b",
             "target_type": "feeds_feed",
diff --git a/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json b/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json
index 9173c72ed..c154c083a 100644
--- a/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json
+++ b/content/node.2cd07893-c184-4369-bbeb-45c2e9e055a7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f44966eb1681af53eb81ff390ccadd27",
             "target_type": "feeds_feed",
diff --git a/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json b/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json
index a320fa764..d1e6dddc4 100644
--- a/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json
+++ b/content/node.2cf41a31-2530-4b4d-98d1-4f8fdf7e546c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6863b2793bb9008b2672513b2cf9f503",
             "target_type": "feeds_feed",
diff --git a/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json b/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json
index 575bef146..ee2f32ce8 100644
--- a/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json
+++ b/content/node.2d05cfa9-d5cf-41df-ba50-2c55b776f1f5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/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        ",
+            "value": "\n          <p><a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1acf10e20cf336c87647e51e764cdd12",
             "target_type": "feeds_feed",
diff --git a/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json b/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json
index bc2a79175..3a2bd390d 100644
--- a/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json
+++ b/content/node.2d0b16d8-0781-411e-a06b-f62bf9a9c253.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "53ec3852bd16e9152d04d6bd43553d18",
             "target_type": "feeds_feed",
diff --git a/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json b/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json
index 1dec036d2..5faf98acd 100644
--- a/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json
+++ b/content/node.2d89873f-8f15-4e92-9f72-1a83855d3d82.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f6c37d9d9fa156de34d1f69cd5c937cc",
             "target_type": "feeds_feed",
diff --git a/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json b/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json
index f0fb05f56..0b747815f 100644
--- a/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json
+++ b/content/node.2da2e369-297c-46bd-83e5-8fd16d4c85c1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In the most recent episode of the <a href=\"/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=\"/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        ",
+            "value": "\n          <p>In the most recent episode of the <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In the most recent episode of the <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5c9c6d0aa35f183dfbf3569302fc4c45",
             "target_type": "feeds_feed",
diff --git a/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json b/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json
index d7d70cdcf..d505527a4 100644
--- a/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json
+++ b/content/node.2e4827a4-0d9c-458c-86eb-d6b40f18d608.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fb957020708c21d55d5d99c008e1797b",
             "target_type": "feeds_feed",
diff --git a/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json b/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json
index eb0c4e985..8d867fef3 100644
--- a/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json
+++ b/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3276725453a049753043e098fb26dc65",
             "target_type": "feeds_feed",
diff --git a/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json b/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json
index ef2a4733f..964216016 100644
--- a/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json
+++ b/content/node.2f07215e-0ea6-4afe-8c19-ed0ed81246d6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3ae42369d30ace581b59bd14ab59566a",
             "target_type": "feeds_feed",
diff --git a/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json b/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json
index fd93fdd8d..aae63e0d0 100644
--- a/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json
+++ b/content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5b63bfce940fe7e208810bb77d3cd2d6",
             "target_type": "feeds_feed",
diff --git a/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json b/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json
index 2239c8e33..8ef452fa1 100644
--- a/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json
+++ b/content/node.2f503fac-0d18-436b-a5d1-64263c5fc616.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6be3e710df2ce66a5d47787fde5a3e20",
             "target_type": "feeds_feed",
diff --git a/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json b/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json
index cd8f6e0d1..3b9f9671c 100644
--- a/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json
+++ b/content/node.2f576a37-bd5a-4894-9340-1e69775c8b68.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e5e300294005922421e456824c17e754",
             "target_type": "feeds_feed",
diff --git a/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json b/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json
index dee27d492..cdc1ce5e6 100644
--- a/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json
+++ b/content/node.2facc6b4-52da-4fc5-b957-e29d06f19ae8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a062ba3a2fcfeca0edc718bd206fe2b6",
             "target_type": "feeds_feed",
diff --git a/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json b/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json
index f19046a17..a36e29788 100644
--- a/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json
+++ b/content/node.2fed4dad-d36f-47f1-9671-07dc97cfb50c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0e528eb2f03aa1240b5f28b0ef0f38eb",
             "target_type": "feeds_feed",
diff --git a/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json b/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json
index 9e4f41823..a4669fc06 100644
--- a/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json
+++ b/content/node.301495eb-5851-4dce-9625-779ebb8d7b2b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "618399863f1103ba0fb1c30d07467918",
             "target_type": "feeds_feed",
diff --git a/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json b/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json
index 1a776dc88..d65502e11 100644
--- a/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json
+++ b/content/node.31026a42-b854-4517-b2d0-790036cfe6ad.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e672c406c3284040f0cc248f0e94010b",
             "target_type": "feeds_feed",
diff --git a/content/node.312fd370-dae0-41b9-977f-282fc553e701.json b/content/node.312fd370-dae0-41b9-977f-282fc553e701.json
index 3f39a21c0..668b0adef 100644
--- a/content/node.312fd370-dae0-41b9-977f-282fc553e701.json
+++ b/content/node.312fd370-dae0-41b9-977f-282fc553e701.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "70de2df26133c67db29db3a24a4e7e6a",
             "target_type": "feeds_feed",
diff --git a/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json b/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json
index 40d0adb98..ca3b1083f 100644
--- a/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json
+++ b/content/node.3179746f-a523-4f4d-8bef-44d0c117cb43.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fd6b39dc43f5f73bcb60ca70e2547173",
             "target_type": "feeds_feed",
diff --git a/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json b/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json
index ede83e6e3..4093c80eb 100644
--- a/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json
+++ b/content/node.32313c89-b894-4ae7-b55d-a9bbd6af6dc6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6264aa9a95fe638fa46104484949a1b4",
             "target_type": "feeds_feed",
diff --git a/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json b/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json
index c3d5d81df..014c44358 100644
--- a/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json
+++ b/content/node.323bc6bc-069b-497b-9f64-d64c21bdba79.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d430f601217ebbf8a937cf42e8daac88",
             "target_type": "feeds_feed",
diff --git a/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json b/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json
index 4b5780b41..ad391d185 100644
--- a/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json
+++ b/content/node.32591463-ab8b-4210-84ca-419bb69439c4.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9814fa80db8f88e683db868e11d9d67b",
             "target_type": "feeds_feed",
diff --git a/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json b/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json
index aa8cda042..7307e27dd 100644
--- a/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json
+++ b/content/node.3373d8dc-7c1d-477f-8628-f3029228b9c4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently started <a href=\"/daily\/2025\/04\/07\/nix-rst2pdf\">using Nix to build my PDF presentation slides<\/a> that <a href=\"/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        ",
+            "value": "\n          <p>I recently started <a href=\"\/daily\/2025\/04\/07\/nix-rst2pdf\">using Nix to build my PDF presentation slides<\/a> that <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently started <a href=\"/daily\/2025\/04\/07\/nix-rst2pdf\">using Nix to build my PDF presentation slides<\/a> that <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "663165d347672170986b3ba5d0f0ac13",
             "target_type": "feeds_feed",
diff --git a/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json b/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json
index 6e21c1666..7b23a54ef 100644
--- a/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json
+++ b/content/node.33bea7ca-ccf4-4865-bc17-314ce54b6988.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as PHP, JavaScript, HTML, CSS, etc, I write a lot of Bash scripts.<\/p>\n\n<p>From <a href=\"/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        ",
+            "value": "\n          <p>As well as PHP, JavaScript, HTML, CSS, etc, I write a lot of Bash scripts.<\/p>\n\n<p>From <a href=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d8356a3f3c57c5eb0702b65d33904107",
             "target_type": "feeds_feed",
diff --git a/content/node.33ea9079-3c84-410b-b568-eeff8c70a41f.json b/content/node.33ea9079-3c84-410b-b568-eeff8c70a41f.json
index 98fbff0a2..c2351a7c1 100644
--- a/content/node.33ea9079-3c84-410b-b568-eeff8c70a41f.json
+++ b/content/node.33ea9079-3c84-410b-b568-eeff8c70a41f.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "43995889-d61c-4934-b644-52c9d3fee4d6"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 69f20c94e..404772450 100644
--- a/content/node.3422a295-b8a9-43a0-9a03-a54d77e52513.json
+++ b/content/node.3422a295-b8a9-43a0-9a03-a54d77e52513.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "622d843638b7ecbce4c0a0e042ea0b2e",
             "target_type": "feeds_feed",
diff --git a/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json b/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json
index 268151f6d..72c62719b 100644
--- a/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json
+++ b/content/node.34be6fed-cd1a-4796-adb8-577340a359b4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I said that <a href=\"/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        ",
+            "value": "\n          <p>Yesterday, I said that <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I said that <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c6b94af805606062e0a2afbdef9c24fc",
             "target_type": "feeds_feed",
diff --git a/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json b/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json
index df1c52b44..f43b53254 100644
--- a/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json
+++ b/content/node.34e3bc00-ec41-4e3a-986d-af500b03fc5c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0c1e2de02ecb6e43c1e99c96b2fed971",
             "target_type": "feeds_feed",
diff --git a/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json b/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json
index bb3604a04..5d5dc08cd 100644
--- a/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json
+++ b/content/node.357d3d3d-4029-4c4f-81b3-ed484ab03ad8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "01eb9599a4993e6a38dff0ff03338270",
             "target_type": "feeds_feed",
diff --git a/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json b/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json
index 9c595d5d0..077c20ceb 100644
--- a/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json
+++ b/content/node.358edef5-5436-46ca-a90c-4d691ea7c281.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3b4ab476b38477647ebc719045e413e0",
             "target_type": "feeds_feed",
diff --git a/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json b/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json
index ccbc04d2f..8c4419cef 100644
--- a/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json
+++ b/content/node.362530ad-9f84-49c4-a8cb-bea45c77c474.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "aa7f86148acbd8f7d810a7b26d5bc29b",
             "target_type": "feeds_feed",
diff --git a/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json b/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json
index 323c7a70a..6427c08c4 100644
--- a/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json
+++ b/content/node.3681f8cd-22d5-4c2c-b03f-a751bc39753d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In <a href=\"/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        ",
+            "value": "\n          <p>In <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "486689fda2edf70f316d73b2d3cd04a9",
             "target_type": "feeds_feed",
diff --git a/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json b/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json
index e9ea267a8..62bf73750 100644
--- a/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json
+++ b/content/node.369e9679-fef1-4678-aab9-7edcb39f5533.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6aba0a6c06896212f2bad2652c917717",
             "target_type": "feeds_feed",
diff --git a/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json b/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json
index 5f19b3114..ab53abe12 100644
--- a/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json
+++ b/content/node.36d7f751-faeb-48a4-9fb3-fc8248bb515c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1a504b384817d66ba5d480432140f3aa",
             "target_type": "feeds_feed",
diff --git a/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json b/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json
index e119b34bb..221d81fb9 100644
--- a/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json
+++ b/content/node.38522a11-5473-4584-a8f0-c9097a843c9b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b9286b595be8e5830126c8065b86f549",
             "target_type": "feeds_feed",
diff --git a/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json b/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json
index 24efc5b9e..03e3fbae8 100644
--- a/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json
+++ b/content/node.38535020-c00e-4720-8534-73346ff7cb0d.json
@@ -84,7 +84,7 @@
         {
             "value": "<p>Once you've <a href=\"\/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>",
             "format": "basic_html",
-            "processed": "<p>Once you've <a href=\"\/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>",
+            "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": ""
         }
     ],
diff --git a/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json b/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json
index 0f37ac7e1..94c47404b 100644
--- a/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json
+++ b/content/node.38988766-4898-4aec-a987-c189ae1ea6c6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a630770a77303507c11aab1e65b36b5e",
             "target_type": "feeds_feed",
diff --git a/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json b/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json
index 670ca8e6e..2976a871c 100644
--- a/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json
+++ b/content/node.391f650b-0f52-43f6-b3f3-bd7fbca1c11e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday's email talked about <a href=\"/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        ",
+            "value": "\n          <p>Yesterday's email talked about <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday's email talked about <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e2137fff0c7d5222b90615f0e322973b",
             "target_type": "feeds_feed",
diff --git a/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json b/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json
index bd0c16e4f..7fc8740a0 100644
--- a/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json
+++ b/content/node.3933cd74-d4f5-4129-b3a1-71d573c5bf85.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b89a2eb3b71c7524ba4153e60220af05",
             "target_type": "feeds_feed",
diff --git a/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json b/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json
index e1af8c434..5d3e46770 100644
--- a/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json
+++ b/content/node.394246dc-42f8-4fbd-987c-7b62c47b9f06.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5297a15011e2b7e487d8a29171c25b19",
             "target_type": "feeds_feed",
diff --git a/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json b/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json
index 87aba8a72..ee435f7a3 100644
--- a/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json
+++ b/content/node.39865a2b-287b-4dbc-b8dc-8af202d1a4ab.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9d8842c7057445df7a5341831b17c570",
             "target_type": "feeds_feed",
diff --git a/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json b/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json
index 73b594e1d..efac4a2fb 100644
--- a/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json
+++ b/content/node.39db6489-2e23-4cb3-a0be-a4e78a2e9142.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f5ae32e6a60dafd8afa4ab8aa2073638",
             "target_type": "feeds_feed",
diff --git a/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json b/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json
index 6dd6ae111..87e76d1b4 100644
--- a/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json
+++ b/content/node.3a13004e-2245-425f-8080-0b98e161bcb0.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2241d99c8a6cb9f5e690ba3e1a835383",
             "target_type": "feeds_feed",
diff --git a/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json b/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json
index aa40ecbc7..23c2fb118 100644
--- a/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json
+++ b/content/node.3b090ba6-775a-44a1-bc43-c6807380fb59.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "da68f3e7c31ad8f0011576d75e320bd3",
             "target_type": "feeds_feed",
diff --git a/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json b/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json
index 3fe67894c..6e5b2cbdf 100644
--- a/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json
+++ b/content/node.3b6973c4-bca5-4e8a-88a2-dc397ec1a691.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6626dc792ceb7d83e35859940d8a2c43",
             "target_type": "feeds_feed",
diff --git a/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json b/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json
index 21d576b66..80fd5e6b8 100644
--- a/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json
+++ b/content/node.3bb4452f-5bd7-4cce-8ec8-d68610e00b92.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f2a468fba8e2f7e05ff09b2678031534",
             "target_type": "feeds_feed",
diff --git a/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json b/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json
index 3c6c8a7c8..7ea5eb012 100644
--- a/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json
+++ b/content/node.3c01a9ce-5e01-4edb-9a43-2fd1a02ee8aa.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4f3f3eed089d1a4af0d75429f2731bfe",
             "target_type": "feeds_feed",
diff --git a/content/node.3cb7e223-af31-471e-acef-d3d069852841.json b/content/node.3cb7e223-af31-471e-acef-d3d069852841.json
index 3d981814d..fc9584481 100644
--- a/content/node.3cb7e223-af31-471e-acef-d3d069852841.json
+++ b/content/node.3cb7e223-af31-471e-acef-d3d069852841.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Whilst writing <a href=\"/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        ",
+            "value": "\n          <p>Whilst writing <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Whilst writing <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "26c761c39af062f8236f0e3f605571b4",
             "target_type": "feeds_feed",
diff --git a/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json b/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json
index 039ac99e6..e1befa7eb 100644
--- a/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json
+++ b/content/node.3d777436-a3ab-4465-b3c2-63d7eb28b50d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "22b1b257bc8acefc91b3f682df2bfa7d",
             "target_type": "feeds_feed",
diff --git a/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json b/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json
index e2782723e..2872ce658 100644
--- a/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json
+++ b/content/node.3e810095-a24b-4f0b-a62b-e39003df099e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7efd20a8b45fd58c71c9d69d560899f3",
             "target_type": "feeds_feed",
diff --git a/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json b/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json
index 535a0ec11..77ce6fc5a 100644
--- a/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json
+++ b/content/node.3faefe1b-3c1d-47e6-93d5-dbdd17f2e4fe.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "70b03f1c2962ba75e6f89142c23c6791",
             "target_type": "feeds_feed",
diff --git a/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json b/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json
index 4e856d9cf..e9d147d83 100644
--- a/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json
+++ b/content/node.400a0b92-7c40-43b0-883d-5f199fb5471f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/presentations\/taking-flight-with-tailwind-css\">why I prefer to use utility styles<\/a> for my own projects.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/presentations\/taking-flight-with-tailwind-css\">why I prefer to use utility styles<\/a> for my own projects.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/presentations\/taking-flight-with-tailwind-css\">why I prefer to use utility styles<\/a> for my own projects.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "608cb7069f4b0d69aa56c86a6d0e262b",
             "target_type": "feeds_feed",
diff --git a/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json b/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json
index 5fa3bb731..d8826122c 100644
--- a/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json
+++ b/content/node.40e0f21e-701e-48ce-9c22-8bee64b1a7b1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "53531d5906d1f9a7bfd86d494bd38724",
             "target_type": "feeds_feed",
diff --git a/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json b/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json
index e76d3b975..d5c2ecdd2 100644
--- a/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json
+++ b/content/node.40f5b812-3bf8-47e5-bc39-57d9ae8db404.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ef19563099602226d685a997087e53be",
             "target_type": "feeds_feed",
diff --git a/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json b/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json
index 081aa9411..a0ba93216 100644
--- a/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json
+++ b/content/node.41754bbf-ade6-41a3-97f6-90f101c65265.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "92a7979f45a6c8ae09c876e6d4bd42ce",
             "target_type": "feeds_feed",
diff --git a/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json b/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json
index c3b1f987a..f5ed3ca14 100644
--- a/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json
+++ b/content/node.4177af82-b6e3-4200-9fb8-d66f47611742.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "641df2822210add8bce07e680ceed39d",
             "target_type": "feeds_feed",
diff --git a/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json b/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json
index 7e97f15a1..a9c9f1eb5 100644
--- a/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json
+++ b/content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3fa7aa685c79856ae622fccfd49a503d",
             "target_type": "feeds_feed",
diff --git a/content/node.42741272-127f-46fb-b058-172301e5edd1.json b/content/node.42741272-127f-46fb-b058-172301e5edd1.json
index 1920d7c64..613897ffd 100644
--- a/content/node.42741272-127f-46fb-b058-172301e5edd1.json
+++ b/content/node.42741272-127f-46fb-b058-172301e5edd1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6f729533d71878ba50e24fef55c23dda",
             "target_type": "feeds_feed",
diff --git a/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json b/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json
index 47bd725ac..3c4428b8f 100644
--- a/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json
+++ b/content/node.42744e61-acab-44e4-bd60-576a30cf7b60.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bfe45200bff8e8397ce77077eda3cd7d",
             "target_type": "feeds_feed",
diff --git a/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json b/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json
index 0dd6abf0b..922ed1aab 100644
--- a/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json
+++ b/content/node.42868f5d-12a8-4cfc-9811-f3f7ad7aac06.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A few days ago, I said that <a href=\"/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        ",
+            "value": "\n          <p>A few days ago, I said that <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A few days ago, I said that <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "994cf3233994d78c7c19d5d17c52c6f5",
             "target_type": "feeds_feed",
diff --git a/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json b/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json
index dcf5f7844..9613433df 100644
--- a/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json
+++ b/content/node.42904e0f-f6d7-496e-8bce-72bd1e669e99.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I asked <a href=\"/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        ",
+            "value": "\n          <p>Yesterday, I asked <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I asked <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0ad492a3800d1a39b43b8381b03a167a",
             "target_type": "feeds_feed",
diff --git a/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json b/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json
index d0d7759c0..44da6db9b 100644
--- a/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json
+++ b/content/node.4297cfc8-623f-4d32-b353-5a441c2c632f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2753953e3bfd1a1568643626ad56e3cf",
             "target_type": "feeds_feed",
diff --git a/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json b/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json
index 5f1b98777..834bb54c0 100644
--- a/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json
+++ b/content/node.42e9e133-51d4-4a91-b132-413eece2278c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9d832e6a96400a2022d179422d39c66a",
             "target_type": "feeds_feed",
diff --git a/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json b/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json
index 4875a0b23..3ea5c8d19 100644
--- a/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json
+++ b/content/node.439b8f2e-1e19-4735-b647-e2fa6a8ff48e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b3ce2b27a1306357903fea42bae79618",
             "target_type": "feeds_feed",
diff --git a/content/node.43c6257e-4064-422d-8075-5ec55861c177.json b/content/node.43c6257e-4064-422d-8075-5ec55861c177.json
index b91485973..e21d42c30 100644
--- a/content/node.43c6257e-4064-422d-8075-5ec55861c177.json
+++ b/content/node.43c6257e-4064-422d-8075-5ec55861c177.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4c926214319ed46035a786ecace696ae",
             "target_type": "feeds_feed",
diff --git a/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json b/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json
index 227ed9bff..482e4dbcb 100644
--- a/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json
+++ b/content/node.43df816f-7fee-4e8a-b396-9a84b2214e7b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "40260e52aebd6f8cd05d453734954342",
             "target_type": "feeds_feed",
diff --git a/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json b/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json
index aa77a9a1e..ea15447ca 100644
--- a/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json
+++ b/content/node.43f35613-9c2f-46e9-b581-8253823fb7d8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As part of my recent digital simplification, I've started hosting the episodes of the <a href=\"/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=\"\/files\/bb\/episodes\/{{ page.episode_filename }}\" 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=\"/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        ",
+            "value": "\n          <p>As part of my recent digital simplification, I've started hosting the episodes of the <a href=\"\/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=\"\/files\/bb\/episodes\/{{ page.episode_filename }}\" 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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As part of my recent digital simplification, I've started hosting the episodes of the <a href=\"/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=\"\/files\/bb\/episodes\/{{ page.episode_filename }}\" 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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a4601bf866ebb0eb1ac20cbe52f0bbcd",
             "target_type": "feeds_feed",
diff --git a/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json b/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json
index 8147086bf..a53d1bffb 100644
--- a/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json
+++ b/content/node.44dcbb55-20f6-4737-9557-d6301fca587d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6b48ac239501bd0ff52a0f5acaedb81c",
             "target_type": "feeds_feed",
diff --git a/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json b/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json
index a1a399baa..4a7cb8de4 100644
--- a/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json
+++ b/content/node.44e71b80-61a3-4376-83aa-3b975401942b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b44dc92d2bb08665b6bec22b5fda467c",
             "target_type": "feeds_feed",
diff --git a/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json b/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json
index 227cf5d0c..60c9724f2 100644
--- a/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json
+++ b/content/node.4528246c-53df-4a2b-aba1-e72a45dc542d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0800e5f256b7e5d9dc618733f4dec508",
             "target_type": "feeds_feed",
diff --git a/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json b/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json
index 9a3f8c050..250d90d39 100644
--- a/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json
+++ b/content/node.45636e82-61b1-4298-a28c-34f139b9a559.json
@@ -84,7 +84,7 @@
         {
             "value": "<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=\"\/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=\"\/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>",
             "format": "basic_html",
-            "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=\"\/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=\"\/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>",
+            "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": ""
         }
     ],
diff --git a/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json b/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json
index 0ea50d376..a22309acc 100644
--- a/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json
+++ b/content/node.4619464a-a90c-4ce6-854d-9decfb58c603.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0c86fb80c00db44f4daefbe61a6ba03b",
             "target_type": "feeds_feed",
diff --git a/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json b/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json
index 9fb8656f7..a08ce82a1 100644
--- a/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json
+++ b/content/node.461af26d-2006-48e4-9aec-6eb2db31d4ef.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6e88858810fb772741027a9ce37485cc",
             "target_type": "feeds_feed",
diff --git a/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json b/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json
index 38b847e04..639545cc0 100644
--- a/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json
+++ b/content/node.4640cfe1-e531-48ab-8fb3-42655a77d667.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e3d2f5da90f0708c2f7168e8c649f8c9",
             "target_type": "feeds_feed",
diff --git a/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json b/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json
index 21e37bae9..8d5feeb3e 100644
--- a/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json
+++ b/content/node.465add9b-a2c7-48f1-84de-966fbbd20c27.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Continuing yesterday's thought on <a href=\"/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        ",
+            "value": "\n          <p>Continuing yesterday's thought on <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Continuing yesterday's thought on <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2ff6c4f363c796e474dd5ad89dd20907",
             "target_type": "feeds_feed",
diff --git a/content/node.46604509-5226-42af-ba63-41eeaed19074.json b/content/node.46604509-5226-42af-ba63-41eeaed19074.json
index cc24f0cb1..efe0b86ce 100644
--- a/content/node.46604509-5226-42af-ba63-41eeaed19074.json
+++ b/content/node.46604509-5226-42af-ba63-41eeaed19074.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b0e612367a93931235c02addd4091033",
             "target_type": "feeds_feed",
diff --git a/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json b/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json
index e39c1c523..0cdab4928 100644
--- a/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json
+++ b/content/node.467e5ad9-cca4-4700-8727-3356e81182aa.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>One of the main uses for <a href=\"/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        ",
+            "value": "\n          <p>One of the main uses for <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>One of the main uses for <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2bda9bfc260c442486c03a20105f9ef3",
             "target_type": "feeds_feed",
diff --git a/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json b/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json
index 1c508283b..6ee925c00 100644
--- a/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json
+++ b/content/node.46b346f5-6f58-4e3d-b45d-dfb3d70d25d2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b132c7f6277c6bbb308c6905d1673959",
             "target_type": "feeds_feed",
diff --git a/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json b/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json
index e79cd043e..1c01e4b33 100644
--- a/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json
+++ b/content/node.46b8861e-c2e4-49ef-8b79-fb14effaef6a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>It's been <a href=\"/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        ",
+            "value": "\n          <p>It's been <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>It's been <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e1997b3a167015374e1ceb9ac28b690e",
             "target_type": "feeds_feed",
diff --git a/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json b/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json
index c5fd15d0b..fd8b7730e 100644
--- a/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json
+++ b/content/node.46f8d4ae-3203-4b91-9bd3-13e0b8ad240d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e3dc97eea5cca21de24880789f8cf5fd",
             "target_type": "feeds_feed",
diff --git a/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json b/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json
index a1d43f703..a4b904a2d 100644
--- a/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json
+++ b/content/node.47578912-129e-4ee2-9392-a5e04f4592b4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I posted a screenshot from my <a href=\"/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=\"/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=\"/daily\/2023\/12\/25\/zero-to-test\">read the first lesson<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>Yesterday, I posted a screenshot from my <a href=\"\/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=\"\/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=\"\/daily\/2023\/12\/25\/zero-to-test\">read the first lesson<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I posted a screenshot from my <a href=\"/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=\"/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=\"/daily\/2023\/12\/25\/zero-to-test\">read the first lesson<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f9f7d8ae3da04b94c84b29061624b268",
             "target_type": "feeds_feed",
diff --git a/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json b/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json
index 975f02bf5..ceff2bdc3 100644
--- a/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json
+++ b/content/node.47749b6f-e118-4fe5-b13d-11fe1189d77d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "15b5f4507ca4a5cb62249ea0461feb8a",
             "target_type": "feeds_feed",
diff --git a/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json b/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json
index cddba9fc2..6e56f6146 100644
--- a/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json
+++ b/content/node.48384c9b-ce41-4356-8364-6ce566eac315.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Last week, I recorded an episode of <a href=\"/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        ",
+            "value": "\n          <p>Last week, I recorded an episode of <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Last week, I recorded an episode of <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f6dc73181ab39abab3e420cbef29003a",
             "target_type": "feeds_feed",
diff --git a/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json b/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json
index 0c18b2b39..c99afb84a 100644
--- a/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json
+++ b/content/node.484a7001-9bbd-43fd-b99f-08c6370723d1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a4d60c0bc89cf319cc0a3598dc62b82f",
             "target_type": "feeds_feed",
diff --git a/content/node.487866ab-71b2-407e-9911-c6207dbccd80.json b/content/node.487866ab-71b2-407e-9911-c6207dbccd80.json
index d70de4ff1..7abb84ee7 100644
--- a/content/node.487866ab-71b2-407e-9911-c6207dbccd80.json
+++ b/content/node.487866ab-71b2-407e-9911-c6207dbccd80.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "1902938a-e92a-4ee7-9129-fe3f3ae41bcf"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 bbeb86879..e98cbe306 100644
--- a/content/node.494f1c44-47b9-48be-9240-5a9df560fdaf.json
+++ b/content/node.494f1c44-47b9-48be-9240-5a9df560fdaf.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/call\">book an advisory call<\/a> or <a href=\"/drupal7\">an upgrade roadmap<\/a> for your Drupal 7 project.<\/p>\n\n        ",
+            "value": "\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=\"\/call\">book an advisory call<\/a> or <a href=\"\/drupal7\">an upgrade roadmap<\/a> for your Drupal 7 project.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/call\">book an advisory call<\/a> or <a href=\"/drupal7\">an upgrade roadmap<\/a> for your Drupal 7 project.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f03a3434c8c7ccf722ebf0de5355df06",
             "target_type": "feeds_feed",
diff --git a/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json b/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json
index 690e4f7d3..fe53651ef 100644
--- a/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json
+++ b/content/node.495d58fb-eba7-4c39-a92e-d1cf5ba8bc95.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "738a534ae36eaaaaee08f143a195474d",
             "target_type": "feeds_feed",
diff --git a/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json b/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json
index ce0f5b3bd..644ce0071 100644
--- a/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json
+++ b/content/node.49a59848-0bef-4184-b9d2-5bf539c6e14c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as being <a href=\"/daily\/2025\/03\/12\/easy\">easy to build<\/a> and <a href=\"/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        ",
+            "value": "\n          <p>As well as being <a href=\"\/daily\/2025\/03\/12\/easy\">easy to build<\/a> and <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as being <a href=\"/daily\/2025\/03\/12\/easy\">easy to build<\/a> and <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cad56e3254ecbb16885c1f741f0776f9",
             "target_type": "feeds_feed",
diff --git a/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json b/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json
index 788dfcd91..eb2200736 100644
--- a/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json
+++ b/content/node.49ef1a05-b415-4537-b2c7-285827e27463.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/daily\/2024\/11\/25\/nix-the-package-manager\">As well as Nix managing packages<\/a> and <a href=\"/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=\"/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        ",
+            "value": "\n          <p><a href=\"\/daily\/2024\/11\/25\/nix-the-package-manager\">As well as Nix managing packages<\/a> and <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/daily\/2024\/11\/25\/nix-the-package-manager\">As well as Nix managing packages<\/a> and <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f0ade844887ddbd5a34d24a087017478",
             "target_type": "feeds_feed",
diff --git a/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json b/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json
index 88714fb33..14ca8ecae 100644
--- a/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json
+++ b/content/node.49f2d11b-a2fd-4f79-930d-a0d97fd0c7fc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "244fb1e186ffb1e05c56a3441aef004b",
             "target_type": "feeds_feed",
diff --git a/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json b/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json
index 4ba9723ec..7ab5770d9 100644
--- a/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json
+++ b/content/node.49fff3d4-4c3a-45fb-8b4f-bf528fa6b171.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0bb94ff586d310b9b4782afab2635483",
             "target_type": "feeds_feed",
diff --git a/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json b/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json
index bd1f88e5b..a8c3d9191 100644
--- a/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json
+++ b/content/node.4a1294d7-248e-48f8-bfae-b49bbe1d19b4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "39666fa6935e0010996ee0d41ac7462b",
             "target_type": "feeds_feed",
diff --git a/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json b/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json
index 41de03056..a870dd852 100644
--- a/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json
+++ b/content/node.4a2000eb-92b5-4a41-8f80-6fa1a6849855.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ef838351b3125011ce7d336faa1387f0",
             "target_type": "feeds_feed",
diff --git a/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json b/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json
index c8bcd8c38..03ab1a88e 100644
--- a/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json
+++ b/content/node.4ae8b0fe-2248-4e67-b68a-816c8539528a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a6007d2feefccdaac0d128595fe05dd0",
             "target_type": "feeds_feed",
diff --git a/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json b/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json
index ebf12977c..d82f87889 100644
--- a/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json
+++ b/content/node.4aec9154-e02d-48cd-84e3-26de40c4d4f3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "529c210a492581735189b8a17c332053",
             "target_type": "feeds_feed",
diff --git a/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json b/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json
index 9a1f457d3..78334edc4 100644
--- a/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json
+++ b/content/node.4af20d94-cb48-4351-a0a6-7f6a0387d105.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6e42e4070398b24d913cecbd7fa25945",
             "target_type": "feeds_feed",
diff --git a/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json b/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json
index bf67f2f5d..d14fe1105 100644
--- a/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json
+++ b/content/node.4b0999e1-0348-478a-af35-1487adb15b7a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4bab95f073ef6c5bab4596c03470a49c",
             "target_type": "feeds_feed",
diff --git a/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json b/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json
index 24959905a..0db179746 100644
--- a/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json
+++ b/content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7da91326631cb7cf3b105e8837f5879c",
             "target_type": "feeds_feed",
diff --git a/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json b/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json
index 65b9098d9..7b1a2f792 100644
--- a/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json
+++ b/content/node.4c0b0072-4046-48aa-b481-84515c265ca0.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a59b6f540ddfce9e980f906b5921178c",
             "target_type": "feeds_feed",
diff --git a/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json b/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json
index 1750ceec7..7357770d0 100644
--- a/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json
+++ b/content/node.4c1497cc-4638-40fc-b045-f342c4d3e5b3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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\u00a0 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\u00a0 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=\"/atdc\">register here for free<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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\u00a0 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\u00a0 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=\"\/atdc\">register here for free<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/atdc\">register here for free<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fa1fa6afff083eeef00370e7db237279",
             "target_type": "feeds_feed",
diff --git a/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json b/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json
index 9574e718e..866d0e5da 100644
--- a/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json
+++ b/content/node.4c3faf72-fafe-4559-a496-7a0e1ddbc948.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d896323fbe54f5997b5e4edeb7c0c0dc",
             "target_type": "feeds_feed",
diff --git a/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json b/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json
index ee9e501ea..f3504b034 100644
--- a/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json
+++ b/content/node.4cdddd8a-3291-4d3f-81c9-e639f527f647.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "87636a91b190a3f76a189dfb1cfa6e92",
             "target_type": "feeds_feed",
diff --git a/content/node.4d1139c2-0183-4670-af08-003694dec455.json b/content/node.4d1139c2-0183-4670-af08-003694dec455.json
index 986e749d7..eec731075 100644
--- a/content/node.4d1139c2-0183-4670-af08-003694dec455.json
+++ b/content/node.4d1139c2-0183-4670-af08-003694dec455.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "629f68f940bdb03dfa139e991ac3b2b1",
             "target_type": "feeds_feed",
diff --git a/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json b/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json
index 5058c7792..8de5aed55 100644
--- a/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json
+++ b/content/node.4d20a016-5fcf-45a6-946d-9fabe2319230.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "63159fd033bcf1d7e3129da389c832f2",
             "target_type": "feeds_feed",
diff --git a/content/node.4d270194-23a5-445f-8b66-5ee347054400.json b/content/node.4d270194-23a5-445f-8b66-5ee347054400.json
index 627432a32..77132aaf5 100644
--- a/content/node.4d270194-23a5-445f-8b66-5ee347054400.json
+++ b/content/node.4d270194-23a5-445f-8b66-5ee347054400.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b9604073a92a4e15df6ba36f167ff649",
             "target_type": "feeds_feed",
diff --git a/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json b/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json
index 3400b44b1..a0a3909ca 100644
--- a/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json
+++ b/content/node.4d65036f-7cf3-4ec5-be30-d20f684b820a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>It's been almost five years since I gave the first version of my \"<a href=\"/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        ",
+            "value": "\n          <p>It's been almost five years since I gave the first version of my \"<a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>It's been almost five years since I gave the first version of my \"<a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6922005e460c87b7b1c677699162005b",
             "target_type": "feeds_feed",
diff --git a/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json b/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json
index 57d6101f5..c929b73fa 100644
--- a/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json
+++ b/content/node.4d6d623b-afb2-4628-b716-2e6c3adac5cb.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "abbf5f0e4c7e129fc05e499228722a6f",
             "target_type": "feeds_feed",
diff --git a/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json b/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json
index 7f20a71c4..5110b8d76 100644
--- a/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json
+++ b/content/node.4de8ccc0-035a-46b9-870d-6df54238eb65.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c6a3315ecb8173fc096250981c691fbe",
             "target_type": "feeds_feed",
diff --git a/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json b/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json
index 8f2d0ba98..3219f29ad 100644
--- a/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json
+++ b/content/node.4df98b71-9bff-4c1d-9636-5074e31a7ace.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "397621c34a88f800e52750829b4bc177",
             "target_type": "feeds_feed",
diff --git a/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json b/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json
index f87d4c834..5d5ff7982 100644
--- a/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json
+++ b/content/node.4e0d5cba-13d4-497e-a320-d1236df4dce2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ac7bcb6f2dcaec78fb9959f65d264b1f",
             "target_type": "feeds_feed",
diff --git a/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json b/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json
index 268ec6795..96751c236 100644
--- a/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json
+++ b/content/node.4e5d1d22-b993-4b38-b2bd-60f328e1ce76.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0758277d9d9ff772a843ca188916ffa7",
             "target_type": "feeds_feed",
diff --git a/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json b/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json
index 15e01a499..8d1d71e0b 100644
--- a/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json
+++ b/content/node.4e66101d-e2bf-4eab-904d-67c15d0466b8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cb4f6ebcd079c83203db842b57e9d34f",
             "target_type": "feeds_feed",
diff --git a/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json b/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json
index 86561af6c..90684d27d 100644
--- a/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json
+++ b/content/node.4f2f14d0-f991-4f10-b516-20e744c08fce.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "18b329b870189395601442a5d226290c",
             "target_type": "feeds_feed",
diff --git a/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json b/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json
index 19669b777..1354aa98c 100644
--- a/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json
+++ b/content/node.4f6883d1-6421-4350-8ca5-7bfc57da20e9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3b27ec6a81d5e6dcf310dfe3e6204b69",
             "target_type": "feeds_feed",
diff --git a/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json b/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json
index ea789b78b..6fdfa0129 100644
--- a/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json
+++ b/content/node.4fdd7824-d2ef-4a4f-a6ca-80a5098af105.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f0c3d6e951782cfb763d893c57d2dced",
             "target_type": "feeds_feed",
diff --git a/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json b/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json
index c83b413ce..1198ab660 100644
--- a/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json
+++ b/content/node.5017b3a0-ce88-4884-bace-c0550e729ab5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0c791781778c8aeadb8f49363376f730",
             "target_type": "feeds_feed",
diff --git a/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json b/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json
index 708da60b5..eea2b1a73 100644
--- a/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json
+++ b/content/node.5060344a-0047-40ab-8fdb-a297518478fb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7f6dcf1b5ac7259908a71513a4e6b908",
             "target_type": "feeds_feed",
diff --git a/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json b/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json
index 00d377e0d..855dd47ac 100644
--- a/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json
+++ b/content/node.50f6b3f3-e483-41b0-a44a-465109c160b7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e93ad68bebb864569d626ff3d30d67bc",
             "target_type": "feeds_feed",
diff --git a/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json b/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json
index fb45a0bca..71ed7090d 100644
--- a/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json
+++ b/content/node.516e5193-61d3-4f2b-885b-4e0c5e81c775.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "019e5d597f894b924aac0c6b461b07fd",
             "target_type": "feeds_feed",
diff --git a/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json b/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json
index 8a82b2382..04608307e 100644
--- a/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json
+++ b/content/node.52049b70-5092-41ea-a749-5fde0d95b39e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently said that <a href=\"/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=\"/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        ",
+            "value": "\n          <p>I recently said that <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently said that <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "47f25a425d659c954d97d5112ac43a64",
             "target_type": "feeds_feed",
diff --git a/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json b/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json
index ff36b6ce6..7c8aeb92a 100644
--- a/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json
+++ b/content/node.526f1b74-c255-4dd3-ba7a-5d529545d01d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In my <a href=\"/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        ",
+            "value": "\n          <p>In my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8f98e53db611d2a06dded4a390a73ab4",
             "target_type": "feeds_feed",
diff --git a/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json b/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json
index d4d29f71b..7fa2a203f 100644
--- a/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json
+++ b/content/node.52c39f9c-1003-4c70-9e2c-8e59ff5b7299.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a1e1e81b117aed3458e6cb11e916a04b",
             "target_type": "feeds_feed",
diff --git a/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json b/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json
index 31bc10835..990db5d10 100644
--- a/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json
+++ b/content/node.530d3f61-3f2c-4cb5-acc7-560d4608367f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b063958005e2aa3015d2060e0878c0aa",
             "target_type": "feeds_feed",
diff --git a/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json b/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json
index 4cce1cfc0..3f0be2074 100644
--- a/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json
+++ b/content/node.5395f0ad-b0c1-472c-b815-4bf3eba9dcfe.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0ceafa8785ee51630825fb772ad853a6",
             "target_type": "feeds_feed",
diff --git a/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json b/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json
index 18b5b75b8..2d3c79cd3 100644
--- a/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json
+++ b/content/node.53a00f10-a301-4294-ad39-916b9bc2ecd7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Once you've <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Once you've <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Once you've <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "674c9c37b7fd93e1d85171115f3aec2a",
             "target_type": "feeds_feed",
diff --git a/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json b/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json
index 8cade9882..d8d4da578 100644
--- a/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json
+++ b/content/node.53ad5789-5fd6-41e8-b748-ce9e0bff280b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>An argument against the <a href=\"/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        ",
+            "value": "\n          <p>An argument against the <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>An argument against the <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0b1a8be5345c3efb403f70fca1daabbf",
             "target_type": "feeds_feed",
diff --git a/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json b/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json
index 864ffc627..30e3e59e0 100644
--- a/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json
+++ b/content/node.53afa754-c4c0-4a31-81ed-5ed4fa9aab77.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a856af7f62fcf490200ee880fa6e6f73",
             "target_type": "feeds_feed",
diff --git a/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json b/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json
index 1cd7206da..481578c58 100644
--- a/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json
+++ b/content/node.53d1af45-bb51-4e4a-a2b9-b732bc9dc8ea.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I wrote about <a href=\"/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        ",
+            "value": "\n          <p>Yesterday, I wrote about <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I wrote about <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5b8c0219dc018568e03908b9744aff46",
             "target_type": "feeds_feed",
diff --git a/content/node.54108c84-c648-4c91-92c6-816711878a4f.json b/content/node.54108c84-c648-4c91-92c6-816711878a4f.json
index b28ae3879..504209663 100644
--- a/content/node.54108c84-c648-4c91-92c6-816711878a4f.json
+++ b/content/node.54108c84-c648-4c91-92c6-816711878a4f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2971b28664070325dea116a96e60f866",
             "target_type": "feeds_feed",
diff --git a/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json b/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json
index b630f006b..7db3ce20d 100644
--- a/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json
+++ b/content/node.54a30090-50dd-4534-af69-bc7120297bf9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ea9be0481194a0fa60a57a3ea920440c",
             "target_type": "feeds_feed",
diff --git a/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json b/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json
index 0b9816213..45c32b221 100644
--- a/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json
+++ b/content/node.5563fb1b-a5a1-4372-84b9-b0be87acc501.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/14-yuri-gerasymov-diffy\">Listen to the episode<\/a><\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/14-yuri-gerasymov-diffy\">Listen to the episode<\/a><\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/14-yuri-gerasymov-diffy\">Listen to the episode<\/a><\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f767e648d91ab4e42156d03ff67f7f6c",
             "target_type": "feeds_feed",
diff --git a/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json b/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json
index 58d47806e..a49ca6251 100644
--- a/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json
+++ b/content/node.557b60f7-1f31-40ec-b0c8-285df7a73dd9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Whether you get <a href=\"/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        ",
+            "value": "\n          <p>Whether you get <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Whether you get <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4644916c3b9cfef844fa7c5503ae3b85",
             "target_type": "feeds_feed",
diff --git a/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json b/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json
index 34e6e2ffd..d03dc2430 100644
--- a/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json
+++ b/content/node.5652a68a-720a-4954-adfa-38b8e2890b8d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/team-coaching\">team coaching<\/a> and <a href=\"/pricing\">private talks and workshops<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/team-coaching\">team coaching<\/a> and <a href=\"\/pricing\">private talks and workshops<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/team-coaching\">team coaching<\/a> and <a href=\"/pricing\">private talks and workshops<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a6dfd22ba492a4321428a81447ebc21a",
             "target_type": "feeds_feed",
diff --git a/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json b/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json
index 51a5a504f..769911af5 100644
--- a/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json
+++ b/content/node.56776268-7d1e-47b3-8c3a-bb7dc5d102f4.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6f502f1378e2ffcb9acf63bd11ff5325",
             "target_type": "feeds_feed",
diff --git a/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json b/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json
index af0979437..e8fb078f0 100644
--- a/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json
+++ b/content/node.56df3f74-7cd2-4229-98b7-a593d435ad70.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "df8a1f8e4c5825078db0d4b92837624d",
             "target_type": "feeds_feed",
diff --git a/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json b/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json
index 5ef4aad2b..64f933bb6 100644
--- a/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json
+++ b/content/node.56e62486-ed1c-4ce8-89e1-8c92cd8fe254.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6b905a72c2e1be12adf25aea58ea044c",
             "target_type": "feeds_feed",
diff --git a/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json b/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json
index 7cf86078e..35eeca496 100644
--- a/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json
+++ b/content/node.5715449a-bcad-41cd-bdb7-252d43b3ebcf.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In my <a href=\"/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        ",
+            "value": "\n          <p>In my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5856ee99a95c5407d33af80db814c94d",
             "target_type": "feeds_feed",
diff --git a/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json b/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json
index 80d0e2af5..61e35c281 100644
--- a/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json
+++ b/content/node.572f5e16-12f6-4470-a07c-06baf52c26e5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7eb65ae3f24b2f4806b258bdef6f47ae",
             "target_type": "feeds_feed",
diff --git a/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json b/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json
index 2c1c44166..489ee08ee 100644
--- a/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json
+++ b/content/node.57f28cf3-4474-4668-8222-c430cbe9b88b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I wrote about <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Yesterday, I wrote about <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I wrote about <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b9459e8502e6216a6d8f4cd2842d9bba",
             "target_type": "feeds_feed",
diff --git a/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json b/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json
index 6d791dad4..8ca56b0f9 100644
--- a/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json
+++ b/content/node.57f698eb-511f-4cfb-95b0-a752efab60ea.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/talks\/tdd-test-driven-drupal\">automated testing and test-driven development<\/a> and another on <a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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=\"\/talks\/tdd-test-driven-drupal\">automated testing and test-driven development<\/a> and another on <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/talks\/tdd-test-driven-drupal\">automated testing and test-driven development<\/a> and another on <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "46b853586496fec3d554e44ee4bdf81f",
             "target_type": "feeds_feed",
diff --git a/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json b/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json
index b7c39e9a2..d656da444 100644
--- a/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json
+++ b/content/node.5920cf0f-3b24-488f-8534-53239f441f5b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fcd2d826fa4f9caf9ec7194920add0bb",
             "target_type": "feeds_feed",
diff --git a/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json b/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json
index c8fc60ffc..1647d8360 100644
--- a/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json
+++ b/content/node.593bdaf4-b28c-4938-b1da-03052baef361.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4720dadf7849019a7ca4401ddec374be",
             "target_type": "feeds_feed",
diff --git a/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json b/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json
index e7248a4a8..60ff77cca 100644
--- a/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json
+++ b/content/node.597567b2-4065-4bea-890f-b8faef33f8c6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dd0fbfd753d7cc8349477b9e7228c8c4",
             "target_type": "feeds_feed",
diff --git a/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json b/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json
index 4828cbab8..ad10ed1a5 100644
--- a/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json
+++ b/content/node.59ae3523-9dc9-4b61-8387-aaeb708385e6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Whether you <a href=\"/daily\/2024\/09\/19\/the-two-ways-of-writing-php-code\">prefer strict code or not<\/a>, <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Whether you <a href=\"\/daily\/2024\/09\/19\/the-two-ways-of-writing-php-code\">prefer strict code or not<\/a>, <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Whether you <a href=\"/daily\/2024\/09\/19\/the-two-ways-of-writing-php-code\">prefer strict code or not<\/a>, <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "868d9285f3f2c28b801786ad11418bb5",
             "target_type": "feeds_feed",
diff --git a/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json b/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json
index 13e25b9ea..2f761e9f3 100644
--- a/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json
+++ b/content/node.59cd5b64-d1c8-4249-ab41-2106e25df543.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "37779b8be562eca580a1d3eb2ead9f83",
             "target_type": "feeds_feed",
diff --git a/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json b/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json
index e3421f003..d5ca46221 100644
--- a/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json
+++ b/content/node.59ff61dd-05ce-4ab5-8d8e-ebb88ea4a07e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cc64c7935024e569db0c62815dab704a",
             "target_type": "feeds_feed",
diff --git a/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json b/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json
index 618245739..6157f80ff 100644
--- a/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json
+++ b/content/node.5a811f7d-30af-40bd-a691-0f181f125541.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2dc52bfbe73534ab29285ff16486431f",
             "target_type": "feeds_feed",
diff --git a/content/node.5a8df3bf-d501-47ae-978b-ef6219c68c60.json b/content/node.5a8df3bf-d501-47ae-978b-ef6219c68c60.json
index b60dca5fc..7d020bc5b 100644
--- a/content/node.5a8df3bf-d501-47ae-978b-ef6219c68c60.json
+++ b/content/node.5a8df3bf-d501-47ae-978b-ef6219c68c60.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "e4c684f2-2c3c-4ca3-a65b-eb7596778538"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 16b759e77..6987eeb2d 100644
--- a/content/node.5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe.json
+++ b/content/node.5a9b5ddb-7ae0-4f69-9b94-fa02f91224fe.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "58c0962d04b426f68f113c3d3701de68",
             "target_type": "feeds_feed",
diff --git a/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json b/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json
index 759f974b3..cc9c0a5e8 100644
--- a/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json
+++ b/content/node.5ae98ed1-594d-4994-b8b1-5b4b89d5af0c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "45f3a63e2d57203a2e7971e0d93c8e4c",
             "target_type": "feeds_feed",
diff --git a/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json b/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json
index d8727b463..28ac66dbe 100644
--- a/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json
+++ b/content/node.5af463dd-91dc-45a4-a0bc-58212e30d402.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8a6c7300585b92faff3cdc9aeaf92cf6",
             "target_type": "feeds_feed",
diff --git a/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json b/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json
index b53a7a638..9e4aa8d4f 100644
--- a/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json
+++ b/content/node.5b0c25b0-761b-437b-8be3-af045c9e00bc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d65b8a6ca1d38217328e475662fad99e",
             "target_type": "feeds_feed",
diff --git a/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json b/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json
index bec65e4f8..d4ef5c74f 100644
--- a/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json
+++ b/content/node.5bc7bc61-6e00-45ed-800d-e324a3ee1196.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9396b3bf8fe0703b3a6bd95debc95407",
             "target_type": "feeds_feed",
diff --git a/content/node.5c296c46-30d9-4ec8-93e4-837330c833b0.json b/content/node.5c296c46-30d9-4ec8-93e4-837330c833b0.json
index 1d68880e0..bd58b1baf 100644
--- a/content/node.5c296c46-30d9-4ec8-93e4-837330c833b0.json
+++ b/content/node.5c296c46-30d9-4ec8-93e4-837330c833b0.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "189f1378-871c-4e2a-93b9-1096fd273c43"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 8243a18cc..d2c17719a 100644
--- a/content/node.5c50152f-4832-4ccc-9751-31c5caeb7cc3.json
+++ b/content/node.5c50152f-4832-4ccc-9751-31c5caeb7cc3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8acef66d71f6264594f0485bcd7cfb2d",
             "target_type": "feeds_feed",
diff --git a/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json b/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json
index 8167a82a3..30ff48d81 100644
--- a/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json
+++ b/content/node.5c687659-3110-4757-b25f-ab28a7190da5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "af6787c66c99562dd87d058806ab584e",
             "target_type": "feeds_feed",
diff --git a/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json b/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json
index e9332c9e9..41182d4cd 100644
--- a/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json
+++ b/content/node.5c793601-f8ea-470d-8c64-3e669226e651.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "370654d00cb259d64990285329962aa4",
             "target_type": "feeds_feed",
diff --git a/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json b/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json
index 16f0ef062..57831e8bf 100644
--- a/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json
+++ b/content/node.5ca26ec2-4ea4-4d25-96ac-c3998c38c038.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Whilst starting to upgrade my <a href=\"/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=\"/daily\/2024\/06\/09\/proudly-found-elsewhere\">get off the island<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>Whilst starting to upgrade my <a href=\"\/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=\"\/daily\/2024\/06\/09\/proudly-found-elsewhere\">get off the island<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>Whilst starting to upgrade my <a href=\"/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=\"/daily\/2024\/06\/09\/proudly-found-elsewhere\">get off the island<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d75c458cf9b991240a7570f820d0e33d",
             "target_type": "feeds_feed",
diff --git a/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json b/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json
index b4d452107..5223243fb 100644
--- a/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json
+++ b/content/node.5cc109fc-0d43-4d3d-9523-b60e9b27198d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS talk<\/a> are on my website.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS talk<\/a> are on my website.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/talks\/taking-flight-with-tailwind-css\">Taking Flight with Tailwind CSS talk<\/a> are on my website.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "aea872543f2df95bb71f3cb9dffe5360",
             "target_type": "feeds_feed",
diff --git a/content/node.5cc36ded-e301-49de-88eb-c218c980707f.json b/content/node.5cc36ded-e301-49de-88eb-c218c980707f.json
index 71e446ad5..f7e89825f 100644
--- a/content/node.5cc36ded-e301-49de-88eb-c218c980707f.json
+++ b/content/node.5cc36ded-e301-49de-88eb-c218c980707f.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "ec064691-4a1e-4a7c-a5f4-0a573286a67b"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 0d2722af4..097d89ded 100644
--- a/content/node.5d894fb5-1253-4f7e-a6ad-429618eeefef.json
+++ b/content/node.5d894fb5-1253-4f7e-a6ad-429618eeefef.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "071392af7e184fa125a44531711fdfde",
             "target_type": "feeds_feed",
diff --git a/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json b/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json
index 8e9a1a339..e94025d02 100644
--- a/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json
+++ b/content/node.5da0ef0c-154d-445e-8632-02cd3b280785.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2afeabd81ff9e0d49b2e428521c127d1",
             "target_type": "feeds_feed",
diff --git a/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json b/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json
index 95962ab4c..f4e28bb26 100644
--- a/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json
+++ b/content/node.5dbba89e-cd61-403e-ac30-8bd0cd9e203e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "14f3a718b42c7abd68a912676fde8f73",
             "target_type": "feeds_feed",
diff --git a/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json b/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json
index 3ee2ed7c4..00f0f3d1f 100644
--- a/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json
+++ b/content/node.5df88778-175b-486a-88fb-aba781cb3b05.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e338b7c88d5cb20842d58191906582b0",
             "target_type": "feeds_feed",
diff --git a/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json b/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json
index 4229b8791..a8616784e 100644
--- a/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json
+++ b/content/node.5e37f5e3-8ada-4d61-925d-5033258e441f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2ddc207d69aba210aead45269c83988b",
             "target_type": "feeds_feed",
diff --git a/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json b/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json
index 671a86fd4..e3ad02297 100644
--- a/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json
+++ b/content/node.5e44dd96-8baf-47dd-9aba-79887e8c3835.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently received these kind words from Frank Landry, who recently completed my <a href=\"/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        ",
+            "value": "\n          <p>I recently received these kind words from Frank Landry, who recently completed my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently received these kind words from Frank Landry, who recently completed my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "931b8ae559e296532c83db53d0eb0671",
             "target_type": "feeds_feed",
diff --git a/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json b/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json
index eb99cd58a..5674faca9 100644
--- a/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json
+++ b/content/node.5e643127-50de-44fa-bd1f-70f69c72ee9f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e8fab9a9c586506079edcd257eb1d672",
             "target_type": "feeds_feed",
diff --git a/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json b/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json
index fdcf60534..9888244c7 100644
--- a/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json
+++ b/content/node.5e8f1843-5372-46c1-bb61-0ff493ca22ae.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "48e2d5e019f08af995265a4dcb06e4f5",
             "target_type": "feeds_feed",
diff --git a/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json b/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json
index 750e2445f..ea4d6ead1 100644
--- a/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json
+++ b/content/node.5ec8d076-631f-428e-aaf3-44fef2b83bac.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d7e1f6d61d5541ac83cd2bfe9bc3e669",
             "target_type": "feeds_feed",
diff --git a/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json b/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json
index 8d0eff26d..b073660fa 100644
--- a/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json
+++ b/content/node.6026652e-2f3a-492c-b1b2-e5a1ef8ceee6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/11-mark-conroy\">Mark Conroy and I discussed<\/a> on the Beyond Blocks podcast.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/11-mark-conroy\">Mark Conroy and I discussed<\/a> on the Beyond Blocks podcast.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/11-mark-conroy\">Mark Conroy and I discussed<\/a> on the Beyond Blocks podcast.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a7d6c56ee6f6fe36ad6ab0b6d430d52b",
             "target_type": "feeds_feed",
diff --git a/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json b/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json
index 72d9af7e7..c6a3b24cb 100644
--- a/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json
+++ b/content/node.60b67ca4-2b82-4810-87ea-8dfe866c2ed6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "676d182d739ffcfdc08fb352326a6503",
             "target_type": "feeds_feed",
diff --git a/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json b/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json
index 83ac8ba3a..d1867085d 100644
--- a/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json
+++ b/content/node.60d29f19-7871-4b8e-a2e5-3bf7edf17c00.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Continuing from <a href=\"/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        ",
+            "value": "\n          <p>Continuing from <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Continuing from <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4da060af4834ea01bfde91a020ba0f5f",
             "target_type": "feeds_feed",
diff --git a/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json b/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json
index 917fa126a..c121fe5d5 100644
--- a/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json
+++ b/content/node.60e98822-2c17-4de7-aa6d-3b12e3eb48c2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "db22261b5253a478d77e2c07ea03d3da",
             "target_type": "feeds_feed",
diff --git a/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json b/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json
index 89f120d89..759595cc0 100644
--- a/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json
+++ b/content/node.6118c41e-e92e-4865-9f1c-64dd19e2bc40.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "354a128b2c40c5adae2aa3cc4b1fd6ef",
             "target_type": "feeds_feed",
diff --git a/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json b/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json
index a6b9b0ca1..0da469cd6 100644
--- a/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json
+++ b/content/node.6118e44d-7b4b-465e-9e7d-d2268a2e2505.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "411c32cffbc1e2bf68a8ab3d2c9c503f",
             "target_type": "feeds_feed",
diff --git a/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json b/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json
index 76e5e461f..03eed9b92 100644
--- a/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json
+++ b/content/node.614ba8ae-b911-4705-95f8-aafe213e00f3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1cd5f63516d47e313f05f821bfa74ee8",
             "target_type": "feeds_feed",
diff --git a/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json b/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json
index e71f3a97e..a944dfbcd 100644
--- a/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json
+++ b/content/node.614cb089-7e70-46ab-9f5f-dd08b529f3d0.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f2796dcd8b3c66004a440f61ec59c655",
             "target_type": "feeds_feed",
diff --git a/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json b/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json
index c78641043..dbaa04b3e 100644
--- a/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json
+++ b/content/node.624faf57-efdb-444b-85b7-fbb680ed2b73.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ece6d288969fcecbef1ddc355b89ca0e",
             "target_type": "feeds_feed",
diff --git a/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json b/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json
index 0778dd53f..9ac79e58a 100644
--- a/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json
+++ b/content/node.62684ebe-62d0-4999-b4c3-c768e371caac.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cd7cf8aa226ddd46c78eab76f4c2e300",
             "target_type": "feeds_feed",
diff --git a/content/node.62d158a4-17c2-488c-990c-d852eb7e3f7c.json b/content/node.62d158a4-17c2-488c-990c-d852eb7e3f7c.json
index cdd115999..e04a2e074 100644
--- a/content/node.62d158a4-17c2-488c-990c-d852eb7e3f7c.json
+++ b/content/node.62d158a4-17c2-488c-990c-d852eb7e3f7c.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "317d48d3-4d85-450e-8358-f495d503b41b"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 988707f0d..0c8ced4eb 100644
--- a/content/node.62d91e86-a22e-4ef9-851d-bd2b02c411a9.json
+++ b/content/node.62d91e86-a22e-4ef9-851d-bd2b02c411a9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "efd0ec8ddb3fb7929febf9e8017a8f84",
             "target_type": "feeds_feed",
diff --git a/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json b/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json
index 83a308e95..e6014419a 100644
--- a/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json
+++ b/content/node.63c8df59-28ad-49c9-a605-028d5730d2b6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "eed28c15ec49405ff32aaeab6788dec9",
             "target_type": "feeds_feed",
diff --git a/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json b/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json
index 2dfee313e..323b1afae 100644
--- a/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json
+++ b/content/node.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Sometimes when <a href=\"/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        ",
+            "value": "\n          <p>Sometimes when <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Sometimes when <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "945a9ecd7e9f1ec6de312f2b03035231",
             "target_type": "feeds_feed",
diff --git a/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json b/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json
index f18c1d81f..0304bd564 100644
--- a/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json
+++ b/content/node.6433f0ed-d000-473b-8412-c61c8e39a80e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "960ab3763a91c3a533d2f22da91bd8fd",
             "target_type": "feeds_feed",
diff --git a/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json b/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json
index f8472cf12..526aadd48 100644
--- a/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json
+++ b/content/node.6480661e-12de-42e9-aa02-d4f37b23942d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "17e2867cfaf4f7465ecd07558b97ce21",
             "target_type": "feeds_feed",
diff --git a/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json b/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json
index 20535a91e..77657980c 100644
--- a/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json
+++ b/content/node.64f12aa1-bb09-4c30-902f-0e94ffb936cb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "02563327b263204583e6aa95ad8c9bd2",
             "target_type": "feeds_feed",
diff --git a/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json b/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json
index 245b2a740..3acf8b4c1 100644
--- a/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json
+++ b/content/node.65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "45fc5e3725cf16ecee4a27e40566329d",
             "target_type": "feeds_feed",
diff --git a/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json b/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json
index fc4ba0fd8..65a6bbc53 100644
--- a/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json
+++ b/content/node.66485e91-b88c-4a7c-8472-e593b8496e82.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week's guest on the Beyond Blocks podcast is\u00a0Niklas 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=\"/podcast\/3-non-technical-contribution\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>This week's guest on the Beyond Blocks podcast is\u00a0Niklas 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=\"\/podcast\/3-non-technical-contribution\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/3-non-technical-contribution\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "51dd20dbb9299ddbcf934107a9b20553",
             "target_type": "feeds_feed",
diff --git a/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json b/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json
index 8afc785f0..ecf33db13 100644
--- a/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json
+++ b/content/node.667d02f9-f672-4a0c-a9cd-e8111ed1d8bd.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d85f39009078b66d9ee5dacc770a0a22",
             "target_type": "feeds_feed",
diff --git a/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json b/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json
index d2731c8ad..fd1aed6ab 100644
--- a/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json
+++ b/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d77f4c3aa58ffc20e26976b05b6332a5",
             "target_type": "feeds_feed",
diff --git a/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json b/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json
index 5efc4901e..a949fea21 100644
--- a/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json
+++ b/content/node.681c802d-45a6-409e-8dd1-3499184f7616.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2025\/02\/24\/patch\">by applying patches<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/daily\/2025\/02\/24\/patch\">by applying patches<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2025\/02\/24\/patch\">by applying patches<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "937f6aa16a83423afa9730474711b269",
             "target_type": "feeds_feed",
diff --git a/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json b/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json
index 88f7681e5..dbb86e911 100644
--- a/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json
+++ b/content/node.6842a257-a488-48aa-bb63-5663fe8e9f6a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7b218181f5d1024fd603acad4aa84aac",
             "target_type": "feeds_feed",
diff --git a/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json b/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json
index 269ec933b..08f7c6b66 100644
--- a/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json
+++ b/content/node.68735c24-e65b-47f6-9c23-e1be5123f6a6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8bb372459a76d7f0e6bbc559bd44f81c",
             "target_type": "feeds_feed",
diff --git a/content/node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b.json b/content/node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b.json
index e78faa5b4..6e9ba0088 100644
--- a/content/node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b.json
+++ b/content/node.687c50a0-f5e5-40ab-8ae0-0a31eb73d65b.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 fe8e34da6..907106b28 100644
--- a/content/node.68c7948f-c44c-46e2-878f-432616c7e365.json
+++ b/content/node.68c7948f-c44c-46e2-878f-432616c7e365.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9983c859dafd94ec45282b7438b9cb59",
             "target_type": "feeds_feed",
diff --git a/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json b/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json
index 2ad7c3fd1..7bce92c19 100644
--- a/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json
+++ b/content/node.6a21fce9-ece0-4827-ad71-aa0211b1b0e1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "477dd3acb45552ebd9d3abd74691f723",
             "target_type": "feeds_feed",
diff --git a/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json b/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json
index 0ca2cf8e7..4b80a9e7d 100644
--- a/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json
+++ b/content/node.6b13d2f6-78fe-4bd6-bbce-5592cb2ce9e1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2396dbcb354eade3105e541370b34bef",
             "target_type": "feeds_feed",
diff --git a/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json b/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json
index f938c1814..509e9047e 100644
--- a/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json
+++ b/content/node.6bd02fde-eab4-4c41-8808-e9f1c00f85d3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8ecf5375b76358c09922dc94523f6dfc",
             "target_type": "feeds_feed",
diff --git a/content/node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191.json b/content/node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191.json
index 1860a7bb8..7dd910d89 100644
--- a/content/node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191.json
+++ b/content/node.6bfb5cd7-ee69-4cbb-8a28-fe1d60fba191.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "6f130024-67b6-448c-a780-8fe31d10f94d"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 cd89c7789..73121ff8e 100644
--- a/content/node.6c69f289-ca43-4731-9729-0341250e0591.json
+++ b/content/node.6c69f289-ca43-4731-9729-0341250e0591.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "685bea9e2790b5b0bd16d23d8c64a61a",
             "target_type": "feeds_feed",
diff --git a/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json b/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json
index 7b254a156..70b2987bb 100644
--- a/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json
+++ b/content/node.6c7900af-a3e4-4402-937d-9eeda843398f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "42e38b75bd8ecb458273f77d2cd34883",
             "target_type": "feeds_feed",
diff --git a/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json b/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json
index e4749a2e3..9f9fd9acf 100644
--- a/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json
+++ b/content/node.6cc053d6-5012-4cc7-81e8-43768a0886be.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/atdc\">register for free<\/a> and get them direct to your inbox.<\/p>\n\n        ",
+            "value": "\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=\"\/atdc\">register for free<\/a> and get them direct to your inbox.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/atdc\">register for free<\/a> and get them direct to your inbox.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3943dc4ec9de105dc8129ddcc5e62eae",
             "target_type": "feeds_feed",
diff --git a/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json b/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json
index c3b13425c..23d1194bc 100644
--- a/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json
+++ b/content/node.6ccfb609-6371-462c-b91c-4aa22d23d248.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I wrote about <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Yesterday, I wrote about <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I wrote about <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7cd6f305207bb1a29052636f877e416e",
             "target_type": "feeds_feed",
diff --git a/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json b/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json
index 49bb8d4c9..5d3b89bc3 100644
--- a/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json
+++ b/content/node.6cecf88f-e9d9-4954-b64e-00246781b591.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/presentations\/building-build-configs\">The slides are already online<\/a> and I've created <a href=\"/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        ",
+            "value": "\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=\"\/presentations\/building-build-configs\">The slides are already online<\/a> and I've created <a href=\"\/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        ",
             "format": "full_html",
-            "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=\"/presentations\/building-build-configs\">The slides are already online<\/a> and I've created <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d52c150ed8a1993d5bffe35438c3f3ae",
             "target_type": "feeds_feed",
diff --git a/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json b/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json
index c035a42de..c02030c47 100644
--- a/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json
+++ b/content/node.6d12e45b-2c1f-4931-9dcf-c96084d99c8f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "66217a4b2a3ea98d7ca6fe3ff56a3c40",
             "target_type": "feeds_feed",
diff --git a/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json b/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json
index 9b5668b6b..b2e5e6a1d 100644
--- a/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json
+++ b/content/node.6d13ed35-7c06-41c2-afe7-847072a84d7a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "03045df60932b862e9b472db135f3986",
             "target_type": "feeds_feed",
diff --git a/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json b/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json
index 38e91d766..0ca585103 100644
--- a/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json
+++ b/content/node.6d87c24a-6453-48fd-9921-cede6b1b0001.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d474dfb74634c98fe69659a4f3c55620",
             "target_type": "feeds_feed",
diff --git a/content/node.6dac7a82-aecd-4bd2-9303-0383d77f4a88.json b/content/node.6dac7a82-aecd-4bd2-9303-0383d77f4a88.json
index eea672961..b680b8045 100644
--- a/content/node.6dac7a82-aecd-4bd2-9303-0383d77f4a88.json
+++ b/content/node.6dac7a82-aecd-4bd2-9303-0383d77f4a88.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "45ff9597-74a6-46d9-91a2-8d6e5b2c28a9"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 490d340f1..bd4da3797 100644
--- a/content/node.6e3be613-f4eb-4a14-87cd-398b0161eeda.json
+++ b/content/node.6e3be613-f4eb-4a14-87cd-398b0161eeda.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f626ebe8fc2c0602e0f849a7068055c7",
             "target_type": "feeds_feed",
diff --git a/content/node.6ed95c44-c301-4f53-8f87-6d33de758f7e.json b/content/node.6ed95c44-c301-4f53-8f87-6d33de758f7e.json
index f630ed2f4..e31e6077a 100644
--- a/content/node.6ed95c44-c301-4f53-8f87-6d33de758f7e.json
+++ b/content/node.6ed95c44-c301-4f53-8f87-6d33de758f7e.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "3b55c7cc-9994-42fd-aece-9c52889b875e"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 771f1ff01..7f62cda66 100644
--- a/content/node.6eeb79ee-eae2-41ea-ab7e-56f216daf636.json
+++ b/content/node.6eeb79ee-eae2-41ea-ab7e-56f216daf636.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I said <a href=\"/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        ",
+            "value": "\n          <p>Yesterday, I said <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I said <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e8c940daa789af9482140efa9f72c6fe",
             "target_type": "feeds_feed",
diff --git a/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json b/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json
index 1db08973d..4cc248a32 100644
--- a/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json
+++ b/content/node.6fb0a429-0264-4308-9436-f1115d5b108b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "55f785f8b5b1bcd8bf8f2c8c09ee1e1e",
             "target_type": "feeds_feed",
diff --git a/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json b/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json
index 731aa3c07..8aaa3e81b 100644
--- a/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json
+++ b/content/node.6fe4adb6-aae8-4a74-ba6b-9bdcd58b05b5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Previously when I gave my <a href=\"/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        ",
+            "value": "\n          <p>Previously when I gave my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Previously when I gave my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d4da3e8cb513d3d3feb0000033cee884",
             "target_type": "feeds_feed",
diff --git a/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json b/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json
index 4e41bec5b..3e7443ad4 100644
--- a/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json
+++ b/content/node.7039fa97-b91e-42c4-b974-c75ab08e4d51.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f85ae7fca421a364a7e48e49450abb31",
             "target_type": "feeds_feed",
diff --git a/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json b/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json
index 21d4a6db3..61186f9ef 100644
--- a/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json
+++ b/content/node.7064860b-42de-47c3-b5ac-3560d941fe0f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Today, whilst working on <a href=\"/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        ",
+            "value": "\n          <p>Today, whilst working on <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Today, whilst working on <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "04a7f9d899ae8eb0f4c33ff32a7dabae",
             "target_type": "feeds_feed",
diff --git a/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json b/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json
index c85b9ef9e..1f64b37eb 100644
--- a/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json
+++ b/content/node.70c71a01-1c5a-4b25-8706-d02a4284662e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2025\/01\/31\/rector\">take a look at Rector<\/a> which can automate it for you.<\/p>\n\n        ",
+            "value": "\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=\"\/daily\/2025\/01\/31\/rector\">take a look at Rector<\/a> which can automate it for you.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2025\/01\/31\/rector\">take a look at Rector<\/a> which can automate it for you.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6fe5dce6168b08b6f939c7125d2ebdb8",
             "target_type": "feeds_feed",
diff --git a/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json b/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json
index 44cede1c3..ba2d681d6 100644
--- a/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json
+++ b/content/node.711d2246-a181-4fe5-900d-c6e4fee3c29d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d6d6e37268d4aebacb46e15def1075f8",
             "target_type": "feeds_feed",
diff --git a/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json b/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json
index 4f0a76d14..e256fca6f 100644
--- a/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json
+++ b/content/node.71802d07-348e-45af-9fed-f4f8232b9142.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "531214c785675f0543e778a343d5a677",
             "target_type": "feeds_feed",
diff --git a/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json b/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json
index 8b21b048c..7e84cc44d 100644
--- a/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json
+++ b/content/node.71882aa6-8635-4242-ad8c-3676d9640060.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6bf45d9427593b0a048a809e9b03eb1b",
             "target_type": "feeds_feed",
diff --git a/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json b/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json
index bd70d7e11..113153108 100644
--- a/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json
+++ b/content/node.71e7e05f-a075-432a-bda3-db66b0e733cc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "36902cd3f90743c2ffd35168c819c294",
             "target_type": "feeds_feed",
diff --git a/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json b/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json
index f77522533..c0134866c 100644
--- a/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json
+++ b/content/node.720b01a3-3f38-46cd-8263-112571d62c60.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4931ceb5b78e05e6999e53dccad1f30d",
             "target_type": "feeds_feed",
diff --git a/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json b/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json
index e3b7ce11c..1b5077f4f 100644
--- a/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json
+++ b/content/node.7210b16f-71c2-44c4-9dc1-4264b243c618.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday I showed <a href=\"/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        ",
+            "value": "\n          <p>Yesterday I showed <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday I showed <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6a6105cc8b6ef3e9fadb5aec0f56aaeb",
             "target_type": "feeds_feed",
diff --git a/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json b/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json
index 0b9ac879e..e8239201c 100644
--- a/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json
+++ b/content/node.7281f569-60d5-45bd-8f3c-b01762098f77.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9de3480ade1a052c5db39773e18ab7f3",
             "target_type": "feeds_feed",
diff --git a/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json b/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json
index 57e874e90..c66267fc2 100644
--- a/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json
+++ b/content/node.72b2ca6d-de17-42a6-a0fd-1afdb1fc55d5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f16171ae436a71a3e9a07afc18cf2a36",
             "target_type": "feeds_feed",
diff --git a/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json b/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json
index 84edc5d4c..bcfa59a04 100644
--- a/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json
+++ b/content/node.72ee8411-6b32-45e5-96e1-2b749601a0ae.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9da4d3a86f1c672f86f84b3581e8b6e9",
             "target_type": "feeds_feed",
diff --git a/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json b/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json
index f1f5fbc40..630b5d6e7 100644
--- a/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json
+++ b/content/node.731a0026-d287-452b-96d7-aeaa3f4bec48.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "059042bee3271e131a06b01030f2f4fd",
             "target_type": "feeds_feed",
diff --git a/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json b/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json
index 5580f7392..c0db015be 100644
--- a/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json
+++ b/content/node.733458ea-e46c-49ed-8e8f-de95148cf0bc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "10d1ecac9f555ea67f22615547fb1f6a",
             "target_type": "feeds_feed",
diff --git a/content/node.739826e2-62a6-4726-8294-5359016f8d24.json b/content/node.739826e2-62a6-4726-8294-5359016f8d24.json
index 7abed12a3..f2c48f95e 100644
--- a/content/node.739826e2-62a6-4726-8294-5359016f8d24.json
+++ b/content/node.739826e2-62a6-4726-8294-5359016f8d24.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ea5781765624e864ecd53e39eda44615",
             "target_type": "feeds_feed",
diff --git a/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json b/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json
index 3b2d55cee..540ab7432 100644
--- a/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json
+++ b/content/node.73a5b2aa-74a8-4fe1-878f-9f264b1c32c3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week, I released the most recent episode of the <a href=\"/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=\"/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        ",
+            "value": "\n          <p>This week, I released the most recent episode of the <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>This week, I released the most recent episode of the <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4fe4a1ea6d73ab3a78060bfa1a6153e2",
             "target_type": "feeds_feed",
diff --git a/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json b/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json
index ad715796d..52b4f69c2 100644
--- a/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json
+++ b/content/node.73c4c40c-d5c3-462a-aba2-7ed0eb7fc1dc.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6549977c5d3e11dfcbc2dadcbeef7dea",
             "target_type": "feeds_feed",
diff --git a/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json b/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json
index 94770a65a..a4e733f3f 100644
--- a/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json
+++ b/content/node.74447b1a-33da-45b7-aa4b-a35e2afb6803.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>If you're working on a team or project that uses pull or merge requests, then <a href=\"/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=\"/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=\"/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        ",
+            "value": "\n          <p>If you're working on a team or project that uses pull or merge requests, then <a href=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>If you're working on a team or project that uses pull or merge requests, then <a href=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dc029e11f32f64e5a3c7d6d908e5572f",
             "target_type": "feeds_feed",
diff --git a/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json b/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json
index a7ea4cf97..3ac95a887 100644
--- a/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json
+++ b/content/node.74b360bb-61b3-4ed4-8942-1c21bdf630ef.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "90c94c7043655d521ff0ddc32b560713",
             "target_type": "feeds_feed",
diff --git a/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json b/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json
index b1a416126..bdcc7442a 100644
--- a/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json
+++ b/content/node.7502e17f-dfd7-46ad-9f34-2b0beca8aed3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c70e6f1af7689e9704999c27d288916d",
             "target_type": "feeds_feed",
diff --git a/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json b/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json
index 497e29174..92e31f568 100644
--- a/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json
+++ b/content/node.753da3d5-1cc0-40df-8afa-101986188a96.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1f1938498491ff40c88d4e5b99fc617b",
             "target_type": "feeds_feed",
diff --git a/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json b/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json
index c3c21312a..b2f11bc35 100644
--- a/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json
+++ b/content/node.75787d98-31be-4b33-a434-15d5a43c07af.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"/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=\"/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"/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        ",
+            "value": "\n          <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"\/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=\"\/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"/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=\"/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a776e5053b9f9b1276b131cb30130d86",
             "target_type": "feeds_feed",
diff --git a/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json b/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json
index d5491832e..3f40d7e45 100644
--- a/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json
+++ b/content/node.7586b569-6528-43ba-b0a4-a55de9faafb3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0cc84c28d13f650205484c629a9967a2",
             "target_type": "feeds_feed",
diff --git a/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json b/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json
index 3810f9f8b..fa13669ce 100644
--- a/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json
+++ b/content/node.759bb289-07cd-4103-bc90-107b7f13978d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In <a href=\"/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        ",
+            "value": "\n          <p>In <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9270caa76092aa60451a52a5d428601a",
             "target_type": "feeds_feed",
diff --git a/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json b/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json
index ca86bb569..0da60f7fc 100644
--- a/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json
+++ b/content/node.75e0f02d-1c15-4877-8443-724ddfaf45f6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "43ead52317b471703708839250e11a67",
             "target_type": "feeds_feed",
diff --git a/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json b/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json
index 86b033225..b96663317 100644
--- a/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json
+++ b/content/node.7678ac40-dfe5-43bd-98cc-37fa80affc7e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "befbe4ca73c04262f510b6bce517e12f",
             "target_type": "feeds_feed",
diff --git a/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json b/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json
index 7d87dede8..a98b3ffe5 100644
--- a/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json
+++ b/content/node.768ec43f-2c43-4071-9a7b-f53b5df43a33.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "029c147e61f92d36ce162b6e31eefed7",
             "target_type": "feeds_feed",
diff --git a/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json b/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json
index fdffd224f..5ff72c7df 100644
--- a/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json
+++ b/content/node.771941bc-1dab-4451-ad03-1cf809b2c511.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b46a6b2e5b2994af854133e567634c6c",
             "target_type": "feeds_feed",
diff --git a/content/node.77377a19-7488-40de-a041-f488b3ae597c.json b/content/node.77377a19-7488-40de-a041-f488b3ae597c.json
index eb674be79..e85505c96 100644
--- a/content/node.77377a19-7488-40de-a041-f488b3ae597c.json
+++ b/content/node.77377a19-7488-40de-a041-f488b3ae597c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b4f1eb8f00f69ca46c2ae3c230ebc37d",
             "target_type": "feeds_feed",
diff --git a/content/node.773bab66-561e-4954-9689-a7d817cbbb35.json b/content/node.773bab66-561e-4954-9689-a7d817cbbb35.json
index 6cacfc8c8..8ca491174 100644
--- a/content/node.773bab66-561e-4954-9689-a7d817cbbb35.json
+++ b/content/node.773bab66-561e-4954-9689-a7d817cbbb35.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "6e8c14dc-fa95-4ffa-b6ae-bd28519562f7"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 e5550f97f..281dec7d6 100644
--- a/content/node.781bcd5b-be77-4514-bffc-aa56d829aaff.json
+++ b/content/node.781bcd5b-be77-4514-bffc-aa56d829aaff.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0cb985cce483116ecdf0ef9bbb61febe",
             "target_type": "feeds_feed",
diff --git a/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json b/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json
index a1c979ea8..a2c803d8d 100644
--- a/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json
+++ b/content/node.78b682e0-a3be-4e49-990b-8fcc7083f6ca.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/daily\/2025\/02\/11\/tidy\">tidy up my own commits<\/a>, though, before I push them for anyone else to see.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/daily\/2025\/02\/11\/tidy\">tidy up my own commits<\/a>, though, before I push them for anyone else to see.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/daily\/2025\/02\/11\/tidy\">tidy up my own commits<\/a>, though, before I push them for anyone else to see.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4fba08380c1f4dbf231499fd7ddea935",
             "target_type": "feeds_feed",
diff --git a/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json b/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json
index 33a2379ab..f097b5cdf 100644
--- a/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json
+++ b/content/node.790a6cce-23fa-4e8b-8ed7-0d83ed40acb1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3e72cb7c3d2fb565211c4e716fbe236a",
             "target_type": "feeds_feed",
diff --git a/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json b/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json
index d08b601e8..9f681818b 100644
--- a/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json
+++ b/content/node.792953b8-b5f7-44dc-8e32-d70629bf06a4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3da78a8b0a4a8e0177c79d863316c825",
             "target_type": "feeds_feed",
diff --git a/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json b/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json
index 385bc825d..3b83f8ba2 100644
--- a/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json
+++ b/content/node.7980b93f-4708-4499-8047-08cb9469b4f2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "42c6dd915ed7b6d8f3872f4c213105fb",
             "target_type": "feeds_feed",
diff --git a/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json b/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json
index 464d10122..75b792691 100644
--- a/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json
+++ b/content/node.7987b079-7f85-4303-ab3c-1338dbeaf171.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week, I gave my <a href=\"/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=\"/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        ",
+            "value": "\n          <p>This week, I gave my <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>This week, I gave my <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b42fcb964b1303b371ff145dd35982e1",
             "target_type": "feeds_feed",
diff --git a/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json b/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json
index 24d48563c..5f4767f4f 100644
--- a/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json
+++ b/content/node.7989ae69-0f6d-4a7d-b560-d828f76cfba4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4b2d47376db0c887f15bedf49de35711",
             "target_type": "feeds_feed",
diff --git a/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json b/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json
index c60169e89..87d2e3ebf 100644
--- a/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json
+++ b/content/node.79ce3fb5-ecce-4b0f-96a2-bf7094473416.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f0b824f4d171e8138cf1c6b8e9bf5604",
             "target_type": "feeds_feed",
diff --git a/content/node.79fdad19-834d-463e-89f6-059c0865a034.json b/content/node.79fdad19-834d-463e-89f6-059c0865a034.json
index a84a55f9b..984646153 100644
--- a/content/node.79fdad19-834d-463e-89f6-059c0865a034.json
+++ b/content/node.79fdad19-834d-463e-89f6-059c0865a034.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A great thing about <a href=\"/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        ",
+            "value": "\n          <p>A great thing about <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A great thing about <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "66179cf5075396d9979accd64d8ccb0d",
             "target_type": "feeds_feed",
diff --git a/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json b/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json
index 73a123fa8..a1bb92473 100644
--- a/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json
+++ b/content/node.7a3bb308-78bb-4f7f-97cf-91407fbe92a4.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ecc568cf8fbe4c5c917c60aaa6ec3460",
             "target_type": "feeds_feed",
diff --git a/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json b/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json
index 98459b3cd..486f8536c 100644
--- a/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json
+++ b/content/node.7a90ce1b-f0d9-443b-b143-b82562fef529.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "550456dfd70a84795f8c61ba84691a1d",
             "target_type": "feeds_feed",
diff --git a/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json b/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json
index 660448d23..e0afc289c 100644
--- a/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json
+++ b/content/node.7ab39604-1f7a-48e6-bd9c-50cfc30e8dfa.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "39ad9b31772a4824f9e1b5335fbb0b48",
             "target_type": "feeds_feed",
diff --git a/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json b/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json
index f3fc32fa3..7b2940c8f 100644
--- a/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json
+++ b/content/node.7b10727a-2349-4337-8e3e-9ae04f0e98c2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "74bd5f418ef3374adbd56755b08e95bb",
             "target_type": "feeds_feed",
diff --git a/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json b/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json
index 99bc4e55c..d75ee019d 100644
--- a/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json
+++ b/content/node.7b5a2a03-3f09-4876-8f0d-8056485566e8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ed6e2359d50107af3a75d41ec9f33762",
             "target_type": "feeds_feed",
diff --git a/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json b/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json
index 35784c31f..db8b33772 100644
--- a/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json
+++ b/content/node.7b639ca0-4e69-4b39-8815-a9d3c712cf9d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "02bc3a05396c873cc0f9bed77cfe2d63",
             "target_type": "feeds_feed",
diff --git a/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json b/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json
index c51fa57c5..0a8f0e285 100644
--- a/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json
+++ b/content/node.7b840e91-b45a-4403-8b34-6b9b4dda2ebf.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f29346ee784205182d857cb2d30f2d23",
             "target_type": "feeds_feed",
diff --git a/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json b/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json
index 5f59443de..b1767f382 100644
--- a/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json
+++ b/content/node.7bc6b922-ec23-4389-8466-ffd96db33b29.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "47bd091b2e6434c4dab3ae5151f7881c",
             "target_type": "feeds_feed",
diff --git a/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json b/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json
index f83b02906..13c42eb0b 100644
--- a/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json
+++ b/content/node.7bcb6ac6-003e-4c30-ae6d-f919a2cb5195.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b1298d5da5638a46cefadc614b1673e6",
             "target_type": "feeds_feed",
diff --git a/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json b/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json
index 5c4035eb3..51c78980e 100644
--- a/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json
+++ b/content/node.7c632749-fb6d-4407-a8f2-aac72d959a4d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d8831ac5b7ba46ed9c5772cb19a46954",
             "target_type": "feeds_feed",
diff --git a/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json b/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json
index e571b5f77..3cc1e3b2a 100644
--- a/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json
+++ b/content/node.7d242a44-c31b-419e-848e-73eba79f962e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "157de5e6e946c20d3a97800528ded3fa",
             "target_type": "feeds_feed",
diff --git a/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json b/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json
index c39648498..8b7bee50f 100644
--- a/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json
+++ b/content/node.7e93586c-c6a0-410a-ae83-a1d50bc12743.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In previous emails, <a href=\"/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=\"/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        ",
+            "value": "\n          <p>In previous emails, <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In previous emails, <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5be7c33a9387a20f7181ac5805318554",
             "target_type": "feeds_feed",
diff --git a/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json b/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json
index dfd2f0636..b5a07dd8f 100644
--- a/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json
+++ b/content/node.7f4e5764-db9a-4cb2-b9c4-08618c6737b7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e96f6c60d2ba5103f1f830ef50fc6fb2",
             "target_type": "feeds_feed",
diff --git a/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json b/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json
index 0af985279..b680641d2 100644
--- a/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json
+++ b/content/node.7f8ffdde-2056-4739-bfe6-cbb0a4de37ae.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "44157cba9274734c7d7c0029601ad594",
             "target_type": "feeds_feed",
diff --git a/content/node.7fab23fc-6ea7-432b-86da-ec32dfc008ab.json b/content/node.7fab23fc-6ea7-432b-86da-ec32dfc008ab.json
index 9a3b0ed87..1328f467e 100644
--- a/content/node.7fab23fc-6ea7-432b-86da-ec32dfc008ab.json
+++ b/content/node.7fab23fc-6ea7-432b-86da-ec32dfc008ab.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 455eb3f6f..0460f0a13 100644
--- a/content/node.7fce2f3b-7564-40a0-8dfc-741c66a3b993.json
+++ b/content/node.7fce2f3b-7564-40a0-8dfc-741c66a3b993.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/blog\/uis-ive-rebuilt-tailwind-css\">number of existing sites<\/a> as examples and written some <a href=\"/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        ",
+            "value": "\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=\"\/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=\"\/blog\/uis-ive-rebuilt-tailwind-css\">number of existing sites<\/a> as examples and written some <a href=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/blog\/uis-ive-rebuilt-tailwind-css\">number of existing sites<\/a> as examples and written some <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "94469e62075ac965bc1432cadee4e2eb",
             "target_type": "feeds_feed",
diff --git a/content/node.7fe05b4e-044a-4426-8fce-538781450976.json b/content/node.7fe05b4e-044a-4426-8fce-538781450976.json
index 644296c52..5bedc8f7a 100644
--- a/content/node.7fe05b4e-044a-4426-8fce-538781450976.json
+++ b/content/node.7fe05b4e-044a-4426-8fce-538781450976.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "306b315a-03c4-4f06-a396-cf0906676d47"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 e4e7402a6..4b78072ce 100644
--- a/content/node.7fe749a2-90b7-4d22-9dff-56eaa7adb3d5.json
+++ b/content/node.7fe749a2-90b7-4d22-9dff-56eaa7adb3d5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "413c39dc33012102e00c123c13251c85",
             "target_type": "feeds_feed",
diff --git a/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json b/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json
index ce33aa0a9..6cfddc71f 100644
--- a/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json
+++ b/content/node.805363c0-2306-47f5-b9ba-57995ebe12b3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "06fce1aaa4c20b2a830e2a22ab305a5e",
             "target_type": "feeds_feed",
diff --git a/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json b/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json
index cf71e0bbe..2550d542e 100644
--- a/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json
+++ b/content/node.80c27b8b-ebb6-486e-9fb8-a4d29ade396c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "05bef1d24f084368e652eb41e2831725",
             "target_type": "feeds_feed",
diff --git a/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json b/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json
index 8aa7f45bf..643de7486 100644
--- a/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json
+++ b/content/node.8108dc36-1eb3-487b-9c03-600c49a6d11c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "517f057d243494aec133607af3972ad8",
             "target_type": "feeds_feed",
diff --git a/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json b/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json
index a270b7a17..d7a085e24 100644
--- a/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json
+++ b/content/node.81676cf3-0b30-4619-a922-12ff3e16ba76.json
@@ -82,9 +82,9 @@
     ],
     "body": [
         {
-            "value": "<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=\"/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=\"/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=\"/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 {\r\n  listen localhost:8095:\r\n  server_name www.oliverdavies.uk:\r\n  root \/var\/www\/vhosts\/website-sculpin;\r\n\r\n  location \/ {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n  }\r\n\r\n  location ~ ^\/archive {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/core {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/daily\/.+ {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/homelab {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/podcast {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/sites\/default\/files {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/themes\/custom\/opdavies {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n}<\/code><\/pre><p>This is the same approach as <a href=\"/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>",
+            "value": "<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=\"\/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=\"\/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=\"\/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 {\r\n  listen localhost:8095:\r\n  server_name www.oliverdavies.uk:\r\n  root \/var\/www\/vhosts\/website-sculpin;\r\n\r\n  location \/ {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n  }\r\n\r\n  location ~ ^\/archive {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/core {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/daily\/.+ {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/homelab {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/podcast {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/sites\/default\/files {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n\r\n  location ~ ^\/themes\/custom\/opdavies {\r\n    try_files $uri $uri.html $uri\/index.html =404;\r\n    root \/var\/www\/vhosts\/website-tome;\r\n  }\r\n}<\/code><\/pre><p>This is the same approach as <a href=\"\/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>",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/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=\"/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>",
+            "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": ""
         }
     ],
diff --git a/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json b/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json
index 562e34552..e61b3e777 100644
--- a/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json
+++ b/content/node.8174931b-97d3-457f-8822-00c905fe9e1d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7935da166360b58eee6cda5b341491bc",
             "target_type": "feeds_feed",
diff --git a/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json b/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json
index 7790b0458..9143adbc2 100644
--- a/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json
+++ b/content/node.81e54ee3-c438-49d9-9450-27cafa5a7fae.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "60b18ba23e94d04d883b816e371d3836",
             "target_type": "feeds_feed",
diff --git a/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json b/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json
index fd5f399d9..0454b98e5 100644
--- a/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json
+++ b/content/node.81f03f9e-6abc-45f9-8d8d-73e7722b30b7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2527d9b10a1752a2435693a747d98027",
             "target_type": "feeds_feed",
diff --git a/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json b/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json
index 9b97a567b..eaa699ce2 100644
--- a/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json
+++ b/content/node.820927f5-8c13-4b77-acb7-fae7fb55b459.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0a69c3b2809135b0b34a0adb490b0aba",
             "target_type": "feeds_feed",
diff --git a/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json b/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json
index 835e0d89b..1bc13bb75 100644
--- a/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json
+++ b/content/node.82672338-b561-408d-a17e-902c1f37e6a9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cfa95fab36c01cd4b2f5e179c30c8d76",
             "target_type": "feeds_feed",
diff --git a/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json b/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json
index de00cbdbb..7b2f296fb 100644
--- a/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json
+++ b/content/node.82839e74-b53c-4d18-af5d-024d8f09fb3f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c777affc63c0cf359d64d0b1d6b7a2b7",
             "target_type": "feeds_feed",
diff --git a/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json b/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json
index b86e65ff9..88313eef3 100644
--- a/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json
+++ b/content/node.8290cf4e-cbbc-415d-b185-cbaba90d42d1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Since <a href=\"/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=\"/podcast\/12-nick-janetakis-docker\">episode with Nick on the Beyond Blocks podcast<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>Since <a href=\"\/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=\"\/podcast\/12-nick-janetakis-docker\">episode with Nick on the Beyond Blocks podcast<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>Since <a href=\"/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=\"/podcast\/12-nick-janetakis-docker\">episode with Nick on the Beyond Blocks podcast<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "15848211557ccf2961d0bab3eb078103",
             "target_type": "feeds_feed",
diff --git a/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json b/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json
index 518a4e106..791ca4676 100644
--- a/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json
+++ b/content/node.8293455b-3322-4e45-a24a-2d64f77db033.json
@@ -84,13 +84,13 @@
         {
             "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"\/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "da50f1968f98fdd321596a74d98b2ec4",
             "target_type": "feeds_feed",
diff --git a/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json b/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json
index 7e2b54914..a141ae555 100644
--- a/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json
+++ b/content/node.82af7a87-a737-49cd-84a0-872e820d9c91.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week, I spoke with <a href=\"https:\/\/mark.ie\">Mark Conroy<\/a> for an upcoming episode of the <a href=\"/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        ",
+            "value": "\n          <p>This week, I spoke with <a href=\"https:\/\/mark.ie\">Mark Conroy<\/a> for an upcoming episode of the <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>This week, I spoke with <a href=\"https:\/\/mark.ie\">Mark Conroy<\/a> for an upcoming episode of the <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "680c0fd0f51522dacede739c63e5cc66",
             "target_type": "feeds_feed",
diff --git a/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json b/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json
index b2101e7eb..c45c86835 100644
--- a/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json
+++ b/content/node.82f12dce-4db3-44d8-9eff-b24feb20d568.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/build-configs\">Build Configs<\/a> is a tool I wrote and recently <a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/build-configs\">Build Configs<\/a> is a tool I wrote and recently <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/build-configs\">Build Configs<\/a> is a tool I wrote and recently <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1ee4600295e86488919b3420dfa02534",
             "target_type": "feeds_feed",
diff --git a/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json b/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json
index c1cf76278..4e3ded332 100644
--- a/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json
+++ b/content/node.82f169a8-a9cf-4705-abaa-f8e29912aa9f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Regardless of <a href=\"/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        ",
+            "value": "\n          <p>Regardless of <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Regardless of <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "edb67464b9188fe49c1cef46dfa04ac8",
             "target_type": "feeds_feed",
diff --git a/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json b/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json
index 80bfb0ca7..e8527c4c4 100644
--- a/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json
+++ b/content/node.82f39468-d922-4a18-88d4-9ef7b8b366f1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ad8edfa32b635972a3fba18023827d89",
             "target_type": "feeds_feed",
diff --git a/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json b/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json
index b75af2443..770505f03 100644
--- a/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json
+++ b/content/node.83443749-8720-4aa7-95b1-9c35e88f094f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/blog\/uis-ive-rebuilt-tailwind-css\">other UIs I've rebuilt with Tailwind<\/a> - some of which I show in my <a href=\"/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=\"/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        ",
+            "value": "\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=\"\/blog\/uis-ive-rebuilt-tailwind-css\">other UIs I've rebuilt with Tailwind<\/a> - some of which I show in my <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/blog\/uis-ive-rebuilt-tailwind-css\">other UIs I've rebuilt with Tailwind<\/a> - some of which I show in my <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ba45cf6bd571c26a3efb9057e7bc5fd3",
             "target_type": "feeds_feed",
diff --git a/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json b/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json
index e14b09b7e..ef6709a2e 100644
--- a/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json
+++ b/content/node.83887671-81a2-4ffc-884c-a2d1b8ccacfa.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1777ed82a3c678a09b17f1c159f7b5cd",
             "target_type": "feeds_feed",
diff --git a/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json b/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json
index 2b2cd48f3..92199e58a 100644
--- a/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json
+++ b/content/node.83916d2b-f03f-4add-9276-5080b66925b4.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d42eb72698b1793f4f2c361ad4470d81",
             "target_type": "feeds_feed",
diff --git a/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json b/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json
index d704d266c..7e78d9db2 100644
--- a/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json
+++ b/content/node.848ad0c5-2fab-4481-8e84-72db6bdc6d2e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "770e300e666c4816b8e8fc9943555225",
             "target_type": "feeds_feed",
diff --git a/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json b/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json
index 829a16139..c33e19b55 100644
--- a/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json
+++ b/content/node.84a6f9be-759c-42ea-815b-6b29a90b7742.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5c2783e9ca75aee09edea870a5cf5f42",
             "target_type": "feeds_feed",
diff --git a/content/node.84decda9-d30b-4cd0-b468-937a7e47776b.json b/content/node.84decda9-d30b-4cd0-b468-937a7e47776b.json
index 3a8f01654..bcdcfea97 100644
--- a/content/node.84decda9-d30b-4cd0-b468-937a7e47776b.json
+++ b/content/node.84decda9-d30b-4cd0-b468-937a7e47776b.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "3e21966a-6812-420b-aca1-0aa641dbb5a2"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 c9a732f4f..5eec4c4a9 100644
--- a/content/node.84ede6fa-2682-4edf-8b22-ee603de0b8c7.json
+++ b/content/node.84ede6fa-2682-4edf-8b22-ee603de0b8c7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday I wrote about <a href=\"/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        ",
+            "value": "\n          <p>Yesterday I wrote about <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday I wrote about <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "64930ff9734d8caf5d32c9d3840e4b0a",
             "target_type": "feeds_feed",
diff --git a/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json b/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json
index 23eed1594..59a118826 100644
--- a/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json
+++ b/content/node.85b61d26-e598-4b64-99b4-445d8d22fba5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ef470110690cdf26694bb4a29a3c1255",
             "target_type": "feeds_feed",
diff --git a/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json b/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json
index c26d35677..e258be281 100644
--- a/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json
+++ b/content/node.862ba3ee-9c27-40e6-9e86-a5ce4c1bae67.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bbdb6758f1c4bd5875133b5b5a4314a5",
             "target_type": "feeds_feed",
diff --git a/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json b/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json
index 8bca54798..cdf3ecd5a 100644
--- a/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json
+++ b/content/node.86c57486-ce6b-45ae-b953-2f15ae8cf0cb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9014cd6aad9e046cc2bea06ae3204989",
             "target_type": "feeds_feed",
diff --git a/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json b/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json
index 914447598..843390287 100644
--- a/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json
+++ b/content/node.8766d230-d3d4-45fb-82a6-2dbaec0c775b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A few days ago, I asked <a href=\"/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        ",
+            "value": "\n          <p>A few days ago, I asked <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A few days ago, I asked <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8704d7b04d607a1f28ca76b40770dae4",
             "target_type": "feeds_feed",
diff --git a/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json b/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json
index 4f1cd15bc..1d69d4f65 100644
--- a/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json
+++ b/content/node.88914f01-f0d5-49fd-ab1f-e756a3ddfd8d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dbe97e5743e2c4d9c4744f379dcd2428",
             "target_type": "feeds_feed",
diff --git a/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json b/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json
index 65c2395c9..3e8beb616 100644
--- a/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json
+++ b/content/node.898e3ece-caad-49b2-8486-400e653eea9d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2bb59d5691c8de6da82be10d5c3b871c",
             "target_type": "feeds_feed",
diff --git a/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json b/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json
index 8daa774fc..6dbf6a615 100644
--- a/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json
+++ b/content/node.8a0608f1-361e-4618-a9a8-8ec2e2d1397e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "45f407c2e5e4e066da156bd49eb7991a",
             "target_type": "feeds_feed",
diff --git a/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json b/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json
index e92d9748f..da1805614 100644
--- a/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json
+++ b/content/node.8a862cc4-ceb9-4ff7-8e1c-2b01cd7e1a09.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bbe07c03d6666a63b4f31aef9e1ef5d3",
             "target_type": "feeds_feed",
diff --git a/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json b/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json
index e52c24022..c7ab6e391 100644
--- a/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json
+++ b/content/node.8a88f79c-3593-4316-8308-8bbc9622d0ec.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "77a04f54c7ca12e8f95a6282d7667d35",
             "target_type": "feeds_feed",
diff --git a/content/node.8a979843-907c-49d9-abaf-a21b0432e648.json b/content/node.8a979843-907c-49d9-abaf-a21b0432e648.json
index 7aace3336..3b69b53ad 100644
--- a/content/node.8a979843-907c-49d9-abaf-a21b0432e648.json
+++ b/content/node.8a979843-907c-49d9-abaf-a21b0432e648.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "6e8c14dc-fa95-4ffa-b6ae-bd28519562f7"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 df268a68e..96efe88e7 100644
--- a/content/node.8b3f37aa-64aa-4d89-8593-52cbf781b713.json
+++ b/content/node.8b3f37aa-64aa-4d89-8593-52cbf781b713.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5c4a4fd75b5b1c31d731d1445a90003d",
             "target_type": "feeds_feed",
diff --git a/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json b/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json
index bac177c6f..44e0b4534 100644
--- a/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json
+++ b/content/node.8b6d9371-69a3-4cbe-ac76-13aecbb4c468.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a4dd64d8e6ca0ab3625278ad7028abfa",
             "target_type": "feeds_feed",
diff --git a/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json b/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json
index 2e97e407f..7d6de5bf1 100644
--- a/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json
+++ b/content/node.8b84ccf4-bb4b-48fd-8009-2c2641466185.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7f55d425fa5b0836f5c8d0f6980cc54e",
             "target_type": "feeds_feed",
diff --git a/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json b/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json
index 6823c7888..193deb86a 100644
--- a/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json
+++ b/content/node.8bcfc61c-0285-4034-ac7b-a3ba7559fba2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "de94dc72634b64860368d368dd1b936a",
             "target_type": "feeds_feed",
diff --git a/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json b/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json
index 41dcc9aa7..16ff39f14 100644
--- a/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json
+++ b/content/node.8be3d8d9-4e73-49db-93a6-83349ac1af05.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5433ca25d20eea02dd4ac8345d46c026",
             "target_type": "feeds_feed",
diff --git a/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json b/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json
index 8838cd1c0..c6b9af28f 100644
--- a/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json
+++ b/content/node.8e31643d-a697-4068-8692-cdc472b96e90.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4b09fa0814819f49425fd0eb6bf68e75",
             "target_type": "feeds_feed",
diff --git a/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json b/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json
index 625b2574a..87f580fc0 100644
--- a/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json
+++ b/content/node.8ee882f8-f25b-4ae7-9dc3-aedc78ee0998.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A couple of weeks ago, I wrote that <a href=\"/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        ",
+            "value": "\n          <p>A couple of weeks ago, I wrote that <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A couple of weeks ago, I wrote that <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a4594c6103d2d62b9550cde5004820f8",
             "target_type": "feeds_feed",
diff --git a/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json b/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json
index 4441b1f90..7aa8864ea 100644
--- a/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json
+++ b/content/node.8eeee62a-a2ae-4af6-b15f-2cbbe81eaeda.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e59143196c70adc39a01487205db060b",
             "target_type": "feeds_feed",
diff --git a/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json b/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json
index 024776fb7..8c2f2d2a1 100644
--- a/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json
+++ b/content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0eeef7ecb5ae126ae9d82df72eb13277",
             "target_type": "feeds_feed",
diff --git a/content/node.90791de2-4132-43e3-94ea-41609f317429.json b/content/node.90791de2-4132-43e3-94ea-41609f317429.json
index 3685c0807..1396d3714 100644
--- a/content/node.90791de2-4132-43e3-94ea-41609f317429.json
+++ b/content/node.90791de2-4132-43e3-94ea-41609f317429.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ec8d13cd01af70105278b0ff6c81493c",
             "target_type": "feeds_feed",
diff --git a/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json b/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json
index fd92f97eb..45de69e72 100644
--- a/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json
+++ b/content/node.90834219-4fa0-4db8-a34e-9a4e7b017359.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "da87df7942e8c7bb996fcc8856ebaf7a",
             "target_type": "feeds_feed",
diff --git a/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json b/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json
index 8b10f4c4a..fe14883ca 100644
--- a/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json
+++ b/content/node.90b4b442-bc96-4b9f-9e1b-70112f628de8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "df97490d71b0f6f78a149c80f0c301f5",
             "target_type": "feeds_feed",
diff --git a/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json b/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json
index 90bdec120..b4fce1bec 100644
--- a/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json
+++ b/content/node.91985c48-6ce5-4270-8f51-478299bb9284.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6b0fad90dfe0aa71566d4a773bb78d7a",
             "target_type": "feeds_feed",
diff --git a/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json b/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json
index 4eebf5637..831020997 100644
--- a/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json
+++ b/content/node.92168b2b-6e46-4548-a7b0-824c862126e3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "222b248251326ba2fe44041d0e2f159a",
             "target_type": "feeds_feed",
diff --git a/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json b/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json
index 793818010..96ec3ffc1 100644
--- a/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json
+++ b/content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a689477a80adb90fdbe7160be7d2450e",
             "target_type": "feeds_feed",
diff --git a/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json b/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json
index 558f45b44..cb4985573 100644
--- a/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json
+++ b/content/node.92cbe949-7398-4e53-b101-11fd2140c868.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "05685b54939905d0714bbd9c928bd011",
             "target_type": "feeds_feed",
diff --git a/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json b/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json
index 06ed109ca..8b726d5f6 100644
--- a/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json
+++ b/content/node.93b8a0b3-9766-47b1-a8bc-03975d6f3063.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "afd0a9a1478406d663af9a2abb8eedae",
             "target_type": "feeds_feed",
diff --git a/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json b/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json
index aa02e9895..645b0b302 100644
--- a/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json
+++ b/content/node.94472cb5-7302-4b56-9fb8-ad96fe2971f8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/presentations\/tdd-test-driven-drupal\">Test-Driven Drupal talk<\/a> are online.<\/p>\n\n        ",
+            "value": "\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=\"\/presentations\/tdd-test-driven-drupal\">Test-Driven Drupal talk<\/a> are online.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/presentations\/tdd-test-driven-drupal\">Test-Driven Drupal talk<\/a> are online.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "00dc66fc251e796aa7a1f167673d4f33",
             "target_type": "feeds_feed",
diff --git a/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json b/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json
index 0aa53409b..7defeac6e 100644
--- a/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json
+++ b/content/node.94d78d4d-fcd1-4d1a-a0fc-e6f8c39d084b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d2e8d39f68f4ae6ba0c9ffab688585b7",
             "target_type": "feeds_feed",
diff --git a/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json b/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json
index 5465e9ce7..6062f660c 100644
--- a/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json
+++ b/content/node.9533c89f-d5dd-4959-ba2c-66be5df70f60.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "60c7b0989070ede0d263c59ede0bc4d4",
             "target_type": "feeds_feed",
diff --git a/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json b/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json
index 19432d132..d2b571dab 100644
--- a/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json
+++ b/content/node.95476ad8-f2dd-4667-99a5-5a5309299702.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e1820905156cf1adfe5f3e7514f30eb2",
             "target_type": "feeds_feed",
diff --git a/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json b/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json
index 1d1b4667e..369ab4bc5 100644
--- a/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json
+++ b/content/node.95a128d2-01a1-4e31-a6de-33bc7c091269.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b9eb71111ebc108eadaa0b9fae7d84ff",
             "target_type": "feeds_feed",
diff --git a/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json b/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json
index 64434cfbf..3b23f8860 100644
--- a/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json
+++ b/content/node.95f8e010-8e75-4da2-ac05-b59763888535.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c3c98eabf22507f37576fbd83774fdc3",
             "target_type": "feeds_feed",
diff --git a/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json b/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json
index cf13baad4..6840f0ed9 100644
--- a/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json
+++ b/content/node.960814d3-b3bd-4a5a-a541-906c1e121902.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In one of the lessons in my <a href=\"/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=\"/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        ",
+            "value": "\n          <p>In one of the lessons in my <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In one of the lessons in my <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c22cd0a275dfae98de9b0fedf7c17fd2",
             "target_type": "feeds_feed",
diff --git a/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json b/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json
index 90217600d..67fa12809 100644
--- a/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json
+++ b/content/node.97127b95-b383-490a-af5f-62e60aa11f0f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as using <a href=\"/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=\"/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=\"/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=\"/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">maintain my own open source software projects<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>As well as using <a href=\"\/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=\"\/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=\"\/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=\"\/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">maintain my own open source software projects<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as using <a href=\"/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=\"/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=\"/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=\"/daily\/2024\/03\/09\/override-node-options-40624-drupal-websites\">maintain my own open source software projects<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cb55832959bd5f053aa3c4766a247f91",
             "target_type": "feeds_feed",
diff --git a/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json b/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json
index 0f3830c02..d1549a04c 100644
--- a/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json
+++ b/content/node.97ba47f0-b202-4ac4-974f-6bb9a50abb38.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a23f721f43c2ea925dd0e3d1b57188c9",
             "target_type": "feeds_feed",
diff --git a/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json b/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json
index 97f7dce8f..bc54cd600 100644
--- a/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json
+++ b/content/node.9834732b-1b38-471a-b1bb-64471b27a2ee.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b38408f033b23dc55649c0a05a3af78b",
             "target_type": "feeds_feed",
diff --git a/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json b/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json
index 37c09597b..de1b14835 100644
--- a/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json
+++ b/content/node.987bb32d-4dc3-49ff-bc30-2563ea769769.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently installed an application called Gitea <a href=\"/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        ",
+            "value": "\n          <p>I recently installed an application called Gitea <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently installed an application called Gitea <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ec1b7c6047417070fb9d7336a9849a98",
             "target_type": "feeds_feed",
diff --git a/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json b/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json
index 2a545f49d..98c2b02ed 100644
--- a/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json
+++ b/content/node.98d20258-bdbe-4286-a2d2-36dc4722cac1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "859a0b5a56a896a9cc602a3a1bbc3bae",
             "target_type": "feeds_feed",
diff --git a/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json b/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json
index c06e71551..e9d3450d5 100644
--- a/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json
+++ b/content/node.98e6a250-a27f-41c2-8685-e80474a2d174.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c81fcb760babf4b27ac37f42d606aade",
             "target_type": "feeds_feed",
diff --git a/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json b/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json
index 512052bea..436580e9a 100644
--- a/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json
+++ b/content/node.9986a906-35f4-4e86-8dc7-27b8e1f64be8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "26af65ffd563616c16d70721cbce516d",
             "target_type": "feeds_feed",
diff --git a/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json b/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json
index cb8e2e674..77377bea6 100644
--- a/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json
+++ b/content/node.99989cd7-1f79-4f8e-abf1-12b69bc7ee1c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A few days ago, I wrote about <a href=\"/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        ",
+            "value": "\n          <p>A few days ago, I wrote about <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A few days ago, I wrote about <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6f566971a35889eee0927fe88991b9e9",
             "target_type": "feeds_feed",
diff --git a/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json b/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json
index 4b1154c4a..8f95b8e6d 100644
--- a/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json
+++ b/content/node.999e4bc2-3d7a-4d73-9f5e-62363accde44.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "850f3e0675f0598a361d17b99f568768",
             "target_type": "feeds_feed",
diff --git a/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json b/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json
index e82ce9865..2dc639861 100644
--- a/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json
+++ b/content/node.99c87aed-1bac-4f19-9ae2-15e2ccd9cd02.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently <a href=\"/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=\"/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        ",
+            "value": "\n          <p>I recently <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "15704c55f5e3b5d6531dc8c8e9ae0182",
             "target_type": "feeds_feed",
diff --git a/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json b/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json
index b9381e160..2c6f0986b 100644
--- a/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json
+++ b/content/node.9a9bcb91-1a60-4126-8a14-d477544568d1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "60ee5cbd523e01444113724332b468eb",
             "target_type": "feeds_feed",
diff --git a/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json b/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json
index b7ba13663..fcd0342a1 100644
--- a/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json
+++ b/content/node.9aba3fab-cb0a-4ea1-a439-9ff419b23841.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "20f663e70965fc6a0abdf47d7dcc5c90",
             "target_type": "feeds_feed",
diff --git a/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json b/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json
index 688492bac..437bffdbc 100644
--- a/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json
+++ b/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "74d7fe2b760e2005106513cfa1b4cae7",
             "target_type": "feeds_feed",
diff --git a/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json b/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json
index 172754fe9..5be85c988 100644
--- a/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json
+++ b/content/node.9b65d27f-65f6-4913-b142-a1a128ebf21f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2a00495abcb2b4fb956be9ee3bf4582e",
             "target_type": "feeds_feed",
diff --git a/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json b/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json
index 5e8d8b1f5..c9ae1381f 100644
--- a/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json
+++ b/content/node.9c40a0cb-0fb2-4f9d-8e69-60b3a2b4ddd3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "59a601afa0b33fe6c4acdffa4bbb1e64",
             "target_type": "feeds_feed",
diff --git a/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json b/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json
index bd175d7ef..d23e96e1b 100644
--- a/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json
+++ b/content/node.9cc91e25-0d1b-4a93-b367-7da047fce99e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5608e282cfbf2d9573fec34289172c58",
             "target_type": "feeds_feed",
diff --git a/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json b/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json
index 93baab386..5a7399971 100644
--- a/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json
+++ b/content/node.9d0e577d-eca2-4b05-9266-00f94901ae69.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9297110388cf153de83397c7246c18c5",
             "target_type": "feeds_feed",
diff --git a/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json b/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json
index c8e5215a6..21ead8d3f 100644
--- a/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json
+++ b/content/node.9d57dff8-de30-4e32-8278-c5a947ef8c25.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5c4e15d5b064e06491b78bb0021c82a7",
             "target_type": "feeds_feed",
diff --git a/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json b/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json
index b2bbb1803..082d552a3 100644
--- a/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json
+++ b/content/node.9d63cfe9-dd20-4e58-955f-bd42a5026c8a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2025\/03\/21\/phpdoc\">PHPStan PHPDoc types<\/a>, there's no need to repeat what the code already says.<\/p>\n\n        ",
+            "value": "\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=\"\/daily\/2025\/03\/21\/phpdoc\">PHPStan PHPDoc types<\/a>, there's no need to repeat what the code already says.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2025\/03\/21\/phpdoc\">PHPStan PHPDoc types<\/a>, there's no need to repeat what the code already says.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0dcfb92613016648b8799e1ee65ada87",
             "target_type": "feeds_feed",
diff --git a/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json b/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json
index 222032914..6913bf562 100644
--- a/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json
+++ b/content/node.9dcd7b33-b2bc-41b1-9d17-f7536a670343.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/atdc\">free Drupal testing email course<\/a> or <a href=\"/call\">book a 1-on-1 consulting call<\/a> and I'll get you started.<\/p>\n\n        ",
+            "value": "\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=\"\/atdc\">free Drupal testing email course<\/a> or <a href=\"\/call\">book a 1-on-1 consulting call<\/a> and I'll get you started.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/atdc\">free Drupal testing email course<\/a> or <a href=\"/call\">book a 1-on-1 consulting call<\/a> and I'll get you started.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d1af70181dbb0fa7bc1126c999977ec5",
             "target_type": "feeds_feed",
diff --git a/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json b/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json
index 434e7eb8c..1ebef18d9 100644
--- a/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json
+++ b/content/node.9deec245-c96a-44f5-a54c-95f61611051d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently started <a href=\"/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        ",
+            "value": "\n          <p>I recently started <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently started <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bd5f1ef86b1ea8d5f9af419bd836ded3",
             "target_type": "feeds_feed",
diff --git a/content/node.9e094927-a767-437b-b3b7-90a5bea35da0.json b/content/node.9e094927-a767-437b-b3b7-90a5bea35da0.json
index 3ec192817..618168e79 100644
--- a/content/node.9e094927-a767-437b-b3b7-90a5bea35da0.json
+++ b/content/node.9e094927-a767-437b-b3b7-90a5bea35da0.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "427b33a7-0a27-458b-8a02-4d6a6780a2e4"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 4da3d67ea..09e77b378 100644
--- a/content/node.9ecc8bf3-5bf6-4713-9868-c6059db4d432.json
+++ b/content/node.9ecc8bf3-5bf6-4713-9868-c6059db4d432.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d6723cf0326f529b61786870511d23ff",
             "target_type": "feeds_feed",
diff --git a/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json b/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json
index 19494f9bb..d4ef5baff 100644
--- a/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json
+++ b/content/node.9ef5d8d7-15bb-40b1-a6e4-e4cedc5fe214.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "951d2d9e9835481f997f95a29b18efdf",
             "target_type": "feeds_feed",
diff --git a/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json b/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json
index a3acc8b3b..9e6170113 100644
--- a/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json
+++ b/content/node.9f51855e-e397-420d-9ee8-e0780937cc24.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e69a1241f2245a8193f94d701b369c7c",
             "target_type": "feeds_feed",
diff --git a/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json b/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json
index a9540db7a..b5f1d5c28 100644
--- a/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json
+++ b/content/node.9f663595-3a33-4503-a86e-c15b8e3113a0.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9e2e450ab9a61ff98aa475086eedc78f",
             "target_type": "feeds_feed",
diff --git a/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json b/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json
index 611ed0167..6dca79ed6 100644
--- a/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json
+++ b/content/node.9f6e27eb-33d2-4347-a1f0-b1293eb88c40.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "71b652d23e3a8bf54a1a5586877f67ca",
             "target_type": "feeds_feed",
diff --git a/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json b/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json
index 365170d97..9138559ac 100644
--- a/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json
+++ b/content/node.9fcb0f0b-9dfd-4a51-b465-79541d63b17b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6adab48b4653c69ec584429dd988b39d",
             "target_type": "feeds_feed",
diff --git a/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json b/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json
index 0853d80f8..af246cc42 100644
--- a/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json
+++ b/content/node.9fe3fe14-044e-4dfa-bbcc-41dea612f05a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6225796a12956da7eebd27198ca6be4b",
             "target_type": "feeds_feed",
diff --git a/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json b/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json
index 29af8553a..3a8a35479 100644
--- a/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json
+++ b/content/node.a0631edf-ffac-4381-92b6-98e76e980131.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week's guest on Beyond Blocks is <a href=\"/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        ",
+            "value": "\n          <p>This week's guest on Beyond Blocks is <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>This week's guest on Beyond Blocks is <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "77a251bc42faf5a39bab63cacb3bb1bb",
             "target_type": "feeds_feed",
diff --git a/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json b/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json
index 96f32d3d0..cf736183a 100644
--- a/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json
+++ b/content/node.a1d0e52d-4cfc-4695-97f8-7f8a4c1a2938.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1f85e49caa14c4e4bd7344bf54c9f094",
             "target_type": "feeds_feed",
diff --git a/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json b/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json
index fa3a3ad70..6521fb130 100644
--- a/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json
+++ b/content/node.a1dc0ff4-ae77-4126-a499-1f39e9c08115.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/4-ed-crompton-oxfam-case-study\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/4-ed-crompton-oxfam-case-study\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/4-ed-crompton-oxfam-case-study\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8d2c1d450d37e19beaa381c50da20645",
             "target_type": "feeds_feed",
diff --git a/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json b/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json
index 45cf8c938..4c6ad27dc 100644
--- a/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json
+++ b/content/node.a24ce0c8-09dd-4ea2-8ce0-4e54a44fda19.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b438edc4ee7e47b4c5ab1fe45e9f8be5",
             "target_type": "feeds_feed",
diff --git a/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json b/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json
index c5b64b869..94ab280b2 100644
--- a/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json
+++ b/content/node.a2b118ea-d319-4808-83f6-94ad79c302f2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3c945c89786eebbad100646cd316dfae",
             "target_type": "feeds_feed",
diff --git a/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json b/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json
index eda579bb2..2ed39f095 100644
--- a/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json
+++ b/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Following last week's email on <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Following last week's email on <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Following last week's email on <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8c32951c32d678ca2fe6bac26a108dcb",
             "target_type": "feeds_feed",
diff --git a/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json b/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json
index eb54518ea..91e604fc1 100644
--- a/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json
+++ b/content/node.a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As someone <a href=\"/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=\"/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        ",
+            "value": "\n          <p>As someone <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As someone <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "38f60865df47fe3136bab0faff10ad7c",
             "target_type": "feeds_feed",
diff --git a/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json b/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json
index b204c21d3..de0c77c38 100644
--- a/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json
+++ b/content/node.a33ea357-381e-4171-9808-85c90c7602c7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Over the last few days, I've written a few emails about static websites and static site generators before I <a href=\"/presentations\/sculpin\">speak about Sculpin<\/a> at PHP Thames Valley.<\/p>\n\n<p>They are <a href=\"/daily\/2025\/03\/12\/easy\">easy to build<\/a> and deploy and <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Over the last few days, I've written a few emails about static websites and static site generators before I <a href=\"\/presentations\/sculpin\">speak about Sculpin<\/a> at PHP Thames Valley.<\/p>\n\n<p>They are <a href=\"\/daily\/2025\/03\/12\/easy\">easy to build<\/a> and deploy and <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/presentations\/sculpin\">speak about Sculpin<\/a> at PHP Thames Valley.<\/p>\n\n<p>They are <a href=\"/daily\/2025\/03\/12\/easy\">easy to build<\/a> and deploy and <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c2ab309fc48ad7634f3e37920943b3e3",
             "target_type": "feeds_feed",
diff --git a/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json b/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json
index c4edbb9ef..5b8a4331c 100644
--- a/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json
+++ b/content/node.a3fdc4e9-f528-43e7-911f-9cf5d0cce210.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "75e1224b8adc36f5f0da6bcd13fc44d5",
             "target_type": "feeds_feed",
diff --git a/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json b/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json
index 464b27fda..066101e5d 100644
--- a/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json
+++ b/content/node.a3fe3b6f-af2b-4740-9ffc-1c93f1bc868c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "144ff924864b048d704deeedcd9f2389",
             "target_type": "feeds_feed",
diff --git a/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json b/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json
index 83c8456cd..42425c769 100644
--- a/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json
+++ b/content/node.a47d5366-6212-48d7-98b0-5ccc2506052c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/podcast\/10-ryan-weaver-symfonycasts\">Twig components<\/a>, maybe - in Drupal.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/podcast\/10-ryan-weaver-symfonycasts\">Twig components<\/a>, maybe - in Drupal.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/podcast\/10-ryan-weaver-symfonycasts\">Twig components<\/a>, maybe - in Drupal.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c855be3a314644488f7547bb4b62da5c",
             "target_type": "feeds_feed",
diff --git a/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json b/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json
index 05aeade12..1adee0c1d 100644
--- a/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json
+++ b/content/node.a4efc095-f78d-45ae-854d-fc52c8afa41b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "302417948921bd4d3e2cf53132a91a19",
             "target_type": "feeds_feed",
diff --git a/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json b/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json
index 39cad184c..3b0ac034e 100644
--- a/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json
+++ b/content/node.a504768a-c5bf-4660-986d-07590f6ee816.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/call\">Book a 1-on-1 consulting call<\/a>, and I'll help you out.<\/p>\n\n        ",
+            "value": "\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=\"\/call\">Book a 1-on-1 consulting call<\/a>, and I'll help you out.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/call\">Book a 1-on-1 consulting call<\/a>, and I'll help you out.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0985c190c212466315018728f90d1b46",
             "target_type": "feeds_feed",
diff --git a/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json b/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json
index 2ced56296..94e2c3bda 100644
--- a/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json
+++ b/content/node.a520e72c-3fdf-476e-bdd7-0120e9e161ea.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Now <a href=\"/daily\/2024\/06\/23\/drupal-10-3-released\">Drupal 10.3 has been released<\/a>, and <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Now <a href=\"\/daily\/2024\/06\/23\/drupal-10-3-released\">Drupal 10.3 has been released<\/a>, and <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Now <a href=\"/daily\/2024\/06\/23\/drupal-10-3-released\">Drupal 10.3 has been released<\/a>, and <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "26e535d4da7da307150526e7fbbdabe2",
             "target_type": "feeds_feed",
diff --git a/content/node.a564439d-3102-47dc-8f4b-70b080383552.json b/content/node.a564439d-3102-47dc-8f4b-70b080383552.json
index acab005db..e094ed89d 100644
--- a/content/node.a564439d-3102-47dc-8f4b-70b080383552.json
+++ b/content/node.a564439d-3102-47dc-8f4b-70b080383552.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9d62f0394c3edfda3c7091efc05827b8",
             "target_type": "feeds_feed",
diff --git a/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json b/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json
index 66480bba5..3c046bbe2 100644
--- a/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json
+++ b/content/node.a564cfaa-2b13-4739-af74-5fde2b75b1a0.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/25-jess-archer-drush-laravel-prompts\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/25-jess-archer-drush-laravel-prompts\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/25-jess-archer-drush-laravel-prompts\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "69a24b089347581b24758ee7c7f6d739",
             "target_type": "feeds_feed",
diff --git a/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json b/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json
index 6957cfb43..52c647467 100644
--- a/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json
+++ b/content/node.a5a69bcd-a7f7-4957-ab0b-393437e4055d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1489f86d52518013ecedf7b402c2c07e",
             "target_type": "feeds_feed",
diff --git a/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json b/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json
index 473c16fe8..cdad0f30b 100644
--- a/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json
+++ b/content/node.a5edab26-6910-43c9-ba33-3f482849596a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6450282a1b4fe2e23ac91ffacb7cd5c1",
             "target_type": "feeds_feed",
diff --git a/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json b/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json
index a887c9f09..8e9b91b3b 100644
--- a/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json
+++ b/content/node.a699f864-3453-4f53-92d5-b394bfaebef7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "29be860248a883db12a44b89149e1392",
             "target_type": "feeds_feed",
diff --git a/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json b/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json
index 2148e7845..1f9a2162c 100644
--- a/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json
+++ b/content/node.a76cc0ca-e585-42b5-8ec9-369b95da3eff.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "062a427093fb899d8a3761083c1927f4",
             "target_type": "feeds_feed",
diff --git a/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json b/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json
index 8acfc7bef..743c33af8 100644
--- a/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json
+++ b/content/node.a7ee1363-3e3b-4733-b302-0c85aad15aea.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c3643649d3f3d1af84fc1912e1eefae4",
             "target_type": "feeds_feed",
diff --git a/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json b/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json
index b964888f5..9ed1c50ac 100644
--- a/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json
+++ b/content/node.a7fe5a85-3eaf-4c33-b0f5-54e67fbc09de.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b7a974fdb8e406115add89a29605c35c",
             "target_type": "feeds_feed",
diff --git a/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json b/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json
index 226e864be..5d4490018 100644
--- a/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json
+++ b/content/node.a8753236-c6ec-4eab-88c0-cf1939cf0333.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2a2b5c587a4d8d90d889a8595926719e",
             "target_type": "feeds_feed",
diff --git a/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json b/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json
index 396d1eaf1..d07b0cd95 100644
--- a/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json
+++ b/content/node.a8a1b0cc-8372-4285-a655-bdd1f77226d3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0e6a565b98631d7f71c7e8d4d68d0d26",
             "target_type": "feeds_feed",
diff --git a/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json b/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json
index c513617a5..2386a31aa 100644
--- a/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json
+++ b/content/node.a8d650da-84f6-4d81-9384-bb26228f3dcb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5b75b1651825917b5ebfb2b16179254d",
             "target_type": "feeds_feed",
diff --git a/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json b/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json
index 7b62406ba..6d2876073 100644
--- a/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json
+++ b/content/node.a8e2e580-5b20-451d-80ef-7ee19aea62ec.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As I said in <a href=\"/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        ",
+            "value": "\n          <p>As I said in <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As I said in <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6e14d379a00279e23ff3a43b65e78390",
             "target_type": "feeds_feed",
diff --git a/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json b/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json
index 4eb79efd7..bd2759d63 100644
--- a/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json
+++ b/content/node.a8f06c67-81eb-471c-9081-0648c9400e27.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e26c9b7ab7102d2ec454810073cf9ab4",
             "target_type": "feeds_feed",
diff --git a/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json b/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json
index af26d4058..7f3e7d2f8 100644
--- a/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json
+++ b/content/node.a9061df6-daf5-47f3-a217-39df555f9762.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "27ff386b427be3114468f0a592aa2363",
             "target_type": "feeds_feed",
diff --git a/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json b/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json
index c89b9e5fc..e2aa5aa70 100644
--- a/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json
+++ b/content/node.a96b6197-2490-4e22-8705-d372ee76664b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5d675721f871790eee2c4073770babdd",
             "target_type": "feeds_feed",
diff --git a/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json b/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json
index 6f7407da8..af54d9cac 100644
--- a/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json
+++ b/content/node.a97003d7-c86d-41a3-8655-ca35c6912d42.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2a53a326fece4691a606a104cf3ec76c",
             "target_type": "feeds_feed",
diff --git a/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json b/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json
index 13b82d1d9..24f7ab533 100644
--- a/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json
+++ b/content/node.a986dbd9-92fb-45fc-9769-bf75542c9b49.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5cafd2e757ac9170c91b0e8184d0ee39",
             "target_type": "feeds_feed",
diff --git a/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json b/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json
index c4a762cb1..f84138d2b 100644
--- a/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json
+++ b/content/node.a99289d5-ad45-4e3d-9d03-031569f7bf70.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "745510ed0044be6758cbc74729ab3d08",
             "target_type": "feeds_feed",
diff --git a/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json b/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json
index a9790f159..85e5636b8 100644
--- a/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json
+++ b/content/node.aa4b919c-76e4-43db-8962-2b2cacd33267.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/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        ",
+            "value": "\n          <p><a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "455ff869c592cdd12244b2264b5b2dff",
             "target_type": "feeds_feed",
diff --git a/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json b/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json
index 3bce4a17a..ddb681ef7 100644
--- a/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json
+++ b/content/node.aa72d773-765e-42bb-bf5b-f070a97f5884.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4880370cb27dce1a6abccc2c014baeae",
             "target_type": "feeds_feed",
diff --git a/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json b/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json
index 2617256f6..72c874523 100644
--- a/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json
+++ b/content/node.aa830670-f0ba-4069-98c1-c71a4e8c7d94.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1d08162ec930721f889a571b47fde853",
             "target_type": "feeds_feed",
diff --git a/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json b/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json
index a31911ecc..8ebf0b4f1 100644
--- a/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json
+++ b/content/node.aba09cf2-f67c-4056-b503-5a53399e634b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>After <a href=\"/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        ",
+            "value": "\n          <p>After <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>After <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1fdb0bb1e22238ec9d831d2b2a3af864",
             "target_type": "feeds_feed",
diff --git a/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json b/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json
index 081bb9a82..855d3fd95 100644
--- a/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json
+++ b/content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7430242f1d716198aa6fb01f727d1f9a",
             "target_type": "feeds_feed",
diff --git a/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json b/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json
index 4ff8a7dde..7d82ab2a6 100644
--- a/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json
+++ b/content/node.abd5479c-e5d2-46ba-8687-0c5d37b31bfe.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Since <a href=\"/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        ",
+            "value": "\n          <p>Since <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Since <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dec79bc6053758566e617ed059c1fc37",
             "target_type": "feeds_feed",
diff --git a/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json b/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json
index dfeabdf9c..ac3cbf7cf 100644
--- a/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json
+++ b/content/node.abf2eeeb-fcd3-4df9-9d3c-aae89244a4bf.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6a9ee2d1506c2929307940f3c4d71d0f",
             "target_type": "feeds_feed",
diff --git a/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json b/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json
index 603cfb2e7..7c6817aca 100644
--- a/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json
+++ b/content/node.ac0f7677-9ca2-4b20-a00f-0264a3aab2c6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ead1c8b01bd5cd04cfb3c0a1d516473b",
             "target_type": "feeds_feed",
diff --git a/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json b/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json
index b069504f0..c449c1cfa 100644
--- a/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json
+++ b/content/node.ac11bd02-625e-4eef-83f3-6ed1f24485ff.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3f5e1ce616fb6f602be9eb2c287dc4b3",
             "target_type": "feeds_feed",
diff --git a/content/node.ac349786-bc86-465d-9374-a277d15a892c.json b/content/node.ac349786-bc86-465d-9374-a277d15a892c.json
index fcf6e1246..ac21dc2cd 100644
--- a/content/node.ac349786-bc86-465d-9374-a277d15a892c.json
+++ b/content/node.ac349786-bc86-465d-9374-a277d15a892c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f0773074647747f68f82e4db2924323f",
             "target_type": "feeds_feed",
diff --git a/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json b/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json
index c60fbb8ef..d0c19b14e 100644
--- a/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json
+++ b/content/node.ac9fe71d-cde5-4954-80da-a94e2ff6ce7a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "01e0bd9d4c8ad64c6ea1a3f3563d37a3",
             "target_type": "feeds_feed",
diff --git a/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json b/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json
index 069a1e2ce..dece3ed38 100644
--- a/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json
+++ b/content/node.acdd68c3-34bb-4a9b-9feb-1c9580852eef.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b418347cf60efb3abda4a93b884ed151",
             "target_type": "feeds_feed",
diff --git a/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json b/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json
index 995e4053c..25c490f17 100644
--- a/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json
+++ b/content/node.ad9f3eb0-45be-4ec0-b4bb-5b61d4a96d6d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d8c18f8667771c2497ae722e5849f6fc",
             "target_type": "feeds_feed",
diff --git a/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json b/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json
index ee7555cd3..d13152f7b 100644
--- a/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json
+++ b/content/node.af1271f1-d7b4-446b-8fb0-1d94eee5846f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "11107beced548217d0455b4197564141",
             "target_type": "feeds_feed",
diff --git a/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json b/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json
index 4f8fdabe1..2205ea2a8 100644
--- a/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json
+++ b/content/node.af570204-edaa-41d8-af54-5136ec8f0954.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "247a1b12455fa21f13c5bcd13b69f5c7",
             "target_type": "feeds_feed",
diff --git a/content/node.afe43360-ecca-472a-b501-062f898650a5.json b/content/node.afe43360-ecca-472a-b501-062f898650a5.json
index ffec4b46d..0bd03a10a 100644
--- a/content/node.afe43360-ecca-472a-b501-062f898650a5.json
+++ b/content/node.afe43360-ecca-472a-b501-062f898650a5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6fbd09cf55994352dfe3e9a6fae9be71",
             "target_type": "feeds_feed",
diff --git a/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json b/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json
index f7b01c599..448e00991 100644
--- a/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json
+++ b/content/node.b09dbe1e-6719-4dab-929f-acd50aa9cfc7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/daily\/2024\/10\/20\/test-then-refactor\">refactored or changed in the future<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/daily\/2024\/10\/20\/test-then-refactor\">refactored or changed in the future<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/daily\/2024\/10\/20\/test-then-refactor\">refactored or changed in the future<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4b75b46173ea0fe84b24f6e4c3cfcdb5",
             "target_type": "feeds_feed",
diff --git a/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json b/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json
index 0af3e5df1..199c85ef8 100644
--- a/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json
+++ b/content/node.b0daabcd-f51d-4208-9742-4a4512e2bbb5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "81b20fc691ca055821b1bd306f13d303",
             "target_type": "feeds_feed",
diff --git a/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json b/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json
index 5681d1f50..bbcb15cc4 100644
--- a/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json
+++ b/content/node.b16f4c7f-2876-4165-8c38-a7ef0b9cbb13.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "62c9b3575536aedbe5b6aa6eec541fe7",
             "target_type": "feeds_feed",
diff --git a/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json b/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json
index 4b255cab0..3464208f1 100644
--- a/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json
+++ b/content/node.b1a76740-f08d-4af6-a37a-a1bdf73fef5c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7b51105f14f48cc301c0e7b3db261bab",
             "target_type": "feeds_feed",
diff --git a/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json b/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json
index 707ad7840..5855312ff 100644
--- a/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json
+++ b/content/node.b2160fad-74d6-425b-9c76-d3b662807dbf.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d0230fb0c7af7c9de0491edbea342ca1",
             "target_type": "feeds_feed",
diff --git a/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json b/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json
index c6af59a05..f68b5bdce 100644
--- a/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json
+++ b/content/node.b2e7fd1a-40f8-40fc-9304-54385e3dcb6d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ae03e717e78fc1762f27dc32a8918c04",
             "target_type": "feeds_feed",
diff --git a/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json b/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json
index 97318fcd8..04fc90ced 100644
--- a/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json
+++ b/content/node.b2f30b62-d067-4e73-9fab-db655e9409d6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "568c4c9322b2426b006acfbbde0b6261",
             "target_type": "feeds_feed",
diff --git a/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json b/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json
index ec137a4cf..a2d425a15 100644
--- a/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json
+++ b/content/node.b34882e4-0e63-4fb7-9e5c-0b6a16eb5c1c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2cbe50d2773f58c7252205ff19b112c5",
             "target_type": "feeds_feed",
diff --git a/content/node.b38b290a-1ce1-481d-987b-9683245740da.json b/content/node.b38b290a-1ce1-481d-987b-9683245740da.json
index 105aa661d..9455da58e 100644
--- a/content/node.b38b290a-1ce1-481d-987b-9683245740da.json
+++ b/content/node.b38b290a-1ce1-481d-987b-9683245740da.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/22-dave-liddament\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/22-dave-liddament\">Listen to the episode now<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/22-dave-liddament\">Listen to the episode now<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "499b1aaa68d51e78b79ff4e1e163550a",
             "target_type": "feeds_feed",
diff --git a/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json b/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json
index 90490d1ab..fbed512c6 100644
--- a/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json
+++ b/content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9553ccae6f298ace5c5f247750bea8a2",
             "target_type": "feeds_feed",
diff --git a/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json b/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json
index 434da2d8c..8e05657ab 100644
--- a/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json
+++ b/content/node.b3d2cc06-7cbf-476e-9dc7-fa13ed17363f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>If you're trying to <a href=\"/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=\"/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=\"/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        ",
+            "value": "\n          <p>If you're trying to <a href=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>If you're trying to <a href=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7c09b32f259965b0c8e9be189b768902",
             "target_type": "feeds_feed",
diff --git a/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json b/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json
index 59fcebdc5..a29a3d461 100644
--- a/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json
+++ b/content/node.b43ce1ab-0d83-463f-9421-d20aaacdd833.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "482bccba295c563b929e0709bade80e5",
             "target_type": "feeds_feed",
diff --git a/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json b/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json
index 121e9ac16..6f54c6b7b 100644
--- a/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json
+++ b/content/node.b43e4c29-4bcf-4cb9-9001-2a9f9f8ec993.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/drupal-upgrade\">Drupal upgrade roadmap<\/a> and get directions how to upgrade to Drupal 10.<\/p>\n\n        ",
+            "value": "\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=\"\/drupal-upgrade\">Drupal upgrade roadmap<\/a> and get directions how to upgrade to Drupal 10.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/drupal-upgrade\">Drupal upgrade roadmap<\/a> and get directions how to upgrade to Drupal 10.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6e4460ba8f2e7ef1df4c709299bfb0a6",
             "target_type": "feeds_feed",
diff --git a/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json b/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json
index 07e0422d2..f852ce22d 100644
--- a/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json
+++ b/content/node.b475d325-7c60-4115-b465-f1d691ab75b0.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "795dc7516651db80b6d0231ec717952b",
             "target_type": "feeds_feed",
diff --git a/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json b/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json
index cff4338ec..a295f9c45 100644
--- a/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json
+++ b/content/node.b48769b5-0c48-4bee-a008-6a760db421de.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Whilst discussing <a href=\"/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        ",
+            "value": "\n          <p>Whilst discussing <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Whilst discussing <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "431bef314ddeb1827fe0a9654609412d",
             "target_type": "feeds_feed",
diff --git a/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json b/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json
index 650b67f5f..0ac34f22f 100644
--- a/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json
+++ b/content/node.b4a61b67-5a6e-4b9f-87c9-95cf1b38df5e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ebb678e6bfb989f0b14c1f494c92a1af",
             "target_type": "feeds_feed",
diff --git a/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json b/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json
index bd1d95287..13430fbaf 100644
--- a/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json
+++ b/content/node.b51a5709-0942-4244-b857-16e5b43ff2fb.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Back in <a href=\"/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        ",
+            "value": "\n          <p>Back in <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Back in <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f3ba6520289a5b3dda2c70904d92968f",
             "target_type": "feeds_feed",
diff --git a/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json b/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json
index ff51b70c6..73ce9110f 100644
--- a/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json
+++ b/content/node.b51b7b96-fe84-43ed-9181-3c590a4015ef.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d262aceb56149a2882d4619968502736",
             "target_type": "feeds_feed",
diff --git a/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json b/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json
index 62dfe9124..06b7aca60 100644
--- a/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json
+++ b/content/node.b526b7c8-0251-4f67-a424-e71f8a6e8b8a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "247980cbd242cc2ccdbfcc15a30390c8",
             "target_type": "feeds_feed",
diff --git a/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json b/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json
index fd12ef7c7..3c4d95791 100644
--- a/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json
+++ b/content/node.b54ead56-01d3-442f-9689-c422f5be5e27.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8f7fe4481187e913f2e5fc1042f5b712",
             "target_type": "feeds_feed",
diff --git a/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json b/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json
index b4ce43a17..87c0af949 100644
--- a/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json
+++ b/content/node.b5b7cf41-fa32-4c63-a182-9b048c290f05.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Something I mentioned during my <a href=\"/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        ",
+            "value": "\n          <p>Something I mentioned during my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Something I mentioned during my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "46a1df14b13ff412272180103b18543b",
             "target_type": "feeds_feed",
diff --git a/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json b/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json
index ad1a36422..993e80225 100644
--- a/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json
+++ b/content/node.b5e6b353-30b6-42d7-a8f1-ed202131a6f6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2024\/08\/07\/people-read-more-code-than-they-write\">people read more code than they write<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/daily\/2024\/08\/07\/people-read-more-code-than-they-write\">people read more code than they write<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2024\/08\/07\/people-read-more-code-than-they-write\">people read more code than they write<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1a2697516ded656f685248cde9ddc09e",
             "target_type": "feeds_feed",
diff --git a/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json b/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json
index a2998b854..880616be4 100644
--- a/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json
+++ b/content/node.b61104ef-e514-4518-bec8-a10b1dcbaa4a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2024\/11\/17\/override-node-options-used-by-localgov-drupal\">LocalGov Drupal<\/a>.<\/p>\n\n<p>Whilst <a href=\"/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        ",
+            "value": "\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=\"\/daily\/2024\/11\/17\/override-node-options-used-by-localgov-drupal\">LocalGov Drupal<\/a>.<\/p>\n\n<p>Whilst <a href=\"\/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        ",
             "format": "full_html",
-            "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=\"/daily\/2024\/11\/17\/override-node-options-used-by-localgov-drupal\">LocalGov Drupal<\/a>.<\/p>\n\n<p>Whilst <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b386cfa88fcc78b52277d0eb4bc4f76d",
             "target_type": "feeds_feed",
diff --git a/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json b/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json
index 10b24fb38..67f6a075b 100644
--- a/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json
+++ b/content/node.b66e30f0-28a1-459d-a0d2-193d1772ece1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>The talk that I gave last week at PHP Stoke was <a href=\"/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        ",
+            "value": "\n          <p>The talk that I gave last week at PHP Stoke was <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>The talk that I gave last week at PHP Stoke was <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "05ba98327bf894b02b9686a1f5c9b14f",
             "target_type": "feeds_feed",
diff --git a/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json b/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json
index a2bd61b31..e644ef2ec 100644
--- a/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json
+++ b/content/node.b68d2c2d-2d78-43c5-b97c-3e57f0308b13.json
@@ -82,9 +82,9 @@
     ],
     "body": [
         {
-            "value": "<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=\"/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>",
+            "value": "<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=\"\/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>",
             "format": "basic_html",
-            "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=\"/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>",
+            "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": ""
         }
     ],
diff --git a/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json b/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json
index b746e7fc7..b4b4748a4 100644
--- a/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json
+++ b/content/node.b6fd9a07-2647-4b83-9ca7-2d3a5668865c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bc73a47b4554b36af87f142a939076a9",
             "target_type": "feeds_feed",
diff --git a/content/node.b71f8b90-7636-4e13-b31a-e7ba42eb94f7.json b/content/node.b71f8b90-7636-4e13-b31a-e7ba42eb94f7.json
index 25e1aa5a9..be53111b5 100644
--- a/content/node.b71f8b90-7636-4e13-b31a-e7ba42eb94f7.json
+++ b/content/node.b71f8b90-7636-4e13-b31a-e7ba42eb94f7.json
@@ -76,7 +76,7 @@
     ],
     "path": [
         {
-            "alias": "",
+            "alias": null,
             "pid": null,
             "langcode": "en"
         }
diff --git a/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json b/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json
index 3814293de..34db12fb1 100644
--- a/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json
+++ b/content/node.b8243d12-2068-42e4-bb31-6f0b5add5e5a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f14adb13d3ae7905d6bc55853f2ce7ae",
             "target_type": "feeds_feed",
diff --git a/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json b/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json
index 26e11645c..d6d20c53c 100644
--- a/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json
+++ b/content/node.b83d4ea0-973a-4164-be6f-df5fff2b9b0e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b535eb52679173284d48e852e1dd8e86",
             "target_type": "feeds_feed",
diff --git a/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json b/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json
index ef02872ba..8c480a4c3 100644
--- a/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json
+++ b/content/node.b86c14c0-4dfe-485e-bc8a-d18215ac85a7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Now <a href=\"/daily\/2025\/02\/28\/preprocessors\">CSS supports variables<\/a> (aka custom properties) and <a href=\"/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=\"/daily\/2024\/05\/26\/is-it-time-to-stop-writing-sass\">instead of a preprocessor like Sass<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>Now <a href=\"\/daily\/2025\/02\/28\/preprocessors\">CSS supports variables<\/a> (aka custom properties) and <a href=\"\/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=\"\/daily\/2024\/05\/26\/is-it-time-to-stop-writing-sass\">instead of a preprocessor like Sass<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>Now <a href=\"/daily\/2025\/02\/28\/preprocessors\">CSS supports variables<\/a> (aka custom properties) and <a href=\"/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=\"/daily\/2024\/05\/26\/is-it-time-to-stop-writing-sass\">instead of a preprocessor like Sass<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5a6518d8c14841bf4d760dcc8afd3399",
             "target_type": "feeds_feed",
diff --git a/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json b/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json
index 3f3e043d8..b59ce7be3 100644
--- a/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json
+++ b/content/node.b892433b-6318-4716-9bb8-fc13e6a55fbb.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In my <a href=\"/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        ",
+            "value": "\n          <p>In my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6dfe7f8c27fa0a23fdab4a3d3adf0676",
             "target_type": "feeds_feed",
diff --git a/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json b/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json
index a0ac3c31b..5c5dc747b 100644
--- a/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json
+++ b/content/node.b89f02aa-5ed5-4e1f-a8b0-c5d98e6ee439.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/call\">upgrade consultation call<\/a> with me or purchase an <a href=\"/drupal7\">upgrade roadmap for your project<\/a> and I'll get you unstuck.<\/p>\n\n        ",
+            "value": "\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=\"\/call\">upgrade consultation call<\/a> with me or purchase an <a href=\"\/drupal7\">upgrade roadmap for your project<\/a> and I'll get you unstuck.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/call\">upgrade consultation call<\/a> with me or purchase an <a href=\"/drupal7\">upgrade roadmap for your project<\/a> and I'll get you unstuck.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "49f172d2f1fab5d643988eb42ef695ee",
             "target_type": "feeds_feed",
diff --git a/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json b/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json
index de01e38b9..13dfef537 100644
--- a/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json
+++ b/content/node.b9297a41-9a9a-46e4-a7a9-4281ff5c88e7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4f6b35edac4d89b8fb13a0be63f410ac",
             "target_type": "feeds_feed",
diff --git a/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json b/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json
index dac358d88..54af6a02b 100644
--- a/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json
+++ b/content/node.b92a815e-5d21-4adc-8a1f-378ba6be23c8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fb6dc9480f15426adce25a251aaa7947",
             "target_type": "feeds_feed",
diff --git a/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json b/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json
index 82eeb4afe..b08668ac9 100644
--- a/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json
+++ b/content/node.ba009e81-1bbd-44dd-928f-21681d2dc1ff.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "18539948fc2de002752220934a543e9c",
             "target_type": "feeds_feed",
diff --git a/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json b/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json
index a87b8a35c..fcd873c76 100644
--- a/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json
+++ b/content/node.ba4ccfb6-f00d-4fb2-8519-aa43356218f6.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Over a year ago, I posted that I was <a href=\"/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        ",
+            "value": "\n          <p>Over a year ago, I posted that I was <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Over a year ago, I posted that I was <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fd61209df55f98bd0ca56ce044f36294",
             "target_type": "feeds_feed",
diff --git a/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json b/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json
index a7ca3b0eb..ab632aff4 100644
--- a/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json
+++ b/content/node.ba897799-0b8a-4c3d-b3f1-f3a0e4e2b25a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f6fe2ba6a57a493e184303e55e02f271",
             "target_type": "feeds_feed",
diff --git a/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json b/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json
index 5e77899e4..176368c56 100644
--- a/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json
+++ b/content/node.baa04acc-64aa-435e-b012-1af94d0b0cf1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "74468b0353a980f541a60ac6ae7d8670",
             "target_type": "feeds_feed",
diff --git a/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json b/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json
index 735527d3e..89dfb25e1 100644
--- a/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json
+++ b/content/node.baa99cce-a9bf-442d-8c24-ea0eb92fbb25.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Something I've said when <a href=\"/presentations\/taking-flight-with-tailwind-css.md\">speaking about Tailwind CSS<\/a> and also during <a href=\"/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        ",
+            "value": "\n          <p>Something I've said when <a href=\"\/presentations\/taking-flight-with-tailwind-css.md\">speaking about Tailwind CSS<\/a> and also during <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Something I've said when <a href=\"/presentations\/taking-flight-with-tailwind-css.md\">speaking about Tailwind CSS<\/a> and also during <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5b4b4815f291bc6b2a7f37552c3d1102",
             "target_type": "feeds_feed",
diff --git a/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json b/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json
index 39da711dc..95a5641e5 100644
--- a/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json
+++ b/content/node.bbb0f7dc-a5f9-4f11-8a33-f8b234c0cc89.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f8e98c50f5284056cf311cfa9f72e1b7",
             "target_type": "feeds_feed",
diff --git a/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json b/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json
index 5957deacb..1b4a22bcd 100644
--- a/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json
+++ b/content/node.bbbe114e-124b-40cb-a884-9edd94353bba.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9d6904a98395f98154e7daf42e53b658",
             "target_type": "feeds_feed",
diff --git a/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json b/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json
index 630a25d56..4883bf539 100644
--- a/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json
+++ b/content/node.bc4593fb-caa7-4abe-90eb-fcc0d6c85ad6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "21005af8fae35fe0bce3fc916d1c0bc8",
             "target_type": "feeds_feed",
diff --git a/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json b/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json
index 769e4b67f..e7caa29a8 100644
--- a/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json
+++ b/content/node.bc747939-87ef-409b-bb1e-48c94863579c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ca4c680e0cbb4095fc2e8350b85a012f",
             "target_type": "feeds_feed",
diff --git a/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json b/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json
index 68d2ff90f..9870285bc 100644
--- a/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json
+++ b/content/node.bcfa962f-c9ea-4346-b10c-4317932097c7.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ac98176315a9e1cccd237bcf0260a3a5",
             "target_type": "feeds_feed",
diff --git a/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json b/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json
index 8fb1c24c9..66244a35c 100644
--- a/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json
+++ b/content/node.bd0ab1a7-853f-44dd-a29f-967b3808e132.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f2fb7d74b91a13b51ff0fd8910e6c614",
             "target_type": "feeds_feed",
diff --git a/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json b/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json
index c3c152b0b..c16394aa1 100644
--- a/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json
+++ b/content/node.bd892fac-0009-4886-9ced-5fbffab2d540.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5e83d222e9f351c117ad6d2c908c0af2",
             "target_type": "feeds_feed",
diff --git a/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json b/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json
index d9df0b886..0aaf995ce 100644
--- a/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json
+++ b/content/node.bdb5298b-feed-4876-9d61-de877c6534da.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a7a87d14263d9b3f3b9db35811001884",
             "target_type": "feeds_feed",
diff --git a/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json b/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json
index e82aa731a..704a8c857 100644
--- a/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json
+++ b/content/node.be0c00dd-5149-4fe2-a17d-03564255330c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "41c6635bf0b850f244bdf48de16fe27a",
             "target_type": "feeds_feed",
diff --git a/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json b/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json
index 13c5e3312..e6d2d59c0 100644
--- a/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json
+++ b/content/node.be1546de-8ebe-4d4c-8493-92fe5dd83fdc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6708362766a6d90506b1782d1cc56c17",
             "target_type": "feeds_feed",
diff --git a/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json b/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json
index 9a2606499..7b88ae50c 100644
--- a/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json
+++ b/content/node.be331d8c-cc1c-404d-9764-7304a5309c80.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In this week's episode of the <a href=\"/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=\"/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        ",
+            "value": "\n          <p>In this week's episode of the <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In this week's episode of the <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "04fbbf59f12e449ba66ad5ff6d0fb063",
             "target_type": "feeds_feed",
diff --git a/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json b/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json
index 56a1f8962..94a36ceae 100644
--- a/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json
+++ b/content/node.befd9d9c-edd5-483e-b378-b3867451769d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In <a href=\"/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        ",
+            "value": "\n          <p>In <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5805ba311b8e79cc68de1b251dd3b2ff",
             "target_type": "feeds_feed",
diff --git a/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json b/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json
index 124140a1d..ccdc7456d 100644
--- a/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json
+++ b/content/node.bf04ca43-aaa4-4877-a1df-80042934a312.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>After sending <a href=\"/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        ",
+            "value": "\n          <p>After sending <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>After sending <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "45269d5f607bea54f9ddd23fd5c84611",
             "target_type": "feeds_feed",
diff --git a/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json b/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json
index e1dabd002..c7dee1a93 100644
--- a/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json
+++ b/content/node.bfd168f9-71fe-41f9-a4f6-60ce897917a7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7b3d0e69e978e096200c927b708f8adf",
             "target_type": "feeds_feed",
diff --git a/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json b/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json
index 97a4c2c13..ed16489dc 100644
--- a/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json
+++ b/content/node.c01c5ea3-cf81-43b9-981e-f51ee24cb8e5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "44047cd2087198d6d3e858acb4075cc2",
             "target_type": "feeds_feed",
diff --git a/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json b/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json
index 9feb1f31c..aaed9c62d 100644
--- a/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json
+++ b/content/node.c027d77e-97c4-43eb-99cd-672dedcf8f14.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I built my <a href=\"/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        ",
+            "value": "\n          <p>I built my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I built my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a700ecf2a857dac7a210989faa80eb4d",
             "target_type": "feeds_feed",
diff --git a/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json b/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json
index 38d83a343..8c9a2a91c 100644
--- a/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json
+++ b/content/node.c0d7b8ea-8a29-4d83-937d-52d951ce250b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2bfadaccd342e33a28413aca4bbe6414",
             "target_type": "feeds_feed",
diff --git a/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json b/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json
index 05a8e6f1c..cca43def6 100644
--- a/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json
+++ b/content/node.c0e34d5c-831b-4f01-aab9-b95fae7e0bb1.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "09e70a063c30cc59ead229e026e00f13",
             "target_type": "feeds_feed",
diff --git a/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json b/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json
index 155bd9fb5..14c560639 100644
--- a/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json
+++ b/content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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=\"/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        ",
+            "value": "\n          <p>As well as <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "abfbb6e640ea537c7cb537b44b7994ab",
             "target_type": "feeds_feed",
diff --git a/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json b/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json
index 318797c70..f1d0ebc76 100644
--- a/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json
+++ b/content/node.c15ee1ad-adb1-4017-a5ef-a56071197a38.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "75435477d7a227a083c9be5742e6fd8e",
             "target_type": "feeds_feed",
diff --git a/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json b/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json
index 0cd90642d..de6e769dd 100644
--- a/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json
+++ b/content/node.c18eb41a-8a26-4a5a-bf17-e1417cebb0dc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e6ccad714f421e19ca6bf59a5f2c224c",
             "target_type": "feeds_feed",
diff --git a/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json b/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json
index 3e9c4e9e3..e68d43bdb 100644
--- a/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json
+++ b/content/node.c1bc355c-4dfb-4ea0-a98e-9801871107f2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e15b57a5fdb50483f2e7b2a23d0fbf8c",
             "target_type": "feeds_feed",
diff --git a/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json b/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json
index 0ab604ec1..63777d5f2 100644
--- a/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json
+++ b/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In January, I wrote about <a href=\"/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        ",
+            "value": "\n          <p>In January, I wrote about <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In January, I wrote about <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dce9edad7a35465af5401069bf3d75cd",
             "target_type": "feeds_feed",
diff --git a/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json b/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json
index d3eefc24a..0170e8196 100644
--- a/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json
+++ b/content/node.c2315804-efa4-4b5e-ae67-41457d8cd8c8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2961539db053ecb851f7ff74172acc9b",
             "target_type": "feeds_feed",
diff --git a/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json b/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json
index 77aa870c3..268989508 100644
--- a/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json
+++ b/content/node.c28c0731-5f76-4b55-8326-a584e385e8cb.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In my <a href=\"/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        ",
+            "value": "\n          <p>In my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ee421350e08042bf1dc38655f1c7358b",
             "target_type": "feeds_feed",
diff --git a/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json b/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json
index e859e7db7..13ef2daaa 100644
--- a/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json
+++ b/content/node.c2b27288-d156-4d16-ac94-cf431548f34a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a0bc3463255d3adc14c37179d7838fec",
             "target_type": "feeds_feed",
diff --git a/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json b/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json
index 3a57e51c0..c18dc3b55 100644
--- a/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json
+++ b/content/node.c2e14331-ad0a-4ec6-9d26-ffa2019e61f6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8e4c0c829c59ed32febbb0b3c5be9acf",
             "target_type": "feeds_feed",
diff --git a/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json b/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json
index 8874bc48b..301132468 100644
--- a/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json
+++ b/content/node.c2ed3f01-0761-4b2a-a845-fccd30c84d57.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "839ad892ec2adbc5d9a97cf4d798231f",
             "target_type": "feeds_feed",
diff --git a/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json b/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json
index 7b7e21c3e..88535316a 100644
--- a/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json
+++ b/content/node.c373d98a-0558-4f14-a58f-e253e43c3435.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>The answer to \"<a href=\"/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=\"/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>The answer to \"<a href=\"\/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=\"\/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>The answer to \"<a href=\"/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=\"/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "74278f8a549e0bdb4602dfed3099d077",
             "target_type": "feeds_feed",
diff --git a/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json b/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json
index 31c26c4de..6759ea359 100644
--- a/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json
+++ b/content/node.c4bece9a-e11b-43a8-861a-2a64a12e5a91.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "43c6e609caa1eda4abbb11aab70e8141",
             "target_type": "feeds_feed",
diff --git a/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json b/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json
index d73be72bb..58c102a98 100644
--- a/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json
+++ b/content/node.c58749a0-bec2-415b-aa25-33eca5cce8b7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2362356e8d2f3a9cef83ebd18dc9bf11",
             "target_type": "feeds_feed",
diff --git a/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json b/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json
index ee3dd0d73..f1bdce5d5 100644
--- a/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json
+++ b/content/node.c61f3ce9-54c7-4b07-9e44-7affd7d16e5b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1d0346a7d6dd5cac3b65b148563e58b2",
             "target_type": "feeds_feed",
diff --git a/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json b/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json
index 56775b7b6..ce36d2c6d 100644
--- a/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json
+++ b/content/node.c62fbabe-1ac1-403a-bb7e-1f0559dd7442.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f37cca5f2692bfc4e92b042590c4cab1",
             "target_type": "feeds_feed",
diff --git a/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json b/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json
index a6f62018c..7b6ceef71 100644
--- a/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json
+++ b/content/node.c68956b5-95b2-48f4-873e-aabc074a5497.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "805afbbb39c5208d4da98592167360a8",
             "target_type": "feeds_feed",
diff --git a/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json b/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json
index 80c2ecb4b..2c72a7831 100644
--- a/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json
+++ b/content/node.c6bc2e2d-1817-4856-9e5d-5a5136963485.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ec096cce9917022d9b2ba1ebcdde5a0e",
             "target_type": "feeds_feed",
diff --git a/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json b/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json
index 58cbf3719..553b3ec5c 100644
--- a/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json
+++ b/content/node.c72430aa-0c6d-4cf8-8a43-812d245ea73d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A few days ago, I mentioned <a href=\"/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        ",
+            "value": "\n          <p>A few days ago, I mentioned <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A few days ago, I mentioned <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "18f69e8494cd5de71961a506175181f4",
             "target_type": "feeds_feed",
diff --git a/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json b/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json
index 8b3867e7c..b94f84008 100644
--- a/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json
+++ b/content/node.c7423f08-eb5a-4602-b85f-9b4691efe3ab.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "863a73768ac75bc3880484ce14aa5d49",
             "target_type": "feeds_feed",
diff --git a/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json b/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json
index f4743a3d8..ae080f6d2 100644
--- a/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json
+++ b/content/node.c765b1bf-87ee-4324-843a-8ca578ef2f69.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8c51b1ac3a2223e3279ac9e4bcc51f58",
             "target_type": "feeds_feed",
diff --git a/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json b/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json
index 73ffb65e4..298af4987 100644
--- a/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json
+++ b/content/node.c798ba8d-2b67-459b-994d-97e286d33ca9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d03c32cba85beb76c8e0e111e3ae1d52",
             "target_type": "feeds_feed",
diff --git a/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json b/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json
index 514c80241..8ff272c7d 100644
--- a/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json
+++ b/content/node.c7ad84af-f5c8-4ff8-92cd-873528acc623.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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=\"/daily\/2022\/08\/12\/git-worktrees-docker-compose\">git worktrees are for you<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/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=\"\/daily\/2022\/08\/12\/git-worktrees-docker-compose\">git worktrees are for you<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/daily\/2022\/08\/12\/git-worktrees-docker-compose\">git worktrees are for you<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1b329f24d5fcdb46e236911745ece2dc",
             "target_type": "feeds_feed",
diff --git a/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json b/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json
index 75952b175..272ef8486 100644
--- a/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json
+++ b/content/node.c7dd2a5b-3a7c-4ab0-8dc2-81f2d2cb8af1.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, <a href=\"/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=\"/presentations\/taking-flight-with-tailwind-css\">Tailwind CSS<\/a> and <a href=\"/\/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        ",
+            "value": "\n          <p>Yesterday, <a href=\"\/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=\"\/presentations\/taking-flight-with-tailwind-css\">Tailwind CSS<\/a> and <a href=\"\/\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, <a href=\"/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=\"/presentations\/taking-flight-with-tailwind-css\">Tailwind CSS<\/a> and <a href=\"/\/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "61a5f029b181771294db67f4654ec590",
             "target_type": "feeds_feed",
diff --git a/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json b/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json
index 034250aa7..c0d863f32 100644
--- a/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json
+++ b/content/node.c841583c-4e19-4eb2-898a-d7e61859daad.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e52d296563e9560ea0b8d1060cc77506",
             "target_type": "feeds_feed",
diff --git a/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json b/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json
index 7dc28a184..0e5344de2 100644
--- a/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json
+++ b/content/node.c87318b5-eb27-4eba-a3d4-a5328f362c9d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In yesterday's email, I wondered <a href=\"/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        ",
+            "value": "\n          <p>In yesterday's email, I wondered <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In yesterday's email, I wondered <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e58c1b76ed53979d349c848dc1c6d475",
             "target_type": "feeds_feed",
diff --git a/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json b/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json
index 9b52dd43b..b8e76639e 100644
--- a/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json
+++ b/content/node.c8d78160-4a98-441c-a707-c1fde53f9044.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "56cd66100b039fcf69f6ebcd06176a9b",
             "target_type": "feeds_feed",
diff --git a/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json b/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json
index 361a7fb28..2b75486d6 100644
--- a/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json
+++ b/content/node.c8e5ab46-3320-4a41-b322-11b08d92aeaa.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9ab0b186e8be83ec48f221f864037954",
             "target_type": "feeds_feed",
diff --git a/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json b/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json
index 3035f5213..661473b2b 100644
--- a/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json
+++ b/content/node.c8fd5532-9338-4ea0-933f-798ce5782931.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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\u00a0puzzle 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=\"/daily\/2023\/11\/09\/readme-driven-development\">capture these decisions in a README file<\/a> <a href=\"/daily\/2024\/09\/04\/diagram-driven-development\">or diagram<\/a>, that's ideal.<\/p>\n\n        ",
+            "value": "\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\u00a0puzzle 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=\"\/daily\/2023\/11\/09\/readme-driven-development\">capture these decisions in a README file<\/a> <a href=\"\/daily\/2024\/09\/04\/diagram-driven-development\">or diagram<\/a>, that's ideal.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2023\/11\/09\/readme-driven-development\">capture these decisions in a README file<\/a> <a href=\"/daily\/2024\/09\/04\/diagram-driven-development\">or diagram<\/a>, that's ideal.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9c34aa974d9627eacb1aee7476f85467",
             "target_type": "feeds_feed",
diff --git a/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json b/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json
index 78bb5c480..4abee67db 100644
--- a/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json
+++ b/content/node.c8ff4c27-c938-4c24-ac36-e4af2fb2457b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cd5a2930ef6ca83b078b4effc46de01f",
             "target_type": "feeds_feed",
diff --git a/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json b/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json
index ad7aca1fc..a125ad8ee 100644
--- a/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json
+++ b/content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>The other day, <a href=\"/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        ",
+            "value": "\n          <p>The other day, <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>The other day, <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "345a3eeaf689f5cb4490ec578563ae9f",
             "target_type": "feeds_feed",
diff --git a/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json b/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json
index 0be72520c..c9bd1427a 100644
--- a/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json
+++ b/content/node.c9c11eda-6318-4e7c-b108-a01feea60e45.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>The video of the most recent version of my <a href=\"/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        ",
+            "value": "\n          <p>The video of the most recent version of my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>The video of the most recent version of my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a8eb871985cb8c2f459c3aa07acaacb5",
             "target_type": "feeds_feed",
diff --git a/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json b/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json
index 936c02f71..da6bc0a7f 100644
--- a/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json
+++ b/content/node.c9c4743b-a803-47b3-8405-f6aeb34a279b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1579ff874773390b1129bfc1dc1f1c57",
             "target_type": "feeds_feed",
diff --git a/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json b/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json
index f73ded0b5..e4e988948 100644
--- a/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json
+++ b/content/node.c9ccd7f8-4727-49fa-9481-4507e7986fd9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, I wrote how to create <a href=\"/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=\"/blog\/using-laravel-collections-drupal\">I've written blog posts<\/a> and <a href=\"/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        ",
+            "value": "\n          <p>Yesterday, I wrote how to create <a href=\"\/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=\"\/blog\/using-laravel-collections-drupal\">I've written blog posts<\/a> and <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, I wrote how to create <a href=\"/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=\"/blog\/using-laravel-collections-drupal\">I've written blog posts<\/a> and <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9ed6c1d39227210765b7041449aae5f5",
             "target_type": "feeds_feed",
diff --git a/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json b/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json
index 9dff320c7..6e6beff20 100644
--- a/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json
+++ b/content/node.ca145f06-f0f5-4538-978f-0af3f1c32d73.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week, I'm starting my own podcast - <a href=\"/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        ",
+            "value": "\n          <p>This week, I'm starting my own podcast - <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>This week, I'm starting my own podcast - <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d8d0de266333d29f23f7994cb8acb4d0",
             "target_type": "feeds_feed",
diff --git a/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json b/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json
index e831de98f..95f041a2d 100644
--- a/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json
+++ b/content/node.ca4340a2-6371-457a-8e95-885adbcdc256.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "400db55c8a1b2bec187c987a57a19658",
             "target_type": "feeds_feed",
diff --git a/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json b/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json
index bb8f50085..808f48a99 100644
--- a/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json
+++ b/content/node.ca7093b6-288d-4326-b755-cc96e0c262dc.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "49162664e5c715f580f3bfe1499494f8",
             "target_type": "feeds_feed",
diff --git a/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json b/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json
index 28c5b1251..85b0e397c 100644
--- a/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json
+++ b/content/node.cb1ef187-ec66-47a4-9d18-a2b4099d16ba.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ff423bb2508f4873bd03521220ecb749",
             "target_type": "feeds_feed",
diff --git a/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json b/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json
index a12fb4fc1..b366697f7 100644
--- a/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json
+++ b/content/node.cb4c03ee-f173-483a-b3b6-f9de065a7d04.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "10d16646b00062b7c85b51e5adc54370",
             "target_type": "feeds_feed",
diff --git a/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json b/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json
index affbe48ee..68c59bbe8 100644
--- a/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json
+++ b/content/node.cb59660e-e499-4b18-a779-46fed92d0879.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b2429e68b50db27a25afc2c94ecfd957",
             "target_type": "feeds_feed",
diff --git a/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json b/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json
index af79e9088..b549e06d6 100644
--- a/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json
+++ b/content/node.cb9b7a67-738f-43c9-bac9-be9b72ac57c5.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "83b11c57e9b106b547608123735755d3",
             "target_type": "feeds_feed",
diff --git a/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json b/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json
index 9e1888ad8..03b6aded8 100644
--- a/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json
+++ b/content/node.cbc726a3-93f3-41e2-ba6b-9c591096eda9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a73cc355613964dd5fbafe455fb3ed71",
             "target_type": "feeds_feed",
diff --git a/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json b/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json
index 2ad0a4f12..730576f18 100644
--- a/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json
+++ b/content/node.cbd099ee-0b05-402b-803d-9753a84a9e83.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently had Ryan Szrama as a guest on the <a href=\"/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        ",
+            "value": "\n          <p>I recently had Ryan Szrama as a guest on the <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently had Ryan Szrama as a guest on the <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0628dc31f17c91dcb60ca2d028116ec0",
             "target_type": "feeds_feed",
diff --git a/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json b/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json
index 879f7d9f7..dbec4e923 100644
--- a/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json
+++ b/content/node.cbfe0f07-d0fc-46d0-950f-167a091e020d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>If you have multiple implementations of a service, as I <a href=\"/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        ",
+            "value": "\n          <p>If you have multiple implementations of a service, as I <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>If you have multiple implementations of a service, as I <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "385f47a0206ed77604fb346a64e36688",
             "target_type": "feeds_feed",
diff --git a/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json b/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json
index ca6029979..c64445be4 100644
--- a/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json
+++ b/content/node.cc44360f-4d47-4899-9f3b-d4a88c4f7eca.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Because <a href=\"/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        ",
+            "value": "\n          <p>Because <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Because <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "67caaeda05aacc7008f9a07114af9b7f",
             "target_type": "feeds_feed",
diff --git a/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json b/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json
index e6f5a2eeb..5bfd7856a 100644
--- a/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json
+++ b/content/node.cc8a6cc8-4072-46f7-a75c-73683eed0d2e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "69d1afc409380b8667d60251a88e9505",
             "target_type": "feeds_feed",
diff --git a/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json b/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json
index d57c1bab9..5700a2d68 100644
--- a/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json
+++ b/content/node.cd3df6ff-471f-4b56-af7c-9b9a6588367e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"/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=\"/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        ",
+            "value": "\n          <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e5fa9a4299d210679c2b24528450155b",
             "target_type": "feeds_feed",
diff --git a/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json b/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json
index 14d27c1fb..147e0a58e 100644
--- a/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json
+++ b/content/node.cd57083c-1262-450a-aab2-b03fa36456d2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "046eae44685470305d623da38d6189e3",
             "target_type": "feeds_feed",
diff --git a/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json b/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json
index a3ab5d462..d21f9a9f1 100644
--- a/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json
+++ b/content/node.cdd7350c-f06a-410e-841c-06acf0dc312c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c80c0a0daeda9ac2879e1a8706bfad5e",
             "target_type": "feeds_feed",
diff --git a/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json b/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json
index 68dba2b86..3c514e8ad 100644
--- a/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json
+++ b/content/node.cdfbc891-17fa-45e3-9ea6-b0b1bc6defd2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "15a1f14b232babef6136f4cc242315c0",
             "target_type": "feeds_feed",
diff --git a/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json b/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json
index 99c05252c..0296227d6 100644
--- a/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json
+++ b/content/node.ce877341-4025-4610-89b6-f1f4c9bfe5af.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b0767502ae62064308bde448678dfb0b",
             "target_type": "feeds_feed",
diff --git a/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json b/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json
index 099cd90d8..d90435096 100644
--- a/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json
+++ b/content/node.ceb12b38-cafc-4b9e-90dc-a2d0236bd180.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "88540be172808effd2faba79bbb514ad",
             "target_type": "feeds_feed",
diff --git a/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json b/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json
index 5510f9ab9..0e1e26c3b 100644
--- a/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json
+++ b/content/node.cf3507e6-7c08-4b4c-a5c9-0c46ddf9e18e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7d159eec4f78f48020571cf370ef6853",
             "target_type": "feeds_feed",
diff --git a/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json b/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json
index 51348d5da..d7909fdcd 100644
--- a/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json
+++ b/content/node.cfb22ecc-4401-41bf-8ed5-4a9321601a17.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3ebf30f7b8a2b03f2ba95b73683d6184",
             "target_type": "feeds_feed",
diff --git a/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json b/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json
index 45b731621..a1f38ca18 100644
--- a/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json
+++ b/content/node.cfd9f86b-c0a6-4aa8-951e-1381f78e0bfd.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b173e5b02c2560a97cc2ef428412e78e",
             "target_type": "feeds_feed",
diff --git a/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json b/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json
index ef6b2e8fa..a5685be57 100644
--- a/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json
+++ b/content/node.cfe8f476-45e3-485a-8d43-60d1c56f2a8e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "838c549a95c0f1257910cb56a6ab9ebe",
             "target_type": "feeds_feed",
diff --git a/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json b/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json
index d6e188f0c..95ceb978e 100644
--- a/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json
+++ b/content/node.d047a824-fbb1-40b0-8391-ceba0cc250f5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3e61ae665c2eec6ae6c753e53475f4eb",
             "target_type": "feeds_feed",
diff --git a/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json b/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json
index 945b3a1df..8d7c5f750 100644
--- a/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json
+++ b/content/node.d06d1e0c-2e71-4928-922f-c587f712a8e9.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "095fcb0d0aa1a515bcda00c6f0fcebe8",
             "target_type": "feeds_feed",
diff --git a/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json b/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json
index 74944a234..96dc72348 100644
--- a/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json
+++ b/content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/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        ",
+            "value": "\n          <p><a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9217d539c0fc267a1534cb9e166f41ee",
             "target_type": "feeds_feed",
diff --git a/content/node.d0cc3427-9501-4857-93e4-d2153b18ebe5.json b/content/node.d0cc3427-9501-4857-93e4-d2153b18ebe5.json
index c24a8ead1..29d53e21e 100644
--- a/content/node.d0cc3427-9501-4857-93e4-d2153b18ebe5.json
+++ b/content/node.d0cc3427-9501-4857-93e4-d2153b18ebe5.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "317d48d3-4d85-450e-8358-f495d503b41b"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 fdbd1408a..deb322c87 100644
--- a/content/node.d0ee1aae-f2fc-49d2-8865-d4912209eeea.json
+++ b/content/node.d0ee1aae-f2fc-49d2-8865-d4912209eeea.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "562ee3b079f3db7e10cc08cfdda26292",
             "target_type": "feeds_feed",
diff --git a/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json b/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json
index fb73a0aac..5fb29a523 100644
--- a/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json
+++ b/content/node.d146f785-7ae1-4728-8d90-20b9cbf8f35d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "204bc5dcd32cb6884423a2b2c71f81aa",
             "target_type": "feeds_feed",
diff --git a/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json b/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json
index 27ab8cf69..734f16ecd 100644
--- a/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json
+++ b/content/node.d1633911-dff9-4079-a0cb-5efe70d9a1fb.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\">published soon<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/podcast\">published soon<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\">published soon<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a813d4b849fdced0618aa5694a3bdadd",
             "target_type": "feeds_feed",
diff --git a/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json b/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json
index 21e2a3071..0564a5958 100644
--- a/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json
+++ b/content/node.d1a650c6-fd8f-4509-801b-10c14f10344e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c064efff8a7c26a4e05fee32b076e0b2",
             "target_type": "feeds_feed",
diff --git a/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json b/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json
index 5e4f3bb5f..656fcf68c 100644
--- a/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json
+++ b/content/node.d31baf5d-0590-4126-aa80-85de9beed94f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "40f6813369f442150f84b87eab9b30ed",
             "target_type": "feeds_feed",
diff --git a/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json b/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json
index 9ab3937fc..dfa7c2c20 100644
--- a/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json
+++ b/content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3b3fc896ed9c2c1970c93dce0d903cac",
             "target_type": "feeds_feed",
diff --git a/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json b/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json
index ceccf35b7..222a4856a 100644
--- a/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json
+++ b/content/node.d33e4704-c07e-421e-8227-f3f74e9f57ff.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e1706194e7328831ad93ed4122decea1",
             "target_type": "feeds_feed",
diff --git a/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json b/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json
index 158423cd1..9cb72b36c 100644
--- a/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json
+++ b/content/node.d344a28e-aa79-4533-8eac-f112926fe811.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I like the <a href=\"/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        ",
+            "value": "\n          <p>I like the <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I like the <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cd05e2a441bf25694103bede108b3e8b",
             "target_type": "feeds_feed",
diff --git a/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json b/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json
index 0158ca6ac..8ccd1c5d3 100644
--- a/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json
+++ b/content/node.d3d14705-ef6a-4827-afad-bb2963dac369.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6afaa3344e6ec1907672718a56f00a9c",
             "target_type": "feeds_feed",
diff --git a/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json b/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json
index e1ca4215d..823b3e936 100644
--- a/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json
+++ b/content/node.d3e4d075-4050-46af-bfd3-94944eaae35b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8740e9029c98140ce8609709977e5145",
             "target_type": "feeds_feed",
diff --git a/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json b/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json
index 92c897585..97cb04d61 100644
--- a/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json
+++ b/content/node.d3fe0eae-7883-4fe6-9a98-747b53d860ca.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e20e2bce0a560bd0261032201f0cacd5",
             "target_type": "feeds_feed",
diff --git a/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json b/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json
index 92c5e8470..e455d8a2f 100644
--- a/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json
+++ b/content/node.d408fc8b-4be2-40b9-b1d4-2047cdc472b6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "82cd165f20dd5a6540c140be3cb646c9",
             "target_type": "feeds_feed",
diff --git a/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json b/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json
index acf2cb5f6..26880bd5a 100644
--- a/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json
+++ b/content/node.d411d43b-7c61-4fa1-b41b-4e7ec5eb862c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/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        ",
+            "value": "\n          <p><a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6306217afe87f3d8cd659f6d4c55923d",
             "target_type": "feeds_feed",
diff --git a/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json b/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json
index 3039364eb..e8381d823 100644
--- a/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json
+++ b/content/node.d415ecdc-cec1-4cc4-98c1-8bcd1d0384eb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "74b3eda982231a0b291c52c67ee09063",
             "target_type": "feeds_feed",
diff --git a/content/node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18.json b/content/node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18.json
index 0dc45cc55..f5430d209 100644
--- a/content/node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18.json
+++ b/content/node.d417d779-e0ca-4f36-8aa3-5ef39a8c4a18.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "a1f48bb9-493b-4f92-b1ac-74152cd6f980"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 8a59f4cf1..10d8460cb 100644
--- a/content/node.d421a5a4-8025-4809-8a30-68c723e46af6.json
+++ b/content/node.d421a5a4-8025-4809-8a30-68c723e46af6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "40e9fa32eee6340942e24d365e4890fa",
             "target_type": "feeds_feed",
diff --git a/content/node.d473b252-b668-40bc-b744-68ea259702fc.json b/content/node.d473b252-b668-40bc-b744-68ea259702fc.json
index ce65332c9..c8caae67e 100644
--- a/content/node.d473b252-b668-40bc-b744-68ea259702fc.json
+++ b/content/node.d473b252-b668-40bc-b744-68ea259702fc.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "0a8e0788-6709-46c0-ab72-f796ee96ad95"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 a43eebf84..58a303ada 100644
--- a/content/node.d487d829-d35c-4c4f-b4e8-af804b29463e.json
+++ b/content/node.d487d829-d35c-4c4f-b4e8-af804b29463e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5b190bfabbdf6ba7e6db2bf0b5e381b8",
             "target_type": "feeds_feed",
diff --git a/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json b/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json
index c87964da8..373cd62a2 100644
--- a/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json
+++ b/content/node.d4beee99-ab37-4663-b331-4de9f42ec333.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "edf363d6ea23096050f54141a8e16bdc",
             "target_type": "feeds_feed",
diff --git a/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json b/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json
index ddf967408..59b94a1c0 100644
--- a/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json
+++ b/content/node.d4e3757c-36f7-45f7-a679-6292e8300200.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Last month, I released the <a href=\"/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        ",
+            "value": "\n          <p>Last month, I released the <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Last month, I released the <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "206e422b01263cdaf2eb41de25c44fc8",
             "target_type": "feeds_feed",
diff --git a/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json b/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json
index 380c541c2..0858b10d4 100644
--- a/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json
+++ b/content/node.d50d17e4-f42c-4296-8f21-5c2cdaea92ed.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f230560d474c0edb4725863e286d1ae8",
             "target_type": "feeds_feed",
diff --git a/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json b/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json
index 557a6f290..2a0f6e3e7 100644
--- a/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json
+++ b/content/node.d592f939-eaf5-4c33-89f6-8af3b36d338f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "062455710dfbfed24f6c650fa013d504",
             "target_type": "feeds_feed",
diff --git a/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json b/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json
index a45d296c6..ac90647c2 100644
--- a/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json
+++ b/content/node.d5957f63-fc2f-4046-864c-9e01c3978a6c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8077a02b9c896a424fb902f6e03884fd",
             "target_type": "feeds_feed",
diff --git a/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json b/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json
index 4a2057f93..5bb8d2cae 100644
--- a/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json
+++ b/content/node.d5d38a64-f226-42e0-8691-6c1b128435bf.json
@@ -76,8 +76,7 @@
     ],
     "path": [
         {
-            "alias": "",
-            "pid": null,
+            "alias": "\/daily\/2025\/05\/15\/dont-dump-write-test",
             "langcode": "en"
         }
     ],
diff --git a/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json b/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json
index 7c9d843e7..1d04a1af3 100644
--- a/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json
+++ b/content/node.d613376e-133d-4730-86f1-70661d24c7ff.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday I explained that Nix, or specifically NixOS, <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Yesterday I explained that Nix, or specifically NixOS, <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday I explained that Nix, or specifically NixOS, <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e7631b334d9daafcfa47e2f3cd60def6",
             "target_type": "feeds_feed",
diff --git a/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json b/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json
index 0d74f7936..c565caf72 100644
--- a/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json
+++ b/content/node.d6363924-78ee-4086-8cf0-41e07c030fd4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Static site generators <a href=\"/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=\"/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=\"/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        ",
+            "value": "\n          <p>Static site generators <a href=\"\/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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Static site generators <a href=\"/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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d941624a5b449961e856801045bb330f",
             "target_type": "feeds_feed",
diff --git a/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json b/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json
index c035bc3bd..79add9df9 100644
--- a/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json
+++ b/content/node.d64f0811-a486-4194-99e8-67d21263cb7f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0f4b0d278153b12d1d47eab4f90b1830",
             "target_type": "feeds_feed",
diff --git a/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json b/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json
index e16bc7aa5..0ba1bad8b 100644
--- a/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json
+++ b/content/node.d6c8fb91-1f7d-4931-84e3-e7257a79daf2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as <a href=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>As well as <a href=\"\/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=\"\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as <a href=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "471a590b0815f9d675396ac79f411d89",
             "target_type": "feeds_feed",
diff --git a/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json b/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json
index c7ff6dc90..222585f4c 100644
--- a/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json
+++ b/content/node.d753217f-2d8f-431d-850c-d54597b46b76.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>In the majority of my <code>flake.nix<\/code> files, such as the one <a href=\"/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        ",
+            "value": "\n          <p>In the majority of my <code>flake.nix<\/code> files, such as the one <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>In the majority of my <code>flake.nix<\/code> files, such as the one <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0c86a05ca569c1a814e9706841378658",
             "target_type": "feeds_feed",
diff --git a/content/node.d783263e-b457-4785-b15c-ce631faf3192.json b/content/node.d783263e-b457-4785-b15c-ce631faf3192.json
index ef8757742..1ff214095 100644
--- a/content/node.d783263e-b457-4785-b15c-ce631faf3192.json
+++ b/content/node.d783263e-b457-4785-b15c-ce631faf3192.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fb71e18ebe99ec55d0c2fe23152a48ed",
             "target_type": "feeds_feed",
diff --git a/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json b/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json
index abff7c870..6720b89e1 100644
--- a/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json
+++ b/content/node.d7924931-d38d-4c59-a987-6a10f48a18c9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "82e659503662822ad611232083fb7ed4",
             "target_type": "feeds_feed",
diff --git a/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json b/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json
index e0e181747..824519b8c 100644
--- a/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json
+++ b/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e320d92eee616c932a9a3fe26b35047c",
             "target_type": "feeds_feed",
diff --git a/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json b/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json
index 3df1e1bd7..2007226a0 100644
--- a/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json
+++ b/content/node.d7c17af9-35ea-4346-bd72-cd68b2ebd88c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4830962fbdad357d03b6e3606bb1df38",
             "target_type": "feeds_feed",
diff --git a/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json b/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json
index 784c332fd..6f12280ce 100644
--- a/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json
+++ b/content/node.d7c36fee-2434-4c3c-95d3-df1303603a35.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Today, Beyond Blocks - <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Today, Beyond Blocks - <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Today, Beyond Blocks - <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "421e5b39dd224c7b86dc375cf5539d56",
             "target_type": "feeds_feed",
diff --git a/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json b/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json
index a81fbceb5..bc8f32f97 100644
--- a/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json
+++ b/content/node.d7d93932-2902-44e3-94d3-331725ce1859.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ffb02a8c9c8b7c10c1db4f1162b1bfee",
             "target_type": "feeds_feed",
diff --git a/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json b/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json
index 74507d71f..0ccfe6289 100644
--- a/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json
+++ b/content/node.d7f7c11b-8ff6-4543-9945-fd500d9a80f9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7ee7cb63765e8fc082bb197e047a1b09",
             "target_type": "feeds_feed",
diff --git a/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json b/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json
index 6a269f72e..37575ccae 100644
--- a/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json
+++ b/content/node.d9520278-39f8-4cdb-9f94-632cabb49acd.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "366cf3181f0d0907a5bca82e961c730d",
             "target_type": "feeds_feed",
diff --git a/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json b/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json
index e2d20e5bb..ecc7e9a08 100644
--- a/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json
+++ b/content/node.d9a46ea6-4cd5-45a9-9871-5c48d32e1cdb.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "135db619112384902229409c9c646b9f",
             "target_type": "feeds_feed",
diff --git a/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json b/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json
index 6dfc63f59..cfe6c11b6 100644
--- a/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json
+++ b/content/node.d9c346b8-279b-4432-9d3a-539a576da4e2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/ansible-course\">Register for my upcoming free email course<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1ac2b400239670e99f97edf6edae6a39",
             "target_type": "feeds_feed",
diff --git a/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json b/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json
index 1fea7ac9a..c0e1104cf 100644
--- a/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json
+++ b/content/node.d9e7d2f3-bb82-4e97-9269-d65e6b08d8d9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "86193996441d0e9ec3a4d46be5b79eb2",
             "target_type": "feeds_feed",
diff --git a/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json b/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json
index fb47f6f27..ffa9da57b 100644
--- a/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json
+++ b/content/node.da3412f8-9a33-4395-a75e-4d107d2557a4.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a7a933ef1250a866505ee7da5f99d039",
             "target_type": "feeds_feed",
diff --git a/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json b/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json
index f98749d3b..4940be490 100644
--- a/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json
+++ b/content/node.da4dbacd-671b-45ee-b70e-58aa16de7d8f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bee10cd012e328234f493c6d52a62c57",
             "target_type": "feeds_feed",
diff --git a/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json b/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json
index f6e7249c0..2c21f778d 100644
--- a/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json
+++ b/content/node.da62317b-2539-43bd-8db0-94bddb14174e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4050be034c1d59312fb930c3290468db",
             "target_type": "feeds_feed",
diff --git a/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json b/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json
index 4a8485bc4..e25df29d0 100644
--- a/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json
+++ b/content/node.daaf3365-9511-4f12-a744-2a8c37a655b9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "142789ac0ec97b452b470ffc7dfb962c",
             "target_type": "feeds_feed",
diff --git a/content/node.dab13df7-2835-407a-90c5-f5574585718b.json b/content/node.dab13df7-2835-407a-90c5-f5574585718b.json
index ec086603c..292164156 100644
--- a/content/node.dab13df7-2835-407a-90c5-f5574585718b.json
+++ b/content/node.dab13df7-2835-407a-90c5-f5574585718b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "79d80b699a527736bd9685bbb68dad9e",
             "target_type": "feeds_feed",
diff --git a/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json b/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json
index 57ab90d1d..c9f924f61 100644
--- a/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json
+++ b/content/node.dab1657a-80c4-4b6c-b7c5-28b874fff857.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "03586d61c309592caca993fa7b3f584c",
             "target_type": "feeds_feed",
diff --git a/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json b/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json
index 1ddb069ff..591030226 100644
--- a/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json
+++ b/content/node.dabbd6ba-8fd9-45dd-98f5-27aa3804dd46.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d5ed61ce59348374630aa49fea8f3709",
             "target_type": "feeds_feed",
diff --git a/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json b/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json
index e210e2745..aed33515a 100644
--- a/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json
+++ b/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "58c9da441a16db434c006de482ddb439",
             "target_type": "feeds_feed",
diff --git a/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json b/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json
index abcbb3d82..365983c2c 100644
--- a/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json
+++ b/content/node.db312e00-7a9d-492d-a6db-7298848e06b2.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bbd5da09465e121b021023b291b56bcd",
             "target_type": "feeds_feed",
diff --git a/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json b/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json
index aa1dc161d..2958e9f39 100644
--- a/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json
+++ b/content/node.dbb959b1-390d-45e8-b080-097a313545d8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e93df0be19a187ce2cfa64f7e7f55371",
             "target_type": "feeds_feed",
diff --git a/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json b/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json
index ca69f9016..2603124bd 100644
--- a/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json
+++ b/content/node.dcaa735c-9ed7-4894-a7bd-ed8931cdd75e.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I recently recorded an episode of <a href=\"/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        ",
+            "value": "\n          <p>I recently recorded an episode of <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I recently recorded an episode of <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2b01095ab8d31f34c714ec27f276817e",
             "target_type": "feeds_feed",
diff --git a/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json b/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json
index bf7199dc2..ed8ead349 100644
--- a/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json
+++ b/content/node.dcae03b2-1838-4db7-9b1d-3fe87b70c19a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f662b53b72b350d04041ab2dc4b49ad0",
             "target_type": "feeds_feed",
diff --git a/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json b/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json
index 75e389296..a2c4e86bc 100644
--- a/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json
+++ b/content/node.dd462165-113a-4b0e-b566-a242cfd475dd.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/podcast\/12-nick-janetakis-docker\">Listen to the episode<\/a><\/p>\n\n        ",
+            "value": "\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=\"\/podcast\/12-nick-janetakis-docker\">Listen to the episode<\/a><\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/12-nick-janetakis-docker\">Listen to the episode<\/a><\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3890d1a3914bf410eda6c0659d3df851",
             "target_type": "feeds_feed",
diff --git a/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json b/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json
index 3efa9849f..579a56f6b 100644
--- a/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json
+++ b/content/node.dda819a3-30c3-45e3-9cb0-30c1f1ffa48e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "07c1e92a060647818b3b343a1a9f7df4",
             "target_type": "feeds_feed",
diff --git a/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json b/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json
index b0a643a95..83275cc28 100644
--- a/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json
+++ b/content/node.de3c8e29-8a94-4f29-8c6a-267c0739c5c8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1ae8abd3b43dffe1b4f702b6060f9213",
             "target_type": "feeds_feed",
diff --git a/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json b/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json
index a71f3b303..b78c74821 100644
--- a/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json
+++ b/content/node.de42d5d4-29c1-4cd7-813a-1a1764f16a7b.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "903c2f153f561fe50422411d38fba8cd",
             "target_type": "feeds_feed",
diff --git a/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json b/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json
index 727312139..46df845cb 100644
--- a/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json
+++ b/content/node.dea5d550-6603-412d-b1a6-eec70c353b96.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>After writing about <a href=\"/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=\"/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        ",
+            "value": "\n          <p>After writing about <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>After writing about <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1dee6b9fb013248db22e14f83b12d176",
             "target_type": "feeds_feed",
diff --git a/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json b/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json
index ca9c4c01c..0bc6c277c 100644
--- a/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json
+++ b/content/node.deaafd9d-8951-41fb-bc84-745a611f3b1b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>As well as my consulting and development work, and educational content such as my <a href=\"/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        ",
+            "value": "\n          <p>As well as my consulting and development work, and educational content such as my <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>As well as my consulting and development work, and educational content such as my <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "14bc4a0b3a6ff96445c7195431abf9ff",
             "target_type": "feeds_feed",
diff --git a/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json b/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json
index 3275380a9..c2dafd9e0 100644
--- a/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json
+++ b/content/node.dec2b9a9-a942-420c-ad1c-a41ab979ba6b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9b0cfa53767098dc8873acdefd4d5eba",
             "target_type": "feeds_feed",
diff --git a/content/node.deefc5f9-12d4-46a5-a647-4522de0e5e63.json b/content/node.deefc5f9-12d4-46a5-a647-4522de0e5e63.json
index c147274de..8125f29a0 100644
--- a/content/node.deefc5f9-12d4-46a5-a647-4522de0e5e63.json
+++ b/content/node.deefc5f9-12d4-46a5-a647-4522de0e5e63.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "b4e262ae-1e39-471f-b5ff-111df3b772d9"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 37d8a804b..3055506c8 100644
--- a/content/node.defbeab8-28ca-4444-b09b-5121de794602.json
+++ b/content/node.defbeab8-28ca-4444-b09b-5121de794602.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d1ab27d91583fa59d50cb8b6676b29d7",
             "target_type": "feeds_feed",
diff --git a/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json b/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json
index 064792cbc..ee35eb358 100644
--- a/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json
+++ b/content/node.df0a8efc-bfd5-4c57-adc6-08d63794041e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "59d38746fc261bf6e7575946a0fea245",
             "target_type": "feeds_feed",
diff --git a/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json b/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json
index 83e1c7ea9..f88993e98 100644
--- a/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json
+++ b/content/node.df628b2c-64d0-4b35-bbde-c3536bcb05bc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3153413157ef5cd139bceebefc51bf52",
             "target_type": "feeds_feed",
diff --git a/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json b/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json
index 523c5d03b..f4e3e5912 100644
--- a/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json
+++ b/content/node.df8406e6-56bf-4de6-a8e0-64caf5b52058.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a773ef0f61d9a98ee69ac78735c23bbb",
             "target_type": "feeds_feed",
diff --git a/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json b/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json
index cb6a82a52..ca0dc953c 100644
--- a/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json
+++ b/content/node.dfe4489a-7d64-4368-b86e-e35180377c15.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1f560ca61cb72b1c394c162cff4811a1",
             "target_type": "feeds_feed",
diff --git a/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json b/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json
index b67bab4a9..179ea38ad 100644
--- a/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json
+++ b/content/node.dfe87217-dc3b-413c-9e42-912386be5d5f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "a7668c39a4177091d20aeb7c9d86cdd2",
             "target_type": "feeds_feed",
diff --git a/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json b/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json
index ad689d29d..127bd045e 100644
--- a/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json
+++ b/content/node.e00e0cdc-8668-4ca5-86e0-1219332907c0.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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\u00a0version.<\/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=\"/podcast\/10-ryan-weaver-symfonycasts\">recent episode of Beyond Blocks<\/a>, \"It takes the drama out of open-source\".<\/p>\n\n        ",
+            "value": "\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\u00a0version.<\/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=\"\/podcast\/10-ryan-weaver-symfonycasts\">recent episode of Beyond Blocks<\/a>, \"It takes the drama out of open-source\".<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/podcast\/10-ryan-weaver-symfonycasts\">recent episode of Beyond Blocks<\/a>, \"It takes the drama out of open-source\".<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7b0e016e1d34348675c648d525c9e63f",
             "target_type": "feeds_feed",
diff --git a/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json b/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json
index 7603aea96..c6a233ad6 100644
--- a/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json
+++ b/content/node.e01efd03-7851-41b8-a34d-7b7a56d77d31.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3cbb18db43461716704cf4d74f02adff",
             "target_type": "feeds_feed",
diff --git a/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json b/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json
index ded69c322..de05dc0b1 100644
--- a/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json
+++ b/content/node.e0c0707d-b542-4aae-a8b4-8633673fd520.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d4fd1c5b9efd845282526403295dacbd",
             "target_type": "feeds_feed",
diff --git a/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json b/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json
index 5ba873368..51f4682a5 100644
--- a/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json
+++ b/content/node.e0d6060d-596b-460f-9cac-22ef16a947b6.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0a86c42026e6ba3f312a5db3e6383a25",
             "target_type": "feeds_feed",
diff --git a/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json b/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json
index e5425a350..8c9aaa557 100644
--- a/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json
+++ b/content/node.e11ce42f-0d2e-4afb-9017-521fde9521a2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/call\">Drupal 7 upgrade consultation call<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "32e42c2ad69b53ec2591f07e14479344",
             "target_type": "feeds_feed",
diff --git a/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json b/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json
index fdb20201c..eff247047 100644
--- a/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json
+++ b/content/node.e169a4e6-9ebe-437b-90e7-e53f9d559a7f.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>How many TODO comments do you have in your codebase?<\/p>\n\n<p>After posting <a href=\"/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        ",
+            "value": "\n          <p>How many TODO comments do you have in your codebase?<\/p>\n\n<p>After posting <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>How many TODO comments do you have in your codebase?<\/p>\n\n<p>After posting <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "536d18a2fcc971be2e7320233cacb1fc",
             "target_type": "feeds_feed",
diff --git a/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json b/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json
index 9f11062cf..8b40a5a8b 100644
--- a/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json
+++ b/content/node.e179e840-bd5c-45b3-8bae-2b3706861bb3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "146ae12ea9007bdc9e974f9967897038",
             "target_type": "feeds_feed",
diff --git a/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json b/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json
index 839f690a0..608e95912 100644
--- a/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json
+++ b/content/node.e187ec3b-5cde-4ab2-8c05-2d38eaa99756.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "4284e8bf5254c92b4ec97575e0b82116",
             "target_type": "feeds_feed",
diff --git a/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json b/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json
index c3a90da45..254634224 100644
--- a/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json
+++ b/content/node.e2679ec1-9cf5-483f-86e0-f176db3daae4.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>I've been <a href=\"/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=\"/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        ",
+            "value": "\n          <p>I've been <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>I've been <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e38c49ae0796baf36f3a37341052d155",
             "target_type": "feeds_feed",
diff --git a/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json b/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json
index 70aa453a3..14fecd1b5 100644
--- a/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json
+++ b/content/node.e292ffd7-ca03-4054-89d1-90ffbae8d1b0.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1ed822840535da7f16ffd29dace80ede",
             "target_type": "feeds_feed",
diff --git a/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json b/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json
index 0d070486b..dd9b104bb 100644
--- a/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json
+++ b/content/node.e2991eb4-1aee-4d04-9045-989159a9b64f.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "07d6a599d591e31580f215b484e9ae34",
             "target_type": "feeds_feed",
diff --git a/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json b/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json
index 9c397a283..e8258cc59 100644
--- a/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json
+++ b/content/node.e3391a68-8501-49ac-a509-c7a1ac579193.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "37b746e93ec56556229b8c0a758a28cf",
             "target_type": "feeds_feed",
diff --git a/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json b/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json
index 3ead6a839..5491dd065 100644
--- a/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json
+++ b/content/node.e35f213b-1b5c-453e-bf2d-fa542a37aac3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3523efa30025b9ea53133ab91ddb3086",
             "target_type": "feeds_feed",
diff --git a/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json b/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json
index 1d91bc913..4f69725c9 100644
--- a/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json
+++ b/content/node.e52fda31-17cc-4379-b8cb-1a22c9e11601.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "427e5da306c0b08b7e6ba695b5a3017b",
             "target_type": "feeds_feed",
diff --git a/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json b/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json
index 98a7fb673..70d9b9c14 100644
--- a/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json
+++ b/content/node.e5d8aaf6-c58c-4851-a48d-e86a616c32b3.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "868ebc7b4844fbd04025c16a9cfb16e9",
             "target_type": "feeds_feed",
diff --git a/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json b/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json
index 2a03f5f76..5bb3d4dda 100644
--- a/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json
+++ b/content/node.e652f53d-9472-4ce0-a70b-79f0dbaa9d1a.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "6f362b9d79b81b8f344cb774a1638e59",
             "target_type": "feeds_feed",
diff --git a/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json b/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json
index 0b75ecae3..5736e7760 100644
--- a/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json
+++ b/content/node.e7cc391d-fde3-4db8-9f1b-5a4b460cca29.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Yesterday, <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Yesterday, <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Yesterday, <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1c553d5a90092cb35e635bb87120d74a",
             "target_type": "feeds_feed",
diff --git a/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json b/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json
index 7adcb6d6e..6019e9d4e 100644
--- a/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json
+++ b/content/node.e8275304-6db2-435e-bd89-9810a1f51490.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ee9c7fdfadc92a583c9a83309b14f644",
             "target_type": "feeds_feed",
diff --git a/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json b/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json
index 8e53f554f..cee30006c 100644
--- a/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json
+++ b/content/node.e837c37b-a3b6-49bd-9af7-e3bc771c4786.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8b2ab9118da9393b9e5398111f66ff1f",
             "target_type": "feeds_feed",
diff --git a/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json b/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json
index 84aa2338d..bde2706ab 100644
--- a/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json
+++ b/content/node.e88621ad-4a3d-481e-b292-b710f0756313.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9932561d0945f63746a1bb5ddd951b0a",
             "target_type": "feeds_feed",
diff --git a/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json b/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json
index d7f4559f3..a5ed61e4d 100644
--- a/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json
+++ b/content/node.e88b4449-20b6-4165-880b-6d34b9579781.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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        ",
+            "value": "\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=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "780bda0044c53e6e45fb49f2037ac82e",
             "target_type": "feeds_feed",
diff --git a/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json b/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json
index 2501a3c23..66a63c663 100644
--- a/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json
+++ b/content/node.e91d28ca-1730-4560-82ab-205175ca2bf9.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c165a71ff34130f10b8bbd674b2708a6",
             "target_type": "feeds_feed",
diff --git a/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json b/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json
index 4bc1095b5..f888e414e 100644
--- a/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json
+++ b/content/node.ea06edab-74a5-42d4-add9-d4dce3d0f792.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c4f9c5744c27b541d231076231201427",
             "target_type": "feeds_feed",
diff --git a/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json b/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json
index 2fb8e7e83..8eeec6e88 100644
--- a/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json
+++ b/content/node.ea81e659-48e0-4eaf-ae3b-a30012102d0e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bd41bad48401d8b39626d1b4c1fa46a3",
             "target_type": "feeds_feed",
diff --git a/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json b/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json
index 3572d8135..7bbd18e36 100644
--- a/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json
+++ b/content/node.eb1fecb1-6d0c-413a-b546-2c2fcf320d94.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "508bce081c6ebd69e4dc32058f9c788e",
             "target_type": "feeds_feed",
diff --git a/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json b/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json
index 0c4c0c4b7..0151b8924 100644
--- a/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json
+++ b/content/node.ebcaf7c3-e103-448b-aa74-6bb469be0c2d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "80b28c3ecc0b1a024878f575f11385d3",
             "target_type": "feeds_feed",
diff --git a/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json b/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json
index e2ff80c2b..ff1ae00d5 100644
--- a/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json
+++ b/content/node.ebf479a8-f93c-4972-ae90-8b59a0ca8081.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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\u00a0so I thought about how I could do something similar within my <a href=\"/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\u00a0for 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        ",
+            "value": "\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\u00a0so I thought about how I could do something similar within my <a href=\"\/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\u00a0for 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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7fd7688e20aec257116644fad8d96aac",
             "target_type": "feeds_feed",
diff --git a/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json b/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json
index 5e4c91d0c..4275f7a58 100644
--- a/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json
+++ b/content/node.ec354679-9830-4361-b0eb-16e976e888ce.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A few months ago, <a href=\"/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=\"/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        ",
+            "value": "\n          <p>A few months ago, <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A few months ago, <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "94b06833489046a4c26442548eee3ca2",
             "target_type": "feeds_feed",
diff --git a/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json b/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json
index 13124e916..cd3c7384c 100644
--- a/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json
+++ b/content/node.ec60eda5-4095-465e-a7f7-7bcf1f5bad8a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/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=\"/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">make it easy to run those tasks locally<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/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=\"\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">make it easy to run those tasks locally<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/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=\"/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">make it easy to run those tasks locally<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d54ad8e941f721ec3bbb3abacd9ca123",
             "target_type": "feeds_feed",
diff --git a/content/node.ec6af399-d960-4715-92c5-760fce33d803.json b/content/node.ec6af399-d960-4715-92c5-760fce33d803.json
index b2a2b7c37..4b5205d21 100644
--- a/content/node.ec6af399-d960-4715-92c5-760fce33d803.json
+++ b/content/node.ec6af399-d960-4715-92c5-760fce33d803.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ce0fd785eeded51305f4d32749a7ce65",
             "target_type": "feeds_feed",
diff --git a/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json b/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json
index 49979cd53..f212d25a4 100644
--- a/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json
+++ b/content/node.ed66b8e2-8b3c-4be4-8cde-eabdfce17709.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d5154e6cb6c11f4bc95c35ff8fc596bd",
             "target_type": "feeds_feed",
diff --git a/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json b/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json
index f9641997f..ff620e136 100644
--- a/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json
+++ b/content/node.ed7dc940-2eb3-48e1-8c38-fc9c812db5ef.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/podcast\">the Beyond Blocks podcast page<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/podcast\">the Beyond Blocks podcast page<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/podcast\">the Beyond Blocks podcast page<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0133e2d8424efefed5ed2aa8915ee1c6",
             "target_type": "feeds_feed",
diff --git a/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json b/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json
index 530db2645..f582388ba 100644
--- a/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json
+++ b/content/node.ed95d76b-0dba-46a3-aa18-2d5f70b07511.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b40abd231dda53a740949b3e5d5ac434",
             "target_type": "feeds_feed",
diff --git a/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json b/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json
index 1697ffb80..6dc5649f1 100644
--- a/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json
+++ b/content/node.edacb021-6f94-4f6f-a39b-4362609caea0.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7a9179502a50a3f6f3443cdebef1a615",
             "target_type": "feeds_feed",
diff --git a/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json b/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json
index ea333d817..2aedc919a 100644
--- a/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json
+++ b/content/node.edd8befd-440a-479a-9759-c8f90b4a2528.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e15720a4ab8c5005c73431fcac145c86",
             "target_type": "feeds_feed",
diff --git a/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json b/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json
index e3c9b3dd2..3b5607c6f 100644
--- a/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json
+++ b/content/node.ee0cdd20-86c9-4ff6-8129-7367e5d9ce2d.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>If you've experienced issues or are worried about deploying changes to production, <a href=\"/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        ",
+            "value": "\n          <p>If you've experienced issues or are worried about deploying changes to production, <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>If you've experienced issues or are worried about deploying changes to production, <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e4e7b3f159846b99658730ca08899088",
             "target_type": "feeds_feed",
diff --git a/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json b/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json
index 8a6281b49..192eef472 100644
--- a/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json
+++ b/content/node.ee81b821-f2be-4dce-a119-7e421bbc7e04.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3b2f48d28cdda255b884d631a4a170ad",
             "target_type": "feeds_feed",
diff --git a/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json b/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json
index bd4904557..ed3260aa0 100644
--- a/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json
+++ b/content/node.ee874ddb-dd03-4843-8a61-202936b2a845.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f999f40729d1c4017022ac0e4fd81a1d",
             "target_type": "feeds_feed",
diff --git a/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json b/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json
index 182c9a116..74113145b 100644
--- a/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json
+++ b/content/node.eed12ec3-1c34-4165-b66d-62dc0cf3dc76.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0fe766113c492410fc331b3c40f82f8e",
             "target_type": "feeds_feed",
diff --git a/content/node.eedbf764-01b3-48e8-9de4-b8d23caa8efd.json b/content/node.eedbf764-01b3-48e8-9de4-b8d23caa8efd.json
index 46274a8b8..0f69af651 100644
--- a/content/node.eedbf764-01b3-48e8-9de4-b8d23caa8efd.json
+++ b/content/node.eedbf764-01b3-48e8-9de4-b8d23caa8efd.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "2fb2991f-8bac-4335-a8cd-a5c6edb158df"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 a835ea1d6..0426cff14 100644
--- a/content/node.eef4147e-e47a-411e-a7de-eb67638dc6bb.json
+++ b/content/node.eef4147e-e47a-411e-a7de-eb67638dc6bb.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d55547f4588464a67252a7743560b0b3",
             "target_type": "feeds_feed",
diff --git a/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json b/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json
index 75d1108eb..93feeb82f 100644
--- a/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json
+++ b/content/node.ef157ce9-4fc5-4441-8592-989b1fcd61b8.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>An important thing when using a tool like <a href=\"/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=\"/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        ",
+            "value": "\n          <p>An important thing when using a tool like <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>An important thing when using a tool like <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ef62cb3ca57e2e9ff518c139412e1563",
             "target_type": "feeds_feed",
diff --git a/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json b/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json
index 5fc103a25..408476732 100644
--- a/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json
+++ b/content/node.efe699bf-ef82-4ce5-b87c-1cbb2e0aa420.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "c2095c4a1278959cfff849fb4f819ace",
             "target_type": "feeds_feed",
diff --git a/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json b/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json
index 6a2033702..f7a1bee8c 100644
--- a/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json
+++ b/content/node.f076aa19-9261-4d21-8fbc-f330d9d4e87a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>After <a href=\"/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        ",
+            "value": "\n          <p>After <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>After <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "23799429878e6da040e6b839e960f525",
             "target_type": "feeds_feed",
diff --git a/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json b/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json
index 454d3e9ab..bdcd0f9ef 100644
--- a/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json
+++ b/content/node.f0fe2425-0fca-41a3-8ca8-67953798b7a5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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=\"/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">replaced Docker and Docker Compose<\/a> on my development projects.<\/p>\n\n        ",
+            "value": "\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=\"\/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=\"\/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">replaced Docker and Docker Compose<\/a> on my development projects.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/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=\"/daily\/2024\/11\/11\/could-nix-and-devenv-replace-docker-compose\">replaced Docker and Docker Compose<\/a> on my development projects.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "461f987d1bc88b97e125becc82a9fd46",
             "target_type": "feeds_feed",
diff --git a/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json b/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json
index fe6aaa21a..8cc89eae9 100644
--- a/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json
+++ b/content/node.f2008694-9d04-4952-b40b-ae2fd880d9fe.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "1ea9de41ddc7b8f9fcdc10618e2ae56b",
             "target_type": "feeds_feed",
diff --git a/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json b/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json
index 6d0f7aaf3..e6eda1191 100644
--- a/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json
+++ b/content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "53ca25f2417162597931bed0d3c8cb57",
             "target_type": "feeds_feed",
diff --git a/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json b/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json
index 1abaf019b..b545fc901 100644
--- a/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json
+++ b/content/node.f229a8b2-9561-4e7d-ad3f-de8acd5a78a3.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f8ddff544e9f6f9a874ffeb914537a12",
             "target_type": "feeds_feed",
diff --git a/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json b/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json
index a03eafe28..202c97f4c 100644
--- a/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json
+++ b/content/node.f245814b-3957-4c84-82fb-47134c3edd24.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9400b956833d34cef7783e6b4ae755bd",
             "target_type": "feeds_feed",
diff --git a/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json b/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json
index fbe90c494..bfd7a3ab3 100644
--- a/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json
+++ b/content/node.f33ae168-76dc-4662-9998-5f6729d19523.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0ef60547dc24a30bc29205ee7fee1f5a",
             "target_type": "feeds_feed",
diff --git a/content/node.f343899f-5778-4b23-a97e-bda411656646.json b/content/node.f343899f-5778-4b23-a97e-bda411656646.json
index 2dfe8e7f1..b5e8f855c 100644
--- a/content/node.f343899f-5778-4b23-a97e-bda411656646.json
+++ b/content/node.f343899f-5778-4b23-a97e-bda411656646.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "60134faa8ccecf50d1f6520e1f849b0c",
             "target_type": "feeds_feed",
diff --git a/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json b/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json
index 38be70cdc..432360de7 100644
--- a/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json
+++ b/content/node.f3454ba6-e5bd-4d85-838a-b838f8687ce7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f746e5178d11a55b0a3eed164216d25a",
             "target_type": "feeds_feed",
diff --git a/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json b/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json
index f4b418c4e..5050b8762 100644
--- a/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json
+++ b/content/node.f38ff989-2a23-4834-9b3a-edc7d016d66d.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "00bb8f11007795b6fe1e9ad3728526ae",
             "target_type": "feeds_feed",
diff --git a/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json b/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json
index 7e8b18e7e..98ee2f427 100644
--- a/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json
+++ b/content/node.f3e4ac1a-f18d-4047-ab65-cdd7f6b31c7a.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>A few days ago, I asked <a href=\"/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=\"/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        ",
+            "value": "\n          <p>A few days ago, I asked <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>A few days ago, I asked <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ccf6ad9403289a3e6790c1f35b1ec8a0",
             "target_type": "feeds_feed",
diff --git a/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json b/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json
index c8b7690ca..f45bb1591 100644
--- a/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json
+++ b/content/node.f3e69f27-6b57-434e-a50a-308e99838872.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/presentations\/building-presenting-slide-decks-rst2pdf\">given a presentation about how I create presentations<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/presentations\/building-presenting-slide-decks-rst2pdf\">given a presentation about how I create presentations<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/presentations\/building-presenting-slide-decks-rst2pdf\">given a presentation about how I create presentations<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "83515e94d744b93f13eb7b8a56283bcc",
             "target_type": "feeds_feed",
diff --git a/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json b/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json
index 356456bf1..eb54bd6df 100644
--- a/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json
+++ b/content/node.f451e001-95a4-4c6c-94e0-cdbcda175b7b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Today, I released <a href=\"/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=\"/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        ",
+            "value": "\n          <p>Today, I released <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Today, I released <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cfe4233208f6139cd05fc4319defd268",
             "target_type": "feeds_feed",
diff --git a/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json b/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json
index 1dbde9541..693cdc3d6 100644
--- a/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json
+++ b/content/node.f4845b86-e79e-4382-8d78-2376221f9324.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "cab67b9a1e9754bab69a7eb6e764fc33",
             "target_type": "feeds_feed",
diff --git a/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json b/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json
index a9463bdbd..26bd17646 100644
--- a/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json
+++ b/content/node.f4b83f92-eda0-4174-a9e1-45a94d97fb05.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b8c389b3b092927696ab5949cecfe240",
             "target_type": "feeds_feed",
diff --git a/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json b/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json
index a4c79a0de..40f8367c0 100644
--- a/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json
+++ b/content/node.f4bd3e6c-94cf-4c81-bf3a-63aa743a6639.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f974bdb7342e7a84aac0ceb4a74dbdfa",
             "target_type": "feeds_feed",
diff --git a/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json b/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json
index 88ac2969a..cfa16c7e9 100644
--- a/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json
+++ b/content/node.f4e48486-b923-43bd-a250-d6db2aeb9411.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2306bfa479659b451bdcfa4124aac8ed",
             "target_type": "feeds_feed",
diff --git a/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json b/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json
index 3fb331924..bcd332d01 100644
--- a/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json
+++ b/content/node.f4ef1ee9-e2f9-42ff-a210-f0e2ce9aab72.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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=\"/team-coaching\">availability for team coaching<\/a>. I'll show you how!<\/p>\n\n        ",
+            "value": "\n          <p><a href=\"\/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=\"\/team-coaching\">availability for team coaching<\/a>. I'll show you how!<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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=\"/team-coaching\">availability for team coaching<\/a>. I'll show you how!<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d436cc2ce8cace5ee48ba43b332aee65",
             "target_type": "feeds_feed",
diff --git a/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json b/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json
index 598c0ef80..9308913e6 100644
--- a/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json
+++ b/content/node.f5117c12-30f6-4bb7-8e7d-32210d6d278e.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f8b9fce72ec35d462c229ed98873a255",
             "target_type": "feeds_feed",
diff --git a/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json b/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json
index acf59c23e..533f1256e 100644
--- a/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json
+++ b/content/node.f529894e-5912-4e77-91a3-d78b9cbf2584.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b0f5d618c19973d6f434cb0ac0614fdb",
             "target_type": "feeds_feed",
diff --git a/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json b/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json
index afa4dbe55..3ce985671 100644
--- a/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json
+++ b/content/node.f5a54b2e-58c3-45e8-8e0f-00fd61db9f27.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "0b974200c82916119ed21b25b854c421",
             "target_type": "feeds_feed",
diff --git a/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json b/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json
index de0801a35..5568c2ae2 100644
--- a/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json
+++ b/content/node.f5f4ce80-df89-4a85-ba7f-5aa819e9a4d7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9266f4bfd35bc443765c6c434bc5975e",
             "target_type": "feeds_feed",
diff --git a/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json b/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json
index 0cc492a3d..c2db77c50 100644
--- a/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json
+++ b/content/node.f6a3faae-6a4e-478d-9a81-95fb87ab7d47.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8aa785b28b32f4d7c1b6db80b6b763a2",
             "target_type": "feeds_feed",
diff --git a/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json b/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json
index f1d3b79d7..bc83d4d15 100644
--- a/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json
+++ b/content/node.f722e13d-4831-4153-9ba1-0243c3387b8c.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "d1416da5c89de0128a5e492e9ddafdfb",
             "target_type": "feeds_feed",
diff --git a/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json b/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json
index 5dbea5330..5df496915 100644
--- a/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json
+++ b/content/node.f72f7027-2ca5-4473-a8f1-2047d8b400fd.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7648009a474298b1a14504ba7a413f7e",
             "target_type": "feeds_feed",
diff --git a/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json b/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json
index 5bbdab135..891355ccf 100644
--- a/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json
+++ b/content/node.f7411fd1-46e2-4056-be8c-89475875f768.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ce828fb0f1512107c9cbf2309c3d5b96",
             "target_type": "feeds_feed",
diff --git a/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json b/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json
index b83c0f9d4..1e5c580bf 100644
--- a/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json
+++ b/content/node.f78a64e6-14a7-4654-95ab-04b1d1bb7318.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "07d86990b8ff8b2156a15058bc92d8e4",
             "target_type": "feeds_feed",
diff --git a/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json b/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json
index 428ea2aaa..520d18715 100644
--- a/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json
+++ b/content/node.f86b9901-80da-4765-aa94-3bf6025efde5.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/presentations\/sculpin\">generated by Sculpin<\/a> but there are some pages generated by Tome - <a href=\"/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=\"/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        ",
+            "value": "\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=\"\/presentations\/sculpin\">generated by Sculpin<\/a> but there are some pages generated by Tome - <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "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=\"/presentations\/sculpin\">generated by Sculpin<\/a> but there are some pages generated by Tome - <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "8afd6c68260de0b67d4d42f8c66d87b0",
             "target_type": "feeds_feed",
diff --git a/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json b/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json
index 9be1eb4f4..0c26d743a 100644
--- a/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json
+++ b/content/node.f8f9967c-cb22-4c57-b68d-629ca40f3d90.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e547ef3248356cce84c15e924b59db53",
             "target_type": "feeds_feed",
diff --git a/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json b/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json
index 183a7f421..f878243c0 100644
--- a/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json
+++ b/content/node.f98589c7-10e8-4903-b801-f2a42135b190.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "df6cac0e06b78b0e457c5d6f45c51e64",
             "target_type": "feeds_feed",
diff --git a/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json b/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json
index 68f2c0a32..7c3d95ae0 100644
--- a/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json
+++ b/content/node.f9a1b695-bf65-4098-abce-c8593a427731.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e82c83bb7af903eba4da99cc5f669d1d",
             "target_type": "feeds_feed",
diff --git a/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json b/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json
index 2b9141745..956e05b5c 100644
--- a/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json
+++ b/content/node.f9b4a966-4ff8-4ecb-b832-46232d30d9ff.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "2c51bf00b628c3b44ddf21e8b65a3ba1",
             "target_type": "feeds_feed",
diff --git a/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json b/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json
index d2b4291b2..5dac2fb30 100644
--- a/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json
+++ b/content/node.fa30b239-baa9-46ec-9ea2-4914280dd13b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>This week, I spoke with Eirik Morland again on the <a href=\"/podcast\">Beyond Blocks podcast<\/a> about recent improvements to violinist.io, such as team\/multi-user subscriptions.<\/p>\n\n<p><a href=\"/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=\"/podcast\/8-eirik-morland-violinist\">Listen to the first episode with Eirik<\/a>.<\/p>\n\n        ",
+            "value": "\n          <p>This week, I spoke with Eirik Morland again on the <a href=\"\/podcast\">Beyond Blocks podcast<\/a> about recent improvements to violinist.io, such as team\/multi-user subscriptions.<\/p>\n\n<p><a href=\"\/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=\"\/podcast\/8-eirik-morland-violinist\">Listen to the first episode with Eirik<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "processed": "\n          <p>This week, I spoke with Eirik Morland again on the <a href=\"/podcast\">Beyond Blocks podcast<\/a> about recent improvements to violinist.io, such as team\/multi-user subscriptions.<\/p>\n\n<p><a href=\"/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=\"/podcast\/8-eirik-morland-violinist\">Listen to the first episode with Eirik<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9fd4322d892e0fd4d10bb06c6e4377b1",
             "target_type": "feeds_feed",
diff --git a/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json b/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json
index 8079c8f37..5c8bd6a9e 100644
--- a/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json
+++ b/content/node.fa7b57ee-9af5-49ce-9522-66d54642e219.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "bdc8ca32430b3dba88a75ebc24a7def1",
             "target_type": "feeds_feed",
diff --git a/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json b/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json
index 8025857f3..771447d23 100644
--- a/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json
+++ b/content/node.fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "5a98269cbc13fc0777b9ad007d4e327d",
             "target_type": "feeds_feed",
diff --git a/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json b/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json
index 1e4026fa1..7729e1e68 100644
--- a/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json
+++ b/content/node.faff03ba-71b2-4b4b-a107-9e7f499eeefd.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/daily\/2024\/08\/06\/computers-dont-care\">optimise for readability<\/a>.<\/p>\n\n        ",
+            "value": "\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=\"\/daily\/2024\/08\/06\/computers-dont-care\">optimise for readability<\/a>.<\/p>\n\n        ",
             "format": "full_html",
-            "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=\"/daily\/2024\/08\/06\/computers-dont-care\">optimise for readability<\/a>.<\/p>\n\n        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "ccf8c14e44b64bd2a73b57d71ad81ca6",
             "target_type": "feeds_feed",
diff --git a/content/node.fb679f64-e559-4319-9a36-b508bc870415.json b/content/node.fb679f64-e559-4319-9a36-b508bc870415.json
index 24434a3fd..31af8628f 100644
--- a/content/node.fb679f64-e559-4319-9a36-b508bc870415.json
+++ b/content/node.fb679f64-e559-4319-9a36-b508bc870415.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "7ea5ffe7f98df1811de34c43a7caca75",
             "target_type": "feeds_feed",
diff --git a/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json b/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json
index 2ff4e4479..d586e2e71 100644
--- a/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json
+++ b/content/node.fb85bcd0-833b-4e23-bab7-4e9ae86075df.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Last week, Mike Karthauser - Senior Software Developer at Huboo - <a href=\"/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        ",
+            "value": "\n          <p>Last week, Mike Karthauser - Senior Software Developer at Huboo - <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Last week, Mike Karthauser - Senior Software Developer at Huboo - <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e88c0190551b13355521158f21adce62",
             "target_type": "feeds_feed",
diff --git a/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json b/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json
index daf429932..9675f0587 100644
--- a/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json
+++ b/content/node.fb950c25-8deb-439d-a5c8-1a24b64cd5be.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9298791e0940f0ff8c997aae39008767",
             "target_type": "feeds_feed",
diff --git a/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json b/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json
index fdeef2fd5..033ab091d 100644
--- a/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json
+++ b/content/node.fba9e05d-92e9-4699-a6ad-dafae26a1670.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "f5036af047c759046d5ac11623982bad",
             "target_type": "feeds_feed",
diff --git a/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json b/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json
index fb332af57..742cb8406 100644
--- a/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json
+++ b/content/node.fbc1e9f3-0957-4dfb-b273-f3ed4a6c40f7.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "fd83c2fde1dc9ee8eddd826af1ec88b8",
             "target_type": "feeds_feed",
diff --git a/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json b/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json
index 616366945..e3467fad0 100644
--- a/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json
+++ b/content/node.fcd0906c-5337-4f6e-8938-c71c2fe672d8.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "9913b8499ed48ffb98e6df624b87e485",
             "target_type": "feeds_feed",
diff --git a/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json b/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json
index eb8d87bfa..174380ad7 100644
--- a/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json
+++ b/content/node.fdf6ccbc-7e57-4767-8c8d-7db48b2874cc.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e964b8ae6d3a589e9ec7419ffe0d83bf",
             "target_type": "feeds_feed",
diff --git a/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json b/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json
index 0d4c8225e..c1948becf 100644
--- a/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json
+++ b/content/node.fe080d63-d163-4e3f-9efc-4ec3c8f9c03c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>After writing about <a href=\"/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=\"/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        ",
+            "value": "\n          <p>After writing about <a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>After writing about <a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3a10f1e0d9065c216ecf8696911485c8",
             "target_type": "feeds_feed",
diff --git a/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json b/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json
index b3243d4c0..91824e3bc 100644
--- a/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json
+++ b/content/node.fe168e9f-37bf-4cb4-b42d-1db79938223b.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Today, I met my new mentee from the Drupal Career Online program.<\/p>\n\n<p><a href=\"/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=\"/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        ",
+            "value": "\n          <p>Today, I met my new mentee from the Drupal Career Online program.<\/p>\n\n<p><a href=\"\/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=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Today, I met my new mentee from the Drupal Career Online program.<\/p>\n\n<p><a href=\"/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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "51f79d0262a9b959e58c9e60f716db6c",
             "target_type": "feeds_feed",
diff --git a/content/node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0.json b/content/node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0.json
index 5176eec58..33798b56e 100644
--- a/content/node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0.json
+++ b/content/node.fe259dd8-b373-43cb-bab1-81c3f8c8f5a0.json
@@ -104,5 +104,6 @@
             "target_type": "taxonomy_term",
             "target_uuid": "4c72b65c-9b3c-4c8a-8826-9849ae4f498d"
         }
-    ]
+    ],
+    "field_topic": []
 }
\ 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 092ab5770..12f67742e 100644
--- a/content/node.fe407991-a896-410c-9223-51a7ad43d4d2.json
+++ b/content/node.fe407991-a896-410c-9223-51a7ad43d4d2.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p><a href=\"/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        ",
+            "value": "\n          <p><a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p><a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "3659e1bc52d94b014aa5474c24745dd2",
             "target_type": "feeds_feed",
diff --git a/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json b/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json
index 00e288366..5ab6467f5 100644
--- a/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json
+++ b/content/node.fe51bb0f-fbce-4823-be30-c4b3aa4a296c.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "b60d151157449fcffc7aa384bd9a81c7",
             "target_type": "feeds_feed",
diff --git a/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json b/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json
index eb6290a15..093296e7a 100644
--- a/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json
+++ b/content/node.fe66604f-b58a-48e7-8c42-5b7b3ce5cb45.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "602cd7fb7a99f9a56adc2966737aa2ab",
             "target_type": "feeds_feed",
diff --git a/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json b/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json
index 62a9650d6..8780a9e72 100644
--- a/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json
+++ b/content/node.fe815eab-027d-49db-afd1-e4a21387b2fe.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\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=\"/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        ",
+            "value": "\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=\"\/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        ",
             "format": "full_html",
-            "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=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "e858790e868fcce3898b265b59a58a8d",
             "target_type": "feeds_feed",
diff --git a/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json b/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json
index 61cee0c51..c023c0886 100644
--- a/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json
+++ b/content/node.ff8d6ab3-e544-4f38-9d76-7206e7e4d9fe.json
@@ -90,7 +90,7 @@
     ],
     "feeds_item": [
         {
-            "imported": "1970-01-01T00:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "dd3142bbe9347b6efceca91355af4c1e",
             "target_type": "feeds_feed",
diff --git a/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json b/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json
index 4851a0ea2..f091d43d8 100644
--- a/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json
+++ b/content/node.ffa93a1b-f239-4c0a-9f34-50cd6532f353.json
@@ -82,15 +82,15 @@
     ],
     "body": [
         {
-            "value": "\n          <p>Before fixing <a href=\"/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        ",
+            "value": "\n          <p>Before fixing <a href=\"\/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        ",
             "format": "full_html",
-            "processed": "\n          <p>Before fixing <a href=\"/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        ",
+            "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:33:45+00:00",
+            "imported": "1970-01-01T00:32:50+00:00",
             "guid": null,
             "hash": "abcc748af8e6e888fd2ed7c8b02d7911",
             "target_type": "feeds_feed",
diff --git a/content/path_alias.05c8d8d4-a8c1-4956-9348-80367df00108.json b/content/path_alias.05c8d8d4-a8c1-4956-9348-80367df00108.json
new file mode 100644
index 000000000..8f94c45a7
--- /dev/null
+++ b/content/path_alias.05c8d8d4-a8c1-4956-9348-80367df00108.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "05c8d8d4-a8c1-4956-9348-80367df00108"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/872ee6d1-ddeb-4b85-a443-c5cf2d9f864d"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/automated-testing-lightning-talk"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.0ccd4c97-8c36-4030-bd02-d1a24eace52b.json b/content/path_alias.0ccd4c97-8c36-4030-bd02-d1a24eace52b.json
new file mode 100644
index 000000000..2bd1cc76e
--- /dev/null
+++ b/content/path_alias.0ccd4c97-8c36-4030-bd02-d1a24eace52b.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "0ccd4c97-8c36-4030-bd02-d1a24eace52b"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/4eec6b8d-0376-4b5f-84a9-cdc2fca2395e"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/getting-your-data-into-drupal-8"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.1013ac37-0c26-4453-9529-d9678bea6bb4.json b/content/path_alias.1013ac37-0c26-4453-9529-d9678bea6bb4.json
new file mode 100644
index 000000000..fc7f8ebbf
--- /dev/null
+++ b/content/path_alias.1013ac37-0c26-4453-9529-d9678bea6bb4.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "1013ac37-0c26-4453-9529-d9678bea6bb4"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/c88b1c71-9bf2-4055-820b-6f9377ed31af"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/dancing-for-drupal"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.193a146a-4b87-4cb7-8139-f612fb3656ef.json b/content/path_alias.193a146a-4b87-4cb7-8139-f612fb3656ef.json
new file mode 100644
index 000000000..c0f3c4ebd
--- /dev/null
+++ b/content/path_alias.193a146a-4b87-4cb7-8139-f612fb3656ef.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "193a146a-4b87-4cb7-8139-f612fb3656ef"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/4d1aa9fa-091a-425a-941a-102e6f17e768"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupal-8-rejoining-the-herd"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.1ccfde63-a91b-48aa-a890-5a5891815d0d.json b/content/path_alias.1ccfde63-a91b-48aa-a890-5a5891815d0d.json
new file mode 100644
index 000000000..8047ae56c
--- /dev/null
+++ b/content/path_alias.1ccfde63-a91b-48aa-a890-5a5891815d0d.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "1ccfde63-a91b-48aa-a890-5a5891815d0d"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/5a9c3a99-84f4-4dc3-8ddc-d05e0469f9b9"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/homelab"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.1df69675-92fc-4238-b3ee-57263243e395.json b/content/path_alias.1df69675-92fc-4238-b3ee-57263243e395.json
new file mode 100644
index 000000000..7ff06f41e
--- /dev/null
+++ b/content/path_alias.1df69675-92fc-4238-b3ee-57263243e395.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "1df69675-92fc-4238-b3ee-57263243e395"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/e83b2be0-560c-43a0-b22c-4d11898e2591"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/introduction-to-mob-programming"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.224b7887-6730-4987-b23c-7b4f61f1b549.json b/content/path_alias.224b7887-6730-4987-b23c-7b4f61f1b549.json
new file mode 100644
index 000000000..233e8ffe7
--- /dev/null
+++ b/content/path_alias.224b7887-6730-4987-b23c-7b4f61f1b549.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "224b7887-6730-4987-b23c-7b4f61f1b549"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/9b87c047-0a3b-4a66-8ea8-f8a1981f686c"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupalorg-2015"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.24b6f8bc-e00b-498e-9a03-754f85e4ee0b.json b/content/path_alias.24b6f8bc-e00b-498e-9a03-754f85e4ee0b.json
new file mode 100644
index 000000000..0b4a1b2c1
--- /dev/null
+++ b/content/path_alias.24b6f8bc-e00b-498e-9a03-754f85e4ee0b.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "24b6f8bc-e00b-498e-9a03-754f85e4ee0b"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/7646b8ce-4388-4b19-9ef6-73439442c359"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/automated-testing-test-driven-development-drupal-8"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.25233bfe-544a-4842-87d7-afcd27779476.json b/content/path_alias.25233bfe-544a-4842-87d7-afcd27779476.json
new file mode 100644
index 000000000..43326dde9
--- /dev/null
+++ b/content/path_alias.25233bfe-544a-4842-87d7-afcd27779476.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "25233bfe-544a-4842-87d7-afcd27779476"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/622123fa-d820-4372-a68d-a049f9ceb348"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupal-ldap-module"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.289c6203-bf95-4f18-a285-482337c510b7.json b/content/path_alias.289c6203-bf95-4f18-a285-482337c510b7.json
new file mode 100644
index 000000000..91b999552
--- /dev/null
+++ b/content/path_alias.289c6203-bf95-4f18-a285-482337c510b7.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "289c6203-bf95-4f18-a285-482337c510b7"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/9478a73a-b12b-426e-abcf-f007d544d244"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupal-8-php-libraries-drupalorg-api"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.2bea11d0-9783-4f4d-b8af-cb2ae20ea43b.json b/content/path_alias.2bea11d0-9783-4f4d-b8af-cb2ae20ea43b.json
new file mode 100644
index 000000000..da2770a51
--- /dev/null
+++ b/content/path_alias.2bea11d0-9783-4f4d-b8af-cb2ae20ea43b.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "2bea11d0-9783-4f4d-b8af-cb2ae20ea43b"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/dbb09dcc-ad50-4ec0-9567-1d799292107f"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/out-of-the-box-initiative-update"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.37bcce63-122c-4aa3-ade9-fa96b9f24e22.json b/content/path_alias.37bcce63-122c-4aa3-ade9-fa96b9f24e22.json
new file mode 100644
index 000000000..2e933b6c5
--- /dev/null
+++ b/content/path_alias.37bcce63-122c-4aa3-ade9-fa96b9f24e22.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "37bcce63-122c-4aa3-ade9-fa96b9f24e22"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/67967073-f8ca-4253-b806-a570806f18ee"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/goodbye-drush-make-hello-composer"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.3c27c0fe-1a53-4073-92c0-edded050d127.json b/content/path_alias.3c27c0fe-1a53-4073-92c0-edded050d127.json
new file mode 100644
index 000000000..10a3db513
--- /dev/null
+++ b/content/path_alias.3c27c0fe-1a53-4073-92c0-edded050d127.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "3c27c0fe-1a53-4073-92c0-edded050d127"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/3424c5e4-6b60-4ba4-b9f1-37b964cbcb91"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupal-8-module-development"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.3deea84a-b1d1-4a20-8fe6-ce809fb116c4.json b/content/path_alias.3deea84a-b1d1-4a20-8fe6-ce809fb116c4.json
new file mode 100644
index 000000000..b0d1f46c5
--- /dev/null
+++ b/content/path_alias.3deea84a-b1d1-4a20-8fe6-ce809fb116c4.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "3deea84a-b1d1-4a20-8fe6-ce809fb116c4"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/32df4c3d-0719-49eb-8dde-0d04ea746de8"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/test-drive-twig-with-sculpin"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.458f6c04-7cf5-4011-a386-a240d552ad0e.json b/content/path_alias.458f6c04-7cf5-4011-a386-a240d552ad0e.json
new file mode 100644
index 000000000..ad7737b65
--- /dev/null
+++ b/content/path_alias.458f6c04-7cf5-4011-a386-a240d552ad0e.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "458f6c04-7cf5-4011-a386-a240d552ad0e"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/720227fb-2539-4f99-8a3a-097ad7fbea5b"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/tdd-test-driven-drupal"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.46cf208b-0fc4-429f-9787-fbdf70da76be.json b/content/path_alias.46cf208b-0fc4-429f-9787-fbdf70da76be.json
new file mode 100644
index 000000000..0dfa128ad
--- /dev/null
+++ b/content/path_alias.46cf208b-0fc4-429f-9787-fbdf70da76be.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "46cf208b-0fc4-429f-9787-fbdf70da76be"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/91228b97-e4df-43c9-8f1e-6aaa6998b6c7"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/communities-contribution"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.56615246-6c0a-4995-b2e5-05410aeb9f85.json b/content/path_alias.56615246-6c0a-4995-b2e5-05410aeb9f85.json
new file mode 100644
index 000000000..cf3c666d9
--- /dev/null
+++ b/content/path_alias.56615246-6c0a-4995-b2e5-05410aeb9f85.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "56615246-6c0a-4995-b2e5-05410aeb9f85"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/6d9734c9-2165-4b6c-8617-1dcb5af116bb"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/modern-drupal-development-with-composer"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.5a0eee15-1d56-43d0-8539-3bd406e48749.json b/content/path_alias.5a0eee15-1d56-43d0-8539-3bd406e48749.json
new file mode 100644
index 000000000..3bc014b2d
--- /dev/null
+++ b/content/path_alias.5a0eee15-1d56-43d0-8539-3bd406e48749.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "5a0eee15-1d56-43d0-8539-3bd406e48749"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/ef95ec60-773e-44ce-a0aa-5e009112f8f4"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupal-vm-generator"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.5aa1fdcc-aaaf-4b96-98d9-a76945ca4d3b.json b/content/path_alias.5aa1fdcc-aaaf-4b96-98d9-a76945ca4d3b.json
new file mode 100644
index 000000000..348b9a295
--- /dev/null
+++ b/content/path_alias.5aa1fdcc-aaaf-4b96-98d9-a76945ca4d3b.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "5aa1fdcc-aaaf-4b96-98d9-a76945ca4d3b"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/d31d81e0-5591-424a-b89f-e38a0b35ff25"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/rst2pdf"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.5f139ec9-b1ab-4613-b00d-19cc03fd1d6f.json b/content/path_alias.5f139ec9-b1ab-4613-b00d-19cc03fd1d6f.json
new file mode 100644
index 000000000..149100fc4
--- /dev/null
+++ b/content/path_alias.5f139ec9-b1ab-4613-b00d-19cc03fd1d6f.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "5f139ec9-b1ab-4613-b00d-19cc03fd1d6f"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/b3371f53-7540-46da-b9dd-0247c0042c60"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/soar-with-tailwind-css"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.5f1f98b4-b422-4633-ba2d-1036ad9bbefb.json b/content/path_alias.5f1f98b4-b422-4633-ba2d-1036ad9bbefb.json
new file mode 100644
index 000000000..546a5fe5d
--- /dev/null
+++ b/content/path_alias.5f1f98b4-b422-4633-ba2d-1036ad9bbefb.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "5f1f98b4-b422-4633-ba2d-1036ad9bbefb"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/f9b17889-2531-4e1e-b120-a0f0e27fed83"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/so-what-is-this-drupal-thing"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.603fe8b8-cabd-44e3-8914-949f8d58f59a.json b/content/path_alias.603fe8b8-cabd-44e3-8914-949f8d58f59a.json
new file mode 100644
index 000000000..ccf1ae009
--- /dev/null
+++ b/content/path_alias.603fe8b8-cabd-44e3-8914-949f8d58f59a.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "603fe8b8-cabd-44e3-8914-949f8d58f59a"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/4229ad32-8ef7-4315-ad6d-c7fea0157f7f"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/it-all-started-with-a-patch"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.76645bbb-c487-499f-a485-e8a3cd431539.json b/content/path_alias.76645bbb-c487-499f-a485-e8a3cd431539.json
new file mode 100644
index 000000000..120b8304c
--- /dev/null
+++ b/content/path_alias.76645bbb-c487-499f-a485-e8a3cd431539.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "76645bbb-c487-499f-a485-e8a3cd431539"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/261e86dc-ffbb-4274-a61a-8ddd9fadff5e"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/git-flow"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.799ccead-b473-474a-9131-d0c36db8c194.json b/content/path_alias.799ccead-b473-474a-9131-d0c36db8c194.json
new file mode 100644
index 000000000..9dcf0daf6
--- /dev/null
+++ b/content/path_alias.799ccead-b473-474a-9131-d0c36db8c194.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "799ccead-b473-474a-9131-d0c36db8c194"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/00e9d07f-479d-4a4d-8a13-ad6cf44c0454"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/examples"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.8c4d45a2-b6d5-4567-bf3e-220bd8bfb393.json b/content/path_alias.8c4d45a2-b6d5-4567-bf3e-220bd8bfb393.json
new file mode 100644
index 000000000..cd6255c8f
--- /dev/null
+++ b/content/path_alias.8c4d45a2-b6d5-4567-bf3e-220bd8bfb393.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "8c4d45a2-b6d5-4567-bf3e-220bd8bfb393"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/29a792d3-f83c-4802-95cf-ce39109dd96a"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/using-illuminate-collections-outside-laravel"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.9a227a05-5717-4b6a-9eb8-3ab05d1e8077.json b/content/path_alias.9a227a05-5717-4b6a-9eb8-3ab05d1e8077.json
new file mode 100644
index 000000000..0c44df0d6
--- /dev/null
+++ b/content/path_alias.9a227a05-5717-4b6a-9eb8-3ab05d1e8077.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "9a227a05-5717-4b6a-9eb8-3ab05d1e8077"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/fd961f16-2935-474b-af7e-99885bd38a5b"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupal-vm-meet-symfony-console"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.a1b87f39-0fbb-46dc-b81a-1e0f11f942ac.json b/content/path_alias.a1b87f39-0fbb-46dc-b81a-1e0f11f942ac.json
new file mode 100644
index 000000000..db1841d82
--- /dev/null
+++ b/content/path_alias.a1b87f39-0fbb-46dc-b81a-1e0f11f942ac.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "a1b87f39-0fbb-46dc-b81a-1e0f11f942ac"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/d46b09ba-3534-422c-b897-05619490a269"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/deploying-drupal-fabric"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.abdc82a8-fbb9-412c-bb91-e0ca0566e8ef.json b/content/path_alias.abdc82a8-fbb9-412c-bb91-e0ca0566e8ef.json
new file mode 100644
index 000000000..08963f8ab
--- /dev/null
+++ b/content/path_alias.abdc82a8-fbb9-412c-bb91-e0ca0566e8ef.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "abdc82a8-fbb9-412c-bb91-e0ca0566e8ef"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/7cc21bad-5b2e-450c-86b4-19b79f4b21c1"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/deploying-php-fabric"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.b7908c26-3b98-444f-968c-7cb5be66d88c.json b/content/path_alias.b7908c26-3b98-444f-968c-7cb5be66d88c.json
new file mode 100644
index 000000000..a8bad5ffa
--- /dev/null
+++ b/content/path_alias.b7908c26-3b98-444f-968c-7cb5be66d88c.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "b7908c26-3b98-444f-968c-7cb5be66d88c"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/11ff7528-5853-4557-bab4-190e6edab4a5"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/deploying-php-ansible-ansistrano"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.b7e67401-20ff-46b7-89e6-0022c6bd1e35.json b/content/path_alias.b7e67401-20ff-46b7-89e6-0022c6bd1e35.json
new file mode 100644
index 000000000..33423d989
--- /dev/null
+++ b/content/path_alias.b7e67401-20ff-46b7-89e6-0022c6bd1e35.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "b7e67401-20ff-46b7-89e6-0022c6bd1e35"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/e2353e18-0a03-4448-a8db-728dbd4146e8"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drupal-8"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.be37fc6c-bf65-4b4d-b652-84d163b0d666.json b/content/path_alias.be37fc6c-bf65-4b4d-b652-84d163b0d666.json
new file mode 100644
index 000000000..18e32c432
--- /dev/null
+++ b/content/path_alias.be37fc6c-bf65-4b4d-b652-84d163b0d666.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "be37fc6c-bf65-4b4d-b652-84d163b0d666"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/67e872b0-38b9-4bf8-9ca2-82b6e2cd488b"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/working-with-workspace"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.bf67d703-6cbb-4272-b81c-2ab8ca1dd96b.json b/content/path_alias.bf67d703-6cbb-4272-b81c-2ab8ca1dd96b.json
new file mode 100644
index 000000000..5f362dc77
--- /dev/null
+++ b/content/path_alias.bf67d703-6cbb-4272-b81c-2ab8ca1dd96b.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "bf67d703-6cbb-4272-b81c-2ab8ca1dd96b"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/478e9266-742d-4c7d-92fb-0f6797b0da9e"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/about-drupal-association"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.c0bde3ce-d3c3-4bd6-b2a1-064b535ca308.json b/content/path_alias.c0bde3ce-d3c3-4bd6-b2a1-064b535ca308.json
new file mode 100644
index 000000000..1e06d0be3
--- /dev/null
+++ b/content/path_alias.c0bde3ce-d3c3-4bd6-b2a1-064b535ca308.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "c0bde3ce-d3c3-4bd6-b2a1-064b535ca308"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/bbdaeb7f-4154-4919-a1e6-1dcc33c3ac87"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/upgrading-your-site-drupal-9"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.c3a908a9-70cd-45f8-b1b8-e9889c8ac645.json b/content/path_alias.c3a908a9-70cd-45f8-b1b8-e9889c8ac645.json
new file mode 100644
index 000000000..f63b3ccde
--- /dev/null
+++ b/content/path_alias.c3a908a9-70cd-45f8-b1b8-e9889c8ac645.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "c3a908a9-70cd-45f8-b1b8-e9889c8ac645"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/d60d49f4-3d4f-4dd1-bcb8-1e75f74032c1"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/building-build-configs"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.cf11b483-34f2-4e6b-9e28-75ea679c1a55.json b/content/path_alias.cf11b483-34f2-4e6b-9e28-75ea679c1a55.json
new file mode 100644
index 000000000..ffdf89239
--- /dev/null
+++ b/content/path_alias.cf11b483-34f2-4e6b-9e28-75ea679c1a55.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "cf11b483-34f2-4e6b-9e28-75ea679c1a55"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/93689f20-8355-413a-8c23-5096802fbd65"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/sculpin"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.d266b885-54c2-4d7a-89a3-828fb7f8ff88.json b/content/path_alias.d266b885-54c2-4d7a-89a3-828fb7f8ff88.json
new file mode 100644
index 000000000..65f087d40
--- /dev/null
+++ b/content/path_alias.d266b885-54c2-4d7a-89a3-828fb7f8ff88.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "d266b885-54c2-4d7a-89a3-828fb7f8ff88"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/209ce05d-6831-47b2-b069-c4e31f698885"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/reading-college"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.dac815a5-e23f-4f3b-a249-b9391d5ed4d0.json b/content/path_alias.dac815a5-e23f-4f3b-a249-b9391d5ed4d0.json
new file mode 100644
index 000000000..2bfea9d16
--- /dev/null
+++ b/content/path_alias.dac815a5-e23f-4f3b-a249-b9391d5ed4d0.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "dac815a5-e23f-4f3b-a249-b9391d5ed4d0"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/2b4c5ae7-3754-44ae-a0c0-40a24a64fc2f"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/configuring-all-the-things-drupal-8"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.e16afff1-7e4f-486d-8c15-9daaa90ae2c2.json b/content/path_alias.e16afff1-7e4f-486d-8c15-9daaa90ae2c2.json
new file mode 100644
index 000000000..ec18dc454
--- /dev/null
+++ b/content/path_alias.e16afff1-7e4f-486d-8c15-9daaa90ae2c2.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "e16afff1-7e4f-486d-8c15-9daaa90ae2c2"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/76b39ff6-103e-4ebf-b4c2-de6c369a7a65"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/taking-flight-with-tailwind-css"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.e2b23961-024e-4223-94db-5a9cb626bcc3.json b/content/path_alias.e2b23961-024e-4223-94db-5a9cb626bcc3.json
new file mode 100644
index 000000000..79fccdc8e
--- /dev/null
+++ b/content/path_alias.e2b23961-024e-4223-94db-5a9cb626bcc3.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "e2b23961-024e-4223-94db-5a9cb626bcc3"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/28e7dab2-8990-43ca-8f69-16608eae051f"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/drush-make-drupalbristol"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.e64f35a6-b476-448c-8043-171e772aabca.json b/content/path_alias.e64f35a6-b476-448c-8043-171e772aabca.json
new file mode 100644
index 000000000..522e2b0d9
--- /dev/null
+++ b/content/path_alias.e64f35a6-b476-448c-8043-171e772aabca.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "e64f35a6-b476-448c-8043-171e772aabca"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/00cbe903-afbd-4074-867d-4499873f3ec9"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/working-without-workspace"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.e7160989-275c-4054-a4f2-2c0efce42985.json b/content/path_alias.e7160989-275c-4054-a4f2-2c0efce42985.json
new file mode 100644
index 000000000..355f43748
--- /dev/null
+++ b/content/path_alias.e7160989-275c-4054-a4f2-2c0efce42985.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "e7160989-275c-4054-a4f2-2c0efce42985"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/3e86a978-80ed-4e0d-9e93-93001f1d52ad"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/decoupling-drupal-vuejs"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.f8a5a912-19db-4c22-9157-4583e9f356c8.json b/content/path_alias.f8a5a912-19db-4c22-9157-4583e9f356c8.json
new file mode 100644
index 000000000..113385387
--- /dev/null
+++ b/content/path_alias.f8a5a912-19db-4c22-9157-4583e9f356c8.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "f8a5a912-19db-4c22-9157-4583e9f356c8"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/8db50e55-72a9-4957-97c7-8a5ae127eeaa"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/presentations\/things-you-should-know-about-php"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95.json b/content/taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95.json
index a97dbadfc..69773972e 100644
--- a/content/taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95.json
+++ b/content/taxonomy_term.0a8e0788-6709-46c0-ab72-f796ee96ad95.json
@@ -33,7 +33,13 @@
             "value": "Ed Crompton"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43.json b/content/taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43.json
index a773dd977..6b749047b 100644
--- a/content/taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43.json
+++ b/content/taxonomy_term.189f1378-871c-4e2a-93b9-1096fd273c43.json
@@ -33,7 +33,13 @@
             "value": "Chris Ballard"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf.json b/content/taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf.json
index b5c66144b..6442635bf 100644
--- a/content/taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf.json
+++ b/content/taxonomy_term.1902938a-e92a-4ee7-9129-fe3f3ae41bcf.json
@@ -33,7 +33,13 @@
             "value": "Dave Liddament"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df.json b/content/taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df.json
index 45ebfab42..6166df00b 100644
--- a/content/taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df.json
+++ b/content/taxonomy_term.2fb2991f-8bac-4335-a8cd-a5c6edb158df.json
@@ -33,7 +33,13 @@
             "value": "Nick Janetakis"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47.json b/content/taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47.json
index 049a695f5..be4681b65 100644
--- a/content/taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47.json
+++ b/content/taxonomy_term.306b315a-03c4-4f06-a396-cf0906676d47.json
@@ -33,7 +33,13 @@
             "value": "Luke McCormick"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
@@ -61,7 +67,7 @@
     ],
     "path": [
         {
-            "alias": "",
+            "alias": null,
             "pid": null,
             "langcode": "en"
         }
diff --git a/content/taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b.json b/content/taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b.json
index 43fbfa3e6..181c79bc1 100644
--- a/content/taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b.json
+++ b/content/taxonomy_term.317d48d3-4d85-450e-8358-f495d503b41b.json
@@ -33,7 +33,13 @@
             "value": "Eirik Morland"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af.json b/content/taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af.json
index 4ec590f23..b3ac61a76 100644
--- a/content/taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af.json
+++ b/content/taxonomy_term.33c14bb8-58a2-4f98-bcf1-658dce47a1af.json
@@ -33,7 +33,13 @@
             "value": "Emma Horrell"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e.json b/content/taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e.json
index 15fc1d211..5758a93b7 100644
--- a/content/taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e.json
+++ b/content/taxonomy_term.3b55c7cc-9994-42fd-aece-9c52889b875e.json
@@ -33,7 +33,13 @@
             "value": "Rob Allen"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2.json b/content/taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2.json
index 96de8db1f..22a4fe220 100644
--- a/content/taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2.json
+++ b/content/taxonomy_term.3e21966a-6812-420b-aca1-0aa641dbb5a2.json
@@ -33,7 +33,13 @@
             "value": "Simon Graham"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4.json b/content/taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4.json
index 202db35f9..f4f699bb0 100644
--- a/content/taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4.json
+++ b/content/taxonomy_term.427b33a7-0a27-458b-8a02-4d6a6780a2e4.json
@@ -33,7 +33,13 @@
             "value": "Dieter Blomme"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6.json b/content/taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6.json
index 8724a5e8b..e91ca88ff 100644
--- a/content/taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6.json
+++ b/content/taxonomy_term.43995889-d61c-4934-b644-52c9d3fee4d6.json
@@ -33,7 +33,13 @@
             "value": "Ryan Szrama"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9.json b/content/taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9.json
index d065e3776..052c27e89 100644
--- a/content/taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9.json
+++ b/content/taxonomy_term.45ff9597-74a6-46d9-91a2-8d6e5b2c28a9.json
@@ -33,7 +33,13 @@
             "value": "Tim Lehnen"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d.json b/content/taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d.json
index 465c964a7..c57478e99 100644
--- a/content/taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d.json
+++ b/content/taxonomy_term.4c72b65c-9b3c-4c8a-8826-9849ae4f498d.json
@@ -33,7 +33,13 @@
             "value": "J\u00fcrgen Haas"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7.json b/content/taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7.json
index 3bda40608..ba7ad2792 100644
--- a/content/taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7.json
+++ b/content/taxonomy_term.6e8c14dc-fa95-4ffa-b6ae-bd28519562f7.json
@@ -33,7 +33,13 @@
             "value": "Mark Conroy"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d.json b/content/taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d.json
index 898b71921..088015645 100644
--- a/content/taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d.json
+++ b/content/taxonomy_term.6f130024-67b6-448c-a780-8fe31d10f94d.json
@@ -33,7 +33,13 @@
             "value": "Niklas Franke"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2.json b/content/taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2.json
index 1612f71e2..650e0b2f6 100644
--- a/content/taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2.json
+++ b/content/taxonomy_term.8bfc82e2-c3c1-4c3b-ad5a-47f5681bcad2.json
@@ -33,7 +33,13 @@
             "value": "Jochen Lillich"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6.json b/content/taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6.json
index 0c4baa0f2..d856233b8 100644
--- a/content/taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6.json
+++ b/content/taxonomy_term.9e99db9e-83af-4d55-9c98-ba53ab2c2ab6.json
@@ -33,7 +33,13 @@
             "value": "George Gordon"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980.json b/content/taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980.json
index 6e71bdadf..8580da89c 100644
--- a/content/taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980.json
+++ b/content/taxonomy_term.a1f48bb9-493b-4f92-b1ac-74152cd6f980.json
@@ -33,7 +33,13 @@
             "value": "Yuri Gerasymov"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09.json b/content/taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09.json
index 8cdb3989e..ed8b49d3c 100644
--- a/content/taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09.json
+++ b/content/taxonomy_term.a6331245-d56d-44dd-9496-936284f1bc09.json
@@ -33,7 +33,13 @@
             "value": "Panagiotis Moutsopoulos"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9.json b/content/taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9.json
index 07e10f9c1..199b540da 100644
--- a/content/taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9.json
+++ b/content/taxonomy_term.b4e262ae-1e39-471f-b5ff-111df3b772d9.json
@@ -33,7 +33,13 @@
             "value": "Jess Archer"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.c0470b91-e700-4602-9e93-07705681d679.json b/content/taxonomy_term.c0470b91-e700-4602-9e93-07705681d679.json
index 0ee697ce5..1bd4ccb5f 100644
--- a/content/taxonomy_term.c0470b91-e700-4602-9e93-07705681d679.json
+++ b/content/taxonomy_term.c0470b91-e700-4602-9e93-07705681d679.json
@@ -33,7 +33,13 @@
             "value": "Ryan Weaver"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32.json b/content/taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32.json
index c2588df14..f879b10ea 100644
--- a/content/taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32.json
+++ b/content/taxonomy_term.cb22fa9d-5b4f-4a48-bb57-8f2f4f010a32.json
@@ -33,7 +33,13 @@
             "value": "Sam Mortenson"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538.json b/content/taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538.json
index c095f4c12..ab9bc67b3 100644
--- a/content/taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538.json
+++ b/content/taxonomy_term.e4c684f2-2c3c-4ca3-a65b-eb7596778538.json
@@ -33,7 +33,13 @@
             "value": "Mike Karthauser"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b.json b/content/taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b.json
index c912be652..5f16318d9 100644
--- a/content/taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b.json
+++ b/content/taxonomy_term.ec064691-4a1e-4a7c-a5f4-0a573286a67b.json
@@ -33,7 +33,13 @@
             "value": "Dan Leech"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f.json b/content/taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f.json
index dd7b12a19..a5ebaa226 100644
--- a/content/taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f.json
+++ b/content/taxonomy_term.f9b1ec5f-2fdb-438c-a266-082a86a6d94f.json
@@ -33,7 +33,13 @@
             "value": "Andy Hoang"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0
diff --git a/content/taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6.json b/content/taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6.json
index f06a39659..3a6cf2b80 100644
--- a/content/taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6.json
+++ b/content/taxonomy_term.fb6ffbd7-a7c1-49a5-8df3-d8167b8359c6.json
@@ -33,7 +33,13 @@
             "value": "Matt Glaman"
         }
     ],
-    "description": [],
+    "description": [
+        {
+            "value": null,
+            "format": null,
+            "processed": ""
+        }
+    ],
     "weight": [
         {
             "value": 0