i am making a kde app called kookkool

Development
1

I’m Muhammad (aion), a developer and long-time fan of the KDE ecosystem. I’ve just finished building my first “big” project: KookKool.

What is KookKool? KookKool is a crowdsourced recipe-sharing application built with Kirigami and KNewStuff. My goal was to create a clean, ad-free, community-driven space for sharing recipes, with built-in features for dietary category validation and ingredient filtering (to keep things focused on food, not brands).

The Challenge: The app is functional and stable, but it currently lacks a visual identity. As this is my first major project, I’m hoping to find someone in the community who might be interested in helping design a logo/icon.

What I’m looking for:

  • A clean, modern icon that fits the KDE Plasma “look and feel.”

  • Something that represents the intersection of cooking/recipes and the KDE spirit.

Project Links:

If you’re a designer interested in helping a new project get off the ground, or if you have any feedback on the project itself, I’d love to hear from you. Thank you for your time and for all the great work the KDE community does!

Best regards, Muhammad (aion)

2

if you are interested, KDE already has a recipe app which could use maintainers. Utilities / Kookbook · GitLab

3

@sune is the (main) dev behind Kookbook, it sounds like if the two of you could join forces, @aion , you could make a really cool

As someone who occasionally uses Kookbook and used a few other apps before, I would just ask that the recipe format is in a standard format:

  • either a common recipe format that is used by other recipe apps and services
  • or a markup format, such as MarkDown (CommonMark) that can be easily searched through and edited by generic tools
4

BTW, you have a typo in the URL. The actual URL is:

5

actully kookkool is for sharing reciepies not just keep the on local mechine and it follow KDE HIG human interface guidelines and i would love to collab with @sune

6

Sune here.

Feel free to look into kookbook.

It is using semi-structured markdown for interpreting recipes. It comes with two GUIs; a desktop one built with qtwidgets (and the one that has gotten the most love) and a kirigami version mostly for mobile (that is slightly underloved)

So far, kookbook have explicitly not cared how the recipes end up on your disk - but I have thought of at least the possibility of importing single recipes into the folder structure.

My recipe-collection is unfortunately in danish, so sharing it might not make it too understandable for others.

But feel free to poke around in the source code.

7

Hi Sune,

Thank you so much for the warm welcome and for pointing me toward the Kookbook source code! I’ve been digging through your project, and it’s a great example of clean architecture, especially your approach to semi-structured Markdown.

I would love to collaborate. My current project, KoolKool, was born out of a desire to add a “community layer” and a more mobile-first interaction to the recipe-sharing experience. Seeing as you’ve already mastered the core logic and parsing, I think there is a huge opportunity to bridge our efforts rather than building two separate tools.

To be transparent about how I work: I’m 14 years old and I’m currently on a journey of learning C++ and Qt. I use AI models to help me generate code, but I make it a strict rule to read and review every single line—I treat it like a deep code review. It takes me longer, but it’s how I’m building my foundation and understanding the architecture.

Regarding the backend, I’ve decided to move forward with Supabase for KoolKool. Managing a custom KDE backend has been a bit of a hassle for me as I’m getting started, so Supabase gives me a much faster way to handle the community features—user accounts, real-time recipe sharing, and an audit-logging system (to track “who” changed “what” and “when,” similar to how Git tracks commits).

My background is actually in writing and communication, so while I’m learning the technical side, my true strength is in building connections, creating user narratives, and simplifying complex features into approachable experiences. I’d love to help with the documentation, the community strategy, and perhaps the Kirigami mobile UI that you mentioned was a bit underloved.

I’m very interested in how we could eventually integrate a community backend while keeping the flexibility of your local-file/Markdown approach.

Could you let me know the best way to start contributing? Should I take a look at the current issues on your repo, or would you prefer I send over a summary of my current codebase so we can identify the best place for me to jump in?

Best regards,

[Aion]