docs: update docs

Author: Nap Joseph Calub

DEVELOPMENT.md

@@ -44,15 +44,7 @@ volume.
 
 ### 1. Create a `.env` file
 
-Copy the example below to a file named `.env` in the project root (do NOT commit
-real secrets):
-
-```env
-SURREALDB_ROOT_USERNAME=your_secure_user
-SURREALDB_ROOT_PASSWORD=your_secure_password
-SURREALDB_LOG_LEVEL=info
-SURREALDB_PORT=8000
-```
+Copy the `.env.example` file to `.env` and fill in the values.
 
 ### 2. Start SurrealDB (Detached Mode)
 
@@ -75,23 +67,17 @@ docker compose up -d
 
 ### 3. Persistent Storage
 
-- Data is stored in the `mydata` directory in your project root, which is
-  mounted into the container.
+- Data is stored in the `data` directory in your project root, which is mounted
+  into the container.
 - This means your database persists across container restarts and
   `docker compose down/up` cycles.
-- To inspect the data, look in the `mydata` directory.
+- To inspect the data, look in the `data` directory.
 - To remove all data (dangerous!):
   ```sh
   docker compose down -v
-  rm -rf mydata/*
+  rm -rf data/*
   ```
 
-### 4. Security Best Practices
-
-- **Never commit your `.env` file** with real secrets to version control.
-- Use a `.env.example` with placeholder values for contributors.
-- For production, use a secrets manager or CI/CD environment variables.
-
 ---
 
 ## Database Bootstrapping and Multi-Tenant Setup
@@ -123,7 +109,7 @@ the tenant to the root user by email:
 ```sh
 deno task tenants create <name> <display_name> <root_user_email>
 # Example:
-deno task tenants create favor "Favor Church" admin@example.com
+deno task tenants create example "Example Church" admin@example.com
 ```
 
 This will:
@@ -132,8 +118,3 @@ This will:
 - Insert a tenant record in the global namespace
 - Link the root user to the tenant with graph edges
 - Apply all tenant migrations to the new namespace
-
----
-
-See `docker-compose.yml` for service configuration details. The `version`
-attribute is no longer required or present in the Compose file.

LICENSE.md

@@ -2,31 +2,33 @@
 
 Copyright (c) 2025 - **We Will Craft contributors**
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
 
 The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 ---
 
 # Favicon
 
-The current site favicon was generated using the following graphics from Twitter Twemoji:
+The current site favicon was generated using the following graphics from Twitter
+Twemoji:
 
 - Graphics Title: 1f525.svg
-- Graphics Author: Copyright 2020 Twitter, Inc and other contributors (https://github.com/twitter/twemoji)
-- Graphics Source: https://github.com/twitter/twemoji/blob/master/assets/svg/1f525.svg
+- Graphics Author: Copyright 2020 Twitter, Inc and other contributors
+  (https://github.com/twitter/twemoji)
+- Graphics Source:
+  https://github.com/twitter/twemoji/blob/master/assets/svg/1f525.svg
 - Graphics License: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

README.md

@@ -6,22 +6,41 @@ Everything you need to shepherd your church.
 
 ## Development
 
+If you have all the dependencies installed, you can start the development server
+by running:
+
 ```bash
 deno task start
 ```
 
+For more details, see [DEVELOPMENT.md](DEVELOPMENT.md).
+
 ## Contributing
 
 **Imposter syndrome disclaimer**: We want your help. No, really.
 
-There may be a little voice inside your head that is telling you that you're not ready to be an open source contributor; that your skills aren't nearly good enough to contribute. What could you possibly offer a project like this one?
+There may be a little voice inside your head that is telling you that you're not
+ready to be an open source contributor; that your skills aren't nearly good
+enough to contribute. What could you possibly offer a project like this one?
 
-We assure you - the little voice in your head is wrong. If you can write code at all, you can contribute code to open source. Contributing to open source projects is a fantastic way to advance one's coding skills. Writing perfect code isn't the measure of a good developer (that would disqualify all of us!); it's trying to create something, making mistakes, and learning from those mistakes. That's how we all improve, and we are happy to help others learn.
+We assure you - the little voice in your head is wrong. If you can write code at
+all, you can contribute code to open source. Contributing to open source
+projects is a fantastic way to advance one's coding skills. Writing perfect code
+isn't the measure of a good developer (that would disqualify all of us!); it's
+trying to create something, making mistakes, and learning from those mistakes.
+That's how we all improve, and we are happy to help others learn.
 
-Being an open source contributor doesn't just mean writing code, either. You can help out by writing documentation, tests, or even giving feedback about the project (and yes - that includes giving feedback about the contribution process). Some of these contributions may be the most valuable to the project as a whole, because you're coming to the project with fresh eyes, so you can see the errors and assumptions that seasoned contributors have glossed over.
+Being an open source contributor doesn't just mean writing code, either. You can
+help out by writing documentation, tests, or even giving feedback about the
+project (and yes - that includes giving feedback about the contribution
+process). Some of these contributions may be the most valuable to the project as
+a whole, because you're coming to the project with fresh eyes, so you can see
+the errors and assumptions that seasoned contributors have glossed over.
 
-(Copied from [Adrienne Friend](https://github.com/adriennefriend/imposter-syndrome-disclaimer))
+(Copied from
+[Adrienne Friend](https://github.com/adriennefriend/imposter-syndrome-disclaimer))
 
 ## License
 
-This project is licensed under the MIT License - see the [LICENSE](LICENSE.md) file for more details.
+This project is licensed under the MIT License - see the
+[LICENSE.md](LICENSE.md) file for more details.