Community

An ecosystem turns over because people take part

Textrix extensions, skills and expert packs come from the community. The official side does four things only: discovery, distribution, review and adoption — it touches neither the money nor the data.

What the official side has to provide

Whether an ecosystem can sustain itself comes down to five things. Miss one and developers stop staying.

A feedback channel

Bug reports and feature requests reach developers directly — the bar has to be low, not a code-hosting issue tracker as the only door.

A developer forum

Official responses plus developer-to-developer help — this is what decides whether a community survives.

Work pages

Download counts, ratings, changelogs and compatibility notes — so that good work can be found.

An official adoption path

Good work can be upgraded to a two-way purchase — bought, brought on board, or merged into the core.

A sandbox and declared permissions

Extensions run in a sandbox with permissions declared up front — so one malicious plugin cannot ruin the ecosystem.

How you can take part

No need to wait for the release — these are possible today.

Build an extension

All four contribution layers share one manifest: extensions, skills, tools and expert packs. One manifest is all it takes to publish.

Report a problem or an idea

Write an email describing the scenario you want. The product is still in development, and early feedback is the most useful kind.

Join the waitlist

Get an invitation the moment it opens — or just reply and tell us how you would use it.

Ground rules for taking part

A community that lasts needs a few clear lines.

  • Argue about the work, not the person: debate technical trade-offs, not people.
  • Declare honestly: state an extension’s capabilities, limits and dependencies before publishing.
  • Respect data sovereignty: never design anything that quietly uploads a user’s files.
  • Always exitable: a user can uninstall at any time and the data stays on their own disk.

Get in touch

The product is still in development and official community channels open with the release. Until then, email is the most direct route — for product questions, collaboration or extension ideas.

What you can write about

  • Bugs and rough edges you have spotted — on this website or in the articles.
  • Feature ideas and priorities: what should the first release get right.
  • Partnership and integration enquiries.
  • Opinions on the trade-off articles — agreement and pushback are both welcome.

Common questions

Is there a forum or a chat group today?

Not yet — official channels open with the release. Until then, email is the most direct route.

Can community contributions be paid?

Yes. Pricing and payment go through the developer’s own channel; the platform only records the price and handles discovery and update delivery — it never touches the user’s money.

Will extensions read my files?

Extensions run in a sandbox and their capabilities and permissions are declared in the manifest — you can see what an extension asks for before installing it.

Related

Keep exploring

If you are weighing building on Textrix, these help.

Still in development

Downloads are not open yet. Join the waitlist and we will invite you the moment it opens.

Email-collection mode: submitting opens a pre-filled message in your mail client.