Update documentation

Author: TotalTechGeek

website/blog/v0.7.0.md

@@ -1,5 +1,5 @@
 ---
-tags: [v0.7.0, patch]
+tags: [v0.7.0, patch, major]
 sidebar_position: 3
 date: 2022-05-17
 authors: 

website/blog/v0.8.0.md

@@ -1,5 +1,5 @@
 ---
-tags: [v0.8.0, patch]
+tags: [v0.8.0, patch, major]
 sidebar_position: 4
 date: 2022-05-18
 authors: 

website/blog/v0.9.0.md

@@ -1,5 +1,5 @@
 ---
-tags: [v0.9.0, patch, fast-check]
+tags: [v0.9.0, patch, fast-check, major]
 sidebar_position: 4
 date: 2022-05-22
 authors: 

website/blog/v0.9.1.md

@@ -0,0 +1,84 @@
+---
+tags: [v0.9.1, patch, minor]
+sidebar_position: 5
+date: 2022-09-13
+authors: 
+    - name: Jesse Mitchell
+      title: Developer of Pineapple
+      url: https://github.com/TotalTechGeek
+      image_url: https://github.com/TotalTechGeek.png
+---
+
+# Improving Property Based Testing (v0.9.1)
+
+Hi all!
+
+This release is focused on providing some small quality of life improvements to the property-based testing features within Pineapple.
+
+There are two main additions to the technology:
+
+#### Namespaces
+
+```js
+/**
+ * Creates the static values for use in various scenarios in our codebase.
+ * @pineapple_define friends
+ */
+function define () {
+  return {
+    kevin: { /* ... */ },
+    shane: { /* ... */ },
+    emily: { /* ... */ }
+  }
+}
+
+/**
+ * #friends.emily, #friends.shane returns 'Battle won!'
+ * #friends.shane, #friends.kevin returns 'Battle draw!'
+ */
+function fight (attacker, defender) {
+  /* ... */
+}
+```
+
+Namespaces might make it simpler to set up various generators & static values that you might wish to use throughout your tests.
+
+#### Better Constant Detection
+
+When you set up definitions in Pineapple, the testing framework will do its best to try to keep track of whether your "arbitrary expression" is actually constant.
+
+This prevents a bunch of duplicate tests from taking place, particularly when it would be annoying (like in snapshots).
+
+Previously, when one would try the following:
+
+```js
+/**
+ * @pineapple_define
+ */
+function define () {
+  return { age: 17 }
+}
+
+/**
+ * @test { name: 'Kevin', age: #age }
+ * The above would not be detected as static in v0.9.0,
+ * but will be in v0.9.1
+ */
+function setupAccount({ name, age }) {
+  /* ... */
+}
+
+/**
+ * @test #age returns false
+ * The above will be detected as constant in both v0.9.0 and v0.9.1
+ */
+function isAmericanDrinkingAge (age) {
+  return age >= 21
+}
+```
+
+Pineapple would not be able to detect that the expression `{ name: 'Kevin', age: #age }` was actually a constant expression. However, if you used `#age`
+outside of a structure as seen in the second example, it would work!
+
+To make developer's lives easier, Pineapple has been improved to try to do a better job of detecting
+constant structures.

website/docs/writing-tests/fuzzing-property-based.md

@@ -115,3 +115,27 @@ function ofAge (person) {
     return person.age > 21
 }
 ```
+
+It is also possible to provide namespaces for your arbitraries:
+
+```js
+/**
+ * @pineapple_define tavern
+ */
+function arbitraries () {
+    return {
+        // you can pass in an arbitrary, a function that returns an arbitrary, or a value that'll be constant.
+        // it will be named the value that you define here in the Pineapple engine.
+        person: fc.record({ id: fc.integer(), name: fc.string(), age: fc.integer(12, 80) }) 
+    }
+}
+
+/**
+ * @test #tavern.person returns args.0.age > 21
+ */
+function ofAge (person) {
+    return person.age > 21
+}
+```
+
+This should make it simpler to organize some of your static / generated data sets that you would like to use for your tests.