Skip to content

Conversation

@jackspirou
Copy link
Member

Summary

This PR implements a comprehensive documentation refactor to reposition Pocket as a graph execution engine for LLM workflows, with the CLI as the primary use case and the Go library as secondary.

Key Changes

🎯 Documentation Restructuring

  • CLI-first approach: Reorganized all documentation to prioritize the CLI binary use case
  • Clear positioning: Consistent messaging as a "graph execution engine" throughout
  • Language-agnostic: Emphasized plugin support for Lua, WebAssembly, and Native Go
  • Fixed API examples: Updated all code samples to use the new pocket.Steps{} struct pattern

📁 New Documentation Structure

docs/
├── README.md                 # Documentation hub
├── cli/                      # Primary use case (NEW)
│   ├── getting-started.md
│   ├── installation.md
│   ├── configuration.md
│   ├── plugins.md
│   └── troubleshooting.md
├── library/                  # Secondary use case (reorganized)
│   ├── getting-started.md
│   ├── embedding.md
│   └── api-reference.md
├── workflows/                # Comprehensive examples
│   ├── basic/
│   ├── advanced/
│   └── real-world/
└── concepts/                 # Core concepts (updated)

🚀 Release Automation

  • GoReleaser integration: Multi-platform binary builds (8 OS/arch combinations)
  • Homebrew support:
    • Pre-built binaries (bottles) by default
    • Source builds with --build-from-source flag
  • Automated workflow: GitHub Actions for testing, building, and releasing
  • Security: SHA256 checksums for all releases

📦 Installation Methods

  1. Homebrew (recommended): brew install agentstation/tap/pocket
  2. Install script: curl -sSL .../install.sh | bash
  3. Go install: go install github.com/agentstation/pocket/cmd/pocket@latest
  4. Direct download: Pre-built binaries from releases page

Testing

The new release system includes:

  • Automated testing on all platforms before release
  • Verification of released binaries on multiple OS
  • Homebrew formula validation
  • Comprehensive test coverage

Migration Impact

Zero breaking changes - All existing code continues to work. The changes are purely organizational and additive.

Next Steps

After merging, we should:

  1. Update the repository description to: "Graph execution engine for LLM workflows"
  2. Update repository tags to include: cli, workflow-engine, llm, graph, yaml, lua, wasm
  3. Create a release to test the new automation

Related Documentation

This refactor positions Pocket alongside tools like kubectl, terraform, and docker - making it accessible to the broader developer community beyond just Go developers.

jackspirou and others added 3 commits July 22, 2025 12:16
- Rewrite main README.md to prioritize CLI usage
- Create dedicated /docs/cli/ directory with comprehensive CLI docs
- Create /docs/library/ for Go library documentation
- Create /docs/nodes/ for node type documentation
- Create /docs/workflows/ for example workflows
- Create /docs/development/ for contributors
- Position Pocket as a graph execution engine for LLM workflows

This restructuring makes the CLI the primary entry point while
maintaining excellent documentation for Go developers.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Major documentation overhaul to reposition Pocket as a graph execution engine
for LLM workflows, with CLI as the primary use case and Go library as secondary.

Documentation Changes:
- Restructured README.md with CLI-first approach
- Created comprehensive CLI documentation suite in docs/cli/
- Reorganized library docs to docs/library/ as secondary use case
- Added workflow examples organized by complexity (basic/advanced/real-world)
- Updated all concept docs to emphasize 'graph execution engine' positioning
- Fixed all API examples to use new Steps struct pattern
- Added language-agnostic plugin examples (Lua, WASM, Native)

Release System:
- Added GoReleaser configuration for multi-platform builds
- Set up automated release workflow with GitHub Actions
- Configured Homebrew formula with dual installation support:
  - Pre-built binaries (bottles) by default
  - Source builds with --build-from-source flag
- Added install.sh script for quick installation
- Created RELEASING.md with maintainer documentation

Key Features:
- Builds for 8 platform/architecture combinations
- SHA256 checksums for all releases
- Automatic Homebrew tap updates
- Comprehensive changelog generation
- Draft releases with proper versioning

This positions Pocket following best practices from tools like kubectl,
terraform, and docker, making it more accessible to the broader developer
community beyond just Go developers.
@codecov-commenter
Copy link

codecov-commenter commented Jul 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

❌ Your project status has failed because the head coverage (40.86%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #13   +/-   ##
=======================================
  Coverage   40.86%   40.86%           
=======================================
  Files          39       39           
  Lines        7393     7393           
=======================================
  Hits         3021     3021           
  Misses       4221     4221           
  Partials      151      151           
Flag Coverage Δ
unittests 40.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9efcdc1...54f72aa. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jackspirou jackspirou merged commit c298c1c into master Jul 22, 2025
5 checks passed
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.

3 participants