Several minor fixes

* include front matter in recent posts
* use headings consistently (level 1 is title, 2+ for 'in content')
* add links to IPC work
* fix links to mailing list posts

README.md

@@ -28,16 +28,18 @@ This is a list of our findings that we're reasonably happy with so far.
 * [Firefox Data Stores Documentation](text/0010-firefox-data-stores.md) documents the existing data stores across all current Firefox platforms.
 * [Fluent in Prefs Design Review](text/0011-fluent-in-prefs-design-review.md) describes the lightweight design review for Fluent in Prefs.
 * [A brief analysis of JSON file-backed storage](text/0012-jsonfile.md) outlines some of the pros and cons of using a flat file (particularly via `JSONFile.jsm`) to store data in Firefox.
+* [Process Isolation in Firefox](text/0012-process-isolation-in-firefox.md) is a WIP evaluation of how far we can push process isolation to improve security and stability.
+* [IPC Security Models and Status](text/0013-ipc-security-models-and-status.md) is an audit of our current IPC status.
 
 ## Posts
 
 We typically send our newsletters to [firefox-dev](https://www.mozilla.org/en-US/about/forums/#firefox-dev).
 
-* [Browser Architecture Update](posts/2017-07-27-browser-architecture-update.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/ueRILL2ppac).
-* [Browser Architecture Newsletter #2](posts/2017-08-24-browser-architecture-newsletter-2.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/Rc2w2a9e8HQ).
-* [Browser Architecture Newsletter #3](posts/2017-09-22-browser-architecture-newsletter-3.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/p9rTlfFUXlQ).
-* [Browser Architecture Newsletter #4](posts/2017-10-19-browser-architecture-newsletter-4.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/CLFtj8qUSv8).
-* [Browser Architecture Newsletter #5](posts/2017-11-29-browser-architecture-newsletter-5.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/XKp3EthdJ60).
+* [Browser Architecture Update](newsletter/_posts/2017-07-27-browser-architecture-update.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/ueRILL2ppac).
+* [Browser Architecture Newsletter #2](newsletter/_posts/2017-08-24-browser-architecture-newsletter-2.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/Rc2w2a9e8HQ).
+* [Browser Architecture Newsletter #3](newsletter/_posts/2017-09-22-browser-architecture-newsletter-3.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/p9rTlfFUXlQ).
+* [Browser Architecture Newsletter #4](newsletter/_posts/2017-10-19-browser-architecture-newsletter-4.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/CLFtj8qUSv8).
+* [Browser Architecture Newsletter #5](newsletter/_posts/2017-11-29-browser-architecture-newsletter-5.md). See also [mailing-list-post](https://groups.google.com/forum/#!topic/firefox-dev/XKp3EthdJ60).
 
 ## Explorations and Experiments
 

text/0010-firefox-data-stores.md

@@ -1,12 +1,17 @@
+---
+title: Firefox Data Stores
+layout: text
+---
 
-# Introduction
+# Firefox Data Stores
+
+## Introduction
 
 There are a large number of data stores being used to hold data across all Firefox instances and platforms. There is currently nowhere that documents all these data stores and how they share information between them. We have 3 platforms, desktop, Android and iOS and each of these platforms shares data with the others. But not all the information is synced completely across all platforms, and the data itself is not stored in the same way everywhere. When starting to think about how we might provide a holistic user data solution for Mozilla, it is important to understand the scope of the problem and the specifics of the data that is being handled. 
 
 We therefore need to look at all of the data stores that we are currently using and document their purpose, structure, the kind of data that they hold and how they share that data.
 
-
-# Summary
+## Summary
 
 The extensive documentation can be found in the [Firefox Data Stores](https://github.com/mozilla/firefox-data-store-docs) repository.
 

text/0011-fluent-in-prefs-design-review.md

@@ -1,3 +1,8 @@
+---
+title: Fluent in Prefs Design Review
+layout: text
+---
+
 # Fluent in Prefs Design Review
 
 ## Introduction

text/0012-jsonfile.md

@@ -1,3 +1,8 @@
+---
+title: A brief analysis of JSON file-backed storage
+layout: text
+---
+
 # A brief analysis of JSON file-backed storage
 
 Several components in Firefox — including libpref, XULStore, autofill, and logins — follow a general pattern:

text/0012-process-isolation-in-firefox.md

@@ -1,11 +1,16 @@
-Process Isolation in Firefox
+---
+title: Process Isolation in Firefox
+layout: text
+---
+
+# Process Isolation in Firefox
 
 Randell Jesup, Mozilla Browser Architecture team
 
 ## NOTE: this document is a Work in Progress!
 
 
-# OVERVIEW
+## Overview
 
 We’ve recently moved a number of parts of Firefox into separate processes (e10s, multi-e10s, GPU process, compositor, WebExtensions process, GMP).  This has produced some serious improvements in both security (sandboxing content, codecs) and stability (restarting GPU process when a GPU driver crashes, etc).  This project is to evaluate how much further we can push process isolation to further improve these things.
 

text/0013-ipc-security-models-and-status.md

@@ -1,3 +1,8 @@
+---
+title: IPC Security Models and Status
+layout: text
+---
+
 # IPC Security Models and Status
 
 Randell Jesup