Merge pull request #26 from Callgent/blog

Blog

docs/advanced-topics/callgent-endpoints/endpoints.md

@@ -5,15 +5,15 @@ Callgents endpoints are adaptors to collect callgent to external systems or user
 There are three types of endpoints:
 
 - [Server Endpoint](./server-endpoint)
-  Responsible for converting task into the encapsulated target system / user invocation, and updating task from invocation result.
+  Responsible for converting requests into the encapsulated target system invocation or user chatting, and retrieving invocation response.
 - [Client Endpoint](./client-endpoint)
-  Responsible for receiving requests into callgent task queue, and responding back to task owner when task has any progress.
+  Responsible for receiving requests into callgent task queue, and responding back to caller when task has any progress.
 - [Event Endpoint](./event-endpoint)
-  Responsible for listening to events from the encapsulated target system / user, and notifying registered event observers on callgent.
+  Responsible for listening to events from the encapsulated target system or user, and notifying registered event observers on callgent.
 
 ## Add a new endpoint to callgent
 
-When you want to collect your callgent to a new external system / user, you need to integrate them by adding a new endpoint.  
+When you want to connect your callgent to a new external system / user, you need to integrate them by adding a new endpoint.  
 You can add any number of endpoints to your callgent.
 
 ### choose a callgent

docs/advanced-topics/callgent-hub.md

@@ -54,9 +54,7 @@ You can add any server endpoint to your callgent. So that you can respond to the
 
 Your responses are automatically sent back to canny.io, to add comments or change status for the original interactions.
 
-拆分实现
-
 1. hub list/search
 2. pre-created callgent template
 3. creation/config process
-4. usage 跑通
+4. usage

docs/advanced-topics/event-driven-orchestration/orchestration.md

@@ -1,53 +1,2 @@
 # Event Driven Orchestration
 
-基于事件的callgent装配：
-
-1. resp事件：on-response, on-error
-   **flow方式**来编排，允许关键字：
-    默认正常resp才触发，允许加修饰语，
-    默认修饰语：when， then
-                 可以是if then, while, for.. case
-2. 非resp事件
-   1. server事件
-      登记哪个client的webhook entry订阅哪个types，必要的映射？etype，otype，data，toWhom?
-   2. action事件：pre-X, 
-      - 依然flow方式，when 上面加event定语
-      - 或者在端点上加，变成Callgent的一部分，
-        - c端点的action事件：挂载Callgent
-
-## 挂载法，和flow法
-
-在事件上挂Callgent指令，
-或者单独flow脚本，
-
-属于同一种，放在不同地方而已。
-
-### auth Callgent
-
-c端点，
-
-## 数据传输
-
-string or object
-
-来自不同client的数据，有不同的格式，如何做统一处理，
-特别是flow上，上一个事件的输出，接入下一个输入时，
-存在数据来源不同的问题，
-action事件来自client，resp事件来自server，
-也就是说Callgent接收的数据，可能是任意格式，
-理论上来说，数据来自哪个端点，该端点就负责数据解析，
-Callgent间传递的数据，要溯源，来自哪个端点，由他负责解析？
-
-还是说不解析？如何从数据包内，获取特定数据
-进来一个或回传一个数据包，我要获取特定值时，需要端点支持，
-抑或端点将数据转为标准格式：
-server响应交给client/next之前，先将数据正规化为json或string？
-按照下一个端点的entry签名做正规化！
-
-当前端点负责为下一个端点解包，
-c端点是已经上游准备好的数据，s端点是3口
-事件传给下个端点前，先弄清对方要什么，准备好了再给他，
-可能跨Callgent的端点
-
-1. callgents间传递，在系统内，
-2. 最后一个Callgent resp发回最初的cb，可以看做一个冒泡回传过程

docs/developers/guide.md

@@ -1,11 +1,13 @@
 ---
 sidebar_position: 1
+keywords: [callgent architecture explained, how callgent works, callgent system components, benefits of using callgent, how to connect services using callgent, asynchronous tasks with callgent, semantic invocation in callgent, diagram of callgent product architecture, callgent technology overview, explore callgent intelligent invocation, how callgent integrates into APIs, understanding callgent’s system flow, callgent adaptive communication methods, leveraging callgent for business efficiency, how callgent supports digital ecosystems, next-gen communication with callgent]
+description: Explore the innovative architecture of Callgent, where services and users are encapsulated behind callgents to seamlessly connect through web, chat, email, and APIs. Learn how semantic invocations enhance interactions.
 ---
 
 # Concepts and Architecture
 
 The core of the callgent architecture, is to encapsulate every **service** and **user** behind a `callgent`.  
-Then build various endpoints into third-party platforms, so that any users and services are naturally connected anywhere in their native ways: chatting, mail, APIs..  
+Then build various endpoints into third-party platforms, so that any users and services are naturally connected anywhere in their native ways: webpages, chatting, mail, APIs..  
 
 Above this, we add a layer of semantic invocations, empowered by large language models (LLMs), to make the callgent able to understand and react to any user/system's intents.
 
@@ -25,7 +27,7 @@ Each system service, and every user is encapsulated into a `Callgent`.
 
 ### Calling Anywhere
 
-Requesting a callgent is done through various `Calling Endpoint`, integrated into third-party platforms. So systems and users are naturally connected anywhere in their native ways: chatting, mail, APIs..
+Requesting a callgent is done through various `Calling Endpoint`, integrated into third-party platforms. So systems and users are naturally connected anywhere in their native ways: Webpages, chatting, mail, APIs..
 
 #### User-as-a-Service
 

docusaurus.config.ts

@@ -4,7 +4,8 @@ import "dotenv/config";
 import { themes as prismThemes } from "prism-react-renderer";
 
 const config: Config = {
-  title: "Callgent",
+  title: "Service as a Callgent",
+  titleDelimiter: '-',
   tagline: "Service as a Callable Agent <br/> Break the silos among Users & Systems",
   favicon: "img/favicon.ico",