YapHub

Appearance

Weekly report ​

Student:mustafa.sarikaya@student.ucll.be
Study: Professional BachelorMajor: ICT
Company: YappaCity: Bilzen

Activities Week 01 (09/02/2026 - 13/02/2026) ​

Monday (Day 1) ​

On my first day at the internship, I met with Davy Dewit, who provided a tour of the office and introduced me to the Yappa team.

Immediately afterwards, I began researching and integrating into Yappa’s internal tools and infrastructure. This included onboarding for Notion (used for complex documentation and databases), the Manu site, and Jira (for tracking development progress via backlogs, tickets, and user stories). I also set up my professional Gmail and Slack, familiarizing myself with the various channels used for internal communication.

Later, I held an initial brainstorming session regarding the "knowledge sharing tool" mentioned in an email from Wesley. I evaluated whether the project should focus on an AI agent for user experience or a classic Slack bot.

Tuesday (Day 2) ​

I focused on creating flowcharts and continued brainstorming technical solutions. I researched potential technologies for the "KnowledgeHub," specifically the Slack API, Symfony, and Twig.

I met with Wesley Lancel to align on the vision and expectations for the project. He provided two key pieces of advice: Yappa needs a centralized tool to easily share knowledge with specific groups or categories. This system should periodically send reports of the newly added content to relevant users. Wesley explained the core "Input-Processing-Output" flow:

  • Input: Initially via Slack, with future expansions including news articles, RSS feeds, YouTube transcriptions, and podcast audio-to-text.
  • Goal: Create a simplified conceptual flow for the KnowledgeHub to gather feedback from Yappa employees.

Wednesday (Day 3) ​

I initialized the GitHub repository for the "KnowledgeHub" to manage version control and uploaded the project's base files. I also set up a VitePress site to host technical documentation, PRDs, and daily/weekly internship reports.

I conducted further investigation into Slack integration by creating and managing "YapHub," a Slack app/bot via the Slack API portal. This will serve as the future connection point for the Symfony backend. Finally, I began development on the Proof of Concept (POC).

Thursday (Day 4) ​

To define the full scope of the KnowledgeHub, I generated 100 generic user stories in Jira, categorized into various epics.

I continued my research into Symfony, PHP, and Slack bot functionalities. I developed flowcharts to visualize the high-level system, specifically focusing on the "ingestion" of resources (knowledge items) and the "digestion" process (periodic reporting). During this phase, I evaluated different architectural options, comparing OpenClaw (an AI agent layer) against a custom Symfony-Bolt integration.

Friday (Day 5) ​

I began the day finalizing the Proof of Concept. The POC allows users to input knowledge by interacting with the bot via slash commands, app shortcuts, or the App Home dashboard. These items are then tagged for specific lists or categories (e.g., Developers, Marketers, CEO, HR). The working POC utilizes a JavaScript-based Slack bot and a Symfony backend with a SQLite database.

I met with Valerie Witters and received valuable feedback during the first demonstration of the POC. Later, I caught up with Wesley in the office to showcase the progress using the POC. He suggested replacing the SQLite database with Notion, as it is already the primary tool used by the team and would make database management more accessible for everyone internally.

I concluded the day researching the Notion API and planning how to integrate this feedback into the next iteration of the POC.

New skills ​

  • Slack Bolt SDK integration and Socket Mode configuration
  • Symfony 7 service architecture and dependency injection
  • Notion API integration with property mapping
  • ProjectManagement using Jira
  • User interface design in Slack

Useful data ​

Remarks ​

In the first week, I established a foundation for the project. The POC completion demonstrated the technical feasibility of the knowledge management system and validated the chosen architecture. Especially with the Notion backed, which is already used by the team.