Yappa Knowledge Hub (YapHub)

Project Context & Stakeholders

Yappa is a full-service digital agency in Bilzen (Belgium) where multidisciplinary teams (Hub Flow developers, online marketeers, and project managers) build custom web applications and digital platforms.

During daily operations, valuable engineering solutions, framework updates, and client discoveries were continuously shared across Slack channels (#dev, #general) and internal knowledge sessions (YappaWaDoeDa). However, this knowledge was rapidly buried in chat streams.

While Notion (“Het Orakel”) served as Yappa’s permanent documentation archive, manually documenting every insight created too much friction. The assignment was to bridge this gap: allow team members to capture knowledge directly in Slack, process and enrich it with AI summaries, and keep Notion automatically synchronized as the central source of truth.

Stakeholders and academic evaluation

• Company promoter & code reviewer: Davy Dewit (Yappa)
• Hub lead (Flow team): Wesley Lancel (Yappa)
• Project manager: Laura Schrijvers (Yappa)
• Academic supervisor: Mimi Willems (UC Leuven-Limburg / UCLL)
• Degree program: Professional Bachelor in ICT, 2025-2026

Research Questions & Architectural Evolution

The project answered four core engineering research questions:

1. How can internal knowledge be captured without disrupting existing communication habits?
2. How can collected knowledge be structured so it remains permanently findable and usable?
3. How can raw knowledge items be transformed into role-tailored summaries for different team personas?
4. How can the architecture remain extensible to future ingress/egress channels (email, RSS, podcasts)?

Exploration to production MVP

During the first two weeks, I mapped over 50 preliminary flowcharts evaluating Twig dashboards, Craft CMS plugins, monolithic C# engines, and autonomous agent loops (OpenClaw).

Validating a Proof of Concept (~150 Jira story points) proved that decoupling Slack as the ingress layer, Symfony 7.3 as the domain engine, and Notion as the consumption layer delivered the lowest user friction and highest maintainability.

Multi-Layer System Architecture

The platform operates across four decoupled layers:

Key Technical Systems

1. Slack-native ingress & interactive App Home

Using Slack message shortcuts or modal triggers (views/modals/knowledge/saveMessage.ts), users capture text and links directly within their workflow.

The Slack application runs in Socket Mode, establishing an outbound WebSocket connection that eliminates the need to expose public HTTP webhook endpoints to the internet. The App Home tab renders dynamic category lists, subscriber counts, and manual digest generation controls.

2. URL content extraction with SSRF protection

When shared messages contain web links, ContentExtractionService fetches the destination page:

• Validates the target IP address against RFC 1918 private subnets and local loopback addresses to prevent Server-Side Request Forgery (SSRF).
• Enforces a strict 10-second request timeout and verifies text/html headers.
• Isolates main readable article content and strips boilerplate scripts/navigation before passing text to the AI pipeline.

3. Role-based AI summarization & 7-step digest pipeline

The AI service (OpenAIService via symfony/ai-bundle) generates concise 2-3 sentence Dutch highlights using structured prompt templates (HIGHLIGHT_SUMMARY_PROMPT) with a low temperature setting for consistency.

Digests follow an automated 7-step pipeline:

1. Trigger: Cron scheduler or manual Slack App Home button click.
2. Collection: Queries unbundled knowledge items within the configured timeframe (weekly, biweekly, monthly).
3. AI Compilation: Summarizes collected items into categorized highlights.
4. Snapshot Storage: Persists immutable digest records to SQLite.
5. Notion Publication: Builds and pushes rich Notion page blocks via NotionPageBuilder.
6. Recipient Resolution: Maps active subscribers from SubscriptionRepository.
7. Slack Distribution: Dispatches formatted direct message cards with individual DigestDelivery audit tracking.

4. Bidirectional Notion synchronization

The NotionRepositoryManager implements DatabaseResolverInterface to dynamically route requests whether the identifier is a local database integer ID or a Notion UUID. Knowledge items push to Notion immediately upon approval, while scheduled Symfony Messenger commands poll Notion every 2 minutes for updates made directly in the workspace.

Engineering Quality, Testing & CI/CD

Over the 13-week solo engagement (~60 working days), code quality was maintained through strict standards and code reviews:

• Codebase scale: 153 PHP backend source files, 45 TypeScript Slack bot files.
• Static analysis: Verified clean under PHPStan Level 8 with strict types enabled throughout.
• Unit & integration testing: 100% PHPUnit 11 test coverage on core domain entities (Knowledge, Category, Subscription, Digest).
• End-to-end testing: 10+ Playwright E2E test suites executing complete Slack-to-Notion user journeys with mocked external services (NOTION_MOCK=true, OPENAI_MOCK=true).
• Code review rigor: 230+ code review comments addressed across 12 feature pull requests.
• Technical debt reduction: Major mid-internship refactor overhauling 55 files (+3,543 / -11,135 LOC) to eliminate hardcoded dependencies.
• Observability: Distributed Sentry tracing configured across both Symfony and Node.js runtimes with structured Monolog audit trails.