wenjin272 commented on code in PR #1018: URL: https://github.com/apache/flink-agents/pull/1018#discussion_r3795690703
########## docs/README.md: ########## @@ -22,12 +22,16 @@ $ docker run -v $(pwd):/src -p 1313:1313 jakejarvis/hugo-extended:latest server #### Local Hugo installation: -Make sure you have installed [Hugo](https://gohugo.io/getting-started/installing/) on your system. +`setup_hugo.sh` installs Hugo 0.110.0, the version the docs build is pinned to. A newer Hugo release removed an internal template the pinned `hugo-book` theme calls, so building with a current Hugo fails with `no such template "_internal/google_analytics_async.html"`. + +On Linux, install it with: Review Comment: Could we narrow this to Linux x86_64? `setup_hugo.sh` currently hard-codes the `Linux-64bit` artifact, while Hugo provides a separate `linux-arm64` package. As written, Linux ARM64 users would install an incompatible binary. Alternatively, the script could select the artifact based on `uname -m`. ########## docs/content/_index.md: ########## @@ -30,6 +30,18 @@ under the License. If you’re interested in playing around with Flink Agents, check out our [get started documentation]({{< ref "docs/get-started/overview" >}}). It provides a step by step introduction on how to install Flink Agents and build agents with it. +### Quickstart + +* [Workflow Agent]({{< ref "docs/get-started/quickstart/workflow_agent" >}}) - Define agent logic as an explicit event-driven workflow +* [ReAct Agent]({{< ref "docs/get-started/quickstart/react_agent" >}}) - Let the model plan and call tools in a reason-act loop +* [YAML Agent]({{< ref "docs/get-started/quickstart/yaml_agent" >}}) - Declare an agent without writing code Review Comment: Could we avoid saying “without writing code” here? The linked quickstart explains that action and tool implementations still need to live in Python or Java, while YAML only describes how those pieces are wired together. “Configure an agent declaratively in YAML” may be more accurate. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
