Over the last few days, I have started cleaning up the commands, including fixing links, adding links, and primarily adding the calculator compatibility section to the sidebar. Anyway, I was wondering if you guys wouldn't mind helping me, so that it gets done faster? One other thing I was wondering is how we should organize the commands that don't have a parent? For example, I decided to set the parent of Un/Archive to variables, since both commands are used with variables. Other commands aren't so obvious, unfortunately.
I just finished going through all of the command pages we have started, so I think they should all have the pertinent information now. However, some of the commands still need a parent, and I tagged them with needs_parent. This doesn't include the commands that still need a screenshot, though.
I've taken care of most of the commands that needed parents. Of the remaining five, two would go well under a "memory management" page, and three under a "linking" page. Neither of which we have at the moment, though we probably should create them at some point.
Incidentally, I'm not sure I agree with setting the parents of pages like graphscreen or variable types to the command index. They are, or at least they should be, about a lot more than the commands involved, even though it's mostly the command pages that use them as breadcrumbs.
Erm, nothing much. In particular, I think the variables page tree is already fairly close to being finished. But there's a lot you can say about such a topic beyond listing the commands that can be used with it.
I added screenshots for the rest of the operators, but I don't really have any idea about what an appropriate screenshot would be for the zoom commands. Do you have any ideas/suggestions?
Well, the reason I hadn't made those myself back when I made the rest of them is that I had no ideas either. I took a screenshot of the ones I had ideas for.