diff --git a/meta/plan.md b/meta/plan.md
index d8d7466..5b038bc 100644
--- a/meta/plan.md
+++ b/meta/plan.md
@@ -23,32 +23,20 @@ Features
 
 # Timeline
 
-## Fri 11 March - v0.1
+## Fri 11 March
 
-Outcome visioning: site polished and project launched
-
-* [ ] Elegant site
-  * [ ] Home Page
-  * [ ] Library
-  * [ ] Guide
-* [ ] Announce
-  * [ ] People contacting us
-  * [ ] More github stars
-
-What is our definition of launchable?
-
-- front page looks good (or ok?)
-- videos up somewhere on the front page
+* [ ] [website-v0.1](projects/website-v0.1.md)
+* [ ] Launch DEFERRED to next week
+  * [ ] Announce on Emerge
+  * [ ] Announce on Life Itself
 
 # Workstreams
 
-* [ ] Online web "home" for the published material e.g. "Making Sense of Web3" so that ... ⏫ **🏃‍♂️ For v0.1 https://github.com/life-itself/web3/issues/53 issue**
+* [ ] Online web "home" for the published material e.g. "Making Sense of Web3" so that ... ⏫
+  * [ ] [website-v0.1](projects/website-v0.1.md) **🏃‍♂️ v0.0.1 https://github.com/life-itself/web3/issues/53 issue**
 * [ ] Collaboration and Contribution (paths and involved already interested people) so that we get more contributions
 * [ ] Content ⏫ **see below and https://github.com/life-itself/web3/issues/55 issue**
 * [ ] Library 🔼 see https://github.com/life-itself/web3/issues/44
-* [ ] Engagement and signups
-  * [ ] ⏫ Sign up to get updates / news …
-  * [ ] Subscribe to our youtube channel
 
 # Content
 
@@ -65,73 +53,15 @@ What is our definition of launchable?
   * [ ] Write up our approach to sensemaking and why it matters (write up existing notes into a coherent essay)
     * [ ] Interview Rufus and/or Stephen to clarify what’s the challenge in the sensemaking
 
-# Website
+## Things to merge from old brainstorm
 
-## Tasks
-
-* [ ] Home page
-* [ ] Analytics
-* [ ] Library page
-* [ ] Guide page
-* [ ] Navbar
-* [ ] Notes section (wiki)
-
-### Home Page
-
-Sketch of home page
-![website-homepage-v0.1-2022-02-23.excalidraw](../excalidraw/website-homepage-v0.1-2022-02-23.excalidraw.svg)
-
-Mockup of home page (design): https://excalidraw.com/#room=8bc8a0afb0afc89015dc,W3jd48r8_B2llA2CZ8A33A
-
-* [ ] Home page
-  * [ ] Hero
-    * [x] Layout
-    * [ ] Remove "Get updates" & replace with CTA
-  * [ ] Latest releases
-    * [ ] Replace images either with YouTube video embed or the thumbnail image (?)
-  * [ ] Guide
-  * [ ] Get involved (front page)
-
-### Library Page
-
-Acceptance
-
-* [ ] `/library` landing page exists
-* [ ] brief overview
-* [ ] links to zotero
-* [ ] Also explanation of how to contribute incl organizational structure
-
-Tasks
-
-* [ ] Basic text for library page e.g. what, etc
-* [ ] Link or embed the full library
-
-### Guide
-
-plan of content https://coggle.it/diagram/YidoEewvuAnxT9LA/t/web3-crypto-guide-toc
-
-* [ ] Stub `/guide/` page and could reuse quite a bit of about as introduction
-
-### Get involved `/get-involved/`
-
-* Developers => contribute on github
-* Non-developers
-  * Researchers / academics etc
-    * Contribute to the library, for example by adding articles and research on web3 and background topics.
-    * Write up key concepts and ideas.
-    * Proof edit articles and transcribe dialogs.
-* General: check out our videos and resources
-  * Share the work with others
-* Feedback: share it on the discussions
-
-### Misc stuff
-
-* [ ] Logo (could auto-generate)
-* [ ] Issue tree image
-  * [ ] Export it or embed?
-  * [ ] Make it simpler
-* [x] can we use symlinks to display content from main part of the repo into the site itself **✅ Yes you can. Rufus has this working**
-
-### Someday
-
-* [ ] (Front page?) Aside: Turning the SCQH into a tree esp the complication (note we have a bunch of this structure in the long version of the SCQH with bullet points). Why? A nice illustration of the hypothesis tree approach.
\ No newline at end of file
+* [ ] Announcement post
+  * [ ] Publishing an intro piece on Emerge: Announcing the initiative (just turn SCQH into that …)
+  * [ ] BONUS: (or 2nd article) is about this an exemplar for collective sense-making in a “time between worlds”
+* [ ] Clear pathway for involvement (Job stories)
+* [ ] Where do we publish the original SCQH so that we can link others to it
+  * [ ] Do we need it given we have the tidied version in about page?
+  * [ ]  Reports - write up well with good referencing [aside: how easy is it to pdf in “proper” format via Git e.g. like the primers one]
+* [ ] Engagement and signups
+  * [ ] 👍👍 Sign up to get updates / news …
+  * [ ]  Subscribe to our youtube channel
diff --git a/meta/projects/website-v0.1.md b/meta/projects/website-v0.1.md
new file mode 100644
index 0000000..215f8ce
--- /dev/null
+++ b/meta/projects/website-v0.1.md
@@ -0,0 +1,127 @@
+---
+created: 2022-03-10
+due: 2022-03-11
+---
+
+# Website v0.1
+
+Launchable and *announceable* website.
+
+Sketch of home page
+![website-homepage-v0.1-2022-02-23.excalidraw](../../excalidraw/website-homepage-v0.1-2022-02-23.excalidraw.svg)
+
+Mockup of home page (design): https://excalidraw.com/#room=8bc8a0afb0afc89015dc,W3jd48r8_B2llA2CZ8A33A
+
+## Acceptance
+
+* [ ] Home Page
+  * [x] ⏫ Looks reasonable
+  * [x] Hero section
+  * [x] 🔼 Latest 2-3 videos up somewhere on the front page
+  * [x] Guide section
+  * [x] Library section
+  * [ ] About the project
+* [x] About page **✅ with SCQH**
+* [ ] Library page
+* [ ] ⏫ Sign up to get updates / news …
+
+Bonus
+
+* [ ] Subscribe to our youtube channel
+* [ ] Guide page
+* [ ] SCQH page (? worth doing separate from about??)
+
+## Tasks
+
+* [ ] Home page - see below
+* [ ] Library page
+* [ ] Guide page
+* [ ] Notes section (wiki)
+* [ ] Misc
+  * [x] ⏫ Analytics
+  * [ ] Navbar
+
+### Home Page
+
+* [ ] Hero
+  * [x] Layout
+  * [ ] Fix "get updates"
+    * [ ] EITHER: Remove "Get updates" & replace with CTA OR keep Get Updates using netlify form support => Choose what to do
+    * [ ] Do it 
+* [ ] Latest releases
+  * [x] Working
+  * [ ] Replace images either with YouTube video embed or the thumbnail image (?) @eilidh
+* [x] Guide section
+  * [ ] Needs longer text
+* [x] Library section
+  * [ ] Image needs changing
+* [ ] Why the project
+* [ ] Get involved (front page)
+
+### Library Page
+
+Acceptance
+
+* [ ] `/library` landing page exists
+* [ ] brief overview
+* [ ] links to zotero
+* [ ] Also explanation of how to contribute incl organizational structure
+
+Tasks
+
+* [ ] Basic text for library page e.g. what, etc
+* [ ] Link or embed the full library
+
+### Guide
+
+plan of content https://coggle.it/diagram/YidoEewvuAnxT9LA/t/web3-crypto-guide-toc
+
+* [ ] Stub `/guide/` page and could reuse quite a bit of about as introduction
+
+### Get involved `/get-involved/`
+
+* Developers => contribute on github
+* Non-developers
+  * Researchers / academics etc
+    * Contribute to the library, for example by adding articles and research on web3 and background topics.
+    * Write up key concepts and ideas.
+    * Proof edit articles and transcribe dialogs.
+* General: check out our videos and resources
+  * Share the work with others
+* Feedback: share it on the discussions
+
+### Inbox
+
+* [ ] Logo and favicon (could auto-generate)
+* [ ] Issue tree image
+  * [ ] Export it or embed?
+  * [ ] Make it simpler
+* [x] can we use symlinks to display content from main part of the repo into the site itself **✅ Yes you can. Rufus has this working**
+
+### Someday
+
+* [ ] (Front page?) Aside: Turning the SCQH into a tree esp the complication (note we have a bunch of this structure in the long version of the SCQH with bullet points). Why? A
+
+## Analysis
+
+### Online location and website
+
+* [x] Do we want a "dedicated" website for this? **✅Yes because running of a github repo? See more analysis below**
+* [x] Where is that dedicated website e.g. at labs.lifeitself.us/web3/ or lifeitself.us/web3/? **✅suggest at subdomain because a) can be powered by a repo which others can contribute to b) a little more independent. => https://web3.lifeitself.us ...**
+* [x] How do we build a website?
+  * [x] What is the "backend"? **✅2022-02-26 will start with markdown in github and see if that cuts it**
+    * [x] What are options? **✅ a)markdown on github b) a headless cms like sanity c) wordpress**
+    * [x] Which do we choose ✅ choose github + markdown because simple, allows for open contribution (have a reasonably tech-y contributor base)
+  * [x] What do we use for the frontend? **✅ NextJS as already using it and solid.**
+    * [x] Is raw github sufficient? ✅ No we want something nicer.
+    * [x] Do we use a template? **✅ Not much - keep it barebones for now**
+* [x] ⏫ What is the home page **✅ See https://excalidraw.com/#room=f31febc4be4500863e2c,j3FmcGnhKLb8xlw53pBe6w** 
+* [x] Is there a need for a blog? **✅ No, Maybe in the future**
+  * [x] Do we need comments / discussion? **✅ Maybe and if so we can use github discussions?? or giscus ...?**
+* [x] Do we need user signup? **✅ No - people are publishing via github**
+
+### Design
+
+* How nice to we make this look **✅ To start with can be very basic ... and we'd like to make it look good**
+* What's the vibe? **✅ Friendly, yet authoritative/rigorous. It will be content heavy not many images ...**
+* Where can we find inspiration? **🏃‍♂️ Look at https://www.awwwards.com/websites/tailwind/, dribble, https://www.lapa.ninja**
\ No newline at end of file