Add a "Recipes" / "Cookbook" section for advanced patterns and performance optimizations

[akshaypilankar]

Following the discussion in issue #55 regarding the addition of a Slider component, it is clear that there are high-performance, architectural ways to achieve complex UI patterns in Oat without necessarily bloating the core library with heavy, pre-built components.

While the maintainer’s approach to handling components like sliders (as mentioned in this comment) is technically superior and keeps the library lightweight, it may not be immediately obvious to users who are used to "plug-and-play" component libraries.

I propose creating a "Recipes" or "Cookbook" page in the documentation (or a RECIPES.md in the repo).

The Goal:

Bridge the Gap: Show "normal" users how to implement common UI elements (like Sliders, Tabs, or Modals) using Oat’s core principles.

Best Practices: Document the "clever" architectural patterns that ensure maximum performance, which might be non-trivial for those unfamiliar with the library's internals.

[knadh]

Yep, we can a recipes page to docs.

[sarthakworks]

I am working on it @knadh @akshaypilankar !!

[sarthakworks]

#84

Hi @knadh added pr #84

Please let me know for any recommendations