Contribution Guidelines

Dev Foundry improves through community contributions. If you see something unclear, outdated, or missing, propose a fix.

What to contribute

• documentation updates and clarifications
• process improvements for events and operations
• templates for updates, demos, and collaboration
• bug fixes in docs site structure or links

Contribution workflow

1. Open an issue (or comment on an existing one) with the problem and proposed change
2. Create a branch and make focused edits
3. Open a pull request with:
   • what changed
   • why it matters
   • any follow-up work
4. Respond to review feedback and iterate quickly

Writing standards

• Keep language clear, direct, and actionable
• Avoid fluff, buzzwords, and vague claims
• Prefer examples and concrete expectations
• Write for builders who need clarity fast

Scope discipline

Keep each pull request scoped to one problem area when possible. Small, clear changes are easier to review and merge.

Community contribution norms

• Assume positive intent
• Give feedback on ideas, not people
• Prioritize shipping useful improvements over perfect drafts