Skip to content

Conversation

@john-mutuma
Copy link
Owner

What does this PR do?

This PR implements a comprehensive documentation overhaul with two major improvements: (1) restructuring documentation into specialized files with clear separation of concerns, and (2) modernizing the terminal workflow by positioning Ghostty as the recommended terminal for local development.

Documentation Restructuring

  • Created specialized documentation files: ARCHITECTURE.md (782 lines), FAQ.md (501 lines), TROUBLESHOOTING.md (1012 lines), and CONTRIBUTING.md (675 lines)
  • Restructured README.md (~400 lines) to focus on user-facing quick start and essential workflows
  • Moved technical deep-dives, complete plugin ecosystem, and comprehensive keybinding references to ARCHITECTURE.md
  • Organized troubleshooting by category (installation, plugins, LSP, AI, git, UI, performance, keybindings, terminal)
  • Added comprehensive FAQ covering 31+ common questions across 7 categories

Ghostty Terminal Integration

  • Positioned Ghostty as the recommended terminal for local development (GPU-accelerated, native splits/tabs)
  • Added comprehensive Ghostty setup guide with tmux-like keybindings (Ctrl+b prefix)
  • Relegated tmux to legacy/remote-only use cases with clear guidance
  • Included Ghostty vs tmux comparison table across 6 feature categories
  • Updated all documentation (README, ARCHITECTURE, FAQ, TROUBLESHOOTING) for consistency

Changes Made

  • README.md: User-focused quick start guide (+92, -26 lines)
  • doc/ARCHITECTURE.md: Technical reference with terminal comparison (+782 lines, new file)
  • doc/FAQ.md: 31+ Q&As across 7 categories (+501 lines, new file)
  • doc/TROUBLESHOOTING.md: Categorized issue resolution (+1012 lines, new file)
  • doc/CONTRIBUTING.md: Contribution guidelines (+675 lines, new file)
  • AGENTS.md: Session history documentation (+222 lines)

Why is it needed?

Documentation Issues:

  • Previous README was overly technical (~1500 lines) mixing user guides with deep technical details
  • New users struggled to quickly understand installation and get started
  • Troubleshooting and FAQ content was scattered throughout
  • No clear separation between user-facing and developer-facing content

Terminal Workflow Issues:

  • tmux positioned as default added complexity for simple local development
  • Modern alternatives like Ghostty offer better performance with native features
  • Users had to learn tmux complexity even when not needed
  • Documentation did not clarify when to use tmux vs modern terminals

How have the changes been tested?

  • All markdown files validated for formatting and links
  • Documentation structure reviewed for logical organization
  • Cross-references between documents verified
  • Keybinding references tested for accuracy
  • Ghostty configuration tested with tmux-like keybindings
  • Installation steps verified on macOS

Screenshots (if applicable)

N/A - Documentation changes only

Checklist

  • Documentation restructured into specialized files (ARCHITECTURE, FAQ, TROUBLESHOOTING, CONTRIBUTING)
  • README.md streamlined to focus on user quick start (~400 lines)
  • Ghostty positioned as recommended terminal with comprehensive setup guide
  • tmux relegated to legacy/remote workflows with clear guidance
  • Ghostty vs tmux comparison table added to ARCHITECTURE.md
  • All 4 doc files updated consistently for Ghostty prioritization
  • Troubleshooting sections added for Ghostty (3 new sections)
  • FAQ updated with Ghostty workflows and terminal choice guidance
  • AGENTS.md updated with session summaries
  • All cross-references between documents validated
  • Git history preserved with meaningful commit messages

John Mutuma added 8 commits October 31, 2025 18:56
…in ecosystem

- Add complete keybinding reference section with 70+ mappings organized into 8 categories
- Add plugin ecosystem section documenting all 70+ plugins across 11 functional categories
- Remove duplicate Essential Shortcuts section (51 lines)
- Remove nvim-ide references from keybinding tables (plugin no longer in config)
- Improve navigation with detailed mode, description, and plugin attribution
- Organize AI tools (Avante, Copilot, OpenCode) with usage examples and key features
- Streamline README to ~400 lines (user-focused)
- Create ARCHITECTURE.md for technical details (664 lines)
- Create TROUBLESHOOTING.md for issue resolution (922 lines)
- Create FAQ.md with 40+ common Q&As (479 lines)
- Update CONTRIBUTING.md cross-references
- Update AGENTS.md with restructuring details
- Move TROUBLESHOOTING.md to doc/ directory (completes doc restructuring)
- Update all README.md references to point to doc/ directory
- All documentation now organized in doc/ directory:
  - ARCHITECTURE.md
  - CONTRIBUTING.md
  - FAQ.md
  - TROUBLESHOOTING.md
- Update entry status from 'pending commit' to completed with commit hashes
- Add doc/ prefix to all file paths in Files Modified/Created section
- Add 'Organized doc/ directory' to Changes Made
- Update file sizes to match actual committed files
- Add 'Moved all documentation files to doc/ directory' to changes
- Position Ghostty as recommended terminal throughout all documentation
- Relegate tmux to legacy/remote-only use case with clear guidance
- Add comprehensive Ghostty setup, keybindings, and troubleshooting docs
- Include Ghostty vs tmux comparison table in ARCHITECTURE.md
- Update FAQ with Ghostty workflows and terminal choice guidance
- Add dedicated Ghostty troubleshooting section with config and split issues
- Update README prerequisites, installation, quick start, and post-install setup
- Maintain backward compatibility by keeping tmux documentation
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.

2 participants