GitHub Repository Inventory

Comprehensive inventory of all Juniro GitHub repositories, their purposes, and current status

Architecture: Hybrid Distributed Architecture with AI Agent Orchestration
Strategy: Centralized AI agents with distributed application repositories

📋 Repository Overview

Architecture Strategy

Centralized AI Agent Hub: juniro-platform orchestrates all AI agents
Distributed Applications: Separate repositories for each user application
Shared Infrastructure: Common backend, design system, and documentation
Enterprise Security: Isolated admin and user systems

Documentation Strategy

juniro-docs: Strategic documentation, guidelines, and processes
juniro-design: Interactive component library, implementation examples, and testing
Clear Separation: No duplication between repositories
Storybook-First: Interactive documentation for components

Repository Naming Convention

juniro-web-*: Web applications (parents, providers, admin, partners, public)
juniro-mobile: Cross-platform mobile application (React Native - iOS & Android from single codebase)
juniro-*: Core infrastructure (docs, design-system, platform, api, infra, repository-template)

Repository Status

Repository	Purpose	Status	Owner	Last Updated
`juniro-docs`	Strategic documentation, guidelines, and processes	✅ Active	Juniro	2025-01-21
`juniro-design`	Interactive component library, implementation examples, and testing	✅ Active	Juniro	2025-01-21
`juniro-platform`	AI Agent Hub & Core Platform	✅ Active	Juniro	2025-01-21
`juniro-api`	Backend API services	✅ Active	Juniro	2025-01-07
`juniro-infra`	Infrastructure as Code	✅ Active	Juniro	2025-01-07
`juniro-web-parents`	Parents marketplace	✅ Active	Juniro	2025-01-07
`juniro-web-providers`	Providers growth platform	✅ Active	Juniro	2025-01-07
`juniro-web-admin`	Admin interface	✅ Active	Juniro	2025-01-07
`juniro-web-partners`	Partners interface	✅ Active	Juniro	2025-01-07
`juniro-web-public`	Public website	✅ Active	Juniro	2025-01-07
`juniro-web-launch`	Pre-launch landing pages (waitlist, provider signup)	✅ Active	Juniro	2025-01-12
`juniro-mobile`	Cross-platform mobile app (React Native)	✅ Active	Juniro	2025-01-16
`juniro-mobile-android`	Android mobile app (archived - replaced by juniro-mobile)	📦 Archived	Juniro	2025-01-16
`juniro-repository-template`	Standardized repository template	✅ Active	Juniro	2025-01-08

🏗 Repository Details

1. juniro-docs

Repository: https://github.com/Juniro/juniro-docs
Purpose: Strategic documentation, guidelines, and processes for Juniro's AI Growth Platform
Technology: Docusaurus, React, MDX
Status: ✅ Active and deployed
Owner: Juniro
Maintainer: Co-founder CTO

Contents:
  - Strategic Documentation (Business, Product, Engineering)
  - Process Guidelines (Development, Design, Operations)
  - Brand Guidelines and Standards
  - Accessibility Standards and Compliance
  - Implementation Guides and Best Practices
  - Component Status Tracking
  - AI Prompt Management Framework
  - Financial Documentation
  - Product Strategy Documentation
  - Team Onboarding Materials

Key Files:
  - docusaurus.config.js: Site configuration
  - sidebars.js: Navigation structure
  - docs/: All documentation content
  - blog/: Internal blog system

Documentation Strategy:
  - Focus: Strategy, guidelines, processes, and standards
  - Component Documentation: Referenced via Storybook links
  - Interactive Examples: Point to juniro-design Storybook
  - Implementation Details: High-level guidance only

Deployment:
  - Platform: Vercel
  - URL: [Production URL]
  - Status: ✅ Live and accessible

Last Updated: 2025-01-21
Next Update: When strategic documentation is updated

2. juniro-design

Repository: https://github.com/Juniro/juniro-design
Purpose: Interactive component library, implementation examples, and testing for Juniro platform
Technology: Storybook, React, TypeScript, Tailwind CSS
Status: ✅ Active and deployed
Owner: Juniro
Maintainer: Co-founder CTO

Contents:
  - React Component Library (Button, Typography, Input, etc.)
  - Interactive Storybook Documentation
  - Design Token Implementation
  - Component Testing (Jest, Playwright)
  - Accessibility Testing (WCAG AA)
  - Figma Integration and Fidelity
  - Live Code Examples and Playground
  - Component API Documentation
  - Usage Patterns and Best Practices

Key Files:
  - src/components/: Component library
  - .storybook/: Storybook configuration
  - src/styles/design-tokens.ts: Design token definitions
  - package.json: Dependencies and scripts
  - tailwind.config.js: Tailwind configuration

Documentation Strategy:
  - Focus: Implementation, examples, testing, and interactive documentation
  - Primary Documentation: Storybook (http://localhost:6006)
  - Component Examples: Live, interactive examples
  - API Documentation: Auto-generated from TypeScript
  - Testing: Built-in accessibility and visual testing

Deployment:
  - Platform: Vercel
  - URL: https://juniro-design-f0zfs6787-juniro-projects.vercel.app
  - Status: ✅ Active and deployed
  - Development: http://localhost:6006 (Storybook)

Last Updated: 2025-01-21
Next Update: When new components are added or existing ones updated

3. juniro-platform (AI Agent Hub)

Repository: https://github.com/Juniro/juniro-platform
Purpose: AI Agent Hub & Core Platform
Technology: TypeScript, React, Next.js, LangChain, OpenAI
Status: ✅ Active
Owner: Juniro
Maintainer: Co-founder CTO

Contents:
  - AI Agent Orchestration
  - Core Platform Services
  - Cross-Repository Coordination
  - Design-to-Code Automation
  - Quality Gates & Metrics
  - Authentication system
  - Payment processing
  - Booking system
  - Shared business logic
  - Platform utilities

Key Files:
  - src/: Application source code
  - components/: UI components
  - pages/: Next.js pages
  - api/: API routes
  - lib/: Utility functions
  - agents/: AI agent implementations

Deployment:
  - Platform: Vercel
  - URL: [Production URL]
  - Status: ✅ Active and deployed

Last Updated: 2025-01-21
Next Update: When platform features are added

4. juniro-mobile ✅ CROSS-PLATFORM MOBILE APP

Repository: https://github.com/Juniro/juniro-mobile
Purpose: Cross-platform mobile application for iOS and Android
Technology: React Native, Expo, TypeScript, NativeWind (Tailwind)
Status: ✅ Active
Owner: Juniro
Maintainer: Co-founder CTO

Architecture Decision:
  - Single codebase for iOS and Android (React Native)
  - Replaces separate juniro-mobile-ios and juniro-mobile-android repos
  - Leverages existing React/TypeScript expertise from web team
  - Shares design tokens and types with juniro-design

Contents:
  - Cross-platform mobile app (iOS + Android)
  - Parent portal screens (discovery, bookings, children)
  - Provider portal screens (dashboard, classes, students)
  - Public screens (search, activity details, provider profiles)
  - Push notifications
  - Offline functionality
  - App store deployment (iOS App Store + Google Play)

Key Files:
  - app/: Expo Router file-based navigation
  - src/components/: Mobile UI components (mirrors web structure)
    - shared-core/: Core components (Button, Input, Modal)
    - shared-customer/: Customer components (Cards, SearchBar)
    - parent-portal/: Parent-specific components
    - provider-portal/: Provider-specific components
  - src/tokens/: Design tokens (synced from juniro-design)
  - src/services/: API layer and integrations
  - src/stores/: State management (Zustand)
  - src/types/: Shared TypeScript types

Tech Stack:
  - Framework: React Native + Expo
  - Navigation: Expo Router / React Navigation
  - Styling: NativeWind (Tailwind for React Native)
  - State: Zustand + TanStack Query
  - Forms: React Hook Form + Zod
  - Icons: Lucide React Native (matches web)

Deployment:
  - Platform: Expo EAS / App Store / Google Play
  - iOS: Apple App Store
  - Android: Google Play Store
  - Development: Expo Go for rapid iteration
  - Status: ✅ Repository created, setup in progress

Last Updated: 2025-01-16
Next Update: When initial setup is complete

5. juniro-api (Planned)

Repository: https://github.com/Juniro/juniro-api
Purpose: Backend API services
Technology: Node.js, Express, TypeScript, PostgreSQL
Status: 🔄 Planned
Owner: Juniro
Maintainer: Co-founder CTO

Contents:
  - REST API endpoints
  - Authentication services
  - Database management
  - Payment processing
  - Email services
  - Analytics tracking

Key Files: (To be created)
  - src/: API source code
  - routes/: API routes
  - middleware/: Express middleware
  - models/: Database models
  - services/: Business logic

Deployment:
  - Platform: GCP / Kubernetes
  - URL: [API Production URL]
  - Status: 🔄 Not yet created

Last Updated: TBD
Next Update: When repository is created

6. juniro-web-launch

Repository: https://github.com/Juniro/juniro-web-launch
Purpose: Pre-launch landing pages for parent waitlist and provider signup
Technology: Next.js 15, React 18, TypeScript, Tailwind CSS
Status: ✅ Active
Owner: Juniro
Maintainer: Co-founder CTO

Contents:
  - Parent waitlist signup page (homepage)
  - Provider registration page
  - Thank you pages with referral integration
  - API routes for form submissions

Key Files:
  - src/app/page.tsx: Parent waitlist (homepage)
  - src/app/providers/page.tsx: Provider signup
  - src/app/thank-you/page.tsx: Parent thank you with referral
  - src/app/api/waitlist/route.ts: Form submission handler
  - src/components/: Reusable components (Header, Footer, WaitlistForm)

Integrations:
  - Posthog: Analytics and A/B testing
  - Loops: Email marketing sequences
  - Viral Loops: Referral/waitlist program

Deployment:
  - Platform: Vercel
  - Production URL: https://juniro.com
  - Local Development: http://localhost:4004
  - Status: ✅ Active and deployed

Post-Launch Plan:
  - After product launch, juniro-web-public will take over juniro.com
  - This repo will be archived or redirect to main site

Last Updated: 2025-01-12
Next Update: When landing pages are updated

7. juniro-repository-template

Repository: https://github.com/Juniro/juniro-repository-template
Purpose: Standardized template for creating new Juniro repositories
Technology: Markdown, Shell Scripts, GitHub Templates
Status: ✅ Active
Owner: Juniro
Maintainer: Co-founder CTO

Contents:
  - Comprehensive documentation templates
  - GitHub issue and PR templates
  - Security policies and procedures
  - Development workflow templates
  - Automated setup scripts
  - Environment configuration templates

Key Files:
  - README.md: Comprehensive project documentation template
  - CONTRIBUTING.md: Contribution guidelines template
  - SECURITY.md: Security policy template
  - CHANGELOG.md: Version history template
  - LICENSE: MIT License template
  - package.json.template: Node.js project configuration
  - .env.example: Environment variables template
  - scripts/setup.sh: Automated repository setup script
  - .github/: GitHub templates and workflows
    - ISSUE_TEMPLATE/: Bug reports, feature requests, documentation
    - PULL_REQUEST_TEMPLATE.md: Standardized PR workflow

Features:
  - Automated placeholder replacement
  - Standardized development workflows
  - Security-first approach
  - Comprehensive documentation standards
  - GitHub integration templates
  - Cross-platform compatibility

Usage:
  - Use as GitHub template for new repositories
  - Run setup script for automated configuration
  - Customize placeholders for project-specific information
  - Follow standardized development workflows

Deployment:
  - Platform: GitHub (Template Repository)
  - URL: https://github.com/Juniro/juniro-repository-template
  - Status: ✅ Active and available for use

Last Updated: 2025-01-08
Next Update: When template improvements are made

📚 Documentation Separation Strategy

Clear Separation of Concerns

juniro-docs Repository

Purpose: Strategic documentation, guidelines, and processes

Contains:

✅ Strategic Documentation: Business strategy, product roadmap, engineering architecture
✅ Process Guidelines: Development workflows, design processes, operational procedures
✅ Standards & Compliance: Brand guidelines, accessibility standards, security policies
✅ Implementation Guides: High-level guidance on using the design system
✅ Status Tracking: Component implementation status and progress
✅ AI Framework: Prompt management and AI strategy documentation

Does NOT contain:

❌ Detailed component documentation (referenced via Storybook)
❌ Interactive examples (point to juniro-design)
❌ Implementation code (lives in juniro-design)

juniro-design Repository

Purpose: Interactive component library, implementation examples, and testing

Contains:

✅ Component Library: React components with TypeScript
✅ Interactive Documentation: Storybook with live examples
✅ Design Tokens: Implementation of design system tokens
✅ Testing: Unit tests, accessibility tests, visual regression tests
✅ API Documentation: Auto-generated from TypeScript
✅ Usage Examples: Live, interactive code playground

Does NOT contain:

❌ Strategic documentation (lives in juniro-docs)
❌ Process guidelines (referenced from juniro-docs)
❌ Business strategy (lives in juniro-docs)

Benefits of This Separation

✅ Eliminated Redundancy

Single source of truth for each type of information
No duplicate maintenance between repositories
Consistent information across all sources

✅ Improved Developer Experience

Interactive documentation in Storybook
Live examples and code playground
Auto-generated API docs from TypeScript
Built-in accessibility testing

✅ Better Maintenance

One place to update each type of documentation
Automatic sync between code and documentation
Reduced documentation debt

✅ Clear Ownership

juniro-docs: Strategy, guidelines, processes
juniro-design: Implementation, examples, testing

Cross-Repository References

From juniro-docs to juniro-design

**🎨 View Component:** [Storybook Button Component](http://localhost:6006)
**📖 Full Documentation:** [Storybook Components](http://localhost:6006)
**🎯 Implementation Guide:** [How to use components](./implementation-guide.md)

From juniro-design to juniro-docs

**📚 Brand Guidelines:** [View in juniro-docs](https://juniro-docs.vercel.app/design-system/brand-guidelines)
**♿ Accessibility Standards:** [View in juniro-docs](https://juniro-docs.vercel.app/design-system/accessibility)
**📋 Component Status:** [View in juniro-docs](https://juniro-docs.vercel.app/design-system/component-status)

🔄 Repository Management

Creation Process

When creating a new repository:
Update this inventory document
Add repository to the table above
Create detailed documentation
Set up proper README.md
Configure branch protection
Set up CI/CD pipeline
Add to monitoring systems

Deletion Process

When deleting a repository:
Archive the repository first
Update this inventory document
Remove from monitoring systems
Update any references in documentation
Notify team members
Delete after 30-day grace period

Renaming Process

When renaming a repository:
Update this inventory document
Update all documentation references
Update CI/CD configurations
Update monitoring systems
Notify team members
Test all integrations

📊 Repository Status Legend

Status	Description
✅ Active	Repository is active and in use
🔄 Planned	Repository is planned but not yet created
🚧 In Progress	Repository is being set up
📦 Archived	Repository is archived
❌ Deprecated	Repository is deprecated

📝 Change Log

2025-01-16

✅ Mobile Strategy Update: Consolidated to single juniro-mobile repository using React Native
✅ Renamed Repository: juniro-mobile-ios → juniro-mobile (cross-platform React Native)
✅ Archived Repository: juniro-mobile-android archived (functionality merged into juniro-mobile)
✅ Updated Naming Convention: Reflects single mobile repo strategy
✅ Updated Tech Stack: React Native + Expo + TypeScript + NativeWind for mobile development
✅ Architecture Decision: Single codebase serves both iOS and Android, leveraging team's React expertise

2025-01-21

✅ Documentation Separation Strategy: Established clear separation between juniro-docs and juniro-design
✅ Updated juniro-docs Purpose: Focus on strategic documentation, guidelines, and processes
✅ Updated juniro-design Purpose: Focus on interactive component library, implementation examples, and testing
✅ Eliminated Redundancy: Removed duplicate component documentation from juniro-docs
✅ Storybook-First Approach: Established Storybook as primary component documentation
✅ Cross-Repository References: Added guidelines for linking between repositories
✅ Benefits Documentation: Documented the advantages of this separation strategy
✅ juniro-platform Status Update: Updated from "Planned" to "Active" status
✅ Removed juniro-shared: Eliminated from current strategy as not needed
✅ Repository Cleanup: Removed outdated references to deprecated repositories
✅ Repository Naming Convention: Updated to reflect correct juniro-web-* naming for web applications
✅ Git Workflow Guide: Created comprehensive Git workflow guide for all Juniro repositories

2025-01-08

✅ Added juniro-repository-template repository details
✅ Created comprehensive repository template with documentation
✅ Added automated setup scripts and GitHub templates
✅ Established standardized development workflows

2025-01-07

✅ Created repository inventory document
✅ Added juniro-docs repository details
✅ Added juniro-design repository details
✅ Added planned repositories (juniro-platform, juniro-mobile, juniro-api)
✅ Established repository management processes

Last Updated: 2025-01-16 Maintained by: Co-founder CTO

📋 Repository Overview​

Architecture Strategy​

Documentation Strategy​

Repository Naming Convention​

Repository Status​

🏗 Repository Details​

1. juniro-docs​

2. juniro-design​

3. juniro-platform (AI Agent Hub)​

4. juniro-mobile ✅ CROSS-PLATFORM MOBILE APP​

5. juniro-api (Planned)​

6. juniro-web-launch​

7. juniro-repository-template​

📚 Documentation Separation Strategy​

Clear Separation of Concerns​

juniro-docs Repository​

juniro-design Repository​

Benefits of This Separation​

✅ Eliminated Redundancy​

✅ Improved Developer Experience​

✅ Better Maintenance​

✅ Clear Ownership​

Cross-Repository References​

From juniro-docs to juniro-design​

From juniro-design to juniro-docs​

🔄 Repository Management​

Creation Process​

Deletion Process​

Renaming Process​

📊 Repository Status Legend​

🔗 Related Documentation​

📝 Change Log​

2025-01-16​

2025-01-21​

2025-01-08​

2025-01-07​