"value":"\n <p>How do you release a new project?<\/p>\n\n<p>Do you build everything and release everything at once?<\/p>\n\n<p>I've used the strategy of building and releasing it a page at a time and running two versions simultaneously.<\/p>\n\n<p>The main live version stays running, and you use a tool like NGINX or Cloudflare as a gatekeeper to direct traffic to the correct application - either the current one or the new one - based on the requested page.<\/p>\n\n<p>When a page is ready, you add it to the list of pages to serve from the new application to put it live.<\/p>\n\n<p>If there's an issue, it is also easy to revert to the original page.<\/p>\n\n<p>I've used this approach with my website and for client Drupal upgrade projects, where some pages are on Drupal 7 and some on Drupal 10.<\/p>\n\n<p>It's not the right approach for every situation, but it's a useful one to have in the toolkit.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>How do you release a new project?<\/p>\n\n<p>Do you build everything and release everything at once?<\/p>\n\n<p>I've used the strategy of building and releasing it a page at a time and running two versions simultaneously.<\/p>\n\n<p>The main live version stays running, and you use a tool like NGINX or Cloudflare as a gatekeeper to direct traffic to the correct application - either the current one or the new one - based on the requested page.<\/p>\n\n<p>When a page is ready, you add it to the list of pages to serve from the new application to put it live.<\/p>\n\n<p>If there's an issue, it is also easy to revert to the original page.<\/p>\n\n<p>I've used this approach with my website and for client Drupal upgrade projects, where some pages are on Drupal 7 and some on Drupal 10.<\/p>\n\n<p>It's not the right approach for every situation, but it's a useful one to have in the toolkit.<\/p>\n\n ",