On Thursday, May 10, 2012 11:56:15 AM UTC-7, Ken Barber wrote: > > > 1. How do I address the problem of forge vs docs site redundancy? Not > sure > > that the above redmine area is the correct place > > Its a good enough place to start. If the documentation overlaps or > says two different things its a fair place to cover it. >
Okay, I'll keep that in mind for future reference. > > 2. The trouble with the bug I filed, though.. is that personally, I > think > > the documentation in that area could do with a *Major* rewrite. > > I filed some stopgap measures, but a rewrite is called for. > > It would not make sense to do that until the "forge vs docs site" issue > is > > decently resolves, though. > > > > Additionally, I do have some experience writing online documentation, > and > > could potentially contribute. > > The bug system is not adequate for doing that, though. > > On that URL I gave you: > > http://projects.puppetlabs.com/projects/puppet-docs > > There is a link on how to contribute: > > http://docs.puppetlabs.com/contribute.html > Funily enough, I just read that. It mentions using git, and remote branches, for direct edits... but it does not mention how to actually *view* your changes in a webbrowser, that I can see. (that is to say, viewing how the complete page will look after your edit) It only seems to mention (fork it) (make your edits) (commit) (submit redmine bug with branch url) -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/LqISOhM9i7AJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
