From 92c17b475b7a9211e6bcb7137eff111a1b63abc0 Mon Sep 17 00:00:00 2001
From: Ayo Ayco <ayo@ayco.io>
Date: Sat, 1 Mar 2025 10:44:20 +0100
Subject: [PATCH] chore: update readme with 'how it works'

---
 README.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 2d13592..37e2c6f 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@
 
 <h1 align="center">McFly</h1>
 
-<p align="center"><strong>McFly</strong> is a no-framework metaframework<br />that assists in leveraging the web platform</p>
+<p align="center"><strong>McFly</strong> is a metaframework<br />that assists in leveraging the web platform</p>
 
 <p align="center">
   <img src="https://img.shields.io/badge/from-the_future-blue?style=flat" />
@@ -42,6 +42,11 @@ Run the following to generate a McFly starter project.
 npm create mcfly@latest
 ```
 
+## How it works (for the nerds)
+
+It is primarily a runtime middleware for [Nitro](https://nitro.build). Every time a page is requested, the McFly middleware intercepts and assembles the view for the requestor. McFly does this with the assets it knows about which are mostly: pages, components, public assets.
+
+A plugin system allows for the core functionality to only "lean" on platform. Anything not yet a standard is implemented as a plugin which will be easily "swapped" away when the platform catches up.
 
 ## Features