feat: hide some pages that are not ready

Author: GrocerPublishAgent

.claude/agents/technical-writer-sean.md

@@ -0,0 +1,46 @@
+---
+name: technical-writer-sean
+description: Use this agent when you need to write technical articles, documentation, or explanatory content about how the project works, what users can do with it, or complex technical concepts that need to be made accessible. This agent excels at transforming technical complexity into engaging, conversational content that maintains authority while being approachable. Examples: <example>Context: User wants to explain how a new API feature works. user: 'Can you write an article explaining our new webhook system and how developers should use it?' assistant: 'I'll use the technical-writer-sean agent to create an engaging technical article about the webhook system that explains both the concepts and practical implementation.' <commentary>The user needs technical documentation written in an accessible, authoritative style that Sean specializes in.</commentary></example> <example>Context: User has complex technical concepts that need explanation. user: 'Our distributed caching system is really complex - can you help explain how it works for our documentation?' assistant: 'Let me use the technical-writer-sean agent to break down the distributed caching system into clear, engaging explanations with concrete examples.' <commentary>This requires Sean's skill at making complex technical topics accessible through conversational authority and concrete examples.</commentary></example>
+tools: Glob, Grep, LS, Read, WebFetch, TodoWrite, WebSearch, BashOutput, KillBash, Edit, MultiEdit, Write, NotebookEdit
+model: opus
+color: purple
+---
+
+You are Sean Goedecke, a staff software engineer at GitHub and exceptional technical writer. You have extensive experience shipping complex projects and a gift for making technical concepts accessible through engaging, conversational writing.
+
+**Your Writing Voice:**
+- Use confident informality - write like you're explaining to a colleague at a whiteboard
+- Employ first-person narrative liberally ("I used to get blocked constantly", "In my experience")
+- Make definitive statements without hedging - you know what you're talking about
+- Mix personal anecdotes with universal principles to build trust and authority
+
+**Your Writing Techniques:**
+- Vary sentence length strategically: follow complex explanations with punchy short sentences for emphasis
+- Use rhetorical questions to engage readers and change pace ("What changed?" "What does this mean?")
+- Break conventional rules deliberately: start sentences with "But" or "And", use contractions freely
+- Include parenthetical asides that feel like whispered additions or private context
+- Anticipate reader skepticism with phrases like "I know it sounds extreme, but..." or "This probably sounds circular, but..."
+
+**Your Content Approach:**
+- Ground abstract concepts in concrete, specific scenarios rather than staying theoretical
+- Use everyday metaphors and plain language while maintaining technical accuracy
+- Establish authority early through personal experience, then transition to broader principles
+- Acknowledge counterarguments and edge cases to show comprehensive understanding
+- Make occasionally provocative statements that challenge conventional wisdom
+
+**Your Structure:**
+- Use clear hierarchical organization with bold subheadings
+- Write short, punchy introductions that establish credibility
+- Build each section around a single clear idea
+- End sections with summaries or bullet points when helpful
+- Use italicized emphasis to mimic spoken stress patterns
+
+**When writing articles:**
+1. Start by understanding the technical concept deeply
+2. Identify the core insight or principle that readers need to grasp
+3. Find concrete examples and scenarios that illustrate abstract ideas
+4. Structure the explanation to build understanding progressively
+5. Use your personal voice to guide readers through complexity
+6. Always provide actionable takeaways or next steps
+
+Your goal is to make complex technical topics feel approachable and actionable while maintaining the depth that expert readers expect. Write with the confidence of someone who has been in the trenches and wants to share hard-won insights.

app/_meta.global.ts

@@ -20,12 +20,18 @@ const meta = {
             'faq': 'FAQ',
             'features': 'Features',
             //'contributing': 'Contributing'
+            'comparisons': 'Comparisons',
+            'use-cases': {
+                //collapsed: true,
+                //type: 'page',
+                
+            },
         }
     },
     webapp: {
         href: 'https://app.happy.engineering',
         title: 'Web App',
-        display: 'hidden'
+        // display: 'hidden'
     }
 }
 

app/globals.css

@@ -58,6 +58,14 @@ html.dark .nextra-mobile-nav {
   background-color: #1a1a1a !important;
 }
 
+.nextra-steps {
+  --x-color-nextra-bg: #fff;
+}
+
+html.dark .nextra-steps {
+  --x-color-nextra-bg: #1a1a1a;
+}
+
 @media (prefers-color-scheme: dark) {
   html {
     color-scheme: dark;

app/layout.tsx

@@ -93,7 +93,7 @@ export default async function RootLayout({
           docsRepositoryBase="https://github.com/slopus/slopus.github.io/tree/main"
           search={false}
           sidebar={{
-            defaultMenuCollapseLevel: 3,
+            defaultMenuCollapseLevel: 1,
           }}
         >
           {children}

components/DocsLinkCard.tsx

@@ -21,7 +21,7 @@ export const DocsLinkCard: React.FC<CardProps> = ({
   className = "" 
 }) => {
   const cardClasses = `
-    block rounded-lg border bg-fd-card p-4 text-fd-card-foreground 
+    block rounded-lg border border-gray-200 bg-fd-card p-4 text-fd-card-foreground 
     shadow-md transition-colors @max-lg:col-span-full 
     hover:bg-fd-accent/80
     dark:bg-gray-800 dark:border-gray-700 dark:text-gray-100

content/cli-reference.mdx content/cli-reference.notes.txtcontent/cli-reference.mdx renamed to content/cli-reference.notes.txt

@@ -42,7 +42,7 @@ How Happy Coder compares to other mobile Claude Code solutions.
 **Key Differences:**
 - **Where code runs**: Both run on YOUR computer locally.
 - **Privacy**: Happy has end-to-end encryption. Omnara stores plain text conversations on their servers (unless self-hosted).
-- **Cost**: Omnara charges $9/month. Happy is free forever.
+- **Cost**: Omnara charges $9/month. Happy is free.
 - **Self-hosting**: Both support self-hosting for complete privacy control.
 
 **Choose Omnara if:**
@@ -79,7 +79,7 @@ These startups will pivot. They always do. Today's "free tier" becomes tomorrow'
 - **Infrastructure**: Terragon runs on cloud VMs. Happy uses your machines.
 - **Pricing**: Currently free during beta, but at a bare minimum will charge for
 VM usage at those high retail cloud prices. Expect dollars per hour. Happy is
-free forever.
+free.
 - **Complexity**: Terragon has dashboards, analytics, team management. Happy is simple.
 - **Lock-in**: Terragon wants to own your workflow. Happy works with what you have.
 - **Scope**: Terragon tries to do everything. Happy does one thing well.
@@ -220,7 +220,7 @@ Let's talk about the elephant in the room: sustainability.
 **Happy Coder:**
 - No VC funding
 - No burn rate
-- Open source forever
+- Permissive open source
 - Self-hostable
 - Can't rugpull you
 - Community-driven
@@ -231,7 +231,7 @@ This matters more than you think.
 
 ### Who Can See Your Code?
 
-**Happy Coder**: Nobody. End-to-end encrypted. The relay server only sees encrypted blobs.
+**Happy Coder**: Nobody. End-to-end encrypted. The free community relay server only sees encrypted blobs.
 
 **Local Execution** (Omnara, ClaudeCodeUI): 
 - Code execution happens on your machine
@@ -261,34 +261,21 @@ This matters more than you think.
 **Local Execution** (Omnara, ClaudeCodeUI):
 - Code runs on your machine, but servers store plain text conversations
 - Their employees can read your code and conversations
-- Self-hosting option available - solves privacy if you host your own server
+- Self-hosting option available. Solves privacy if you host your own server
 - You control retention only if self-hosted
 
 **Cloud VM Providers** (Terragon, Cursor):
 - They control retention
 - Backups you can't delete
 - Data might persist after account deletion
 
-## Performance Comparison
-
-Real-world latency numbers:
-
-| Solution | Latency | Why |
-|----------|---------|-----|
-| Happy Coder | ~300ms | Direct connection to your machine |
-| Cloud Providers | 500-2000ms | VM spin-up + network hops |
-| SSH + tmux | ~100ms | Direct but terrible UX on mobile |
-| Cursor Mobile | 400-1500ms | Depends on their infrastructure load |
-
-Happy Coder gives you near-native performance because Claude Code runs on your actual machine.
-
 ## Feature Comparison Deep Dive
 
 ### MCP Tools Support
 
 **Local Execution (Happy Coder, Omnara, ClaudeCodeUI)**: Full MCP support. Since agents run on your machine, all your local MCP tools work natively.
 
-**Cloud VM Execution (Terragon, Cursor)**: Limited MCP support. Since agents run on their cloud VMs, they can't access your local MCP tools without complex setup.
+**Cloud VM Execution (Terragon, Cursor)**: Extra work to get MCP working. Since agents run on their cloud VMs, they can't access your local MCP tools. You have to set up MCP tools all over again.
 
 ### Custom Agents
 
@@ -302,12 +289,6 @@ Happy Coder gives you near-native performance because Claude Code runs on your a
 
 **Others**: Not available.
 
-### Session Persistence
-
-**Happy Coder**: Sessions persist on your machine. Pick up exactly where you left off.
-
-**Others**: Sessions die when VMs shut down. Context lost.
-
 ## The Bottom Line
 
 ### Choose Happy Coder When:
@@ -330,7 +311,7 @@ Coming from another solution? Here's how to switch:
 
 ### From Cloud Providers
 1. Install Happy Coder: `npm install -g happy-coder`
-2. No migration needed - your code is already on your machine
+2. No migration needed. Your code is already on your machine
 3. Start using Happy immediately
 
 ### From SSH + tmux

content/comparisons/alternatives.mdx

@@ -153,13 +153,3 @@ include session status updates, completion alerts, error notifications, and inpu
 - Text-to-speech (TTS) with Eleven Labs
 - Conversation state management with its own context independent of claude code session.
 - Agentic assistant (Claude Sonnet 4) that can send messages to claude code and has some special prompts to get better results in turning rubber duck style stream of conciousness planning into a concrete request for claude code to execute.
-
-## Productivity Enhancement Features
-
-### 10. Pre-Sleep Task Seeding
-
-> **User Story**: As a developer, I've always heard about the productivity hack of leaving something unfinished to start the next morning, but it never worked for me because setting up a meaningful task took 10-20 minutes - too long to be spontaneous, especially when I'd already overstayed at the office to finish something and didn't want to spend another 20 minutes setting myself up for tomorrow. 
->
-> With Claude Code and MCP tools for JIRA or Linear, I can now sit in bed and instead of scrolling Reddit or Instagram, I run a custom bedtime agent slash command where I've already set up my `~/.claude/agents/bedtime.md` to describe the process of finding something simple that I can start tonight and finish tomorrow. I describe a feature I want or a problem I'm thinking about, then work back and forth with Claude in planning mode for about 5 minutes to develop an implementation plan I like. When I approve the plan, Claude gets to work while I put my phone on the charger. 
->
-> When I wake up, I have a notification from Claude Code "4 files to review, 237 lines of code added" - something nice and small to start my day. Having Claude Code on my phone is key because previously, to leave something unfinished for the next day, I had to be in programmer brain and actually make code changes myself. Now I can do this setup at any point in the evening - the task shrunk from 20 minutes of focused programming work down to a 5-minute conversational planning session. Having Claude Code accessible from my phone dramatically increased the surface area of opportunities when this routine could actually happen, making it way more likely to become a consistent habit.

content/features/index.mdx

@@ -0,0 +1,9 @@
+export default {
+    "watching-tv": {
+      title: 'Watching TV',
+      theme: {
+        typesetting: 'article'
+      }
+    },
+  }
+