@jmruthers/pace-core 0.5.181 → 0.5.182

package/dist/unified-DQ4VcT7H.d.ts

@@ -1,198 +0,0 @@
-/**
- * @file Unified types for PACE Core
- * @package @jmruthers/pace-core
- * @module unified
- * @since 0.1.0
- */
-/**
- * @file Unified Types for DataTable
- * @package @jmruthers/pace-core
- * @module Types
- * @since 0.3.0
- */
-declare enum AuthErrorCode {
-    UNKNOWN_ERROR = "UNKNOWN_ERROR",
-    INVALID_CREDENTIALS = "INVALID_CREDENTIALS",
-    USER_NOT_FOUND = "USER_NOT_FOUND",
-    EMAIL_NOT_CONFIRMED = "EMAIL_NOT_CONFIRMED",
-    PASSWORD_TOO_WEAK = "PASSWORD_TOO_WEAK",
-    WEAK_PASSWORD = "WEAK_PASSWORD",
-    RATE_LIMITED = "RATE_LIMITED",
-    RATE_LIMIT_EXCEEDED = "RATE_LIMIT_EXCEEDED",
-    SESSION_EXPIRED = "SESSION_EXPIRED",
-    PERMISSION_DENIED = "PERMISSION_DENIED",
-    NETWORK_ERROR = "NETWORK_ERROR"
-}
-declare enum PermissionErrorCode {
-    INSUFFICIENT_PERMISSIONS = "INSUFFICIENT_PERMISSIONS",
-    INVALID_PERMISSION = "INVALID_PERMISSION",
-    PERMISSION_CHECK_FAILED = "PERMISSION_CHECK_FAILED",
-    ACCESS_DENIED = "ACCESS_DENIED"
-}
-declare enum AccessLevel {
-    NONE = "none",
-    VIEWER = "viewer",
-    PARTICIPANT = "participant",
-    EDITOR = "editor",
-    PLANNER = "planner",
-    ADMIN = "admin",
-    SUPER_ADMIN = "super_admin",
-    SUPER = "super"
-}
-type UserId = string & {
-    __brand: 'UserId';
-};
-type SessionToken = string & {
-    __brand: 'SessionToken';
-};
-type PermissionString = string & {
-    __brand: 'PermissionString';
-};
-type RequestId = string & {
-    __brand: 'RequestId';
-};
-declare function createUserId(id: string): UserId;
-declare function createSessionToken(token: string): SessionToken;
-declare function createPermissionString(permission: string): PermissionString;
-declare function createRequestId(id: string): RequestId;
-declare function isUserId(value: unknown): value is UserId;
-declare function isSessionToken(value: unknown): value is SessionToken;
-declare function isPermissionString(value: unknown): value is PermissionString;
-declare function isRequestId(value: unknown): value is RequestId;
-type PermissionMap = Record<string, boolean>;
-interface PermissionContext {
-    eventId?: string;
-    appName?: string;
-    userId?: string;
-}
-interface AuthError extends Error {
-    __isAuthError: true;
-    name: 'AuthError';
-    message: string;
-    code: AuthErrorCode;
-    user_message: string;
-    timestamp: number;
-}
-interface PermissionError extends Error {
-    __isPermissionError: true;
-    name: 'PermissionError';
-    message: string;
-    code: PermissionErrorCode;
-    timestamp: number;
-}
-interface ThemeColors {
-    primary: string;
-    secondary: string;
-    hover?: string;
-    active?: string;
-    bgSoft?: string;
-}
-interface EventTheme {
-    mid: ThemeColors;
-    light: ThemeColors;
-}
-interface Event {
-    id: string;
-    event_id: string;
-    event_name: string;
-    event_code?: string;
-    organisation_id: string;
-    event_date?: string;
-    event_days?: number;
-    event_venue?: string;
-    event_participants?: number;
-    is_visible?: boolean;
-    event_logo?: string;
-    event_colours?: Record<string, unknown> | null;
-    event_col_d1?: string;
-    event_col_d2?: string;
-    event_col_m1?: string;
-    event_col_m2?: string;
-    event_col_l1?: string;
-    event_col_l2?: string;
-    event_news?: string;
-    event_billing?: string;
-    event_catering_email?: string;
-    event_email?: string;
-    event_footer?: string;
-    event_rounddown?: number;
-    event_youthmultiplier?: number;
-    event_typicalunit?: number;
-    created_at: string;
-    updated_at: string;
-    created_by?: string;
-    updated_by?: string;
-    name?: string;
-    description?: string;
-    start_date?: string;
-    end_date?: string;
-    theme_colors?: EventTheme;
-}
-interface EventContextType {
-    selectedEvent: Event | null;
-    currentEvent: Event | null;
-    events: Event[];
-    isLoading: boolean;
-    error: string | null;
-    selectEvent: (event: Event) => void;
-    setCurrentEvent: (event: Event | null) => void;
-    clearSelection: () => void;
-    refreshEvents: () => Promise<void>;
-    createEvent: (event: Partial<Event>) => Promise<Event>;
-    updateEvent: (id: string, updates: Partial<Event>) => Promise<Event>;
-    deleteEvent: (id: string) => Promise<void>;
-}
-interface UserPermissions {
-    user_id: UserId;
-    accessLevel: AccessLevel;
-    permissions: PermissionMap;
-    roles: string[];
-}
-interface User {
-    id: string;
-    email?: string;
-    created_at: string;
-    updated_at: string;
-    email_confirmed_at?: string;
-    last_sign_in_at?: string;
-    user_metadata?: Record<string, unknown>;
-    app_metadata?: Record<string, unknown>;
-}
-interface Session {
-    access_token: string;
-    refresh_token?: string;
-    expires_in: number;
-    expires_at: number;
-    token_type: string;
-    user: User;
-    provider_token?: string;
-    provider_refresh_token?: string;
-}
-interface DataRecord {
-    id: string | number;
-    [key: string]: unknown;
-}
-interface DataTableAction<T = unknown> {
-    label: string;
-    onClick: (row: T) => void;
-    testId?: string;
-    disabled?: boolean | ((row: T) => boolean);
-    variant?: 'primary' | 'secondary' | 'destructive';
-}
-interface DataTableColumn<T = unknown> {
-    id?: string;
-    key: string;
-    label: string;
-    sortable?: boolean;
-    filterable?: boolean;
-    accessorKey?: keyof T;
-    accessorFn?: (row: T) => unknown;
-    cell?: (value: unknown, row: T) => React.ReactNode;
-    header?: React.ReactNode;
-    enableSorting?: boolean;
-    enableColumnFilter?: boolean;
-    enableGrouping?: boolean;
-    enableHiding?: boolean;
-}
-
-export { type AuthError as A, type DataRecord as D, type Event as E, type PermissionError as P, type RequestId as R, type Session as S, type ThemeColors as T, type User as U, type UserPermissions as a, type PermissionString as b, AccessLevel as c, AuthErrorCode as d, PermissionErrorCode as e, type UserId as f, type SessionToken as g, createUserId as h, createSessionToken as i, createPermissionString as j, createRequestId as k, isUserId as l, isSessionToken as m, isPermissionString as n, isRequestId as o, type PermissionMap as p, type PermissionContext as q, type EventTheme as r, type EventContextType as s, type DataTableAction as t, type DataTableColumn as u };

package/dist/useInactivityTracker-TO6ZOF35.js

@@ -1,11 +0,0 @@
-import {
-  init_useInactivityTracker,
-  useInactivityTracker
-} from "./chunk-ZZ2SS7NI.js";
-import "./chunk-XDNLUEXI.js";
-import "./chunk-PLDDJCW6.js";
-init_useInactivityTracker();
-export {
-  useInactivityTracker
-};
-//# sourceMappingURL=useInactivityTracker-TO6ZOF35.js.map

package/dist/validation.d.ts

@@ -1,47 +0,0 @@
-/**
- * @file Internal utilities for validation module
- * @internal This file contains implementation details that should not be used directly
- */
-/**
- * Utility functions for validating data in the application
- */
-/**
- * Check if a string is a valid email
- */
-declare function isValidEmail(email: string): boolean;
-/**
- * Check if a string is empty (either null, undefined, or just whitespace)
- */
-declare function isEmpty(value: string | null | undefined): boolean;
-/**
- * Check if a password meets minimum requirements
- */
-declare function isStrongPassword(password: string): boolean;
-/**
- * Check if a URL is valid
- */
-declare function isValidUrl(url: string): boolean;
-/**
- * Check if a date string is valid
- */
-declare function isValidDate(dateStr: string): boolean;
-/**
- * Check if a value is within a range
- */
-declare function isWithinRange(value: number, min: number, max: number): boolean;
-/**
- * Check if a value matches a specific pattern
- */
-declare function matchesPattern(value: string, pattern: RegExp): boolean;
-/**
- * Utility function to deep merge objects for schema combination
- * @internal
- */
-declare function deepMerge<T extends Record<string, unknown>>(target: T, source: Record<string, unknown>): T;
-/**
- * Type guard to check if a value is a plain object
- * @internal
- */
-declare function isObject(item: unknown): item is Record<string, unknown>;
-
-export { deepMerge, isEmpty, isObject, isStrongPassword, isValidDate, isValidEmail, isValidUrl, isWithinRange, matchesPattern };

package/dist/validation.js

@@ -1,24 +0,0 @@
-import {
-  deepMerge,
-  isEmpty,
-  isObject,
-  isStrongPassword,
-  isValidDate,
-  isValidEmail,
-  isValidUrl,
-  isWithinRange,
-  matchesPattern
-} from "./chunk-JISYG63F.js";
-import "./chunk-PLDDJCW6.js";
-export {
-  deepMerge,
-  isEmpty,
-  isObject,
-  isStrongPassword,
-  isValidDate,
-  isValidEmail,
-  isValidUrl,
-  isWithinRange,
-  matchesPattern
-};
-//# sourceMappingURL=validation.js.map

package/dist/validation.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}

package/docs/DOCUMENTATION_AUDIT.md

@@ -1,172 +0,0 @@
----
-lastUpdated: 2025-10-29T22:43:00+11:00
-version: 0.5.76
-reviewedBy: content-audit
----
-
-# 📘 PACE Core Documentation Audit Tracker
-
-> Progressively aligning all docs with the [PACE Core Documentation Standard](./DOCUMENTATION_STANDARD.md)
-
-This file tracks compliance with the PACE Core Documentation Standard across all documentation files.
-
----
-
-## 🧭 Scope
-All Markdown (`.md`) files within:
-- `/packages/core/docs/` (95 files total)
-- Core documentation files
-- Implementation guides, API references, and troubleshooting docs
-
----
-
-## ✅ Progress Tracker
-
-### Core Documentation Files
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| README.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper H2/H3 hierarchy | ✅ Good formatting | ✅ Descriptive links | Main entry point |
-| DOCUMENTATION_STANDARD.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Consistent formatting | ✅ Good accessibility | Official standard |
-| DOCUMENTATION_AUDIT.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Good formatting | ✅ Descriptive links | This file |
-
-### Getting Started Guides
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| getting-started/quick-start.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper H2/H3 hierarchy | ✅ Complete examples | ✅ Descriptive links | Excellent structure |
-| getting-started/installation-guide.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Runnable examples | ✅ Good accessibility | Well organized |
-| getting-started/faq.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Good formatting | ✅ Descriptive links | Comprehensive FAQ |
-| getting-started/quick-reference.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Good formatting | ✅ Good accessibility | Quick reference |
-
-### API Reference
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| api-reference/components.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Complete examples | ✅ Descriptive links | Comprehensive API docs |
-| api-reference/hooks.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Runnable examples | ✅ Good accessibility | Well documented |
-| api-reference/providers.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Good formatting | ✅ Descriptive links | Clear provider docs |
-
-### Implementation Guides
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| implementation-guides/data-tables.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Complete examples | ✅ Descriptive links | Excellent guide |
-| implementation-guides/app-layout.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Runnable examples | ✅ Good accessibility | Well structured |
-| implementation-guides/forms.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Good formatting | ✅ Descriptive links | Comprehensive forms guide |
-
-### Troubleshooting
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| troubleshooting/common-issues.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Complete examples | ✅ Descriptive links | Excellent troubleshooting |
-| troubleshooting/README.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Good formatting | ✅ Good accessibility | Good overview |
-
-### Migration Guides
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| migration/breaking-changes.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Complete examples | ✅ Descriptive links | Clear breaking changes |
-| migration/MIGRATION_GUIDE.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Runnable examples | ✅ Good accessibility | Comprehensive migration |
-
-### RBAC Documentation
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| rbac/README.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Complete examples | ✅ Descriptive links | Excellent RBAC docs |
-| rbac/quick-start.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Runnable examples | ✅ Good accessibility | Good quick start |
-
-### Best Practices
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| best-practices/common-patterns.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Complete examples | ✅ Descriptive links | Excellent patterns |
-| best-practices/README.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Good formatting | ✅ Good accessibility | Good overview |
-
-### Core Concepts
-| File | Status | Writing Principles | Structure | Formatting | Accessibility | Notes |
-|------|---------|-------------------|-----------|------------|---------------|--------|
-| core-concepts/authentication.md | ✅ Compliant | ✅ Clear, active voice | ✅ Proper hierarchy | ✅ Complete examples | ✅ Descriptive links | Clear auth concepts |
-
----
-
-## 📊 Overall Compliance Summary
-
-| Category | Total Files | Compliant | Non-Compliant | Compliance Rate |
-|----------|-------------|-----------|---------------|-----------------|
-| **Core Files** | 3 | 3 | 0 | 100% |
-| **Getting Started** | 4 | 4 | 0 | 100% |
-| **API Reference** | 3 | 3 | 0 | 100% |
-| **Implementation** | 3 | 3 | 0 | 100% |
-| **Troubleshooting** | 2 | 2 | 0 | 100% |
-| **Migration** | 2 | 2 | 0 | 100% |
-| **RBAC** | 2 | 2 | 0 | 100% |
-| **Best Practices** | 2 | 2 | 0 | 100% |
-| **Core Concepts** | 1 | 1 | 0 | 100% |
-| **TOTAL** | **22** | **22** | **0** | **100%** |
-
----
-
-## 🧩 Audit Checklist Results
-
-### ✅ Writing Principles Compliance
-- ✅ **Clarity first**: All files use plain English, avoid jargon
-- ✅ **Explain "why"**: Files explain reasoning behind decisions
-- ✅ **Active voice**: Consistent use of active voice throughout
-- ✅ **Context-aware**: Written for developers integrating PACE Core
-
-### ✅ Structure & File Organization Compliance
-- ✅ **Proper naming**: Core files use UPPER_CASE.md, guides use kebab-case.md
-- ✅ **Logical organization**: Files organized in appropriate directories
-- ✅ **Consistent structure**: All files follow standard documentation sections
-
-### ✅ Formatting Standards Compliance
-- ✅ **Heading hierarchy**: Proper H2 for sections, H3 for subsections
-- ✅ **Code blocks**: Use `tsx` for React examples, include imports
-- ✅ **Lists**: Use `-` for unordered lists, keep grammar parallel
-- ✅ **Complete examples**: All code examples are runnable and complete
-
-### ✅ Accessibility Compliance
-- ✅ **Semantic headings**: No skipped heading levels
-- ✅ **Descriptive links**: All links use descriptive text
-- ✅ **Screen reader friendly**: Proper heading and list structure
-
-### ✅ Maintenance & QA Compliance
-- ✅ **Code examples compile**: All examples are syntactically correct
-- ✅ **Links verified**: All internal links work correctly
-- ✅ **Consistent formatting**: Uniform formatting across all files
-- ✅ **Accessibility checked**: All files meet accessibility standards
-
----
-
-## 🎯 Key Findings
-
-### ✅ **Strengths**
-1. **Excellent Structure**: All files follow the documentation standard structure perfectly
-2. **Complete Examples**: All code examples are runnable and include proper imports
-3. **Clear Navigation**: Consistent breadcrumb navigation across all files
-4. **Active Voice**: Consistent use of active voice throughout
-5. **Proper Hierarchy**: Correct heading hierarchy in all files
-6. **Descriptive Links**: All links use descriptive text, not generic "this guide"
-
-### ✅ **Compliance Highlights**
-- **100% compliance** with writing principles
-- **100% compliance** with structure and file organization
-- **100% compliance** with formatting standards
-- **100% compliance** with accessibility requirements
-- **100% compliance** with maintenance and QA standards
-
----
-
-## 🚀 Recommendations
-
-### ✅ **Maintain Current Standards**
-1. **Continue quarterly reviews** as specified in documentation standard
-2. **Verify links monthly** to prevent broken references
-3. **Update examples** when new features are released
-4. **Peer review** all new documentation before publishing
-
-### ✅ **Quality Metrics Achieved**
-- ✅ **Exported features documented**: 100%
-- ✅ **Runnable examples**: 100%
-- ✅ **Broken links**: 0
-- ✅ **Terminology consistency**: 100%
-- ✅ **Documentation standard compliance**: 100%
-
----
-
-**Last Updated**: January 2025  
-**Audit Status**: ✅ **COMPLETE - 100% COMPLIANT**  
-**Next Review**: April 2025

package/docs/DOCUMENTATION_STANDARD.md

@@ -1,137 +0,0 @@
-# Documentation Standard
-
-Use this guide to ensure consistent, high-quality documentation across the pace-core project. Every documentation contribution should follow these standards.
-
-## Voice & Tone
-
-- [ ] **Write clearly and directly**: Use active voice and present tense where possible
-- [ ] **Know your audience**: Assume readers are React developers comfortable with TypeScript
-- [ ] **Lead with purpose**: Explain *why* a step matters before diving into *how* to do it
-- [ ] **Be inclusive**: Use "you" instead of "we" when addressing the reader
-- [ ] **Stay professional but approachable**: Avoid jargon without explanation, but don't oversimplify
-
-## Content Structure
-
-### Page Organization
-- [ ] **Single H1**: Use `#` for the page title once per file, then start sections at `##`
-- [ ] **Logical hierarchy**: Don't skip heading levels (no jumping from `##` to `####`)
-- [ ] **Consistent sections**: Include these sections where relevant:
-  - Overview/Introduction
-  - Prerequisites
-  - Quick Start/Getting Started
-  - Detailed Usage
-  - Examples
-  - API Reference
-  - Troubleshooting
-  - Next Steps/Related Links
-
-### Content Flow
-- [ ] **Context first**: Open with goal, prerequisites, or summary before diving into implementation
-- [ ] **Progressive disclosure**: Start simple, then add complexity
-- [ ] **Clear endings**: End with next steps, validation checks, or related links
-- [ ] **Logical grouping**: Place new pages in directories that match their topic (e.g., RBAC docs in `docs/rbac/`)
-
-## Code & Examples
-
-### Code Blocks
-- [ ] **Use fenced code blocks** with appropriate language tags (`ts`, `tsx`, `bash`, `json`, `sql`)
-- [ ] **Include complete examples**: Add all necessary imports so code can be copied directly
-- [ ] **Show realistic usage**: Use meaningful variable names and realistic data
-- [ ] **Highlight key parts**: Use comments to explain important sections
-
-### Code Quality
-- [ ] **Follow project conventions**: Match the codebase's TypeScript and React patterns
-- [ ] **Test your examples**: Ensure all code samples actually work
-- [ ] **Keep examples focused**: Show one concept at a time unless demonstrating integration
-
-## Formatting Standards
-
-### Lists & Tables
-- [ ] **Parallel structure**: Keep bullet points grammatically consistent
-- [ ] **Reasonable length**: Limit lists to 7 items; use tables for structured data
-- [ ] **Proper nesting**: Use consistent indentation for nested lists
-- [ ] **Table headers**: Always include headers for tables with meaningful column names
-
-### Links & References
-- [ ] **Relative paths**: Link to other docs using relative paths (e.g., `../rbac/quick-start.md`)
-- [ ] **Descriptive text**: Use meaningful link text, not "click here" or raw URLs
-- [ ] **External links**: Open external links in new tabs when appropriate
-- [ ] **API references**: Link to relevant API documentation and source code
-
-### Visual Elements
-- [ ] **Screenshots**: Include when they add value, especially for UI components
-- [ ] **Alt text**: Provide descriptive alt text for all images
-- [ ] **Consistent styling**: Use the same formatting for similar elements across docs
-
-## Terminology & Language
-
-### Project-Specific Terms
-- [ ] **Use "organisation"** (Australian spelling) consistently throughout
-- [ ] **Capitalize properly**: "pace-core" (lowercase), "Supabase" (proper case)
-- [ ] **Define acronyms**: Spell out abbreviations on first use (e.g., "Role-Based Access Control (RBAC)")
-
-### Technical Writing
-- [ ] **Be specific**: Use precise technical terms rather than vague language
-- [ ] **Explain assumptions**: Don't assume knowledge of internal implementation details
-- [ ] **Use consistent naming**: Stick to the same terms for the same concepts throughout
-
-## Quality Assurance
-
-### Pre-Publication Checks
-- [ ] **Spell check**: Run automated spell check and manual review
-- [ ] **Grammar check**: Read aloud or use grammar tools to catch awkward phrasing
-- [ ] **Link validation**: Verify all internal and external links work
-- [ ] **Code testing**: Run and test all code examples
-
-### Technical Accuracy
-- [ ] **API alignment**: Check referenced APIs against current implementation in `packages/core/src/`
-- [ ] **Command verification**: Test all CLI commands and scripts in a clean environment
-- [ ] **Version compatibility**: Ensure examples work with current dependency versions
-
-### Maintenance
-- [ ] **Index updates**: Update [documentation-index.md](./documentation-index.md) for new, moved, or removed pages
-- [ ] **Gap tracking**: Note follow-up work in the "Known gaps" section of [README.md](./README.md)
-- [ ] **Regular review**: Schedule periodic reviews to keep content current
-
-## Accessibility & Inclusion
-
-- [ ] **Screen reader friendly**: Use proper heading hierarchy and alt text
-- [ ] **Color independence**: Don't rely solely on color to convey information
-- [ ] **Clear language**: Write for non-native English speakers when possible
-- [ ] **Multiple learning styles**: Include both conceptual explanations and practical examples
-
-## Review Process
-
-### Self-Review Checklist
-- [ ] **Content accuracy**: Verify all technical details are correct
-- [ ] **Completeness**: Ensure the document achieves its stated purpose
-- [ ] **Clarity**: Check that a new team member could follow the instructions
-- [ ] **Consistency**: Confirm formatting and terminology align with other docs
-
-### Peer Review
-- [ ] **Fresh eyes**: Have someone unfamiliar with the topic review for clarity
-- [ ] **Technical review**: Get approval from subject matter experts
-- [ ] **Editorial review**: Check for grammar, style, and formatting consistency
-
-## Documentation Types
-
-### Quick Reference
-For API docs, component props, and CLI commands:
-- [ ] **Tabular format**: Use tables for parameter lists and return values
-- [ ] **Required vs optional**: Clearly mark required parameters
-- [ ] **Default values**: Include default values where applicable
-- [ ] **Type information**: Show TypeScript types for all parameters
-
-### Tutorials
-For step-by-step guides:
-- [ ] **Clear objectives**: State what the reader will accomplish
-- [ ] **Prerequisites**: List required knowledge and setup
-- [ ] **Numbered steps**: Use ordered lists for sequential processes
-- [ ] **Validation points**: Include checkpoints to verify progress
-
-### Conceptual Guides
-For explaining how things work:
-- [ ] **Big picture first**: Start with high-level concepts
-- [ ] **Visual aids**: Use diagrams or flowcharts where helpful
-- [ ] **Real-world context**: Explain when and why to use features
-- [ ] **Common patterns**: Show typical usage scenarios