documentation versioning
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 56
- Forks
- 180
- PR merge metrics
- No merged PRs in 30d
Description
Hi. Thank you for PEST, really enjoy working with it.
Since version 3 of PEST has already been released, I would like to ask if you are planning to introduce versioning for the documentation on the website, and if any help is needed with this? Currently, it's unfortunately difficult to understand which feature is available in which version in the documentation..
thank you
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
No files or tests are named. Start by reviewing the documentation website structure and how Pest versions are currently represented; define the versioning approach and its scope before implementation. Done means readers can identify which features are available in each documented Pest version.
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