Break up contributor guide for better navigability

website/docs/Getting-Started.mdx

@@ -131,7 +131,7 @@ The figure below shows an example conversation flow with AutoGen.
 - Follow on [Twitter](https://twitter.com/pyautogen)
 - See our [roadmaps](https://aka.ms/autogen-roadmap)
 
-If you like our project, please give it a [star](https://github.com/microsoft/autogen/stargazers) on GitHub. If you are interested in contributing, please read [Contributor's Guide](/docs/Contribute).
+If you like our project, please give it a [star](https://github.com/microsoft/autogen/stargazers) on GitHub. If you are interested in contributing, please read [Contributor's Guide](/docs/contributor-guide/contributing).
 
 <iframe
   src="https://ghbtns.com/github-btn.html?user=microsoft&amp;repo=autogen&amp;type=star&amp;count=true&amp;size=large"

website/docs/contributor-guide/contributing.md

@@ -0,0 +1,34 @@
+# Contributing to AutoGen
+
+This project welcomes and encourages all forms of contributions, including but not limited to:
+
+- Pushing patches.
+- Code review of pull requests.
+- Documentation, examples and test cases.
+- Readability improvement, e.g., improvement on docstr and comments.
+- Community participation in [issues](https://github.com/microsoft/autogen/issues), [discussions](https://github.com/microsoft/autogen/discussions), [discord](https://aka.ms/autogen-dc), and [twitter](https://twitter.com/pyautogen).
+- Tutorials, blog posts, talks that promote the project.
+- Sharing application scenarios and/or related research.
+
+Most contributions require you to agree to a
+Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
+the rights to use your contribution. For details, visit <https://cla.opensource.microsoft.com>.
+
+If you are new to GitHub [here](https://help.github.com/categories/collaborating-with-issues-and-pull-requests/) is a detailed help source on getting involved with development on GitHub.
+
+When you submit a pull request, a CLA bot will automatically determine whether you need to provide
+a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
+provided by the bot. You will only need to do this once across all repos using our CLA.
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
+contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
+
+## Roadmaps
+
+To see what we are working on and what we plan to work on, please check our
+[Roadmap Issues](https://aka.ms/autogen-roadmap).
+
+## Becoming a Reviewer
+
+There is currently no formal reviewer solicitation process. Current reviewers identify reviewers from active contributors. If you are willing to become a reviewer, you are welcome to let us know on discord.

website/docs/contributor-guide/docker.md

@@ -0,0 +1,51 @@
+# Docker for Development
+
+For developers contributing to the AutoGen project, we offer a specialized Docker environment. This setup is designed to streamline the development process, ensuring that all contributors work within a consistent and well-equipped environment.
+
+## Autogen Developer Image (autogen_dev_img)
+
+- **Purpose**: The `autogen_dev_img` is tailored for contributors to the AutoGen project. It includes a suite of tools and configurations that aid in the development and testing of new features or fixes.
+- **Usage**: This image is recommended for developers who intend to contribute code or documentation to AutoGen.
+- **Forking the Project**: It's advisable to fork the AutoGen GitHub project to your own repository. This allows you to make changes in a separate environment without affecting the main project.
+- **Updating Dockerfile**: Modify your copy of `Dockerfile` in the `dev` folder as needed for your development work.
+- **Submitting Pull Requests**: Once your changes are ready, submit a pull request from your branch to the upstream AutoGen GitHub project for review and integration. For more details on contributing, see the [AutoGen Contributing](https://microsoft.github.io/autogen/docs/Contribute) page.
+
+## Building the Developer Docker Image
+
+- To build the developer Docker image (`autogen_dev_img`), use the following commands:
+
+  ```bash
+  docker build -f .devcontainer/dev/Dockerfile -t autogen_dev_img https://github.com/microsoft/autogen.git#main
+  ```
+
+- For building the developer image built from a specific Dockerfile in a branch other than main/master
+
+  ```bash
+  # clone the branch you want to work out of
+  git clone --branch {branch-name} https://github.com/microsoft/autogen.git
+
+  # cd to your new directory
+  cd autogen
+
+  # build your Docker image
+  docker build -f .devcontainer/dev/Dockerfile -t autogen_dev-srv_img .
+  ```
+
+## Using the Developer Docker Image
+
+Once you have built the `autogen_dev_img`, you can run it using the standard Docker commands. This will place you inside the containerized development environment where you can run tests, develop code, and ensure everything is functioning as expected before submitting your contributions.
+
+```bash
+docker run -it -p 8081:3000 -v `pwd`/autogen-newcode:newstuff/ autogen_dev_img bash
+```
+
+- Note that the `pwd` is shorthand for present working directory. Thus, any path after the pwd is relative to that. If you want a more verbose method you could remove the "`pwd`/autogen-newcode" and replace it with the full path to your directory
+
+```bash
+docker run -it -p 8081:3000 -v /home/AutoGenDeveloper/autogen-newcode:newstuff/ autogen_dev_img bash
+```
+
+## Develop in Remote Container
+
+If you use vscode, you can open the autogen folder in a [Container](https://code.visualstudio.com/docs/remote/containers).
+We have provided the configuration in [devcontainer](https://github.com/microsoft/autogen/blob/main/.devcontainer). They can be used in GitHub codespace too. Developing AutoGen in dev containers is recommended.