weiqingy commented on code in PR #1018:
URL: https://github.com/apache/flink-agents/pull/1018#discussion_r3801207448


##########
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:
   Good catch. Went with the `uname -m` route since it turned out to be about 
six lines, so the script now picks `Linux-64bit` or `linux-arm64` and fails 
with the architecture name rather than quietly installing the wrong binary. 
README note updated to match.



##########
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:
   Agreed, that's more accurate. Taken your wording.



-- 
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]

Reply via email to