Leonid Ganeline e2d7677526 docs: compound ecosystem and integrations (#4870) ... # Docs: compound ecosystem and integrations **Problem statement:** We have a big overlap between the References/Integrations and Ecosystem/LongChain Ecosystem pages. It confuses users. It creates a situation when new integration is added only on one of these pages, which creates even more confusion. - removed References/Integrations page (but move all its information into the individual integration pages - in the next PR). - renamed Ecosystem/LongChain Ecosystem into Integrations/Integrations. I like the Ecosystem term. It is more generic and semantically richer than the Integration term. But it mentally overloads users. The `integration` term is more concrete. UPDATE: after discussion, the Ecosystem is the term. Ecosystem/Integrations is the page (in place of Ecosystem/LongChain Ecosystem). As a result, a user gets a single place to start with the individual integration.		2023-05-18 09:29:57 -07:00
..
agent_executors/examples	bump version to 173 (#4910)	2023-05-17 23:36:45 -07:00
agents	Typos (#4851)	2023-05-17 11:52:22 -04:00
toolkits/examples	Harrison/spark connect example (#4659)	2023-05-13 21:44:54 -07:00
tools	docs: compound ecosystem and integrations (#4870)	2023-05-18 09:29:57 -07:00
agent_executors.rst
agents.rst	agent docs (#2551)	2023-04-07 10:01:23 -07:00
getting_started.ipynb	Modify docs (#2539)	2023-04-07 07:21:38 -07:00
how_to_guides.rst
plan_and_execute.ipynb	Fix age inconsistency in plan and execute Jupyter notebook example (#4814)	2023-05-16 15:27:27 -07:00
toolkits.rst
tools.rst	tool validation logic	2023-04-17 21:59:32 -07:00