Guide v Docs

[lorensr]

Let's add a guideline to Contributing.md saying what stuff to put where

Generally docs is what it does, and guide is opinionated long form ("articles") on how to use it? But guide has a good bit of "what it does" too, eg build tool section, mobile.

For example, this should be docs because it's "what it does"? meteor/guide#457

And we've got some overlap, eg with modules, which we should probably keep down, but it makes sense for long form articles to sometimes include information from the docs.

[tmeasday]

It's tricky. Also because the docs existed before the guide, there is a bit of explanatory content in there which probably doesn't really belong in that format.

I think the basic idea is the docs is "just the facts" which includes a lot more detail and completeness around options / edge cases / whatever. The guide is opinionated and tells you more or less just what you need to know to do it in the recommended way.

With that in mind I tend to agree with you about guide#457

[abernix]

Yeah, I agree that meteor/guide#457 (my own issue) should be docs too. There wasn't really a reasonable place in the docs for it. All the information about NPM use was in Guide.

[filipenevola]

I'm closing this issue because it's too old.

If you think this issue is still relevant please open a new one.