It is significantly more difficult to write a 'how to' guide than people think, even if you are proficient in use of the product. This is especially true in computer programs that give you wide options.
As Peter alluded to, the problem is that if you are writing a 'how to' guide, it is because you are trying to explain how to use something that lends itself to exploration without consequence to a person who doesn't want to explore. Because of that, it requires a lot of handholding, screenshots, and exploration of most of the facets of the program in detail. That all takes time, effort, and lots of skull sweat. What may be inherently obvious to you won't be to a noob, so you have to plan for that. You have to proofread, then let someone else do it, then preferably run through it yourself, following the instructions exactly as you wrote them to get the intended result.
Sounds a lot like making good instructions for building a kit, right?
Or to put it another way, imagine doing a build thread, except you're not only doing the build, documenting it throughly, but you're showing different techniques for the same build ("Here's what wood glue does for ya...now lets use epoxy and build it AGAIN...").
I've had to do plenty of this kind of writing for a combat flight simulation that has an open structure...and people still astonish me with how little skull sweat they are willing to put in to be able to run custom content.
Simply put, if you have a high school level understanding of the English language and physics, have progressed in your rocket building skills to be able to create and successfully fly scratch build LPR models, and can navigate these forums without crashing your computer, you have MORE than enough skills to design and build a rocket in OR. Technical issues getting OR to run might be a different story and could require specialized knowledge...but that's not what this discussion is about.
FC