💖 Thanks for opening this pull request! 💖 The InnerSource Commons community really appreciates your time and effort to contribute to the project. Please make sure you have read our Contributing Guidelines.

If you are submitting a new pattern, the following things will help get your pull request across the finish line! 🏁

• Confirm that you have used our pattern template. Please remove any placeholder text and sections that your pattern did not need.
• We run a number of automated checks on your PR. Please review the output of those checks on the PR itself, and see if any issues got flagged that you can fix yourself.
• Make sure you have added your new pattern to the list of patterns in the main README.md. If you are unsure where to add your pattern, just let us know by commenting on your PR and we will help you.

This project has a small number of maintainers, volunteering their time to this project. So please be patient and we will get back to you as soon as we can. If we don't acknowledge this pull request after 7 days, feel free to chat to us about it in our Slack workspace.

@ovas04 I put up a preview of your Spanish content on our staging site. There you can check how it looks like in our hosting platform (we use gitbook): https://innersourcecommons.gitbook.io/innersource-patterns-staging/es-test

FYI I had to copy your branch into our repo, so that I could generate this preview. If you want to make changes, you can make them to your own branch though (this PR here).

Besides that I will try to find somebody who can do a review of the content in Spanish (as I don't speak that language). Or do you have somebody that would be interested and willing to review your Spanish translations?

@ovas04 and @rmarting thank you for your great work on this.

You can just let me know when you feel this translation is good enough to be released. Does not have to be perfect! At least in my mind, having "a translation" is already a lot better than what we have now (which is none haha). I am assuming that at least for part of the Spanish speaking community it will be a lot easier to consume this material in their native language.

So you just tell me when we are good to go. Then I will do the remaining administrative work to get the Spanish translation released on our production site.

And of course, we can always fix other glitches in an iterative fashion after this, if we like.

PS: I will be at a conference for a couple of days now, and might not be a all that responsive.

I would like to take a few days more to complete the review. In general, looks great, just to complete the reading and highlight the most important things. Does it work for you before releasing the whole new Spanish site?

TL;DR: LGTM

The content is good enough and there is always space for improvement, but the content is live and the changes should be minimal (as Spanish native speaker some sentences could be changed, but it is fine). I reviewed the whole content from the PR layout, and I would like to take a look of the testing site including the whole content (and reviews done) before publishing online. Then I can confirm and approve everything.

I would like to congratulate @ovas04 for his amazing job and flexiblity to adapt my comments. I know that he is the main contributor, just wondering if I could be part of the footer to support in the future any new translation. Suggesting from the ignorance about the rules to add names in the translated pages.

- **2025-04-03** - Traducción [Roman Martin Gil](https://github.com/rmarting)

PS: Just reported the #788 to satisfy the workflows. Not sure if it is a blocker to promote the content.

Of course, @rmarting! I was actually going to ask you about that. Give me a couple of hours, and I’ll update everything accordingly.

You two are amazing. It was very cool to see this smooth collaboration from the sidelines :)

I can get this PR merged by the end of the week and will then bring the Spanish translation live.