Skip to content

Project Overview

What is Yappa Knowledge Hub?

Yappa Knowledge Hub is an AI-powered internal knowledge management tool designed for the team at Yappa. It solves the problem of scattered information across Slack messages, emails, notes, and deal updates by providing a centralised system for capturing, processing, and distributing knowledge.

Internship Context

DetailValue
InstitutionUCLL University of Applied Sciences
ProgrammeProfessional Bachelor
Duration56 working days (~12 weeks, 3 months)
CompanyYappa
ProjectInternal Knowledge Hub (Kennisverzameltool)

Problem Statement

Internal knowledge at Yappa is currently scattered across Slack messages, forwarded emails, notes, deal updates, announcements, and external content. Information shared "in the moment" becomes hard to:

  • Find later — no central search across knowledge sources
  • Contextualise — different teams need different perspectives on the same information
  • Convert into updates — weekly overviews and digests require manual effort
  • Keep curated — no moderation or quality control mechanism

Vision

Build a central system that makes internal knowledge:

  1. Easy to capture — low-friction submission directly from Slack
  2. Smartly processed — AI summaries tailored per audience role (developer, CEO, marketer)
  3. Actively distributed — periodic digests by thematic list and target group

Core Concepts

Thematic List

A curated stream of resources designed for a specific purpose and audience. Each list has a name, description, target audience roles, default tags, and a digest schedule.

Resource

A single knowledge item submitted by a user — text, URL, PDF, or audio transcript. Each resource carries metadata, tags, and can be assigned to multiple lists.

Target Group

A role-based audience (e.g., Developers, Marketers, CEO) that determines how AI summaries are styled through per-group prompt templates.

Digest

A periodic bundled report per list, generated on schedule (weekly/biweekly/monthly), containing all new resources with their summaries, delivered via Slack.

Scope — 13 Epics, 100 User Stories

The project is structured across 13 epics totalling 100 user stories and 302 story points:

#EpicStoriesSP
01Content Ingestion1239
02Thematic Lists & Organisation922
03AI-Powered Summaries1029
04Periodic Digests / Reports623
05Bot / Service Interaction824
06Configuration & Administration819
07Search & Discovery723
08User / Role Management718
09Analytics & Insights718
10Content Quality & Moderation612
11Integrations & Extensibility624
12Onboarding & Help511
13AI Agent & Orchestration940
Total100302

Priority Breakdown

  • 🔴 Must-have (MVP) — 32 stories (core Slack ingestion, AI summaries, digests, config)
  • 🟡 Should-have — 47 stories (search, analytics, moderation, extensibility)
  • 🟢 Nice-to-have — 21 stories (advanced agents, exports, bulk import)

Tech Stack

LayerTechnologyPurpose
BackendPHP 8.x + Symfony 7API, workers, command bus
DatabasePostgreSQL / MySQLRelational data (Doctrine ORM)
QueueRedis + Symfony MessengerAsync processing
AIOpenRouter / OpenAI / localProvider-agnostic summarisation
PlatformSlack (Google Workspace)Primary user interface
DocsVitePress + MermaidThis documentation site

Stakeholders

RoleResponsibility
InternDesign, develop, test, and document the system
Company MentorProduct guidance, Slack workspace access, feedback
UCLL MentorAcademic supervision, weekly report review
Yappa TeamEnd users, pilot testers, feedback providers

Key Decisions

DecisionChoiceRationale
Primary channelSlackWhere the team already works
AI strategyProvider-agnosticFlexibility to switch models
Ingestion UXMessage Shortcut + ModalLowest friction, no commands to memorise
ProcessingAsync (Messenger)Non-blocking Slack interactions
MVP scopePasted text + AI summaries + DigestsHighest value, lowest complexity