Update documentation

[Medyan-Naser]

Contributing Guidelines

• I have read and understood the CONTRIBUTING.md guidelines

Description

This PR adds a full documentation website for the XLB project using Sphinx and Read the Docs.

• The original README.md has been split into multiple structured pages.
• A new api_reference page has been added for future automated API documentation.
• A docs/ folder was created to hold the Sphinx project files.
• A .readthedocs.yml file was added to configure the Read the Docs build.
• The site is live at: https://xlb.readthedocs.io/en/latest/

This setup provides a scalable and maintainable structure for XLB documentation going forward.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• All pytest tests pass

Linting and Code Formatting

Make sure the code follows the project's linting and formatting standards. This project uses Ruff for linting.

To run Ruff, execute the following command from the root of the repository:

ruff check .

• Ruff passes

[mehdiataei]

Hi Meydan, thanks a lot for your PR. We really appreciate the effort. We’re currently using MK Docs for our documentation and don’t have plans to migrate away from it.

If you’re interested in contributing further, it would be great to have your help improving the existing documentation.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Medyan-Naser]

I have read the CLA Document and I hereby sign the CLA

[hsalehipour]

Thanks a lot @Medyan-Naser for this contribution. I have discovered this automatic documentation page:
https://deepwiki.com/Autodesk/XLB

Considering this page (which updates automatically based on the latest in the repo), I think we may not need this PR any longer. What do you think?

[Medyan-Naser]

@hsalehipour

DeepWiki is useful and does a good job auto-generating docs, but we can’t fully verify its accuracy or control how complete it is at any point.

Also, my PR adds first-time usage examples and a quick start guide for XLB, which is missing from DeepWiki and is usually what helps most with onboarding.

So I think it still makes sense to keep and maintain our internal docs.