Documentation style

Open
#236 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Review the documentation at https://psignifit.readthedocs.io/en/latest/ and identify inconsistent use of voice, such as “we” versus “you need to,” along with structural differences across sections. Done means the language and structure are made consistent while preserving the existing tutorial-style approach.

Written by the indexing model from the issue text.

Description

From @guillermoaguilar :

Now about the documentation, https://psignifit.readthedocs.io/en/latest/?badge=latest it is complete and 100% usable, but there were some concerns raised by @otizonaizit last time, that the language or structure might not be "standard" or at the same level of other software packages.

As I counterargument, I say that the package is very specific, it does 1 thing: psychometric function estimation. In that sense it is different from numpy or scipy, which are much more general and thus the documentation should fit many more needs. That's why I think a 'tutorial' style is ok. Still the language
at times is mixed (e.g. "we", "you need to"), and this should be made uniform.

Dominant language
Python
Stars
66
Forks
26
Avg merge
9m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wichmann-lab/python-psignifit

All issues in wichmann-lab/python-psignifit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.