> Am 22.06.17 um 11:16 schrieb Greg Sutcliffe: > > +1 for moving the plugin documentation to the plugins part of the > > website. I think that makes sense, and we can (as with other areas) > > keep the wiki for footnotes, edge cases, and tips. > > > > Greg > > I'd suggest to add a Markdown file to the core repo. I believe code > documentation is better suited to be in the code repo and the > documentation can be reviewed alongside the code change in core by core > maintainers. The website should be more for foreman users. But > theforeman.org is fine with me as well. > > - Timo
Having this info in the codebase itself sounds reasonable but I'd prefer having it on one place with other pages such as template writing wiki. The later is also useful for users and ideally will be moved to theforeman.org one day. If there was a reliable way to sync it from theforeman.org to core codebase, that would we great. If I had to choose between these two, then I find theforeman.org better. I think Google would give better results for potential plugin writers too. -- Marek -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
