docs: add Readme for website

Author: codybrom

CONTRIBUTING.md

@@ -50,6 +50,17 @@ If you'd like to help out with the source code, follow these guidelines:
 5. **Commit Your Changes:** Write a clear commit messages explaining the reason and context for your changes, this will facilitate for other collaborators to understand the scope of your contributions.
 6. **Create a Pull Request:** Submit a pull request from your branch with a clear explanation of the changes that you've made to the original project repository, along with the links to issues referenced (`Closes #123`, `Fixes #345`) .
 
+## Contributing to the Blankie Website
+
+The Blankie website (https://blankie.rest) currently maintains a perfect 100 score across all Google Lighthouse categories:
+
+* Performance
+* Accessibility
+* Best Practices
+* SEO
+
+Any contributions to the website should attempt maintain these scores. Please test your changes using Lighthouse before submitting a pull request. You can run Lighthouse tests using Chrome DevTools.
+
 ## Other Contributions
 
 For now we are not accepting contributions in the following areas, but we hope to in the future:

docs/README.md

@@ -0,0 +1,70 @@
+# Blankie Website
+
+This is the website for [Blankie](https://blankie.rest), built with [Astro](https://astro.build) and deployed on GitHub Pages.
+
+## Production
+
+The live site is available at [https://blankie.rest](https://blankie.rest)
+
+## Tech Stack
+
+- [Astro](https://astro.build) - Static Site Generator
+- [Tailwind CSS](https://tailwindcss.com) - Styling
+- [astro-seo](https://github.com/jonasmerlin/astro-seo) - SEO optimization
+- [@playform/compress](https://github.com/playform/compress) - Asset compression
+
+## Performance
+
+The website maintains a perfect 100 score across all categories in Google Lighthouse (Performance, Accessibility, Best Practices, and SEO). All contributions should ensure these scores are maintained.
+
+## Development
+
+You can develop either locally or using Docker Compose. Both methods will give you hot-reloading and the same development experience.
+
+### Using Docker Compose (Recommended)
+
+From the root directory of the project, simply run:
+
+```bash
+docker compose up
+```
+
+The development server will be available at `http://localhost:4321`. The container will automatically reload when you make changes to the source files.
+
+### Local Development
+
+- Note: Node.js 22 or later is required to run the development server.
+
+If you prefer developing without Docker, open a terminal inside the `docs` directory, then run the following commands:
+
+1. Install dependencies:
+
+    ```bash
+    npm install
+    ```
+
+2. Start the development server:
+
+    ```bash
+    npm run dev
+    ```
+
+3. Build for production:
+
+    ```bash
+    npm run build
+    ```
+
+4. Preview the production build:
+
+    ```bash
+    npm run preview
+    ```
+
+## Deployment
+
+The site is automatically deployed to GitHub Pages at [https://blankie.rest](https://blankie.rest) when changes are pushed to the `main` branch that affect files in the `docs` directory or the GitHub Actions workflow file. The deployment is handled by the GitHub Actions workflow defined in `.github/workflows/pages.yml`.
+
+## License
+
+The documentation website is included under the project's MIT License. See the [LICENSE](../LICENSE) file for details.