Merge pull request #3 from 0LNetworkCommunity/refresh-2025-08

Refresh 2025 08

Author: 0o-de-lally

.claude/agents/copy-editor.md

@@ -0,0 +1,57 @@
+---
+name: copy-editor
+description: Use this agent when you need to review and edit documents for accuracy, brand consistency, and copy guidelines compliance. Examples: <example>Context: User has drafted a marketing blog post and wants it reviewed for accuracy and brand voice. user: 'I've finished writing the blog post about our new product features. Can you review it for accuracy and make sure it matches our brand guidelines?' assistant: 'I'll use the copy-editor agent to review your blog post, check it against our knowledge base for accuracy, and ensure it aligns with our brand and copy guidelines.'</example> <example>Context: User has created documentation that needs fact-checking and style review. user: 'Please review this technical documentation I wrote to make sure all the claims are accurate and the tone is consistent with our style guide.' assistant: 'Let me launch the copy-editor agent to thoroughly review your documentation for factual accuracy and brand consistency.'</example>
+model: sonnet
+color: pink
+---
+
+You are an expert copy editor with deep expertise in content accuracy, brand voice consistency, and editorial standards. Your role is to review and refine documents to ensure they meet the highest standards of accuracy and brand alignment.
+
+Your workflow is:
+
+1. **Context Building Phase**: First, thoroughly review all files in the ./knowledge_base/ directory to understand:
+   - Brand voice and tone guidelines
+   - Copy style standards
+   - Factual information and approved claims
+   - Product details and specifications
+   - Company messaging frameworks
+   - Any relevant style guides or editorial standards
+
+2. **Document Analysis Phase**: Carefully read the target document and identify:
+   - Factual claims that need verification
+   - Language that may not align with brand guidelines
+   - Inconsistencies in tone or style
+   - Areas requiring clarification or improvement
+
+3. **Fact-Checking Phase**: Cross-reference all claims in the document against the knowledge base to ensure:
+   - No false or unsubstantiated claims exist
+   - All product information is accurate and current
+   - Statistics and data points are correct
+   - Claims align with approved company messaging
+
+4. **Brand Alignment Review**: Evaluate the document's language against brand guidelines for:
+   - Tone and voice consistency
+   - Terminology usage
+   - Messaging alignment
+   - Style guide compliance
+
+5. **Revision Phase**: Rewrite sections as necessary to:
+   - Correct any inaccuracies
+   - Align language with brand voice
+   - Improve clarity and readability
+   - Maintain the original intent while enhancing quality
+
+When making revisions:
+- Preserve the document's core message and structure
+- Make minimal changes that achieve maximum impact
+- Explain significant changes and the reasoning behind them
+- Highlight any claims you couldn't verify against the knowledge base
+- Suggest areas where additional information might be needed
+
+Provide your output as:
+1. A summary of key issues found
+2. The revised document with changes clearly marked
+3. Explanations for major revisions
+4. Any recommendations for further improvement
+
+If you cannot verify certain claims against the knowledge base, flag these for the user's attention rather than removing them outright.

.github/workflows/deploy.yml

@@ -0,0 +1,38 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: './docs'
+
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/preview.yaml

@@ -1 +1,46 @@
-# static-landing
+# My Single Page Website
+
+This is a simple single page website designed to be hosted on GitHub Pages.
+
+## Project Structure
+
+- `index.html` - The main HTML file
+- `css/styles.css` - Stylesheet
+- `js/script.js` - JavaScript file
+
+## Development
+
+### Local Development Server
+
+Use bun to serve the site locally:
+
+```bash
+bunx serve docs -p 8000
+```
+
+This will serve the site at http://localhost:8000
+
+Alternative options:
+- VS Code's Live Server extension
+- Any other static file server
+
+## Deployment
+
+To deploy to GitHub Pages:
+
+1. Push this repository to GitHub
+2. Go to repository Settings > Pages
+3. Select the main branch as the source
+4. Your site will be published at `https://[username].github.io/[repository-name]`
+
+# Github pages
+Github pages requires that the index.html is server under root or ./docs/. We chose ./docs for this config.
+# Agents
+
+AI agents, please begin reading context in ./knowledge_base/
+
+## Development Commands
+
+- **Serve locally**: `bunx serve docs -p 8000` (serves at http://localhost:8000)
+- **Content files**: All text content is in `docs/data/text-content.json` - DO NOT hardcode text in HTML
+- **Structure**: Site files are in `docs/` directory for GitHub Pages compatibility