Update docs on how to interact with local LLM

[LeoLjl]

Why are these changes needed?

Specifying how to initiate an endpoint and interact with local LLMs using flaml.autogen is needed.

Related issue number

microsoft/autogen#15 #1037

Checks

• I've included any doc changes needed for https://microsoft.github.io/FLAML/. See https://microsoft.github.io/FLAML/docs/Contribute#documentation to build and test documentation locally.
• I've added tests (if relevant) corresponding to the changes introduced in this PR.
• I've made sure all auto checks have passed.

[sonichi]

Thanks for the detailed documentation. I have a few questions.

[LeoLjl]

@microsoft-github-policy-service agree

[sonichi]

Please follow https://microsoft.github.io/FLAML/docs/Contribute#pre-commit to pass the code-formatting check.

[sonichi]

Looks good to me. You can add subtasks for TODOs: register_chat_model and easier endpoint spinup process.

Could you compile the website locally to verify the format is good? Follow: https://microsoft.github.io/FLAML/docs/Contribute#documentation
Also, if you don't have a figure for the blogpost, you can simply put a "filename.md" under "blog/" instead of using "folder_name/index.mdx". The ".md" file can be easily previewed in vscode. See https://docusaurus.io/docs/blog#adding-posts

[LeoLjl]

Could you compile the website locally to verify the format is good? Follow: https://microsoft.github.io/FLAML/docs/Contribute#documentation Also, if you don't have a figure for the blogpost, you can simply put a "filename.md" under "blog/" instead of using "folder_name/index.mdx". The ".md" file can be easily previewed in vscode. See https://docusaurus.io/docs/blog#adding-posts

I complied the website, the format is good. I see that other blog posts are using the folder/index.mdx, for consistency I decide to retain this file layout.

[sonichi]

In future, consider using a single .md file for simple posts without auxiliary files. @qingyun-wu

[sonichi]

I requested a change after seeing @JieyuZ2 's comment.