python-mocket icon indicating copy to clipboard operation
python-mocket copied to clipboard

Clarify the initial scope of the documentation

Open git-staus opened this issue 2 months ago • 4 comments

A question under #308 went unanswered and I figured further discussion warranted its own issue.

As a new Mocket user, what do you need the most for being successful at integrating Mocket into your test suite? [...] do we need more tutorials, how-to guides, technical reference or explanation, in your opinion?

Within the Diátaxis framework (what the original author went on to call this approach to documentation) I believe tutorials and thereafter technical reference work best: First you want to see what Mocket has to offer (to judge its relevance), and then adapt what you saw to your specific requirements aided by reference documentation. How-to guides also make sense for the latter step, but since Mocket seems to me to solve a relatively homogenous problem, going straight to the reference documentation might work for most. This is just my half-informed guess of course.

The articles and examples listed in the README and the docstrings I found while working on #310 seem to fall in these categories of documentation already! I guess organising them into a single webpage looks better and makes them easier to find and expand upon.

Other new or prospective users of Mocket are have their say here as well!

git-staus avatar Oct 12 '25 20:10 git-staus

Hi @git-staus, now I guess you understand what I meant when I said nobody is really actively contributing here. Feel free to take the lead with this and do what you feel is right.

mindflayer avatar Nov 03 '25 17:11 mindflayer

Yeah, nothing but crickets really... However, even if it's only me, I still end up with decent-ish documentation of where I was in my thinking process.

Re just this issue: I will likely come up with a concrete answer once I get going with my stub at #311. It's still in the pipeline!

git-staus avatar Nov 03 '25 20:11 git-staus

It's still in the pipeline!

Not sure why a couple of job didn't run. Now it's all done, sorry about that.

mindflayer avatar Nov 04 '25 07:11 mindflayer

Oh sorry, I wrote in broken English and we misunderstood each other. I meant to say #311 is still in my personal metaphorical "pipeline" of things to do. "it's still on my agenda" would have been a better phrasing. Funny how it still made sense.

git-staus avatar Nov 04 '25 09:11 git-staus