[Feature] [Monorepo] Release UI v1.0.0 and unify layouts across ecosystem platforms

[Gautam25Raj]

Summary

This PR releases the @repo/ui package as stable v1.0.0 and introduces a unified layout and design system experience across the ecosystem platforms, including the site, blog platform, and docs platform.

Features

UI Package (packages/ui)

• Released the UI package as stable production-ready v1.0.0
• Added a premium, Portal-based, and theme-aware Tooltip component
• Implemented smart overflow truncation detection for tooltip rendering
• Enhanced Menu component with customizable size variants:
  • sm
  • md
• Overhauled README.md with:
  • Comprehensive usage documentation
  • Unified component reference table
  • Improved developer guidance

Platform Layout Unification

Blog Platform (apps/blog-platform)

• Integrated the unified MainLayout
• Added consistent Navbar and Footer across the platform
• Added standardized:
  • Error templates
  • Loading templates
  • Not-found templates
• Standardized config/site.ts navigation configuration

Docs Platform (apps/docs-platform)

• Integrated the unified MainLayout
• Unified navigation and footer experience
• Added shared design-system-aligned templates for:
  • Error states
  • Loading states
  • Not-found pages
• Improved platform-wide navigation consistency

Ecosystem Site Improvements (apps/site)

Template Experience

• Added line-clamp-1 support for template names
• Integrated smart tooltip rendering only for truncated content
• Removed redundant tooltips from template descriptions
• Improved template preview card consistency

Roadmap & Configuration

• Centralized kanban tag color mappings into:
  • KanbanTagColor.ts
• Improved roadmap tag consistency and maintainability
• Updated template asset mappings for correct platform alignment

Ecosystem Updates

• Updated:
  • llms.txt
  • openapi.json
• Improved authentication and document-type schema consistency

Improvements

Design System & Consistency

• Unified layout structure across all ecosystem platforms
• Improved shared UI consistency and navigation behavior
• Enhanced maintainability through centralized configuration patterns

Developer Experience

• Improved documentation quality and component discoverability
• Enhanced reusable UI infrastructure across applications

Notes

• No breaking changes expected
• Focused on ecosystem consistency, stable UI release, and platform standardization

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
• 🧪 Tests (adding or updating tests)

Checklist

• I have read the CONTRIBUTING.md document.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.