feat: integrate mycoder-docs repository into monorepo

- Added documentation site as packages/docs
- Updated GitHub Action to deploy on docs-release branch
- Removed eslint configuration from docs package
- Created docs-release branch for deployment
- Updated README to include docs package

Closes #253

Author: bhouston

.github/workflows/deploy-docs.yml

@@ -0,0 +1,59 @@
+name: Deploy Documentation to Cloud Run
+
+on:
+  push:
+    branches:
+      - docs-release
+  workflow_dispatch:
+
+env:
+  REGION: us-central1
+  GAR_HOSTNAME: us-central1-docker.pkg.dev
+  PROJECT_ID: drivecore-primary
+  SERVICE_NAME: mycoder-docs
+
+jobs:
+  deploy:
+    name: Deploy to Cloud Run
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Google Auth
+        id: auth
+        uses: google-github-actions/auth@v2
+        with:
+          credentials_json: ${{ secrets.GCP_SA_KEY }}
+
+      - name: Set up Cloud SDK
+        uses: google-github-actions/setup-gcloud@v2
+
+      - name: Configure Docker for GCP
+        run: |
+          gcloud auth configure-docker $GAR_HOSTNAME --quiet
+
+      - name: Set image path
+        run: echo "IMAGE_PATH=$GAR_HOSTNAME/$PROJECT_ID/shared-docker-registry/$SERVICE_NAME:${{ github.sha }}" >> $GITHUB_ENV
+
+      - name: Build and push Docker container
+        run: |
+          cd packages/docs
+          docker build -t ${{ env.IMAGE_PATH }} .
+          docker push ${{ env.IMAGE_PATH }}
+
+      - name: Deploy to Cloud Run
+        id: deploy
+        uses: google-github-actions/deploy-cloudrun@v2
+        with:
+          service: ${{ env.SERVICE_NAME }}
+          region: ${{ env.REGION }}
+          image: ${{ env.IMAGE_PATH }}
+          flags: '--allow-unauthenticated'
+
+      - name: Show Output
+        run: echo ${{ steps.deploy.outputs.url }}

README.md

@@ -103,6 +103,7 @@ Examples:
 
 - [mycoder](packages/cli) - Command-line interface for MyCoder
 - [mycoder-agent](packages/agent) - Agent module for MyCoder
+- [mycoder-docs](packages/docs) - Documentation website for MyCoder
 
 ## Development
 

packages/docs/.dockerignore

@@ -0,0 +1,40 @@
+# Dependencies
+node_modules
+.pnp
+.pnp.js
+
+# Build outputs
+build
+.docusaurus
+dist
+coverage
+
+# Git and GitHub
+.git
+.github
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# Logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# Docker
+Dockerfile
+.dockerignore
+
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?

packages/docs/Dockerfile

@@ -0,0 +1,26 @@
+FROM node:20-alpine
+
+WORKDIR /app
+
+# Install pnpm
+RUN npm install -g pnpm
+
+# Copy package.json and lock files
+COPY package.json pnpm-lock.yaml ./
+
+# Install dependencies
+RUN pnpm install --frozen-lockfile
+
+# Copy the rest of the application
+COPY . .
+
+# Build the Docusaurus site
+ENV NODE_ENV=production
+RUN pnpm build
+
+# Expose the port the app will run on
+ENV PORT=8080
+EXPOSE ${PORT}
+
+# Command to run the application
+CMD ["pnpm", "serve", "--port", "8080", "--no-open"]

packages/docs/README.md

@@ -0,0 +1,60 @@
+# MyCoder Documentation
+
+This package contains the official documentation for MyCoder, an AI-powered coding assistant. The documentation is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
+
+## What's Inside
+
+- **Product Documentation**: Comprehensive guides on how to use MyCoder
+- **Getting Started**: Platform-specific setup instructions for Windows, macOS, and Linux
+- **Usage Guides**: Detailed information on features and capabilities
+- **Blog**: Updates, tutorials, and insights about MyCoder
+
+## Development
+
+### Prerequisites
+
+- Node.js version 18.0 or above
+- pnpm (recommended)
+
+### Local Development
+
+```bash
+# Navigate to the docs package
+cd packages/docs
+
+# Start the development server
+pnpm start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+### Build
+
+```bash
+# Generate static content
+pnpm build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+### Deployment
+
+The documentation site is automatically deployed when changes are pushed to the `docs-release` branch.
+
+## Contributing
+
+We welcome contributions to improve the documentation:
+
+1. Create a feature branch (`git checkout -b feature/amazing-improvement`)
+2. Make your changes
+3. Commit your changes (`git commit -m 'Add some amazing improvement'`)
+4. Push to the branch (`git push origin feature/amazing-improvement`)
+5. Open a Pull Request
+
+## License
+
+This project is licensed under the MIT License - see the LICENSE file for details.
+
+## Contact
+
+If you have questions or feedback, please join our [Discord community](https://discord.gg/5K6TYrHGHt).

packages/docs/blog/agentic-coding-guidelines.md

@@ -0,0 +1,174 @@
+---
+title: Best Practices for Efficient Agentic Coding
+shortTitle: Agentic Coding Best Practices
+date: 2025-03-06
+authors: [ben]
+tags: [ai, coding]
+---
+
+As AI coding assistants become more capable, developers are discovering new workflows that maximize their effectiveness. This post outlines best practices for organizing your codebase to work efficiently with AI agents like MyCoder.
+
+<!-- truncate -->
+
+As AI-based coding agents like [mycoder.ai](https://mycoder.ai) become increasingly capable, adopting structured, clear, and AI-friendly coding practices will enhance efficiency for both humans and AI agents. Here are ten best practices for efficient agentic coding:
+
+## 1. Documentation as Code
+
+Keep comprehensive documentation directly in your codebase:
+
+- Place detailed `README.md` files at the root and within individual packages.
+- Include a clear `CONTRIBUTING.md` outlining coding conventions and workflows.
+- Add inline documentation for complex logic or non-obvious code.
+
+**Example README.md:**
+
+```markdown
+# Frontend Package
+
+This package contains the React frontend application.
+
+## Directory Structure
+
+- `src/components`: Reusable UI components
+- `src/pages`: Page components corresponding to routes
+- `src/hooks`: Custom React hooks
+- `src/utils`: Utility functions
+
+## Development Workflow
+
+1. Run `npm run dev` to start the development server
+2. Follow the component pattern in `src/components/Button.tsx` for new components
+3. All new components must have corresponding test files
+
+## Testing
+
+We use Jest and React Testing Library. Run tests with `npm test`.
+```
+
+## 2. Minimize Package Explosion
+
+Use fewer packages with clear boundaries. Only create separate packages for code shared across multiple applications.
+
+**Preferred Structure:**
+
+```
+my-project/
+  packages/
+    frontend/
+    backend/
+    shared/
+```
+
+## 3. Simplify Project Structure
+
+Favor flatter directory structures with semantically meaningful names to avoid deep nesting.
+
+**Preferred Structure:**
+
+```
+src/
+  auth/
+    LoginForm.tsx
+    SignupForm.tsx
+    useAuth.ts
+    validation.ts
+    auth.types.ts
+```
+
+## 4. Avoid Re-exports and Indirection
+
+Limit the use of re-exported modules to reduce confusion. Import components directly:
+
+**Recommended import:**
+
+```typescript
+import { TextInput } from 'src/components/forms/inputs/TextInput';
+```
+
+## 5. Prefer Compile-Time Validation Over Runtime Checks
+
+Use strong typing and compile-time validation instead of relying heavily on runtime validation:
+
+**Type-safe approach:**
+
+```typescript
+import { createRoute, json } from 'some-router-lib';
+
+export const userRoute = createRoute({
+  path: '/users/:id',
+  loader: async ({ params }) => json(await getUserDetails(params.id)),
+  action: async ({ request }) =>
+    json(await updateUser(await request.formData())),
+  meta: () => ({ title: 'User Details' }),
+});
+```
+
+## 6. Consolidate Linting and Formatting at Root Level
+
+Centralize linting and formatting configurations at the monorepo root to ensure consistency.
+
+**Example root-level package.json scripts:**
+
+```json
+"scripts": {
+  "lint": "eslint . --fix",
+  "format": "prettier . --write"
+}
+```
+
+## 7. Avoid Overly Interdependent Configuration Systems
+
+Favor self-contained, independent configuration files per package rather than complex inheritance:
+
+```
+root/
+  packages/
+    frontend/
+      tsconfig.json
+    backend/
+      tsconfig.json
+    shared/
+      tsconfig.json
+```
+
+## 8. Type-Driven Development
+
+Use comprehensive, precise types to enforce correctness at compile-time rather than relying on runtime validation.
+
+Example:
+
+```typescript
+type User = {
+  id: string;
+  name: string;
+  role: 'admin' | 'user' | 'guest';
+};
+```
+
+## 9. Consistent, Predictable File Organization
+
+Maintain consistent file structures for components:
+
+```
+components/
+  Button/
+    Button.tsx
+    Button.test.tsx
+    Button.module.css
+    index.ts
+```
+
+## 10. Test-Case Driven Documentation
+
+Write clear, self-explanatory tests that also serve as documentation:
+
+```typescript
+test('calculateDiscount applies discounts correctly', () => {
+  const cart = [{ price: 100, eligible: true }];
+  expect(calculateDiscount(cart)).toEqual([{ price: 90, eligible: true }]);
+});
+```
+
+By adopting these agentic coding practices, your codebase will be optimized for clarity, maintainability, and efficient collaboration with AI coding agents.
+
+_(This article is a summary of the personal blog post "[Stop Writing Code for Humans - The Future Belongs to AI Agents](https://benhouston3d.com/blog/agentic-coding-best-practices)" by Ben Houston.)_

packages/docs/blog/authors.yml

@@ -0,0 +1,19 @@
+ben:
+  name: Ben Houston
+  title: Founder of DriveCore
+  url: https://github.com/bhouston
+  image_url: https://github.com/bhouston.png
+  socials:
+    github: bhouston
+    x: BenHouston3D  # Updated from twitter
+    bluesky: benhouston3d.com
+    mastodon: 'BenHouston3D@mastodon.gamedev.place'
+
+mycoder_team:
+  name: MyCoder Team
+  title: MyCoder Development Team
+  url: https://github.com/drivecore
+  image_url: https://github.com/drivecore.png
+  socials:
+    github: drivecore
+    x: BenHouston3D