Define skeleton of docs

[tomkis]

Define skeleton (for example as mindmap) of what has to be documented.

Draw inspiration from provided sources.

Content requirements ideas

Here are some of ideas for content requirements

• How to install platform
• How to use platform
• How to wrap agent - this will be very simplistic as the concept of providers will likely change
• How to contribute (draw inspiration from MCP)

IA: https://app.mural.co/t/ibmresearchdesign6459/m/ibmresearchdesign6459/1739817117981/967e9f0a46b38c169feef03ba9a8c5a04d961206?sender=ubf66640e3eb42e4863417297

Inspirations

• https://modelcontextprotocol.io/introduction
• https://mastra.ai/docs
• https://agentprotocol.ai/
• https://whitepaper.actor/
• https://docs.agentops.ai/v1/introduction
• https://docs.lovable.dev/introduction
• https://awslabs.github.io/multi-agent-orchestrator/general/how-it-works/
• https://fetch.ai/docs
• https://docs.dagger.io/

[matoushavlena]

Proposal:

• Introduction

  • 🚧 Quickstart
  • 🚧 Installation
  • Changelog
  • Tutorials (overlaps with How to Guides)
  • Roadmap
  • FAQ

• How to Guides

  • ❗ Use agents
    • CLI, UI, REST, Python, TypeScript, import from github?
    • inference setup / model management
    • env setup / config
  • Compose agents
  • ❗ Contribute / create agents
    • Python, TS, docker
    • Add custom provider
    • Agent implementation
    • Progress notification / streaming
    • Debug

• Agent library

  • ✅ Official
  • ✅ Community

• Concepts

  • ❗ Overall architecture
    • CLI, server, UI, diagram
  • ❗ Agents
    • Agent types (chat, hands-off, custom, schemas)
  • ❗ Providers (Radek)
    • Manifest, Managed/Unmanaged, Lifecycle, Regsitry
  • Tools

• ✅ Agent Communication Protocol

  • ...
  • SDK

• Telemetry / Observability

  • Telemetry