You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 19, 2026. It is now read-only.
I would like to contribute to the PAELLADOC project and help you build an excellent product for the community. Now that I've been using PAELLADOC for a couple of weeks, I wanted to share some ideas and feedback that I have. Please let me know what you think!
As a user, the biggest priority would be cleaning up the .cursor directory. I've noticed some duplicate documents, some still all Spanish, and some with broken links or references. (e.g., .cursor/rules/docs/ has multiple duplicates.)
Translations: IMHO, this should come last. Let's establish a solid framework for English (assuming that's the majority user base) and then create other languages. It would be less work, in the long run, to generate the other languages using a script and language dictionaries.
Standardization: I noticed that some commands use underscores _ and some use dashes - for the name (e.g., GENERATE_CODE and GENERATE-DOC). It would be good to ensure that everything follows a standard naming scheme to make it less confusing and easier for users to remember.
The /docs/PAELLASEO directory and the /schemas/seo-frontmatter.yaml file. Are you using these for testing?
I have a few more ideas, but I don't want to overwhelm you with a gigantic list! So, I'll just leave you with my top 4 for now. 😄
Cheers!
Adam
P.S. - Do you have a roadmap or list of items you want to implement?
Hi Adam, @ahenriksen-inferno
I want to be completely transparent with you - I know the code quality isn't where it should be. PAELLADOC started as an idea I was passionate about, and I needed to capture the momentum before it faded. The plan was always to improve it later with the help of the community.
Your contribution means so much more than you probably realize. You're not just fixing some inconsistencies - you're laying the first stone of what I envision PAELLADOC becoming: "The Development Exoskeleton for AI Teams."
The vision is to create a complete development lifecycle system:
Research & Validation - Helping teams make decisions with confidence
Product Management - Keeping teams aligned with integrated tools
Documentation-to-Code - Eliminating the implementation gap
I launched with what I had because I believe in the core concept, but I always knew it would take contributors like you to help transform it into something truly valuable.
Regarding a roadmap - I'm currently focusing on updating the website with our full value proposition and will be adding a dedicated ROADMAP section to the navigation. If you're interested, I'd love to incorporate your insights into this roadmap.
Would you be open to implementing a +1 criteria system for prioritizing issues and features? This would help us align on what to tackle first, and we could start working together right away on the improvements you've identified.
Your feedback isn't just helpful - it's essential. Each improvement you suggest brings us closer to creating a tool that genuinely improves how AI teams preserve and utilize context.
Thank you for seeing the potential beneath the rough edges.
José
I really appreciate the transparency and understand how small ideas can turn into big projects quickly! That is why I offered my help, as I could sense that you wanted to move fast and were quickly getting buried with the success and interest of the community. I'm happy to help you in any way that I can. Due to my other work priorities, I have about 1-2 hours a day that I can dedicate to the project. Just let me know what you'd like me to work on.
Thank you so much — I really appreciate your support and energy! I’ve just added the +1, and honestly, whatever you decide to jump into will be more than welcome. Your help means a lot, especially now that things are moving fast and a bit of chaos is creeping in. Your eye and experience will be a huge asset.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi, Jose (@jlcases)!
I would like to contribute to the PAELLADOC project and help you build an excellent product for the community. Now that I've been using PAELLADOC for a couple of weeks, I wanted to share some ideas and feedback that I have. Please let me know what you think!
As a user, the biggest priority would be cleaning up the
.cursordirectory. I've noticed some duplicate documents, some still all Spanish, and some with broken links or references. (e.g.,.cursor/rules/docs/has multiple duplicates.)Translations: IMHO, this should come last. Let's establish a solid framework for English (assuming that's the majority user base) and then create other languages. It would be less work, in the long run, to generate the other languages using a script and language dictionaries.
Standardization: I noticed that some commands use underscores
_and some use dashes-for the name (e.g.,GENERATE_CODEandGENERATE-DOC). It would be good to ensure that everything follows a standard naming scheme to make it less confusing and easier for users to remember.The
/docs/PAELLASEOdirectory and the/schemas/seo-frontmatter.yamlfile. Are you using these for testing?I have a few more ideas, but I don't want to overwhelm you with a gigantic list! So, I'll just leave you with my top 4 for now. 😄
Cheers!
Adam
P.S. - Do you have a roadmap or list of items you want to implement?
All reactions