What are some guidelines for releasing a package, mostly in regards to creating the documentation, if it's really necessary or just a readme file, or what is really expected?
@vlg There are no strict guidelines beyond a readme, but most people would like to have some real documentation beyond that. It depends a bit on what the package does, of course.
Designing a logbook for diabetics, provides graphs, too. Wanted to make it pretty and automated. There were only 2 other packages two had some similar and they could use some work, imo.
For example, I'm not sure whether I should but color options in the preamble of a temple.tex or keep that clean and put everything in the .sty for the person to edit it.
@vlg Documentation on how to use and provided macros would be appreciated, I guess. It doesn't have to explain how thinks work in detail, just what is available at the user level and how to use it.
@vlg editing the sty file shouldn't be necessary. Make options available either via package options or with macros.
Would you happen to know how package documentations are made? Is it a template, because most seem similar- with the macros on the left margin and all that
@vlg Personally I draw a big distinction between user documentation and code documentation, and the 'standard' that @JosephWright refers to is appropriate for code documentation but not necessarily for user documentation.
@vlg don't assume people will edit a .sty file that make's things difficult in most setups
@vlg that is probably doc format which is common as it's distributed with the core latex release (and documented in the latex companion book) and used for the latex sources
