diff --git a/content/_index.md b/content/_index.md
index a9c0320..7350c02 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -1,4 +1,4 @@
+++
title = "number zero"
-description = "Less net work for networks"
-+++
\ No newline at end of file
+description = "a deep-tech software engineering company dedicated to building fully distributed systems"
++++
diff --git a/content/blog/_index.md b/content/blog/_index.md
deleted file mode 100644
index 6c6669e..0000000
--- a/content/blog/_index.md
+++ /dev/null
@@ -1,75 +0,0 @@
-+++
-title = "blog"
-
-description = ""
-
-# A draft section is only loaded if the `--drafts` flag is passed to `zola build`, `zola serve` or `zola check`.
-draft = false
-
-# Used to sort pages by "date", "update_date", "title", "title_bytes", "weight", or "none". See below for more information.
-# sort_by = "none"
-
-# Used by the parent section to order its subsections.
-# Lower values have higher priority.
-weight = 0
-
-# Template to use to render this section page.
-template = "blog/index.html"
-
-# The given template is applied to ALL pages below the section, recursively.
-# If you have several nested sections, each with a page_template set, the page
-# will always use the closest to itself.
-# However, a page's own `template` variable will always have priority.
-# Not set by default.
-page_template = "blog/page.html"
-
-# This sets the number of pages to be displayed per paginated page.
-# No pagination will happen if this isn't set or if the value is 0.
-paginate_by = 0
-
-# If set, this will be the path used by the paginated page. The page number will be appended after this path.
-# The default is page/1.
-# paginate_path = "page"
-
-# If set, there will pagination will happen in a reversed order.
-# paginate_reversed = false
-
-# This determines whether to insert a link for each header like the ones you can see on this site if you hover over
-# a header.
-# The default template can be overridden by creating an `anchor-link.html` file in the `templates` directory.
-# This value can be "left", "right", "heading" or "none".
-# "heading" means the full heading becomes the text of the anchor.
-# insert_anchor_links = "none"
-
-# If set to "true", the section pages will be in the search index. This is only used if
-# `build_search_index` is set to "true" in the Zola configuration file.
-# in_search_index = true
-
-# If set to "true", the section homepage is rendered.
-# Useful when the section is used to organize pages (not used directly).
-render = true
-
-# This determines whether to redirect when a user lands on the section. Defaults to not being set.
-# Useful for the same reason as `render` but when you don't want a 404 when
-# landing on the root section page.
-# Example: redirect_to = "documentation/content/overview"
-# redirect_to =
-
-# If set to "true", the section will pass its pages on to the parent section. Defaults to `false`.
-# Useful when the section shouldn't split up the parent section, like
-# sections for each year under a posts section.
-transparent = false
-
-# Use aliases if you are moving content but want to redirect previous URLs to the
-# current one. This takes an array of paths, not URLs.
-aliases = []
-
-# If set to "true", a feed file will be generated for this section at the
-# section's root path. This is independent of the site-wide variable of the same
-# name. The section feed will only include posts from that respective feed, and
-# not from any other sections, including sub-sections under that section.
-generate_feed = false
-
-# Your own data.
-[extra]
-+++
\ No newline at end of file
diff --git a/content/blog/a_new_direction_for_iroh.md b/content/blog/a_new_direction_for_iroh.md
deleted file mode 100644
index 0202a01..0000000
--- a/content/blog/a_new_direction_for_iroh.md
+++ /dev/null
@@ -1,50 +0,0 @@
-+++
-title = "A New Direction for Iroh"
-date = 2023-02-17
-description = """
-Thus far, Iroh has been built as an implementation of the InterPlanetary File System (IPFS) focused on interoperability with Kubo, the reference implementation of IPFS. In the near future Iroh will break interoperability with Kubo, with the goal of moving the IPFS project forward.
-"""
-[extra]
-author="n0 team"
-+++
-
-[Iroh](https://iroh.computer) will still be aim to implement the core goals of the IPFS design, but moving forward our exclusive focus is on hitting numbers that make Iroh a reliable piece of technology that just works.
-
-The measurements we’ve gathered from our work to date leaves us confident that we need to make breaking changes to get to that “it just works” feeling, which means a new direction for Iroh. Rather than delete the IPFS implementation we’ve built so far we will rename the project to *Beetle*, and put it into maintenance mode.
-
-In the coming weeks we will publish source code, design documents, measurements and production deployment reports that lead up to a re-release of Iroh. You can stay up to date by subscribing to our [youtube channel](https://www.youtube.com/channel/UCdWMU1dBMmB4SrMokGI4jvA).
-
-We have no plans to leave the IPFS community, instead we want to use our freedom from today's spec requirements to take big risks in the name of pushing IPFS forward. We see what we’re building as IPFS 2.0, and plan to convince others that Iroh should be formalized as future IPFS improvements through a quantified design and real world adoption. We may fail, and if so our work will be published in the open as lessons for our colleagues to build upon.
-
-### Why?
-
-Because our metrics are telling us this is what we have to do. “Plan A” for Iroh was something like this:
-
-1. Build a version of IPFS in rust that talks to kubo.
-2. Measure.
-3. Improve.
-4. `GOTO 2`, until Iroh performance metrics approaches a theoretical max.
-
-After 9 months of building and 5 releases of Iroh, we’ve accomplished a few iterations of Plan A. We have built an IPFS implementation that interoperates with kubo, measured it, and shipped a number of performance improvements.
-
-Iroh is nowhere near any theoretical maximum.
-
-There are lots of details to unpack in the future, but to get a sense of numbers, the current interop-focused Iroh needs at least 2,000 simultaneous p2p connections to serve as a gateway; sends on the order of 1,000 messages to retrieve a single 256KB block of data; takes on the order of seconds to resolve DHT queries; and cannot reliably remain connected to the vast majority of peers on the network, if connection is possible at all. We need those numbers to be on the order of 200 peers; less than 1 message per block; and 95%+ reliability. There is no way to get there without breaking things.
-
-So, Plan B:
-
-1. Define an IPFS-like system and quantify “working” in terms of stuff we can measure.
-2. Build a thing that hits those numbers.
-3. Build bridges to other IPFS implementations.
-
-We’ve been working with this “Plan B” approach since early January, and our early experiments in this new paradigm are extremely promising. We’ve also been spending a great deal of time learning from other research in the space, some of which we are deeply excited to utilize given this newfound freedom.
-
-The world needs IPFS. The only way to get there is to learn & grow. If you’ve ever thought “IPFS doesn’t work”, but wished it did, [we would like to hear from you](https://github.com/n0-computer/iroh/discussions).
-
-
\ No newline at end of file
diff --git a/content/legal.md b/content/legal.md
index 6e7f1af..1dcbd6d 100644
--- a/content/legal.md
+++ b/content/legal.md
@@ -53,4 +53,20 @@ template = "page.html"
[extra]
+++
-This is the legal page
\ No newline at end of file
+## Site Policies
+
+### Data and Privacy
+We do not collect any cookies or personal data on this website.
+
+### Licensing
+Except as noted, the contents of this site is licensed under the [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/).
+
+### Licensing Exeptions
+Any code samples on this site are licensed under the [Apache 2.0 License](https://www.apache.org/licenses/LICENSE-2.0).
+
+Trademarks and logos are not included under this license.
+
+In some cases, a page may include content consisting of images, audio or video material, or a link to content on a different webpage (such as videos or slide decks). This content is not covered by the license, unless specifically noted.
+
+### Attributions
+This policy page was adapted from the [Google for Developers](https://developers.google.com/terms/site-policies) policy page.
diff --git a/content/roles/_index.md b/content/roles/_index.md
index 191235f..3b101ab 100644
--- a/content/roles/_index.md
+++ b/content/roles/_index.md
@@ -54,7 +54,7 @@ in_search_index = true
# The taxonomies for this page. The keys need to be the same as the taxonomy
# names configured in `config.toml` and the values are an array of String objects. For example,
# tags = ["rust", "web"].
-[taxonomies]
+# [taxonomies]
# Your own data.
[extra]
@@ -62,4 +62,4 @@ in_search_index = true
## Open Roles at number 0
-### [Business Development Contractor](/roles/biz_dev)
\ No newline at end of file
+### [Business Development Contractor](/roles/biz_dev)
diff --git a/content/roles/biz_dev.md b/content/roles/biz_dev.md
index 82fd1c6..b6f2daf 100644
--- a/content/roles/biz_dev.md
+++ b/content/roles/biz_dev.md
@@ -85,4 +85,4 @@ This is a build role. We're transitioning both the team & the project towards ad
### How to Apply:
-Please submit your resume and a cover letter detailing your experience and why you would be a great fit for this role to "team @ [this web site]". Or just reach out to us [on twitter](https://twitter.com/n0computer)
\ No newline at end of file
+Please submit your resume and a cover letter detailing your experience and why you would be a great fit for this role to "team @ [this web site]". Or just reach out to us [on twitter](https://twitter.com/n0computer)
diff --git a/readme.md b/readme.md
index a6e6b57..438da9d 100644
--- a/readme.md
+++ b/readme.md
@@ -1,17 +1,13 @@
-### base template for zola + tailwind site
-
-This should be a good jumping off point for building sites with zola.
-I started with this [blog post](https://www.maybevain.com/writing/using-tailwind-css-with-zola-static-site-generator/) as a reference, but numerous things are out of date because javascript.
-From there, built out the bones of a template using https://github.com/tchartron/blow as a reference.
+### n0 website
+
+Based on [b5/zola_tailwind_template](https://github.com/b5/zola_tailwind_template)
## Getting started
You'll need [`zola`](https://getzola.org), [`node`](), and [`yarn`]()
```
-$ git clone git@github.com:b5/zola_tailwind_template.git
-$ cd zola_tailwind_template
$ yarn
$ yarn dev
```
-then visit `127.0.0.1:1111` in a browser
\ No newline at end of file
+then visit `127.0.0.1:1111` in a browser
diff --git a/templates/index.html b/templates/index.html
index 69459ef..4e8404a 100644
--- a/templates/index.html
+++ b/templates/index.html
@@ -9,6 +9,8 @@
Less net work for networks
We are an open R&D organization focused on efficient distributed systems
+
An engineering-first, measurements focused company that ships high-quality software that we continually measure & improve.
+
number 0 is fully committed to shipping open source software under permissive licenses.
@@ -17,7 +19,7 @@
We are a
01
-
Rather than optimize for performance or decentralization, we're building networks that use fewer resources to perform the same task.
+
A deep-tech software engineering company dedicated to building fully distributed systems.
With five plus years of experience building open distributed systems each, our founding team understands the importance of collaboration and accessibility when it comes to developing innovative software and conducting research.
We measure everything. We think technology is best when it's a bit creative. We build things that just work. If that sounds cool to you, let's connect.
@@ -29,7 +31,7 @@
We measure everything. We think technology is best when it&apos
-
A toolkit for building distributed applications.
+
A library for building on direct connections between devices, putting more control in the hands of your users.
