Skip to content

Commit 6b15ce4

Browse files
committed
initial migration of pages and manual testing
code sizeing new batch data insertion versioning & migration next batch next batch fix mdx-rendered and adding next batch of files adding api files fixed some language rendering and added more pages added workflows files added other workflow files streaming files added additional frameworks added new batch added top level files data modeling all files migrated initial changelog addressing cursor comments fix tabs added a bit of padding to the nav added sonner for language change fix TOC fix the build add ts ignore to mux player removed top nav fix TOC challenges added templates to new docs split server & client components moved to static api route instead we got search udpated errror handling updaign adjusting added default added sitemap update sitemap config caching gh stars fixing issues attempt build fix another attempt at build fix yet another attempt yet another fix yet another centering fixed issues fixed search variety of fixes prevent overscroll fix content wrapper for code editor and consistent heights better search highlights fix alignement of text in sidebar submenu added feature flags add flags wellknown enpoint fixed flags added ai section feature flag made text smalelr in header tiny spacing tweaks fix changelog styles initial guides
1 parent f75c9ee commit 6b15ce4

File tree

168 files changed

+28967
-3086
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

168 files changed

+28967
-3086
lines changed

apps/framework-docs-v2/.npmrc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Force all dependencies to be hoisted locally to this app's node_modules
2+
# This prevents TypeScript from finding React types in nested node_modules
3+
# This overrides the root .npmrc which prevents hoisting to support multiple React versions
4+
# Since this app only uses React 19, we can safely hoist everything here
5+
shamefully-hoist=true
6+
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# Feature Flags Setup
2+
3+
## Quick Start
4+
5+
1. **Already configured:**
6+
- ✅ Vercel Toolbar installed
7+
- ✅ Flags SDK with PostHog adapter
8+
- ✅ Discovery endpoint at `/.well-known/vercel/flags`
9+
10+
2. **Required environment variables:**
11+
```bash
12+
FLAGS_SECRET=<auto-generated by toolbar>
13+
POSTHOG_PERSONAL_API_KEY=<from PostHog settings>
14+
POSTHOG_PROJECT_ID=<from PostHog settings>
15+
```
16+
17+
3. **Usage:**
18+
- Run `pnpm dev`
19+
- Open Vercel Toolbar → Flags Explorer
20+
- Toggle flags to test navigation visibility
21+
22+
## Available Flags
23+
24+
- `show-hosting-section` - Controls Hosting tab visibility (default: off)
25+
- `show-guides-section` - Controls Guides tab visibility (default: off)
26+
- `show-ai-section` - Controls AI tab visibility (default: on)
27+
28+
## How It Works
29+
30+
- **Flags SDK** automatically reads `vercel-flag-overrides` cookie
31+
- **Resolution order**: Cookie Override → PostHog → Default
32+
- **Dynamic rendering** everywhere for flag overrides to work
33+
- SEO-friendly: Pages still server-render with full HTML
34+
35+
## Files
36+
37+
- `src/flags.ts` - Flag definitions
38+
- `src/app/.well-known/vercel/flags/route.ts` - Discovery endpoint
39+
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Automated Reports
3+
description: Guide to building automated reporting systems with MooseStack
4+
---
5+
6+
# Automated Reports
7+
8+
This guide covers how to build automated reporting systems using MooseStack workflows and APIs.
9+
10+
## Overview
11+
12+
Automate the generation and distribution of reports using scheduled workflows and API integrations.
13+
14+
## Key Concepts
15+
16+
- Scheduled workflows
17+
- Report generation
18+
- Email and notification delivery
19+
- Template management
20+
21+
## Next Steps
22+
23+
Learn about [workflows](/moosestack/workflows) and [APIs](/moosestack/apis) to build automated reports.
24+
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
title: Going to Production
3+
description: Guide to preparing and deploying MooseStack applications to production
4+
---
5+
6+
# Going to Production
7+
8+
This guide covers best practices and considerations for deploying MooseStack applications to production environments.
9+
10+
## Overview
11+
12+
Moving from development to production requires careful planning around infrastructure, monitoring, security, and scalability. This guide walks you through the essential steps.
13+
14+
## Key Topics
15+
16+
- Infrastructure preparation
17+
- Security and authentication
18+
- Monitoring and observability
19+
- Performance optimization
20+
- Disaster recovery and backups
21+
- Scaling strategies
22+
23+
## Next Steps
24+
25+
Learn more about [deployment](/moosestack/deploying) and [monitoring](/moosestack/metrics) to prepare your application for production.
26+
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: In-App Chat Analytics
3+
description: Guide to implementing analytics for in-app chat features
4+
---
5+
6+
# In-App Chat Analytics
7+
8+
This guide shows you how to implement analytics for in-app chat features using MooseStack.
9+
10+
## Overview
11+
12+
Track and analyze chat interactions, message volumes, response times, and user engagement metrics.
13+
14+
## Key Concepts
15+
16+
- Streaming chat events
17+
- Real-time aggregations
18+
- User behavior analysis
19+
- Performance monitoring
20+
21+
## Next Steps
22+
23+
Learn about [streaming](/moosestack/streaming) and [APIs](/moosestack/apis) to implement chat analytics.
24+
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Performant Dashboards
3+
description: Guide to building high-performance dashboards with MooseStack
4+
---
5+
6+
# Performant Dashboards
7+
8+
This guide covers best practices for building performant dashboards using MooseStack.
9+
10+
## Overview
11+
12+
Building dashboards that load quickly and provide real-time insights requires careful consideration of data modeling, query optimization, and caching strategies.
13+
14+
## Key Concepts
15+
16+
- Materialized views for pre-aggregated data
17+
- Efficient query patterns
18+
- Caching strategies
19+
- Real-time data updates
20+
21+
## Next Steps
22+
23+
Learn more about [data modeling](/moosestack/data-modeling) and [OLAP](/moosestack/olap) to get started.
24+
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Change Data Capture
3+
description: Guide to implementing change data capture (CDC) with MooseStack
4+
---
5+
6+
# Change Data Capture
7+
8+
This guide covers how to implement change data capture (CDC) to track and replicate database changes in real-time using MooseStack.
9+
10+
## Overview
11+
12+
Change Data Capture (CDC) enables you to capture and stream database changes as they happen, allowing you to keep multiple systems in sync and build real-time analytics pipelines.
13+
14+
## Key Concepts
15+
16+
- Real-time change detection
17+
- Event streaming and replication
18+
- Schema evolution handling
19+
- Conflict resolution strategies
20+
21+
## Next Steps
22+
23+
Learn more about [streaming](/moosestack/streaming) and [connecting CDC services](/moosestack/streaming/connect-cdc) to implement change data capture.
24+
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Impact Analysis
3+
description: Guide to analyzing the impact of schema changes
4+
---
5+
6+
# Impact Analysis
7+
8+
This guide covers how to analyze the impact of schema changes before applying them.
9+
10+
## Overview
11+
12+
Before making schema changes, it's important to understand how they will affect existing queries, views, and downstream systems.
13+
14+
## Key Concepts
15+
16+
- Query dependency analysis
17+
- View impact assessment
18+
- Downstream system considerations
19+
- Change validation
20+
21+
## Next Steps
22+
23+
Learn about [schema versioning](/moosestack/olap/schema-versioning) and [migrations](/moosestack/migrate) to manage changes safely.
24+
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Migrations
3+
description: Guide to managing database migrations with MooseStack
4+
---
5+
6+
# Migrations
7+
8+
This guide covers best practices for managing database migrations in MooseStack projects.
9+
10+
## Overview
11+
12+
Migrations allow you to version control your database schema and apply changes safely across environments.
13+
14+
## Key Concepts
15+
16+
- Migration types
17+
- Lifecycle management
18+
- Schema versioning
19+
- Rollback strategies
20+
21+
## Next Steps
22+
23+
Learn more about [migration types](/moosestack/migrate/migration-types) and [lifecycle management](/moosestack/migrate/lifecycle).
24+
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Connectors
3+
description: Guide to using connectors to integrate data sources with MooseStack
4+
---
5+
6+
# Connectors
7+
8+
This guide covers how to use connectors to integrate various data sources with your MooseStack data warehouse.
9+
10+
## Overview
11+
12+
Connectors enable you to seamlessly integrate external data sources, APIs, and databases into your MooseStack data warehouse, making it easy to centralize data from multiple systems.
13+
14+
## Key Concepts
15+
16+
- Available connector types
17+
- Configuration and setup
18+
- Data synchronization patterns
19+
- Error handling and retries
20+
21+
## Next Steps
22+
23+
Learn more about [data sources](/moosestack/data-sources) and [streaming](/moosestack/streaming) to understand how connectors work with MooseStack.
24+

0 commit comments

Comments
 (0)