Update links and favicon

Update links and favicon

Author: h3xxit

_config.yml

@@ -16,11 +16,14 @@ versions:
 
 url: https://utcp.io
 
+# For version-specific builds, set the appropriate baseurl
+# For example, when building the v0.1 version: baseurl: "/v0.1"
+
 # Set a path/url to a logo that will be displayed instead of the title
 # logo: "/assets/images/utcp-logo.png"
 
 # Set the path to the favicon
-favicon_ico: "assets/images/black-logo-square.png"
+favicon_ico: "/assets/images/black-logo-square.ico"
 
 # Color scheme supports "light" (default) and "dark"
 color_scheme: black

_includes/favicon.html

@@ -0,0 +1 @@
+<link rel="icon" href="{{ site.favicon_ico | relative_url }}" type="image/x-icon">

assets/images/black-logo-square.ico

@@ -285,6 +285,6 @@ await client.deregister_tool_provider("weather_api")
 
 The `UtcpClient` is designed to be extensible. For advanced use cases, you can replace its core components with your own custom implementations.
 
--   **Custom Tool Repositories**: By default, the client stores tools in memory. If you need to persist discovered tools in a database or a file-based cache, you can implement a custom `ToolRepository`. Learn more in the [Tool Repositories](./client/tool-repository.md) guide.
+-   **Custom Tool Repositories**: By default, the client stores tools in memory. If you need to persist discovered tools in a database or a file-based cache, you can implement a custom `ToolRepository`. Learn more in the [Tool Repositories](./client/tool-repository) guide.
 
--   **Custom Tool Search Strategies**: The default search strategy uses tag and description matching. If you need more sophisticated search capabilities, such as semantic search or integration with a vector database, you can implement a custom `ToolSearchStrategy`. Learn more in the [Tool Search Strategies](./client/tool-search-strategy.md) guide.
+-   **Custom Tool Search Strategies**: The default search strategy uses tag and description matching. If you need more sophisticated search capabilities, such as semantic search or integration with a vector database, you can implement a custom `ToolSearchStrategy`. Learn more in the [Tool Search Strategies](./client/tool-search-strategy) guide.

docs/for-tool-callers.md

@@ -201,18 +201,18 @@ When providing tool definitions, make sure to document which variables users nee
 
 For details on provider-specific configuration, see the dedicated pages for each type:
 
-- [HTTP Provider](providers/http.md)
-- [HTTP Stream Provider](providers/http-stream.md)
-- [Server-Sent Events (SSE) Provider](providers/sse.md)
-- [WebSocket Provider](providers/websocket.md)
-- [gRPC Provider](providers/grpc.md)
-- [GraphQL Provider](providers/graphql.md)
-- [Command-Line (CLI) Provider](providers/cli.md)
-- [Model Context Protocol (MCP) Provider](providers/mcp.md)
-- [Text File Provider](providers/text.md)
-- [TCP Provider](providers/tcp.md)
-- [UDP Provider](providers/udp.md)
-- [WebRTC Provider](providers/webrtc.md)
+- [HTTP Provider](providers/http)
+- [HTTP Stream Provider](providers/http-stream)
+- [Server-Sent Events (SSE) Provider](providers/sse)
+- [WebSocket Provider](providers/websocket)
+- [gRPC Provider](providers/grpc)
+- [GraphQL Provider](providers/graphql)
+- [Command-Line (CLI) Provider](providers/cli)
+- [Model Context Protocol (MCP) Provider](providers/mcp)
+- [Text File Provider](providers/text)
+- [TCP Provider](providers/tcp)
+- [UDP Provider](providers/udp)
+- [WebRTC Provider](providers/webrtc)
 
 ## Implementing a Discovery Endpoint