Create a comprehensive NotebookLM instance for the Console Framework team to serve as a centralized knowledge base and onboarding resource.

NotebookLM Contents Should Include:

Team Survival Guide

• Emergency contacts and escalation paths
• On-call procedures and runbook references
• Common production issues and their solutions
• Quick reference for critical commands and tools
• Team rituals and meeting schedules
• Communication channels (Slack channels, email lists)

Onboarding Documentation

• Team mission and responsibilities
• Architecture overview of Console Framework
• Development environment setup guide
• Code review process and standards
• Testing requirements and best practices
• Deployment procedures and release process
• Access requests checklist (GitHub, JIRA, Jenkins, etc.)

Technical Documentation

• Repository structure and key directories
• API documentation and integration points
• Frontend Operator (FEO) configuration guide
• PatternFly component usage patterns
• Konflux pipeline documentation
• Feature flag management
• Authentication and authorization patterns

Process Documentation

• JIRA workflow and ticket management
• Sprint planning and estimation guidelines
• Definition of Done
• Bug triage process
• Dependency update procedures
• Documentation standards

Knowledge Base

• Frequently asked questions
• Troubleshooting guides
• Lessons learned from incidents
• Best practices and anti-patterns
• Links to external resources and training materials

Acceptance Criteria:

• [ ] NotebookLM instance created and accessible to team
• [ ] Core survival guide content populated
• [ ] Onboarding checklist for new team members created
• [ ] Key technical documentation migrated or linked
• [ ] Team members trained on how to use and contribute to NotebookLM
• [ ] Process established for keeping documentation up to date