posit-dev / posit-dev/open-source-website
Create documentation for contributors
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 55
- Forks
- 24
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 17
Description
- Adding and updating software, people, events, videos, cheatsheets, blog posts
- Conventions and style guide
- Frontmatter YAML
- Various shortcodes
- Querying items, json-logic
- Scripts
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
No files, tests, or entry points are named. Start by reviewing the repository structure and existing contributor-facing material, then cover the listed topics—content updates, conventions, YAML frontmatter, shortcodes, querying, json-logic, and scripts—until each has documented guidance and the checklist is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100