docs: Update README with current status and known issues

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Author: Copilot

apps/site/README.md

@@ -1,21 +1,35 @@
-# Object UI Documentation Site
+# Object UI Documentation Site (Fumadocs Migration - In Progress)
 
-This is the official documentation site for Object UI, built with [Fumadocs](https://fumadocs.vercel.app/).
+This is the official documentation site for Object UI, being migrated to [Fumadocs](https://fumadocs.vercel.app/).
+
+## Status
+
+🚧 **Work in Progress** - The site structure is complete but there are issues with the fumadocs source API integration that need to be resolved.
+
+### Completed
+- ✅ Next.js 15 + TypeScript setup
+- ✅ Tailwind CSS configuration  
+- ✅ Fumadocs UI integration
+- ✅ MDX content processing
+- ✅ Basic documentation pages created
+- ✅ Homepage and layout structure
+
+### Known Issues
+- ⚠️ Route generation not working - investigating fumadocs 15.x API changes
+- The `.source` output from fumadocs-mdx needs proper integration with loader
+- `createMDXSource` API compatibility issue with runtime-processed docs/meta
 
 ## Development
 
 ```bash
 # Install dependencies
 pnpm install
 
-# Start development server
+# Start development server (NOTE: routes currently return 404)
 pnpm dev
 
 # Build for production
 pnpm build
-
-# Start production server
-pnpm start
 ```
 
 ## Project Structure
@@ -36,32 +50,22 @@ apps/site/
 └── source.config.ts     # Fumadocs MDX configuration
 ```
 
-## Features
-
-- 📝 MDX-based documentation
-- 🎨 Built with Tailwind CSS
-- 🌗 Dark mode support
-- 🔍 Full-text search (coming soon)
-- 📱 Responsive design
-- ⚡ Fast page loads with Next.js
-
-## Adding Documentation
-
-1. Create a new `.mdx` file in `content/docs/`
-2. Add frontmatter with title and description:
-   ```mdx
-   ---
-   title: Your Page Title
-   description: Page description
-   ---
-   
-   # Your Content Here
-   ```
-3. Update `content/docs/meta.json` to add the page to navigation
+## Technical Notes
+
+The fumadocs-mdx compiler generates a `.source` directory with processed docs and meta exports. These are wrapped by `_runtime.doc()` and `_runtime.meta()` functions. The correct integration with fumadocs-core's `loader` and `createMDXSource` needs investigation based on fumadocs 15.x API.
+
+## Next Steps
+
+1. Investigate correct fumadocs 15.x API for integrating `.source` exports
+2. Fix route generation to resolve 404 errors
+3. Add search functionality
+4. Migrate remaining documentation content
+5. Set up deployment
 
 ## Tech Stack
 
 - [Next.js 15](https://nextjs.org/) - React framework
 - [Fumadocs](https://fumadocs.vercel.app/) - Documentation framework
 - [Tailwind CSS](https://tailwindcss.com/) - Styling
 - [TypeScript](https://www.typescriptlang.org/) - Type safety
+

apps/site/app/docs/[[...slug]]/page.tsx

@@ -17,6 +17,7 @@ export default async function Page({
   const page = source.getPage(slug);
   if (!page) notFound();
 
+  // Type assertion needed due to custom data mapping
   const MDX = (page.data as any).body;
 
   return (

apps/site/lib/source.ts

@@ -2,11 +2,12 @@ import { loader } from 'fumadocs-core/source';
 import { docs } from '@/.source';
 
 // Map the docs from .source to the format expected by loader
+// Note: docs from .source is wrapped by _runtime.doc(), not a plain array
 const mappedDocs = docs
   .filter((doc: any) => doc && doc.info && doc.info.path)
   .map((doc: any) => {
     let path = doc.info.path.replace(/\.mdx?$/, '');
-    // Convert index.mdx to empty path
+    // Convert index.mdx to empty path for root /docs route
     if (path === 'index') path = '';
 
     return {