StDoodle
Minion
Sally; as I mentioned in the other thread, I've reconsidered my plan of attack. The "main" wiki documentation on non-ash stuff will likely do a lot of linking to your guide, but it does seem like a better idea to keep the two separate. The "main" wiki stuff will simply be a list of what's available and how it works, for the most part. Very spartan, etc. Your guide functions well as a walk-through, so it should be kept on its own. My idea is that the main wiki documentation will be for those who are familiar with the basics and a great deal of KoLmafia (regular users), but a good place to look up info they aren't familiar with. If someone simply doesn't understand what to do at all with certain functionality, then the guide would be the place to go.
It seems like you've probably already had this same thought yourself, but just in case, don't bother trying to cram in every little command and every feature. The guide so far seems great for getting to know your way around KoLmafia, and be comfortable using it and understanding what it's doing. The main wiki pages can take care of all the "little" stuff, obscure commands, special-case syntax, etc. Again, it appears you've reached this conclusion well ahead of me (I've been really busy lately ), so probably nothing new.
There is something new I could use your help on, though. (and / or Bales, possibly) I would like to make it easier to link between various pages of the guide and main wiki documentation (none of which has been written yet) on the main program. As such, I want to make sure stuff isn't going to get moved around from one page to another in the guide, or if it is, come up with a good way to reference each section such that I can make templates to handle the linking. Don't worry about the technical details, I just want to know how you envision the organization of the guide playing out, and whether or not there's a good chance that certain sections will be moved from one page to another in the future.
Also, as I mentioned in the wiki thread, I've finally figured out how to get dynamically collapsible menus working on the wiki! I'm not sure how well I can add support for certain advanced features (such as initial expansion state), but I can certainly convert your entire table of contents / guide organization into a simple one-line template if you so desire. Ideally, I could even figure out a way to reference certain parts of the hierarchy such that you could add a single line to the bottom of each page of the guide with a "Next / Previous / Main" link that automatically updates when the structure changes (of course, the template would need to be updated, but just the one page vs. every dependent page).
Any thoughts & input you have on this would be appreciated. Also, I'm not going to go ahead and mess with anything unless I get a go-ahead from you or Bale.
It seems like you've probably already had this same thought yourself, but just in case, don't bother trying to cram in every little command and every feature. The guide so far seems great for getting to know your way around KoLmafia, and be comfortable using it and understanding what it's doing. The main wiki pages can take care of all the "little" stuff, obscure commands, special-case syntax, etc. Again, it appears you've reached this conclusion well ahead of me (I've been really busy lately ), so probably nothing new.
There is something new I could use your help on, though. (and / or Bales, possibly) I would like to make it easier to link between various pages of the guide and main wiki documentation (none of which has been written yet) on the main program. As such, I want to make sure stuff isn't going to get moved around from one page to another in the guide, or if it is, come up with a good way to reference each section such that I can make templates to handle the linking. Don't worry about the technical details, I just want to know how you envision the organization of the guide playing out, and whether or not there's a good chance that certain sections will be moved from one page to another in the future.
Also, as I mentioned in the wiki thread, I've finally figured out how to get dynamically collapsible menus working on the wiki! I'm not sure how well I can add support for certain advanced features (such as initial expansion state), but I can certainly convert your entire table of contents / guide organization into a simple one-line template if you so desire. Ideally, I could even figure out a way to reference certain parts of the hierarchy such that you could add a single line to the bottom of each page of the guide with a "Next / Previous / Main" link that automatically updates when the structure changes (of course, the template would need to be updated, but just the one page vs. every dependent page).
Any thoughts & input you have on this would be appreciated. Also, I'm not going to go ahead and mess with anything unless I get a go-ahead from you or Bale.