Project Roadmap

This document outlines the strategic direction for the project, covering active development initiatives, planned technical improvements, and future explorations. It serves as a guide for contributors and maintainers to understand the evolving goals of the Kobi Kadosh ecosystem.

Active Initiatives

These are the primary areas of focus currently under development, with associated feature branches.

1. Elysia Backend Implementation

• Goal: Establish a robust, dedicated backend API using ElysiaJS. This API will serve as the core data layer for the blog and enable a consumer SDK.
• Purpose: To make blog content, communities, and other data accessible via a standardized API, allowing for diverse consumption methods beyond the static site.
• Key Features:
  • Authentication (Better Auth).
  • Subscription & Waitlist management.
  • Content API for posts and pages.
• Current Branch: claude/complete-elysia-implementation-01BVDS6aTfBEUvznt847NiRV

2. Telegram Monitoring & Integration

• Goal: Create a background pipeline for site health monitoring and notifications via Telegram.
• Purpose: To provide real-time alerts for site downtime or issues.
• Strategy: Implement an adaptive scheduling heuristic that adjusts check frequency based on activity (more frequent checks during high activity/changes, less frequent during stable periods) to optimize costs.
• Current Branches:
  • claude/add-telegram-monitoring-011CUgsa6E7jV81AQBXGB4PU
  • feature/telegram/comments.app

3. Resume Generator Tool

• Goal: Develop a tool to generate tailored resumes.
• Purpose: To encode the maintainer's persona (Kobi) and professional history into the codebase, allowing for the generation of customized resumes for specific roles or contexts.
• Current Branch: claude/resume-generator-tool-01DuKWJPJ9Cvi99ie7neB2Uh

4. New Site Experiences

We are expanding the blog to include new, immersive ways to consume content and connect.

• DevSpace:
  • Concept: A dedicated community space to showcase activities and foster connection around the content.
  • Current Branch: claude/devspace-route-template-011CUwnMVXCLDJuo2zyqsUiV
• My Set:
  • Concept: A curated showcase of the maintainer's workspace, tools, and gear, featuring affiliate integration.
  • Current Branch: claude/create-myset-page-013WZr5LFc2nXrJgtH1Wc8F5
• Audio Playback:
  • Concept: Offering an "Audio Experience" for blog posts, allowing users to listen to content in a podcast style.
  • Current Branch: edj3pe-codex/add-audio-playback-component-to-post

Planned Improvements

These are technical initiatives aimed at hardening the codebase and improving quality of life for developers and users.

• Quality Assurance & CI/CD:
  • Implement comprehensive linting pipelines (claude/linting-pipeline-setup-QDxUn).
  • Expand End-to-End (E2E) testing coverage (referencing claude/qa-tests-documentation-otsrf).
• Performance & Accessibility:
  • Regular audits for Web Vitals.
  • Ensuring full A11y compliance for all new pages.
• CLI Enhancements:
  • Continue expanding the kobi CLI tool to provide more agentic capabilities for managing the blog ecosystem.

Future Explorations

Ideas for long-term evolution and "exceptional blog" features.

• AI Integration: Explore integration with tools like NotebookLM to generate dynamic audio summaries or interactive Q&A interfaces for blog content.
• Agentic Workflows: Further develop the concept of the blog as an autonomous entity that can self-monitor, self-optimize, and assist the maintainer.
• Community Engagement: Deeper integrations for reader interaction, potentially leveraging the Telegram integration for comments or community chats.

Strategic Vision: In the Spirit of the Project

Beyond immediate features, we envision a "living codebase" that embodies the principles of modern, AI-first engineering.

1. The Digital Garden (Knowledge Graph)

• Concept: Move beyond linear blog posts to a networked knowledge graph.
• Implementation: Implement bidirectional linking and visual graph exploration tools (e.g., using D3.js or similar) to show how concepts in different posts connect.
• Goal: Allow readers to traverse "thought trails" rather than just chronological feeds.

2. Agentic IDE & Self-Healing Code

• Concept: The repository itself should be an active participant in its own maintenance.
• Implementation:
  • Proactive Agents: Background jobs that check for outdated dependencies, broken links, or performance regressions and automatically propose PRs.
  • Style Enforcers: Agents that not only lint but rewrite code to match the maintainer's evolving style guide.

3. Open Source & Educational Platform

• Concept: "Learn in Public" on steroids.
• Implementation:
  • Interactive Playground: Embed live code editors (Sandpack/StackBlitz) within blog posts to let readers experiment with the concepts discussed.
  • Mentorship Modules: Dedicated paths for junior engineers to follow the maintainer's learning curriculum.

4. Voice & Conversational Interface

• Concept: A "Talk to the Blog" feature.
• Implementation: An integrated voice agent (using the Elysia backend) that can answer questions about the maintainer's experience, blog content, or technical opinions, synthesizing information from the entire knowledge base.