YapHub

Appearance

Weekly report ​

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

Activities Week 04 (02/03/2026 - 06/03/2026) ​

Monday (Day 16) ​

Today I happened to be late because of a flat tire, but I managed to make it before the daily standup started.

I spent some time today reviewing the code review comments left by Davy regarding the Symfony server. I addressed the concerns he brought up and spent the rest of the day working on the AI summaries features of the MVP.

Tuesday (Day 17) ​

I merged a couple of PRs today that Davy had finished reviewing. I also received feedback about the Notion integration suggesting that I should use an SDK package instead of using the API directly. Consequently, I ported all the services from direct API calls to the SDK package. I also spent some time working on the AI summaries features of the MVP.

Wednesday (Day 18) ​

In the morning, I pushed the requested changes regarding the Notion PR, and they are currently awaiting review. Around noon, a speaker came and gave a presentation about AI. I found it very informative as they explained the more corporate side of AI and how it can be used to improve productivity and efficiency. It also opened my eyes to how companies see AI and how they use it in their daily operations.

The rest of the day was spent testing out the AI summary features of the MVP and refactoring the PRs based on Davy's code review comments.

Thursday (Day 19) ​

Today I pushed the changes for the Notion integration with services and mappers in three PRs. Davy reviewed them and left a few comments in the afternoon. I spent the rest of the day refactoring the PRs based on Davy's code review comments, while continuing to work on the AI summaries.

The backend infrastructure for the AI summary feature is currently in place, and I am working on the frontend in Slack to define how the interaction should work. Users can now create a summary using a template based on a Category (Thematische Lijst) and Role (Doelgroep). After the generation is complete, the user receives a direct message (DM) from the bot with options to edit the summary directly or regenerate it with additional information. All of this data is stored in the Notion database. The Notion databases are available here: https://www.notion.so/YapHub-Links-31ae292a15d5808da7bae92680db3518

Friday (Day 20) ​

In the morning, I finished addressing all the code review comments brought up by Davy in the Notion PR and merged it. I then spent the rest of the day working on the AI summaries.

I also experimented in Notion, specifically focusing on designing the database views. Notion offers numerous combinations for structuring data displays, and I explored various combinations of filters, groups, layouts, and properties. I created around 20 database views across the seven tables in the database (Knowledge, Categories, TargetGroups, AiSummaries, PromptTemplates, and DigestReports).

I also managed to finish the AI summaries in the Symfony backend along with interfacing with Slack. Now, upon submission of a knowledge item, the user is sent a DM containing the generated summaries. They are given the option to regenerate the summary with additional comments or modify it directly. I also implemented Modal Views in Slack, enabling users to view, edit, and regenerate summaries seamlessly from within the Slack interface.

New skills ​

  • Refactoring API implementations to use SDK packages
  • Designing and configuring Notion database views (Filters, Groups, Layouts)
  • Developing interactive Slack Modal Views for user interactions

Useful data ​

Remarks ​

This week was heavily focused on refining the Notion integration and building out the AI summary features. Porting the API calls to the Notion SDK was a significant architectural improvement requested during code review. The addition of interactive Slack Modals has greatly enhanced the user experience by allowing direct manipulation of the AI summaries seamlessly from within Slack.