Reorganize documentation into docs/ directory to improve README readability

[Copilot]

Problem

The README had become extremely long (733 lines), making it difficult to navigate and overwhelming for users trying to quickly understand the package. As noted in the issue: "The README for the project has gotten way too long lol".

Solution

Reorganized the documentation using a docs/ directory structure, following best practices for package documentation:

Changes Made

• Reduced README from 733 to 134 lines (82% reduction)
• Created 16 dedicated documentation files in the docs/ directory, one for each extension type
• Transformed README into a clean overview with:
  • Quick feature summary
  • Installation instructions
  • Code examples
  • Links to detailed documentation
• Added comprehensive docs index (docs/README.md) for easy navigation
• Implemented cross-linking between all documentation pages

New Documentation Structure

mayr_extensions/
├── README.md (Quick overview & setup)
└── docs/
    ├── README.md (Documentation index)
    ├── build_context_extensions.md
    ├── bool_extensions.md
    ├── datetime_extensions.md
    ├── duration_extensions.md
    ├── object_extensions.md
    ├── dynamic_extensions.md
    ├── image_extensions.md
    ├── number_extensions.md
    ├── string_extensions.md
    ├── list_extensions.md
    ├── map_extensions.md
    ├── set_extensions.md
    ├── humanize_extensions.md
    ├── widget_extensions.md
    └── datetime_format.md

Benefits

✅ Improved user experience - README is no longer overwhelming
✅ Better organization - Each extension type has dedicated documentation
✅ Easier maintenance - Update specific sections without scrolling through 700+ lines
✅ Enhanced discoverability - Users can quickly find relevant information
✅ Professional structure - Follows documentation best practices
✅ Better for contributors - Clear, organized documentation structure

Example

Before, users had to scroll through 733 lines to find String Extensions. Now:

1. Open README → See quick overview
2. Click String Extensions → Jump directly to detailed docs
3. Each doc page has navigation back to the index

All original content has been preserved and reorganized for better accessibility.

Original prompt

The README for the project has gotten way too long lol, I think we should make use of docs/ or if you have any better suggestion, I am open to hear it

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.