fix link in blog (#332)

fix links in blog posts

README.md

@@ -23,14 +23,15 @@ Unlike many agent frameworks that only track the chat history with LLMs in text,
 
 
 ## 🆕 News
+- 📅2024-05-07: We have added two blog posts on [Evaluating a LLM agent](https://microsoft.github.io/TaskWeaver/blog/evaluation) and [Adding new roles to TaskWeaver](https://microsoft.github.io/TaskWeaver/blog/role) in the documentation.📝
 - 📅2024-03-28: TaskWeaver now offers all-in-one Docker image, providing a convenient one-stop experience for users. Please check the [docker](https://microsoft.github.io/TaskWeaver/docs/usage/docker) for more details.🐳
 - 📅2024-03-27: TaskWeaver now switches to `container` mode by default for code execution. Please check the [code execution](https://microsoft.github.io/TaskWeaver/docs/code_execution) for more details.🐳
 - 📅2024-03-07: TaskWeaver now supports configuration of different LLMs for various components, such as the Planner and CodeInterpreter. Please check the [multi-llm](https://microsoft.github.io/TaskWeaver/docs/llms/multi-llm) for more details.🔗
 - 📅2024-03-04: TaskWeaver now supports a [container](https://microsoft.github.io/TaskWeaver/docs/code_execution) mode, which provides a more secure environment for code execution.🐳
 - 📅2024-02-28: TaskWeaver now offers a [CLI-only](https://microsoft.github.io/TaskWeaver/docs/advanced/cli_only) mode, enabling users to interact seamlessly with the Command Line Interface (CLI) using natural language.📟
 - 📅2024-02-01: TaskWeaver now has a plugin [document_retriever](https://github.com/microsoft/TaskWeaver/blob/main/project/plugins/README.md#document_retriever) for RAG based on a knowledge base.📚
 - 📅2024-01-30: TaskWeaver introduces a new plugin-only mode that securely generates calls to specified plugins without producing extraneous code.🪡 
-- 📅2024-01-23: TaskWeaver can now be personalized by transforming your chat histories into enduring [experiences](https://microsoft.github.io/TaskWeaver/docs/customization/experience) 🎉
+<!-- - 📅2024-01-23: TaskWeaver can now be personalized by transforming your chat histories into enduring [experiences](https://microsoft.github.io/TaskWeaver/docs/customization/experience) 🎉 -->
 <!-- - 📅2024-01-17: TaskWeaver now has a plugin [vision_web_explorer](https://github.com/microsoft/TaskWeaver/blob/main/project/plugins/README.md#vision_web_explorer) that can open a web browser and explore websites.🌐 -->
 <!-- - 📅2024-01-15: TaskWeaver now supports Streaming♒ in both UI and command line.✌️ -->
 <!-- - 📅2024-01-01: Welcome join TaskWeaver [Discord](https://discord.gg/Z56MXmZgMb). -->

website/blog/role.md

@@ -61,9 +61,9 @@ and the current flow actually incurred unnecessary LLM call overhead to generate
 Second, it does not make sense to represent the instructions in variables.
 The instructions are not data to be processed, but a text guide for the agent to follow.
 
-For these reasons, we introduced the concept of [roles](../docs/concepts/role.md) in TaskWeaver.
+For these reasons, we introduced the concept of [roles](/docs/concepts/role) in TaskWeaver.
 Roles are actually not new in TaskWeaver as there are already roles like `Planner` and `CodeInterpreter`.
-To add a new role, the developer can follow the documentation [here](../docs/concepts/role.md).
+To add a new role, the developer can follow the documentation [here](/docs/concepts/role).
 In general, a role is a class that inherits the `Role` class and implements the `reply` method.
 The `reply` method is the function that the agent calls to interact with the role, which has the 
 following signature:
@@ -73,7 +73,7 @@ def reply(self, memory: Memory, **kwargs) -> Post:
     # implementation
 ```
 
-It takes the `memory` object, which is the memory of the agent, and returns a [Post](../docs/concepts/post.md) object, which is the response of the role to the Planner.
+It takes the `memory` object, which is the memory of the agent, and returns a [Post](/docs/concepts/post) object, which is the response of the role to the Planner.
 With the `memory` object, the role can access the history of the conversation and the context of the conversation.
 You may have noticed that all roles in TaskWeaver can only talk to the Planner, not to each other.
 If a role needs to talk to another role, it should go through the Planner.
@@ -94,7 +94,7 @@ flowchart TD
     B --response--> A
 ```
 
-The communication between the Planner and the roles is done through the [Post](../docs/concepts/post.md) object.
+The communication between the Planner and the roles is done through the [Post](/docs/concepts/post) object.
 In other words, they talk to each other by sending messages in natural language.
 What if a role needs to send some data to another role? If this is the case, we would recommend to implement a new plugin
 instead of a new role. Otherwise, you may need to store the data in an external storage like a database and let the other role to access it.
@@ -107,7 +107,7 @@ Even though we can emphasize the importance of the Planner to pass all the neces
 it is still possible that the Planner misses some information.
 
 To address this challenge, we introduce the concept of `board` in TaskWeaver. 
-The `board` is a shared memory space that can be accessed by all roles, which is associated with the current [Round](../docs/concepts/round.md).
+The `board` is a shared memory space that can be accessed by all roles, which is associated with the current [Round](/docs/concepts/round).
 The `board` is a dictionary-like object that can store any information that is needed by the roles.
 Each role can decide to write or read any information from the `board`.