canonical / canonical/vanilla-framework

docs: clarify the contribution process

Open
#4,905 3 comments 1 reaction 0 assignees View on GitHub
Documentation 📝 P3 Triaged Triaged: Pragma
Dominant language
HTML
Stars
983
Forks
216
Avg merge
3d 13h
Merged PRs (30d)
3

Description

As a developer, I want to have clear guidelines when a component/new styles should be upstreamed to vanilla, and what's the process in detail. What are the criteria for adding such component?

We should clarify the contribution process, including the fact that we want to err on the side of upstreaming new components.

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named in the issue. Start by finding the repository's contribution guidance and component or style documentation; done means the criteria and detailed process for upstreaming are clearly documented, including the preference to err on the side of upstreaming new components.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html, sass
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.