Skip to content

docs: gitbooks v3 — flatten frontend/tauri-shell, kill product/, fix links, default app env to production#1385

Merged
senamakel merged 7 commits into
tinyhumansai:mainfrom
senamakel:docs/flatten-frontend-tauri-shell
May 9, 2026
Merged

docs: gitbooks v3 — flatten frontend/tauri-shell, kill product/, fix links, default app env to production#1385
senamakel merged 7 commits into
tinyhumansai:mainfrom
senamakel:docs/flatten-frontend-tauri-shell

Conversation

@senamakel
Copy link
Copy Markdown
Member

@senamakel senamakel commented May 9, 2026

Summary

  • Drop the Use Cases section. The pages were thin and duplicated framing already covered in the feature pages and Welcome doc. Delete gitbooks/use-cases/ entirely.
  • Default OPENHUMAN_APP_ENV to production in .env.example. The runtime code already defaults to production; only the example envs were nudging contributors to staging. Comment those lines + BACKEND_URL / VITE_BACKEND_URL so a fresh .env resolves to production. Also fix the cloud-deploy doc that incorrectly said "Defaults to staging".
  • Flatten developing/frontend/ and developing/tauri-shell/ into single pages. The chapter-per-file structure made the sidebar long and hard to scan. Concatenate each set into developing/frontend.md (architecture / state / services / providers / pages & routing / components / hooks) and developing/tauri-shell.md (architecture / IPC commands / core bridge). Strip per-chapter "Previous / Next" footers and rewire internal cross-links.
  • Consolidate gitbooks/product/ into gitbooks/features/. Skills & Integrations + Messaging Channels merge into features/integrations.md (new "How connections work", "Messaging channels", "Skills" sections). Intelligence merges into features/obsidian-wiki/memory-tree.md (new "In the desktop app — the Intelligence tab" section). architecture.md, platform.md, privacy-and-security.md, subconscious.md move to features/. cloud-deploy.md moves back to developing/ (it was always a contributor doc). The product/ directory is removed entirely.
  • Fix broken links. Repoint repo-root references that go up one level too few from inside gitbooks/developing/ (../docs → ../../docs, ../.do → ../../.do, ../.github → ../../.github, ../src → ../../src, ../docker-compose.yml → ../../docker-compose.yml). Repoint cross-links that survived the frontend/tauri-shell flattening (../frontend/services.md → frontend.md#services-layer, ../ARCHITECTURE.md → architecture.md, ../src-tauri/01-architecture.md → tauri-shell.md). Strip dead /broken/pages/<id> placeholders for since-deleted pages.
  • Reduce em-dashes 311 → 61 across prose (skips code fences, tables, frontmatter, headings, horizontal rules), and clean up .gitbook/assets/ (drop 31 unused images, compress the remaining 5 with pngquant, normalize a U+202F filename — directory shrunk 34M → 2.6M). Refresh README hero image, drop the duplicate "highlights" section in favor of links inline in "What is OpenHuman".

Problem

  • The Use Cases pages had drifted out of date and didn't add anything the feature pages weren't already saying.
  • .env.example told new contributors to use staging, even though the runtime code defaults to production.
  • The developing/frontend/ and developing/tauri-shell/ chapter directories made the sidebar noisy and the navigation circuitous.
  • The product/ section overlapped heavily with features/ (Skills & Integrations duplicating Integrations, Intelligence duplicating Memory Tree UI, Messaging Channels being a paragraph that fits inside Integrations).
  • Migrations across recent PRs left behind 30 broken in-gitbooks links and several /broken/pages/<id> placeholders from the GitBook UI when files were renamed.
  • Asset directory had ballooned to 34 MB with unused images.

Solution

  • Pure docs change. The only non-doc edits are reference updates inside doc comments (one Rust file, the deploy workflow, .do/app.yaml, the PR template, source-code comments referencing moved paths) plus the .env.example defaults.
  • Stays scoped to documentation and config-example files; no runtime code changes.

Submission Checklist

  • N/A: docs / env-example only, no runtime behaviour to test.
  • N/A: docs-only change, no covered code lines.
  • N/A: docs-only change, coverage matrix unchanged.
  • N/A: docs-only change, no feature IDs touched.
  • N/A: docs-only change, no new network deps.
  • N/A: docs-only change, release smoke unchanged.
  • N/A: no linked issue.

Impact

  • Runtime / platform impact: none.
  • Pre-push hook flagged a pre-existing TypeScript breakage on main in app/src/features/human/Mascot/yellow/MascotCharacter.tsx (Cannot find module '@remotion/zod-types' / 'remotion'), unchanged on this branch. Pushed with --no-verify per the project's pre-push policy in CLAUDE.md.

Related

  • Closes:
  • Follow-up PR(s)/TODOs: none.

AI Authored PR Metadata (required for Codex/Linear PRs)

Linear Issue

  • Key: N/A
  • URL: N/A

Commit & Branch

  • Branch: docs/flatten-frontend-tauri-shell
  • Commit SHA: latest on branch.

Validation Run

  • pnpm --filter openhuman-app format:check
  • N/A: pnpm typecheck — pre-existing breakage on main, untouched in this PR.
  • N/A: docs-only, no focused tests.
  • cargo fmt --manifest-path Cargo.toml --all --check
  • cargo fmt --manifest-path app/src-tauri/Cargo.toml --all --check

Validation Blocked

  • command: pnpm compile
  • error: Cannot find module '@remotion/zod-types' or its corresponding type declarations. in app/src/features/human/Mascot/yellow/MascotCharacter.tsx
  • impact: Pre-existing on main. No code in this PR touches that file or its imports.

Behavior Changes

  • Intended behavior change: none — docs only.
  • User-visible effect: cleaner gitbook site (fewer pages, no broken links), .env.example resolves to production by default.

Parity Contract

  • Legacy behavior preserved: yes — no runtime code changed.
  • Guard/fallback/dispatch parity checks: N/A.

Duplicate / Superseded PR Handling

  • Duplicate PR(s): none.
  • Canonical PR: this one.
  • Resolution: N/A.

Summary by CodeRabbit

  • Documentation
    • Reorganized GitBook documentation structure: consolidated frontend and Tauri shell guides into single reference pages.
    • Simplified table of contents by removing separate "Use Cases" and "Product" sections.
    • Updated internal links and restructured developer/feature documentation for clarity.
    • Revised environment configuration guidance in .env.example files, marking optional variables as commented examples with clear defaults documented.

senamakel added 7 commits May 8, 2026 21:54
The runtime code (src/main.rs::resolve_environment, app/src-tauri's
resolve_sentry_environment, cef_profile::default_root_dir_name,
app/src/utils/config.ts) already treats production as the default
when OPENHUMAN_APP_ENV is unset — the only thing pointing new
contributors at staging was .env.example itself.

Comment out OPENHUMAN_APP_ENV / VITE_OPENHUMAN_APP_ENV / BACKEND_URL
/ VITE_BACKEND_URL in .env.example and app/.env.example so a fresh
copy of the example file resolves to production through the runtime
defaults. Uncomment + set staging only when you actually want the
staging backend.

Also fix gitbooks/developing/cloud-deploy.md which incorrectly
documented the default as 'staging'.
The Use Cases pages were thin and duplicated framing already
covered by the feature pages and the Welcome doc. Remove the
directory and the matching SUMMARY.md section.
The chapter-per-file structure under gitbooks/developing/frontend/
and gitbooks/developing/tauri-shell/ was hard to scan and made the
sidebar long. Concatenate each set into one consolidated page with
each former chapter as a top-level section:

- gitbooks/developing/frontend.md  (architecture, state, services,
  providers, pages & routing, components, hooks & utilities)
- gitbooks/developing/tauri-shell.md  (architecture, IPC commands,
  core bridge & helpers)

Strip the per-chapter "Previous / Next" navigation footers since
they no longer make sense, and rewire the few cross-links that
pointed at the old chapter paths.

Update SUMMARY.md, CLAUDE.md, AGENTS.md, and .claude/rules/README.md
to point at the new flat paths.
The Product section duplicated framing already covered by feature
pages — Skills & Integrations re-explained third-party
integrations, Intelligence re-explained the Memory Tree UI,
Messaging Channels was a paragraph that fits inside the
integrations doc, and Cloud Deploy / Subconscious / Architecture
had drifted between Product and Developing.

Net moves:

- features/integrations.md absorbs skills-and-integrations.md and
  messaging-channels.md (new "Messaging channels" + "Skills" +
  "Native voice and tools" sections + a "How connections work"
  status table).
- features/obsidian-wiki/memory-tree.md absorbs intelligence.md
  (new "In the desktop app — the Intelligence tab" section).
- product/architecture.md, platform.md, privacy-and-security.md,
  subconscious.md  -> features/.
- product/cloud-deploy.md -> developing/cloud-deploy.md (it was
  always a contributor doc).
- product/intelligence.md, messaging-channels.md, skills-and-
  integrations.md deleted (content merged).
- gitbooks/product/ directory removed entirely.

Update SUMMARY.md (drop Product section, fold pages into
Features and Developing), README.md (rewire the messaging-
channels / privacy & security links), gitbooks/README.md, the
overview/getting-started + overview/how-it-works cross-links,
and developing/README.md (point Subconscious + high-level
Architecture at the new locations).
…ce em-dashes

- Repoint repo-root references that go up one level too few from
  inside gitbooks/developing/ (../docs -> ../../docs, ../.do ->
  ../../.do, ../.github -> ../../.github, ../src -> ../../src,
  ../docker-compose.yml -> ../../docker-compose.yml).
- Repoint cross-links that survived the frontend/tauri-shell
  flattening: ../frontend/services.md -> frontend.md#services-layer,
  ../ARCHITECTURE.md -> architecture.md, ../src-tauri/01-architecture.md
  -> tauri-shell.md.
- Strip /broken/pages/<id> placeholders that the GitBook UI left
  behind for since-deleted pages (Skills, Conscious Loop, Webview
  Integration, Memory Context Window, Install, Auto-update).
- Drop the SKILL-WORKING-MEMORY paragraph in developing/architecture.md
  (target file deleted).
- Delete duplicate gitbooks/overview/platform.md (only
  features/platform.md is in SUMMARY).
- Reduce em-dashes 311 -> 61 across prose (skip code fences,
  tables, frontmatter, headings, horizontal rules).

After this pass, gitbooks/ has 0 broken internal links and 0
stale GitHub blob/tree links.
…ve content clarity

- Replaced outdated images in README.md and gitbooks/README.md with a new demo image.
- Reformatted the product comparison table for better readability.
- Removed several obsolete screenshot files to streamline assets.
@senamakel senamakel requested a review from a team May 9, 2026 05:27
@senamakel senamakel merged commit 0a92015 into tinyhumansai:main May 9, 2026
16 of 17 checks passed
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 9, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0f2e50b2-f260-4f43-ad5a-0be6f87d1f84

📥 Commits

Reviewing files that changed from the base of the PR and between 2b6c455 and 746a8e3.

⛔ Files ignored due to path filters (5)
  • gitbooks/.gitbook/assets/Screenshot 2025-12-13 at 1.32.35 PM.png is excluded by !**/*.png
  • gitbooks/.gitbook/assets/Screenshot 2026-05-08 at 9.37.23 PM.png is excluded by !**/*.png
  • gitbooks/.gitbook/assets/Screenshot 2026-05-08 at 9.39.01 PM.png is excluded by !**/*.png
  • gitbooks/.gitbook/assets/Screenshot 2026-05-08 at 9.39.39 PM.png is excluded by !**/*.png
  • gitbooks/.gitbook/assets/demo.png is excluded by !**/*.png
📒 Files selected for processing (60)
  • .claude/rules/README.md
  • .env.example
  • AGENTS.md
  • CLAUDE.md
  • README.md
  • app/.env.example
  • gitbooks/README.md
  • gitbooks/SUMMARY.md
  • gitbooks/developing/README.md
  • gitbooks/developing/agent-observability.md
  • gitbooks/developing/architecture.md
  • gitbooks/developing/cef.md
  • gitbooks/developing/cloud-deploy.md
  • gitbooks/developing/coding-harness.md
  • gitbooks/developing/e2e-testing.md
  • gitbooks/developing/frontend.md
  • gitbooks/developing/frontend/README.md
  • gitbooks/developing/frontend/architecture.md
  • gitbooks/developing/frontend/components.md
  • gitbooks/developing/frontend/hooks-utils.md
  • gitbooks/developing/frontend/pages-routing.md
  • gitbooks/developing/frontend/providers.md
  • gitbooks/developing/frontend/services.md
  • gitbooks/developing/frontend/state-management.md
  • gitbooks/developing/getting-set-up.md
  • gitbooks/developing/release-policy.md
  • gitbooks/developing/tauri-shell.md
  • gitbooks/developing/tauri-shell/README.md
  • gitbooks/developing/tauri-shell/architecture.md
  • gitbooks/developing/tauri-shell/commands.md
  • gitbooks/developing/tauri-shell/core-bridge.md
  • gitbooks/developing/testing-strategy.md
  • gitbooks/features/architecture.md
  • gitbooks/features/auto-fetch.md
  • gitbooks/features/integrations.md
  • gitbooks/features/local-ai.md
  • gitbooks/features/model-routing.md
  • gitbooks/features/native-tools.md
  • gitbooks/features/obsidian-wiki/README.md
  • gitbooks/features/obsidian-wiki/memory-tree-pipeline.md
  • gitbooks/features/obsidian-wiki/memory-tree.md
  • gitbooks/features/platform.md
  • gitbooks/features/privacy-and-security.md
  • gitbooks/features/subconscious.md
  • gitbooks/features/token-compression.md
  • gitbooks/features/voice.md
  • gitbooks/overview/getting-started.md
  • gitbooks/overview/how-it-works.md
  • gitbooks/overview/platform.md
  • gitbooks/product/intelligence.md
  • gitbooks/product/messaging-channels.md
  • gitbooks/product/skills-and-integrations.md
  • gitbooks/use-cases/community-managers-and-moderators.md
  • gitbooks/use-cases/dao-and-web3-communities.md
  • gitbooks/use-cases/distributed-teams.md
  • gitbooks/use-cases/individual-power-users.md
  • gitbooks/use-cases/knowledge-workers.md
  • gitbooks/use-cases/overview.md
  • gitbooks/use-cases/service-providers-and-contributors.md
  • gitbooks/use-cases/traders-and-analysts.md

📝 Walkthrough

Walkthrough

This PR consolidates GitBook documentation by merging fragmented frontend and Tauri shell docs into single comprehensive reference pages, restructures the table of contents by removing Product and Use Cases sections, updates environment variable guidance to make values optional with documented defaults, and applies minor wording refinements across feature documentation.

Changes

Documentation Consolidation & Restructuring

Layer / File(s) Summary
Documentation Consolidation
gitbooks/developing/frontend.md, gitbooks/developing/tauri-shell.md
Two new comprehensive markdown files consolidate previously distributed documentation: frontend.md (2,301 lines) covers React 19 + Vite architecture, Redux state, services layer, routing, components, hooks, and utilities; tauri-shell.md (211 lines) documents desktop host responsibilities, sidecar lifecycle, IPC command surface, and core process bridging.
Removal of Nested Doc Structure
gitbooks/developing/frontend/*.md, gitbooks/developing/tauri-shell/*.md
Deleted 8 frontend sub-pages (README.md, architecture.md, components.md, hooks-utils.md, pages-routing.md, providers.md, services.md, state-management.md) and 4 Tauri sub-pages (README.md, architecture.md, commands.md, core-bridge.md) that are now consolidated into parent-level pages.
Removal of Product & Use Cases
gitbooks/product/, gitbooks/use-cases/
Deleted entire Product section (intelligence.md, messaging-channels.md, skills-and-integrations.md) and Use Cases section (overview and 6 use-case pages: individual-power-users, traders-and-analysts, dao-and-web3, community-managers, distributed-teams, knowledge-workers, service-providers) from the documentation structure.
GitBook TOC Restructuring
gitbooks/SUMMARY.md
Reorganized table of contents: removed top-level Product and Use Cases sections; consolidated Developing section by replacing multi-page frontend/* and tauri-shell/* subsections with single entries; restructured Features section to surface additional topics (memory tree, subconscious loop, privacy & security, platform & availability, architecture).
Link Path Updates
.claude/rules/README.md, AGENTS.md, CLAUDE.md, gitbooks/developing/README.md, gitbooks/developing/*.md, gitbooks/features/*.md, gitbooks/overview/*.md
Updated internal documentation links throughout to point to new consolidated page locations (e.g., developing/frontend/README.mddeveloping/frontend.md, developing/tauri-shell/commands.mddeveloping/tauri-shell.md, product/privacy-and-security.mdfeatures/privacy-and-security.md).
Environment Variable Guidance
.env.example, app/.env.example
Made VITE_OPENHUMAN_APP_ENV and VITE_BACKEND_URL optional via commented examples with documented defaults (production env and https://api.tinyhumans.ai respectively); updated root .env.example to introduce separate "App environment selector" section and clarify that Vite variables mirror the main OPENHUMAN_APP_ENV setting.
Minor Content Refinements
README.md, gitbooks/README.md, gitbooks/developing/*.md, gitbooks/features/*.md, gitbooks/overview/*.md
Applied punctuation, wording, and formatting improvements across feature documentation, overview pages, and contributor guides; updated hero image asset reference; adjusted feature bullet phrasing in README; refined descriptions in architecture, auto-fetch, integrations, local-ai, model-routing, memory-tree, privacy-and-security, and other feature pages without changing functional content.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

  • tinyhumansai/openhuman#925: Adds Vite envDir configuration to load .env files from repo root, complementing this PR's clarification of optional VITE_* variables in app/.env.example.

Poem

📚 The docs once scattered now stand tall,
nested folders neatly merged into one,
paths redirected, links rewoven clean—
a rabbit's warren of knowledge, now serene!
Use Cases fade as Features bloom bright,
the GitBook garden springs into light. 🐰✨

AusAgentSmith pushed a commit to AusAgentSmith/openhuman that referenced this pull request May 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant