Skip to content

docs: Mirror "self-improving" tagline update from PraisonAI PR #1574 on docs landing pages #280

Description

@MervinPraison

Context

PraisonAI PR #1574 was merged into main (head SHA 641155d4c4d5233621bf42d83fe05cbcd3c2095d). It is a small, two-line marketing-copy edit that adds "self-improving" to the product tagline so the top-level positioning matches what src/praisonai-agents/README.md already advertises ("autonomous, self-improving agents").

Diff applied in PraisonAI:

- shipping autonomous agents that research, plan, and execute tasks across your apps
+ shipping autonomous, self-improving agents that research, plan, and execute tasks across your apps

Files changed:

  • README.md
  • src/praisonai/README.md

The docs site (MervinPraison/PraisonAIDocs) currently has its own landing-page taglines that describe agents as "autonomous" but never use "self-improving" as a top-level descriptor, even though the underlying capability is real and already documented (see issue #232docs/features/skill-manage.mdx). This issue brings the docs marketing copy into parity with the README so a visitor lands on the same positioning whether they arrive via GitHub or via the docs site.

Important

This is a content update only — no new pages are needed. The self-improving feature itself (skill_manage write API) already has dedicated documentation at docs/features/skill-manage.mdx. Per AGENTS.md, do NOT create or modify anything under docs/concepts/.


Triage: update vs. new content

Question Answer
Does PR #1574 add a new feature? No — it is a tagline-only README change.
Is the underlying capability ("self-improving" agents) already documented? Yes. docs/features/skill-manage.mdx (created via #232) plus existing reflection docs (docs/features/) cover it.
Are new docs pages needed? No.
Does any existing docs copy need to be updated? Yes — three landing pages and (optionally) one card.

Files to update

1. docs/index.mdx

Current hero subhead (line ~30 of file):

<p className="text-xl text-gray-600 dark:text-gray-400 mb-6 max-w-2xl mx-auto">
  Multi-agent teams that solve complex tasks, automate workflows, and deliver to Telegram, Discord, Slack — with low-code simplicity.
</p>

Change to:

<p className="text-xl text-gray-600 dark:text-gray-400 mb-6 max-w-2xl mx-auto">
  Self-improving multi-agent teams that solve complex tasks, automate workflows, and deliver to Telegram, Discord, Slack — with low-code simplicity.
</p>

Why: This is the very first line of marketing copy a visitor reads on the docs home page. Mirrors the README tagline shift verbatim in spirit (add the self-improving descriptor without rewording the rest).


2. docs/introduction.mdx

Current opening Card body (lines ~10–13):

<CardGroup cols={1}>
  <Card title="Welcome to PraisonAI" icon="wand-magic-sparkles">
    Build powerful autonomous agents that understand, decide, and execute with unprecedented capability.
  </Card>
</CardGroup>

Change to:

<CardGroup cols={1}>
  <Card title="Welcome to PraisonAI" icon="wand-magic-sparkles">
    Build powerful autonomous, self-improving agents that understand, decide, and execute with unprecedented capability.
  </Card>
</CardGroup>

Also update the "What is PraisonAI?" intro paragraph above it:

Current:

PraisonAI is a powerful Multi-Agent Framework for building and deploying AI agents that can understand, reason, and execute complex tasks autonomously.

Change to:

PraisonAI is a powerful Multi-Agent Framework for building and deploying autonomous, self-improving AI agents that can understand, reason, and execute complex tasks.

Why: Both edits use the exact autonomous, self-improving phrasing from the README diff, keeping cross-surface tagline consistency.


3. docs/home.mdx

Current hero text (line ~37):

<div className="text-lg text-gray-600 dark:text-gray-400 mb-8 max-w-3xl">
  Build production-ready AI agents that reason, remember, and act autonomously — with just a few lines of code.
</div>

Change to:

<div className="text-lg text-gray-600 dark:text-gray-400 mb-8 max-w-3xl">
  Build production-ready AI agents that reason, remember, self-improve, and act autonomously — with just a few lines of code.
</div>

Why: Fits the existing list pattern (reason, remember, act) by adding "self-improve" as a peer verb — communicates the same capability without breaking the rhythm of the sentence.


4. (Optional but recommended) docs/introduction.mdx — Key Features card

Existing card under "Key Features" already says "Autonomous Agents". Consider renaming to "Autonomous, Self-Improving Agents" so the headline aligns with the README:

Current:

<Card title="Autonomous Agents" icon="robot">
  - Understand natural language
  - Make decisions
  - Execute tasks
</Card>

Change to:

<Card title="Autonomous, Self-Improving Agents" icon="robot">
  - Understand natural language
  - Make decisions
  - Execute tasks
  - Learn and persist new skills
</Card>

The new bullet ("Learn and persist new skills") points at the real capability surfaced by docs/features/skill-manage.mdx and docs/features/autonomy-loop.mdx.


Files NOT to touch

  • docs/concepts/** — human-approved only per AGENTS.md.
  • docs/features/skill-manage.mdx — already documents the self-improving skill API.
  • docs/features/autonomy-loop.mdx — already documents the autonomy loop.
  • docs.json — no navigation changes are required; nothing is being added or moved.
  • docs/js/, docs/rust/ — auto-generated; out of scope.

Acceptance criteria

  • docs/index.mdx hero subhead includes "self-improving"
  • docs/introduction.mdx "What is PraisonAI?" paragraph and welcome Card include "autonomous, self-improving"
  • docs/home.mdx hero text includes "self-improve" in the verb list
  • (Optional) docs/introduction.mdx "Autonomous Agents" Card renamed and gains the "Learn and persist new skills" bullet
  • No files added or removed
  • No edits to docs/concepts/
  • docs.json not modified
  • Mintlify components remain valid (the changes are plain-text only inside existing JSX/MDX nodes)

Branch + PR for the follow-up agent

Per the standing instruction in this workspace, the follow-up agent should:

  1. Develop on branch claude/admiring-euler-WfsiD
  2. Push with git push -u origin claude/admiring-euler-WfsiD
  3. Open a draft PR linking back to this issue and to PraisonAI PR docs: cover standalone praisonai-code CLI + wrapper-bridge degradation model (PraisonAI PR #2547, C7 phase 1) #1574

References

Writing rules recap (from AGENTS.md)

  • Concise, active voice; no filler intros.
  • Don't add new pages — this is a wording-only update.
  • Don't touch docs/concepts/.
  • Preserve existing Mintlify component structure (<Card>, <CardGroup>, JSX <div>s, <p>s) — only edit the inner copy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    claudeTrigger Claude Code analysisdocumentationImprovements or additions to documentationenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions