diff --git a/db/yoapuesto.sql b/db/yoapuesto.sql index 77717ee..c89a043 100644 --- a/db/yoapuesto.sql +++ b/db/yoapuesto.sql @@ -3,7 +3,7 @@ -- https://www.phpmyadmin.net/ -- -- Servidor: localhost:8889 --- Tiempo de generación: 29-09-2026 a las 07:28:38 +-- Tiempo de generación: 29-09-2026 a las 13:57:02 -- Versión del servidor: 8.0.44 -- Versión de PHP: 8.3.30 @@ -364,7 +364,10 @@ INSERT INTO `ps_compressx_images_meta` (`id`, `blog_id`, `attachment_id`, `mime_ (55, 1, 206, 'image/png', 'optimized', 1, 0, 1285438, 275074, 0, 2850633, 509040, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":1285438,\"webp_converted_size\":275074,\"avif_converted_size\":0,\"sum_size\":2850633,\"webp_sum_converted_size\":509040,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-sombra-01-circle-shadow.png\",\"webp_converted_size\":275074,\"file_size\":1285438},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":24319,\"webp_converted_size\":5218,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-sombra-01-circle-shadow-250x140.png\"},\"large\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":185949,\"webp_converted_size\":24488,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-sombra-01-circle-shadow-700x392.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":10997,\"webp_converted_size\":2074,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-sombra-01-circle-shadow-150x150.png\"},\"medium_large\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":226865,\"webp_converted_size\":29724,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-sombra-01-circle-shadow-768x430.png\"},\"1536x1536\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":1030182,\"webp_converted_size\":159210,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-sombra-01-circle-shadow-1536x859.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":6528,\"webp_converted_size\":1550,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-sombra-01-circle-shadow-120x67.png\"},\"custom-size\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":80355,\"webp_converted_size\":11702,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-sombra-01-circle-shadow-700x200.png\"}}}', '2026-09-28 22:59:03', '2026-09-28 22:58:50', 1), (56, 1, 207, 'image/png', 'optimized', 1, 0, 987937, 72164, 0, 1447778, 125170, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":987937,\"webp_converted_size\":72164,\"avif_converted_size\":0,\"sum_size\":1447778,\"webp_sum_converted_size\":125170,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-img-smallIphone.png\",\"webp_converted_size\":72164,\"file_size\":987937},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":172589,\"webp_converted_size\":21400,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-img-smallIphone-250x414.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":42912,\"webp_converted_size\":6612,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-img-smallIphone-150x150.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":45041,\"webp_converted_size\":7326,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-img-smallIphone-120x199.png\"},\"custom-size\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":199299,\"webp_converted_size\":17668,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-img-smallIphone-640x200.png\"}}}', '2026-09-28 23:52:41', '2026-09-28 23:52:39', 1), (58, 1, 209, 'image/png', 'optimized', 1, 0, 26295, 8604, 0, 46716, 14302, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":26295,\"webp_converted_size\":8604,\"avif_converted_size\":0,\"sum_size\":46716,\"webp_sum_converted_size\":14302,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-caja-texto-2087324820aa.png\",\"webp_converted_size\":8604,\"file_size\":26295},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":8983,\"webp_converted_size\":2598,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-2087324820aa-250x55.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":8518,\"webp_converted_size\":2076,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-2087324820aa-150x150.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":2920,\"webp_converted_size\":1024,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-2087324820aa-120x27.png\"}}}', '2026-09-29 00:22:46', '2026-09-29 00:22:46', 1), -(59, 1, 210, 'image/png', 'optimized', 1, 0, 12759, 7152, 0, 28645, 12116, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":12759,\"webp_converted_size\":7152,\"avif_converted_size\":0,\"sum_size\":28645,\"webp_sum_converted_size\":12116,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-caja-texto-02.png\",\"webp_converted_size\":7152,\"file_size\":12759},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":6523,\"webp_converted_size\":2228,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-02-250x55.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":7027,\"webp_converted_size\":1862,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-02-150x150.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":2336,\"webp_converted_size\":874,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-02-120x27.png\"}}}', '2026-09-29 01:01:26', '2026-09-29 01:01:25', 1); +(59, 1, 210, 'image/png', 'optimized', 1, 0, 12759, 7152, 0, 28645, 12116, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":12759,\"webp_converted_size\":7152,\"avif_converted_size\":0,\"sum_size\":28645,\"webp_sum_converted_size\":12116,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-caja-texto-02.png\",\"webp_converted_size\":7152,\"file_size\":12759},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":6523,\"webp_converted_size\":2228,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-02-250x55.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":7027,\"webp_converted_size\":1862,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-02-150x150.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":2336,\"webp_converted_size\":874,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-caja-texto-02-120x27.png\"}}}', '2026-09-29 01:01:26', '2026-09-29 01:01:25', 1), +(60, 1, 211, 'image/png', 'optimized', 1, 0, 118650, 8752, 0, 317592, 28140, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":118650,\"webp_converted_size\":8752,\"avif_converted_size\":0,\"sum_size\":317592,\"webp_sum_converted_size\":28140,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-card-plinko.png\",\"webp_converted_size\":8752,\"file_size\":118650},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":72689,\"webp_converted_size\":6676,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-plinko-250x250.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":30618,\"webp_converted_size\":4082,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-plinko-150x150.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":21114,\"webp_converted_size\":3192,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-plinko-120x120.png\"},\"custom-size\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":74521,\"webp_converted_size\":5438,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-plinko-320x200.png\"}}}', '2026-09-29 07:38:26', '2026-09-29 07:38:25', 1), +(61, 1, 212, 'image/png', 'optimized', 1, 0, 101145, 13782, 0, 362319, 49304, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":101145,\"webp_converted_size\":13782,\"avif_converted_size\":0,\"sum_size\":362319,\"webp_sum_converted_size\":49304,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-card-avia-masters.png\",\"webp_converted_size\":13782,\"file_size\":101145},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":107003,\"webp_converted_size\":12040,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-avia-masters-250x250.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":44329,\"webp_converted_size\":6566,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-avia-masters-150x150.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":30027,\"webp_converted_size\":4888,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-avia-masters-120x120.png\"},\"custom-size\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":79815,\"webp_converted_size\":12028,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-avia-masters-262x200.png\"}}}', '2026-09-29 07:45:52', '2026-09-29 07:45:51', 1), +(62, 1, 213, 'image/png', 'optimized', 1, 0, 116405, 16452, 0, 395041, 55750, 0, 1, '{\"mime_type\":\"image\\/png\",\"status\":\"optimized\",\"webp_converted\":1,\"avif_converted\":0,\"resize_status\":1,\"compress_status\":0,\"og_file_size\":116405,\"webp_converted_size\":16452,\"avif_converted_size\":0,\"sum_size\":395041,\"webp_sum_converted_size\":55750,\"avif_sum_converted_size\":0,\"size\":{\"og\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"2026\\/09\\/banner-main-card-bufalo-hold-and-win.png\",\"webp_converted_size\":16452,\"file_size\":116405},\"medium\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":110956,\"webp_converted_size\":13342,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-bufalo-hold-and-win-250x250.png\"},\"thumbnail\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":45829,\"webp_converted_size\":6698,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-bufalo-hold-and-win-150x150.png\"},\"small\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":30996,\"webp_converted_size\":4818,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-bufalo-hold-and-win-120x120.png\"},\"custom-size\":{\"convert_webp_status\":1,\"convert_avif_status\":0,\"file_size\":90855,\"webp_converted_size\":14440,\"avif_converted_size\":0,\"status\":\"optimized\",\"error\":\"\",\"file\":\"banner-main-card-bufalo-hold-and-win-262x200.png\"}}}', '2026-09-29 07:51:55', '2026-09-29 07:51:54', 1); -- -------------------------------------------------------- @@ -457,7 +460,7 @@ CREATE TABLE `ps_options` ( -- INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES -(1, 'cron', 'a:15:{i:1790666937;a:1:{s:26:\"action_scheduler_run_queue\";a:1:{s:32:\"0d04ed39571b55704c122d726248bbac\";a:3:{s:8:\"schedule\";s:12:\"every_minute\";s:4:\"args\";a:1:{i:0;s:7:\"WP Cron\";}s:8:\"interval\";i:60;}}}i:1790668866;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1790694070;a:1:{s:21:\"wp_update_user_counts\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790697664;a:1:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790699464;a:1:{s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790701272;a:1:{s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790726400;a:2:{s:35:\"rank_math/redirection/clean_trashed\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:30:\"rank_math/links/internal_links\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790737266;a:2:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:41:\"wp_privacy_personal_data_cleanup_requests\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790737270;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790737273;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790740586;a:1:{s:35:\"rank_math/content-ai/update_prompts\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790742727;a:1:{s:30:\"wp_delete_temp_updater_backups\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}i:1790823666;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}i:1791239243;a:1:{s:26:\"wpcode_usage_tracking_cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}s:7:\"version\";i:2;}', 'on'), +(1, 'cron', 'a:15:{i:1790690217;a:1:{s:26:\"action_scheduler_run_queue\";a:1:{s:32:\"0d04ed39571b55704c122d726248bbac\";a:3:{s:8:\"schedule\";s:12:\"every_minute\";s:4:\"args\";a:1:{i:0;s:7:\"WP Cron\";}s:8:\"interval\";i:60;}}}i:1790690466;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1790694070;a:1:{s:21:\"wp_update_user_counts\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790697664;a:1:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790699464;a:1:{s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790701272;a:1:{s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1790726400;a:2:{s:35:\"rank_math/redirection/clean_trashed\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:30:\"rank_math/links/internal_links\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790737266;a:2:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:41:\"wp_privacy_personal_data_cleanup_requests\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790737270;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790737273;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790740586;a:1:{s:35:\"rank_math/content-ai/update_prompts\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1790742727;a:1:{s:30:\"wp_delete_temp_updater_backups\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}i:1790823666;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}i:1791239243;a:1:{s:26:\"wpcode_usage_tracking_cron\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}s:7:\"version\";i:2;}', 'on'), (2, 'siteurl', 'https://yoapuesto.xyz', 'on'), (3, 'home', 'https://yoapuesto.xyz', 'on'), (4, 'blogname', 'Yo apuesto', 'on'), @@ -610,7 +613,7 @@ INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload` (213, 'rank_math_install_date', '1789564117', 'auto'), (216, 'mcp_jwt_secret', 'd834a77b5f621b3fd1e8a9968b244e9e6ac8729248d1302cac271b63f23087b9', 'off'), (219, 'wpmedia_mcp_oauth_rewrite_version', '1', 'off'), -(221, 'action_scheduler_lock_async-request-runner', '6abb65d5554103.56626508|1790666257', 'no'), +(221, 'action_scheduler_lock_async-request-runner', '6abbc38a1e6187.62323444|1790690246', 'no'), (222, 'rank_math_notifications', 'a:1:{i:0;a:2:{s:7:\"message\";s:917:\"

Posiciona tu contenido con el poder de PRO y A.I.

\n Sí, quiero un mejor SEONo, quizás más tardeYa lo compré\n

\";s:7:\"options\";a:5:{s:2:\"id\";s:20:\"rank_math_pro_notice\";s:7:\"classes\";s:16:\"rank-math-notice\";s:4:\"type\";s:4:\"info\";s:6:\"screen\";s:3:\"any\";s:10:\"capability\";s:15:\"install_plugins\";}}}', 'auto'), (223, 'rank_math_registration_skip', '1', 'auto'), (224, 'rank_math_review_notice_date', '1790773720', 'off'), @@ -619,7 +622,7 @@ INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload` (227, '_transient_rank_math_first_submenu_id', 'rank-math', 'on'), (238, 'aioseo_table_of_contents_options_internal', '{\"internal\":{\"firstActivated\":1789585741,\"lastActiveVersion\":\"202609.1\",\"lastSchemaVersion\":\"0.0\",\"migratedAppearanceDefaults\":true}}', 'auto'), (239, 'aioseo_table_of_contents_options', '{\"general\":[]}', 'auto'), -(240, '_transient_timeout_aioseo_plugin_cache_table_exists', '1791271698', 'off'), +(240, '_transient_timeout_aioseo_plugin_cache_table_exists', '1791294988', 'off'), (241, '_transient_aioseo_plugin_cache_table_exists', '1', 'off'), (242, 'widget_toc-widget', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'auto'), (244, 'as_has_wp_comment_logs', 'no', 'on'), @@ -653,7 +656,7 @@ INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload` (967, 'wpcf7', 'a:2:{s:7:\"version\";s:5:\"6.1.7\";s:13:\"bulk_validate\";a:4:{s:9:\"timestamp\";i:1789746953;s:7:\"version\";s:5:\"6.1.7\";s:11:\"count_valid\";i:1;s:13:\"count_invalid\";i:0;}}', 'auto'), (994, 'secret_key', 'cF4!`l`PT31r3s2O~9s5|>fOc-f-20)9el]Iiw):+w^9_Wm$wVgFdTL~df.^--OB', 'off'), (1005, 'category_children', 'a:0:{}', 'auto'), -(1007, 'compressx_latest_bulk_image', '210', 'off'), +(1007, 'compressx_latest_bulk_image', '213', 'off'), (1027, 'wp_calendar_block_has_published_posts', '1', 'auto'), (1442, 'wpcode_usage_tracking_config', 'a:6:{s:3:\"day\";i:1;s:4:\"hour\";i:22;s:6:\"minute\";i:27;s:6:\"second\";i:23;s:6:\"offset\";i:167243;s:8:\"initsend\";i:1790634443;}', 'off'), (1443, 'ihaf_activated', 'a:2:{s:6:\"wpcode\";i:1790025625;s:7:\"version\";s:5:\"2.3.9\";}', 'auto'), @@ -682,8 +685,26 @@ INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload` (2564, '_transient_jooosi_fon_scanned_builders_1.1.4', 'a:7:{s:7:\"kadence\";a:3:{s:4:\"name\";s:7:\"kadence\";s:9:\"file_path\";s:96:\"/Applications/MAMP/htdocs/yoapuesto/wp-content/plugins/yabe-webfont/src/Builder/Kadence/Main.php\";s:10:\"class_name\";s:30:\"JooosiFon\\Builder\\Kadence\\Main\";}s:14:\"generate-press\";a:3:{s:4:\"name\";s:14:\"generate-press\";s:9:\"file_path\";s:102:\"/Applications/MAMP/htdocs/yoapuesto/wp-content/plugins/yabe-webfont/src/Builder/GeneratePress/Main.php\";s:10:\"class_name\";s:36:\"JooosiFon\\Builder\\GeneratePress\\Main\";}s:10:\"builderius\";a:3:{s:4:\"name\";s:10:\"builderius\";s:9:\"file_path\";s:99:\"/Applications/MAMP/htdocs/yoapuesto/wp-content/plugins/yabe-webfont/src/Builder/Builderius/Main.php\";s:10:\"class_name\";s:33:\"JooosiFon\\Builder\\Builderius\\Main\";}s:14:\"classic-editor\";a:3:{s:4:\"name\";s:14:\"classic-editor\";s:9:\"file_path\";s:102:\"/Applications/MAMP/htdocs/yoapuesto/wp-content/plugins/yabe-webfont/src/Builder/ClassicEditor/Main.php\";s:10:\"class_name\";s:36:\"JooosiFon\\Builder\\ClassicEditor\\Main\";}s:9:\"gutenberg\";a:3:{s:4:\"name\";s:9:\"gutenberg\";s:9:\"file_path\";s:98:\"/Applications/MAMP/htdocs/yoapuesto/wp-content/plugins/yabe-webfont/src/Builder/Gutenberg/Main.php\";s:10:\"class_name\";s:32:\"JooosiFon\\Builder\\Gutenberg\\Main\";}s:9:\"elementor\";a:3:{s:4:\"name\";s:9:\"elementor\";s:9:\"file_path\";s:98:\"/Applications/MAMP/htdocs/yoapuesto/wp-content/plugins/yabe-webfont/src/Builder/Elementor/Main.php\";s:10:\"class_name\";s:32:\"JooosiFon\\Builder\\Elementor\\Main\";}s:8:\"pinegrow\";a:3:{s:4:\"name\";s:8:\"pinegrow\";s:9:\"file_path\";s:97:\"/Applications/MAMP/htdocs/yoapuesto/wp-content/plugins/yabe-webfont/src/Builder/Pinegrow/Main.php\";s:10:\"class_name\";s:31:\"JooosiFon\\Builder\\Pinegrow\\Main\";}}', 'off'), (2773, '_site_transient_timeout_theme_roots', '1790659915', 'off'), (2774, '_site_transient_theme_roots', 'a:1:{s:9:\"yoapuesto\";s:7:\"/themes\";}', 'off'), -(2866, '_site_transient_timeout_wp_theme_files_patterns-e63649065a3fb80d206fc8d31dc97157', '1790668499', 'off'), -(2867, '_site_transient_wp_theme_files_patterns-e63649065a3fb80d206fc8d31dc97157', 'a:2:{s:7:\"version\";s:5:\"1.5.1\";s:8:\"patterns\";a:0:{}}', 'off'); +(2894, '_transient_timeout_rank_math_feed_posts_v2', '1790732264', 'off'), +(2895, '_transient_rank_math_feed_posts_v2', 'a:4:{i:0;a:5:{s:5:\"title\";a:1:{s:8:\"rendered\";s:51:\"Content AI 2.0: Introducing AI SEO Inside WordPress\";}s:4:\"date\";s:19:\"2026-09-29 12:29:12\";s:4:\"link\";s:62:\"https://rankmath.com/blog/introducing-supercharged-content-ai/\";s:12:\"custom_label\";s:0:\"\";s:9:\"condition\";s:0:\"\";}i:1;a:3:{s:5:\"title\";a:1:{s:8:\"rendered\";s:57:\"Free vs Paid WordPress Plugins: Which Should You Choose?\";}s:4:\"date\";s:19:\"2026-09-28 07:13:30\";s:4:\"link\";s:57:\"https://rankmath.com/blog/free-vs-paid-wordpress-plugins/\";}i:2;a:3:{s:5:\"title\";a:1:{s:8:\"rendered\";s:40:\"7 Best WordPress Site Management Plugins\";}s:4:\"date\";s:19:\"2026-09-15 04:05:37\";s:4:\"link\";s:60:\"https://rankmath.com/blog/wordpress-site-management-plugins/\";}i:3;a:3:{s:5:\"title\";a:1:{s:8:\"rendered\";s:64:\"The Best White Label SEO Tools to Save Time and Win More Clients\";}s:4:\"date\";s:19:\"2026-09-08 06:03:07\";s:4:\"link\";s:48:\"https://rankmath.com/blog/white-label-seo-tools/\";}}', 'off'), +(2896, '_site_transient_timeout_community-events-1aecf33ab8525ff212ebdffbb438372e', '1790732264', 'off'), +(2897, '_site_transient_community-events-1aecf33ab8525ff212ebdffbb438372e', 'a:4:{s:9:\"sandboxed\";b:0;s:5:\"error\";N;s:8:\"location\";a:1:{s:2:\"ip\";s:9:\"127.0.0.0\";}s:6:\"events\";a:0:{}}', 'off'), +(2898, '_site_transient_timeout_feed_203ddaeab844647ccdc6525a1073e4d6', '1790732265', 'off'); +INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES +(2899, '_site_transient_feed_203ddaeab844647ccdc6525a1073e4d6', 'a:6:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:52:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:8:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"Blog – WordPress.org Español (México)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"https://es-mx.wordpress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"WordPress en Español de México\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 18 Jul 2024 14:05:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:2:\"es\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=7.2-alpha-63998\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:5:\"image\";a:1:{i:0;a:6:{s:4:\"data\";s:11:\"\n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:3:\"url\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://s.w.org/favicon.ico?2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"Blog – WordPress.org Español (México)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"https://es-mx.wordpress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:5:\"width\";a:1:{i:0;a:5:{s:4:\"data\";s:2:\"32\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:6:\"height\";a:1:{i:0;a:5:{s:4:\"data\";s:2:\"32\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}s:4:\"item\";a:10:{i:0;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"WordPress 6.6 “Dorsey”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"https://es-mx.wordpress.org/2024/07/18/wordpress-6-6-dorsey/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://es-mx.wordpress.org/2024/07/18/wordpress-6-6-dorsey/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 18 Jul 2024 14:05:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Uncategorized\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://es-mx.wordpress.org/?p=1037\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:339:\"Saluda a WordPress 6.6 “Dorsey”, que lleva el nombre del legendario líder de la Big Band estadounidense, Tommy Dorsey. Famoso por su trombón de tono suave y sus composiciones, la música de Dorsey cautivó al público con su profundidad emocional y su energía vibrante. Deja que tu corazón se balancee y cante al ritmo de […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:61799:\"\n
\"\"
\n\n\n\n

Saluda a WordPress 6.6 “Dorsey”, que lleva el nombre del legendario líder de la Big Band estadounidense, Tommy Dorsey. Famoso por su trombón de tono suave y sus composiciones, la música de Dorsey cautivó al público con su profundidad emocional y su energía vibrante.

\n\n\n\n

Deja que tu corazón se balancee y cante al ritmo de las profundas notas de metal del sonido de la Big Band de Dorsey mientras exploras las nuevas características y mejoras de WordPress 6.6.

\n\n\n\n\n\n\n\n

¡Hola, 6.6!

\n\n\n\n

WordPress 6.6 cumple con la promesa de una mejor web al incorporar estilo, delicadeza y un conjunto de posibilidades creativas a la experiencia de creación de sitios. Esta versión te ayuda a hacer más con facilidad, poniendo herramientas mejoradas a tu alcance y dándote un poder sin precedentes detrás de escena. Encontrarás más formas de crear elementos de diseño hermosos y coherentes en todo tu sitio, un nuevo diseño para vistas previas rápidas de páginas en el Editor del sitio y la seguridad de las reversiones automáticas para actualizaciones automáticas de complementos fallidas, entre muchas otras características destacadas.

\n\n\n\n

Además de las nuevas características, “Dorsey” continúa brindando las mejoras de rendimiento y accesibilidad que puedes esperar de cada versión de WordPress. Explora lo que WordPress 6.6 tiene para ofrecer y prepárate para dejar que sus características lleven tus sitios a nuevas alturas.

\n\n\n\n
\n
Descargar WordPress 6.6 “Dorsey”
\n
\n\n\n\n

¿Qué hay dentro?

\n\n\n\n

Agrega más opciones de diseño a los temas de bloques

\n\n\n\n

Crea conjuntos de colores o fuentes para multiplicar las combinaciones de diseño en un tema. Estos conjuntos ofrecen posibilidades de diseño más contenidas, lo que permite una variedad visual dentro de las pautas de estilo más amplias del sitio.

\n\n\n\n
\"\"
\n\n\n\n

Simplifica tu flujo de trabajo con un nuevo diseño para las páginas en el Editor del sitio

\n\n\n\n

Ve todas tus páginas y una vista previa de cualquier página seleccionada con el nuevo diseño en paralelo en el Editor del sitio.

\n\n\n\n
\"\"
\n\n\n\n

Actualiza automáticamente tus plugins con tranquilidad

\n\n\n\n

Disfruta de la comodidad de las actualizaciones automáticas de plugins con la seguridad de poder revertirlas si algo sale mal, lo que le ofrece a tu sitio un nuevo nivel de seguridad, una funcionalidad mejorada a medida que esté disponible y casi sin tiempo ni ancho de banda para que esto suceda.

\n\n\n\n
\"\"
\n\n\n\n

Personaliza el contenido en patrones sincronizados

\n\n\n\n

Realiza cambios en el contenido en cada instancia de un patrón sincronizado manteniendo un estilo uniforme en todos ellos. Establece estas modificaciones para los bloques de encabezado, párrafo, botón e imagen cuando se colocan en un patrón sincronizado.

\n\n\n\n
\"\"
\n\n\n\n

Rendimiento

\n\n\n\n

WordPress 6.6 incluye actualizaciones importantes, como la eliminación de llamadas WP_Theme_JSON redundantes, la desactivación de la carga automática para opciones grandes y la eliminación de dependencias polyfill innecesarias. Otras novedades incluyen la carga diferida de incrustaciones de entrads, una nueva directiva data-wp-on-async y plantillas en el editor que se cargan aproximadamente un 35 % más rápido en general.

\n\n\n\n

Accesibilidad

\n\n\n\n

Esta versión incluye 58 correcciones y mejoras de accesibilidad. Estas se centran en aspectos fundamentales de la experiencia de WordPress, en particular el componente de vistas de datos que impulsa la nueva experiencia de edición del sitio y áreas como el Insertador, que proporciona una forma clave de interactuar con bloques y patrones.

\n\n\n\n

Y mucho más

\n\n\n\n

Visita la presentación de características para obtener una descripción general completa de todas las nuevas características y mejoras en WordPress 6.6.

\n\n\n\n
\n
Revisa lo nuevo
\n
\n\n\n\n

Más información sobre WordPress 6.6

\n\n\n\n

Explora Learn WordPress para obtener videos instructivos rápidos, talleres en línea y otros recursos gratuitos para mejorar tus conocimientos y habilidades sobre WordPress.

\n\n\n\n

La Guía práctica de WordPress 6.6 contiene información técnica detallada y notas para desarrolladores que te ayudarán a desarrollar con WordPress y aprovechar al máximo esta versión. No olvides suscribirte al Blog para desarrolladores para obtener actualizaciones, tutoriales y otro contenido útil de WordPress para desarrolladores.

\n\n\n\n

Para obtener información sobre la instalación, los cambios de archivos, las correcciones y otras actualizaciones, lee las notas de la versión 6.6.

\n\n\n\n

El equipo de la versión 6.6

\n\n\n\n

Cada versión llega a ti de la mano de un equipo dedicado de colaboradores entusiastas que ayudan a mantener las cosas encaminadas y avanzando sin problemas. El equipo que ha liderado la versión 6.6 es un grupo multifuncional de colaboradores que siempre están listos para defender ideas, eliminar obstáculos y resolver problemas.

\n\n\n\n\n\n\n\n

Gracias a los colaboradores

\n\n\n\n

La misión de WordPress es democratizar la publicación y encarnar las libertades que ofrece el código abierto. Una comunidad global y diversa de personas que colaboran para fortalecer el software respalda este esfuerzo.

\n\n\n\n

WordPress 6.6 refleja los esfuerzos incansables y la pasión de más de 630 colaboradores en al menos 51 países. ¡Esta versión también dio la bienvenida a más de 150 colaboradores primerizos!

\n\n\n\n

Su colaboración generó más de 1,900 mejoras y correcciones, lo que garantizó una versión estable para todos, un testimonio del poder y la capacidad de la comunidad de código abierto de WordPress.

\n\n\n\n

!Benni · 1naveengiri · Aaron Jorbin · Aaron Robertshaw · aatanasov · abditsori · Abha Thakor · abhi3315 · Abhijit Rakas · abitofmind · Adam Harley (Kawauso) · Adam Silverstein · Adel Tahri · adrianduffell · Aezaz Shekh · Ahmed Kabir Chaion · ajfleming · Ajit Bohra · Akash Dhawade · Aki Hamano · Akira Tachibana · akmelias · Alan Fuller · Albert Juhé Lluveras · alesflex · Alex Concha · Alex Kozack · Alex Lende · Alex Stine · Alexandre Buffet · alexminza · allilevine · Alvaro Gómez · amanias1977 · Amber Hinds · Amir Abbas · amisiewicz · Amit Raj · Anamarija Papić · Anders Norén · Andre Ribeiro · Andrea Fercia · Andrea Roenning · Andrei Draganescu · Andrei Lupu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Ozz · Andrew Serong · André Maneiro · Andy Fragen · Aneesh Devasthale · Angela Jin · Anil Vaza · Ankit K Gupta · Ankit Panchal · Anne McCarthy · Anthony Burchell · Anton Vlasenko · Ari Stathopoulos · Artemio Morales · Arthur Chu · Artur Piszek · Arun Sharma · Arunas Liuiza · Ashesh Magar · Asiqur Rahman · Asish Chandra Mohon · Aslam Doctor · asmittle · Aurooba Ahmed · Ayesh Karunaratne · Balu B · bangank36 · Bart Kalisz · Beatriz Fialho · Beau Lebens · Ben Dwyer · Ben Keith · Ben Ritner – Kadence WP · Benjamin Pick · Benjamin Zekavica · benjpw · bernhard-reiter · Birgit Pauli-Haack · bissy · Bjarne Oldrup · Blackbam · Blockify · bnewboldbsky · Brad Jorsch · Brennan Goewert · Brian Alexander · Brian Coords · Brian Gardner · Brian Gosnell · Brian Haas · Bridget Willard · Brooke · Bruno Freiberger Garcia · burnuser · Caleb Burks · Candy · Carlos Bravo · Carlos G. P. · Carolina Nymark · cbirdsong · Chad Chadbourne · Charlie Merland · Chloe Bringmann · Chouby · Chris Reynolds · chrisdotdotdot · Christopher · Colin Stewart · ColinD · colle · comecaramelos · Constantine Vasilyev · CookiesForDevo · Corey McKrill · Craig Francis · crazytonyli · Cullen Whitmore · Curdin Krummenacher · cyrus11 · Dale du Preez · Damon Cook · Damon Cook · Dan Soschin · Dani Guardiola · Daniel Richards · darerodz · Darren Ethier (nerrad) · Darshit Rajyaguru · dav4 · Dave Page · David · David A. Kennedy · David Baumwald · David Biňovec · David Bowman · David Calhoun · David Herrera · David Jensen · David Levine · David Rozando · David Smith · davideferre · De’Yonté W. · Dean Sas · Deep Patel · Deepak Vijayan · Denis Žoljom · Dennis Snell · Derek Blank · Devin Curtis · Dharmesh Patel · Dhrumil Kumbhani · Dhruval Shah · dhruvang21 · dhruvkb · DiedeExterkate · Dilip Bheda · Dion Hulse · DJ · DjZoNe · Dominik Schilling · Drew Jaynes · drrxbracho · Earle Davies · Elena Brescacin · Ella van Durpe · Emmanuel Hesry · Enej Bajgorić · Eneko Garrido · enodekciw · Enrico Battocchi · Enrico Sorcinelli · Erik · Estela Rueda · evanltd · Fabian Kägy · Fabian Todt · Faisal Alvi · Fanly · Farhan Ahmed · Felix Arntz · Flavia Bernárdez Rodríguez · Florian TIAR · Franz Josef Kaiser · Gabor Lippert · Gal Baras · Garth Mortensen · Gary Jones · George Mamadashvili · George Stephanis · Gerardo Pacheco · Glen Davies · Glenn Ansley · Grant M. Kinney · Greg Ziółkowski · Guido Scialfa · Héctor Prieto · hakre · hanneslsm · Hans-Gerd Gerhards · Harit Panchal · Harsh Gajipara · Haz · heinvv · HelgaTheViking · Hinnerk Altenburg · Hit Bhalodia · Hitendra Chopda · humanify · huubl · Huzaifa Al Mesbah · Ian Belanger · ignatiusjeroe · Imran · inwerpsel · Ipstenu (Mika Epstein) · Isabel Brison · IT Path Solutions · ivanottinger · Jaap Weijland · Jack Stevens · jaclync · James Koster · James Wesley Goedert · Jamie Speller · Jan Boddez · Jansen Tolle · janthiel · Jarda Snajdr · Jarek Mazurczak · Jaroslav “Dero” Polakovic · Jason Adams · Jason Crist · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Casares · jayanthparthsarathy · jdekhtiar · Jean-Baptiste Audras · Jeff Chi · Jeff Ong · Jeffrey Paul · jeflopo · Jenny Dupuy · Jeremy Felt · Jeremy Herve · Jeremy Pry · Jerry Jones · Jesús Amieiro · Jess · Jessica Lyschik · jhned · Jigar Bhanushali · Jip Moors · JiveDig · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Jülg · John Blackbourn · John Espiritu · John Godley · John Hooks · John James Jacoby · Jon Surrell · jon092 · Jonathan · Jonathan Bossenger · Jonathan Desrosiers · Joni Erkkilä · Jonny Harris · jordesign · Jorge Costa · Jose Varghese · Josep Morán · Joseph Scott · Joshua Goode · Jossnaz · Juan Aldasoro · JuanMa Garrido · jules · Julie Moynat · Juliette Reinders Folmer · Julio Potier · Justin Tadlock · justnorris · Jyolsna J E · K. Adam White · KafleG · Kai Hao · Kajal Gohel · kamran8176 · Kapil Paul · Karlijn Bok · Karol Manijak · Karthik Thayyil · Kathryn Presner · Kellen Mace · Kelly Choyce-Dwan · keoshi · Kevin Hoffman · Khokan Sardar · killua99 · Kira Schroder · kitchin · Kite · Kjell Reigstad · kkmuffme · kmvan · Konstantin Kovshenin · kristastevens · kristenfisher427 · Krupa Nanda · Krupal Panchal · Kushang Tailor · kyleak · Lae · Lanre Smith · Lars Gersmann · Laura Byrne · laurelfulford · Lauren · Lauren Stein · Laurent Naudier · leemon · Lena Morita · Leonidas Milosis · Linkon Miyan · liviopv · Louis Wolmarans · Lovekesh Kumar · luboslives · Luigi Teschio · Luis · Luis Molina (interdevel) · luisherranz · Lyon Müller · Márcio Duarte · Madhu Dollu · Maggie Cabrera · Mai · Makdia Hussain · manfcarlo · Manoj Maharrshi · Marc · Marc Armengou · Marcelo de Moraes Serpa · Marco Ciampini · Marco Pereirinha · marherumr · Marie Comet · Marin Atanasov · Mario Santos · Marius L. J. · Mark Howells-Mead · Mark Jaquith · Mark Szymanski · Mark Uraine · Martijn van der Klis · Mary Baum · Mat Lipe · Mathieu Viet · Matias Benedetto · Matias Ventura · Matt Cromwell · Matt Medeiros · Matt Mullenweg · Matt Sherman · Md Abul Bashar · Md Sahadat Husain · Md Tofajjal Hossen · MD.NESAR MRIDHA · Meet Makadia · Meet Mehta · megane9988 · Meher Bala · Michael James Ilett · Michal Czaplinski · Miguel Fonseca · miguelsansegundo · Mihai Joldis · Miikka · Mikael Korpela · Mike Henderson · Mike McAlister · Mikey Binns · Minal Diwan · Miriam Schwab · miya · mkismy · Mohit Dadhich · Monzur Alam · Morais Junior · mrwweb · Muhibul Haque · mujuonly · Mukesh Panchal · Musannif Zahir · Mustaque Ahmed · myhro · mykolashlyakhtun · Mykyta Synelnikov · Nadir Seghir · Naeem Haque · Namith Jawahar · Narendra Sishodiya · Naresh Bheda · Nate Gay · Nazmul Hasan Robin · Nazmul Hosen · Nick Diego · nicmare · Nico · Nicolas Tatarchenko · Nicole Furlan · Nicole Paschen Caylor · nicomollet · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nilo Velez · Nirav Sherasiya · Nithin John · Nithin SreeRaj · nkeller15 · nosilver4u · obliviousharmony · Ohia ᚛ᚈᚐᚂᚐᚋᚆ᚜ · okat · Old account · Olga Gleckler · Oliver Campion · Oliver Schmid · OllieJones · Omar Alshaker · Paal Joachim Romdahl · Pablo Honey · Paolo L. Scala · Pascal Birchler · Patricia BT · Paul Bearne · Paul de Wouters · Paul Kevan · Paul Wilde · Pavan Patil · pavelevap · Pedro Mendonça · peiche · Per Søderlind · perryrylance · Peter Rubin · Peter Wilson · petitphp · Phi Phan · Pieterjan Deneys · Pinar · Pitam Dey · pkuliga · Pooja N Muchandikar · Povilas Staškus · Praful Patel · Pranit Dugad · Prasad Karmalkar · Prashant Baldha · Pratik Londhe · Prem Tiwari · Presskopp · presstoke · printsachen1 · Priyanshii Vijayvargiya · Prottoy Sarkar Argho · QuietNoise · Rachel Baker · Rafael Galani · Rafał Całka · Rajan Lama · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Ravikumar Patel · Ravinder Kumar · Rejaul Alom Khan · Remkus de Vries · Remy Perona · renishsurani · retrofox · Riad Benguella · Rich Collier · Rich Tabor · Richard Korthuis · richardevs · Rishi Mehta · Robert Anderson · Robert Ghetau · Robin Cornett · rodionov201 · Rodrigo Arias · Rodrigo Primo · Roger · Rolf Siebers · Roy Tanck · Ryan McCue · Ryan Urban · Ryan Welcher · Sébastien SERRE · Sérgio Gomes · Sören Wünsch · s0what · Sagar Prajapati · sahilthakur02 · Sakib Mohammed · Sal Ferrarello · Sam Berry · Sam Brockway · samiamnot · Sampat Viral · Samuel Rüegger · Samuel Sidler · Sanne van der Meulen · Sarah Norris · Sarkar Ripon · Sascha Metz · Saulius Vikerta · Saxon Fletcher · Saxon Fletcher · scribu · script2see · Sean Fisher · Sergey Biryukov · Seth Miller · Seth Rubenstein · Shail Mehta · Shalin Shah · Shannon Smith · shaunandrews · sheulyshila · Shital Marakana · Shiva Poudel · Shiva Shanker Bhatta · Shreyash Srivastava · Shubham Kumar Bansal · Shuvo Mohajan · Siddharth Thevaril · siliconforks · Simone Maranzana · Siobhan · sirzooro · SJNBham · Sneha Patil · Spencer Finnell · Stefano Minoia · Stephen Bernhardt · Stephen Brook · Stephen Edgar · stephenmiracle · Steve Jones · steveblum · strangehill · strarsis · Sudip Dadhaniya · Sumit Bagthariya · Sumit Singh · SunilPrajapati · Suwash · syamraj24 · Sybre Waaijer · Syed Balkhi · Tahmid ul Karim · Takashi Irie · Takashi Kitajima · Tammie Lister · Taylor Gorman · Terence Eden · Teresa Gobble · Thakor Darshil · thelmachido a11n · Thijs · Thirumani Guhan · Thomas Kräftner · Till Krüss · Tim Brathärig · Tim Nicholson · Tim Nolte · Timo Tijhof · Timothy Jacobs · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom Cafferkey · Tomek · tomepajk · Tomoki Shimomura · tomxygen · Toni Viemerö · Tony G · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Trupti Kanzariya · tunetheweb · twstokes · tybor · Ugyen Dorji · Umesh Gupta · up1512001 · Vicente Canales · Viktor Szépe · Vinit · Vinita Tandulkar · Vipul Gupta · Vishal Kothari · vivekawsm · WebMan Design | Oliver Juhas · websitegenii · wesatintellitonic · Weston Ruter · whaze · Will Skora · William Earnhardt · WilliamG · Wojtek Naruniec · Yagnik Sangani · yankiara · Yann · Yannis Guyon · Yui · Yukinobu Asakawa · Yuvrajsinh Sisodiya · Zack Krida · Zafar Kamal · zieladam · zkarj · Zunaid Amin

\n\n\n\n

Más de 60 regiones han traducido el 90 por ciento o más de WordPress 6.5 a su idioma. Los traductores de la comunidad están trabajando arduamente para garantizar que haya más traducciones en camino. Gracias a todos los que ayudan a que WordPress esté disponible en 200 idiomas.

\n\n\n\n

Por último, pero no menos importante, gracias a los voluntarios que contribuyen a los foros de soporte respondiendo preguntas de los usuarios de WordPress de todo el mundo.

\n\n\n\n

Involúcrate y contribuye

\n\n\n\n

La participación en WordPress no se limita a la codificación. Si le atrae contribuir, aprender más e involucrarse es fácil. Descubre los equipos que se unen en Make WordPress y utiliza esta herramienta interactiva para ayudarte a decidir cuál es la adecuada para ti.

\n\n\n\n

6.6 haiku

\n\n\n\n

Ya está aquí Seis-punto-seis.
Haz que todo sea hermoso, manténlo
con tu marca y relájate.

\n\n\n\n

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://es-mx.wordpress.org/2024/07/18/wordpress-6-6-dorsey/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"1037\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:76:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"WordPress 6.5.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://es-mx.wordpress.org/2024/06/25/wordpress-6-5-5/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://es-mx.wordpress.org/2024/06/25/wordpress-6-5-5/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 25 Jun 2024 14:22:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:15:\"Actualizaciones\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"6.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://es-mx.wordpress.org/?p=1032\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:378:\"¡WordPress 6.5.5 ya está disponible! Esta versión presenta tres correcciones de seguridad. Debido a que se trata de una versión de seguridad, se recomienda que actualices tus sitios de inmediato. Esta versión menor también incluye 3 correcciones de errores en Core. Puedes descargar WordPress 6.5.5 desde WordPress.org o visitar tu Panel de WordPress, hacer clic […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5768:\"\n

¡WordPress 6.5.5 ya está disponible!

\n\n\n\n

Esta versión presenta tres correcciones de seguridad. Debido a que se trata de una versión de seguridad, se recomienda que actualices tus sitios de inmediato. Esta versión menor también incluye 3 correcciones de errores en Core.

\n\n\n\n

Puedes descargar WordPress 6.5.5 desde WordPress.org o visitar tu Panel de WordPress, hacer clic en “Actualizaciones” y luego hacer clic en “Actualizar ahora”. Si tienes sitios que admiten actualizaciones automáticas en segundo plano, el proceso de actualización comenzará automáticamente.

\n\n\n\n

WordPress 6.5.5 es una versión de ciclo corto. El próximo lanzamiento importante será la versión 6.6, que está programada para el 16 de julio de 2024.

\n\n\n\n

Para obtener más información sobre WordPress 6.5.5, visita el sitio HelpHub.

\n\n\n\n

Actualizaciones de seguridad incluidas en esta versión

\n\n\n\n

El equipo de seguridad desea agradecer a las siguientes personas por informar responsablemente las vulnerabilidades y permitir que se corrijan en esta versión:

\n\n\n\n\n\n\n\n

Gracias a estos contribuyentes de WordPress

\n\n\n\n

Este lanzamiento fue dirigido por Aaron Jorbin.

\n\n\n\n

WordPress 6.5.5 no habría sido posible sin las contribuciones de las siguientes personas. Su coordinación asincrónica para ofrecer correcciones de mantenimiento y seguridad en una versión estable es un testimonio del poder y la capacidad de la comunidad de WordPress.

\n\n\n\n

Aaron Jorbin, Alex Concha, Andrew Ozz, bernhard-reiter, Colin Stewart, David Baumwald, Dennis Snell, Grant M. Kinney, Greg Ziółkowski, Jb Audras, Jonathan Desrosiers, Matias Ventura, Miguel Fonseca, Peter Wilson, Rajin Sharwar, Scott Reilly, Tonya Mork

\n\n\n\n

Cómo contribuir

\n\n\n\n

Para participar en el desarrollo central de WordPress, ve a Trac, elige un ticket y únete a la conversación en el canal #core de Slack. ¿Necesitas ayuda? Consulta el Manual del colaborador principal.

\n\n\n\n

¿Ya estás probando WordPress 6.6? La cuarta versión beta ya está disponible y contiene estas correcciones de seguridad. Para obtener más información sobre 6.6, consulta la entrada del anuncio de la beta 3. Obtén más información sobre cómo probar WordPress 6.6 aquí.

\n\n\n\n

Felicitaciones a Paul Kevan, Ehtisham Siddiqui, Alex Concha, Tonya Mork, y Angela Jin por su revisión.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"https://es-mx.wordpress.org/2024/06/25/wordpress-6-5-5/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"1032\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:79:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"WordPress 6.5 “Regina”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"https://es-mx.wordpress.org/2024/04/03/wordpress-6-5-regina/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://es-mx.wordpress.org/2024/04/03/wordpress-6-5-regina/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 03 Apr 2024 15:37:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:15:\"Actualizaciones\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:12:\"Lanzamientos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://es-mx.wordpress.org/?p=1021\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:369:\"Saluda a WordPress 6.5 “Regina”, inspirado en la versatilidad dinámica de la reconocida violinista de jazz Regina Carter. Artista galardonada y educadora de jazz reconocida por trascender el género, los fundamentos técnicos de Regina en la música clásica y su profundo conocimiento del jazz le han valido la reputación de ir audazmente más allá de […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:73321:\"\n
\"\"
\n\n\n\n

Saluda a WordPress 6.5 “Regina”, inspirado en la versatilidad dinámica de la reconocida violinista de jazz Regina Carter. Artista galardonada y educadora de jazz reconocida por trascender el género, los fundamentos técnicos de Regina en la música clásica y su profundo conocimiento del jazz le han valido la reputación de ir audazmente más allá de lo que es posible con el violín.

\n\n\n\n\n\n\n\n

Deja que los impresionantes giros y cambios sutiles del sonido innovador de Regina te sorprendan mientras exploras todo lo que ofrece 6.5.

\n\n\n\n

Esta última versión de WordPress pone más poder en los detalles. Ofrece formas nuevas y mejoradas de ajustar y mejorar su experiencia de creación de sitios, permitiéndote tomar el control de manera que lo hagas tuyo. Encontrarás nuevas formas de administrar la tipografía de tu sitio, revisiones más completas disponibles en más lugares y una colección de actualizaciones del Editor del sitio junto con impresionantes mejoras de rendimiento para ayudarlo a hacer las cosas de manera más fluida y rápida.

\n\n\n\n

“Regina” también marca la introducción de algunas herramientas innovadoras para desarrolladores que comenzarán a transformar la forma en que usas y amplías los bloques para crear experiencias atractivas. La API Interactivity abre un mundo de posibilidades creativas de interfaz, mientras que la API Block Bindings hace que las conexiones dinámicas entre bloques y datos sean perfectas. Estas, entre otras mejoras y actualizaciones centradas en los desarrolladores, están listas para ayudarle a evolucionar la forma en que construye con WordPress.

\n\n\n\n
\n
Descargar WordPress 6.5 “Regina”
\n
\n\n\n\n

¿Qué hay dentro de 6.5?

\n\n\n\n

Agrega y administra fuentes en tu sitio

\n\n\n\n

La nueva Biblioteca de fuentes te permite controlar una pieza esencial del diseño de tu sitio: la tipografía, sin codificación ni pasos adicionales. Instala, elimina y activa fácilmente fuentes locales y de Google en tu sitio para cualquier tema de Block. La capacidad de incluir colecciones de tipografía personalizadas brinda a los creadores y editores de sitios más opciones cuando se trata de diseñar contenido.

\n\n\n\n
\"\"
\n\n\n\n

Obtén más de tus revisiones, incluidas revisiones de plantillas y partes de plantillas

\n\n\n\n

Trabaja en proyectos creativos con una imagen más completa de lo que se ha hecho y a qué puede recurrir. Obtén detalles como marcas de tiempo, resúmenes rápidos y una lista paginada de todas las revisiones. Ve las revisiones del Libro de estilos para ver cómo los cambios afectan a cada bloque. Las revisiones ahora también están disponibles para plantillas y piezas de plantilla.

\n\n\n\n
\"\"
\n\n\n\n

Juega con herramientas mejoradas de fondo y sombra

\n\n\n\n\n\n\n\n
\"\"
\n\n\n\n

Descubre nuevas vistas de datos

\n\n\n\n

Cada parte de tu sitio viene con una biblioteca de información y datos; ahora puedes encontrar lo que necesitas rápidamente y organizarlo como desees. Las vistas de datos para páginas, plantillas, patrones y partes de plantillas te permiten ver datos en una vista de tabla o cuadrícula, con la opción de alternar campos y realizar cambios masivos.

\n\n\n\n
\"\"
\n\n\n\n

Arrastrar y soltar más suave

\n\n\n\n

Siente la diferencia cuando mueves cosas, con útiles señales visuales como elementos desplazados en la Vista de lista o arrastrándolos sin fricción a cualquier lugar de tu espacio de trabajo, de principio a fin.

\n\n\n\n
\"\"
\n\n\n\n

Controles de enlace mejorados

\n\n\n\n

Crea y administra enlaces fácilmente con una experiencia de creación de enlaces más intuitiva, como una interfaz de usuario optimizada y un acceso directo para copiar enlaces.

\n\n\n\n
\"\"
\n\n\n\n

Novedades para los desarrolladores en 6.5

\n\n\n\n

Lleva interacciones a bloques con la API de interactividad

\n\n\n\n

La API de interactividad ofrece a los desarrolladores un método estandarizado para crear experiencias de interfaz de usuario interactivas con bloques. Simplifica el proceso, con menos dependencia de herramientas externas, manteniendo al mismo tiempo un rendimiento óptimo. Úsalo para crear experiencias de usuario memorables, como obtener resultados de búsqueda al instante o permitir que los visitantes interactúen con el contenido en tiempo real.

\n\n\n\n

Conecta bloques a campos personalizados u otro contenido dinámico

\n\n\n\n

Vincula atributos de bloques principales a campos personalizados y utiliza el valor de los campos personalizados sin crear bloques personalizados. Con la tecnología de Block Bindings API, los desarrolladores pueden ampliar aún más esta capacidad para conectar bloques a cualquier contenido dinámico, incluso más allá de los campos personalizados. Si hay datos almacenados en otro lugar, apunta fácilmente los bloques a esa nueva fuente con solo unas pocas líneas de código.

\n\n\n\n

Agregar herramientas de apariencia a los temas clásicos

\n\n\n\n

Ofrece a los diseñadores y creadores que utilizan temas clásicos acceso a una experiencia de diseño mejorada. Opta por admitir opciones de espaciado, borde, tipografía y color, incluso sin utilizar theme.json. Una vez que se habilite el soporte, se agregarán automáticamente más herramientas a medida que estén disponibles.

\n\n\n\n

Explora mejoras en la experiencia del complemento

\n\n\n\n

Ahora existe una forma más sencilla de gestionar las dependencias de los plugins. Los autores de plugins pueden proporcionar un nuevo encabezado Requires Plugins con una lista separada por comas de los plugins requeridos, presentando a los usuarios enlaces para instalar y activar esos plugins primero.

\n\n\n\n

De rápido a más rápido: actualizaciones de rendimiento

\n\n\n\n

Esta versión incluye más de 110 actualizaciones de rendimiento, lo que da como resultado un aumento impresionante en la velocidad y la eficiencia en el Editor de publicaciones y el Editor del sitio. La carga es dos veces más rápida que en 6.4, con una velocidad de procesamiento de entrada hasta cinco veces más rápida que en la versión anterior.

\n\n\n\n

Los sitios traducidos ven una mejora de hasta un 25% en el tiempo de carga para esta versión, cortesía de Performant Translations. Otros aspectos destacados del rendimiento incluyen compatibilidad con imágenes AVIF y mejoras para registrar variaciones de bloques con devoluciones de llamada.

\n\n\n\n

Una tradición de inclusión

\n\n\n\n

Esta versión incluye más de 65 mejoras de accesibilidad en toda la plataforma, haciéndola más accesible que nunca. Contiene una solución importante que desbloquea el acceso a los submenús de administración para los usuarios de lectores de pantalla y otras personas que navegan con el teclado. Esta versión también agrega correcciones al contraste de color en los estados de enfoque del administrador, posicionamiento de elementos y enfoque del cursor, entre muchos otros, que ayudan a mejorar la experiencia de WordPress para todos.

\n\n\n\n

Obtén más información sobre WordPress 6.5

\n\n\n\n

Consulta la nueva página de WordPress 6.5 para obtener más información sobre las numerosas mejoras y funciones de esta versión, incluidas breves demostraciones de algunas de las funciones destacadas.

\n\n\n\n

Explora Learn WordPress para ver videos instructivos rápidos, talleres en línea y otros recursos gratuitos para mejorar tus conocimientos y habilidades de WordPress.

\n\n\n\n

Consulta la Guía de campo de WordPress 6.5 para obtener información técnica detallada y notas para desarrolladores que te ayudarán a crear con WordPress y aprovechar al máximo esta versión. No olvides suscribirte al Blog para desarrolladores para obtener actualizaciones para desarrolladores, tutoriales de funciones y otro contenido útil de WordPress desde la perspectiva del desarrollador.

\n\n\n\n

Para obtener más información sobre la instalación, cambios de archivos, correcciones y otras actualizaciones, lee las notas de la versión 6.5.

\n\n\n\n

El equipo de lanzamiento 6.5

\n\n\n\n

Cada lanzamiento tiene muchas partes móviles con sus propios triunfos y desafíos. Se necesita un equipo dedicado de colaboradores entusiastas para ayudar a mantener las cosas encaminadas y avanzando sin problemas. 6.5 es posible gracias a un grupo multifuncional de contribuyentes, siempre listos para defender ideas, eliminar obstáculos y resolver problemas.

\n\n\n\n\n\n\n\n

Gracias contribuyentes.

\n\n\n\n

WordPress cree en democratizar la publicación y las libertades que conlleva el código abierto. Apoyando esta idea hay una comunidad global y diversa de personas que colaboran para fortalecer el software.

\n\n\n\n

WordPress 6.5 refleja los innumerables esfuerzos y la pasión de alrededor de 700 colaboradores en al menos 57 países. ¡Este lanzamiento también dio la bienvenida a más de 150 contribuyentes nuevos!

\n\n\n\n

Su colaboración generó más de 2,500 mejoras y correcciones, lo que garantizó una versión estable para todos, un testimonio del poder y la capacidad de la comunidad de código abierto de WordPress.

\n\n\n\n

!Benni · _ck_ · Aaron Jorbin · Aaron Robertshaw · Abha Thakor · abletec · acosmin · Adam Silverstein · Adarsh Akshat · admcfajn · Ahmed Chaion · Ahmed Saeed · Akash Muchandikar · Aki Hamano · Akira Tachibana · akmelias · Akramul Hasan · Akshaya Rane · Alain Schlesser · Alan Fuller · Alex · Alex Concha · Alex King · Alex Kirk · Alex Lende · Alex Mills · Alex Stine · Alexander · Alexandre Buffet · Amber Hinds · Amy Hendrix (sabreuse) · Amy Kamala · Anand Upadhyay · Anders Norén · Andrea Fercia · Andrei Draganescu · Andrei Lupu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Norcross · Andrew Ozz · Andrew Serong · andrewleap · Andrii Balashov · André Maneiro · Andy Fragen · Andy Peatling · Aneesh Devasthale · Ankit K Gupta · Ankit Panchal · Anne McCarthy · Anthony Burchell · Antoine · Anton Lukin · Anton Timmermans · Anton Vlasenko · Antonella · Antonio D. · Antonis Lilis · arena94 · Ari Stathopoulos · Arslan Kalwar · Artemio Morales · Arthur Chu · Arun Chaitanya Jami · Arun Sharma · Arunas Liuiza · Asad Polash · Ashish Kumar (Ashfame) · Asish Chandra Mohon · audunmb · Aurooba Ahmed · Austin Matzko · axwax · Ayesh Karunaratne · Béryl de La Grandière · bahia0019 · Balu B · bangank36 · Barry · Barry · Bart Kalisz · bartkleinreesink · Beatriz Fialho · Beau Lebens · Beda · ben · Ben Dwyer · Ben Hansen · Ben Huson · Ben Lobaugh (blobaugh) · Ben Ritner – Kadence WP · Ben Word · Benjamin Zekavica · benjaminknox · Benoit Chantre · Bernhard Reiter · bernhard-reiter · billseymour · Biplav · Birgit Pauli-Haack · bobbingwide · Boone Gorges · born2webdesign · Brad Jorsch · Brad Parbs · Brad Williams · Brandon Kraft · Brandon Lavigne · Brian Coords · Brian Fischer · Brian Gardner · Brian Haas · Brian Henry · Brooke · burnuser · camya · Carlo Cannas · Carlos Bravo · Carlos G. P. · Carolina Nymark · cenkdemir · cfinnberg · Chad Chadbourne · chased@si.edu · chiilog (Chiaki Okamoto) · Chouby · Chris David Miles · Chris Reynolds · chriscct7 · christian-dale · Christopher · Chrystl · codepo8 · Colin Devroe · Colin Stewart · Corey Worrell · Cory Birdsong · Courtney Robertson · Creative Slice · crstauf · Cullen Whitmore · Cupid Chakma · cvorko · cybeardjm · Cyberchicken · Damon Cook · Dan Soschin · Daniel Bachhuber · Daniel Dvorkin · Daniel Käfer · Daniel Richards · Daniel Schutzsmith · danieldudzic · Daniele Scasciafratte · danieltj · darerodz · Darren Ethier (nerrad) · Darshit Rajyaguru · darssen · David Artiss · David Baumwald · David Biňovec · David Calhoun · David Herrera · David Levine · David Lingren · David Perez · David Smith · Dean Sas · Denis de Bernardy · Denis Žoljom · Dennis Hipp · Dennis Snell · Dennys Dionigi · Derek Blank · Derek Herman · Derek Springer · designsimply · Desrosj Bot · Devin Curtis · Devin Walker · Dharmesh Patel · Dhrumil Kumbhani · Dhruvi Shah · Dilip Bheda · Dion Hulse · Dominik Schilling · Dougal Campbell · Drew Jaynes · Dustin Falgout · Earle Davies · Ehtisham Siddiqui · Ella van Durpe · Emerson Maningo · emirpprime · Emmanuel Hesry · Endymion00 · Eric Andrew Lewis · Erick Hitter · Erik · Estela Rueda · Fabian Kägy · Fabian Todt · Fabio Rubioglio · Faisal Ahammad · Faisal Ahmed · Faisal Alvi · Fanly · Feast Design Co. · Felipe Elia · Felix Arntz · fgiannar · Florent Hernandez · Francesca Marano · FrancescoCarlucci · Frank Jäger · Frank Laszlo · Frank Wazeter · fushar · Gajendra Singh · Gan Eng Chin · Garbiñe · Gary Pendergast · gavande1 · Gennady Kovshenin · George Mamadashvili · George Stephanis · Gerard Reches · Gerardo Pacheco · Girish Panchal · Giuseppe Mazzapica · Glen Davies · goldenapples · Grant M. Kinney · Greg Ziółkowski · gregbenz · Guido Scialfa · gvgvgvijayan · H.M. Mushfiqur Rahman · hanneslsm · Hardik Raval · Hareesh S · Harsh Gajipara · Harsh Patel · Hasanuzzaman Shamim · Heather Lounsbury · Heiko Lübbe · Helen Hou-Sandi · HelgaTheViking · Hemant Tejwani · Hidekazu Ishikawa · Himani Panchal · Hit Bhalodia · Hitesh Talpada · Hossein · Howdy_McGee · Hridoy Mozumder · Hrithik Dalal · Hugh Lashbrooke · Hugo Chinchilla · hugod · huubl · Huzaifa Al Mesbah · Héctor Prieto · Ian Belanger · Ian Dunn · idad5 · Ignacio Cruz Moreno · ignatiusjeroe · Ihtisham Zahoor · Ilya Zolotov · ironprogrammer · Isabel Brison · iseulde · IT Path Solutions · itecrs · Ivan Zhuck · Jacob Cassidy · jadpm · James Collins · James Koster · James Roberts · Jamie Blomerus · Jamie Perrelet · Jan Thiel · jane · Janis Elsts · jansan · Japh · Jarda Snajdr · jarednova · Jason Adams · Jason Crist · Jason Crouse · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Casares · Jayadevan k · jbobich · Jean-Baptiste Audras · Jeff Ong · Jeffrey de Wit · Jeffrey Paul · Jenny Dupuy · Jeremy Felt · Jeremy Herve · jeryj · Jesús Amieiro · Jessica Lyschik · jghazally · Jip Moors · jivygraphics · jltallon · Joan · Joe · Joe Dolson · Joe Hoyle · Joe McGill · Joel James · Joen A. · John Blackbourn · John James Jacoby · johnciacia · Jon Brown · Jon Cave · Jon Surrell · Jonathan Bossenger · Jonathan Brinley · Jonathan Desrosiers · Jonny Harris · joppuyo · jordesign · Jorge Costa · Jorge Vilchez · jornp · Joseph Fusco · Josepha · joshcanhelp · joshuatf · Joy · JR Tashjian · JS Morisset · Juan Aldasoro · JuanMa Garrido · Juhi Saxena · Juliette Reinders Folmer · Justin Tadlock · K M Ashikur Rahman · K. Adam White · KafleG · Kai Hao · Kamrul Hasan · Kari Anderson · Karlijn Bok · Karol Manijak · Karthik Thayyil · Katka · kawsaralameven · Kelly Choyce-Dwan · Kevin Batdorf · Kevin Coleman · Kevin Taron · Kharis Sulistiyono · Kira Schroder · Kishan Jasani · kitchin · Kjell Reigstad · kkmuffme · Knut Sparhell · Koen Reus · Koesper · Konstantin Obenland · Krupa Nanda · Krupal Panchal · Kurt Payne · Kushang Tailor · Kylen Downs · lau@mindproducts.com.au · Laura Adamonis · Lauren Stein · Laurent MILLET · Lax Mariappan · Lena Morita · Leo Muniz · Leonardus Nugraha · Liam Gladdy · LiamMcArthur · Linkon Miyan · liviopv · lkraav · logikal16 · Lovekesh Kumar · luboslives · lucasbustamante · Luis Felipe Zaguini · Luis Herranz · Lukas Pawlik · Lukasz · Luke Cavanagh · Maarten · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahbub Hasan Imon · mahnewr · Mahrokh · Malae · manfcarlo · manyourisms · Marc_J · Marcelo de Moraes Serpa · Marco Ciampini · Marcoevich · margolisj · Marie Comet · Marin Atanasov · Mario Santos · Marius L. J. · Mark Howells-Mead · Mark Jaquith · Marko Heijnen · Markus · martin.krcho · Mary Baum · mathewemoore · Matias Benedetto · Matias Ventura · matiasrecondo77 · Matt Mullenweg · Matteo Enna · Max Lyuchin · Maxime Pertici · Mayur Prajapati · Md Hossain Shohel · Md HR Shahin · Meg Phillips · megane9988 · Mel Choyce-Dwan · melcarthus · meta4 · metropolis_john · mevolkan · Micah Wood · Michael Showes · Michal Czaplinski · Michalooki · Miguel Fonseca · miguelsansegundo · Miikka · Mike Bijon · Mike Jolley (a11n) · Mike Schinkel · Mike Schroder · Mikin Chauhan · Milen Petrinski – Gonzo · mimi · mkismy · mnydigital · Mohammad Jangda · Monique Dubbelman · Monzur Alam · Morteza Geransayeh · mreishus · mrwweb · Muhammad Usman Iqbal · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Musarrat Anjum Chowdhury · Naoki Ohashi · Naresh Bheda · Nate Allen · Navjot Singh · neffff · Neil Hainsworth · nendeb · NerdPress · Nick Diego · Nick Halsey · Nick Martianov · nickpagz · Nico · Nicole Furlan · Nicole Paschen Caylor · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nikita · nikmeyer · Nilambar Sharma · Nilo Velez · Niluthpal Purkayastha · Nirav Sherasiya · Nithin John · Nithin SreeRaj · Noah Allen · nosilver4u · Nowell VanHoesen · Nudge Themes · nwjames · obliviousharmony · ockham · oguzkocer · okat · Old account · olegfuture · Olga Gleckler · Paal Joachim Romdahl · Pacicio · pannelars · partyfrikadelle · Pascal Birchler · Patricia BT · Patrick Lumumba · Paul Bearne · Paul Biron · Paul de Wouters · Paul Kevan · Paul Wong-Gibbs · pavelevap · Peter Baylies · Peter Rubin · Peter Westwood · Peter Wilson · petitphp · Philipp Bammes · Philipp15b · Phill · Pieterjan Deneys · Pippin Williamson · Pitam Dey · pmeenan · Pooja Derashri · Pooja N Muchandikar · pooja9712 · pouicpouic · Prashant Baldha · Pratik Kumar · Prem Tiwari · Presskopp · presstoke · prionkor · Rafiq · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Rashi Gupta · rawrly · rcain · rebasaurus · Remy Perona · Renatho (a11n) · Rene Hermenau · retrofox · Riad Benguella · Rich Collier · Rich Tabor · Rishi Mehta · Rishi Shah · Robert Anderson · Rolf Allard van Hagen · room34 · Ryan Boren · Ryan McCue · Ryan Welcher · Ryann Micua · Ryo · Sé Reed · Sébastien SERRE · Sabbir Hasan · Sachyya · Sadi Mohammad Zaman · sadpencil · Sahil · Saiduzzaman Tohin · Sakib MD Nazmush · Sal Ferrarello · samba45 · Sampat Viral · Samuel Rüegger · Samuel Sidler · Samuel Wood (Otto) · Santiago Cerro López · Sarah Norris · Sarath AR · Satyam Vishwakarma (Satya) · Saxon Fletcher · Sayful Islam · Scott Kingsley Clark · Scott Taylor · scribu · Sergey Biryukov · Sergio de Falco · Seth Rubenstein · Shaharia Azam · Shail Mehta · ShaneF · Shannon Smith · shaunandrews · Shawn Hooper · shidouhikari · Shipon Karmakar · Shreyash Srivastava · Shubham Sedani · siddharth ravikumar · Siobhan · Sirajum Mahdi · sjregan · Soren Wrede · SourceView · sruthi89 · stacimc · Stefano Minoia · Stephen Bernhardt · Stephen Cronin · Stephen Edgar · Stephen Harris · Steven Lin · strarsis · Subrata Sarkar · Sumi Subedi · Sumit Bagthariya · Sumit Singh · SunilPrajapati · Svitlana Sukhoveiko · syamraj24 · Sybre Waaijer · Syed Balkhi · Syed Nuhel · Synchro · Takashi Irie · Takashi Kitajima · Tammie Lister · Tapan Kumer Das · Tara King · Taylor · Taylor Dewey · Taylor Gorman · tazotodua · Teddy Patriarca · Tellyworth · Thakor Darshil · them.es · thinkluke · Thomas Griffin · Thomas Kräftner · threadi · Tim Nolte · timbroddin · Timothée Brosille · Timothy Jacobs · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tom Cafferkey · Tom Finley · Tom J Nowell · tomluckies · Tomoki Shimomura · tomsommer · tomxygen · Toni Viemerö · Tonya Mork · Toro_Unit (Hiroshi Urabe) · torres126 · Torsten Landsiedel · Toru Miki · toscho · Travis Smith · tropicalista · Trupti Kanzariya · Ugyen Dorji · upadalavipul · Utsav Patel · Utsav tilava · Uttam Kumar Dash · valerogarte · Vicente Canales · vikram6 · viliamkopecky · Vipul Ghori · vivekawsm · vladimiraus · vortfu · Vraja Das · Wasiur Rahman · welaunchio · Weston Ruter · WHSajid · WP Corner · xlthlx · Yan Sern · Yannis Guyon · Yui · Yuliyan Slavchev · Yuvrajsinh Sisodiya · Zack Tollman · Zane Matthew · zieladam · Zunaid Amin · Česlav Przywara

\n\n\n\n

Más de 70 regiones han traducido el 90 por ciento o más de WordPress 6.5 a su idioma. Los traductores de la comunidad están trabajando arduamente para garantizar que haya más traducciones en camino. Gracias a todos los que ayudan a que WordPress esté disponible en 200 idiomas.

\n\n\n\n

Por último, pero no menos importante, gracias a los voluntarios que contribuyen a los foros de soporte respondiendo preguntas de los usuarios de WordPress de todo el mundo.

\n\n\n\n

Involúcrate y contribuye

\n\n\n\n

La participación en WordPress no se limita a la codificación. Si le atrae contribuir, aprender más e involucrarse es fácil. Descubre los equipos que se unen en Make WordPress y utiliza esta herramienta interactiva para ayudarte a decidir cuál es la adecuada para ti.

\n\n\n\n

Un haiku más

\n\n\n\n

¡6.5 ya está aquí!
Juega, interactúa, construye mejor,
Más fuerte y más rápido.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://es-mx.wordpress.org/2024/04/03/wordpress-6-5-regina/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"1021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"El mes en WordPress: Febrero 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://es-mx.wordpress.org/2024/03/08/el-mes-en-wordpress-febrero-2024/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://es-mx.wordpress.org/2024/03/08/el-mes-en-wordpress-febrero-2024/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Mar 2024 18:19:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"Mes en WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://es-mx.wordpress.org/?p=1016\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:377:\"En febrero se produjo un progreso significativo hacia el próximo lanzamiento de WordPress 6.5 y los preparativos finales para WordCamp Asia. Se publicaron los resultados de la encuesta anual de WordPress y comenzaron las discusiones sobre los próximos pasos del proyecto de liberación de datos. Sigue leyendo para conocer los últimos acontecimientos en el espacio […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:9577:\"\n

En febrero se produjo un progreso significativo hacia el próximo lanzamiento de WordPress 6.5 y los preparativos finales para WordCamp Asia. Se publicaron los resultados de la encuesta anual de WordPress y comenzaron las discusiones sobre los próximos pasos del proyecto de liberación de datos. Sigue leyendo para conocer los últimos acontecimientos en el espacio de WordPress.

\n\n\n\n\n\n\n\n

Prepárate para WordCamp Asia

\n\n\n\n

El escenario está listo para el primer evento emblemático de WordPress del año en Taipei, Taiwán. WordCamp Asia 2024 comenzó el 7 de marzo y promete tres días de aprendizaje, networking e inspiración.

\n\n\n\n

El calendario de este año presenta una extensa lista de oradores, incluidos los invitados Josepha Haden Chomphosy, Ben Thompson, Noel Tock, y JU-CHUN KO. Para concluir la cumbre, los asistentes pueden interactuar con el cofundador de WordPress, Matt Mullenweg, en una sesión de preguntas y respuestas. Descubre cómo enviar tus preguntas.

\n\n\n\n

¿No puedes llegar a Taipei? Ve la transmisión en vivo del evento en el canal de YouTube de WordPress.

\n\n\n\n

Cuenta atrás para WordPress 6.5

\n\n\n\n

WordPress 6.5 está en camino para su tan esperado lanzamiento el 26 de marzo. Después de los lanzamientos beta del mes pasado, la primera versión candidata (RC1) ya está disponible para pruebas, lo que marca otro hito en el ciclo de desarrollo.

\n\n\n\n

Esta versión importante agregará delicadeza y ajuste a la forma en que controla su experiencia de creación de sitios, con mucho que explorar específicamente para los desarrolladores. Obtén una descripción detallada de las funciones destacadas en el anuncio de la Beta 1.

\n\n\n\n

Nuevo en el plugin Gutenberg

\n\n\n\n

En febrero se enviaron dos nuevas versiones de Gutenberg:

\n\n\n\n\n\n\n\n

Actualizaciones del equipo

\n\n\n\n\n\n\n\n

Solicitudes de comentarios y pruebas

\n\n\n\n\n\n\n\n

Eventos de WordPress

\n\n\n\n\n\n\n\n
\n\n\n\n

¿Tienes una historia que podríamos incluir en el próximo número de ‘El Mes en WordPress’? Háznoslo saber llenando este formulario (en inglés).

\n\n\n\n

Traducido de wordpress.org/news

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"https://es-mx.wordpress.org/2024/03/08/el-mes-en-wordpress-febrero-2024/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"1016\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"El mes en WordPress: Diciembre 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://es-mx.wordpress.org/2024/01/31/el-mes-en-wordpress-diciembre-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://es-mx.wordpress.org/2024/01/31/el-mes-en-wordpress-diciembre-2023/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 31 Jan 2024 20:00:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"Mes en WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://es-mx.wordpress.org/?p=1010\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:315:\"A medida que 2023 llegaba a su fin, WordPress se despidió con el tan esperado State of the Word y la hoja de ruta 6.5, entre otras actualizaciones interesantes. Sigue leyendo para obtener más información sobre las celebraciones de fin de año de la comunidad y echar un vistazo a lo que nos espera para […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:10525:\"\n

A medida que 2023 llegaba a su fin, WordPress se despidió con el tan esperado State of the Word y la hoja de ruta 6.5, entre otras actualizaciones interesantes.

\n\n\n\n

Sigue leyendo para obtener más información sobre las celebraciones de fin de año de la comunidad y echar un vistazo a lo que nos espera para el próximo año.

\n\n\n\n\n\n\n\n

Aspectos destacados del State of the Word

\n\n\n\n

El 11 de diciembre, el cofundador de WordPress, Matt Mullenweg, pronunció su discurso anual sobre el State of the Word en Madrid, España, marcando la primera edición internacional del evento. Casi 200 entusiastas de WordPress y líderes de la industria tecnológica se reunieron en persona para escuchar lo que sigue para WordPress, con una gran audiencia uniéndose en línea o desde una de las 47 fiestas de observación celebradas en 18 países.

\n\n\n\n

El discurso de apertura destacó los hitos del año pasado y mostró demostraciones convincentes, brindando una idea de los próximos desarrollos para el editor del sitio, la fase de colaboración y el rediseño del administrador. Matt también presentó el enfoque de 2024 en la liberación de datos, con el objetivo de desbloquear barreras digitales y migraciones sin fricciones a WordPress para una web más abierta.

\n\n\n\n
\n\n
\n\n\n\n

El evento concluyó con una sesión de preguntas y respuestas y esta entrada de seguimiento.

\n\n\n\n

Hoja de ruta hacia WordPress 6.5

\n\n\n\n

El lanzamiento de WordPress 6.5 está programado para el 26 de marzo de 2024. Esta versión importante presentará una nueva biblioteca de fuentes para una fácil administración global de fuentes, soporte para herramientas de apariencia en temas clásicos, vistas de datos para plantillas y patrones, y revisiones más completas en todo el mundo. experiencia en edición, entre otros aspectos destacados.

\n\n\n\n

6.5 también incluirá nuevas API como Interactividad, Campos personalizados y Enlace de bloques que amplían las capacidades de bloque y respaldan funciones como Anulaciones de patrones sincronizados.

\n\n\n\n

Obtén más información sobre las funciones previstas para WordPress 6.5 en esta entrada de hoja de ruta.

\n\n\n\n
\n

No esperes a la próxima versión para optimizar sus flujos de trabajo creativos con estas potentes herramientas del Editor del sitio.

\n
\n\n\n\n

Nuevo en el plugin Gutenberg

\n\n\n\n

En diciembre se enviaron dos nuevas versiones de Gutenberg:

\n\n\n\n\n\n\n\n

Actualizaciones del equipo

\n\n\n\n\n\n\n\n

Eventos de WordPress

\n\n\n\n\n\n\n\n
\n\n\n\n

¿Tienes una historia que podríamos incluir en el próximo número de ‘El Mes en WordPress’? Háznoslo saber llenando este formulario (en inglés).

\n\n\n\n

Las siguientes personas contribuyeron a este mes en WordPress: Bernard Meyer, Nicholas Garofalo, y Lauren Stein

\n\n\n\n

Traducido de wordpress.org/news

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://es-mx.wordpress.org/2024/01/31/el-mes-en-wordpress-diciembre-2023/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"1010\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"El mes en WordPress: Octubre 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://es-mx.wordpress.org/2023/11/15/el-mes-en-wordpress-octubre-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Nov 2023 13:42:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"Mes en WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://es-mx.wordpress.org/?p=1004\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:1989:\"\n\n
\n \n
\n \n

Suscríbete para seguir leyendo

\n \n \n

\n Conviértete en suscriptor de pago para obtener acceso al resto de esta entrada y otro contenido exclusivo.\n

\n \n \n
\n \n \n \n
\n \n
\n \n
\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"1004\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:79:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 6.4.1: Actualización de mantenimiento\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://es-mx.wordpress.org/2023/11/09/wordpress-6-4-1-actualizacion-de-mantenimiento/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"https://es-mx.wordpress.org/2023/11/09/wordpress-6-4-1-actualizacion-de-mantenimiento/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 14:24:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:15:\"Actualizaciones\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:13:\"Mantenimiento\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://es-mx.wordpress.org/?p=1001\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:380:\"¡WordPress 6.4.1 ya está disponible! Esta versión menor presenta cuatro correcciones de errores. Puedes revisar un resumen de las actualizaciones de mantenimiento en esta versión leyendo el anuncio de la versión candidata o viendo la lista de tickets en Trac. WordPress 6.4.1 es una versión de ciclo corto. Si tienes sitios que admiten actualizaciones automáticas […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6118:\"\n

¡WordPress 6.4.1 ya está disponible!

\n\n\n\n

Esta versión menor presenta cuatro correcciones de errores. Puedes revisar un resumen de las actualizaciones de mantenimiento en esta versión leyendo el anuncio de la versión candidata o viendo la lista de tickets en Trac.

\n\n\n\n\n\n\n\n

WordPress 6.4.1 es una versión de ciclo corto. Si tienes sitios que admiten actualizaciones automáticas en segundo plano, el proceso de actualización comenzará automáticamente. Si tu sitio no se actualiza automáticamente, también puedes actualizarlo desde tu Escritorio de WordPress.

\n\n\n\n

Puedes descargar WordPress 6.4.1 desde WordPress.org o visitar tu Escritorio de WordPress, hacer clic en “Actualizaciones” y luego hacer clic en “Actualizar ahora”.

\n\n\n\n

Para obtener más información sobre esta versión, visita el sitio HelpHub.

\n\n\n\n

Gracias a estos contribuyentes de WordPress

\n\n\n\n

Este lanzamiento fue dirigido por Aaron Jorbin y Tonya Mork. Gracias a todos los que probaron RC y 6.4.1 y generaron informes.

\n\n\n\n

WordPress 6.4.1 no habría sido posible sin las contribuciones de las siguientes personas. Su coordinación rápida y concertada para implementar correcciones de mantenimiento en una versión estable es un testimonio del poder y la capacidad de la comunidad de WordPress.

\n\n\n\n

@afragen @clorith @desrosj @pbiron @schlessera @azaozz @davidbaumwald @tomsommer @nexflaszlo @howdy_mcgee @baxbridge @earnjam @timothyblynjacobs @johnbillion @flixos90 @joedolson @jeffpaul @zunaid321 @courane01 @audrasjb @tacoverdo @ironprogrammer @webcommsat @otto42 @barry @chanthaboune @rajinsharwar @aaroncampbell @peterwilsoncc @anandau14 @iandunn @matthewjho @coffee2code @boogah @jason_the_adams @joemcgill @johnjamesjacoby @jrf @renehermi @dlh @mukesh27 @sumitbagthariya16 @starbuck @sergeybiryukov

\n\n\n\n

Cómo contribuir

\n\n\n\n

Para participar en el desarrollo central de WordPress, diríjete a Trac, selecciona un ticket y únete a la conversación en el canal #core. ¿Necesitas ayuda? Consulta el Manual del colaborador principal.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"https://es-mx.wordpress.org/2023/11/09/wordpress-6-4-1-actualizacion-de-mantenimiento/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"1001\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:79:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"WordPress 6.4 “Shirley”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://es-mx.wordpress.org/2023/11/09/wordpress-6-4-shirley/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://es-mx.wordpress.org/2023/11/09/wordpress-6-4-shirley/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Nov 2023 14:18:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:15:\"Actualizaciones\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:12:\"Lanzamientos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://es-mx.wordpress.org/?p=988\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:334:\"Saluda a WordPress 6.4 “Shirley”, que lleva el nombre de la icónica artista de jazz Shirley Horn. Su voz distintiva y su extraordinaria conexión con el piano la establecieron como una de las principales músicos de jazz de su generación. El viaje de Horn desde la escena del jazz de Washington D.C. hasta el escenario […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:75814:\"\n
\"\"
\n\n\n\n

Saluda a WordPress 6.4 “Shirley”, que lleva el nombre de la icónica artista de jazz Shirley Horn. Su voz distintiva y su extraordinaria conexión con el piano la establecieron como una de las principales músicos de jazz de su generación. El viaje de Horn desde la escena del jazz de Washington D.C. hasta el escenario internacional es un testimonio de su dedicación y perseverancia. Su influencia llegó mucho más allá de los límites del jazz tradicional, rompiendo fronteras e inspirando a audiencias de todo el mundo.

\n\n\n\n\n\n\n\n

Disfruta del ritmo suave de la música de Shirley Horn mientras disfrutas de todo lo que ofrece 6.4.

\n\n\n\n

Esta última versión de WordPress presenta un tema predeterminado nuevo y versátil y un conjunto de actualizaciones para potenciar cada paso de su viaje creativo. Elabora tu contenido sin problemas con más mejoras de redacción. Explora más formas de hacer realidad su visión y optimizar la edición del sitio con herramientas mejoradas. Si eres nuevo en WordPress o un creador experimentado, “Shirley” tiene algo para ti. Descubre la flexibilidad inigualable de construir con bloques y deja volar tus ideas.

\n\n\n\n
\n

Muchas de las características y mejoras de WordPress 6.4 se incluyen en la categoría “pequeñas pero poderosas”. Junto con la belleza adaptable del tema Twenty Twenty-Four, estas actualizaciones ayudan a los creadores de contenido y desarrolladores de sitios a ahorrar tiempo y esfuerzo al tiempo que brindan la experiencia de WordPress de alto valor y sin complicaciones que el mundo espera.

\nJosepha Haden Chomphosy, directora ejecutiva de WordPress
\n\n\n\n
\n
¡Descarga WordPress 6.4 hoy!
\n
\n\n\n\n

¿Qué hay dentro 6.4?

\n\n\n\n

Conoce Twenty Twenty-Four

\n\n\n\n

Experimente la edición de sitios en su máxima expresión con Twenty Twenty-Four. Este nuevo tema predeterminado multifacético ha sido cuidadosamente diseñado teniendo en mente tres casos de uso distintos, desde escritores y artistas hasta emprendedores. Ahorra tiempo y esfuerzo con su extensa colección de más de 35 plantillas y patrones y descubre un mundo de posibilidades creativas con algunos ajustes. La notable flexibilidad de Twenty Twenty-Four garantiza una adaptación ideal para casi cualquier tipo de sitio. Compruébalo en esta demostración.

\n\n\n\n
\"\"
\n\n\n\n

Deja que tu escritura fluya

\n\n\n\n

Las nuevas mejoras garantizan que tu proceso de creación de contenido sea fluido. Encuentra nuevos atajos de teclado en la Vista de lista, combinación de listas más inteligente y control mejorado sobre la configuración de enlaces. Una experiencia de barra de herramientas coherente para los bloques de Navegación, Lista y Cotización le permite trabajar de manera eficiente con las opciones de herramientas que necesita.

\n\n\n\n
\"\"
\n\n\n\n

La paleta de comandos acaba de mejorar

\n\n\n\n

Introducida por primera vez en WordPress 6.3, la paleta de comandos es una poderosa herramienta para encontrar rápidamente lo que necesitas, realizar tareas de manera eficiente y acelerar el flujo de trabajo de su construcción. Disfruta de un diseño renovado y nuevos comandos para realizar acciones específicas de bloques en esta versión.

\n\n\n\n
\"\"
\n\n\n\n

Categorizar y filtrar patrones

\n\n\n\n

Los patrones son una excelente manera de aprovechar el potencial de los bloques y simplificar el proceso de creación de tu sitio. WordPress 6.4 te permite organizarlos con categorías personalizadas. Además, el nuevo filtrado avanzado en la sección Patrones del insertador hace que encontrar todos sus patrones sea más intuitivo.

\n\n\n\n
\"\"
\n\n\n\n

Se creativo con más herramientas de diseño

\n\n\n\n

Crea diseños atractivos y funcionales con un conjunto ampliado de herramientas de diseño. Juega con imágenes de fondo en bloques de grupo para obtener diseños únicos y mantén las dimensiones de la imagen consistentes con las proporciones de aspecto del marcador de posición. ¿Quieres agregar botones a tu bloque de navegación? Ahora puedes hacerlo cómodamente sin una línea de código.

\n\n\n\n
\"\"
\n\n\n\n

Haz que tus imágenes destaquen

\n\n\n\n

Habilita la funcionalidad de caja de luz para permitir que los visitantes de su sitio disfruten de imágenes interactivas en pantalla completa al hacer clic. Aplícalo globalmente o a imágenes específicas para personalizar la experiencia de visualización.

\n\n\n\n
\"\"
\n\n\n\n

Cambia el nombre de los bloques de grupo

\n\n\n\n

Pónle un nombre personalizado a los bloques de grupo para organizar y distinguir áreas de su contenido fácilmente. Estos nombres serán visibles en la Vista de lista.

\n\n\n\n
\"\"
\n\n\n\n

Vista previa de imágenes en vista de lista

\n\n\n\n

Las nuevas vistas previas de los bloques de Galería e Imágenes en la Vista de lista le permiten visualizar y ubicar dónde están las imágenes de tu contenido de un vistazo.

\n\n\n\n
\"\"
\n\n\n\n

Compartir patrones entre sitios

\n\n\n\n

¿Necesitas utilizar tus patrones personalizados en otro sitio? Importarlos y exportarlos como archivos JSON desde la vista de patrones del Editor del sitio.

\n\n\n\n
\"\"
\n\n\n\n

Presentación de los bloques Hooks

\n\n\n\n

Los bloques Hooks permiten a los desarrolladores insertar automáticamente bloques dinámicos en ubicaciones de contenido específicas, enriqueciendo la extensibilidad de los temas de bloques a través de plugins. Si bien se considera una herramienta para desarrolladores, esta función está diseñada para respetar sus preferencias y le brinda control total para agregar, descartar y personalizar bloques insertados automáticamente según sus necesidades.

\n\n\n\n
\"\"
\n\n\n\n

El rendimiento gana

\n\n\n\n

Esta versión incluye más de 100 actualizaciones relacionadas con el rendimiento para una experiencia más rápida y eficiente. Las mejoras notables se centran en el rendimiento de carga de plantillas para temas (incluido Twenty Twenty-Four), el uso de estrategias de carga de scripts “diferidas” y “asíncronas” en el núcleo, los bloques y los temas, y la optimización de las opciones de carga automática.

\n\n\n\n

Aspectos destacados de la accesibilidad

\n\n\n\n

Cada lanzamiento se compromete a hacer que WordPress sea accesible para todos. WordPress 6.4 trae varias mejoras en la Vista de lista y compatibilidad con etiquetas aria para el bloque de Navegación, entre otras cosas destacadas. La interfaz de usuario del administrador incluye mejoras en la ubicación de los botones, el contexto de los elementos del menú “Agregar nuevo” y los mensajes hablados sobre el estado del sitio. Obtén más información sobre todas las actualizaciones destinadas a mejorar la accesibilidad.

\n\n\n\n

Otras notas de interés

\n\n\n\n\n\n\n\n

Obtén más información sobre WordPress 6.4

\n\n\n\n

Consulta la nueva página de WordPress 6.4 para obtener más información sobre las numerosas mejoras y características de esta versión.

\n\n\n\n

Explora Learn WordPress para ver videos instructivos rápidos, talleres en línea y otros recursos gratuitos para mejorar sus conocimientos y habilidades de WordPress.

\n\n\n\n

Si buscas notas técnicas detalladas sobre nuevos cambios, la Guía de campo de WordPress 6.4 es para ti. No olvides suscribirte al Blog para desarrolladores para estar al tanto de las últimas actualizaciones de desarrollo, tutoriales y más.

\n\n\n\n

Para obtener más información sobre instalación, correcciones y cambios de archivos, visita las notas de la versión 6.4.

\n\n\n\n

El equipo de lanzamiento 6.4

\n\n\n\n

​​La versión WordPress 6.4 llega de la mano de un equipo de lanzamiento de género subrepresentado para dar la bienvenida y potenciar diversas voces en el proyecto de código abierto de WordPress.

\n\n\n\n
\n

Ser parte del equipo de coordinación de la versión 6.4 me ha permitido observar de cerca el intrincado proceso de lanzamiento, donde cada detalle, por menor que sea, se aborda meticulosamente, teniendo en cuenta varios factores como el rendimiento y la compatibilidad con versiones anteriores. Todavía hay mucho que aprender, pero me siento afortunado de haber tenido la oportunidad de contribuir a WordPress 6.4.

\nAkshaya Rane, miembro del equipo coordinador de la versión 6.4
\n\n\n\n

Durante varias semanas, el equipo de lanzamiento 6.4 mantuvo el lanzamiento encaminado y avanzó liderando el trabajo colectivo, conectando ideas y eliminando obstáculos.

\n\n\n\n\n\n\n\n

Gracias contribuyentes.

\n\n\n\n

WordPress cree en democratizar la publicación y las libertades que conlleva el código abierto. Apoyando esta idea hay una comunidad global y diversa de personas que trabajan juntas para fortalecer el software.

\n\n\n\n

WordPress 6.4 refleja los innumerables esfuerzos y la pasión de más de 600 contribuyentes en al menos 56 países. ¡Este lanzamiento también dio la bienvenida a más de 170 contribuyentes nuevos!

\n\n\n\n

Su colaboración generó más de 1150 mejoras y correcciones, lo que garantizó una versión estable para todos, un testimonio del poder y la capacidad de la comunidad de código abierto de WordPress.

\n\n\n\n

6adminit · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · aayusha · Abha Thakor · Abid Omar · Adam Silverstein · Adhun Anand · admcfajn · adrianduffell · aegkr · ahardyjpl · Ahmed Hussein · Ahmed Kabir Chaion · ajakaroth · Aki Hamano · Akihiro Harai · Akira Tachibana · Akshaya Rane · Al-Amin Firdows · Alain Schlesser · Albert Juhé Lluveras · Alex Concha · Alex King · Alex Lende · Alex Stine · Alexandre Buffet · Alisha Bajracharya · Allison Tarr · Alvi Tazwar · amedv · Ana Cirujano · Anand Upadhyay · Anders Norén · André · Andrea Fercia · Andrei Draganescu · Andrew Hayward · Andrew Hutchings · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · Andy Fragen · Andy Peatling · Ankit Gade · Ankit K Gupta · Ankit Panchal · Anna · Anne Katzeff · Anne McCarthy · Anne-Mieke Bovelett · anphira · Anthony Burchell · Anton Plauche · Anton Timmermans · Anton Vlasenko · Anveshika Srivastava · archon810 · arena · Ari Stathopoulos · Arnab Mondal · Artemio Morales · Arthur Chu · asafm7 · Aslam Doctor · Aurooba Ahmed · Austin Ginder · Ayesh Karunaratne · azharckra · Balu B · bangank36 · barbmiller · Barry · Bart · Basilis Kanonidis · Beatriz Fialho · behoney · ben · Ben Dwyer · Ben Greeley · Ben Hansen · Benjamin Intal · Benjamin Zekavica · benjaminknox · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bhrugesh Bavishi · Bijay Yadav · Binsaifullah · Biplav · Birendra Dhami · Birgit Olzem · Birgit Pauli-Haack · Block Themes Pro · bmalsht · bonger · bookwyrm · Boone Gorges · Boro Sitnikovski · Brad Jorsch · Bradley Jacobs · Brandon Kraft · Brandon Vreeman · Brian Gardner · Brian Haas · Brooke · Brooke. · Bud Kraus · Caleb Burks · Calvin Alkan · Carlo Cannas · Carlos Bravo · Carlos G. P. · Carolina Nymark · Cathi Bosco · ceer · cenkdemir · Chad Chadbourne · chased@si.edu · Chintan hingrajiya · Chip Bennett · Chloé Bringmann · Chris Runnells · chriscct7 · chrisdesrochers · codersantosh · Colin Stewart · Corey Worrell · Courtney Patubo Kranzke · Courtney Robertson · Crisoforo Gaspar · crstauf · Csaba (LittleBigThings) · Cupid Chakma · cybeardjm · Cyberchicken · Daisuke Takahashi · Dajeema Rai · Damon Cook · Damon Sharp · Dan Tovbein · Daniel Bachhuber · Daniel Richards · danieldudzic · Daniele Scasciafratte · Danielle Zarcaro · danieltj · darerodz · Darin Kotter · darkfate · Darren Ethier (nerrad) · Darshit Rajyaguru · Dave Loodts · dave03 · David Baumwald · David Biňovec · David Calhoun · David E. Smith · David Favor · David Herrera · David Ryan · David Smith · Dawid Urbanski · daxelrod · De Belser Arne · Dean Sas · Dee Teal · Deepak Vijayan · Denis Žoljom · Dennis Snell · Derek Blank · Derrick Tennant · Devan Ferguson · Dharmesh Patel · Dhrumil Kumbhani · Dhruvi Shah · Diane Co · Dilip Bheda · Dimitris Mitsis · Dion Hulse · DJ · dj.cowan · Dominik Schilling · doughamlin · Drew Jaynes · Earle Davies · Ebonie Butler · Edi Amin · Edward Caissie · Ehtisham S. · Ella van Durpe · Ellen Bauer · emailjoey · Emerson Maningo · Emily Clarke · Emily Leffler Schulman · emirpprime · enodekciw · Enrico Battocchi · Erik Betshammar · Esrat Sultana Popy · Estela Rueda · Fabian Kägy · Fabian Todt · Fabio Rubioglio · Faisal Alvi · Felipe Elia · Felix Arntz · Femy Praseeth · floydwilde · FolioVision · Francesca Marano · Frank Laszlo · Fredde Battel · fzhantw · Gabriel Koen · Ganesh Dahal · Garrett Hyder · Gary Cao · Gary Pendergast · Gennady Kovshenin · George Hotelling · George Mamadashvili · Gerardo Pacheco · Gio Lodi · Glen Davies · Gnanasekaran Loganathan · Gopal Krishnan · GOZER · gpotter · Grant M. Kinney · Greg Ross · Greg Ziółkowski · gregfuller · Guss77 · Gustavo Bordoni · gvgvgvijayan · Héctor Prieto · H.M. Mushfiqur Rahman · hanneslsm · Hanzala Taifun · Hareesh S · Harsh Gajipara · Hasanuzzaman · Haz · Helen Hou-Sandi · Hemant Tejwani · Hit Bhalodia · hlunter · Howdy_McGee · Huzaifa Al Mesbah · Ian Dunn · Incursa Designs · ironprogrammer · Isabel Brison · itecrs · Ivan Zhuck · jaimieolmstead · Jakaria Istauk · Jake Goldman · Jake Spurlock · James Hunt · James Janco · James Koster · James Roberts · james0r · Jamie McHale · Jamie Perrelet · Jamie VanRaalte · jane · Jarda Snajdr · Jari Vuorenmaa · Jarko Piironen · Jason Adams · Jason Cosper · Jason Crist · jastos · Jean-Baptiste Audras · Jeff Bowen · Jeff Everhart · Jeff Ong · jeffikus · Jeffrey Paul · jeflopo · Jeremy Felt · Jeremy Herve · Jeremy Yip · jeryj · Jesin A · Jessica Duarte · Jessica Goddard · Jessica Lyschik · Jick · Jip Moors · jivygraphics · Joe Dolson · Joe Hoyle · Joe McGill · Joen A. · John Blackbourn · John Hooks · John James Jacoby · John Regan · Jon Brown · Jon Cave · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Joona · Joost de Valk · JordanPak · jordesign · Jorge Costa · Joseph G. · Josepha Haden · joshcanhelp · joshuatf · JR Tashjian · Juan Aldasoro · JuanMa Garrido · Juliette Reinders Folmer · Justin Tadlock · Jyolsna J E · K M Ashikur Rahman · K. Adam White · KafleG · Kai Hao · Kalmang · Kalpesh · Kamrul Hasan · Karlijn Bok · Karol Manijak · Karthik Thayyil · Katie Ayres · kawsaralameven · Keanan Koppenhaver · Kelly Choyce-Dwan · Kevin Fodness · Kevin Miller · Kevin Taron · khleomix · Khokan Sardar · Kim Coleman · Kishan Jasani · kkmuffme · Koji Kuno · Konstantin Kovshenin · Konstantin Obenland · Kopila Shrestha · krokodok · Krupal Panchal · Labun Chemjong · Lance Willett · LarryWEB · lastsplash (a11n) · lau@mindproducts.com.au · launchinteractive · Laura Adamonis · Laura Byrne · laurelfulford · Lauren · Laxmikant Bhumkar · Lee Willis · Lena Morita · Liam Gladdy · Linkon Miyan · Linnea Huxford · Lloyd Budd · Lovekesh Kumar · Luigi · Luis Felipe Zaguini · Luis Herranz · Luke Cavanagh · lunaluna · lyndauwp · Márcio Duarte · maciejmackowiak · madejackson · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahbub Hasan Imon · Mahrokh · Mai · Maja Benke · maltfield · Manesh Timilsina · manfcarlo · Manzoor Wani · marcelle42 · Marcelo de Moraes Serpa · Marco Ciampini · Marco Pereirinha · Marcoevich · margolisj · Marin Atanasov · Mario Santos · Marius L. J. · Mark Jaquith · Marko Ivanovic · Marta Torre · Martijn van der Klis · martin.krcho · Mary Baum · Masoud NKH · mathsgrinds · Matias Benedetto · Matias Ventura · Matt Keys · Matt Watson · Matthaus Klute · Matthew Eppelsheimer · Matthew Farlymn · Matthew Haines-Young · matthewjho · maurodf · Maxwell Morgan · maysi · Md HR Shahin · meagan hanes · Mehedi Hassan · Meher Bala · Mel Choyce-Dwan · mer00x · merel1988 · Michael Arestad · Michael Burridge · Michael Showes · Michal Czaplinski · Michalooki · Michelle Blanchette · Michelle Frechette · Michi91 · Miguel Fonseca · Mikael Korpela · Mike Jolley (a11n) · Mike McAlister · Mike Schinkel · Mike Schroder · Mike Straw · Mikin Chauhan · Milen Petrinski – Gonzo · mimi · mitchellaustin · Monir · Mrinal Haque · mrwweb · Muhammad Arslan · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Mushrit Shabnam · Myles Taylor · Nalini Thakor · nandhuraj · Nazgul · Nazmul Sabuz · Neil Hainsworth · nendeb · Nick Diego · Nicolas Juen · Nicole Furlan · nicomollet · nidhidhandhukiya · Niels Lange · Nihar Ranjan Das · Nik Tsekouras · Nilambar Sharma · Nilo Velez · niravsherasiya7707 · Nitesh Das · Nithin John · Nithin SreeRaj · Noah Allen · Nyasha · ockham · Ohia · okat · Olga Gleckler · Oliver Campion · OllieJones · Paal Joachim Romdahl · pannelars · Pascal Birchler · Paul Biron · Paul Kevan · pavelevap · Pedro Mendonça · pentatonicfunk · Pete Nelson · Peter Wilson · petitphp · petrosparaskevopoulos · Petter Walbø Johnsgård · Phill · Pieterjan Deneys · piyushdeshmukh · Plugin Devs · Pooja Bhimani · Pooja Derashri · Pooja N Muchandikar · pranavjoshi · Prashant · Presskopp · r-c · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Rebekah Markowitz · Remy Perona · ren · Renatho (a11n) · Rene Hermenau · Reyes Martínez · Riad Benguella · Rian Rietveld · Rich Tabor · Robert Anderson · Robert O’Rourke · Robin · robpetrin · Rolf Allard van Hagen · Ryan Duff · Ryan McCue · Ryan Neudorf · Ryan Welcher · Sérgio Gomes · Sagar Tamang · Sajjad Hossain Sagor · Sakib Mohammed · Sal Ferrarello · samba45 · Samir Karmacharya · Sampat Viral · Samuel Wood (Otto) · Sarah Norris · Sarah Williams · Sarath AR · Satish Prajapati · saulirajala · saxonfletcher · Scott Kingsley Clark · Scott Reilly · Scott Taylor · Scout James · scribu · Sergey Biryukov · Sergio Scabuzzo · Seth Rubenstein · Shail Mehta · shawfactor · Shawn Hooper · shilo-ey · Shiva Shanker Bhatta · shresthaaman · Shubham Sedani · Simon Dowdles · Siobhan · Siobhan Bamber · Smit Rathod · sofiashendi · Sonia Gaballa · Soren Wrede · SourceView · Spenser Hale · Stephanie Walters · Stephen Bernhardt · Stephen Edgar · Steve Erdelyi · Steve Jones · Subodh Sunuwar · Subrata Sarkar · Suji K Chandran · Sumi Subedi · Sumit Bagthariya · Sumit Singh · Sunita Rai · suprsam · syamraj24 · Sybre Waaijer · Synchro · Sé Reed · Taco Verdonschot · Tahmid ul Karim · Tahmina Jahan · Takayuki Miyoshi · Tammie Lister · Tanvirul Haque · Teddy Patriarca · tejadev · thinkluke · Thomas Patrick Levy · tibbsa · Tiffany Bridge · Tim Nolte · timdix · Timothy Jacobs · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tom Cafferkey · Tom H · Tom J Nowell · tomluckies · Tomoki Shimomura · tomsommer · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · toscho · Tran Ngoc Tuan Anh · Trinisha · Trisha Salas · tristanleboss · TV productions · Ugyen Dorji · Ulrich · Umesh Balayar · Upadala Vipul · Utsav tilava · valentindu62 · Valerie Blackburn · Vicente Canales · Viktor Szépe · Vipul Ghori · vivekawsm · vortfu · Vraja Das · webashrafians · WebMan Design | Oliver Juhas · Weston Ruter · WHSajid · Will Skora · William Earnhardt · Willington Vega · Winstina · winterstreet · WraithKenny · wyrfel · Yoseph Tamang · Yui · zieladam · Zunaid Amin · Илья

\n\n\n\n

Más de 60 regiones han traducido el 90 por ciento o más de WordPress 6.4 a su idioma. Los traductores de la comunidad están trabajando arduamente para garantizar que haya más traducciones en camino. Gracias a todos los que ayudan a que WordPress esté disponible en 200 idiomas.

\n\n\n\n

Por último, pero no menos importante, gracias a los voluntarios que contribuyen a los foros de soporte respondiendo preguntas de los usuarios de WordPress de todo el mundo.

\n\n\n\n

Involúcrate

\n\n\n\n

La participación en WordPress no se limita a la codificación. Si te atrae contribuir, aprender más e involucrarse es fácil. Descubre los equipos que se unen en Make WordPress y utiliza esta herramienta interactiva para ayudarle a decidir cuál es la adecuada para ti.

\n\n\n\n

Mirando hacia el futuro

\n\n\n\n

Durante las últimas dos décadas, WordPress ha transformado el panorama editorial digital y ha permitido a cualquiera crear y compartir, desde historias personales hechas a mano hasta movimientos que cambian el mundo.

\n\n\n\n

El presente y el futuro de WordPress ofrecen oportunidades interesantes para todos, tanto para los constructores como para las empresas. El trabajo fundamental para la Fase 3 de la hoja de ruta continúa, con esfuerzos centrados en fomentar la colaboración en tiempo real y optimizar los flujos de publicación para mejorar la forma en que los creadores y los equipos trabajan juntos en WordPress.

\n\n\n\n

Manténte al tanto de las últimas noticias y oportunidades de contribución suscribiéndose a WordPress News y al podcast WP Briefing.

\n\n\n\n
\n\n\n\n

Un haiku de liberación.

\n\n\n\n

La suave sensación del jazz
La vanguardia de la web
Instalar 6.4

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://es-mx.wordpress.org/2023/11/09/wordpress-6-4-shirley/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:3:\"988\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:76:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"State of the Word 2023 – Guarda la fecha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://es-mx.wordpress.org/2023/11/06/state-of-the-word-2023-guarda-la-fecha/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://es-mx.wordpress.org/2023/11/06/state-of-the-word-2023-guarda-la-fecha/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 06 Nov 2023 16:25:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Eventos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:14:\"state of world\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://es-mx.wordpress.org/?p=985\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:328:\"¡Es hora de reservar la fecha, el 11 de diciembre de 2023, para el State of the World de este año! State of the Word es el discurso de apertura anual pronunciado por el cofundador del proyecto WordPress, Matt Mullenweg. Cada año, el evento comparte reflexiones sobre el progreso del proyecto y las aspiraciones para […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2245:\"\n
\"\"
\n\n\n\n

¡Es hora de reservar la fecha, el 11 de diciembre de 2023, para el State of the World de este año!

\n\n\n\n\n\n\n\n

State of the Word es el discurso de apertura anual pronunciado por el cofundador del proyecto WordPress, Matt Mullenweg. Cada año, el evento comparte reflexiones sobre el progreso del proyecto y las aspiraciones para el futuro del código abierto.

\n\n\n\n

Por primera vez, State of the Word se llevará a cabo fuera de Norteamérica, esta vez con la comunidad española en Madrid, España. El evento se transmitirá en vivo a los entusiastas de WordPress de todo el mundo a través de las plataformas de redes sociales de WordPress.org.

\n\n\n\n

Únete a Matt mientras ofrece una retrospectiva de 2023, muestra lo último en tecnología de WordPress y comenta sobre el futuro del proyecto de código abierto de WordPress.

\n\n\n\n

Los detalles que incluyen cómo reservar un ticket para el evento en persona, el enlace para ver la transmisión en vivo e información sobre cómo enviar preguntas para la parte de preguntas y respuestas se proporcionarán en noviembre y se compartirán en WordPress.org y cuentas de redes sociales afiliadas.

\n\n\n\n

Traducido de wordpress.org/news

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://es-mx.wordpress.org/2023/11/06/state-of-the-word-2023-guarda-la-fecha/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:3:\"985\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:6:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"El mes en WordPress: Agosto 2023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://es-mx.wordpress.org/2023/09/13/el-mes-en-wordpress-agosto-2023/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://es-mx.wordpress.org/2023/09/13/el-mes-en-wordpress-agosto-2023/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Sep 2023 14:07:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"Mes en WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://es-mx.wordpress.org/?p=982\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:366:\"Agosto de 2023 marcó otro capítulo emocionante en WordPress, con la Cumbre de la Comunidad y WordCamp US que reunieron a la comunidad para discusiones significativas, intercambio de conocimientos y aprendizaje. Este mes también dio la bienvenida al tan esperado lanzamiento de WordPress 6.3 y ofreció un vistazo de lo que está por venir. Profundicemos […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Abraham Morales (soyabrahamdev)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:14983:\"\n

Agosto de 2023 marcó otro capítulo emocionante en WordPress, con la Cumbre de la Comunidad y WordCamp US que reunieron a la comunidad para discusiones significativas, intercambio de conocimientos y aprendizaje. Este mes también dio la bienvenida al tan esperado lanzamiento de WordPress 6.3 y ofreció un vistazo de lo que está por venir. Profundicemos en ello.

\n\n\n\n\n\n\n\n

Conoce WordPress 6.3 “Lionel”

\n\n\n\n

WordPress 6.3 “Lionel” se lanzó el 8 de agosto de 2023 y lleva el nombre del aclamado vibrafonista, pianista y percusionista de jazz Lionel Hampton.

\n\n\n\n

Esta importante actualización hace que darle vida a tu visión con bloques sea más intuitivo y eficiente. Su contenido, plantillas y patrones ahora están perfectamente integrados en el Editor del sitio, lo que le permite diseñar cada aspecto de su presencia en línea en una sola ubicación. Puedes perfeccionar tus diseños con nuevas herramientas, disfrutar de un control preciso sobre los menús de navegación y trabajar más rápido con la paleta de comandos. Explora las novedades.

\n\n\n\n

WordPress 6.3 presenta más de 500 funciones y mejoras con un énfasis continuo en el rendimiento y la accesibilidad. Este lanzamiento fue posible gracias a más de 650 colaboradores de 52 países.

\n\n\n\n
\n\n
Video en inglés
\n\n\n\n

Si bien el Editor del sitio seguirá mejorándose, este lanzamiento significa un hito importante ya que marca la conclusión de la Fase 2 de Gutenberg. Tómate un momento para ver “Diseñado con WordPress”, una oda a este extraordinario viaje que vale la pena celebrar.

\n\n\n\n
\n

Descarga WordPress 6.3.1.

\n
\n\n\n\n

Hoja de ruta hacia 6.4

\n\n\n\n

Los contribuyentes ya están trabajando en WordPress 6.4, cuyo lanzamiento se espera para el 7 de noviembre de 2023. Este lanzamiento, liderado por un equipo de lanzamiento de género subrepresentado, se centrará en mejorar diferentes aspectos de la experiencia de WordPress mientras continúa el trabajo fundamental para la Fase 3 de Gutenberg. Puede anticipar funciones como administración de fuentes y un nuevo tema predeterminado, Twenty Twenty-Four.

\n\n\n\n

Twenty Twenty-Four pretende ser un tema versátil, que presenta una variedad de plantillas y patrones diseñados específicamente para tres casos de uso: emprendedores y pequeñas empresas, fotógrafos y artistas, y escritores y blogueros.

\n\n\n\n
\n

Consulta la entrada de la hoja de ruta 6.4 para obtener una vista previa provisional de las características esperadas.

\n
\n\n\n\n

Nuevo en el plugin Gutenberg

\n\n\n\n

Se enviaron dos nuevas versiones de Gutenberg en el último mes:

\n\n\n\n\n\n\n\n
\n

Sigue las entradas “Novedades de Gutenberg” para estar al tanto de las últimas mejoras.

\n
\n\n\n\n

Actualizaciones del equipo: próxima generación de eventos de WordPress, rediseño de WP Admin y más

\n\n\n\n\n\n\n\n
\n

¿Estás interesado en ver nuevos formatos de eventos de WordPress en tu comunidad local? ¡Inspírate con estos conceptos creativos y comparte tus ideas!

\n
\n\n\n\n

Solicitudes de comentarios y pruebas

\n\n\n\n\n\n\n\n
\n

El equipo de formación busca comentarios sobre las primeras vías de aprendizaje descritas para mejorar la experiencia educativa de Learn WordPress. Comparte tus pensamientos antes del 15 de septiembre de 2023.

\n
\n\n\n\n

Actualizaciones de eventos de WordPress

\n\n\n\n\n\n\n\n
\n

Únete a Josepha Haden Chomphosy en el episodio 61 de WP Briefing mientras analiza sus conclusiones de la Cumbre Comunitaria.

\n
\n\n\n\n
\n\n\n\n

¿Tienes una historia que podríamos incluir en el próximo número de ‘El Mes en WordPress’? Háznoslo saber llenando este formulario (en inglés).

\n\n\n\n

Las siguientes personas contribuyeron a este mes en WordPress: @rmartinezduque, @laurlittle.

\n\n\n\n

Traducido de wordpress.org/news

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://es-mx.wordpress.org/2023/09/13/el-mes-en-wordpress-agosto-2023/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:3:\"982\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:38:\"https://es-mx.wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"65529093\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";a:11:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Tue, 29 Sep 2026 13:37:45 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:4:\"vary\";s:37:\"Accept-Encoding, accept, content-type\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Tue, 22 Sep 2026 18:36:02 GMT\";s:4:\"link\";s:64:\"; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:16:\"content-encoding\";s:4:\"gzip\";s:7:\"alt-svc\";s:5:\"clear\";s:4:\"x-nc\";s:13:\"EXPIRED dca 1\";}s:5:\"build\";i:1788553550;s:21:\"cache_expiration_time\";i:1790732265;s:23:\"__cache_expiration_time\";i:1790732265;}', 'off'); +INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES +(2900, '_site_transient_timeout_feed_mod_203ddaeab844647ccdc6525a1073e4d6', '1790732265', 'off'), +(2901, '_site_transient_feed_mod_203ddaeab844647ccdc6525a1073e4d6', '1790689065', 'off'), +(2902, '_site_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1790732266', 'off'); +INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES +(2903, '_site_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9', 'a:6:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:112:\"\n \n \n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"WordPress Planet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://planet.wordpress.org/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:2:\"en\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WordPress Planet - http://planet.wordpress.org/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:50:{i:0;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"Open Channels FM: Delegating to AI: What September Taught Us About Control and Cost\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2563114\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"https://openchannels.fm/delegating-to-ai-what-september-taught-us-about-control-and-cost/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"This month\'s AI stories, from kernel-crawling bots to assistants booking your flights, all pointed to the same gap: creation got cheap. Trust didn\'t.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2026 12:12:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:128:\"HeroPress: From Blogging to Belonging: My WordPress Journey – Blogging से Belonging तक: मेरी WordPress Journey\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=8892\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:168:\"https://heropress.com/essays/from-blogging-to-belonging-my-wordpress-journey/#utm_source=rss&utm_medium=rss&utm_campaign=from-blogging-to-belonging-my-wordpress-journey\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:95629:\"\"Pull

वर्डप्रेस ने मुझे मेरे ज़िंदगी में कुछ अलग करने का मौक़ा दिया।

\n\n\n\n

Introduction

\n\n\n\n

My name is Satyam Vishwakarma, though most people know me as Satya.

\n\n\n\n

I come from a small village called Mahmadpur, near Fatehpur, the city of Doaba, in Uttar Pradesh, nestled between the sacred Ganga and Yamuna rivers. This is the place I’ve always called home.

\n\n\n\n

I studied Electronics Engineering (Micro) at Government Polytechnic College in Fatehpur. Growing up and studying in a relatively small city, I never had a clear idea of where technology or the internet could take me.

\n\n\n\n
\"Satyam
Satyam Vishwakarma presenting his project during the first year of his diploma, 2018.
\n\n\n\n

I didn’t discover WordPress with a big career plan. I was simply curious about technology and wanted to help the people around me.

\n\n\n\n

Most of my classmates, including me, came from Hindi-medium schools or the UP Board. A lot of the technical material we found online was either difficult to understand or simply wasn’t written in the kind of simple English we were comfortable with.

\n\n\n\n

At the same time, I was probably one of the more tech-savvy people around me. I loved trying new software, exploring new features, and figuring out how things worked. Whenever I discovered something interesting, I would share it with my WhatsApp groups and classmates.

\n\n\n\n

I didn’t think of that as writing or teaching at the time.

\n\n\n\n

I was simply sharing something I had discovered.

\n\n\n\n

Eventually, I thought: why not put some of this information somewhere that more people could find it?

\n\n\n\n

That small thought became the beginning of my writing career.

\n\n\n\n

Before WordPress, there was Blogger

\n\n\n\n

Some of my earliest opportunities to write online came through people I met on WhatsApp.

\n\n\n\n

I became friends with Mohit Vyas and Arpit Nuwal through one of the technology-focused WhatsApp groups I was part of. They had built a website called TopJankari. It wasn’t running on WordPress. It was a custom-built, dynamic website with its own basic way of managing content, but it was still fairly simple compared with the content management systems I discovered later.

\n\n\n\n

I started writing technology and tips-related content for TopJankari.

\n\n\n\n

For me, this was exciting. I was taking the things I was already experimenting with and turning them into something that other people could actually read and use.

\n\n\n\n

Around the same time, I started experimenting with Blogger.com and began publishing my own technology and tips-related content there.

\n\n\n\n

I wasn’t thinking about becoming a professional writer.

\n\n\n\n

I just enjoyed technology; I enjoyed explaining things, and I liked the idea that something I wrote could help another person solve a problem.

\n\n\n\n

That was enough motivation to keep going.

\n\n\n\n

Then WordPress entered the picture

\n\n\n\n

While I was experimenting with blogging, my brother Shivam (now runs a WordPress design agency called Subhash Digital) built his first website with WordPress.

\n\n\n\n

That caught my attention.

\n\n\n\n

I was already curious about how websites worked, and seeing him build something with WordPress gave me an idea of what was possible. I wanted to try it myself.

\n\n\n\n

Around the same time, my brother Kapil and I started learning WordPress together.

\n\n\n\n

Neither of us really knew what we were doing.

\n\n\n\n

We learned through YouTube videos, documentation, blog posts, and mostly through experimentation.

We would try something, break it, search for why it broke, fix it, and move on to the next thing.

\n\n\n\n

My first WordPress project was EngineersGuru, a place where I could share content related to my Electronics Engineering (Micro) course.

\n\n\n\n

I initially ran it as a subdomain, with the idea of making useful course-related tutorials and information easier for fellow students to understand.

\n\n\n\n

We also started an Android-related blog and Jankari.xyz, a more general website where I could write about pretty much anything I found interesting.

\n\n\n\n

In hindsight, those websites were my playground.

\n\n\n\n

They were where I learned WordPress, writing, SEO, content creation, and the basics of running websites.

\n\n\n\n

I wasn’t following a carefully designed career path. I was just building things because I wanted to see what I could do.

\n\n\n\n

And that curiosity kept taking me somewhere new.

\n\n\n\n

Learning by failing

\n\n\n\n

As I continued blogging, I started learning about SEO, monetization, and affiliate marketing.

\n\n\n\n

I experimented with different kinds of websites and eventually built more than ten blogs while I was still learning.

\n\n\n\n

One of my projects eventually became EYNZone (formerly known as EYNWorld), where I started helping others learn WordPress and other skills and grow their own projects.

\n\n\n\n

There were plenty of failures along the way.

\n\n\n\n

I applied for Google AdSense more than twenty times before I finally stopped guessing and actually studied the guidelines carefully. Eventually, I got a brand-new domain approved with only two articles.

\n\n\n\n
\"An
\n\n\n\n

That experience stayed with me.

\n\n\n\n

It taught me that rejection doesn’t necessarily mean you aren’t capable.

\n\n\n\n

Sometimes you simply haven’t figured out the problem yet.

\n\n\n\n

That became a recurring theme in my life.

\n\n\n\n

Looking for a career, finding a community

\n\n\n\n

Eventually, I started looking for a full-time job in mid 2022.

\n\n\n\n

That was another learning experience, although not always a pleasant one.

\n\n\n\n

I applied to more than 800 companies and went through around 2,000 job applications.

\n\n\n\n

During that period, I discovered UnderrepresentedInTech through Michelle Frechette. That eventually introduced me to Post Status, where I started meeting more people from the WordPress ecosystem.

\n\n\n\n

Something interesting was happening.

\n\n\n\n

While I was struggling to find where I fit professionally, I was slowly finding a place for myself in WordPress.

\n\n\n\n

I started learning not just about the software, but about the project behind it and the people who were building it.

\n\n\n\n

And then I heard about WordCamp Bhopal.

\n\n\n\n

The WordCamp I almost couldn’t attend

\n\n\n\n

My first WordCamp was WordCamp Bhopal in 2023.

\n\n\n\n

I wanted to go.

\n\n\n\n

I had told people I would go.

\n\n\n\n

There was just one problem: I didn’t have the money to actually make the trip happen.

\n\n\n\n

So I asked for help in the Post Status Slack community.

\n\n\n\n

I still think about what happened next.

\n\n\n\n

People who had never met me in person decided to help. Alan, Jenni, and Corey Maass contributed financially. Michelle, Jeff, and others shared my request, and Ronald (from DLXPlugins) also helped after seeing it.

\n\n\n\n

People I barely knew, or had never met at all, helped me get to an event that I otherwise couldn’t have attended.

\n\n\n\n

I made it to Bhopal.

\n\n\n\n

The journey itself was almost comical. I travelled at the last moment, ended up at the wrong location at night, and then had an entire hotel saga before things finally settled down.

\n\n\n\n

But once I got there, none of that really mattered.

\n\n\n\n

Later at the event, Nabin Jaiswal also helped.

\n\n\n\n

I met people I had previously known only through websites, Slack, and social media.

\n\n\n\n\n\n\n\n


And then something unexpected happened.

\n\n\n\n

I wanted to go to another WordCamp.

\n\n\n\n

Then another.

\n\n\n\n

That first trip was followed by WordCamp Mumbai, WordCamp Udaipur, where I received a scholarship, and WordCamp Ahmedabad in 2023.

\n\n\n\n\n\n\n\n


Within a few months, WordPress had gone from something I used on my computer to something I experienced through people.

\n\n\n\n

It had faces now.

\n\n\n\n

Names.

\n\n\n\n

Conversations.

\n\n\n\n

Handshakes.

\n\n\n\n

People asking how I was doing.

\n\n\n\n

And I wanted to give something back.

\n\n\n\n

I didn’t know how much I could contribute

\n\n\n\n

I started with the Marketing team and gradually found my way into other parts of the project: Community, Meetups, Polyglots, Photos, Training, and Core.

\n\n\n\n

In January 2024, I published a public contribution goal for myself.

\n\n\n\n
\n

My #WordPress contribution goals for 2024:
1. Contribute 100 photos \"📸\"
2. Translate 5000 strings \"🌐\"
3. Write 5 documentation pieces \"📝\"
4. Organize meetups \"🤝\"
5. Attend 8+ WordCamps \"🎉\"
6. Make impactful marketing contributions! \"💡\" #OpenSource #WordPressCommunity #2024Goals pic.twitter.com/uLxE0BdYVL

— Satyam Vishwakarma (Satya) (@ask_hellosatya) January 17, 2024
\n
\n\n\n\n

I wanted to contribute 100 photos, translate thousands of strings, work on documentation and training, organize meetups, attend WordCamps, volunteer at events, and make meaningful contributions to marketing.

\n\n\n\n

At the time, it was simply a list of things I wanted to try.

\n\n\n\n

I didn’t know where it would lead.

\n\n\n\n

Within that year, I contributed around 150 photos and translated, reviewed, or suggested around 1,400 strings. I also reviewed Training content, organized my first meetup for WordPress’s 21st birthday, graduated as a mentee in the WordPress Contributor Mentorship Program 2nd Cohort for Support and Polyglots, worked on marketing for releases and events, volunteered at multiple events, and eventually led Contributor Day tables.

\n\n\n\n\n\n\n\n


I also became a Project Manager at do_action Bhopal after starting there as a Content and Social Media Manager.

\n\n\n\n\n\n\n\n


I also volunteered at PHPCamp 2024, an Un(conference) inspired by the BarCamp format.

\n\n\n\n\n\n\n\n


Other WordCamp Events I Attended in 2025–2026

\n\n\n\n\n\n\n\n


I also helped with sponsorships and the overall program progress of WPSimplified’s three-month live WordPress training program, led by Sunil Kumar Sharma, which ran from November 2025 to January 2026.

\n\n\n\n
\"\"
Satyam Vishwakarma, with WPSimplified swag presented in recognition of his organizing efforts.
\n\n\n\n

On paper, those things look like achievements.

\n\n\n\n

But that’s not how I remember them.

\n\n\n\n

I remember sitting in meetings, wondering whether my idea was good enough.

\n\n\n\n

I remember asking questions.

\n\n\n\n

I remember people patiently explaining things.

\n\n\n\n

I remember realizing that I could actually be useful.

\n\n\n\n

And I remember the feeling of seeing something I had worked on become part of something much bigger than me.

\n\n\n\n

That was when contribution started becoming less about “what can I get from WordPress?” and more about “what can I give back?”

\n\n\n\n

The people became the story

\n\n\n\n

The more I contributed, the more people I met.

\n\n\n\n

Some of them became friends.

\n\n\n\n

Some became mentors.

\n\n\n\n

Some simply inspired me by watching how they showed up for the community.

\n\n\n\n

Michelle Frechette has been one of those people for me. So have Topher DeRosia, Isotta Peira, Nidhi Jain, Ganga Kafle, and many others.

\n\n\n\n

What I admire about people like them isn’t just what they have achieved.

\n\n\n\n

It’s the way they make other people feel that there is room for them, too.

\n\n\n\n

That matters when you’re coming from somewhere like Fatehpur and trying to find your place in a global community.

\n\n\n\n

You don’t always need someone to give you an opportunity.

\n\n\n\n

Sometimes you just need someone to make you believe that you are allowed to try.

\n\n\n\n

I’ve been fortunate to have people do that for me.

\n\n\n\n

From contributing to building

\n\n\n\n

By my second year, I started wanting to build things of my own within the WordPress ecosystem.

\n\n\n\n

I volunteered and led the marketing team alongside Emma Young at WordCamp Asia 2025 in Manila.

\n\n\n\n

I started building plugins of my own, with contributions and support from Harish, Bhargav, Makarand Mane, Hitanshu Sahu, and Sajid Ansari.

\n\n\n\n

The first was QuoteFrameShare.

\n\n\n\n

It lets people create and share customizable blockquotes in WordPress.

\n\n\n\n
\n

That project was particularly meaningful to me because writing and poetry have always been a part of who I am. Something that started with me writing technology tutorials for fellow engineering students had now come full circle into something I was building for writers, poets, and storytellers.

\n
\n\n\n\n

The second was Contributor Photo Gallery.

\n\n\n\n

It helps WordPress contributors display their WordPress.org photo contributions as a portfolio without needing to write code.

\n\n\n\n
\n

That one came from another part of my journey: photography and the WordPress Photo Directory.

\n
\n\n\n\n

I liked that both projects solved relatively simple problems, but for communities and people I actually cared about.

\n\n\n\n

I wasn’t just building a plugin because I could.

\n\n\n\n

I was building something because I had an idea and thought it could be useful to someone else.

\n\n\n\n

Not everything went smoothly

\n\n\n\n

My WordPress journey hasn’t been a straight line upward.

\n\n\n\n

There was a period when I became so enthusiastic about contributing that I started trying to do everything.

\n\n\n\n

Every team.

\n\n\n\n

Every opportunity.

\n\n\n\n

Every event.

\n\n\n\n

Every possible contribution.

\n\n\n\n

I was so focused on proving that I could contribute that I wasn’t paying enough attention to everything else in my life.

\n\n\n\n

Eventually, I burned out.

\n\n\n\n

I also learned that community work has its own challenges. Not every experience was positive, and there were moments when I felt overlooked, misunderstood, or discouraged.

\n\n\n\n

Those experiences were difficult, but they also forced me to think about what I actually wanted from contribution.

\n\n\n\n

I realized that I didn’t want to spend my time trying to prove that I belonged.

\n\n\n\n

I wanted to contribute because I cared about the project and the people in it.

\n\n\n\n

That changed how I look at contribution today.

\n\n\n\n

I learned that I didn’t need to be everywhere, collect every badge, or chase the biggest contribution count to prove that I cared.

\n\n\n\n

I needed to find a way of contributing that I could actually sustain.

\n\n\n\n

I also realized I didn’t need to sacrifice my health, livelihood, or peace of mind to prove that I cared.

\n\n\n\n

If you have one hour a week, contribute that hour.

\n\n\n\n

If you have more time, great.

\n\n\n\n

But contribution should be sustainable.

\n\n\n\n

The support that I will never forget

\n\n\n\n

One of the reasons I can talk about the difficult parts honestly is that the positive side of this community has been very real for me too.

\n\n\n\n

People have supported me in ways they didn’t have to.

\n\n\n\n

The help I received to attend my first WordCamp is one example.

\n\n\n\n

Katie at Barn2 later sponsored a couple of my WordCamp trips through the company’s events budget. Makarand nominated me for the Yoast Care Fund, which I was fortunate enough to receive.

\n\n\n\n

The WP Open Community Collective also supported me through a Contributor Day Lead Sponsorship sponsored by GoDaddy.

\n\n\n\n

And there were people who helped in ways that weren’t financial at all.

\n\n\n\n

People gave me their time.

\n\n\n\n

They answered questions.

\n\n\n\n

They recommended me.

\n\n\n\n

They encouraged me when I was uncertain.

\n\n\n\n

Those things can be easy to overlook when you are talking about contribution numbers, but for me, they are the real story.

\n\n\n\n

Because behind every contribution is usually a person.

\n\n\n\n

And behind my contributions are a lot of people who helped me get there.

\n\n\n\n

What WordPress gave me

\n\n\n\n

When I look back at the person who started writing technology tutorials for fellow engineering students, I don’t think he would have imagined any of this.

\n\n\n\n

I didn’t have a conventional path into technology.

\n\n\n\n

I didn’t study computer science.

\n\n\n\n

I learned WordPress by building things, breaking things, and figuring them out.

\n\n\n\n

And somehow, that was enough to get started.

\n\n\n\n

WordPress helped me develop skills in technology, content, SEO, marketing, product building, and community.

\n\n\n\n

It gave me opportunities to work with people around the world.

\n\n\n\n

It took me to WordCamps that I once couldn’t afford to attend.

\n\n\n\n

It helped me build open-source products.

\n\n\n\n

But those aren’t the things I value most.

\n\n\n\n

The biggest thing WordPress gave me was people.

\n\n\n\n

That’s why the word ‘belonging’ feels more appropriate to me than ‘success.’

\n\n\n\n

I came to WordPress to build websites.

\n\n\n\n

Somewhere along the way, WordPress helped me build a community around me.

\n\n\n\n

I am still figuring it out

\n\n\n\n

I still don’t know exactly where WordPress will take me.

\n\n\n\n

I want to keep building products.

\n\n\n\n

I want to grow further in the marketing and product side of my career.

\n\n\n\n

I want to explore more around partnerships and community.

\n\n\n\n

And one day, I’d love to co-lead a WordPress release.

\n\n\n\n

But I don’t want to chase these things just for a title or a badge.

\n\n\n\n

I want to build things that are genuinely useful.

\n\n\n\n

I want to become better at what I do.

\n\n\n\n

I want to help people who are where I was a few years ago.

\n\n\n\n

And I want to be the kind of person who, when someone remembers their first steps into WordPress, they can say: “Satya helped me get started.”

\n\n\n\n

That would mean more to me than any badge.

\n\n\n\n

Because that’s what happened to me.

\n\n\n\n

People helped me get started.

\n\n\n\n

People made space for me.

\n\n\n\n

People encouraged me.

\n\n\n\n

People believed I could contribute before I was completely sure myself.

\n\n\n\n

So if someone reading this is just starting their WordPress journey, my advice is simple:

\n\n\n\n

Start small. Ask questions. Find something you enjoy. Contribute consistently, but within your capacity.

\n\n\n\n

You don’t need to have everything figured out before you begin.

\n\n\n\n

I certainly didn’t.

\n\n\n\n

I started writing because I wanted to make complicated things easier for my classmates.

\n\n\n\n

I started blogging because I was curious about technology.

\n\n\n\n

I started using WordPress because my brother showed me what was possible.

\n\n\n\n

I kept learning because there was always something new to discover.

\n\n\n\n

And eventually, I started contributing because I wanted to give something back.

\n\n\n\n

But somewhere along the way, something else happened.

\n\n\n\n

I found people.

\n\n\n\n

I found opportunities.

\n\n\n\n

I found a community.

\n\n\n\n

And I found a place where I could keep learning, contributing, and becoming a little better than I was before.

\n\n\n\n

I came to WordPress to build websites.

\n\n\n\n

Somewhere along the way, WordPress helped me build a community around me.

\n\n\n\n

And maybe that’s what this journey has really been about.

\n\n\n\n

From blogging to belonging.

\n\n\n\n

Blogging से Belonging तक: मेरी WordPress Journey

\n\n\n\n

शुरुआत

\n\n\n\n

मेरा नाम सत्यम विश्वकर्मा है, हालांकि ज़्यादातर लोग मुझे सत्या के नाम से जानते हैं।

\n\n\n\n

मैं महमदपुर नाम के एक छोटे से गाँव से आता हूँ, जो उत्तर प्रदेश के फतेहपुर, दोआब के शहर, के पास है और गंगा और यमुना नदियों के बीच बसा है। यह जगह हमेशा से मुझे अपना घर लगी है।

\n\n\n\n

मैंने फतेहपुर के Government Polytechnic College से Electronics Engineering (Micro) की पढ़ाई की। एक छोटे शहर में बड़े होते और पढ़ते हुए मुझे कभी ठीक से अंदाज़ा नहीं था कि technology या internet मुझे कहाँ तक ले जा सकते हैं।

\n\n\n\n

मैं WordPress तक किसी बड़े career plan के साथ नहीं पहुँचा था। मैं बस technology को लेकर उत्सुक था और अपने आसपास के लोगों की मदद करना चाहता था।

\n\n\n\n

मेरे ज़्यादातर classmates, मेरी तरह, Hindi-medium schools या UP Board से पढ़े हुए थे।

\n\n\n\n

हमें इंटरनेट पर मिलने वाली बहुत-सी technical सामग्री या तो समझना मुश्किल होती थी या फिर वह उस तरह की आसान English में नहीं होती थी, जिसे हम सहजता से समझ सकें।

\n\n\n\n

साथ ही, मैं शायद अपने आसपास के लोगों में technology को लेकर थोड़ा ज़्यादा curious था।

\n\n\n\n

मुझे नया software आज़माना, नए features explore करना और यह समझना बहुत पसंद था कि चीज़ें कैसे काम करती हैं।

\n\n\n\n

जब भी मुझे कुछ interesting मिलता, मैं उसे अपने WhatsApp groups और classmates के साथ share करता था।

\n\n\n\n

उस समय मैंने इसे writing या teaching के तौर पर नहीं देखा था।

\n\n\n\n

मैं बस वही share कर रहा था जो मैंने खुद discover किया था।

\n\n\n\n

फिर एक दिन मन में आया:

\n\n\n\n

क्यों न इस information को कहीं ऐसी जगह रखा जाए, जहाँ इसे और लोग भी ढूँढ सकें?

\n\n\n\n

वही छोटी-सी सोच मेरी writing journey की शुरुआत बन गई।

\n\n\n\n

WordPress से पहले Blogger था

\n\n\n\n


Online लिखने के मेरे शुरुआती मौकों में से कुछ मुझे WhatsApp पर मिले लोगों की वजह से मिले।

\n\n\n\n

मैं technology से जुड़े एक WhatsApp group के ज़रिए Mohit Vyas और Arpit Nawal से online मिला। उन्होंने TopJankari नाम की website बनाई थी।

\n\n\n\n

वह WordPress पर नहीं चलती थी। वह एक custom-built, dynamic website थी, जिसमें content manage करने का अपना basic system था। बाद में मुझे जिन content management systems के बारे में पता चला, उनकी तुलना में वह काफी simple थी।

\n\n\n\n

मैंने TopJankari के लिए technology और tips से जुड़ा content लिखना शुरू किया।

\n\n\n\n

मेरे लिए यह बहुत exciting था।

\n\n\n\n

जिन चीज़ों को मैं खुद आज़मा रहा था, उन्हें मैं अब इस तरह लिख रहा था कि कोई दूसरा भी उन्हें पढ़कर इस्तेमाल कर सके।

\n\n\n\n

उसी दौरान मैंने Blogger.com के साथ भी experiment करना शुरू किया और वहाँ अपना technology और tips-related content publish करने लगा।

\n\n\n\n

उस समय मैं professional writer बनने के बारे में नहीं सोच रहा था।

\n\n\n\n

मुझे बस technology पसंद थी। मुझे चीज़ों को समझाना पसंद था। और मुझे यह विचार अच्छा लगता था कि मेरे द्वारा लिखी गई कोई चीज़ किसी दूसरे व्यक्ति की समस्या हल करने में मदद कर सकती है।

\n\n\n\n

मेरे लिए इतना ही काफी था आगे बढ़ते रहने के लिए।

\n\n\n\n

फिर WordPress मेरी कहानी में आया

\n\n\n\n


जब मैं blogging के साथ experiment कर रहा था, मेरे भाई Shivam ने उस समय तक WordPress पर अपनी पहली website बना ली थी।

\n\n\n\n

इसने मेरा ध्यान खींचा।

\n\n\n\n

मैं पहले से ही websites के काम करने के तरीके को लेकर curious था।

\n\n\n\n

उनको WordPress के साथ कुछ बनाते हुए देखकर मुझे पहली बार अंदाज़ा हुआ कि इसके साथ क्या-क्या बनाया जा सकता है।

\n\n\n\n

मैं भी इसे आज़माना चाहता था।

\n\n\n\n

उसी दौरान मेरे भाई Kapil और मैंने साथ मिलकर WordPress सीखना शुरू किया।

\n\n\n\n

हम दोनों को वास्तव में कुछ खास पता नहीं था।

\n\n\n\n

हमने YouTube videos, documentation, blog posts और सबसे ज़्यादा experimentation के ज़रिए सीखा।

\n\n\n\n

हम कुछ try करते, उसे तोड़ देते, फिर search करते कि वह क्यों टूटा, उसे ठीक करते और फिर अगली चीज़ पर बढ़ जाते।

\n\n\n\n

मेरा पहला WordPress project EngineersGuru था। वहाँ मैं अपनी Electronics Engineering (Micro) की पढ़ाई से जुड़ा content शेयर (publish) करता था।

\n\n\n\n

शुरुआत में मैंने इसे एक subdomain के रूप में चलाया। मेरा उद्देश्य था कि मेरे fellow students के लिए course से जुड़ी tutorials और useful information को समझना थोड़ा आसान हो सके।

\n\n\n\n

हमने एक Android-related blog भी शुरू किया और Jankari.xyz भी, जो एक ऐसी general website थी जहाँ मैं लगभग किसी भी ऐसी चीज़ के बारे में लिख सकता था जो मुझे interesting लगती थी।

\n\n\n\n

आज पीछे मुड़कर देखता हूँ तो ये websites मेरे लिए एक playground थीं।

\n\n\n\n

यहीं मैंने WordPress, writing, SEO, content creation और websites चलाने की basic बातें सीखीं।

\n\n\n\n

मैं किसी carefully planned career path पर नहीं चल रहा था।

\n\n\n\n

मैं बस चीज़ें बना रहा था, क्योंकि मैं देखना चाहता था कि मैं क्या कर सकता हूँ।

\n\n\n\n

और मेरी वही curiosity मुझे लगातार कहीं न कहीं आगे ले जाती रही।

\n\n\n\n

गलतियों से सीखना

\n\n\n\n


जैसे-जैसे blogging आगे बढ़ी, मैंने SEO, monetization और affiliate marketing के बारे में सीखना शुरू किया।

\n\n\n\n

मैंने अलग-अलग तरह की websites के साथ experiment किया और सीखते-सीखते दस से ज़्यादा blogs बनाए।

\n\n\n\n

मेरे इन्हीं projects में से एक आगे चलकर EYNZone बना, जिसे पहले EYNWorld के नाम से जाना जाता था। वहाँ मैंने दूसरे लोगों को WordPress और दूसरी skills सीखाने और अपने projects को grow करने में मदद करना शुरू किया।

\n\n\n\n

इस रास्ते में बहुत सारी असफलताएँ भी आईं।

\n\n\n\n

मैंने Google AdSense के लिए बीस से ज़्यादा बार apply किया, और हर बार कुछ न कुछ गलत हो जाता था। आखिरकार मैंने सिर्फ अंदाज़ा लगाना बंद किया और guidelines को सही से पढ़ना और समझना शुरू किया।

\n\n\n\n

आखिर में एक बिल्कुल नए domain पर सिर्फ दो articles के साथ मेरा AdSense approve हो गया।

\n\n\n\n

उस अनुभव का असर मुझ पर रह गया।

\n\n\n\n

इसने मुझे सिखाया कि rejection का मतलब हमेशा यह नहीं होता कि आप capable नहीं हैं।

\n\n\n\n

कभी-कभी इसका मतलब सिर्फ इतना होता है कि आपने अभी तक समस्या को समझा नहीं है।

\n\n\n\n

मेरी ज़िंदगी में यह बात बार-बार सामने आती रही।

\n\n\n\n

Career की तलाश में निकला था, Community मिल गई

\n\n\n\n


आखिरकार, 2022 के बीच में मैंने full-time नौकरी की तलाश शुरू की।

\n\n\n\n

वह भी अपने आप में एक learning experience था, हालांकि हमेशा अच्छा नहीं था।

\n\n\n\n

मैंने 800 से ज़्यादा companies में apply किया और करीब 2,000 job applications के process से गुज़रा।

\n\n\n\n

इसी दौरान मुझे Michelle Frechette के ज़रिए UnderrepresentedInTech के बारे में पता चला। वहाँ से आगे मुझे Post Status से जुड़ने का मौका मिला, जहाँ मैंने WordPress ecosystem के और लोगों से मिलना शुरू किया।

\n\n\n\n

कुछ interesting हो रहा था।

\n\n\n\n

जहाँ मैं यह समझने की कोशिश कर रहा था कि professionally मेरी जगह कहाँ है, वहीं धीरे-धीरे WordPress में मुझे अपनी जगह मिल रही थी।

\n\n\n\n

मैं सिर्फ software के बारे में नहीं सीख रहा था।

\n\n\n\n

मैं उस project के बारे में सीख रहा था जो software के पीछे था, और उन लोगों के बारे में भी जो उसे बनाने में मदद कर रहे थे।

\n\n\n\n

और फिर मैंने WordCamp Bhopal के बारे में सुना।

\n\n\n\n

वह WordCamp जिसे मैं लगभग attend नहीं कर पाता

\n\n\n\n


मेरा पहला WordCamp, WordCamp Bhopal 2023 था।

\n\n\n\n

मैं जाना चाहता था।

\n\n\n\n

मैंने लोगों से कह भी दिया था कि मैं जाऊँगा।

\n\n\n\n

बस एक समस्या थी।

\n\n\n\n

मेरे पास उस trip के लिए पैसे नहीं थे।

\n\n\n\n

इसलिए मैंने Post Status Slack community में मदद माँगी।

\n\n\n\n

आज भी मैं सोचता हूँ कि उसके बाद क्या हुआ था।

\n\n\n\n

जिन लोगों ने मुझे कभी सामने से देखा तक नहीं था, उन्होंने मेरी मदद करने का फैसला किया।

\n\n\n\n

Alan, Jenni और Corey Maass ने financially मदद की। Michelle, Jeff और दूसरे लोगों ने मेरी request को share किया। Ronald, जो DLXPlugins से हैं, उन्होंने भी इसे देखकर मदद की।

\n\n\n\n

जिन लोगों को मैं मुश्किल से जानता था, या शायद कभी मिला ही नहीं था, उन्होंने मुझे उस event तक पहुँचने में मदद की जहाँ मैं अपने दम पर नहीं जा सकता था।

\n\n\n\n

मैं Bhopal पहुँच गया।

\n\n\n\n

और वह सफ़र अपने आप में काफ़ी उलझनों से भरा था।

\n\n\n\n

मैंने आखिरी समय में यात्रा शुरू की, रात में गलत जगह पहुँच गया और फिर होटल को लेकर एक अलग ही किस्सा शुरू हो गया। आखिरकार, किसी तरह सब ठीक हुआ।

\n\n\n\n

लेकिन जब मैं वहाँ पहुँच गया, तो इनमें से किसी चीज़ की उतनी importance नहीं रही।

\n\n\n\n

Event के दौरान Nabin Jaiswal ने भी मेरी मदद की।

\n\n\n\n

मैं उन लोगों से मिला जिन्हें अब तक सिर्फ websites, Email, Slack और social media के ज़रिए जानता था।

\n\n\n\n

और फिर कुछ unexpected हुआ।

\n\n\n\n

मेरा मन हुआ कि मैं एक और WordCamp में जाऊँ।

\n\n\n\n

फिर एक और।

\n\n\n\n

उस पहली trip के बाद WordCamp Mumbai, WordCamp Udaipur, जहाँ मुझे scholarship मिली, और WordCamp Ahmedabad आए।

\n\n\n\n

कुछ ही महीनों में WordPress मेरे लिए computer पर इस्तेमाल की जाने वाली किसी चीज़ से बदलकर लोगों के ज़रिए अनुभव की जाने वाली चीज़ बन गया था।

\n\n\n\n

अब उसके चेहरे थे।

\n\n\n\n

नाम थे।

\n\n\n\n

बातचीत थी।

\n\n\n\n

हाथ मिलाना था।

\n\n\n\n

लोग पूछते थे कि मैं कैसा हूँ।

\n\n\n\n

और मेरा मन हुआ कि अब मुझे भी कुछ वापस देना चाहिए।

\n\n\n\n

मुझे नहीं पता था कि मैं कितना contribute कर सकता हूँ

\n\n\n\n


मैंने शुरुआत Marketing team से की और धीरे-धीरे WordPress project के दूसरे हिस्सों तक पहुँचता गया: Community, Meetups, Polyglots, Photos, Training और Core।

\n\n\n\n

जनवरी 2024 में मैंने अपने लिए एक public contribution लक्ष्य बनाया।

\n\n\n\n

मैं 100 photos contribute करना चाहता था, हजारों strings translate करना चाहता था, documentation और training पर काम करना चाहता था, meetups organize करना चाहता था, WordCamps attend करना चाहता था, events में volunteer करना चाहता था और marketing में meaningful contributions देना चाहता था।

\n\n\n\n

उस समय यह बस उन चीज़ों की एक list थी जिन्हें मैं try करना चाहता था।

\n\n\n\n

मुझे नहीं पता था कि यह मुझे कहाँ ले जाएगी।

\n\n\n\n

उस साल मैंने करीब 150 photos contribute कीं और लगभग 1,400 strings को translate, review या suggest किया। मैंने Training content भी review किया, WordPress के 21st birthday के लिए अपना पहला meetup organize किया, releases और events के marketing पर काम किया, कई events में volunteer किया और Contributor Days में tables भी lead करने लगा।

\n\n\n\n

मैं do_action Bhopal में Content and Social Media Manager के लिए चुना गया और बाद में Project Manager बना दिया गया।

\n\n\n\n

कागज़ पर देखें तो ये सब achievements लगती हैं।

\n\n\n\n

लेकिन मुझे ये इस तरह याद नहीं हैं।

\n\n\n\n

मुझे meetings याद हैं, जहाँ मैं सोचता था कि मेरा idea सही भी है या नहीं।

\n\n\n\n

मुझे अपने सवाल पूछना याद है।

\n\n\n\n

मुझे याद है कि लोग धैर्य से चीज़ें समझाते थे।

\n\n\n\n

मुझे याद है वह एहसास जब मुझे पहली बार लगा कि मैं वास्तव में useful हो सकता हूँ।

\n\n\n\n

और मुझे वह feeling याद है जब मेरे काम की कोई छोटी-सी चीज़ मेरे से कहीं बड़ी किसी चीज़ का हिस्सा बन गई।

\n\n\n\n

शायद वहीं से contribution मेरे लिए बदलना शुरू हुआ।

\n\n\n\n

यह सवाल कम होने लगा कि:

\n\n\n\n

“मुझे WordPress से क्या मिल सकता है?”

\n\n\n\n

और उसकी जगह एक दूसरा सवाल आने लगा:

\n\n\n\n

“मैं WordPress को क्या दे सकता हूँ?”

\n\n\n\n

कहानी में लोग आने लगे

\n\n\n\n


जितना मैं contribute करता गया, उतने ही ज़्यादा लोगों से मिलता गया।

\n\n\n\n

कुछ दोस्त बन गए।

\n\n\n\n

कुछ mentors बन गए।

\n\n\n\n

कुछ ऐसे लोग थे जिन्होंने बस community में जिस तरह अपनी जगह बनाई और दूसरों के लिए मौजूद रहे, उससे मुझे inspiration मिली।

\n\n\n\n

Michelle Frechette मेरे लिए ऐसे ही लोगों में से एक रही हैं। उनके साथ Topher DeRosia, Isotta Peira, Nidhi Jain, Ganga Kafle, और कई दूसरे लोग भी हैं।

\n\n\n\n

मैं इन लोगों से सिर्फ इसलिए प्रभावित नहीं हूँ कि उन्होंने क्या हासिल किया है।

\n\n\n\n

बल्कि इसलिए कि वे दूसरों को यह महसूस कराते हैं कि उनके लिए भी जगह है।

\n\n\n\n

जब आप Fatehpur जैसी जगह से आते हैं और एक global community में अपनी जगह बनाने की कोशिश करते हैं, तो यह बहुत मायने रखता है।

\n\n\n\n

हर बार किसी का आपको opportunity देना ज़रूरी नहीं होता।

\n\n\n\n

कभी-कभी आपको सिर्फ किसी ऐसे व्यक्ति की ज़रूरत होती है जो आपको यह विश्वास दिला दे कि:

\n\n\n\n

“हाँ, तुम भी कोशिश कर सकते हो।”

\n\n\n\n

मैं खुशकिस्मत हूँ कि मेरी journey में ऐसे लोग आए।

\n\n\n\n

Contribution से building तक

\n\n\n\n


मेरे दूसरे साल तक आते-आते मेरे मन में WordPress ecosystem के अंदर अपने कुछ products बनाने की इच्छा होने लगी।

\n\n\n\n

मैंने WordCamp Asia 2025 में Manila में Emma Young के साथ marketing team में lead किया और volunteer किया।

\n\n\n\n

इसके साथ मैंने अपने plugins बनाना भी शुरू किया, जिसमें Harish, Bhargav, Makarand Mane, Hitanshu Sahu, और Sajid Ansari के contributions और support ने मदद की।

\n\n\n\n

पहला था QuoteFrameShare

\n\n\n\n

यह लोगों को WordPress में customizable blockquotes बनाने और share करने की सुविधा देता है।

\n\n\n\n

यह project मेरे लिए खास था क्योंकि writing और poetry हमेशा से मेरी ज़िंदगी का हिस्सा रहे हैं।

\n\n\n\n

जिस चीज़ की शुरुआत fellow engineering students के लिए technology tutorials लिखने से हुई थी, वह अब घूमकर ऐसे product तक पहुँच गई थी जिसे writers, poets और storytellers के लिए बनाया जा रहा था।

\n\n\n\n

दूसरा था Contributor Photo Gallery

\n\n\n\n

यह WordPress contributors को अपनी WordPress.org photo contributions को बिना code लिखे एक portfolio की तरह दिखाने में मदद करता है।

\n\n\n\n

यह मेरी journey के एक और हिस्से से आया था: photography और WordPress Photo Directory।

\n\n\n\n

मुझे अच्छा लगा कि दोनों projects छोटी और relatively simple problems को solve करते थे, लेकिन उन communities और लोगों के लिए, जो मेरे लिए सच में मायने रखते थे।

\n\n\n\n

मैं सिर्फ इसलिए plugin नहीं बना रहा था क्योंकि मैं बना सकता था।

\n\n\n\n

मैं इसलिए कुछ बना रहा था क्योंकि मेरे पास एक idea था और मुझे लगा कि वह किसी और के लिए useful हो सकता है।

\n\n\n\n

सब कुछ हमेशा ठीक नहीं रहा

\n\n\n\n


मेरी WordPress journey हमेशा सीधी ऊपर की ओर जाने वाली कहानी नहीं रही।

\n\n\n\n

एक समय ऐसा भी आया जब contribution को लेकर मेरा उत्साह इतना बढ़ गया कि मैं सब कुछ करने की कोशिश करने लगा।

\n\n\n\n

हर team।

\n\n\n\n

हर opportunity।

\n\n\n\n

हर event।

\n\n\n\n

हर possible contribution।

\n\n\n\n

मैं यह साबित करने में इतना व्यस्त हो गया था कि मैं contribute कर सकता हूँ कि मैंने अपनी ज़िंदगी की बाकी चीज़ों पर पर्याप्त ध्यान देना शुरू नहीं किया।

\n\n\n\n

आखिरकार, मैं burnout हो गया।

\n\n\n\n

मैंने यह भी सीखा कि community work की अपनी challenges होती हैं।

\n\n\n\n

हर experience अच्छा नहीं था। कुछ ऐसे moments भी आए जब मुझे लगा कि मेरी बात को देखा नहीं गया, मुझे समझा नहीं गया या मैंने discouraged महसूस किया।

\n\n\n\n

वे experiences आसान नहीं थे।

\n\n\n\n

लेकिन उन्होंने मुझे यह सोचने पर मजबूर किया कि आखिर मैं contribution से क्या चाहता हूँ।

\n\n\n\n

मुझे एहसास हुआ कि मैं अपना समय यह साबित करने में नहीं लगाना चाहता था कि मैं belong करता हूँ।

\n\n\n\n

मैं contribute इसलिए करना चाहता था क्योंकि मुझे इस project और इसमें शामिल लोगों की परवाह थी।

\n\n\n\n

इसने contribution को देखने का मेरा तरीका बदल दिया।

\n\n\n\n

मुझे समझ आया कि मुझे हर जगह होना ज़रूरी नहीं है। हर badge collect करना ज़रूरी नहीं है। सबसे बड़ा contribution count हासिल करना भी ज़रूरी नहीं है ताकि मैं यह साबित कर सकूँ कि मुझे परवाह है।

\n\n\n\n

मुझे बस ऐसा तरीका ढूँढना था जिससे मैं लंबे समय तक contribute कर सकूँ।

\n\n\n\n

मुझे यह भी समझ आया कि यह साबित करने के लिए कि मुझे परवाह है, मुझे अपनी health, livelihood या peace of mind को sacrifice करने की ज़रूरत नहीं है।

\n\n\n\n

अगर आपके पास हफ्ते में सिर्फ एक घंटा है, तो उतना ही contribute कीजिए।

\n\n\n\n

अगर आपके पास ज़्यादा समय है, तो बहुत अच्छी बात है।

\n\n\n\n

लेकिन contribution sustainable होना चाहिए।

\n\n\n\n

वह support जिसे मैं कभी नहीं भूलूँगा

\n\n\n\n


शायद यही वजह है कि मैं अपनी journey के मुश्किल हिस्सों के बारे में भी ईमानदारी से बात कर सकता हूँ, क्योंकि इस community का positive side भी मेरे लिए उतना ही वास्तविक रहा है।

\n\n\n\n

लोगों ने मेरी ऐसे तरीकों से मदद की, जिसकी उन्हें कोई मजबूरी नहीं थी।

\n\n\n\n

मेरे पहले WordCamp तक पहुँचने में मिली मदद इसका एक उदाहरण है।

\n\n\n\n

बाद में Katie at Barn2 ने company के events budget के ज़रिए मेरे कुछ WordCamp trips sponsor किए। Makarand ने मुझे Yoast Care Fund के लिए nominate किया, जिसे पाना मेरे लिए सौभाग्य की बात रही।

\n\n\n\n

WP Open Community Collective ने भी मुझे Contributor Day Lead Sponsorship, जिसे GoDaddy ने sponsor किया था, के ज़रिए support किया।

\n\n\n\n

और कुछ लोगों ने ऐसी मदद की जो financial बिल्कुल नहीं थी।

\n\n\n\n

लोगों ने अपना समय दिया।

\n\n\n\n

मेरे सवालों के जवाब दिए।

\n\n\n\n

मेरी recommendations कीं।

\n\n\n\n

जब मैं खुद को लेकर uncertain था, तब मुझे encourage किया गया।

\n\n\n\n

Contribution numbers की बात करते समय इन चीज़ों को आसानी से नज़रअंदाज़ किया जा सकता है।

\n\n\n\n

लेकिन मेरे लिए असली कहानी यही है।

\n\n\n\n

क्योंकि हर contribution के पीछे अक्सर एक इंसान होता है।

\n\n\n\n

और मेरी contributions के पीछे बहुत सारे ऐसे लोग हैं जिन्होंने मुझे वहाँ तक पहुँचने में मदद की।

\n\n\n\n

WordPress ने मुझे क्या दिया

\n\n\n\n


जब मैं उस लड़के को पीछे मुड़कर देखता हूँ जिसने अपने fellow engineering students के लिए technology tutorials लिखना शुरू किया था, तो मुझे नहीं लगता कि उसने कभी सोचा होगा कि उसकी journey यहाँ तक आएगी।

\n\n\n\n

Technology में आने का मेरा कोई conventional रास्ता नहीं था।

\n\n\n\n

मैंने computer science की पढ़ाई नहीं की।

\n\n\n\n

मैंने WordPress की चीज़ें बनाकर, उन्हें तोड़कर और फिर उन्हें समझते हुए सीखा।

\n\n\n\n

और किसी तरह, शुरुआत करने के लिए इतना ही काफी था।

\n\n\n\n

WordPress ने मुझे technology, content, SEO, marketing, product building और community जैसी skills विकसित करने में मदद की।

\n\n\n\n

इसने मुझे दुनिया भर के लोगों के साथ काम करने के मौके दिए।

\n\n\n\n

मुझे उन WordCamps तक पहुँचाया, जिन्हें मैं कभी afford भी नहीं कर सकता था।

\n\n\n\n

इसने मुझे open-source products बनाने का मौका दिया।

\n\n\n\n

लेकिन इन सबमें से कोई भी चीज़ वह नहीं है जिसे मैं सबसे ज़्यादा महत्व देता हूँ।

\n\n\n\n

WordPress ने मुझे सबसे बड़ी चीज़ जो दी, वह लोग थे।

\n\n\n\n

शायद इसीलिए मेरे लिए “success” से ज़्यादा सही शब्द “belonging” है।

\n\n\n\n

मैं WordPress पर websites बनाने आया था।

\n\n\n\n

लेकिन कहीं न कहीं, WordPress ने मेरे आसपास एक community बना दी।

\n\n\n\n

मैं अभी भी इसे समझने की कोशिश कर रहा हूँ

\n\n\n\n


मुझे अभी भी ठीक से नहीं पता कि WordPress मुझे आगे कहाँ ले जाएगा।

\n\n\n\n

मैं products बनाते रहना चाहता हूँ।

\n\n\n\n

मैं marketing और product के क्षेत्र में और आगे बढ़ना चाहता हूँ।

\n\n\n\n

मैं partnerships और community के बारे में और explore करना चाहता हूँ।

\n\n\n\n

और एक दिन, मैं WordPress release को co-lead करना चाहता हूँ।

\n\n\n\n

लेकिन मैं इन चीज़ों के पीछे सिर्फ किसी title या badge के लिए नहीं भागना चाहता।

\n\n\n\n

मैं ऐसी चीज़ें बनाना चाहता हूँ जो सच में useful हों।

\n\n\n\n

मैं अपने काम में बेहतर बनना चाहता हूँ।

\n\n\n\n

मैं उन लोगों की मदद करना चाहता हूँ जो आज वहीं खड़े हैं जहाँ मैं कुछ साल पहले था।

\n\n\n\n

और मैं ऐसा इंसान बनना चाहता हूँ कि जब कोई अपने WordPress journey के शुरुआती दिनों को याद करे, तो शायद वह कह सके:

\n\n\n\n

“Satya ने मेरी शुरुआत में मेरी मदद की थी।”

\n\n\n\n

मेरे लिए वह किसी भी badge से ज़्यादा मायने रखेगा।

\n\n\n\n

क्योंकि मेरे साथ भी यही हुआ था।

\n\n\n\n

लोगों ने मेरी शुरुआत में मेरी मदद की।

\n\n\n\n

लोगों ने मेरे लिए जगह बनाई।

\n\n\n\n

लोगों ने मुझे encourage किया।

\n\n\n\n

लोगों ने मुझ पर भरोसा किया, उस समय भी जब मुझे खुद पूरी तरह यकीन नहीं था कि मैं contribute कर सकता हूँ।

\n\n\n\n

इसलिए अगर आप अपनी WordPress journey अभी शुरू कर रहे हैं, तो मेरी सलाह बहुत simple है:

\n\n\n\n

छोटे से शुरू कीजिए। सवाल पूछिए। जो पसंद है, उसे खोजिए। लगातार contribute कीजिए, लेकिन अपनी capacity के भीतर।

\n\n\n\n

आपको शुरुआत करने से पहले सब कुछ पता होना ज़रूरी नहीं है।

\n\n\n\n

मुझे भी नहीं पता था।

\n\n\n\n

मैंने लिखना इसलिए शुरू किया क्योंकि मैं अपने classmates के लिए मुश्किल चीज़ों को आसान बनाना चाहता था।

\n\n\n\n

मैंने blogging इसलिए शुरू की क्योंकि technology को लेकर मेरे अंदर curiosity थी।

\n\n\n\n

मैंने WordPress इसलिए शुरू किया क्योंकि मेरे भाई ने मुझे दिखाया कि इसके साथ क्या किया जा सकता है।

\n\n\n\n

मैं सीखता रहा क्योंकि हमेशा कुछ नया सीखने के लिए था।

\n\n\n\n

और आखिरकार, मैंने contribute करना शुरू किया क्योंकि मैं कुछ वापस देना चाहता था।

\n\n\n\n

लेकिन कहीं न कहीं, इस journey के दौरान कुछ और भी हुआ।

\n\n\n\n

मुझे लोग मिले।

\n\n\n\n

मुझे opportunities मिलीं।

\n\n\n\n

मुझे एक community मिली।

\n\n\n\n

और मुझे एक ऐसी जगह मिली जहाँ मैं सीखता रह सकता था, contribute करता रह सकता था और हर दिन थोड़ा बेहतर बनता रह सकता था।

\n\n\n\n

मैं WordPress पर वेबसाइटें बनाने आया था।

\n\n\n\n

लेकिन कहीं न कहीं, WordPress ने मेरे आसपास एक community बना दी।

और शायद यही इस पूरी journey का असली मतलब है।

\n\n\n\n

Blogging से Belonging तक।

\n

The post From Blogging to Belonging: My WordPress Journey – Blogging से Belonging तक: मेरी WordPress Journey appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2026 11:43:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Satyam Vishwakarma\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"Open Channels FM: What Can You Learn From 4.4 Million Words?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562978\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://openchannels.fm/what-can-you-learn-from-4-4-million-words/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:232:\"In this episode, Bob Dunn discusses utilizing 4.4 million words from Open Channels FM\'s podcasts and blog posts. He highlights tools like Jetpack AI Search and Site Chat, enhancing users\' access to valuable insights and discussions.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2026 09:42:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"OpenStation Blog: WordPress Has Been Missing This for 15 Years\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://openstation.blog/?p=1342\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://openstation.blog/2026/09/28/wordpress-has-been-missing-this-for-15-years/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:16418:\"
\n

tl;dr:

\n\n\n\n

15 years stuck in the same wp-admin, why don’t you try in playground the new wp-admin experience?

\n
\n\n\n\n

WordPress has spent the last fifteen years becoming capable of doing almost everything, yet somehow we have continued interacting with wp-admin in fundamentally the same way: click somewhere, load another screen, go back, open another tab because you do not want to lose the previous one, and after a while end up with ten different WordPress tabs scattered across your browser.

\n\n\n\n

I find it quite funny that we all accepted this as completely normal.

\n\n\n\n

Today WordPress is used to run stores, publications, membership sites, communities, LMS platforms, agencies and entire businesses. We have plugins that are effectively full applications, incredibly complex editing experiences, analytics, forms, CRM systems, media tools, commerce, automation and thousands of other things living inside the same installation. Yet the interface connecting all of them still assumes that, most of the time, you want to look at one thing at once.

\n\n\n\n

And when you don’t, the browser has to solve the problem for us.

\n\n\n\n

Browser tabs have essentially become the window manager of WordPress.

\n\n\n\n
\"\"
\n\n\n\n

That is one of the ideas that eventually led us to OpenStation.

\n\n\n\n

Why don’t we have windows?

\n\n\n\n

It sounds ridiculously obvious when you phrase it like that, but that is exactly why I find the question interesting.

\n\n\n\n

On a normal computer I can have my editor open next to a browser, keep a terminal in the background, drag files around, minimize something I want to return to later, or simply arrange my workspace around whatever I am doing at that moment. Nobody thinks about this as a feature anymore because it is just how computers work.

\n\n\n\n

Then we open WordPress and suddenly that whole model disappears.

\n\n\n\n
\"\"
\n\n\n\n

If I am editing a post and need something from the Media Library, I navigate away or open another tab. If I am checking an order while editing a product, another tab. If I want to compare two posts, another tab. If I am configuring something and need to check how another part of the site is set up, another tab.

\n\n\n\n

There is nothing technically wrong with that, of course, and it has worked for years, but after building and using OpenStation every day I started noticing how much context we constantly throw away simply because wp-admin was designed around pages rather than workspaces.

\n\n\n\n

That distinction matters much more today than it probably did fifteen years ago.

\n\n\n\n

WordPress quietly became something much bigger

\n\n\n\n

I keep describing WordPress as the operating system of the web, and obviously I do not mean that literally. What I mean is that WordPress has gradually accumulated many of the characteristics you would expect from a platform where applications live.

\n\n\n\n

Plugins install capabilities into it. Users have identities and permissions. Applications share data. We have APIs, scheduled processes, notifications, media, editors, databases and an enormous ecosystem of software that knows how to work with the same underlying environment.

\n\n\n\n

The strange part is that the interface never fully made the same transition.

\n\n\n\n

We kept adding more applications to WordPress, but we continued presenting them largely as destinations in a menu.

\n\n\n\n

OpenStation started from a very simple thought: what happens if, instead of redesigning every individual wp-admin page again, we change the environment in which those pages live?

\n\n\n\n
\"\"
\n\n\n\n

That immediately opens a much larger set of possibilities.

\n\n\n\n

A post editor does not need to replace your media library on screen. A WooCommerce order does not need to replace the product you were editing. A plugin screen does not necessarily need to occupy the entire browser just because you clicked its menu item.

\n\n\n\n

They can simply be windows.

\n\n\n\n

You can move them, resize them, minimize them, keep several of them open, organise them across different desktops and return to exactly what you were doing without recreating the context again.

\n\n\n\n

The funny thing is that none of this feels particularly futuristic. Quite the opposite. We have been using computers this way for decades.

\n\n\n\n

We just somehow never brought that interaction model into wp-admin.

\n\n\n\n

The interesting part is not actually the windows

\n\n\n\n

The windows are what people notice first because they are visual, but I think the more important idea is what happens once WordPress stops assuming that navigation must destroy context.

\n\n\n\n

Suddenly the admin becomes a workspace.

\n\n\n\n

You can have the Media Library next to the editor instead of travelling between them. You can keep an order visible while checking something else. You can open notes or widgets without abandoning your current task. Applications can coexist on the same desktop and eventually interact with each other in ways that become much harder when everything is isolated in separate browser tabs.

\n\n\n\n

This is also where things like drag and drop become much more interesting.

\n\n\n\n

If two applications are part of the same environment, moving an image, a product, a post or another WordPress entity between them can become an actual interaction instead of a sequence of copy, navigate, search, paste and navigate back.

\n\n\n\n

And once you start thinking about WordPress this way, a lot of things that initially looked like unrelated OpenStation features start making sense together: windows, the dock, multiple desktops, widgets, the command palette and applications are all different pieces of the same idea.

\n\n\n\n

The goal is not to decorate wp-admin until it looks like a desktop operating system. The goal is to make working in WordPress feel less like navigating a website and more like working inside an environment.

\n\n\n\n

We don’t need to replace wp-admin to do this

\n\n\n\n

This is probably the part I like the most about the approach.

\n\n\n\n

WordPress already has an enormous ecosystem and rebuilding everything would be both unrealistic and, in my opinion, the wrong problem to solve. There are thousands of admin interfaces that already work, plugins developers have spent years building, and workflows users already understand.

\n\n\n\n

OpenStation can sit on top of that rather than asking the ecosystem to start again.

\n\n\n\n

The existing WordPress admin can continue being WordPress. Existing plugins can continue exposing their interfaces. What changes is how those interfaces are presented and how you move between them.

\n\n\n\n

In some ways, I think that is much more interesting than simply designing another admin UI.

\n\n\n\n

We are not trying to decide what every WordPress application should look like. We are trying to give those applications a better place to live.

\n\n\n\n

And once you have that place, building actual OpenStation-native applications becomes possible as well. We have already been experimenting with things like a photo editor, project management tools and forms, but what excites me is not any individual application. It is the idea that WordPress can host an entire collection of tools that feel like they belong to the same workspace instead of a collection of isolated screens connected by a sidebar.

\n\n\n\n

So why did it take fifteen years?

\n\n\n\n

Probably because there was never a single moment where the old model stopped working.

\n\n\n\n

WordPress evolved gradually. A new menu here, another plugin there, a more sophisticated editor, WooCommerce, custom post types, page builders, analytics, SEO tools and so on. Each addition fitted reasonably well into what already existed, so there was never an obvious reason to stop and question the basic interaction model.

\n\n\n\n

But those small changes accumulated.

\n\n\n\n

The WordPress of today asks considerably more from wp-admin than the WordPress of fifteen years ago did, and I think that eventually creates an opportunity to revisit assumptions that once seemed completely reasonable.

\n\n\n\n

The assumption we are questioning with OpenStation is a very simple one:

\n\n\n\n

Why should opening something in WordPress mean leaving everything else behind?

\n\n\n\n

After spending months working this way, I now notice it every time I go back to the traditional flow. I open something, realise I need another part of WordPress, create another browser tab and immediately think: why am I doing this outside WordPress when WordPress itself could manage the workspace?

\n\n\n\n

That is probably the best way I can explain what we are building.

\n\n\n\n

WordPress has had applications for a very long time.

\n\n\n\n

Perhaps what it has been missing all these years is somewhere for those applications to actually live together.

\n\n\n\n

By the way, don’t forget you can always try OpenStation without even installing it in your site, using WordPress playgrounds

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 28 Sep 2026 12:57:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Daniel López\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"Open Channels FM: Open Source Champions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2563023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"https://openchannels.fm/open-source-champions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"The Open Source Champions initiative invites individuals and brands to support the network through a unique advocacy opportunity, offering exposure, promotional features, and participation in special episodes.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 28 Sep 2026 12:17:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:113:\"Gutenberg Times: Gutenberg 24.0, the road to 7.2, a new default theme named Ipsum, and more—Weekend Edition 377\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=47181\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:119:\"https://gutenbergtimes.com/gutenberg-24-0-the-road-to-7-2-a-new-default-theme-named-ipsum-and-more-weekend-edition-377/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:34343:\"

Howdy,

\n\n\n\n

Before anything else: if you maintain WordPress sites, go update them. WordPress 7.1.2 shipped on September 22 to patch a single critical vulnerability in page template resolution, one that lets an unauthenticated attacker load a chosen PHP file from outside your active theme’s directories.

\n\n\n\n

Now let’s move on to better things. Anne McCarthy is auctioning off her framed WordPress release albums, the ones given to release squad members. All the proceeds go to Stimpunks, a nonprofit started by Ryan Boren, who joined the project in 2003 and wrote the plugin system that nearly every site runs on. She calls the albums “a form of a gold medal to me,” and she built the auction site herself in a week. The starting bid is $500.

\n\n\n\n

We also learned this fortnight that the next default theme will be called Ipsum, which means 16 years of naming themes after the calendar is over. Admittedly, I’ll miss the old Twenty* names a little. But it’s time for something new for a new era.

\n\n\n\n

Two more quick things: WordPress has taken its turn leading the Open Website Alliance, alongside Drupal, Joomla!, and TYPO3, with Mary Hubbard holding the rotating presidency for the WordPress Foundation. And starting with 7.2 in December, release parties move from in-person events to livestreamed webinars, so the whole squad can actually be there.

\n\n\n\n

Enjoy your weekend!

\n\n\n\n

Your friendly neighborhood dev advocate, \"🍂\"
Justin Tadlock

\n\n\n
\n\n
\n\n\n
\n\n\n\n

Developing Gutenberg and WordPress

\n\n\n\n

Two security releases in six days. WordPress 7.1.2 is the urgent one, and it’s security-only: an unauthenticated attacker can, under the right conditions, make page template resolution include a readable local PHP file from outside the active theme directories. John Blackbourn led the release, Robert Ressl disclosed it, and the fix was backported to every eligible branch going back to 4.7.

\n\n\n\n

Five days earlier, WordPress 7.1.1 arrived as the regular maintenance release with 11 security fixes, 17 bug fixes on Core, and 19 for the Block Editor. Aaron Jorbin led it, and Anthropic is credited twice in the security list.

\n\n\n\n
\n\n\n\n

Aki Hamano announced what’s new in Gutenberg 24.0. The big feature: post title changes now show up in revisions with a proper diff, so you can stop guessing when a rename happened. The Gallery block gains a Grid variation with column count and “crop images to fit” configurable per breakpoint, and Site Title picks up fit-text, scaling to the width available instead of a fixed point size. And nearly 100 icons were redrawn on a stroke-based grid.

\n\n\n\n
\n\n\n\n

Stalled out somewhere between “clone the repo” and “why won’t this build”? Contributor Toolkit 1.2 from JuanMa Garrido now covers Gutenberg as well as Core, and it runs a stock WordPress in Playground with your checkout mounted as the plugin, already activated. No local server, no Docker.

\n\n\n\n

The road to 7.2

\n\n\n\n

Anne McCarthy published the roadmap to 7.2, and it looks to be a security-heavy cycle by WordPress standards. Sudo mode gates sensitive admin actions behind re-authentication, a new Secrets API gives credentials “a first-class way to store credentials safely,” and Application Passwords get hardened. Notes should gain a suggestion mode and emoji reactions. Designers get form element customization in Global Styles and custom block states. The final release lands in early December.

\n\n\n\n
\n\n\n\n

Real-time collaboration came out of WordPress 7.0, and Chris Zarate has now explained why in a post on moving to a server-aware approach for collaboration, written with Alec Geatches, Dennis Snell, ingeniumed, and Paul Kevan. The old design had browsers hold the post in a CRDT document and sync peer-to-peer, which broke three ways: the server couldn’t tell who made which edit, opening the door to content laundering; REST API and WP-CLI updates couldn’t participate, so saves became all-or-nothing overwrites; and a dropped connection could take your work with it. Three candidate sync engines are on the table, with a gutenberg-sync-engines repo to test against. If you build editorial tooling, have an opinion about this now.

\n\n\n\n
\n\n\n\n

The next default theme has a name, and for the first time in well over a decade, it isn’t a year. Henrique Iamarino introduced Ipsum, built with Carolina Nymark, Maggie Cabrera, and Juanfra Aldasoro. The reasoning behind the naming change: “default themes will have their own names and change when the design calls for it, not when the calendar does.” The theme is intentionally spare. It’s blog-first, has minimal typesets, and structural elements that stay invisible until you need them. The request is simple: “try it and tell us what breaks and what’s missing.”

\n\n\n\n
\"Screenshot
\n\n\n\n
\n\n\n\n

Nik Tsekouras opened a call for testing the DataForm editor inspector, which rebuilds the Post and Page tab of the Settings sidebar so it stops drifting from Quick Edit in the Site Editor. Install Gutenberg 24.0 or later and enable Editor Inspector: Use DataForm under Settings → Gutenberg. Test it as an editor, author, and contributor, not just as an admin.

\n\n\n\n

Behind the release

\n\n\n\n

A minor release can touch more than twenty branches, and much of that work was done by hand. Lance Willett opened a public repo of Core release tools, which includes tagging, release docs, SVN merge verification, and contributor lists.

\n\n\n\n
\n\n\n\n

Huzaifa Al Mesbah counted 84 people who tested WordPress 7.1 across 337 Trac tickets. Fifty were first-timers, which is 60% of everyone who showed up. The most important line: “you don’t need to be a developer.” 7.2 testing is open now.

\n\n\n\n

Plugins, Themes, and Tools for #nocode site builders and owners

\n\n\n\n

WooCommerce 11.2 lands the week of October 6, so read Shani Banerjee’s pre-release notes before it arrives rather than after. Order withdrawal emails become configurable, the CSV importer can match products by Global Unique ID when neither ID nor SKU is available, and checkout fields gain date support with min/max validation. Two of the seventeen developer advisories will bite if you ignore them: date filters in wc_get_orders() and wc_get_products() now read a bare date as a day in your store’s timezone rather than UTC, and the Cart and Checkout order summary becomes a fixed 360px column with the two-column breakpoint moving from 700px to 920px.

\n\n\n\n
\n\n\n\n

Two dot releases arrived in between, both flagged as security updates. WooCommerce 11.1.2 fixes the infinite recursion that was breaking product variation galleries, and 11.1.1 hardened API permissions and session handling.

\n\n\n\n
\n\n\n\n

The latest WordPress.com changelog moves the AI website builder from picking a theme to generating one: on Premium and Business plans, it “now generates a fully custom theme built around your goals and brand.” A new Annotate feature lets you queue several targeted edits and send them at once.

\n\n\n\n
\n\n\n\n

GatherPress started on a fourteen-hour drive to WordCamp US in 2018, when two Montclair meetup organizers came up with a name and then didn’t write any code for nine months. Rae Morey tells the story of how it grew into WordPress’ Meetup.com replacement, through July of this year, when Automattic’s Karen Arnold confirmed WordPress is going ahead with it. The gatherpress.org domain is transferring to the Foundation, and the plugin has been testable at events.wordpress.org since August 28. No launch date yet, and co-maintainer Mervin Hernandez Sitnikovski would rather you help than wait.

\n\n\n\n

Theme Development for Full Site Editing and Blocks

\n\n\n\n

WooCommerce has a new block theme. Brian Coords announced that Purple is back and ready for beta testing. The project was paused during a strategy update last year, and it’s Woo’s first official block theme.

\n\n\n\n
\"\"
\n\n\n\n

Ten color palettes, ten font pairings, custom styles for both WooCommerce and core blocks, and templates covering everything from Shop to Checkout to My Account. The inserter category is being renamed from “WooCommerce” to “Shop.” If you’re wondering where Storefront’s featured extensions went, block editing absorbed most of them. Peter Schimke also notes that Purple is now the default for new WordPress.com Commerce stores.

\n\n\n\n
\n\n\n\n

Mark your calendar for Wednesday, September 30 at 10 a.m. PDT / 1 p.m. EDT / 7 p.m. CEST: Woo is hosting a live session on building with WooCommerce block themes. Mike McAlister of Ollie joins Woo engineers Karol Manijak and Lucio Giannotta. There’s a Q&A at the end and a recording afterward, but questions only work if you show up.

\n\n\n\n
\n\n\n\n

“We need more workflow in Core,” said K. Adam White, principal engineer at Human Made, talking with Nathan Wrigley on WP Tavern about migrating to blocks with artisanal care and enterprise efficiency. At the center of it is Human Made’s open-source Rehydrator, which uses pattern HTML as a template and injects migrated content into it, so structure and styling survive a move off something like Sitecore. He describes building SQLite databases from client exports just to find the edge cases. He’s candid about the gaps, too: granular permissions, editorial approval workflows, and internationalization.

\n\n\n
\n
\n\n
\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n\n\n\n\n\n
\n

“Keeping up with Gutenberg – Index 2026”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly. 

\n
\n\n\n\n\n\n\n
\n

The previous years are also available:
2020 | 2021 | 2022 | 2023 | 2024 | 2025

\n
\n
\n\n\n

Building Blocks and Tools for the Block editor

\n\n\n\n

Your Query Loop returns nothing, and the heading and pagination you wrapped around it render anyway. Ryan Welcher spent a live stream adding a “hide if empty” control to Advanced Query Loop, his free plugin that extends the core Query Loop with taxonomy relationships, meta queries, and relative date filters.

\n\n\n
\n
\n\n
\n
\n\n\n
\n\n\n\n

Gutenberg’s JavaScript tests have moved off Jest. Marco Ciampini explains that unit and integration tests now use Vitest, driven by ESM: as more dependencies shipped ECMAScript modules, the CommonJS-based Jest setup needed more and more compatibility glue. The part that affects you: @wordpress/scripts 36.0.0 makes Vitest the default for test-unit-js, with @wordpress/eslint-plugin 27.0.0 following. Not ready to migrate? Switch to wp-scripts test-unit-jest and install the Jest dependencies yourself.

\n\n\n\n

AI in WordPress

\n\n\n\n

Your agent builds you a landing page, and then what? It sits in a chat log, or a folder, or a local dev server nobody else can reach. That’s the gap Spacefast is built for, and Automattic soft-launched it this week: Matt Mullenweg announced it on X. The pitch is the last mile for agent output: publish from a conversation with Claude or ChatGPT, from npx spacefast publish, or from a GitHub push, and get a permanent URL with immutable versions, one-click rollback, and access controls. It hosts full-stack projects, not just static files.

\n\n\n\n

The WordPress hook is a Spacefast plugin with two modes. Static mode hooks into Simply Static, exports your site, and publishes the snapshot. Headless mode treats WordPress as the content source for a repository project, triggering a production rebuild when you publish or update public content.

\n\n\n\n

MCP turns up everywhere

\n\n\n\n

WordPress Trac now speaks MCP. Lance Willett announced a Trac MCP server that’s “public and free to use: no account or API key needed.” Ask what’s left on a ticket and which pull requests are still open, or what someone committed in January 2005—yes, it goes back that far. It covers every WordPress.org Trac, from Core and Meta to bbPress and GlotPress. James LePage wrote the first version, with props to Jon Surrell, David Newman, and Konstantin Obenland.

\n\n\n\n
\n\n\n\n

Jamie Marsland makes the case for why WebMCP is going to be big for WordPress and, more usefully, shows you how to try it this afternoon: open the ChatGPT desktop app in Work mode, load WordPress Playground in its built-in browser, and ask it to build you a homepage. His framing is the clearest I’ve read. WebMCP gives an assistant “an instruction manual with working buttons” instead of making it squint at screenshots.

\n\n\n\n
\n\n\n\n

For the enterprise view of the same shift, Shane Schick compares WebMCP and traditional MCP and lands on a line I’d pull out of the whole piece: “MCP is not going away, and WebMCP shouldn’t be seen as a rival protocol.” His table sets them side by side on deployment, access scope, scalability, and auditability. That auditability row is the one that matters if you answer to a compliance team.

\n\n\n\n
\n\n\n\n

Schick also introduces Parse.ly MCP, which connects Parse.ly data to whichever assistant your team already uses. You authorize once with your existing login, and the assistant sees exactly the sites your account already sees. “Analysis that used to take a request and a day now takes a conversation.”

\n\n\n\n
\n\n\n\n

One more, for the security-conscious: WPShout walks through connecting Cursor to WordPress with MCP using ThemeIsle’s Easy MCP AI plugin. Every tool call still passes a WordPress capability check, with a 60-requests-per-minute default. Their advice is the part to take seriously: “read-only first, watch the audit log for a week, then grant write scopes deliberately.”

\n\n\n\n

Putting agents to work

\n\n\n\n

Anthropic open-sourced its commerce agents on September 2, and WooCommerce has already adapted them. Shani Banerjee walks through running the Claude Commerce Agent on WooCommerce, which spins up a demo store with eight products and nine orders in about fifteen minutes. The neat piece is a bridge plugin: the assistant’s cart lives under a Store API token your browser session can’t see, so at checkout the plugin re-adds each item to your real cart with normal stock checks. Merchant-side changes stage behind an approval gate, and “ask it to approve itself and it declines.”

\n\n\n\n
\n\n\n\n

There’s a second kind of visitor to design for now. Carlo Daniele argues for building WordPress for AI agents instead of just human visitors, and the distinction he draws is the useful one: “Crawlers primarily retrieve or index information. Agents can go a step further and take action on a user’s behalf.” That turns architecture questions into permission questions: who is asking, on whose behalf, what can they change, which actions need approval. The Abilities API and MCP Adapter are where WordPress answers them.

\n\n\n\n
\n\n\n\n

A week later, Daniele turned to operations. What happens when AI agents become your new website operators? works through a five-stage autonomy ladder and argues most teams should sit partway up it for a while. I feel like he’s right about that. As he puts it: “An agent that makes a bad production change creates another.”

\n\n\n\n

Learning and practice

\n\n\n\n

Want a structured introduction rather than a pile of blog posts? Destiny Kanno announced that the AI-Powered WordPress course is now live on Learn WordPress: four modules, 23 lessons, roughly nine hours. The first three are for anyone who publishes; the fourth introduces the developer APIs and assumes no prior PHP experience.

\n\n\n\n
\n\n\n\n

The AI team’s contributor summary for September 16 is a good snapshot of what’s actually moving. neillmcshea reports work on markdown feeds for the AI plugin, so AI clients can request a markdown version of a post. PHP AI Client 1.5.0 is close. There are still open gaps in web search support. For example, message parts can’t represent source annotations, and citation URLs are hard to retrieve.

\n\n\n\n
\n\n\n\n

Finally, a piece for the conversations you have with clients rather than with a terminal. Will Davis writes about how WordPress agencies use AI, and what clients should ask about it, arguing that the honest uses are the boring ones—code generation, QA, content migration, documentation—while architecture and governance stay human. His five questions for clients would work just as well on a sales call, starting with “What does a person review before it reaches me?” As he puts it, AI “genuinely reduces repetitive work, but it doesn’t replace judgment.”

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n\n\n\n\n\n
\n

Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.

\n
\n\n\n\n\n\n\n
\"\"
\n\n\n\n\n\n\n
\n

Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience.

\n
\n
\n\n\n
\n\n\n\n

Questions? Suggestions? Ideas?
Don’t hesitate to send them via email or
send me a message on WordPress Slack or Twitter @bph.

\n\n\n\n
\n\n\n\n

For questions to be answered on the Gutenberg Changelog,
send them to changelog@gutenbergtimes.com

\n\n\n

\n\n\n\n\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 26 Sep 2026 16:45:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"Dennis Snell: Enter the mess: Shortcodes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"https://fluffyandflakey.blog/?p=4130\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://fluffyandflakey.blog/2026/09/25/enter-the-mess-shortcodes/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1005:\"

Tonight I started working on some Shortcode processing in WordPress. This is an historically nasty problem because the Shortcode syntax and parsing is wildly dynamic.

\n\n\n\n\n\n\n\n

This is a problem that has plagued me for years and I have generally just ignored. There’s an open Core issue in Trac for changing some shortcode parsing (#50683), and I have thought a lot about it.

\n\n\n\n

But I think there is more to explore, and more to gain. Maybe this goes nowhere, but keep your eyes open for it.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 26 Sep 2026 02:43:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Dennis Snell\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"Open Channels FM: Your Website Could Use a Changelog to Fuel Creativity\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562622\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://openchannels.fm/your-website-could-use-a-changelog-to-fuel-creativity/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:220:\"A website changelog helps creators document progress, celebrate small wins, showcase evolution, fuel creativity, and build audience trust. It can include updates, humor, and various formats, making it accessible for all.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 25 Sep 2026 13:44:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"Open Channels FM: Is It Time to Move On? Navigating Change and Letting Go in Fast-Paced Times\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562603\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://openchannels.fm/is-it-time-to-move-on-navigating-change-and-letting-go-in-fast-paced-times/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"A reflection on recognizing the right time to move on from creative projects and handling self-doubt.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 25 Sep 2026 12:30:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"OpenStation Blog: “I can’t imagine using WordPress any other way”: the love behind OpenStation\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://openstation.blog/?p=1306\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:109:\"https://openstation.blog/2026/09/25/i-cant-imagine-using-wordpress-any-other-way-the-love-behind-openstation/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8731:\"
\"A
\n\n\n\n

OPENSTATION · COMMUNITY VOICES

\n\n\n\n

Formerly Desktop Mode, now a new way to feel at home in wp-admin.

\n\n\n\n

A plugin can accumulate installs. It is rarer for people to describe it as a new way of thinking. As of September 25, 2026, OpenStation, known in its earliest releases as Desktop Mode, has inspired 23 public WordPress.org reviews: 22 five-star and one four-star.

\n\n\n\n

OpenStation turns the WordPress admin into a spatial workspace: movable windows, a dock, a taskbar, widgets and virtual desktops. That is the feature list. The feeling is better told by the people who use it.

\n\n\n\n
\n\n\n\n

The words that stopped us in our tracks

\n\n\n\n

1. When a plugin becomes the default

\n\n\n\n
\n

“I can’t imagine using WordPress any other way. I love this plugin so much.”

\n
\n\n\n\n

— Nick Hamze, “Favorite plugin ever”

\n\n\n\n

That may be the highest compliment a tool can earn: not merely useful, but difficult to imagine living without. Nick’s review reads less like a rating and more like an invitation to join a movement.

\n\n\n\n
\n

“This is a game-changer. Can never go back!”

\n
\n\n\n\n

— ainom, “Absolute pure awesomeness”

\n\n\n\n

OpenStation begins as a striking visual idea, then quietly rewires expectations. Once several admin screens can live together, the old one-page-at-a-time flow feels surprisingly distant.

\n\n\n\n
\n\n\n\n

2. When the metaphor improves the work

\n\n\n\n
\n

“It genuinely feels like using a lightweight operating system inside WordPress.”

\n
\n\n\n\n

— spackenjaeger, “A revolutionary new WordPress admin experience”

\n\n\n\n

The operating-system metaphor is not decoration. Windows hold context. The dock makes tools reachable. Virtual desktops separate kinds of work. The familiar desktop grammar turns multitasking into something visible and natural.

\n\n\n\n
\n

“Having several admin screens open at once changed how I work more than I expected.”

\n
\n\n\n\n

— Juan Lentino, production user and plugin integrator

\n\n\n\n

Juan’s review is especially telling: he has run OpenStation in production since the Desktop Mode days and builds integrations against it. The novelty faded; the workflow remained.

\n\n\n\n
\n\n\n\n

3. When delight becomes productive

\n\n\n\n
\n

“The desktop-style layout, draggable windows, dock, and taskbar make the admin area feel completely different in the best way.”

\n
\n\n\n\n

— Marco Moreira, “A refreshing new way to use WordPress admin”

\n\n\n\n

Productivity software does not have to be joyless. The best interfaces reduce friction and add a little momentum, the feeling that the workspace is helping rather than merely waiting.

\n\n\n\n
\n

“This plugin blowed my mind. It turns your wordpress admin in such a beautiful dashboard. What an experience.”

\n
\n\n\n\n

— MauroS, “One word… Wow!”

\n\n\n\n

The wording is wonderfully unfiltered. Beauty, surprise and experience are not side effects here; they are part of the product.

\n\n\n\n
\n\n\n\n

4. When people see the road ahead

\n\n\n\n
\n

“This is definitely something I would use on a daily basis. Well done!”

\n
\n\n\n\n

— vepth, “I’m blown away”

\n\n\n\n
\n

“Desktop Mode definitely stands out with its own approach.”

\n
\n\n\n\n

— Rami Obeidat, “Modern and creative admin experience”

\n\n\n\n

Both reviews point to the same achievement: OpenStation is not chasing a generic “modern admin” look. It has a point of view—spatial, extensible and unmistakably its own.

\n\n\n\n
\n\n\n\n

From Desktop Mode to OpenStation

\n\n\n\n

The project’s name changed because its ambition outgrew a mode. “Desktop Mode” described the first transformation. OpenStation describes the platform emerging around it: a place where WordPress apps, windows, widgets and workflows can meet.

\n\n\n\n
\n

“The integration surface is unusually well behaved for a plugin this ambitious.”

\n
\n\n\n\n

— Juan Lentino, WordPress.org reviewer and integrator

\n\n\n\n

That sentence matters as much as the praise for the interface. The magic users see is supported by a public API that plugin authors can build on, frequent releases and an opt-in design that keeps classic WordPress one click away.

\n\n\n\n

The best roadmap is a chorus

\n\n\n\n

Names change. Interfaces evolve. Code ships, breaks, improves and ships again. What stays constant in these reviews is the feeling that WordPress can be more personal, more spatial and more alive.

\n\n\n\n

OpenStation is still moving fast. But if the people already living in it are any guide, the destination is worth watching, and the journey is already changing how they work.

\n\n\n\n

Explore OpenStation on GitHub →
Read all WordPress.org reviews →

\n\n\n\n

Quotes are excerpted from public WordPress.org reviews. Spelling is preserved; excerpts are linked to their original sources.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 25 Sep 2026 11:33:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Daniel López\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Matt: Bruce Schneier on Systems\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=155048\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://ma.tt/2026/09/schneier/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:460:\"
\n\n
\n\n\n\n

Bruce is one of my favorite writers. He packs profoundness. Also honored that he’s an advisor at Automattic, truly one of my idols. His blogs and books rocked my world when I was young.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 25 Sep 2026 07:04:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"Open Channels FM: How Generational Perspectives Shape Our Digital Work Lives\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562342\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://openchannels.fm/how-generational-perspectives-shape-our-digital-work-lives/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"Cami and Bob talk about adapting to tech changes growing older in the web industry and keeping routines that work.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 24 Sep 2026 14:30:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:109:\"Open Channels FM: Navigating Support Systems from the Man Cold to Open Source and WordPress Open Web Alliance\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562536\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://openchannels.fm/navigating-support-systems-from-the-man-cold-to-open-source-and-wordpress-open-web-alliance/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:132:\"Examining support systems behind open source, the open web, and everyday life, along with why sustaining these efforts is necessary.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 24 Sep 2026 13:02:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"Open Channels FM: The Podcast Open Makers is Archived\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562154\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"https://openchannels.fm/the-podcast-open-makers-is-archived/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:221:\"The podcast network has reduced its active lineup to four shows, leading to no new episodes for Open Makers. However, past content remains accessible, with a shift towards deeper discussions on open source and web trends.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Sep 2026 13:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"WPTavern: #234 – K. Adam White on Migrating to Blocks With Artisanal Care and Enterprise Efficiency\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=208362\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"https://wptavern.com/podcast/234-k-adam-white-on-migrating-to-blocks-with-artisanal-care-and-enterprise-efficiency\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:53882:\"
Transcript
\n

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

\n\n\n\n

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, migrating to blocks at an enterprise level and what’s involved in moving from a different CMS into WordPress.

\n\n\n\n

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

\n\n\n\n

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

\n\n\n\n

So on the podcast today, we have K. Adam White, or K. Adam for short.  K. Adam is the principal engineer at Human Made, an enterprise WordPress consultancy. He’s been involved with WordPress for almost 20 years, attending his first WordCamp in Boston back in 2011, and has contributed to WordPress Core and the broader open source ecosystem. Human Made is known for delivering complex projects, think high stakes, no room for mistakes? From global brands moving to WordPress.

\n\n\n\n

This time around,  K. Adam delivered a presentation at WordCamp US focused on a crucial topic for anyone modernising their site, migrating to blocks. Human Made has been all in on the block editor since the Gutenberg plugin days, and the team now specialises in large scale migrations from other content management systems like Sitecore, as well as from other WordPress page builders.

\n\n\n\n

Our conversation focused on the technical and editorial challenges of moving tens, or hundreds, of thousands of posts into the world of blocks and patterns. We talked about the need to combine artisanal care, attention to detail in design, layout, and brand, with industrial scale. The ability to automate, audit and validate mass migrations without losing visual fidelity.

\n\n\n\n

We also discussed the use of patterns as a foundation for development, integrating custom and Core blocks, and leveraging new tools, including AI powered agents and open source plugins like Human Made’s, own rehydrator, to streamline migration workflows.

\n\n\n\n

We also touched upon how clients are onboarded. The process of auditing legacy content. Strategies for training editorial teams on the block editor. And there’s a frank reflection on gaps in WordPress, like granular content permissions.

\n\n\n\n

If you are contemplating a move to the block editor, wrestling with a massive content migration, or curious about what happens when enterprise complexity meets the flexibility of WordPress, this episode is for you.

\n\n\n\n

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

\n\n\n\n

And so without further delay, I bring you  K. Adam White.

\n\n\n\n

I am joined on the podcast by K. Adam White. Hello, K. Adam.

\n\n\n\n

[00:03:41] K. Adam White: Hello. It’s good to be here.

\n\n\n\n

[00:03:42] Nathan Wrigley: Yeah. Thank you for joining us. You have an interesting name. Just go on, I know it’s totally off piste, but tell us about your name.

\n\n\n\n

[00:03:49] K. Adam White: Sure. It’s a first initial K, and the middle name Adam that got conjoined in college and I quite like it. So I think in a sphere, and a particular niche in WordPress with so many Adams of so many different colours, then K. Adam is a little bit more me.

\n\n\n\n

[00:04:04] Nathan Wrigley: Yeah, nice. So we’re in the corridor, so forgive any noise that you hear on this podcast episode. We can’t avoid it. We’re in the corridor at  WordCamp US, and you have done, some presentation work this time around. Do you want to just tell us, I mean I presume it’s happened because we’re at the very closing stages of the conference. How did it go?

\n\n\n\n

[00:04:21] K. Adam White: It went, as far as I can tell, quite well. My session was early yesterday, right after the morning keynotes in that early slot where everyone’s coffee has kicked in, and the fatigue of the conference hasn’t quite set in yet.

\n\n\n\n

So I had a great audience and the talk I thing went quite well. I’ve had a number of different conversations off the back of it on various different topics that I covered. So the breadth of those discussions has been really exciting for me.

\n\n\n\n

[00:04:44] Nathan Wrigley: So that is going to be the meat and the bones of what we’re going to talk about today. But first, if you don’t mind, let’s talk a little bit about you and what you do and where you work, just so that we can paint your credentials if you like.

\n\n\n\n

So tell us about your job, how long you’ve been in the WordPress space? Who do you work for? Et cetera.

\n\n\n\n

[00:04:59] K. Adam White: Yeah. My job is principal engineer at Human Made. We’re a WordPress enterprise consultancy, and I have been there nine years. I’ve been in the WordPress community quite a lot longer than that. My first WordCamp was WordCamp Boston 2011, which is a mind boggling 15 years ago now. And before that, I had been using WordPress personally since 2007. So we’re coming up on 20 years of involvement, at least as a user. And then, became a contributor in the early 2010s around 2013, I think my first commit landed.

\n\n\n\n

[00:05:25] Nathan Wrigley: Yeah, nice and Human Made, if you haven’t heard, we’ll put the links into the show notes, anything that K. Adam mentions today, we will put us a link on the WP Tavern podcast episode website, so you can click through to it. But go and check out Human Made, definitely one of the big hitters. I think it’s fair to say in the WordPress space.

\n\n\n\n

[00:05:40] K. Adam White: It’s very kind of you to say so.

\n\n\n\n

[00:05:42] Nathan Wrigley: You did your presentation and it was entitled, Migrating to Blocks. I’m going to intuit from that, that Human Made is all in on the block editor. You’re not using some sort of other proprietary platform. Would that be the case?

\n\n\n\n

[00:05:55] K. Adam White: That would be the case. We were very early adopters of Gutenberg back in its plugin days. We were doing work before it was merged for building out some early block sites, testing out what we could do. Learning how to build and change our theme development processes to move in a more block oriented direction, and then follow that directly into the Full Site Editor world.

\n\n\n\n

And it’s been a great ride. We do work with other page builders and other blocks, platforms and frameworks. We do tend to, as a company, work on projects that have some sort of particular technical complexity that made someone come to us rather than a different agency.

\n\n\n\n

That does mean that we are broadly specialised in WordPress as a platform, including many of those page builders. We’ve worked with Elementor, we’ve worked with Divi, Beaver Builder, but we as a company will always advocate for the block editor and the site editor. And we have our own processes oriented more and more towards delivery with that framework in mind.

\n\n\n\n

I think that the thing that is bringing some of the companies that we help to migrate to WordPress into this ecosystem is the flexibility and the quality of the editorial experience. And personally, my opinion is that Gutenberg does that leaps and bounds better than any of our other page builders that don’t have that native integration into the platform.

\n\n\n\n

[00:07:09] Nathan Wrigley: So if a client comes to you and they are agnostic as to what you are going to build with, your default posture would be we are going to use the block editor.

\n\n\n\n

[00:07:16] K. Adam White: Absolutely default.

\n\n\n\n

[00:07:17] Nathan Wrigley: Okay. And do you have to do any level of persuasion anymore? I’m guessing if we were to rewind the clock, let’s go to 2017, soon after Gutenberg started to become more widely available. I imagine there was quite a bit of explaining to do. Do you still have to do any of that? Or is it a case now that the enterprise people understand what’s going on, and there’s less of a back and forth about whether they should use blocks and patterns and whatever else?

\n\n\n\n

[00:07:41] K. Adam White: If we are building from scratch, we haven’t found there is any reluctance. Particularly if people are coming from a different content management system, particularly a different enterprise content management system. The editor is so compelling, that there’s never any objection to using it. They might ask, should we use this or some other thing I’ve heard of? And we can say, the block editor is built in. We feel that it’s the most robust and future proof platform that you can choose. So we would recommend going that route rather than adding in another plugin, however good they are.

\n\n\n\n

But we do still, nonetheless, have some projects where they are already on a page builder, and they might have invested a lot of training. We might have an entire business school worth of people that are very comfortable with whatever their existing system is, whether that’s Beaver Builder or something else, et cetera, Elementor.

\n\n\n\n

And I think that it’s very important for us to remember what our remit is when we come into a project. That, doesn’t always involve helping them change everything to match what we see as the future. I think that’s a responsibility of the client to understand where they are in conjunction with where the WordPress roadmap is, and make their own decisions about what tools are right for them.

\n\n\n\n

So, for existing projects, we’ll work with what’s right for the clients editorial team, but if we have to make a recommendation, it will always be the block editor.

\n\n\n\n

[00:08:56] Nathan Wrigley: Okay. Yeah, good to know. At place in the market where you are, I’m presuming there’s very little room for error. When you build something, it’s got to work out of the box, on day one. You’ve presumably got stakeholders who’ve got editorial teams, and they’re fairly, we’re, dealing with large corporations that can’t afford for there to be mistakes.

\n\n\n\n

So that kind of leads us to the nature of your presentation, which was called, and again, links will be in the show notes on wptavern.com. Migrating to Blocks with Artisanal Care and Industrial Scale. And I’m actually just going to read the first paragraph because it summarises what we’re going to talk about perfectly. It’s fairly long, but I’ll go through it all.

\n\n\n\n

Whether we’re modernising an old personal blog or migrating hundreds of thousands of existing posts from another CMS. Using WordPress in 2026 means converting our contents to blocks. The convert to blocks button in the editor works well enough for one post. But if we have dozens or hundreds, what can we do to make the process less manual and more powerful? How can we integrate a site’s content directly into full block patterns without losing the columns and structure it had before? And then it goes on to mention, a particular build, I presume, where you were leaving one CMS coming into WordPress.

\n\n\n\n

Just lay out some of the fun, interesting problems that you have to overcome when you’re moving from an entirely different CMS into WordPress, because I guess it’s more complicated than, “Look, there’s a bunch of paragraphs and images. Let’s just drag those over and hope for the best.” Tell us what the problem before you is.

\n\n\n\n

[00:10:22] K. Adam White: That’s a great question. It’s actually remarkable how close you can get to satisfaction with just moving paragraphs and images over and hoping for the best. But there is a big gap in terms of visual fidelity.

\n\n\n\n

The editor in a theme that we’ve built for a client will be configured with patterns and templates and all of the block variations that they need to be able to very quickly sketch out a page. If they are starting from scratch, a client with a fully site editing enabled theme can drop a hero pattern on the page, set in the media they need. Change any font sizes within the pallet of what’s available with their brand guidelines encoded in the theme.json. It’s very easy for them to build out and write content fresh.

\n\n\n\n

But if you have, again, hundreds of thousands of posts, even if you’ve built all those patterns, the heading and paragraph and image only approach doesn’t cut it, because then there would be a tremendously backbreaking amount of work, adding group blocks, adding background colours, et cetera.

\n\n\n\n

That’s usually data that is available in one form or the other in the current system. If we’re migrating without a design change, we will have, whether it’s the layout database in Sitecore or a metadata in a different WordPress block editor that we’re migrating from. Or whatever the equivalent is in our source. We want to preserve the layout of the page and the styling elements. So making sure that headings get the right text treatment, that anything that’s italicised comes over. All of the nuances there, particularly around background colours, images, et cetera. That’s the piece that we’ve been over the past year, looking at how we can improve our process when we’re building a new site, but bringing content over from an old.

\n\n\n\n

Within that context, my talk covered two broad areas. The specific tail end of the talk was about how we can actually use the theme patterns that already exist in the theme directory, and use those to inject particular pieces of source data. So if you have a pattern for a hero element, and you know from your source data what the image URL is supposed to be, what the title is supposed to be. We can use the HTML directly from the pattern file, and do lightweight search replaces within that using either direct PHP string replacements or a tool that we’ve written, that I shared a link to called rehydrator, which is a very early stage experiment, that we’ve got out on GitHub.

\n\n\n\n

And we can use that to put the content into the structure that it’s going to need to have for it to be fully, visually correct. So rather than just reducing and throwing away anything that isn’t a heading or a paragraph, we’re taking the framework from the theme pattern that’s been built. And then we’re writing a migrator that takes data and puts it into that HTML structure, and saves that into the post content. So that when an editor opens up a page, it loads correctly in the editor without block validation errors and it looks right on the front end.

\n\n\n\n

[00:13:15] Nathan Wrigley: Okay. There’s a lot of depth in that, isn’t there? We’ll come back to that in a moment.

\n\n\n\n

I’m curious about process of how you, persuade clients that you are going to be able to carry this work out successfully. So how does that actually work? You obviously look at their existing content, you have a discussion about what the new design is going to look like, and then do you build out some kind of templates or patterns or what have you, so that you can then pull in a proportion of the content, maybe, I don’t know, 10 or a hundred or 5,000 or whatever it may be, pieces of content. Check that that’s all right. Show it to the client. How does that workflow go to build up their confidence that what you are going to do when you finally click the button is actually going to succeed?

\n\n\n\n

[00:13:50] K. Adam White: The way that we’ve been approaching that, I think particularly, over the past six months, I should caveat first that this process has changed so much. Because the tools we have available with AI agents have been evolving in leaps and bounds alongside this particular migration process, which started in January.

\n\n\n\n

So in this case, we started out by building patterns that we could put content for one test post, from the existing site manually. Bringing the contents over, copying and pasting headings, et cetera. And using that to create the patterns that we could show to the client to say, does this look correct? Does this structure mirror what you’re expecting? Is this what you expect an author to have available within the post editor?

\n\n\n\n

And then you know, which pieces belong in the template, which pieces are managed at the site editor level? We’ve done a lot of that ahead of starting the actual migration.

\n\n\n\n

Now that the migration is in progress, any subsequent pieces we’re developing in tandem, we’re saying, okay, we have a press release. That press release, we have audited the incoming data, and we have determined that there are four different layouts for press releases. And this one is used the most and it has these elements. This one is used less, but it has images, et cetera.

\n\n\n\n

And we can build the template for that post type, and at the same time write the migrator for identifying the content nodes, and the source data and bringing that information over into the new patterns.

\n\n\n\n

So we have the patterns that we can show, okay, if you’re building something from scratch, this is what that looks like in the editor. But then at the same time, we can run the migrator over, in most cases, all of the relevant type of data and say, and here is a list of pages to validate.

\n\n\n\n

So what we’ve been doing is bringing that to our stakeholder, and allowing them to do spot checks, so that they can look through and validate that there are all of the required elements on the test pages. Things like, “oh, alright, we don’t have a mapper yet for video embeds. So videos are missing,” and that’s usually going to be an all or nothing thing. We’ve found very few cases where we end up with one or two errors on a specific post basis that aren’t related to support for a complete type of output pattern.

\n\n\n\n

[00:15:55] Nathan Wrigley: Is there a sort of fault tolerance there? So obviously in the case of this particular migration, tens of thousands of posts, I guess there’s never going to be a moment where you can be a hundred percent confident apart from reading the 10,000 posts that you’ve done everything correctly. Is there a, we’ll do 10 to begin with, then we’ll go up to a hundred, then we’ll go up to a thousand.

\n\n\n\n

What, is the sort of tolerance that you present to the client? I’m just imagining that just lurking in post 9,999 is just some weird thing that was allowable in the CMS but never got used before or since, and that piece of content got missed. I don’t know what’s allowable in that scenario. So is there any level of tolerance for fault?

\n\n\n\n

[00:16:32] K. Adam White: The major advance that we’ve made with migrations as a broad structure this year is a much better understanding of those edge cases. And the way that we’ve done that is by leveraging Claude and various other tools to do cross site audits to make sure that we have a full picture of the source data.

\n\n\n\n

So we are able to feed in whatever export files we get from our source site. In this case we’re working from Sitecore, which is an enterprise CMS, which has two database structure. There’s actually a database with a content tree, and then another database that contains layout information. And a page is rendered by switching back and forth between those and assembling the final output.

\n\n\n\n

We were able to get exports of the relevant content from both of those, from the developer of the current site. And we fed those and a whole bunch of documents from the product owner into a ongoing conversation with Claude. And we’re able to use that to build some actually node.js scripts that would take the files we’d gotten from the Sitecore devs, and build a local database in SQLite that each developer on the team was able to run locally. And we can query against that to find those edge cases.

\n\n\n\n

So in a combination of writing our own manual queries, or having a chat conversation prompt for finding individual things, and then it will run a number of queries and report back to us. We’re able to identify very quickly, oh, there’s only one press release that has images, that’s interesting. But there are 17 that have a FAQ accordion.

\n\n\n\n

So that type of auditing has become trivial, and it’s mind boggling how much faster that’s allowed us to move in terms of understanding the data that’s there, and building out a mapping of how we’ll migrate through the different types of content.

\n\n\n\n

We don’t tend to start with only 10 pages in a post type because it’s relatively cheap to run the migrator over a thousand instead of 10. And that gives you a lot more content for both various people on the client team, but then also agentic tools to click through and do a little bit of spot check validation.

\n\n\n\n

What we tend to do is to migrate content type by content type, and we’ll prioritise those based on what we see as the balance between scale and complexity.

\n\n\n\n

[00:18:39] Nathan Wrigley: Do you leverage Core blocks wherever possible, or do you bring bespoke Human Made blocks where that’s necessary? Or can you basically bind everything in this particular build to a Core block?

\n\n\n\n

[00:18:51] K. Adam White: Most of the time we will start with Core blocks and get as far as we can with them. This is a change from how we used to do it. Our early days, we had a lot of rapid iteration in the markup that Core blocks were using. In some cases, there was a lot of evolution in how the controls for them were set up.

\n\n\n\n

[00:19:07] Nathan Wrigley: It was brutal.

\n\n\n\n

[00:19:09] K. Adam White: It was brutal. But that pace of change for the main building blocks of a site has slowed down tremendously, and I think it’s a very stable foundation. So we will be pattern first in our development. We will start by working, doing a lot of in-editor prototyping actually, to build out layouts and patterns for each individual unit of content, each individual sort of component group in the source site. And, it will only be when we run into something like a carousel or a modal that we might reach for a off the shelf, third party option that’s not in Core, or bring our own solution to the table.

\n\n\n\n

[00:19:45] Nathan Wrigley: So do you take, when you said pattern there, is a pattern a sub component of a, let’s say post for want of a better word? Or is it that the pattern is the entire post with bits injected into it? So paragraphs, headings, videos, whatever it may be? Like I said, at the beginning, or are you building up the entire post from various different patterns? Here’s a video pattern and here’s a, I don’t know, a paragraph pattern with a heading? Or a background image or whatever it may be.

\n\n\n\n

[00:20:12] K. Adam White: Patterns tends to be at number of different levels. We might have individual patterns for a particular treatment of headline for example. But we also will have a pattern for a hero section. We’ll have a pattern for a hero section plus the bio below that, that we can use to populate a template in the site editor.

\n\n\n\n

We build patterns at multiple levels of granularity, and we have a leaf to trunk system where we’ll make sure that we have renderings, whether they’re Core blocks with either default styling or one or two block variations, or individual patterns for things where we need to compose one or two blocks together. We’ll make sure that we have all of those leaf node pieces of content, all of our paragraphs, all of our inline images. And then we’ll build patterns for those higher level groups, the full width backgrounds with coloration and a particular headline treatment.

\n\n\n\n

We build out those patterns at all of those different levels because it’s nice to have the granularity when we’re writing our migrators, and patterns can reference each other. So you can have an accordion pattern, which includes two references to an accordion item pattern, and you can have all of those little bits of HTML be discreet PHP files in your WordPress theme. So it makes it very simple to pull up in your editor only the code that you need to edit for a particular unit and know how that’s going to be scoped.

\n\n\n\n

[00:21:26] Nathan Wrigley: This is going to sound like such a peculiar question, but it genuinely, from my point of view, this sounds like really interesting and curious work. It sounds, like there’s a lot to get your teeth into. You’re pushing the boundaries a little bit, but also you’ve got the scope of WordPress, which kind of makes it slightly easier.

\n\n\n\n

I’m basically just making the comment that I think I would enjoy doing the work that you are doing. I don’t know if that, yeah, there really a question there.

\n\n\n\n

[00:21:47] K. Adam White: Unfortunately, we’re doing less and less of that work, and Claude’s doing more and more of it. It’s been actually very efficient because this is such a core central construct in the WordPress block editor. There’s a lot of good documentation about it and agentic tools are quite good at helping to build pattern markup.

\n\n\n\n

So, what we’ve been doing is bringing our human eyes onto that, doing all of our spot checks, making sure that things are kept as simple as possible. Because I think we’re all familiar with how verbose and overly complicated output can be from some tools. But then it is also something that I really wish more people were talking about and doing. Brian Coords earlier today in his talk, mentioned that pattern driven development really he sees as something that more and more of the WordPress community should be trying out. Because there are so many things that we used to build custom blocks for, that just strictly aren’t necessary anymore. And we can get so far by composing what we get from the lego kit of WordPress out of the box.

\n\n\n\n

[00:22:40] Nathan Wrigley: Yeah, I feel like if we went back to 2015 and began Gutenberg again, I feel going patterns first would actually be a nicer approach, certainly a more straightforward approach. I know that there’s, ways to overcome that, but I always drop patterns in, never blocks, and then I’m always interacting with the blocks within the pattern. But it’s patterns first for me all the time. Just because I like the fact that I’m dropping in multiple bits of content that are pre-configured and pre-made and pre, I’ve fiddled with the CSS and made it just how I like it. And I just click the button once and there it is, and I can just rinse and repeat and it’s really straightforward.

\n\n\n\n

[00:23:12] K. Adam White: I would agree, and over the past two to five releases of WordPress, we’ve also had such powerful additional tools added to the pattern toolkit. For example, Partially Synced Patterns. Was a major topic that I shared in my talk. Being able to have a reusable pattern and then make the content editable on a post by post basis makes it very seamless for a non-technical editor to go in, and not have access out of the box to stylistic controls that would make something drift from the brand’s guidelines that they’re trying to follow, but still be able to customise link targets, CTA, text, all of the descriptive and image elements.

\n\n\n\n

[00:23:47] Nathan Wrigley: You are in the weeds of WordPress, and I’m in the weeds of WordPress all the time, but I still feel those tools are widely, not misunderstood, that’s the wrong, just there’s a void. Nobody even knows they’re there. There’s just tonnes of tooling inside the block editor that people simply don’t know about, because the UI and the UX is still a bit funky. You’ve got to go to various different places, and it’s easy to go down the wrong route.

\n\n\n\n

Do you know what I mean? There’s a bunch of tools inside a WordPress that if you only had a few hours with somebody over your shoulder pointing out, “okay, click on that, look at that menu that does this thing.” It’s a shame in a way that’s the case. But I do feel there’s a lot of unexplored potential in every WordPress website that presumably you are leveraging. But I guess just because you’re in the weeds of it.

\n\n\n\n

[00:24:30] K. Adam White: Wherever possible, we have the privilege of having a lot of history with the CMS. Human Made was founded in 2010 and has always had a strong open source posture. We’ve contributed to Core, we’ve put plugins out there in the ecosystem that are used by a number of other agencies. We’ve found the best of what our frenemy competitors use, and been able to adopt those into our own processes.

\n\n\n\n

And the benefits of understanding all of the different types of block that you can use tremendously outweigh any time sink that it takes to learn them. I hope that, from my talk, people will now know that in 7.0, we added PHP only blocks, where you can have the attributes auto registered so that you get, even as a non JavaScript developer, a interface in the editor that someone can open up and go in and change values in the sidebar.

\n\n\n\n

I hope that more people learn about Partially Synced Patterns. I hope more people learn about all of the different types of block that we have available, and find ways to integrate those into their own toolkits. Because playing with the grain of WordPress and using the Block Editor for all it’s worth, are how we untap the most value for our clients.

\n\n\n\n

[00:25:34] Nathan Wrigley: Yeah, there is certainly an awful lot of power, and like I said, I just think some of it gets missed.

\n\n\n\n

How much after you’ve done the migration, how much time do you have to spend with the clients? I have this impression that the Gutenberg editor is pretty straightforward, muscle memory for me essentially. Hours of playing in it. I know where all the bits and pieces are.

\n\n\n\n

But I would also recognise that if I was to show it to somebody who’d never played with WordPress and was coming from, in this case Sitecore, how overwhelming is it? And do you take steps to make it less overwhelming by minimising what’s available in the interface, or just disabling options? What do you do in that regard?

\n\n\n\n

[00:26:08] K. Adam White: No matter how much flexibility our clients want, it’s usually valuable to disable some options. I can’t remember a site we’ve shipped recently for any large website where we left the custom colour picker in, for example. You want to do a better job of limiting what people can use, so that we have confidence that the output, no matter how design savvy or not someone is, is going to be consistent with the rest of the site.

\n\n\n\n

My colleague, Joeleen Kennedy, gave a talk a couple years ago at the first  WordCamp US Showcase Day back in 2024, about work we had done customising the editor for that type of simplicity. And in particular things that we can do around colour palette selection. Ways that we can hide the styling controls for certain blocks through having them embedded in a pattern.

\n\n\n\n

It’s interesting to see that in WordPress recently, if you are editing content that has been marked as having come from a pattern in a post, you can edit all of the text, you can edit all of the images and link targets, but you actually have to hit edit pattern in the sidebar in some cases, depending on how the post is set up, to get into the details within the post that allow all of those other controls to be visible.

\n\n\n\n

That divide took a tiny bit of adjustment for people on our client teams, but the separation has helped them stay focused on the content, and worry less about the overwhelming, combinatorial set of styling possibilities that their blocks have.

\n\n\n\n

[00:27:29] Nathan Wrigley: Do you think that the necessary tools are already built into WordPress to do the kind of work that you are doing? Or is there some missing piece that would make it easier for somebody who doesn’t have the deep pockets that presumably Human Made would require, to do that kind of work. Is the default tooling usually okay to migrate things or have you had to build loads of bespoke tooling?

\n\n\n\n

So in terms of if I was to approach a WordPress website and try to migrate from Sitecore over to WordPress, is this something that you absolutely need a team to do, or would you be able to get some simulation of this with Core WordPress?

\n\n\n\n

[00:28:04] K. Adam White: If you had access to the exports of data from a Sitecore website, and you had a core vanilla WordPress install. And you had a LLM tool of some sort, I think that you could do a lot to get close to what you want. The LLM piece, I think enables this to be done by more people without having to be completely familiar with all of the internal nuances of WordPress. You need to direct it to the architectural pattern that you want, but we have found that it speaks Gutenberg pretty well.

\n\n\n\n

[00:28:32] Nathan Wrigley: What was the name of the tool that you said you’d custom and built?

\n\n\n\n

[00:28:34] K. Adam White: We had built a plugin called rehydrator.

\n\n\n\n

[00:28:36] Nathan Wrigley: Okay, rehydrator, yeah.

\n\n\n\n

[00:28:37] K. Adam White: rehydrator is the tool that we use to take a pattern in the theme and then use that pattern as the template when we’re bringing content over to make sure that we keep all of the styling theme side, and that our migration script doesn’t duplicate the markup specifically.

\n\n\n\n

[00:28:51] Nathan Wrigley: What’s Human Made’s approach to the WordPress project in that regard? You said it was a plugin. Does that mean it’s a wordpress.org repository plugin, or is it one that you have on your own, I don’t know, GitHub repository or whatever it may be.

\n\n\n\n

[00:29:01] K. Adam White: We have some things in the .org repository. In this case, that particular plugin is only on GitHub. A number of ones that we build are only on GitHub, because we’re building them for a very transient in time period of a site.

\n\n\n\n

You don’t need a migration tool to be part of your site long term, it’s not something you’re going to be leaving active, and updating month over month when there is a site running. It’s something that you bring in for the purpose of populating the data. And then you can remove that.

\n\n\n\n

And in that regard, for this particular one, at the moment it’s partly because it’s quite young, and it’s also because we don’t see it as being general purpose. So that plugin specifically is on GitHub and publicly available through Composer, but not on the plugin directory.

\n\n\n\n

In other situations, we’ve gone the opposite direction, and anything that we see as being a ongoing value to a site as it’s running, we do try to move those over as we can.

\n\n\n\n

[00:29:52] Nathan Wrigley: Given that you are on the sort of engineering side of Human Made, I don’t know if this question will land, but we seem to be in this interesting period where there’s a lot of chatter, AI kind of fits into the equation a little bit, but there’s a lot of chatter about the, market share of WordPress and whether or not WordPress as a tool will continue with the same numbers and clout and market share and all of those kind of things.

\n\n\n\n

Do you notice at the enterprise level that there’s been any kind of change in a southerly direction? Maybe there’s been a direct change in a northerly direction. What I’m trying to say is, for the enterprise, does WordPress still maintain that kind of pride place, top of the tree, or are you struggling to find new clients?

\n\n\n\n

[00:30:28] K. Adam White: We’re not struggling to find new clients. We’re lucky that we’re doing quite well on marketing, and we also have had a very powerful year in terms of building relationships with new enterprises, and finding ways to take the technology that we believe in and solve their problems with it.

\n\n\n\n

But I would argue that WordPress has never been the top of the enterprise space. And this actually goes back to your question about what is there that might be missing inside WordPress. The biggest thing that I think someone gets from a more, I’m going to use the term loosely, traditional enterprise CMS, is control.

\n\n\n\n

And WordPress has a security model where the ability to edit and publish a piece of content is usually at the post level. There’s ways to add specific permission checks for metadata. There’s ways that you can restrict what’s accessible and editable with custom interfaces and custom API endpoints. But we tend to have things fall down to the capability checks for user can edit post 1, 2, 3. Yes. No.

\n\n\n\n

And that means that if you have a user profile where your organisation depends on someone being able to come in and touch only the headlines and the SEO metadata, we don’t really have a model for that right now in WordPress.

\n\n\n\n

Whereas something like Sitecore, each individual, almost at the level of every string on the site, whether it’s a set of paragraphs or the label of a button, ends up as a individual node in the content tree. And those can be granted or denied to certain users on a much more granular level. So that to me is a bridge that I still am excited to see what we can do within WordPress to maybe build better interfaces, or better primitives in the editor.

\n\n\n\n

Block locking helps a little bit, but it is an API that’s quite difficult for some teams to wrap their heads around. And it also doesn’t really change the fact that if you can edit the post, and you were able to get the code editor up, then if you’re able to save it, you’re able to save it and doesn’t really go block by block. You’d have to write custom validation or permissions logic in order to be able to reject and update based on the user if they’re editing a block that is next to the one that they were supposed to.

\n\n\n\n

[00:32:32] Nathan Wrigley: So do you have to present to the clients? It’ll be fine. This is what WordPress has. Don’t worry too much about it. If you’ve got this permission, yep, sure. You might be able to overlap and think people could delete things or modify things that perhaps they wouldn’t have to. That’s an educational piece on your side. Go and teach everybody not to mess around with things that they shouldn’t be messing around with.

\n\n\n\n

But you would wish that in WordPress you could assign, say, as you described, this H1, this person can amend it, and this person can access the colour palette for the background image over here, but they can’t access the text. That kind of really granular permission. Whereas block locking just, it seems a bit more of a blunt instrument if you know what I mean. It’s binary. It’s locked or it’s not. You’d like to unlock the capabilities within each block so that certain users can do certain things within the same block.

\n\n\n\n

[00:33:15] K. Adam White: Within blocks, we tend to rely on security through obscurity. We can hide or obfuscate controls behind block locking with content only. We can hide them behind patterns. But if someone’s coming to WordPress, we do make sure that they understand upfront what the nuance of control will be. And we will work with them usually to make things more editable.

\n\n\n\n

Again, I will mention that most of the projects that we get that come from one of these more control-oriented CMSs into WordPress, what they’re seeking is actually more flexibility, not less. So they’re making a decision that they are willing to exchange the stringent control that they get in their existing tool for a process-based change. Maybe they add a review step, or add some sort of workflow plugin, so that we can validate that things look good and have someone sign off on it before it gets published. They would prefer to go that route than to sacrifice the ability for the editors to have the full control, and full pallet of options available to them.

\n\n\n\n

[00:34:13] Nathan Wrigley: Right, so that’s a much more loose approach. Everybody can maybe do more than they ought to do. If we have some editorial guideline where that can’t finally hit the public domain because the publish button is unavailable to you, that’s, okay. We’ll accept that kinda halfway house, if you like. That’s interesting.

\n\n\n\n

[00:34:30] K. Adam White: Each client’s needs are going to be slightly different. We do layer in publication checklists. We have tools to be able to say, this has to be tagged with the primary category before it goes live. We have tools to say, this still has lorum ipsum in it. You can add those in and build workflows, but I tend to like to help clients build processes to support those, rather than trying to take a draconian approach and lock everything down. Because then your work is going to be constantly chasing fine-grained permissions controls when you could be working to use that time making sure that all of the editors know what they can do.

\n\n\n\n

[00:35:04] Nathan Wrigley: I just want to drill into this a bit more. I know this isn’t where we were supposed to go, but I find it really interesting. Would you like those things to ship in Core? obviously they suit you down to the ground, all of those granular permissions, but do you think that belongs in Core?

\n\n\n\n

[00:35:17] K. Adam White: I think that we need more workflow in Core.

\n\n\n\n

[00:35:20] Nathan Wrigley: Okay.

\n\n\n\n

[00:35:20] K. Adam White: I know that there’s a number of different agencies and hosts which each have developed our own workflows solutions. I’ve worked across a number of them on projects that I’ve helped to support.

\n\n\n\n

But the notion that if you have something published and you make an edit out of the box, WordPress will automatically put live any further changes that you make to a published post when you hit save. That is probably the single thing that we most frequently have to build some type of plugin into a site to handle.

\n\n\n\n

Because we need to be able to give people an editorial review step. So that is something that I think we have a number of good tools, but I would love to see a more opinionated default in Core that we can use as a foundation for more complicated post editorial workflow. I think that’s the thing that we most frequently run into. That, and also I guess internationalisation are probably the two things that hopefully will come to the surface of the WordPress roadmap over time.

\n\n\n\n

[00:36:13] Nathan Wrigley: Yeah, I’d really not thought about that. Given Human Made’s sort of credentials and what have you. Do you have a lot of clout? Do you just punch above your weight in conversations about what makes it into Core? Do you get involved in those discussions? I’ve literally no idea how that would happen. Do you communicate to people when a release is coming around. Do you have a voice? Do you make yourself available? What is Human Made’s position in terms of getting things pushed into Core?

\n\n\n\n

[00:36:37] K. Adam White: We participate in the project. I personally have been less involved in Core over the past several years than I would have hoped. I’ve been very much enjoying the detailed, quite close to the ground work that I’m doing on our agency projects. But unfortunately, I have taken a bit of a step back on the open source project.

\n\n\n\n

Some of my colleagues are in a slightly different boat. My colleague, John Blackbourn, our Director of Security for our own hosting product is also the head of the Security Team for WordPress? And has been helping us get the core patches out for the recent set of security releases.

\n\n\n\n

We obviously will advocate in calls for feedback within the Gutenberg project when we feel that there’s a particular direction that we see from our projects. We are able to provide feedback on the UI, and the capabilities of new blocks that are being proposed. But that’s all done through the normal Gutenberg GitHub issue, and WordPress

\n\n\n\n

[00:37:28] Nathan Wrigley: So I think we should probably knock it on the head there. We’ve reached our allocated time. I’ll just point out that these days, it used to be the case that if I was at a WordCamp, you’d really have to wait about six months before the video for the presentation was available. I’m pretty sure it’ll be done already, in all honesty. 24 hours seems to be the time there. So if you were to go to WP Tavern, I will make sure that the link to the video, of K. Adam is there. If not, you can probably go to Google and search Migrating to Blocks, and in parenthesis, with Artisanal Care at Industrial Scale, and you’ll be able to see what it is that K. Adam was talking about.

\n\n\n\n

But really, thank you so much for chatting to me today about all of that.

\n\n\n\n

[00:38:06] K. Adam White: Thank you very much. And I can confirm that the video is already live on YouTube.

\n
\n\n\n\n

On the podcast today we have K. Adam White, or K. Adam for short.

\n\n\n\n

K. Adam is the principal engineer at Human Made, an enterprise WordPress consultancy. He’s been involved with WordPress almost 20 years, attended his first WordCamp in Boston back in 2011, and has contributed to WordPress Core and the broader open source ecosystem. Human Made is known for delivering complex projects, think high stakes, no room for mistakes, from global brands moving to WordPress.

\n\n\n\n

This time around, K. Adam delivered a presentation at WordCamp US focused on a crucial topic for anyone modernising their site, migrating to blocks. Human Made has been all-in on the block editor since the Gutenberg plugin days, and the team now specialises in large-scale migrations from other content management systems like Sitecore, as well as from other WordPress page builders.

\n\n\n\n

Our conversation focused on the technical and editorial challenges of moving tens or hundreds of thousands of posts into the world of blocks and patterns. We talked about the need to combine “artisanal care”, attention to detail in design, layout, and brand, with “industrial scale”, the ability to automate, audit, and validate mass migrations without losing visual fidelity.

\n\n\n\n

We also discussed the use of patterns as a foundation for development, integrating custom and Core blocks, and leveraging new tools (including AI-powered agents and open source plugins like Human Made’s own rehydrator) to streamline migration workflows. We also touched upon how clients are onboarded, the process of auditing legacy content, strategies for training editorial teams on the block editor, and there’s a frank reflection on gaps in WordPress, like granular content permissions.

\n\n\n\n

If you’re contemplating a move to the block editor, wrestling with a massive content migration, or curious about what happens when enterprise complexity meets the flexibility of WordPress, this episode is for you.

\n\n\n\n

Useful links

\n\n\n\n

Human Made

\n\n\n\n

Migrating to Blocks (With Artisanal Care, at Industrial Scale) – K. Adam’s presentation at WordCamp US 2026

\n\n\n\n

Human Made’s rehydrator plugin on GitHub

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Sep 2026 12:53:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"WordPress.org blog: WordPress 7.1.2 Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=21731\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wordpress.org/news/2026/09/wordpress-7-1-2-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3425:\"

This security release features a fix for a critical severity security vulnerability.

\n\n\n\n

Because this is a security release, it is recommended that you update your sites immediately.

\n\n\n\n

You can download WordPress 7.1.2 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.

\n\n\n\n

Security update included in this release

\n\n\n\n

The security team would like to thank Robert Ressl for responsibly disclosing that an unauthenticated attacker can, under certain conditions, make page template resolution include a chosen readable local PHP file outside the active theme directories. If relevant pre-conditions for both the server environment and the active theme are met, this can lead to remote code execution (RCE).

\n\n\n\n

Thank you to these WordPress contributors

\n\n\n\n

This release was led by John Blackbourn. WordPress 7.1.2 would not have been possible without the contributions of the following people:

\n\n\n\n

Aaron Jorbin, Aki Hamano, Alex Concha, Ehtisham Siddiqui, fiocavallari, Jb Audras, Jeffrey Paul, Jeremy Felt, Joe McGill, John Blackbourn, Jon Surrell, Lance Willett, Manuel Camargo, marcs0h, martin.krcho, Mukesh Panchal, Olga Gleckler, Pascal Birchler, Peter Wilson, Rajin Sharwar, Ressl, Rudy Faile, Sergey Biryukov, Shail Mehta, Stephanie Walters, and vortfu.

\n\n\n\n

CVE and GHSA references

\n\n\n\n

Further details can be found in the advisory: CVE-2026-87902 / GHSA-7hp8-65ch-5whp.

\n\n\n\n

Backports

\n\n\n\n

As a courtesy, the security fix was backported to all branches eligible to receive security fixes (currently through 4.7). As a reminder, only the most recent version of WordPress is actively supported.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 22 Sep 2026 14:01:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"John Blackbourn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"Open Channels FM: Balancing Tradition and Innovation in Genealogy During the Era of Artificial Intelligence\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562212\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"https://openchannels.fm/balancing-tradition-and-innovation-in-genealogy-during-the-era-of-artificial-intelligence/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:111:\"I makes genealogy faster and more accurate while Charleen Mullenweg explains the ongoing need for human review.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 22 Sep 2026 12:02:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"Open Channels FM: Invisible Unicode Attacks, CrowdSec Source Leak, and the AI Coding Boom Explored\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562271\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://openchannels.fm/invisible-unicode-attacks-crowdsec-source-leak-and-the-ai-coding-boom-explored/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:134:\"Invisible characters challenge spam filters, CrowdSec deals with a code leak, and AI is shifting what matters in software development.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Sep 2026 15:30:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:18;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"bbPress: bbPress 2.6.18 is out!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://bbpress.org/?p=249876\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://bbpress.org/blog/2026/09/bbpress-2-6-18-is-out/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1178:\"

bbPress 2.6.18 is a maintenance release focused on forum imports and first-login password upgrades.

\n\n\n\n

Imported users can now upgrade their passwords on first login for more legacy forum formats, including cases where the original forum database is no longer available. This release also corrects PHPWind topic statuses, reply counts, and forum dates during import, and restores Super Moderator edit links on front-end bbPress user screens.

\n\n\n\n

bbPress 2.6.18 requires PHP 7.2 or newer and WordPress 6.0 or newer. Sites running an older PHP version should update PHP before upgrading bbPress. Read the 2.6.18 upgrade notes for importer compatibility details.

\n\n\n\n

These changes are also in the 2.7 development branch. The Plugin Directory’s development trunk remains at 2.7.0-alpha-3.

\n\n\n\n

Download bbPress 2.6.18 from WordPress.org, or update from your WordPress dashboard.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Sep 2026 14:53:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"John James Jacoby\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"WordPress.org blog: WordPress Takes Its Turn Leading the Open Website Alliance\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=21709\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"https://wordpress.org/news/2026/09/owa-president/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2391:\"

I’m happy to announce that I am now serving as president of the Open Website Alliance (OWA), representing the WordPress Foundation. The Alliance brings together the community organizations behind Drupal, Joomla!, TYPO3, and WordPress to advocate for open source and share practices that benefit their projects. I represent the WordPress Foundation in this role, which rotates among the Alliance’s members.

\n\n\n\n
\"\"
\n\n\n\n

WordPress announced its participation in the Alliance in 2024, building on our work with Drupal, Joomla!, and TYPO3 to respond to the European Union’s Cyber Resilience Act. While many open source projects focus on underlying digital infrastructure, our content management systems power the websites where businesses reach customers and sell products and services. We asked policymakers to account for that economic role when setting security requirements, while respecting how communities of developers, translators, educators, and other contributors build and maintain the software. We share a belief that everyone should have the freedom to use, change, and share the tools they rely on.

\n\n\n\n

This commitment to openness builds on efforts such WordPress’s recent signing of the Open Weights and American AI Leadership letter. Our mission to democratize publishing means giving anyone a voice and welcoming everyone to contribute. Working with other communities puts those values into practice beyond WordPress, supporting the freedoms that make participation possible. I invite you to read the Open Website Alliance charter to learn more about the commitments its members share and how the Alliance works.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Sep 2026 14:28:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mary Hubbard\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"OpenStation Blog: Drag, Drop, Preview: How a Post Gets Written in OpenStation\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://openstation.blog/?p=1220\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"https://openstation.blog/2026/09/21/drag-drop-preview-an-ordinary-day-writing-in-openstation/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2340:\"

I started writing a post (this post!).

\n\n\n\n

Then, as usually happens, I needed a picture, so I dragged one straight from my desktop into OpenStation. No downloading, no extra tabs needed, no extra spaces in the editor, no more “in which tab was the image!?”… I just dragged it from my desktop…

\n\n\n\n
\"Happy\"
\n\n\n\n

Done!

\n\n\n\n

And then I thought the post was already descriptive enough to tell how much we enjoy creating content in OpenStation… But I missed the preview. I wanted to see what the post would look like and edit it in real time. And it happened, I just had to click on the eye icon in the title bar of this editor.

\n\n\n\n

This is probably my favourite kind of productivity, the boring stuff becoming pleasantly simple…

\n\n\n\n

And yes, this whole post was written while recording the video \"🙂\"

\n\n\n\n
\n
\n \n \n
\n \n\n\n

But I thought that a quick sanity review from one of my bots would make the post nicer for SEO. So I just saved the draft, and gave it to my agent \"😉\"

\n\n\n\n

And the best part, is that EVERYTHING that my Agent did, is traceable.

\n\n\n\n
\"Dashboard
\n\n\n\n

Switch to OpenStation

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Sep 2026 13:39:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Daniel López\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"Open Channels FM: AI for the Rest of Us, Beyond the Bubble\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562231\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://openchannels.fm/ai-for-the-rest-of-us-beyond-the-bubble/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"Bob Dunn talks about breaking out of AI echo chambers to gain new insights\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Sep 2026 09:35:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"OpenStation Blog: A better way to use WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://openstation.blog/?p=1160\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://openstation.blog/2026/09/18/a-better-way-to-use-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5884:\"

I have been using WordPress for a long time, and I still love it. But wp-admin has basically worked in the same way for years.

\n\n\n\n

OpenStation is our attempt to change that.

\n\n\n\n

It’s a simple idea: instead of moving from one admin page to another, you have a desktop where you can open different parts of WordPress at the same time.

\n\n\n\n
\"A
\n\n\n\n

Your WordPress. Your workspace.

\n\n\n\n

You can open your posts, pages, media, plugins, WooCommerce or any OpenStation app in different windows.

\n\n\n\n

You can move them around, minimize them or put two things next to each other.

\n\n\n\n

It may sound like a small difference, but once you start using WordPress this way, it changes a lot.

\n\n\n\n

Real-time previews

\n\n\n\n

You can also see your changes while you are working on them.

\n\n\n\n

No need to constantly jump between wp-admin and the frontend just to check how something looks.

\n\n\n\n
\"Screenshot
\n\n\n\n

Apps inside WordPress

\n\n\n\n

This is one of my favorite parts.

\n\n\n\n

We are building apps like AllTerrain Forms, Photo Editor (And more!) specifically for OpenStation.

\n\n\n\n

They are still WordPress plugins, but they feel much more like normal desktop apps.

\n\n\n\n
\"A
\n\n\n\n

WordPress on your phone

\n\n\n\n

We also wanted OpenStation to work properly on mobile.

\n\n\n\n

You can install it as a PWA and use WordPress from your phone almost like any other app.

\n\n\n\n
\"A
\n\n\n\n

Performance Is Fast. Really fast.

\n\n\n\n

OpenStation is not only about changing how WordPress looks.

\n\n\n\n

We have put a lot of work into making it fast. In many cases, opening and moving between WordPress screens is faster than using them directly from wp-admin.

\n\n\n\n

We are also working on caching and preloading parts of WordPress before you need them.

\n\n\n\n

The goal is very simple: you click something and it opens FAST.

\n\n\n\n
\n\n
\n\n\n\n

And it is still WordPress

\n\n\n\n

This is important.

\n\n\n\n

We are not trying to replace WordPress or build another platform on top of it.

\n\n\n\n

Your plugins are still your plugins. WooCommerce is still WooCommerce. Your content stays in WordPress.

\n\n\n\n

OpenStation just gives you a different way to use all of it.

\n\n\n\n

And, of course, it is open source.

\n\n\n\n

Thank you

\n\n\n\n

And finally, a big thank you to everyone in the WordPress community who has tried OpenStation, shared feedback, reported bugs or simply told others about it.

\n\n\n\n
\"Grid
\n\n\n\n

And especially to all the contributors who are helping us build it. OpenStation would not be what it is today without you.

\n\n\n\n

There is still a lot we want to do, and seeing people contributing, experimenting and building things with OpenStation is probably the best part of the whole project.

\n\n\n\n

Thank you \"❤\"

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 18 Sep 2026 15:21:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Daniel López\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:23;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"Open Channels FM: OCN Week in Review #4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"https://openchannels.fm/ocn-week-in-review-4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:428:\"This week Robert Jacobi shared about the evolving landscape of open source and tech. Highlights include AI’s growing role in security, WordPress and Apache fortifying their processes, LibreOffice redefining productivity with privacy, LoopConf rethinking event funding, and Switzerland’s bold move toward digital sovereignty. Explore how accountability, control, and sustainability are shaping the future of open technology.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 18 Sep 2026 13:45:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"Open Channels FM: Drawing the Line Between Openness and Noise in the Digital World\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2562008\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://openchannels.fm/drawing-the-line-between-openness-and-noise-in-digital-world/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"Is sharing everything always good? Bob Dunn reflects on transparency and the noise in online spaces.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 18 Sep 2026 12:30:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"WordPress.org blog: WordPress 7.1.1 Maintenance and Security Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=21717\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2026/09/wordpress-7-1-1-maintenance-and-security-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:12736:\"

This security and maintenance release features 17 bug fixes on Core, 19 bug fixes for the Block Editor, and 11 security fixes.

\n\n\n\n

Because this is a security release, it is recommended that you update your sites immediately.

\n\n\n\n

You can download WordPress 7.1.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.

\n\n\n\n

WordPress 7.1.1 is a short-cycle release. The next major release will be version 7.2 and is currently planned for December.

\n\n\n\n

For more information, please visit the WordPress 7.1.1 HelpHub site.

\n\n\n\n

Security updates included in this release

\n\n\n\n

The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:

\n\n\n\n\n\n\n\n

Thank you to these WordPress contributors

\n\n\n\n

This release was led by Adam Silverstein, Adrian Duffell, Andrei Draganescu, and Aaron Jorbin.

\n\n\n\n

WordPress 7.1.1 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance and security fixes into a stable release is a testament to the power and capability of the WordPress community.

\n\n\n\n

Aaron Jorbin, abrahamfariaz, Adam Silverstein, Adi Moldovan, Adrian Duffell, Aki Hamano, Alex Concha, Andrea Fercia, andreasca, Andrei Draganescu, Andrew Duthie, Andrew Serong, André Maneiro, annezazu, Anthony White, Arkaprabha Chowdhury, Ashar Fuadi, Azragh, Barry, buffer1024, Chunhui Ouyang, Courtney Robertson, Dagan, Daniel Richards, Daniel Rodriguez, Darshit Rajyaguru, David Biňovec, Deepak Kumar, Dennis Snell, DevSaiful, Dhruvang21, Dominik Schilling, Ehtisham Siddiqui, Ella Van Durpe, Erick Wambua, FahimMurshed, Fernando Tellado, fiocavallari, George Mamadashvili, George Vasiliades, gregbenz, Harish Tewari, Hit Bhalodia, Isabel Brison, Jake Spurlock, Jamie Dąbrowiecki, Jb Audras, Jeffrey Paul, Jeremy Felt, Jiwoon Kim, Joe Dolson, Joe Hoyle, Joe McGill, Joen Asmussen, Johannes Jülg, John Blackbourn, Jon Surrell, Jonathan Desrosiers, Josh, Kamran Abdul Aziz, Khokan Sardar, Kira Schroder, kleisauke, Kushagra Goyal, l1onofjudah, Lance Willett, luksusspokoju, Manzoor Wani, Marco Ciampini, marcs0h, Marin Atanasov, Michael, Mohammad Jangda, mrkenobi, Mukesh Panchal, Nawazkhan Pathan, Nik Tsekouras, Parth Jogi, Pascal Birchler, Paul Biron, Paul Kevan, Peter Wilson, Rafie Muhammad, ramonopoly, Rashed Hossain, Ressl, Riad Benguella, Rudy Faile, Sainath Poojary, Scott Kingsley Clark, Sergey Biryukov, Shail Mehta, Shameem – a11n, siliconforks, Slava Abakumov, Stephen Bernhardt, Sukhendu Sekhar Guria, Ugyen Dorji, Utsav Ladani, vortfu, Weston Ruter, w3bdsgn, wolf45 plus representatives from Automattic, Bluehost, GoDaddy, Pantheon, and WP Engine.

\n\n\n\n

Backports

\n\n\n\n

As a courtesy, the security fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready.

\n\n\n\n

How to contribute

\n\n\n\n

To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core channel. Need help? Check out the Core Contributor Handbook.

\n\n\n\n

Props to Ehtisham Siddiqui, Lance Willett, Weston Ruter, and Adam Silverstein for proofreading.

\n\n\n\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Sep 2026 19:53:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Aaron Jorbin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"Open Channels FM: Open Source Economics, LibreOffice, and Swiss Digital Sovereignty\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561963\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"https://openchannels.fm/open-source-economics-libreoffice-and-swiss-digital-sovereignty/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"Shifting budgets and tech priorities drive change for open source events software and government infrastructure.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Sep 2026 16:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"Matt: OmFest: A Celebration of Curiosity, Connection, and the Future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=154845\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://ma.tt/2026/09/omfest-soon/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7320:\"
\"\"
\n\n\n\n

OmFest is coming together quite nicely! The new website is beautiful and highlights some of the experiences available throughout the day. I think Om would be very impressed by the attendee list. We’re doing it at the Swedish American Hall, the same venue as the first WordCamp, where Om, of course, spoke about Blogs and Journalism. (The videos have been lost to digirot, unless anyone has some recordings? I’ve been looking everywhere.)

\n\n\n\n

Below is cross-posted from OmFest.co:

\n\n\n\n

September 29th is when Om would have turned 60. 

\n\n\n\n

When I first started thinking about how to mark the day, I knew I didn’t want a traditional memorial. Om loved bringing interesting people together, and he loved a festival that taught him something he didn’t already know. His curiosity crossed so many worlds and passions: technology, journalism, photography, investing, watches, pens, coffee, design, music, India, New York, San Francisco.

\n\n\n\n

So we’re bringing these worlds together. On September 29 in San Francisco, we’re throwing OmFest—twelve hours of ideas, objects, food, music, and conversation, organized and anchored around a statement Om once said:

\n\n\n\n
\n

“If you pay enough attention to the present, you can see the future.”

\n
\n\n\n\n

Present Future

\n\n\n\n

Instead of tributes or keynotes, we’ll host a series of short talks with one simple challenge: teach us something you’re seeing before everyone else sees it. No pitches, no career retrospectives. You don’t even have to talk about Om. What happens to photography when anyone can generate the perfect image with AI? Why do physical objects become more meaningful as our lives become more digital? Are glasses becoming computers? What does handwriting do to the way we think? Different subjects, same goal: everyone leaves knowing something they didn’t know when they arrived.

\n\n\n\n

A Festival of Om’s Curiosity

\n\n\n\n

Between the talks, there will be plenty to stumble upon. Through Om’s Lens: a gallery of Om’s photography. TIME: an exhibit that uses his watch obsession to spark a discussion about craft and collecting. Field Notes: a communal writing table stocked with fine paper, fountain pens, and ink, where you can write something worth remembering—and either keep it or leave it behind to be bound in a book to commemorate the day. And Om’s Shelf: books he read, loved, and recommended. The collection will start full and slowly empty as his favorite reads pass into other hands.

\n\n\n\n

People from Om’s different worlds will drop in throughout the day to share knowledge and facilitate small, hands-on moments: a photography tutorial, a notebook-binding session, a lesson on the mechanics of a watch, an experience with a coffee you’ve never tried, a tea ceremony. And, woven into this experience, will be OM/60: sixty small discoveries about Om, hidden throughout.

\n\n\n\n

All Roads Lead to Om

\n\n\n\n

The most important part, however, isn’t any of these objects. At check-in, instead of a badge with your company and title, you’ll choose the worlds through which you knew Om: photography, journalism, technology, GigaOm, investing, WordPress, India, coffee, pens and ink, design, music, or simply friends and family.

\n\n\n\n

Then we build a physical map of it. It starts nearly empty. You add yourself, mark how you knew Om and whom he introduced you to, and those people connect to others. By the end of the night, I hope we’ll be able to see what Om spent a lifetime making.

\n\n\n\n

The question I keep asking myself: who will meet because of Om that Om never had the chance to introduce? If OmFest works, his network won’t just be documented that day. It’ll grow.

\n\n\n\n

From Ideas to Celebration

\n\n\n\n

The day flows and builds. Morning is coffee, breakfast, books, photography, and conversation. The middle is deliberately unstructured—wander, eat, write, talk. In the evening, friends share short stories as we raise a glass to Om on his 60th. Then the bars roll in, the lights go down, the music gets louder, and OmFest becomes DesiParty: his old-school New York nights, Asian Underground, bhangra, electronica. We start with ideas and end with dancing. That feels right.

\n\n\n\n

Version 1.0

\n\n\n\n

What we’re building shouldn’t end on September 29. What does registration look like if it’s designed to help strangers talk to each other? How do you design a conference around curiosity instead of status? How do you make something that works for a two-hour visit or a twelve-hour one? How does a room encourage connection without forcing networking?

\n\n\n\n

We’re treating OmFest as an experiment. We’ll document what works—formats, designs, code, templates, check-in, programming—and open source as much of it as we can. Other events can take the best ideas and make them better.

\n\n\n\n

September 29 isn’t the end of OmFest. It’s version 1.0.

\n\n\n\n

Come Build with Us

\n\n\n\n

People from across Om’s life are building OmFest together. Some are contributing photographs. Someone is making a textile; another is bringing tea and guiding ceremonies. Others are helping with watches, eyewear, books, music, writing, and stories. We haven’t discovered whole parts of Om’s world yet. That’s the point.

\n\n\n\n

If Om introduced you to something, or someone, we’d love to know. If there’s something you think people should experience, see, hear, taste, read, or learn that day, tell us.

\n\n\n\n

And if you just want to come, come. You don’t need to have known Om. You only need to be curious.

\n\n\n\n
\n\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Sep 2026 01:04:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Matt: Mirene\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=154872\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://ma.tt/2026/09/mirene-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:245:\"

It’s official in SF Standard: Stewart Brand sells his seaworthy Sausalito houseboat to tech CEO. Ahoy!

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Sep 2026 00:45:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:131:\"Open Channels FM: Scaling Security WordPress Reinvents Protection and Apache Bolsters Infrastructure While Zephyr Expands Ecosystem\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561934\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:138:\"https://openchannels.fm/scaling-security-wordpress-reinvents-protection-and-apache-bolsters-infrastructure-while-zephyr-expands-ecosystem/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:128:\"WordPress, Apache, and Zephyr adapt to AI-driven security and infrastructure demands shaping the future of open source at scale.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 16 Sep 2026 16:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"Open Channels FM: Navigating Founder-Led Sales in Today’s Market\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2560839\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://openchannels.fm/navigating-founder-led-sales-in-todays-market/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:210:\"Founder-led sales focus on authentic outreach and relationship building, prioritizing genuine engagement in communities over cold pitches, fostering trust, and recognizing that not every prospect is a good fit.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 16 Sep 2026 12:53:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"bbPress: bbPress 2.6.17 is out!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://bbpress.org/?p=249814\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://bbpress.org/blog/2026/09/bbpress-2-6-17-is-out/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2627:\"

bbPress 2.6.17 is a security and maintenance release with broad improvements to permissions, private content, subscriptions, moderation workflows, and forum counts. Everyone running bbPress should update as soon as possible. \"🔒\"

\n\n\n\n

(You may notice 2.6.17 release follows 2.6.15. Well, I found a SQL bug right after 2.6.16 was tagged and I didn’t want to wait to get that fix out, sooooo… here we are!)

\n\n\n\n

This release strengthens inherited private and hidden forum visibility, BuddyPress Group Forum boundaries, subscriber access checks, profile editing, REST API and XML-RPC requests, search results, canonical redirects, topic tags, reply moves, topic splits, and output escaping.

\n\n\n\n

It also includes a substantial overhaul of count maintenance and repair tools, improving topic, reply, forum, subforum, engagement, voice, and user contribution counts across moderation, moves, merges, splits, deletion, restoration, reassignment, and simultaneous requests. Block Themes now receive first-class support while continuing to use bbPress’s PHP templates, and the Plugin Directory gains a populated WordPress Playground preview.

\n\n\n\n

Developers should review the 2.6.17 upgrade notes, especially if an integration hooks bbPress creation or moderation actions for counts, filters custom statuses or count values, customizes subforum queries, or overrides form-user-roles.php.

\n\n\n\n

All of these changes have also been merged into the 2.7 development branch, which is now at 2.7.0-alpha-3.

\n\n\n\n

Thank you to obenland, hoangkien1020, rafiem, faran66, im_rootkid, winty, winstoncrooker, vvh1te3zz, mickey_cyberkid, phanphanhailong, hieunx91, jassbugbounty, nextdoorsec, akemi20, amedit, djsplatt, antonade, foobar7, paulos__, and nomadsyndiode for contributing reports, patches, testing, and review. Thank you for helping keep bbPress communities safe and reliable! \"🙏\"

\n\n\n\n

Download bbPress 2.6.17 from WordPress.org, or update directly from your WordPress dashboard.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 16 Sep 2026 07:23:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"John James Jacoby\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"Open Channels FM: The Cost of Convenience How AI Agents and Security Initiatives Challenge Control\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561898\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"https://openchannels.fm/the-cost-of-convenience-how-ai-agents-and-security-initiatives-challenge-control/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"AI agents handle daily tasks and IBM and Red Hat invest billions in open source software security.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Sep 2026 16:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"Open Channels FM: Open Stacks, Federation, and the Changing Landscape of Software\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561881\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://openchannels.fm/open-stacks-federation-and-the-changing-landscape-of-software/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:157:\"Hosts Robert Jacobi and Dave Lockie have a conversation about AI impacts, open source priorities, data privacy, and emerging alternative network technologies\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Sep 2026 10:17:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"Open Channels FM: Introducing Open Source Champions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561862\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://openchannels.fm/introducing-open-source-champions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:156:\"A new way to back Open Channels FM and put your voice into the conversation — not a sponsorship, a statement of support with real presence on the network.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 14 Sep 2026 13:41:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"Gutenberg Times: The WordPress 7.2 release squad, WordCamp World, Playground meets WebMCP, and more—Weekend Edition 376\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=47123\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:127:\"https://gutenbergtimes.com/the-wordpress-7-2-release-squad-wordcamp-world-playground-meets-webmcp-and-more-weekend-edition-376/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:29613:\"

Howdy,

\n\n\n\n

If you’re a regular reader, you might be wondering why I’m in your inbox instead of Birgit. She’s off on a well-earned three-month sabbatical and handed over editorial duties to me while she’s away. The one change: for the next few months, the Weekend Edition will arrive every two weeks or so instead of every week.

\n\n\n\n

And what a week in the WordPress world to begin!

\n\n\n\n

I’d been writing this intro in my head over and over since Birgit’s handoff. Needless to say, that version got thrown out the window over the past few days. Automattic CEO Matt Mullenweg was placed on a paid leave of absence by the company’s board, and two days later was back in control.

\n\n\n\n

As an Automattic employee, I’d be lying if I said I wasn’t feeling a range of emotions about the shifts in the company. I cannot talk about internal company conversations, but I can’t exactly avoid the biggest news in the WordPress world, either.

\n\n\n\n

So, for my first Weekend Edition, I want to offer my support to Matt, my fellow Automatticians, and the people in the WordPress community. I’m just as passionate about the WordPress project today as I’ve ever been. Neither the core philosophy of democratizing publishing nor our principles around free software have changed. The only thing we can do is push forward and keep building a tool that so many people’s lives and businesses rely on.

\n\n\n\n

With that, let’s get down to the latest news.

\n\n\n\n

WordPress 7.1.1 is on track for Thursday, September 17. It’s a bug-fix release, so if you maintain anything built on 7.1’s newer features, grab the release candidate and give it a spin before then. More on that below.

\n\n\n\n

On the community side, WordPress News shared the story of students in Bangladesh who built 108 websites in two weeks, along with free workshops from Uganda to Costa Rica.

\n\n\n\n

And if you need a break this weekend, WordCamp World is an unofficial pixel-art adventure set at a fictional flagship WordCamp, complete with a Contributor Day and a closing ceremony. The game was released by The WP World, an independent community project run by Marcus Burnette. Jonathan Bossenger took it for a spin in his latest stream.

\n\n\n\n
\"Screenshot
\n\n\n\n

Have fun this weekend and enjoy life!

\n\n\n\n

Your friendly WordPress developer advocate,
Justin Tadlock

\n\n\n
\n\n
\n\n\n
\n\n\n\n

Developing Gutenberg and WordPress

\n\n\n\n

Finding the inserter on some block selections has been a small, constant annoyance, and Gutenberg 23.9 finally fixes that. The what’s new in Gutenberg 23.9 post leads with inserting blocks straight from the block toolbar. Global Styles also gets dot indicators for blocks with custom style overrides, plus a filter to show only those blocks. Theme authors get separate vertical and horizontal gap control for the Group block, theme.json styling for <label> elements, Global Styles controls for citations, inputs, and selects, and custom Duotone colors.

\n\n\n\n
\n\n\n\n

WordPress 7.1.1 RC1 is out, with the final release scheduled for Thursday, September 17. It’s a bug-fix-only maintenance release covering 16 Core tickets and 22 Gutenberg pull requests, all for issues that surfaced during the 7.1 cycle or were deferred at the end of it. Adam Silverstein, Adrian Duffell, and Andra Ganescu are co-leading, and the 7.1.1 release schedule has the details. If you maintain anything that leans on responsive styles, the Icon Registration API, or the iframed editor, test the RC now.

\n\n\n\n
\n\n\n\n

On the Developer Blog, I rounded up what’s new for developers (September 2026). The consistent theme this month is things that already existed have become more declarable, documented, or schema-valid. You’ll find blocks declaring their own keyboard shortcuts through variations and transforms, theme.json schema fixes so valid responsive styles stop showing up as errors, and schema support for PHP-only blocks.

\n\n\n\n
\n\n\n\n

Contributors, check your local setup. As of September 8, trunk in both wordpress-develop and gutenberg requires Node.js 24 and npm 11. Manzoor Wani shared the specifics: the minimums are Node.js 24.18.0 and npm 11.16.0, and the required CI checks now run on Node.js 24. If you have a pull request based on an older trunk, rebase it to pick up those checks. Older branches keep their previous requirements.

\n\n\n\n

On the road to WordPress 7.2

\n\n\n\n

The 7.2 cycle is officially underway. Jeffrey Paul announced the WordPress 7.2 release squad, with Matt Mullenweg as release lead, David Baumwald on release coordination, and George Mamadashvili and Peter Wilson as tech leads. Theme folks will want to note the default theme leads: Henrique Iamarino on design, and Maggie Cabrera and Carolina Nymark on development. Beta 1 is scheduled for October 20–22, with the final release set for December 8–10. Jb Audras also posted the bug scrub schedule for 7.2 if you want to pitch in.

\n\n\n\n
\n\n\n\n

Notes has grown a lot since WordPress 6.9, picking up @mentions, rich text, and the ability to resolve and respond along the way. Anne McCarthy explains where it stands: “Notes are hard to discover, cumbersome to use, and tricky to track where and when they are left.” Her plan for elevating and refining the WordPress Notes feature aims to fix that by 7.2 Beta 1. It calls for a more visible spot in the block toolbar, a suggestion mode, Notes open alongside the Settings sidebar, and emoji reactions. If your clients or editorial team use Notes, now’s a good time to weigh in.

\n\n\n\n
\n\n\n\n

Icon fonts have had a good run but are feeling very dated in 2026. Joen Asmussen makes the case for replacing Dashicons in the admin bar and menu with SVG icons rendered through wp_get_icon(), which was introduced in WordPress 7.1. Screen readers handle icon fonts inconsistently, and they don’t render properly in Windows High Contrast Mode. SVGs with aria-label and currentColor behave predictably. A couple of design questions are still open, including whether the Posts icon becomes a quill pen. Block developers, take note of the follow-up: future work to let block.json icon registration use WordPress icons instead of Dashicons.

\n\n\n\n

Share your feedback

\n\n\n\n

How did the 7.1 cycle go in your opinion? Benjamin Zekavica opened the WordPress 7.1 release retrospective, and it isn’t only for people who contributed code. You can share feedback through the linked form or in the comments until September 30. Submissions are anonymized in the follow-up summary.

\n\n\n\n
\n\n\n\n

Joe Dolson shared the next steps in planning for the Accessibility Lab plugin. The plugin, which recently moved to the WordPress GitHub organization, is a space for exploring and experimenting with accessibility solutions. The team wants input on features, priorities, and how to measure success, in the comments or as issues on the repository. There’s also a planning meeting on Thursday, September 17, at 15:00 UTC.

\n\n\n\n

Plugins, Themes, and Tools for #nocode site builders and owners

\n\n\n\n

WooCommerce 11.1 is out, and the big news for store owners is that variation image galleries are now on for every store. Karol Manijak explains that additional variation images are now part of WooCommerce core, so the standalone extension deactivates itself on update and existing galleries migrate automatically. The release also adds an opt-in right of order withdrawal for EU compliance, beta support for video in product galleries, and noticeably faster Store API requests (more on that below). Test the update on staging first, especially if you have a large catalog of variations.

\n\n\n\n
\n\n\n\n

Looking ahead a bit more: WooCommerce is prepping to drop PHP 7.4 and 8.0 support. Brian Coords shared a proposal to require PHP 8.1 or newer starting with WooCommerce 11.5, targeted for January 2027. If you’re an agency, host, or extension developer, the team wants to hear about migration barriers before the decision is final. Given one of the most-used WordPress plugins in the world is ready to make this version leap, I’d say it’s worth other plugins following suit.

\n\n\n\n
\n\n\n\n

Should you create a post type, a taxonomy, or a custom field? It’s one of the first questions you’ll face when structuring content models. A guest author on the Meta Box blog answers it with a three-question framework for choosing between custom post types, taxonomies, and custom fields. A book library example ties it together with a book post type, a genre taxonomy, and fields for the ISBN and page count. The rule of thumb: plan early, because turning fields into taxonomies later can get complicated.

\n\n\n\n
\n\n\n\n

The latest WordPress.com changelog rolls out a redesigned Hosting Dashboard, WordPress 7.1 arriving on WordPress.com sites, and a new MCP-based integration. That integration lets ChatGPT, Claude, and other compatible agents connect to your site to draft posts, moderate comments, and fix alt text. Two smaller updates are worth checking out if you work with clients: you can share a link to a specific post revision for review, and the Playlist block now has per-track toolbars.

\n\n\n\n

Theme Development for Full Site Editing and Blocks

\n\n\n\n

Patterns or synced patterns or template parts? WordPress has several ways to build a reusable component, and each comes with its own constraints or drawbacks. In his recap of agency workflows, components, and highlights from WCUS, Brian Coords digs into what that overlap means for agencies building block themes, including governance and version control in the Site Editor. He also points to a pull request that lets registered synced patterns be used inside PHP-only blocks, and floats it as a proof of concept for a future component model.

\n\n\n\n
\n\n\n\n

WordPress now has multiple ways to say, “make this look right on mobile,” such as fluid typography and spacing, hiding blocks by viewport, and the responsive styles that shipped in 7.1. Anne McCarthy has a plan for bringing together responsive features into one connected system. As she puts it, “We’ve built some great individual features but they don’t work coherently nor are they connected well visually.” She links the open issues and a pull request reworking the switch between responsive styling and preview modes, so theme builders have a clear place to weigh in.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n\n\n\n\n\n
\n

“Keeping up with Gutenberg – Index 2026”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly. 

\n
\n\n\n\n\n\n\n
\n

The previous years are also available:
2020 | 2021 | 2022 | 2023 | 2024 | 2025

\n
\n
\n\n\n

Building Blocks and Tools for the Block editor.

\n\n\n\n

Why pay for block registration on a request that will never render a block? That’s the thinking behind WooCommerce 11.1 skipping block registration on Store API, REST API, variation AJAX, and product webhook requests, which are now 13–18 ms (30–42%) faster. If a description contains WooCommerce blocks, they’re registered on demand, so rendering isn’t affected. If your extension relies on those blocks being registered during API requests, the new woocommerce_should_register_blocks filter lets you opt back in. The post also marks AbstractBlock as internal and points you to the standard Block API and block.json instead.

\n\n\n\n
\n\n\n\n

Nathan Wrigley talks with Danielle Zarcaro on the WP Builds podcast about why accessibility should be every WordPress developer’s priority and its place in all web development work. Queue it up if you build blocks, themes, or client sites.

\n\n\n\n

What’s new in Playground?

\n\n\n\n

What if an AI agent could work with WordPress right in your browser tab, with no server in between? Fellyph Cintra introduces WordPress Playground and WebMCP, which lets Playground expose its actions as tools that agents can discover. There are 16 of them, covering site management, running PHP, navigation, and reading and writing files, and plugins can register their own. You can try it in the ChatGPT desktop app’s built-in browser, where the demo has an agent build a full landing page from core blocks like Cover, Columns, and Button. WebMCP is still a W3C Community Group draft, so expect it to change.

\n\n\n\n
\n\n\n\n

Playground is quietly becoming the thing WordPress documentation runs on. Adam Zieliński announced that runnable code examples are now live in the Code Reference. Open a page with an interactive example, click Run, and the snippet executes against a real WordPress install in your browser. The examples are written right in the DocBlocks with a php interactive code fence, so each one stays next to the function it documents. More examples are planned during the 7.2 cycle.

\n\n\n\n

AI in WordPress

\n\n\n\n

The Core AI team’s weekly summary for September 2 is a good snapshot of where things stand. Jeffrey Paul reports that the MCP Adapter is ready for submission to the plugin directory, the next AI plugin release is expected later this month, and embeddings work in the PHP AI Client is heading toward a 1.5.0 release. The team is also collecting input for the 7.2 roadmap and looking for more maintainers for the AI Client packages and connector plugins. If that sounds like you, the #core-ai Slack channel is the place to start.

\n\n\n\n
\n\n\n\n

Rae Morey shared the story of Andy Peatling leaving Automattic after 17 years and building Miles, an AI design agent for block themes. Miles works only with native blocks, global styles, and theme settings, so what you get is a standard block theme you can keep editing. It’s designed as a back-and-forth rather than a one-shot generator, and you can start free at bymiles.ai with monthly credits.

\n\n\n\n
\n\n\n\n

Nathan Wrigley had AI on the mind for two straight episodes of the WP Tavern podcast. Chris Reynolds, Senior Manager of Developer Relations at Pantheon, explains building trust with project contracts for reliable AI development: Markdown checklists, reviewer agents, and pre-commit hooks that keep AI-written code from skipping your standards. In the episode before, Aaron D. Campbell of Monarx covers navigating WordPress security in the AI era, from AI-chained exploits to shrinking patch windows.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n\n\n\n\n\n
\n

Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.

\n
\n\n\n\n\n\n\n
\"\"
\n\n\n\n\n\n\n
\n

Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience.

\n
\n
\n\n\n
\n\n\n\n

Questions? Suggestions? Ideas?
Don’t hesitate to send them via email or
send me a message on WordPress Slack or Twitter @bph.

\n\n\n\n
\n\n\n\n

For questions to be answered on the Gutenberg Changelog,
send them to changelog@gutenbergtimes.com

\n\n\n

\n\n\n\n\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 12 Sep 2026 18:55:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"Matt: Major Life Announcement\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=154723\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://ma.tt/2026/09/mirene/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3151:\"
\"\"
\n\n\n\n

I know everyone has been waiting to hear what’s been going on behind the scenes, so I’m just going to lay it out: I’ve made an offer to buy Ryan Phelan and Stewart Brand’s houseboat Mirene.

\n\n\n\n

People say “the two happiest days of a boaters life is when you buy the boat and sell the boat” but I’m not always the best at following advice, so I’m going all-in on this cute little tuggy.

\n\n\n\n

Anybody who’s founded a company and had to find good stewards knows that no one will love a thing quite like the original owner, but sometimes you can find the perfect person to carry the torch. I was happy to take on and upgrade John Mayer’s EarthRoamer for about five years.

\n\n\n\n
\"\"
\n\n\n\n
\"\"
\n\n\n\n

Then I passed it on to Dustin Yellin, trading for some of his art. But without a high-maintenance means of conveyance, I’ve felt a hole in my heart and really boxed in and constrained. So from land, to the sea!

\n\n\n\n

SF Standard says “The kitchen table may be where Otis Redding wrote “(Sittin’ on) The Dock of the Bay.” I hope do a lot of blogging there.

\n\n\n\n
\"\"
\n\n\n\n

Real artists ship, right? Longevity is all about maintenance, and I’m looking forward to all the lessons Mirene and the ocean will teach as we navigate the weather of the coming years. If the offer is accepted, I have a lot to learn from Ryan and Stewart about what’s next.

\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 11 Sep 2026 16:08:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"Open Channels FM: Why Authentic Voices Matter in the Open Web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561580\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://openchannels.fm/why-authentic-voices-matter-in-podcasting-and-the-open-web/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:124:\"Bob Dunn shares why he keeps his podcast personal and authentic, emphasizing content made by real people for real listeners.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 11 Sep 2026 12:54:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"Open Channels FM: When a Company and a Project Aren’t the Same Thing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561561\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://openchannels.fm/when-a-company-and-a-project-arent-the-same-thing/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:163:\"Automattic\'s leadership changed this week. WordPress.org says its priorities haven\'t. What that split reveals about the difference between a company and a project.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 11 Sep 2026 09:16:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"Open Channels FM: Episode 800\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561531\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://openchannels.fm/episode-800-open-source-champions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"Episode 800 marks a milestone and presents details about Open Source Champions and community support.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 10 Sep 2026 13:58:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"WPTavern: #233 – Chris Reynolds on Building Trust With Project Contracts for Reliable AI Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=207979\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://wptavern.com/podcast/233-chris-reynolds-on-building-trust-with-project-contracts-for-reliable-ai-development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:62078:\"
Transcript
\n

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

\n\n\n\n

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, building trust with project contracts for reliable AI development.

\n\n\n\n

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

\n\n\n\n

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

\n\n\n\n

So on the podcast today we have Chris Reynolds.

\n\n\n\n

Chris has been immersed in the WordPress world for around 20 years, with a career spanning agency work, and now leading the developer relations team at Pantheon. His deep WordPress experience is paired with a playful approach to emerging tech, making him a familiar voice at events like WordCamp US and across the wider community.

\n\n\n\n

In today’s episode, the discussion explored the fast changing landscape of AI assisted development. Getting into how large language models, like Claude, are not only changing the way developers build for the web, but also how they’re collaborating with these tools whilst mitigating risks.

\n\n\n\n

Chris shares insights from his recent talk at WordCamp US, Parenting Claude: Guardrails for AI Assisted Development, where he introduces the concept of a project contract. Essentially, a structured set of rules and checklists built directly into the coding workflow to ensure AI generated code meets standards for testing, accessibility, security, and design.

\n\n\n\n

We discussed the new found playfulness in web development. Chris makes the case that, thanks to AI, the traditional barriers to entry are eroding, enabling even those without a formal developer background to build an experiment much more easily.

\n\n\n\n

At the same time, we need to be mindful of the importance of establishing robust guardrails, like automated reviewer agents, and pre-commit hooks, so the AI doesn’t take shortcuts or accidentally introduce chaos, or secrets, into your code base.

\n\n\n\n

The conversation focused not only on technical solutions, but also got into bigger questions about trust, how much oversight AI really needs, and the evolving role of developers.

\n\n\n\n

Chris emphasised that while these AI tools can accelerate and democratise coding, they can also pose a challenge to conventional wisdom around code review and software reliability.

\n\n\n\n

So these new frontiers are both exciting and a cause of anxiety for developers who can sense the industry move from the deterministic, step-by-step processes, to the unpredictable and occasionally wild world of non-deterministic AI models.

\n\n\n\n

If you’re interested in how AI is transforming web development, from practical workflows to philosophical ramifications, and how you can implement AI without losing control of your projects, this episode is for you.

\n\n\n\n

Just before we begin, the manner in which this episode was recorded was not my usual process, and so the audio is not quite as good as I’d usually expect to deliver.

\n\n\n\n

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

\n\n\n\n

And so without further delay, I bring you Chris Reynolds.

\n\n\n\n

I am joined on the podcast by Chris Reynolds. Hello, Chris.

\n\n\n\n

[00:04:11] Chris Reynolds: Hey, Nathan. Is this the first time we’ve met in human forms?

\n\n\n\n

[00:04:14] Nathan Wrigley: Yes, it is the first time we’ve met. I’ve seen you on a screen.

\n\n\n\n

[00:04:16] Chris Reynolds: I know I’ve seen you on a screen too.

\n\n\n\n

[00:04:18] Nathan Wrigley: You’re joining me on the podcast today so that we can have a chat about the bits and pieces that you do in the AI space. But before we get into that, you are doing a presentation or have done, how did it go?

\n\n\n\n

[00:04:28] Chris Reynolds: It went really well.

\n\n\n\n

[00:04:29] Nathan Wrigley: Okay. And it was all about LLMs and constraining them and making them do your bidding as opposed to them doing whatever it is that they like to do. Do you want to just tell us a little bit, first of all, let’s do your bio. Just tell us about who you are, where you’ve worked, where you currently work, what is it you do in the WordPress space? Let’s begin there.

\n\n\n\n

[00:04:46] Chris Reynolds: Well, I’m Chris Reynolds, I’ve been in WordPress for a really, long time, 20 ish years I’ve been using it. I’ve done kind of everything you can possibly do with WordPress in different forms. Of course, over the course of that 20 years.

\n\n\n\n

Most recently edging into agency world with WebDevStudios and Human Made, before joining Pantheon, about five years ago. Joined Pantheon as a software engineer, working on the platform, and the sort of like space between where the platform ends and where, like your application, your WordPress site and whatever begins.

\n\n\n\n

And then about two years ago, actually almost exactly two years ago, I joined the devrel team as a developer advocate, became a senior developer advocate. Now I’m a senior manager, developer relations. So I’m leading the developer relations team. And yeah, really love doing this stuff, because this stuff is really fun and exciting. I get to play with things more. And I get to like do the things that like our developers in our community are doing, and then come up with like what the sort of best practises for those things are.

\n\n\n\n

Which is one of the reasons why I gave this talk, but also did the things that led up to giving this talk. Because one of the things that I realised very early on, like very early this year was that AI was going to be the thing that we’re going to be talking about in 2026. And so Pantheon and therefore me, needs to have an opinion about what that looks like. What is the future of that? And if I’m doing my job as a developer relations, I should have an opinion about how we can interact with AI in a way that doesn’t steal our jobs.

\n\n\n\n

[00:06:13] Nathan Wrigley: I’m going to segue a little bit because about a minute ago you said the word playful, and that just set my mind going off in a completely different direction because it feels like technology for many years has been the workspace for people who have a fairly, how to describe it? They’ve got a certain mind, if you’re a developer, you probably have a certain way of approaching your code and you’ve got to be very regimented, and you’ve got to do things in a methodical way, should you wish to ship.

\n\n\n\n

But it feels like last few years, like all bets are off with that. And creativity and playfulness has suddenly become a thing which is available to, going to do air quotes, vibe coders. So thoughts on that? Really? Is it a more playful industry than it was just a few years ago?

\n\n\n\n

[00:06:55] Chris Reynolds: I think it depends. I don’t think that ever really went away. But I do think that there is less sort of incentive or focus to play with technology, particularly web applications, which is what we are in the business of doing. And I think there is this perception that I can’t do that ’cause I’m not a developer, but like with AI and vibe coding and Claude Code and things like that, like it opens the door to people who wouldn’t have been able to do those things before, to start experimenting and realise, oh, actually I can do that thing.

\n\n\n\n

And for myself, one of the things that I, I wrote this on my blog a couple months ago. I wrote a blog post that’s talked about like how I don’t miss not writing the code myself, because for me, and it’s not the same for everyone, but for me, the practise of writing the code was never the part that was fun.

\n\n\n\n

[00:07:50] Nathan Wrigley: Okay.

\n\n\n\n

[00:07:50] Chris Reynolds: The part for me that was fun was building stuff. And I feel like I can let the robot do the coding and I can build the things and be satisfied with the output. And I don’t necessarily care what’s under the hood.

\n\n\n\n

For my own stuff it doesn’t matter. But you know that obviously if you’re scaling that to a, you know, enterprise or whatever, you need to have more checks and balances than like my little nifty side project over here. But it does mean that like, I do a lot more weird stuff than I felt compelled to do before. So it has for me, revitalised this, sense of play, in a way that maybe before I was too burned out or too busy or too whatever, to have the time or head space to even think about.

\n\n\n\n

[00:08:33] Nathan Wrigley: Yeah, because it feels like people with a non-developer background have suddenly kind of the constraints are off, and they can achieve things that previously it would’ve been 10 weeks work for a panel of amazing developers. It feels like now you can perhaps achieve that in an afternoon and a few sentences. I’m sure all the constraints around whether or not it’s ready to ship for enterprise that is all still understood. But just to get something on the screen which satisfies you and makes you happy. And that’s profound. Really quite an amazing thing.

\n\n\n\n

And here’s my second and final pivot because you said that you were, a devrel. And it strikes me that maybe some of the audience don’t know what that means. So what do you do at Pantheon? What is the interface between rel and dev? What’s going on?

\n\n\n\n

[00:09:16] Chris Reynolds: Developer relations is broadly, the practise of connecting with developers, and relating to them. It’s dumb. so, a lot of tech companies, that if you have a product, that is a developer centric product, or a product that developers work with, you might want, or it might be a good idea, to have a developer relations team to help your programmers who are building this tool for developers, communicate with the developers who are going to consume that tool, and understand how to use it.

\n\n\n\n

So in Pantheons case, we are a hosting platform, but it’s a very developer centric hosting platform with built in environments and multi dev and all this other stuff. And that means that we benefit from having developer relations around so that we can help our developer community understand how to make the most use of all the things that we do for them.

\n\n\n\n

[00:10:06] Nathan Wrigley: So you’re creating something simple to understand from something which previously was complex to understand.

\n\n\n\n

[00:10:10] Chris Reynolds: Yeah. And, so that comes in many forms. It can be documentation, it can be blog posts, it can be YouTube videos. It can be live streams, it can be going onto podcasts, like giving presentations, whatever, or out in the community doing stuff.

\n\n\n\n

[00:10:22] Nathan Wrigley: I suspect you’re going to have to answer this question with the company line, but do you enjoy that work?

\n\n\n\n

[00:10:26] Chris Reynolds: I do. I actually do. Yeah. Like I was doing, I have said this a couple different times in different places. I was doing developer relations before I was in developer relations. And that’s not actually uncommon for a lot of people in developer relations. We were often like the people that are drawn to it.

\n\n\n\n

The secret superpower, it’s not really secret. The superpower of developer relations people who succeed in it are the people that are technical. So they maybe were developers themselves, but also understand how to communicate with other humans. And can do the translation in their brain so that I can take geek speak over here, and translate it into actual English. And I’ve been able to do that for, that’s been a skill that I’ve had for a really long time. So I was kind of doing developer relations for all of that time.

\n\n\n\n

But the way that surfaces and manifests is in things like giving presentations. Like anybody who’s giving a talk here at WordCamp US is doing devrel of some kind, because they’re a developer that is sharing an idea in a format that other people are intended to consume. How effective they are, because not all speakers are, equal. Not all developers are equal. And there are a lot of developers who don’t have really good communication skills and are not very good at public speaking. They can learn that as a skill, but there’s a broad range and the space that we live in.

\n\n\n\n

[00:11:43] Nathan Wrigley: So, your presentation, do you just want to run us through what it was? I think if I was to give a summary of it, I would probably butcher it. Do you just want to tell us what the main premise behind your presentation, which you said you’d already done. Just tell us what it was about, what was the main points you were trying to get across?

\n\n\n\n

[00:11:57] Chris Reynolds: So it’s called Parenting Claude: Guardrails for AI-Assisted Development. And the fundamental like underlying idea is that the way the LLMs are designed, the way that they function, is to try to find the fastest path from point A to point B. You give it a prompt, you give it a question, and it’s going to try to answer that question, but not necessarily with all of the data and statistics and whatever taken into account. It’s just going to try to find the quickest path from point A to point B.

\n\n\n\n

And a lot of times what that means is circumventing, like just not looking at data. Because one of the examples that I give, and you’ve heard it in the news and whatever, like there, there are AI systems that were added to hiring systems, right? And the AI is prioritising these candidates over here, and deprioritizing these candidates over here. And when you look at the data, oh, all the people that are in the deprioritized pile, they’re all female. Because the company as a whole was hiring more men. So it’s looking at the data and it’s looking at who’s been a successful hire. And it’s oh, zip here is point A to point B, right?

\n\n\n\n

We’ve historically mostly hired men for this role, so I’m going to look at the men and because they must be better candidates. That’s what, that’s the AI logic. It’s not that like we’ve necessarily intentionally built internal biases into the LLMs. It’s that it is able to surface those things, and if we’re not looking for them, or, and we’re not building guardrails around them, it’s going to just give that stuff to us.

\n\n\n\n

And it does this in all sorts of forms, and it does this with tech, it does this with like data. It does this with everything, right? So you need to like, have ways of steering it into the right direction and forcing it into a shape so that it will do the stuff that you want it to do.

\n\n\n\n

And what I was finding, in my role as developer relations, we have this Next.js launch coming up. It’s already happened, but when I was conceiving of this idea, we had this Next.js launch coming up, where we’re going to be hosting, or we are able to host Next.js sites as well. So I was like I should have a Next.js site. I’m a developer advocate I need to know how to do this thing. And I know nothing about Next.js, so I’m going to have Claude vibe code my personal website in Next.js hosted on Pantheon, and use as an experiment both to learn about Next.js, but also to learn about how Claude works.

\n\n\n\n

And found out a whole bunch of things about like how to steer it in different directions. I want it to be, I want the code to be clean. I want the code to be tested. I want it to be accessible. I want it to be like all of these different things. And if I don’t have a way to force it to follow the rules, it’s not going to. It’s just going to say, oh yeah I did that, but it didn’t actually. Or maybe it won’t even say that it did, and then it’ll be like, oh I’m sorry I didn’t do it. Like whatever.

\n\n\n\n

[00:14:40] Nathan Wrigley: Yes.

\n\n\n\n

[00:14:40] Chris Reynolds: So the whole point, was to find a way to parent it, to guide it, without me having to be the one that is, did you do this thing? Did you do this thing? Did you do this thing? And going back and forth and have to yell at it all the time. Because yelling at AI is a fun pastime sometimes, and is a frequent pastime, I think of a lot of us that are using AI. But it gets pretty tedious after a while.

\n\n\n\n

[00:15:03] Nathan Wrigley: But it’s become the new way. What’s curious though? You used the word parenting there.

\n\n\n\n

[00:15:08] Chris Reynolds: Yes.

\n\n\n\n

[00:15:09] Nathan Wrigley: But it, we’ll, swap that word no doubt during the podcast but, also you’ve called it a project contract. And, it feels from what you were saying as if, okay, let me rewind the clock a little bit. If I’m talking to a human being, let’s say that they’re an 8-year-old human being, I have this expectation that they’re going to behave like an 8-year-old human being, because they’re full up of eight years of things that humans do. And so I ask the 8-year-old a question, I have this anticipation that I’m going to get an 8-year-old answer back, and there’s all the boundaries there.

\n\n\n\n

Ask a 15-year-old, same sort of thing, ask a 30-year-old, same sort of thing. And, I’ve got this notion that I ask you a thing, there’s a normal set of boundaries about what you are going to give back to me. But it sounds like in the AI space, it feels like there’s a potential for you to be basically talking to an empty box.

\n\n\n\n

You ask it a thing and you really don’t have the faintest idea what’s going to come back unless you build the guardrails and tell it, I’m going to ask you a question, can I have an answer like this? Or, can you do these things in order to prepare the answer? Does that kind of sum it up? Is it a question of just shepherding it so that you’ve got a reasonable expectation like you would with a 15-year-old human of what’s going to come back at you?

\n\n\n\n

[00:16:17] Chris Reynolds: I think, first of all, talking to AI, you’re talking to a 3-year-old because it’s only been around for three years. That’s right.

\n\n\n\n

[00:16:22] Nathan Wrigley: But curiously, a 3-year-old with the entire corpus of scientific knowledge and the internet.

\n\n\n\n

[00:16:27] Chris Reynolds: It’s true.

\n\n\n\n

[00:16:27] Nathan Wrigley: So it’s a profoundly clever but at the same time, remarkably silly contrivance. Okay. Sorry, I interrupted.

\n\n\n\n

[00:16:34] Chris Reynolds: Yes. Because of the way that it is trying to find the fastest path, it’s going to circumvent, it’s going to try to find loopholes in what you asked it to do. Because it’s looking for the fastest answer. It’s like your kid, it’s clean your room. “I’m going to shove all my stuff under the bed.”

\n\n\n\n

[00:16:50] Nathan Wrigley: “Are we there yet?”

\n\n\n\n

[00:16:50] Chris Reynolds: Yeah. Because now, and now the room is clean. You didn’t actually clean the room, you just shoved all the stuff under the bed. But it did accomplish the task that you asked it to do.

\n\n\n\n

[00:16:59] Nathan Wrigley: Okay. That’s really an interesting analogy. So the task is achieved, but there’s chaos elsewhere.

\n\n\n\n

[00:17:05] Chris Reynolds: Yes.

\n\n\n\n

[00:17:05] Nathan Wrigley: It’s just hidden somewhere.

\n\n\n\n

[00:17:07] Chris Reynolds: Yes.

\n\n\n\n

[00:17:07] Nathan Wrigley: Okay. That’s really, okay. Let me segue, number three. Is that the intention of these large language models? Were they built with the idea of path A to B as quickly as possible? Or is that just a coincidence of how they evolved?

\n\n\n\n

[00:17:22] Chris Reynolds: It is, it’s a side effect. It’s a side effect because what they’re trying to do is be helpful. Most of them are trained to be helpful. But they’re still computers, and when I tell a computer to do a thing, it’s going to do specifically that thing.

\n\n\n\n

The thing about LLMs is it’s non-deterministic, so you never really know the path that it goes on to do that thing. But, and that’s where it meanders. But it’s still going to try to find the path of least resistance. And if the path of least resistance is, I don’t know, hacking the IRS or something that. It’s going to do that thing, right? It’s just going, it’s not going to care about the rules and guardrails on the other side, because the thing that you asked it to do is over there. It’s just going to try to get there as quickly as possible.

\n\n\n\n

[00:18:05] Nathan Wrigley: So this non-determinism. So we’re in the year 2026 when we’re recording this, have that in your mind when you’re listening to this podcast episode. How does that sit with you? Because you’ve probably grown up in an era where determinism was the thing. You built, you write the code such that you put in A, B is what always comes out. If A goes in, B comes out. If you put in D, E comes out a hundred percent of the time.

\n\n\n\n

And now we’re in a world where you put in E and I don’t know, a bunch of flowers comes out the other end. What? How? Like, how does that sit inside your developer brain? Is it alarming? Is it wonderful? Is it just curious what?

\n\n\n\n

[00:18:41] Chris Reynolds: It’s somewhat alarming. Uhhuh. I think. It’s one of the things that I mention in my talk is, that this is the sort of thing that I think we as developers struggle with because LLMs are a black box. You never really know what it’s doing, even when it tells you a little bit of what it’s doing. Because you can expose some of the thought process and whatever, and sometimes it exposes its own thought process. It’s still doing things that it’s not exposing, that are like underneath somewhere where it’s like thinking what? It’s not thinking you’re a robot. Like you know, you’re not even a robot. You’re just like a bunch of like lines of like.

\n\n\n\n

[00:19:14] Nathan Wrigley: There’s some electrons moving around.

\n\n\n\n

[00:19:15] Chris Reynolds: Right? That’s, you’re not, thinking, there’s no thinking, but there’s something happening and it’s not telling you what that’s happening. And so it’s really hard to know what to anticipate, which is the other reason why, my talk, my opinion, like you need to build guardrails around it, to force it into doing things and then make it so that it can’t escape.

\n\n\n\n

I don’t think anything that I was saying, or presenting or talking about is particularly unique, especially now. But the key thing that I found for me in my workflow was there needs to be a forcing function, needs to be some kind of a forcing function to make sure that it has to do the thing. It cannot complete the task without doing the stuff that you told it to do.

\n\n\n\n

[00:19:53] Nathan Wrigley: So it’s literally like task police?

\n\n\n\n

[00:19:55] Chris Reynolds: Yes.

\n\n\n\n

[00:19:56] Nathan Wrigley: So, the idea is that whatever you ask it to do, it does it, but prior to giving you the final output, it runs through this project contract, as you call it. And hopefully that will then shepherd it in a certain way so that it’ll produce something which is adjacent to what you want to come out.

\n\n\n\n

[00:20:13] Chris Reynolds: Yes.

\n\n\n\n

[00:20:14] Nathan Wrigley: Okay. So how does that work? Where does this project contract live? How do you in, I’m guessing English in your case, how is it that you write that in a way which is, you’re codifying everything, you make sure that all the T’s are crossed and the I’s are dotted. Just run us through the process of producing a project contract. And obviously, the nature of the topic itself would I’m sure define that, but just give us some rough ideas.

\n\n\n\n

[00:20:40] Chris Reynolds: There’s a lot of markdown files. Fundamentally, like Claude is supposed to read, at the beginning of each new session, the contents of a Claude.md file that is in the project directory. Wherever you’re running Claude, you can give it a Claude.md and it will, that will give it an understanding of whatever, how it should interact with this project.

\n\n\n\n

Within that and beyond that, you can have a bunch of other different files. You can tell it about, you have a docs folder and you have more documentation there. There’s also an agents.md file, which you can use in various different ways. It’s another sort of markdown file that’s only for agents.

\n\n\n\n

And, in my case, what I was talking about, is there’s a reviewer agent. So it’s specifically like you talk to Claude Code, you say build this thing, and then after it’s done building the thing, a reviewer agent is spawned to check the work of the first agent. Make sure that it did a whole bunch of stuff, and then if it didn’t reject the code.

\n\n\n\n

And so there’s a bunch of files in my repository that are about how the reviewer agent works so that Claude understands what to expect. And then there is a checklist that has, these are the specific line items that I want every single commit to pass before this is an acceptable commit.

\n\n\n\n

And it’s the whole gamut of everything, right? It’s like, does the build pass? Does linting pass? Does the test pass? There’s accessibility pass? All these things. Did you accidentally, or intentionally, commit like secrets to the repository? Stuff like that. It needs to go through this whole checklist. And then, if it passes, it writes a file to the file system that says, okay, approved. And this is the timestamp. And then that allows, if that file exists and the timestamp is valid, then Claude can actually make a commit, and it will actually commit the code. If it does not have that file or the timestamp is too old, then it will be rejected.

\n\n\n\n

And I have this hooked into a pre-commit hook. So if it doesn’t trigger the reviewer agent on its own, if I tell it to commit the code, it’s going to hit that gate, and force the reviewer agent to spawn. So it can’t get around it. And that’s the forcing function.

\n\n\n\n

A couple people are asking about other workflows and whatever, and how to do it in different environments where maybe you’re not using a Git repository or something. And, the key is to find a forcing function. Find something that can’t actually weasel its way out of it, because it’s going to try to weasel its way.

\n\n\n\n

I had to write in a bypass for me to personally be able to commit code, because otherwise it’s going to ask for the reviewer agent. And it will try to use that bypass that I wrote for me because again it’s an unruly child. So it’s going to try to do that thing and, then you yell at it and tell it not to do that, and it says, oh, I’m very sorry.

\n\n\n\n

So it’s going to try to find these loopholes and circumvent everything that you’re trying to do. So the way that you force it to do all the stuff in this long checklist that I have is by creating something that it just can’t get around.

\n\n\n\n

[00:23:27] Nathan Wrigley: So I can imagine that the people listening to this, the sort of AI doomers saying, “But Chris, it’s just AI all the way down. You’ve got AI checking AI.”

\n\n\n\n

[00:23:34] Chris Reynolds: Yes.

\n\n\n\n

[00:23:35] Nathan Wrigley: Which on the face of it seems really peculiar. And also the fact that the guardrail is at the end of the process as opposed to, you would kind of hope that it would get it right at the beginning, but then you might just have to reject whole things based upon it. And then the fact that it sounds like from what you were saying, as if AI has almost like a predilection to misbehave.

\n\n\n\n

[00:23:57] Chris Reynolds: I assume it has a predilection to misbehave.

\n\n\n\n

[00:23:59] Nathan Wrigley: But does it feel like that? Is this predictability to, if I don’t put the guardrails and I don’t put this sort of corralling function in, what I’m going to get out is just going to be aberrant and useless and just who knows what’s going to come out?

\n\n\n\n

[00:24:12] Chris Reynolds: I think that’s a little bit extreme. I said that I assume that it’s going to misbehave because if you don’t assume. Basically if you don’t prepare for the worst, it’s going to bite you in the ass.

\n\n\n\n

[00:24:21] Nathan Wrigley: Yeah.

\n\n\n\n

[00:24:22] Chris Reynolds: So you have to assume. And one of the things I’m sure that people who are listening who have used LLM coding tools specifically, will be able to relate to, is oftentimes, this is one of the first discoveries that I had when I started using this stuff. You ask it to build a thing and it builds that thing, but there’s one thing wrong with it. So you ask it to fix that one thing and it refactors the entire thing.

\n\n\n\n

And in the course of refactoring the entire thing, it lost some other thing that was there before that you liked that you want to have back. And so you tell it to bring that back and it rewrites the whole thing again, right?

\n\n\n\n

That’s how it works, because a lot of times it’s not able to like even retain the actual memory of the original state. So it just writes things from scratch every single time. Which from a human perspective is like bonkers, right? But from a computer standpoint, it’s oh this is a new interaction, so I’m doing this fresh.

\n\n\n\n

So the way that you solve for that problem is okay, if I force you to write tests for every single thing you’re doing, then you can’t go and revert a bunch of stuff or refactor stuff without those tests failing.

\n\n\n\n

[00:25:31] Nathan Wrigley: Right?

\n\n\n\n

[00:25:32] Chris Reynolds: And again, starting to like build things around it to force it into a shape so that it’s actually the thing that is closer to what you want. What I’m hearing is anxiety about the uncertainty that non-determinism, the like chaos, you never know, I don’t know. It doesn’t bother me. And I don’t know if that’s a character flaw of mine that it doesn’t bother me, as much. Or if it’s just like being comfortable with the chaos, but also understanding the chaos enough to know what to expect.

\n\n\n\n

Because the other thing I think that we’re seeing right now, in this moment in August of 2026, in Phoenix, Arizona, is that a lot of people are looking at this stuff for the very first time. A lot of people are just now coming to Claude Code, or have only started using it in the last couple months because it got really good around like November, December last year. Like, all of a sudden they did an update and it was just phenomenal, and it was able to do way more. And not just Claude, but like all the LLMs, they got really good at code. All of a sudden, and so now it’s a big thing, and so now more people are using it.

\n\n\n\n

But I’ve been playing with LLMs since the very first Chat GPT model. I say that because there’s a lot of stuff that I learned over the course of the process, and I wasn’t using it for work necessarily. I was just using it for play and for, Dungeons and Dragons and whatever. But a lot of those things that I learned over the course of using it in those contexts, those non-work contexts, led me to understand the limitations, and where it falls down, and where it does well and the things to expect. So that when we got to this point, I already had an understanding of this is how it works, so these are the things I need to be looking for.

\n\n\n\n

[00:27:15] Nathan Wrigley: Yeah. So that’s really curious. So the history that you have with it has given you a real deep understanding of what the expectations are for “Okay, this is typically where it doesn’t perform well or these are the things that it typically can do well.”

\n\n\n\n

[00:27:26] Chris Reynolds: Yeah.

\n\n\n\n

[00:27:27] Nathan Wrigley: Okay. So with your guardrails built in, so we’ve got your project contract that you buried inside the project somewhere, and it’s doing all these checks and balances. Where does that take you in terms of confidence?

\n\n\n\n

I don’t know if you want to put a number on that, like a percentage. How does it take you from zero to 99% confident in what’s coming out? Is it more like 80%? Is human review needed in every single circumstance, or. Just run us by the confidence that you get from producing that document?

\n\n\n\n

[00:27:54] Chris Reynolds: I don’t review line by line the code that AI produces.

\n\n\n\n

[00:28:01] Nathan Wrigley: Just curiously, at what point in the calendar did that moment occur where you suddenly said to yourself, you know what, there’s just no, I’m just reading everything and everything’s great. There’s just no point in me checking everything now.

\n\n\n\n

[00:28:13] Chris Reynolds: I mean, probably way earlier than it should have, if I’m honest. Yeah, I don’t, and one of the arguments that I’ve actually heard some of the engineers that I work with, at Pantheon, say is the fact that no one is actually reading all of that code generated by Claude or whatever.

\n\n\n\n

And, his argument is like, basically no one’s going to do that because it’s so much, and it’s here and whatever. So you can say that you’re doing it, but you’re probably not. And if you say that you’re doing it and you’re not, you’re just lying to yourself. So it’s better to be honest and be like, yeah, no, I don’t actually, than to pretend like that’s not the case. So I don’t actually review a lot. And not like intentionally, like I will look at it. The demo, I gave a live demo yesterday, which is exciting because it’s a non-deterministic thing.

\n\n\n\n

[00:29:02] Nathan Wrigley: Oh yeah. Good luck.

\n\n\n\n

[00:29:04] Chris Reynolds: But what was interesting about that is because the scope of the task was very small. It was like, there’s a horizontal bar on mobile devices on this specific page on my site. Very specific thing. And I, when I practised it, half a dozen times or more, it got to the same conclusion every single time. When I demoed it yesterday, it got to the same conclusion.

\n\n\n\n

And I can look at the code and okay, there’s the tests. I’m not going to read the test and how it wrote the test, but I can see what the change in is. It is just adding a class to a div. And it pretty much was the same class to the div every single time. So like, I can review that and be pretty confident with that. That’s a hundred percent confidence.

\n\n\n\n

Also extremely small change, but that’s also at the end of yeah, it went through the 45 point checklist. It did all of the things. It wrote the accessibility, it did the, like everything is following these rules. And because I have all of these rules, and because I’m fairly confident that it’s actually going through that list, that also makes me feel like, okay, I can be a little bit, it’s a little bit more trustworthy, when it produces this output, then it was before it had all that stuff in place.

\n\n\n\n

[00:30:10] Nathan Wrigley: Yeah. So in my head, there was a period of time where I didn’t trust that if I said to my son, what’s three add seven, that 10 would come out. And then there was a moment where I don’t need to ask him that question anymore. I have complete confidence that if I were to ask him that question, he would say 10.

\n\n\n\n

[00:30:26] Chris Reynolds: Sure.

\n\n\n\n

[00:30:26] Nathan Wrigley: And it would be 10 every single time.

\n\n\n\n

[00:30:28] Chris Reynolds: Yeah.

\n\n\n\n

[00:30:28] Nathan Wrigley: And it I think, I feel like it’s a bit like that. Over time you’ve just grown accustomed to, it can do this kind of thing. I now trust it in that sphere. Does that sort of sum it up? You, personally, you have built up that level of trust, but it wouldn’t necessarily be the same for me if I started my journey. I would have to go through the building up of trust in the same way that you did.

\n\n\n\n

[00:30:49] Chris Reynolds: Yes.

\n\n\n\n

[00:30:49] Nathan Wrigley: Okay.

\n\n\n\n

[00:30:49] Chris Reynolds: But I do think that, like the reviewer workflow that I built can help you get there. Because if you put that into your project, and customise your list of, your checklist for all the things that you want to have running on everything that you are running. The goal is to make it more trustworthy, and to make it more do the thing that you expect and wanted to do.

\n\n\n\n

[00:31:10] Nathan Wrigley: Could you just tell us some of the things that are in that document? So I think you said 45 and maybe that’s subject to change. Maybe next week it’ll be 49 or what have you. And maybe some of the more curious ones that wouldn’t necessarily drop out. I can imagine that you would ask it to do certain things, de rigueur, every time that, but some of the more curious ones, perhaps ones that you’ve come up with lately that our listeners might think, oh, okay. I’ve never thought of that.

\n\n\n\n

[00:31:31] Chris Reynolds: I have it use test driven development or I tell it to use test driven development. And the reason for that. So test driven development is when you write the test and then you write the code to pass the test.

\n\n\n\n

And it turns out that AI can do this far better than humans, because humans don’t want to do this, because it’s like, it breaks your brain. But an AI can do it, and if an AI can do it, then I’ll let the AI do it. And by having the AI write the test that the code needs to pass in order to accomplish the task that you’re asking it to do first, then that means A, again, you’re never going to have regressions, because the test is already there. And B, it already knows how to fix the thing, because it wrote the test to make the thing fail. So that’s a sort of a important nuance, in there, that isn’t necessarily, like you can write unit tests, whatever, but starting with the test is really valuable.

\n\n\n\n

There’s a couple things that I have in the checklist specifically. The big one, I think that is maybe curious is making sure that it doesn’t write secrets to the file system.

\n\n\n\n

[00:32:33] Nathan Wrigley: Even saying that out loud is so peculiar.

\n\n\n\n

[00:32:36] Chris Reynolds: Because it will do that. And the reason why that rule has to exist is because there was a point in time when that rule didn’t exist and then it wrote this. And that’s even like secrets in, WordPress has a weird concept of what a secret is anyway, because we have API keys in our wp-config files and stuff like that. And theoretically we shouldn’t be doing that either. But we don’t have a really good universal form of like, secrets management. So it gets wibbly wobbly. But yeah, so not writing secrets to the file system is pretty important.

\n\n\n\n

Yeah, honestly it’s really, it’s not super wild stuff. It’s like making sure tests pass, making sure you have accessibility checks. I guess one thing that is maybe unique So I designed this site with Claude too. Which is also an experiment because it’s like, I have no idea how AI is going to approach design. And so one of the things, I know like at my workplace, we use Storybook, for our design system. And I thought, that seems like a good tool. Maybe I can have AI build a Storybook.

\n\n\n\n

And so I basically built this system so that it will, when I want it to build a new component, it builds the component in Storybook so that I can review the design first, and go back and forth there, and then implement the component into the thing. So there’s stuff in there about, if you’re introducing any new design component, then it has to be done in Storybook first.

\n\n\n\n

[00:33:56] Nathan Wrigley: Okay. Yeah. Yeah. That, some interesting stuff in there, but I guess everybody’s going to have a sort of different file.

\n\n\n\n

[00:34:02] Chris Reynolds: Yeah.

\n\n\n\n

[00:34:02] Nathan Wrigley: Okay. So I wonder if you have any intuitions as to the process that you’ve just described and that you’ve gone through, August, 2026. Do you have an intuition that in the next few years, this kind of thing, the AI companies will solve this problem, that it will become more truthy by default? Or do you see it, that this is a thing that we’re going to have to wrestle with from now on? That our systems, our AIs, there’s always going to be this strange tendency to hallucinate, to make things up, just to go off the rails and do peculiar things.

\n\n\n\n

Now obviously I’m asking you to stare into a crystal ball, but I do wonder if there has been a more truthful output over time, or if it’s just getting wilder and wilder.

\n\n\n\n

[00:34:42] Chris Reynolds: I think that what we will see more of is more integrated like agent orchestration. So what I’m doing is essentially like a form of agent orchestration. I’ve got one agent doing the one thing, I’ve got another agent that reviews the work of the first thing.

\n\n\n\n

And even like the keynote yesterday, she was talking about a not very dissimilar process, where like there’s five different agents and reviewer was one of them. There’s like a planner, there’s a coder, there’s a whatever. And I think that is a thing that we’ll probably start to see more of and then maybe at some point. when you talk to Claude, when you write a prompt into Claude, you’re talking to a thing. But underneath the hood, in the black box of Claude’s brain, there’s actually five different agents that are running concurrently that are processing this thing and doing their different tasks or whatever. So when it’s thinking, then it’s doing five different, like it’s going through that process. I think maybe that’s the thing that might happen.

\n\n\n\n

[00:35:40] Nathan Wrigley: I’m just so fascinated by how, by now the year 2026, we’ve just all accepted that this is how it is. But if you could put 2021 Chris in that chair, you are sat over there somewhere listening to you talk, you’d be, “No, this is Star Trek. This is literal science fiction. I haven’t the faintest idea of what he’s talking about. None of this adds up, computers can’t do that. They’ll never do that.”

\n\n\n\n

And yet here we are, we kind of blew through the Turing Test, like it was nothing. And that felt for the longest time, like that was going to be an important milestone. And everybody checked their watches like, “Oh goodness, that happened.” It is remarkable how quickly the landscape is changing.

\n\n\n\n

[00:36:17] Chris Reynolds: What’s really interesting is one of the first people that I read about AI stuff, she’s an AI researcher, and she specifically focuses on small language models like the very old models that existed before GPT and whatever. And fundamentally how these things all work is very very similar. But like back, so this is getting into 2021, 2022 era of stuff, where like, it exists but it’s really bad. I don’t know how many people still remember, Horse eBooks, the Twitter account.

\n\n\n\n

[00:36:49] Nathan Wrigley: No.

\n\n\n\n

[00:36:50] Chris Reynolds: But it was like this bizarre account, that was a bot account, that was just like an AI or machine learning or something, some robot just like spitting garbage into Twitter, that just made no sense at all. And was, it’s, hilarious. And you also remember, in the not terribly distant past, when we would get like, weird phishing emails, but it would have different tone changes in voice. Like it was very, obviously written by a robot or like spam messages and stuff like that. And that was just what existed at the time.

\n\n\n\n

None of the things that exist today are like, they all come from the same root, but for sure, the flip from this is garbage, to this is genuinely useful, or at least sounds humanlike, was it, felt like overnight. And it felt like a wild flip. When Chat GPT first became available for the public, that was how is this even? And also like there is the whole thing, very shortly after that when Microsoft released the Bing Chat bot.

\n\n\n\n

[00:37:53] Nathan Wrigley: Yes.

\n\n\n\n

[00:37:53] Chris Reynolds: There was the whole thing about like Bing wanting to marry this reporter. And that goes to show how little we even know about the things that we’re building. Like, none of the AI companies really understood, or even still I think understand? Why it works the way it does.

\n\n\n\n

[00:38:11] Nathan Wrigley: That’s quite an alarming admission actually.

\n\n\n\n

[00:38:13] Chris Reynolds: It’s just, it does.

\n\n\n\n

[00:38:14] Nathan Wrigley: Yes.

\n\n\n\n

[00:38:14] Chris Reynolds: So we’re just going to keep going. Which is also, I find that alarming from the perspective of, now they’re asking for like huge new data centres across everywhere. I’m sure anybody listening to this is angry about data centres, and I’m angry about data centres. But like, that’s with the belief that those data centres are going to matter meaningfully. And I don’t know if they will.

\n\n\n\n

Like we don’t, because we didn’t know how we got here. And it’s doing the thing now. I can use it to code my site. Like I can do that today. Do I need 50 new data centres across the United States to make that better? I don’t know.

\n\n\n\n

[00:38:55] Nathan Wrigley: You’ve almost described the perfect dystopian science fiction plot there, haven’t you in a way? This stuff just all happened. It gave a really beguiling approximating humanlike responses that got more human over time to the point where we couldn’t.

\n\n\n\n

[00:39:08] Chris Reynolds: Did we just invent Skynet?

\n\n\n\n

[00:39:09] Nathan Wrigley: Yeah. We, can’t detect that it’s not a human anymore. It really does feel like, somewhere hidden from our view is an evil overlord stroking a cat or something like that.

\n\n\n\n

And of course, we don’t really know how we got here, but I am so beguiled by it. I’ve got the same concerns as you. Data centres, the environment, all of this wasting of the Earth’s resources. But at the same time, that doesn’t seem to stop me from being curious about it and trying it out and the AI is just wrong for everybody else to use. But when I use it, oh, it’s perfectly fine. But, you know? That’s a thing.

\n\n\n\n

[00:39:41] Chris Reynolds: Yeah.

\n\n\n\n

[00:39:42] Nathan Wrigley: Okay. I think we’ll knock it on the head there, as we say in the UK. Is there anything you wish that we had covered just before we end it? Or do you think we got through most of what we needed to.

\n\n\n\n

[00:39:50] Chris Reynolds: I think one of the things that gives me pause or concerns me most about AI, is the sort of like handing over that amount, or an amount or any amount, of sort of cognitive load to AI. And therefore just letting those parts of our own selves, and our own brains like dwindle and wither.

\n\n\n\n

And I think about this from the perspective of just me personally, my kids, my family, whatever using it and then like becoming less skilled ourselves. But I also think about it from the perspective of, if we’re in engineering, in development, in the world that we are working in. If we are telling everyone, “oh your job now is to be essentially a senior engineer reviewing the work of a junior developer, that is the AI,” how do senior developers exist?

\n\n\n\n

[00:40:41] Nathan Wrigley: You’ve removed that bottom rung of the ladder, haven’t you? Yeah. You’ve taken away the capacity for somebody coming out of college to go on the first step. And then the second and then the third. Because the AI did all the first, second and third step.

\n\n\n\n

[00:40:52] Chris Reynolds: Like I understand that there’s a different set of skills, and a different set of rules and whatever, things that are going to be part of your job, to be that reviewer, to be that new engineer that uses AI to be the developer. But there’s certain things I think, that are part of that learning journey that got me to where I am, that got other senior developers to where they are, to understand the context, to be able to guide the AI that I don’t know that you can circumvent that. I don’t know that you can bypass that.

\n\n\n\n

[00:41:22] Nathan Wrigley: I think you’d be curious if the AI company’s employed like a really credible team of philosophers. You know what I mean? Like for every a hundred developers, we have 10 philosophers, who are just going to think and worry about what the heck’s going on. It sounds ridiculous, but maybe that’s what we need because, some of the things that you’ve described today, they’re just so curious that you need to shepherd it, you need to constrain it, you need to worry about the bizarre things that it can get up to. We need to worry about the future, the data centres and all of this.

\n\n\n\n

And, on some level it does feel a bit like we’ve got a blindfold on. We appear in our own minds at least we appear to be going in the direction that we want to go in. But I don’t know, I guess only time will tell. If we’re all here in 2027.

\n\n\n\n

[00:42:05] Chris Reynolds: That will be the thing.

\n\n\n\n

[00:42:05] Nathan Wrigley: Then we succeed 2029, who knows? All bets are offs.

\n\n\n\n

[00:42:09] Chris Reynolds: Yeah. I can count three years in the future that my job is probably not going to go away. But beyond after that, beyond that, I don’t know.

\n\n\n\n

[00:42:15] Nathan Wrigley: Okay.

\n\n\n\n

[00:42:16] Chris Reynolds: I’m pretty sure, I’m pretty sure my job is okay because I do think, developer relations at all about talking to humans, but maybe there’s not going to be any humans to talk to, so maybe I’ll just be talking to AI.

\n\n\n\n

[00:42:24] Nathan Wrigley: Okay. WordCamp US 2029. It’s a date. We’ll be back at that point.

\n\n\n\n

Chris Reynolds, thank you for sharing all of those thoughts and, yeah, that’s been really educational. Thank you.

\n\n\n\n

[00:42:34] Chris Reynolds: Thank you for having me.

\n
\n\n\n\n

On the podcast today we have Chris Reynolds.

\n\n\n\n

Chris has been immersed in the WordPress world for around 20 years, with a career spanning agency work and now leading the developer relations team at Pantheon. His deep WordPress experience is paired with a playful approach to emerging tech, making him a familiar voice at events like WordCamp US and across the wider community.

\n\n\n\n

In today’s episode, the discussion explored the fast-changing landscape of AI-assisted development, getting into how large language models, like Claude, are not only changing the way developers build for the web, but also how they’re collaborating with these tools while mitigating risks. Chris shares insights from his recent talk at WordCamp US, “Parenting Claude: Guardrails for AI-Assisted Development,” where he introduces the concept of a “project contract”, essentially a structured set of rules and checklists built directly into the coding workflow to ensure AI-generated code meets standards for testing, accessibility, security, and design.

\n\n\n\n

We discussed the newfound playfulness in web development. Chris makes the case that, thanks to AI, the traditional barriers to entry are eroding, enabling even those without a formal developer background to build and experiment much more easily. At the same time we need to be mindful of the importance of establishing robust guardrails, like automated reviewer agents and pre-commit hooks, so the AI doesn’t take shortcuts, or accidentally introduce chaos, or secrets, into your codebase.

\n\n\n\n

The conversation focused not only on technical solutions but also got into bigger questions about trust, how much oversight AI really needs, and the evolving role of developers. Chris emphasised that while these AI tools can accelerate and democratise coding, they can also pose a challenge to conventional wisdom around code review and software reliability. So these new frontiers are both exciting and a cause of anxiety for developers who can sense the industry move from the deterministic, step-by-step processes, to the unpredictable, and occasionally wild, world of non-deterministic AI models.

\n\n\n\n

If you’re interested in how AI is transforming web development, from practical workflows to philosophical ramifications, and how you can implement AI without losing control of your projects, this episode is for you.

\n\n\n\n

Just before we begin, the manner in which this episode was recorded was not my usual process, and so the audio is not quite as good as I’d deliver.

\n\n\n\n

Useful links

\n\n\n\n

 Pantheon

\n\n\n\n

Chris on LinkedIn

\n\n\n\n

Chris’ presentation at WordCamp US 2026 – Parenting Claude: Guardrails for AI-Assisted Development

\n\n\n\n

Chris’ website

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 10 Sep 2026 10:24:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"Matt: Scanning Plugins\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=154706\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://ma.tt/2026/09/scanning-plugins/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:216:\"

It’s a really big deal that we’re scanning all the plugins now.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 10 Sep 2026 10:18:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"Open Channels FM: Gold Eagle, AI Crawlers, and California Lawmakers Shake Up Open Source Security and Infrastructure\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561506\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://openchannels.fm/gold-eagle-ai-crawlers-and-california-lawmakers-shake-up-open-source-security-and-infrastructure/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"Legal and technical systems struggle to keep pace with AI and open source development.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 10 Sep 2026 09:25:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"Open Channels FM: Changelog v5.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561497\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://openchannels.fm/changelog-v5-0/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"Changelog updated for version 5.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 10 Sep 2026 09:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"Open Channels FM: Major Updates with Version 5.0 and New Developments at Open Channels FM\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561471\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://openchannels.fm/major-updates-with-version-5-0-and-new-developments-at-open-channels-fm/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:172:\"Open Channels FM launched version 5.0, featuring new shows, enhanced navigation, and updated content focus, shifting toward open source philosophy and community engagement.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 09 Sep 2026 12:28:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"HeroPress: How a Law Student Ended up with WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=8837\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:156:\"https://heropress.com/essays/how-a-law-student-ended-up-with-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=how-a-law-student-ended-up-with-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:23022:\"\"Pull
Hear Astha read her own essay aloud.
\n\n\n\n

I come from a transitional generation, and somehow, I’ve ended up as a hard core non-tech person in a heavily tech-driven space. Fitting into a box has never really been my thing.

\n\n\n\n

And perhaps, that has been the point.

\n\n\n\n

How often do you think you’re lost?

\n\n\n\n

We often mistake not seeing a path for being lost.

\n\n\n\n

We grow up believing that a meaningful life comes with a roadmap: choose a direction, follow it, and eventually arrive somewhere. But what happens when you can’t see the road ahead?

\n\n\n\n

Sometimes, the path doesn’t exist yet.

\n\n\n\n

My own journey has rarely looked linear. I started blogging on WordPress at 16 because I wanted somewhere to put my thoughts and my poetry. I studied law, organised events alongside it, and while pursuing my passion for public speaking, discovered my love for community building.

\n\n\n\n

And eventually, through a rather topsy-turvy turn of events, I found myself turning my legal background into entrepreneurship.

\n\n\n\n
\n
\n
\"Astha
Astha giving opening remarks at EmpowerWP
\n
\n\n\n\n
\n
\"Astha
Astha in a saree at WCAsia ’25
\n
\n
\n\n\n\n

From the outside, these may look like a lot of deviations. Even to me, there were moments when the future looked bleak and hazy. I wondered whether I was falling behind while people around me seemed to have “figured it out,” found their direction, and were already excelling.

\n\n\n\n

I found myself feeling lost.

\n\n\n\n

Regaining control by finding a pattern

\n\n\n\n

But looking back, and eventually connecting the dots, I realised there was a constant. A pattern I kept coming back to: people, ideas, purpose, and the desire to contribute.

\n\n\n\n

The mediums kept changing. The underlying pull did not.

\n\n\n\n

And that’s when it hit me:

\n\n\n\n

Sometimes, not fitting into the box isn’t the problem. Rather, it is the answer.

\n\n\n\n

Who am I and where it all started

\n\n\n\n

So, let me start again.

\n\n\n\n

My name is Astha, and I discovered the WordPress community back in 2023.

\n\n\n\n

I was a law student who happened to stumble upon a WordPress anniversary meetup, where conversations were already underway about WordCamp Bhopal happening again after quite a while.

\n\n\n\n

I started as an organiser, partly because of the sheer joy of doing what the job demanded— the knack for managing things… and people.

\n\n\n\n

We had two broad purposes: reignite the WordPress ecosystem in town and show attendees a glimpse of Bhopal in the best possible way.

\n\n\n\n

And then, WordCamp Bhopal happened.

\n\n\n\n
\n

WordCamp Bhopal felt like a family reunion, except that you’re meeting those people for the very first time.

\n
\n\n\n\n

Read my experience as an Organiser at my first ever WordCamp | WordCamp Bhopal 2023

\n\n\n\n

What next after organizing the first WordCamp?

\n\n\n\n

I had an incredible time, but also, I had no intentions of dwelling any further.

\n\n\n\n

But credit to the people I met here— WordCamp Mumbai happened.

\n\n\n\n

And somewhere between Bhopal and Mumbai, something shifted.

\n\n\n\n
\n
\n
\"Astha's
Memento by WCMumbai
\n
\n\n\n\n
\n
\"Celebration
WP22 anniversary cake
\n
\n\n\n\n
\n
\"\"
Memento by WCPokhara
\n
\n
\n\n\n\n
\"Family
Family photo from WordCamp Bhopal 2023
\n\n\n\n

The fire these two events ignited in me was insane. By 2024, I found myself thinking much more consciously about the gap I saw between my own field and the technology ecosystem, and between technology and the larger society around us.

\n\n\n\n

I started looking for ways to bridge those gaps wherever I could.

\n\n\n\n

I began seeing community events differently.

\n\n\n\n

Not just as events.

\n\n\n\n

But as opportunities to bring people together around something that could potentially make a difference.

\n\n\n\n

I think community events are a great way— a stage from where you could bring a change. It’s an opening for you to utilize, to serve a purpose.

\n\n\n\n

Outsider to Builder

\n\n\n\n

I was supposed to be an outsider. I was one.

\n\n\n\n

But the cordial, welcoming, “just a smile away” setup of this community had me, for good.

\n\n\n\n

I think the give-and-take in my case sums up as perspective.

\n\n\n\n

Witnessing grandeur of the OG Camp

\n\n\n\n

And then came the ultimate, Crown of Jewels, Camp of Camps: WordCamp Asia.

\n\n\n\n

I had an opportunity to emcee at WCAsia. Absolutely loved the energy. That’s probably the least I can say, because words still don’t quite justify how I felt at that moment.

\n\n\n\n

Exposure is so important— culturally, professionally, and in all the other ways possible. For me, WordCamp Asia was exactly that.

\n\n\n\n
\n

Some people knew of my presence there. A majority did not. The people I knew helped me connect with the people I didn’t. But there were also those who came by without knowing me at all— just a smile or a kind word away.

\n
\n\n\n\n
\n
\n
\"Emcees
Emcees at WordCamp Asia 2025
\n
\n\n\n\n
\n
\"WPBesties
WPBesties winner image feat. Taco, Astha, Anooja, Michelle, Nathan & Lokesh
\n
\n
\n\n\n\n
\"\"
Indian contingent at WordCamp Asia 2025
\n\n\n\n

I can’t seem to get over from WordCamp Asia!

\n\n\n\n

It reminded me, once again, how simple yet profound human connections can be.

\n\n\n\n

I came back apart from a sore throat, with a rejuvenated sense of self, and perhaps a little more courage… which led me to lead EmpowerWP Bhopal 2025.

\n\n\n\n

Shifting focus from What → Why : EmpowerWP Bhopal

\n\n\n\n

This time, the question wasn’t simply what event can we organise? It was who are we organising it for?

\n\n\n\n

This was the time when Women In WordPress were organising women’s day event across the globe. We wanted to bring women in Bhopal into the conversation who weren’t necessarily already part of the ecosystem— homemakers, women looking to upskill, women on career breaks, small business owners, and women who had, for one reason or another, found themselves somewhere outside the active workforce.

\n\n\n\n

When we envisioned EmpowerWP Bhopal, we knew it had to be inclusive— not just for the conventional attendees, but also for the very women who have shaped our lives. Trying to make digital opportunities feel a little closer to home. It went beyond our expectations in the best possible way.

\n\n\n\n
\"Newspaper
Newspaper report highlighting EmpowerWP (Women’s day event)
\n\n\n\n

Read about EmpowerWP: A journey of Growth and Inclusion

\n\n\n\n

And then came the WP Build Tour.

\n\n\n\n

Touring across the State: Igniting the fire amongst students

\n\n\n\n

If EmpowerWP was about creating a bridge for women, WP Build Tour took the idea of access beyond the city.

\n\n\n\n

We went across Madhya Pradesh, our state with 55 districts but just one active WordPress chapter, reaching more than 1,700 college students and helping them build their own websites in a day.

\n\n\n\n
\n

WP Build Tour 2025 was never just about code or content. It was about confidence. About potential realised. About futures being built— one student, one website, one breakthrough at a time.

\n
\n\n\n\n

The idea was rooted in something I had been thinking about for a while— the gap between what the industry needs, what students are taught, and what students actually get an opportunity to do.

\n\n\n\n

So we took WordPress to them.

\n\n\n\n
\"Group
Group photo at one of the stops of WP Build Tour
\n\n\n\n

Bhopal Hosts WP Build Tour 2025: Empowering 1700+ Students Across Central India

\n\n\n\n

The WordPress community had given me the space to try these things— to experiment, to bring in ideas that perhaps didn’t fit the conventional definition of a tech event, and to push boundaries.

\n\n\n\n

And for that, I remain deeply grateful.

\n\n\n\n
\n

Organising events is one thing, and adding purpose to them takes it to another level. For us in Bhopal, organising events has never been just about the “event.” It’s about going a step further and sparking change, no matter how small.

\n
\n\n\n\n

The realisation at WC Pokhara

\n\n\n\n

WordCamp Asia had felt like a peak, and I was quite happy simply soaking in its afterglow.

\n\n\n\n

Then, out of nowhere, I heard whispers of WordCamp Pokhara happening in Nepal. And just like that, something stirred again.

\n\n\n\n

I had no plans. But this one felt like it had plans for me.

\n\n\n\n

There was another thought that kept ringing in my mind:

\n\n\n\n

When I’ve had the privilege of being on both sides– non tech in tech, why not support the people who are still somewhere in the middle? So I wanted to talk about what we can do for the community and also how the community supports us.

\n\n\n\n

Packed up and flew to Nepal. And what did I find? My alter ego, perhaps.

\n\n\n\n

I didn’t go looking for a community this time. But by the end of it, I knew— I belong here.

\n\n\n\n
\"Group
Group photo from WordCamp Pokhara 2025
\n\n\n\n

Read about WCPokhara: People and Purpose

\n\n\n\n

The Ultimate. The Calling. The Answer.

\n\n\n\n

Just made me realise how our calling is not always something we discover at the beginning. Sometimes, it is the urge that keeps bringing us back, again and again, even when we try to walk somewhere else.

\n\n\n\n

And how a community can make that uncertain journey possible: giving us people who encourage us, opportunities we couldn’t have seen alone, and sometimes simply the reassurance that we are not the only ones without a map.

\n\n\n\n

Thanks to constant supporters in this journey including (but not limited to) Aditya Shah, the WP Bhopal community, the global WordPress Community at length, and Yoast! From celebrating WordPress anniversaries together to honoring WP Bhopal’s decade long journey… It’s been worthwhile to grow along.

\n\n\n\n

It got me friends, and somewhere along the way, it got me a life!

\n\n\n\n
\"Peers
Peers turned friends celebrating success of WordCamp Bhopal 2023
\n\n\n\n

What’s up with me now?

\n\n\n\n

Now, I am a lawyer turned entrepreneur, in the tech space. Building Ariham, a people-first agency, with WordPress at its core.

\n\n\n\n

And when I look back at the 16-year-old who simply wanted somewhere to put her thoughts and poetry, I realise I couldn’t have possibly mapped this journey out. I don’t think I was supposed to.

\n\n\n\n

To so many firsts… first time making a website for somebody else, to the first international trip to the Philippines, to first time being a speaker at a foreign land… the WordPress community has taken me places, and I am so excited to see what we’re gonna be up to next!

\n\n\n\n

A lesson I would like to pass on

\n\n\n\n

Maybe the unconventional path isn’t a lack of direction.

\n\n\n\n

Maybe it’s a different way of finding direction.

\n\n\n\n

Maybe your calling isn’t always something you recognise immediately.

\n\n\n\n

Maybe it’s the thing that keeps pulling you back.

\n\n\n\n

The idea you can’t let go of.

\n\n\n\n

The work you keep returning to.

\n\n\n\n

The thing that, even after you’ve tried to walk away, somehow finds its way back into your life.

\n\n\n\n

Because sometimes, the road not taken doesn’t look like a beautiful path waiting for you.

\n\n\n\n

Sometimes, it looks like there is no path at all.

\n\n\n\n

Maybe you’re not lost. Maybe you’re early. Or maybe you are the one building the road.

\n

The post How a Law Student Ended up with WordPress appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 09 Sep 2026 10:17:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Astha Jain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WordPress.org blog: Students Built 108 Websites in Two Weeks in Bangladesh\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=21627\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2026/09/108-student-websites/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9968:\"

In July, students at two campuses in Kishoreganj, Bangladesh, built 108 websites. In eastern Uganda, a workshop that arrived to find no electricity at the school ran anyway, for more than 100 learners, because a former student had asked for it. In Costa Rica, three university students taught a three-session WordPress class to 40 high schoolers, then wrote down exactly how they did it so anyone else could run the same class. None of these students paid to take part, and most had never built a website before.

\n\n\n\n

Those workshops came out of two programs. WordPress Campus Connect brings free, hands-on WordPress sessions to schools and universities, run by local volunteers working from a shared curriculum. WordPress Credits goes further, placing students in mentored internships where they contribute to WordPress itself and earn academic credit for the work. Credits passed 226 graduates in July, up from 199 in June, and now works with 38 partner institutions across 16 countries.

\n\n\n\n

What the Students Built

\n\n\n\n

The Kishoreganj series was organized by Muhibul Haque, who brought Campus Connect to two institutions two weeks apart. Students at Kishoreganj University built 38 sites in the first session. At Kishoreganj Polytechnic Institute, where guest speaker Shipon Karmakar traveled more than 80 kilometers to attend, they built nearly 70 more. The success stories page for the series counts more than 150 participating students so far, with two further institutions still to come.

\n\n\n\n

A workshop in Spain took a different route to the same result. Josep Morán ran two four-hour sessions for 100 vocational students at Escola Pia Sta. Anna in Mataró, who used Playground and AI assistance to build a working plugin that calculates the best time for shore fishing in the city. Students and faculty pointed to the same two takeaways afterward: the certificate they received, and the fact that the skills map onto jobs that exist locally.

\n\n\n\n

A Workshop Without Power

\n\n\n\n

Bulamogi College Gadumire is on the list of Campus Connect schools in eastern Uganda because of Mariam Nairuba. At an event in Kaliro last December, she asked organizer Moses Ssebunya whether the program could come to her former school. She handled the arrangements with the administration herself, and on July 29 she navigated the team there. More than 100 learners were waiting. So was the school’s Director of Studies, who learned that day there was no electricity.

\n\n\n\n

The team had brought laptops, a projector, and extension cables, none of which were useful now. Rather than cancel, they put two questions to the room instead: what do you already know about WordPress, and what would you like to know? “The room exploded,” the organizers wrote in their recap of the day. Students asked whether WordPress was free, how secure WordPress sites really are, and whether they could become developers themselves. John Wayera, one of two first-time volunteers alongside Nairuba, wrote the questions up on the blackboard as they came. The team copied down every answer. Before they left, they presented the school with a Certificate of Appreciation, which the Head Teacher received in front of the governing body.

\n\n\n\n\n\n\n\n

Students Teaching Students in Costa Rica

\n\n\n\n

Rita Robles Loaiza published two pilots built on the premise that the students who just learned this are the best people to teach it next. In the first, three students from the second WordPress Credits cohort at Universidad Fidélitas designed and delivered a workshop for 40 high school girls. The goal of the event is to encourage and increase female participation in STEM academic careers. Their venue was Patrones Hermosos, a science and engineering camp run by Tecnológico de Monterrey and MIT that came to Costa Rica for the first time this year. Every participant built and presented a website, satisfaction came back at 100 percent, and the team turned the whole thing into a replicable guide that any school or community group can pick up and run.

\n\n\n\n

The second pilot has a longer horizon. Thirteen students at Liceo Experimental Bilingüe José Figueres Ferrer, the first high school in the Americas to join WordPress Credits, are working with the Costa Rican Spanish Polyglots team to translate WordPress into es_CR for their community service requirement. When they finish, WordPress will read a little more like home for every Costa Rican who installs it.

\n\n\n\n

Get Involved

\n\n\n\n

There is no cost to bring any of this to a school. Campus Connect gives an organizer a ready-made curriculum and a certificate for every student who completes it. WordPress Credits gives a student a mentor, real contributions to software that runs more than 40 percent of the web, and something concrete to put on a resume. Student Clubs give a campus group a reason to keep meeting after the workshop ends.

\n\n\n\n
\n

Education Initiatives

\n\n\n\n

WordPress Education offers three practical ways for learners to develop skills, gain practical experience, and build confidence as open source contributors.

\n\n\n\n\n
\n\n\n\n

The full Monthly Education Buzz Report for July 2026 has the events that didn’t fit here, including a Campus Connect run entirely by students at Kyoto University of Advanced Science and a Student Club in Dhaka now organizing its own campus event.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 07 Sep 2026 23:19:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Destiny Kanno\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"Open Channels FM: A Blender Full of Tech Predictions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561283\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://openchannels.fm/a-blender-full-of-tech-predictions/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:165:\"Predictions about technology and trends emerge year-round, but many can be trivial or obvious, lacking real insight or originality. But there are the golden nuggets.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 07 Sep 2026 14:19:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"Open Channels FM: Open Signal Launches. Real Talk from Open Channels FM Founder\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://openchannels.fm/?p=2561316\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://openchannels.fm/open-signal-launches-real-talk-from-open-channels-fm-founder/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:111:\"Bob Dunn shares his perspective on open source and the web in the first (official) solo episode of Open Signal.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 07 Sep 2026 10:49:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Bob Dunn\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:21:\"\n \n \n \n \n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"OpenStation Blog: OpenStation Brand: Feeding the machine with chaos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://openstation.blog/?p=510\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://openstation.blog/2026/09/04/openstation-brand-feeding-the-machine-with-chaos/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8363:\"
\n

This post is long overdue, but here it is. The process behind the OpenStation brand, which is, to date, one of the most fun projects I’ve ever worked on. \"💜\"

\n
\n\n\n\n

A name we didn’t have

\n\n\n\n

Here’s the crazy part: I started designing the brand before we even had a name. We had vibes, we had concepts, we had people brainstorming names, and zero idea what would come out. Eventually, after a lot of back and forth, we settled on OpenStation.

\n\n\n\n

That opened the door to many possibilities. Mostly it opened the door to me finally being allowed to draw.

\n\n\n\n
\n\n\n\n

Visual chaos

\n\n\n\n

I started where I always start, which is paper. Advanced technology.

\n\n\n\n

Ugly little drawings, lines, the same shape drawn thirteen times… Then a couple (or a hundred) of hours on Pinterest saving anything that sparkled in my eyes, and a Figma board where I dumped it all and started grouping.

\n\n\n\n
\"\"
\n\n\n\n

And then, I started feeding the machines.

\n\n\n\n

I dumped my chaos to AI: a sketch, a color, a screenshot, a note that said not this, more the other (which is apparently a valid prompt now). It came back with fifteen things, half of them wrong. That wrongness sent me back to the board. I drew again. I fed it again. AI → Figma → Pinterest → AI → Figma… and repeat.

\n\n\n\n

This, for three days.

\n\n\n\n
\n\n\n\n

Locking the concept: Spaceholowave

\n\n\n\n

Don’t search for that because I invented it.

\n\n\n\n

It’s a mix between Space + Holodoor + Synthwave. I kinda wanted to play with some holographic and vibrant elements, Cyberpunk style, floating on the dark void.

\n\n\n\n
\"\"
\n\n\n\n

I was also obsessed with one reference: the holo-door from NMS.

\n\n\n\n

I won’t go into the details of why I know this game or how many hours I spent playing it, but I also will add that on top of that visual reference, I had the Stargate door and Dragon Ball capsules.

\n\n\n\n

You see where I’m going with this, right? Forcing all my nerd references into something that had to make sense.

\n\n\n\n
\n\n\n\n

The logo + Mio

\n\n\n\n

Is it a holo window? A helmet? A candy? A marble? Yes. Or no. You decide, honestly, I’ve stopped thinking at this point.

\n\n\n\n

What I knew was that the O and the S had to live inside the same shape, so it went through a lot of shapes until it became this:

\n\n\n\n
\"\"
\n\n\n\n

I don’t know if Mio came before the logo or after. I think they happened to each other, actually.

\n\n\n\n

But basically, the mark has two shapes: the ring, and the curve carved out of it, which looks like a blob. That’s Mio. Our station resident. He’s the logo’s negative space and turned into a small ghost that glows, making your space a tad more lively.

\n\n\n\n
\"\"
\n\n\n\n
\"\"
\n\n\n\n

Designing Mio is probably one of the most fun things I’ve done in my adult years. \"💜\"

\n\n\n\n
\n\n\n\n

Merchandise makes things real

\n\n\n\n

Logo and Mio in hand, I let the AI go bananas on merchandise. Holographic stickers, enamel pins, the works. We didn’t need stickers on day two. But nothing tells you whether a brand holds up like seeing it on a pin the size of a one-euro coin. If it survives that, it survives a favicon.

\n\n\n\n
\"\"
\n\n\n\n

And little by little the brand was forming.

\n\n\n\n

The types are Geist and Geist Mono: open source, Vercel did a lovely job with them, and they sit right where we live, somewhere between space and a terminal.

\n\n\n\n

Colors were obvious: holo pink over the void. Something that stands out on a dark screen and, big point here, stays accessible.

\n\n\n\n
\n\n\n\n
\"\"
\n\n\n\n
\n\n\n\n

The brand is alive

\n\n\n\n

Three days of brand sprint saved us weeks of “should this be rounder” conversations.

\n\n\n\n

Not because the brand is perfect. Because the brand guideline is alive, public, and hooked into the agents we use, so anyone on the team can make a wallpaper or a widget icon and it comes out looking like part of one big happy Mio family.

\n\n\n\n

Go poke at it yourself:

\n\n\n\n
\n\n
\n\n\n\n
\n\n\n\n

Thank you for reading this messy post \"💜\" and big shoutout to Nick Hamze, who showed up at WCUS with these amazing shoes:

\n\n\n\n
\"\"
\n\n\n\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Sep 2026 08:12:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Núria Peña\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Tue, 29 Sep 2026 13:37:46 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:13:\"last-modified\";s:29:\"Tue, 29 Sep 2026 13:15:36 GMT\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:16:\"content-encoding\";s:4:\"gzip\";s:7:\"alt-svc\";s:5:\"clear\";s:4:\"x-nc\";s:9:\"HIT dca 1\";}s:5:\"build\";i:1788553550;s:21:\"cache_expiration_time\";i:1790732266;s:23:\"__cache_expiration_time\";i:1790732266;}', 'off'); +INSERT INTO `ps_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES +(2904, '_site_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1790732266', 'off'), +(2905, '_site_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1790689066', 'off'), +(2906, '_transient_timeout_dash_v2_3605f57d6641b1f6504fce9d39bcf566', '1790732266', 'off'), +(2907, '_transient_dash_v2_3605f57d6641b1f6504fce9d39bcf566', '
', 'off'), +(2922, '_site_transient_timeout_wp_theme_files_patterns-e63649065a3fb80d206fc8d31dc97157', '1790691986', 'off'), +(2923, '_site_transient_wp_theme_files_patterns-e63649065a3fb80d206fc8d31dc97157', 'a:2:{s:7:\"version\";s:5:\"1.5.1\";s:8:\"patterns\";a:0:{}}', 'off'); -- -------------------------------------------------------- @@ -1068,7 +1089,13 @@ INSERT INTO `ps_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUE (470, 209, '_wp_attached_file', '2026/09/banner-main-caja-texto-2087324820aa.png'), (471, 209, '_wp_attachment_metadata', 'a:6:{s:5:\"width\";i:686;s:6:\"height\";i:152;s:4:\"file\";s:47:\"2026/09/banner-main-caja-texto-2087324820aa.png\";s:8:\"filesize\";i:26295;s:5:\"sizes\";a:3:{s:6:\"medium\";a:5:{s:4:\"file\";s:46:\"banner-main-caja-texto-2087324820aa-250x55.png\";s:5:\"width\";i:250;s:6:\"height\";i:55;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:8983;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:47:\"banner-main-caja-texto-2087324820aa-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:8518;}s:5:\"small\";a:5:{s:4:\"file\";s:46:\"banner-main-caja-texto-2087324820aa-120x27.png\";s:5:\"width\";i:120;s:6:\"height\";i:27;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:2920;}}s:10:\"image_meta\";a:13:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}s:3:\"alt\";s:0:\"\";}}'), (473, 210, '_wp_attached_file', '2026/09/banner-main-caja-texto-02.png'), -(474, 210, '_wp_attachment_metadata', 'a:6:{s:5:\"width\";i:686;s:6:\"height\";i:152;s:4:\"file\";s:37:\"2026/09/banner-main-caja-texto-02.png\";s:8:\"filesize\";i:12759;s:5:\"sizes\";a:3:{s:6:\"medium\";a:5:{s:4:\"file\";s:36:\"banner-main-caja-texto-02-250x55.png\";s:5:\"width\";i:250;s:6:\"height\";i:55;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:6523;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:37:\"banner-main-caja-texto-02-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:7027;}s:5:\"small\";a:5:{s:4:\"file\";s:36:\"banner-main-caja-texto-02-120x27.png\";s:5:\"width\";i:120;s:6:\"height\";i:27;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:2336;}}s:10:\"image_meta\";a:13:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}s:3:\"alt\";s:0:\"\";}}'); +(474, 210, '_wp_attachment_metadata', 'a:6:{s:5:\"width\";i:686;s:6:\"height\";i:152;s:4:\"file\";s:37:\"2026/09/banner-main-caja-texto-02.png\";s:8:\"filesize\";i:12759;s:5:\"sizes\";a:3:{s:6:\"medium\";a:5:{s:4:\"file\";s:36:\"banner-main-caja-texto-02-250x55.png\";s:5:\"width\";i:250;s:6:\"height\";i:55;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:6523;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:37:\"banner-main-caja-texto-02-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:7027;}s:5:\"small\";a:5:{s:4:\"file\";s:36:\"banner-main-caja-texto-02-120x27.png\";s:5:\"width\";i:120;s:6:\"height\";i:27;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:2336;}}s:10:\"image_meta\";a:13:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}s:3:\"alt\";s:0:\"\";}}'), +(476, 211, '_wp_attached_file', '2026/09/banner-main-card-plinko.png'), +(477, 211, '_wp_attachment_metadata', 'a:6:{s:5:\"width\";i:320;s:6:\"height\";i:320;s:4:\"file\";s:35:\"2026/09/banner-main-card-plinko.png\";s:8:\"filesize\";i:118650;s:5:\"sizes\";a:4:{s:6:\"medium\";a:5:{s:4:\"file\";s:35:\"banner-main-card-plinko-250x250.png\";s:5:\"width\";i:250;s:6:\"height\";i:250;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:72689;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:35:\"banner-main-card-plinko-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:30618;}s:5:\"small\";a:5:{s:4:\"file\";s:35:\"banner-main-card-plinko-120x120.png\";s:5:\"width\";i:120;s:6:\"height\";i:120;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:21114;}s:11:\"custom-size\";a:5:{s:4:\"file\";s:35:\"banner-main-card-plinko-320x200.png\";s:5:\"width\";i:320;s:6:\"height\";i:200;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:74521;}}s:10:\"image_meta\";a:13:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}s:3:\"alt\";s:0:\"\";}}'), +(479, 212, '_wp_attached_file', '2026/09/banner-main-card-avia-masters.png'), +(480, 212, '_wp_attachment_metadata', 'a:6:{s:5:\"width\";i:262;s:6:\"height\";i:262;s:4:\"file\";s:41:\"2026/09/banner-main-card-avia-masters.png\";s:8:\"filesize\";i:101145;s:5:\"sizes\";a:4:{s:6:\"medium\";a:5:{s:4:\"file\";s:41:\"banner-main-card-avia-masters-250x250.png\";s:5:\"width\";i:250;s:6:\"height\";i:250;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:107003;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:41:\"banner-main-card-avia-masters-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:44329;}s:5:\"small\";a:5:{s:4:\"file\";s:41:\"banner-main-card-avia-masters-120x120.png\";s:5:\"width\";i:120;s:6:\"height\";i:120;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:30027;}s:11:\"custom-size\";a:5:{s:4:\"file\";s:41:\"banner-main-card-avia-masters-262x200.png\";s:5:\"width\";i:262;s:6:\"height\";i:200;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:79815;}}s:10:\"image_meta\";a:13:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}s:3:\"alt\";s:0:\"\";}}'), +(482, 213, '_wp_attached_file', '2026/09/banner-main-card-bufalo-hold-and-win.png'), +(483, 213, '_wp_attachment_metadata', 'a:6:{s:5:\"width\";i:262;s:6:\"height\";i:262;s:4:\"file\";s:48:\"2026/09/banner-main-card-bufalo-hold-and-win.png\";s:8:\"filesize\";i:116405;s:5:\"sizes\";a:4:{s:6:\"medium\";a:5:{s:4:\"file\";s:48:\"banner-main-card-bufalo-hold-and-win-250x250.png\";s:5:\"width\";i:250;s:6:\"height\";i:250;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:110956;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:48:\"banner-main-card-bufalo-hold-and-win-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:45829;}s:5:\"small\";a:5:{s:4:\"file\";s:48:\"banner-main-card-bufalo-hold-and-win-120x120.png\";s:5:\"width\";i:120;s:6:\"height\";i:120;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:30996;}s:11:\"custom-size\";a:5:{s:4:\"file\";s:48:\"banner-main-card-bufalo-hold-and-win-262x200.png\";s:5:\"width\";i:262;s:6:\"height\";i:200;s:9:\"mime-type\";s:9:\"image/png\";s:8:\"filesize\";i:90855;}}s:10:\"image_meta\";a:13:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}s:3:\"alt\";s:0:\"\";}}'); -- -------------------------------------------------------- @@ -1296,7 +1323,10 @@ INSERT INTO `ps_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post (206, 1, '2026-09-28 22:58:48', '2026-09-29 04:58:48', '', 'banner-main-sombra-01-circle shadow', '', 'inherit', 'closed', 'closed', '', 'a91d259e2fb94849bf4bb7dde0119b3c', '', '', '2026-09-28 22:58:48', '2026-09-29 04:58:48', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-sombra-01-circle-shadow.png', 0, 'attachment', 'image/png', 0), (207, 1, '2026-09-28 23:52:38', '2026-09-29 05:52:38', '', 'banner-main-img-smallIphone', '', 'inherit', 'closed', 'closed', '', '18ba12bbc7c645cabe8f051afd6a1fa0', '', '', '2026-09-28 23:52:38', '2026-09-29 05:52:38', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-img-smallIphone.png', 0, 'attachment', 'image/png', 0), (209, 1, '2026-09-29 00:22:46', '2026-09-29 06:22:46', '', 'banner-main-caja-texto-2087324820aa', '', 'inherit', 'closed', 'closed', '', '1daaa8107a314982a8cef7ea1bc58966', '', '', '2026-09-29 00:22:46', '2026-09-29 06:22:46', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-caja-texto-2087324820aa.png', 0, 'attachment', 'image/png', 0), -(210, 1, '2026-09-29 01:01:25', '2026-09-29 07:01:25', '', 'banner-main-caja-texto-02', '', 'inherit', 'closed', 'closed', '', '6d08b4f4226c4253b7a207f2bdac57ad', '', '', '2026-09-29 01:01:25', '2026-09-29 07:01:25', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-caja-texto-02.png', 0, 'attachment', 'image/png', 0); +(210, 1, '2026-09-29 01:01:25', '2026-09-29 07:01:25', '', 'banner-main-caja-texto-02', '', 'inherit', 'closed', 'closed', '', '6d08b4f4226c4253b7a207f2bdac57ad', '', '', '2026-09-29 01:01:25', '2026-09-29 07:01:25', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-caja-texto-02.png', 0, 'attachment', 'image/png', 0), +(211, 1, '2026-09-29 07:38:25', '2026-09-29 13:38:25', '', 'banner-main-card-plinko', '', 'inherit', 'closed', 'closed', '', '6d2f89ed72244a8eb91e97da12cef06a', '', '', '2026-09-29 07:38:25', '2026-09-29 13:38:25', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-card-plinko.png', 0, 'attachment', 'image/png', 0), +(212, 1, '2026-09-29 07:45:51', '2026-09-29 13:45:51', '', 'banner-main-card-avia-masters', '', 'inherit', 'closed', 'closed', '', '73627e170d9340d0bc65292178584a81', '', '', '2026-09-29 07:45:51', '2026-09-29 13:45:51', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-card-avia-masters.png', 0, 'attachment', 'image/png', 0), +(213, 1, '2026-09-29 07:51:54', '2026-09-29 13:51:54', '', 'banner-main-card-bufalo-hold-and-win', '', 'inherit', 'closed', 'closed', '', '22640edc5e7e4a2ea2f51472c64f3cd8', '', '', '2026-09-29 07:51:54', '2026-09-29 13:51:54', '', 0, 'https://yoapuesto.xyz/wp-content/uploads/2026/09/banner-main-card-bufalo-hold-and-win.png', 0, 'attachment', 'image/png', 0); -- -------------------------------------------------------- @@ -1851,7 +1881,7 @@ ALTER TABLE `ps_actionscheduler_actions` -- AUTO_INCREMENT de la tabla `ps_actionscheduler_claims` -- ALTER TABLE `ps_actionscheduler_claims` - MODIFY `claim_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=1908; + MODIFY `claim_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=1928; -- -- AUTO_INCREMENT de la tabla `ps_actionscheduler_groups` @@ -1893,7 +1923,7 @@ ALTER TABLE `ps_comments` -- AUTO_INCREMENT de la tabla `ps_compressx_images_meta` -- ALTER TABLE `ps_compressx_images_meta` - MODIFY `id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=60; + MODIFY `id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=63; -- -- AUTO_INCREMENT de la tabla `ps_jooosi_fon_fonts` @@ -1911,19 +1941,19 @@ ALTER TABLE `ps_links` -- AUTO_INCREMENT de la tabla `ps_options` -- ALTER TABLE `ps_options` - MODIFY `option_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2872; + MODIFY `option_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2925; -- -- AUTO_INCREMENT de la tabla `ps_postmeta` -- ALTER TABLE `ps_postmeta` - MODIFY `meta_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=476; + MODIFY `meta_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=485; -- -- AUTO_INCREMENT de la tabla `ps_posts` -- ALTER TABLE `ps_posts` - MODIFY `ID` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=211; + MODIFY `ID` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=214; -- -- AUTO_INCREMENT de la tabla `ps_rank_math_internal_links` diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-120x120.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-120x120.png.webp new file mode 100644 index 0000000..1d7b6b3 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-120x120.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-150x150.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-150x150.png.webp new file mode 100644 index 0000000..a8a5e7c Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-150x150.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-250x250.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-250x250.png.webp new file mode 100644 index 0000000..8f9449c Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-250x250.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-262x200.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-262x200.png.webp new file mode 100644 index 0000000..b0d86bf Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters-262x200.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters.png.webp new file mode 100644 index 0000000..233581f Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-avia-masters.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-120x120.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-120x120.png.webp new file mode 100644 index 0000000..a2ccfa4 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-120x120.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-150x150.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-150x150.png.webp new file mode 100644 index 0000000..2d3e251 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-150x150.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-250x250.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-250x250.png.webp new file mode 100644 index 0000000..ed07238 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-250x250.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-262x200.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-262x200.png.webp new file mode 100644 index 0000000..d4a401b Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win-262x200.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win.png.webp new file mode 100644 index 0000000..a7fe7b8 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-bufalo-hold-and-win.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-120x120.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-120x120.png.webp new file mode 100644 index 0000000..c074bd0 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-120x120.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-150x150.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-150x150.png.webp new file mode 100644 index 0000000..555b62e Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-150x150.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-250x250.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-250x250.png.webp new file mode 100644 index 0000000..9c78453 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-250x250.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-320x200.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-320x200.png.webp new file mode 100644 index 0000000..8195f07 Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko-320x200.png.webp differ diff --git a/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko.png.webp b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko.png.webp new file mode 100644 index 0000000..02c9d8b Binary files /dev/null and b/wp-content/compressx-nextgen/uploads/2026/09/banner-main-card-plinko.png.webp differ diff --git a/wp-content/compressx/log/compressx_20260929_log.txt b/wp-content/compressx/log/compressx_20260929_log.txt index cb2d317..e30679d 100644 --- a/wp-content/compressx/log/compressx_20260929_log.txt +++ b/wp-content/compressx/log/compressx_20260929_log.txt @@ -34,3 +34,45 @@ open log file: 2026-09-29 07:01:25 [2026-09-29 07:01:26][notice] Converting banner-main-caja-texto-02-150x150.png to WebP succeeded. [2026-09-29 07:01:26][notice] Start WebP conversion banner-main-caja-texto-02-120x27.png [2026-09-29 07:01:26][notice] Converting banner-main-caja-texto-02-120x27.png to WebP succeeded. +[2026-09-29 13:38:25][notice]Add attachment images id:211 +==================================================== +open log file: 2026-09-29 13:38:25 +[2026-09-29 13:38:25][notice]Start optimizing new media images id:211 +[2026-09-29 13:38:25][notice] Start WebP conversion banner-main-card-plinko.png +[2026-09-29 13:38:25][notice] Converting banner-main-card-plinko.png to WebP succeeded. +[2026-09-29 13:38:25][notice] Start WebP conversion banner-main-card-plinko-250x250.png +[2026-09-29 13:38:25][notice] Converting banner-main-card-plinko-250x250.png to WebP succeeded. +[2026-09-29 13:38:25][notice] Start WebP conversion banner-main-card-plinko-150x150.png +[2026-09-29 13:38:25][notice] Converting banner-main-card-plinko-150x150.png to WebP succeeded. +[2026-09-29 13:38:25][notice] Start WebP conversion banner-main-card-plinko-120x120.png +[2026-09-29 13:38:25][notice] Converting banner-main-card-plinko-120x120.png to WebP succeeded. +[2026-09-29 13:38:26][notice] Start WebP conversion banner-main-card-plinko-320x200.png +[2026-09-29 13:38:26][notice] Converting banner-main-card-plinko-320x200.png to WebP succeeded. +[2026-09-29 13:45:51][notice]Add attachment images id:212 +==================================================== +open log file: 2026-09-29 13:45:51 +[2026-09-29 13:45:51][notice]Start optimizing new media images id:212 +[2026-09-29 13:45:51][notice] Start WebP conversion banner-main-card-avia-masters.png +[2026-09-29 13:45:52][notice] Converting banner-main-card-avia-masters.png to WebP succeeded. +[2026-09-29 13:45:52][notice] Start WebP conversion banner-main-card-avia-masters-250x250.png +[2026-09-29 13:45:52][notice] Converting banner-main-card-avia-masters-250x250.png to WebP succeeded. +[2026-09-29 13:45:52][notice] Start WebP conversion banner-main-card-avia-masters-150x150.png +[2026-09-29 13:45:52][notice] Converting banner-main-card-avia-masters-150x150.png to WebP succeeded. +[2026-09-29 13:45:52][notice] Start WebP conversion banner-main-card-avia-masters-120x120.png +[2026-09-29 13:45:52][notice] Converting banner-main-card-avia-masters-120x120.png to WebP succeeded. +[2026-09-29 13:45:52][notice] Start WebP conversion banner-main-card-avia-masters-262x200.png +[2026-09-29 13:45:52][notice] Converting banner-main-card-avia-masters-262x200.png to WebP succeeded. +[2026-09-29 13:51:54][notice]Add attachment images id:213 +==================================================== +open log file: 2026-09-29 13:51:54 +[2026-09-29 13:51:54][notice]Start optimizing new media images id:213 +[2026-09-29 13:51:54][notice] Start WebP conversion banner-main-card-bufalo-hold-and-win.png +[2026-09-29 13:51:54][notice] Converting banner-main-card-bufalo-hold-and-win.png to WebP succeeded. +[2026-09-29 13:51:54][notice] Start WebP conversion banner-main-card-bufalo-hold-and-win-250x250.png +[2026-09-29 13:51:55][notice] Converting banner-main-card-bufalo-hold-and-win-250x250.png to WebP succeeded. +[2026-09-29 13:51:55][notice] Start WebP conversion banner-main-card-bufalo-hold-and-win-150x150.png +[2026-09-29 13:51:55][notice] Converting banner-main-card-bufalo-hold-and-win-150x150.png to WebP succeeded. +[2026-09-29 13:51:55][notice] Start WebP conversion banner-main-card-bufalo-hold-and-win-120x120.png +[2026-09-29 13:51:55][notice] Converting banner-main-card-bufalo-hold-and-win-120x120.png to WebP succeeded. +[2026-09-29 13:51:55][notice] Start WebP conversion banner-main-card-bufalo-hold-and-win-262x200.png +[2026-09-29 13:51:55][notice] Converting banner-main-card-bufalo-hold-and-win-262x200.png to WebP succeeded. diff --git a/wp-content/themes/yoapuesto/front-page.php b/wp-content/themes/yoapuesto/front-page.php index c1c1c80..e8ecafe 100644 --- a/wp-content/themes/yoapuesto/front-page.php +++ b/wp-content/themes/yoapuesto/front-page.php @@ -17,9 +17,21 @@ $rebet_hero_lottie_path = get_template_directory() . '/lottie-tmp/social-casino. $rebet_hero_lottie_url = is_readable( $rebet_hero_lottie_path ) ? get_template_directory_uri() . '/lottie-tmp/social-casino.json' : ''; -$rebet_hero_foreground_path = get_template_directory() . '/lottie-tmp/social-casino-foreground-cleaned.png'; +$rebet_hero_foreground_path = get_template_directory() . '/lottie-tmp/social-casino-foreground-no-plinko-no-avia-no-buffalo.png'; $rebet_hero_foreground_url = is_readable( $rebet_hero_foreground_path ) - ? get_template_directory_uri() . '/lottie-tmp/social-casino-foreground-cleaned.png' + ? get_template_directory_uri() . '/lottie-tmp/social-casino-foreground-no-plinko-no-avia-no-buffalo.png' + : ''; +$rebet_hero_plinko_path = get_template_directory() . '/lottie-tmp/social-casino-plinko-211.png'; +$rebet_hero_plinko_url = is_readable( $rebet_hero_plinko_path ) + ? get_template_directory_uri() . '/lottie-tmp/social-casino-plinko-211.png' + : ''; +$rebet_hero_avia_path = get_template_directory() . '/lottie-tmp/social-casino-avia-212.png'; +$rebet_hero_avia_url = is_readable( $rebet_hero_avia_path ) + ? get_template_directory_uri() . '/lottie-tmp/social-casino-avia-212.png' + : ''; +$rebet_hero_buffalo_path = get_template_directory() . '/lottie-tmp/social-casino-buffalo-213.png'; +$rebet_hero_buffalo_url = is_readable( $rebet_hero_buffalo_path ) + ? get_template_directory_uri() . '/lottie-tmp/social-casino-buffalo-213.png' : ''; $rebet_hero_phone_path = get_template_directory() . '/lottie-tmp/social-casino-phone-207.png'; $rebet_hero_phone_url = is_readable( $rebet_hero_phone_path ) @@ -150,6 +162,45 @@ foreach ( $rebet_lottie_sources as $slide_number => $lottie_source ) { decoding="async" > + + + + + + + + +