OrvyxCommunity

Contribute

Orvyx is built in the open where it matters most: the documentation, the community and the showcases are all written and maintained with the people who use the product. You do not need permission to start.

Ways to contribute

  • Write documentation. Fix a step that no longer matches the product, or write the guide you wish had existed when you started. The docs live in the same repository as the source.
  • Answer questions in the community. Most workflow questions have been asked before, and a clear answer from someone who has run the workflow is worth more than any feature request.
  • Report bugs. Open an issue with what you did, what you expected and what happened. Include the trace id from the response if you have it; it lets a maintainer find the exact request instead of guessing.
  • Submit a showcase entry. Describe a workflow you actually run. The process is below.

How to submit a showcase entry

  1. Check the existing showcase first. An entry that adds a genuinely different setup — a different platform, team shape or constraint — is what the showcase is for.
  2. Write the summary: what you built, how it runs day to day, and the one decision that made the biggest difference. Specifics beat scale; a single-workspace newsletter is as useful as a twelve-account agency flow.
  3. Add tags that describe the workflow, such as the platform, the format or the team shape.
  4. Submit it through the contribution form or as an issue in the repository, and a maintainer will follow up. Entries are published in the showcase once they are checked for accuracy against the product.

Recognition

Contributions are credited to their author. Documentation improvements carry your name in the repository history, showcase entries carry the author line you submit, and sustained contributions are highlighted in community events. If you would prefer to contribute under a team or role label instead of a personal name, say so when you submit.

Core application contributions are by invitation

Contributions to the core Orvyx application happen by invitation, because changes to generation, billing and access control carry obligations that reviews alone cannot transfer. Documentation and community contributions are open to everyone, and an invitation usually starts with one of them.

The source and issue tracker live at github.com/tryaio-com/Orvyx.