Choose Documentation Engine for SDK

[krvital]

Select and implement a documentation engine for generating SDK documentation.

Requirements:

• Design Reference: Follow the look and feel of Supabase and Slate documentation engines.
• Features:
  • Ability to generate a documentation site dynamically.
  • Support for code examples in multiple languages with a switcher or similar user experience.
  • Generate documentation for our SDK based on provided packages.

Implement a sample documentation site using the selected engine.

[krvital]

It seems that supabase uses docusarus for inner product documentation pages. So, maybe we need to try utilize docusaurus for our needs.