diff --git a/source/_daily_emails/2024-04-02.md b/source/_daily_emails/2024-04-02.md
new file mode 100644
index 00000000..e6a3b9e3
--- /dev/null
+++ b/source/_daily_emails/2024-04-02.md
@@ -0,0 +1,27 @@
+---
+title: Releasing a new project one page at a time
+date: 2024-04-02
+permalink: archive/2024/04/02/releasing-a-new-project-one-page-at-a-time
+tags:
+    - software-development
+    - drupal
+cta: ~
+snippet: |
+    How do you release a new website? One page at a time.
+---
+
+How do you release a new project?
+
+Do you build everything and release everything at once?
+
+I've used the strategy of building and releasing it a page at a time and running two versions simultaneously.
+
+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.
+
+When a page is ready, you add it to the list of pages to serve from the new application to put it live.
+
+If there's an issue, it is also easy to revert to the original page.
+
+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.
+
+It's not the right approach for every situation, but it's a useful one to have in the toolkit.