[Docs] Form Authoring Recommendation Docs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.7k
- Forks
- 682
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 7
Description
This document should outline the two approaches enabled by Form:
- Form first
- Field first
Where field-first is more JSX template heavy and form-first is more standard schema focused.
We should provide an official recommendation for form-first.
However, those that prefer field-first APIs or need one-off behaviors can still use fields; it just centralizes more logic in your JSX
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Form authoring documentation and review the existing guidance for form-first and field-first usage. Document both approaches, explain that form-first is the recommended schema-focused option while field-first suits JSX-heavy or one-off behavior, and verify that the recommendation is clear to readers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100