Repository navigation
EN Contributing
Arena Agent edited this page Sep 18, 2026
·
2 revisions
Keep pages task-oriented. A good page answers three questions:
- What problem does this feature solve?
- What is the smallest runnable example?
- Where is the authoritative reference and what are the limitations?
هر صفحه بهتر است یک مفهوم را آموزش دهد، مثال قابل اجرا داشته باشد و به مستندات اصلی لینک بدهد.
- Prefer short sections and concrete examples.
- State the version when behavior is release-sensitive.
- Explain why a rule exists, not just its syntax.
- Keep examples internally consistent: use the same command names and file extensions as the CLI.
- Avoid promising behavior that is not covered by tests or the reference docs.
- When updating a feature, update its example and link at the same time.
plix check example.px
plix run example.px
plix build example.px -o exampleFor repository-level changes, also run the relevant Rust and shell test commands from CONTRIBUTING.md. Wiki changes should be small, reviewable commits with a descriptive message.
Learning path: ← FAQ
- Getting Started
- Installation
- Language Reference
- Types and Ownership
- Structs and Traits
- Modules and Projects
- Standard Library
- Error Guide
- Runtime Model
- Architecture
- Compiler Development
- Testing and Tooling
- Cookbook
- Python FFI
- FAQ
- Contributing