ElementsProject / ElementsProject/elementsproject.org
Contributor Guidelines
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 89
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Hello, Elements Project community!
I'm starting a conversation about how to best manage contributions to the ElementsProject.org website. What is the most appropriate flow for a community-managed, content-oriented resource on the web?
Considerations should include how we manage content updates, bug and issue reports, tasks and resourcing, and who is able to merge (and who is expected to merge) pull requests.
Seeking opinions and discussion.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points; start by reviewing how this website currently handles content updates, bug reports, tasks, resourcing, and pull-request merging. Done is not defined: the thread is seeking community opinions about a contribution workflow rather than requesting a specific documented change.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100