Welcome to paelladoc Discussions!

[jlcases]

👋 Welcome to PAELLADOC Discussions

This space is designed to connect developers, product managers, and technical teams interested in improving knowledge management and documentation in AI projects.

🚀 Purpose of this space

PAELLADOC addresses a crucial problem: the loss of context and knowledge in technical projects, especially those using AI. In these Discussions we aim to:

• Share structured documentation strategies (MECE)
• Solve questions about implementation and best practices
• Showcase use cases and implementation examples
• Collaborate on improving and expanding PAELLADOC
• Connect with other teams facing similar challenges

📂 Available categories

• 📣 Announcements: Official updates and new releases
• 💡 Ideas: Proposals for new features or improvements
• ❓ Q&A: Technical questions about implementation and usage
• 🧠 Knowledge Sharing: Documentation strategies and knowledge management
• 🙌 Show and tell: Show how you're using PAELLADOC in your project

🤝 To get started...

Introduce yourself in the comments and tell us:

1. What type of project(s) are you developing?
2. What challenges do you face with documentation or knowledge management?
3. What do you hope to achieve with PAELLADOC?

We look forward to building together a community that transforms how we manage technical knowledge!

[KamilKozera]

Hi,

I'm currently developing a GUI wrapper for Apache ECharts. Since the library has an extensive and complex configuration system, it's essential to provide the right context when working with an AI. I've experimented with PAELLADOC, but I'm having difficulty understanding and applying the process effectively.

What I really need is a complete, structured workflow for developing the application—from defining tasks or user stories to using those to generate code with the help of AI. I'm also unsure how to translate documentation into practical prompts that produce usable code.

A step-by-step video showing a practical example of working with AI to generate code from PAELLADOC documentation would be extremely helpful. For example I have used PAELLA [app name] and I have documentation ready for project. Then I GENERATE_CODE from the documentation. But how to proceed from here and generate the docs (and the code from the docs) for new features etc?

[jlcases]

Thank you for your interest KamilKozera, Your use case with Apache ECharts is exactly the kind of complex documentation challenge we designed this for.
I completely understand the need for a clearer workflow demonstration. You're not the first person to request this!
To be honest, I'm a developer, not a YouTuber - videos aren't my strong suit! I'm actually looking for someone on Fiverr right now who can help create a proper tutorial video showing the complete workflow you described:
Starting with PAELLA
Documentation structuring
Using GENERATE_CODE
Iterative development
While I search for the right person to create this content, here's what I can suggest for your ECharts wrapper:
Document each component separately using the Component Specification template
For configuration options, the Technical Specifications template works well
Use Architecture Decision Record to document why you're exposing certain options
Would you be interested in being a beta tester for the video tutorial once it's ready? Your feedback would be invaluable since you have a real use case.
In the meantime, feel free to ask specific questions in GitHub Discussions - I'm much better at writing responses than making videos! :)

[KamilKozera]

That's for an answer. Yes, I can be your beta tester, feel free to reach me out.