Add new config DOC_FOLDERS to support multiple doc folders

[javidhsueh]

No description provided.

[jckr]

what does this do?

[javidhsueh]

It will source files in the folder into Gatsby system and create File nodes. Later on, gatsby-transformer-remark transforms markdown files into MarkdownRemark nodes.

Here I'm trying to source data from DOC_FOLDER or DOC_FOLDERS

[ibgreen]

Should these all have the same name: 'docs'? Does this affect how we query them?

[jckr]

right now DOC_FOLDER doesn't do anything. ocular will always look into /docs

[javidhsueh]

I think we should expose it explicitly to the users instead of looking into /docs magically.

[ibgreen]

If DOC_FOLDER doesn't do anything let's delete it and use DOC_FOLDERS only? Having two of these does not seem to be in the user's interest.

[jckr]

from our conversation what this does is that this allows to build one single documentation tree from files existing in various folders.
But we'll also want to build several documentation trees (ie not necessarily starting with /docs).
What I'd like is an API that doesn't force us to change the configuration down the road.

[ibgreen]

But we'll also want to build several documentation trees (ie not necessarily starting with /docs).

What use case do you have in mind?

[javidhsueh]

from our conversation what this does is that this allows to build one single documentation tree from files existing in various folders.
But we'll also want to build several documentation trees (ie not necessarily starting with /docs).
What I'd like is an API that doesn't force us to change the configuration down the road.

Right now, it still supports 'DOC_FOLDER' and 'DOC_FOLDERS' at the same time. The 'DOC_FOLDER' will supersede over 'DOC_FOLDERS' if both of them exist.

[ibgreen]

If DOC_FOLDER doesn't do anything let's delete it and use DOC_FOLDERS only? Having two of these does not seem to be in the user's interest.

[ibgreen]

Should these all have the same name: 'docs'? Does this affect how we query them?

[javidhsueh]

• Remove comment
• Remove "DOC_FOLDER" from documentation
• Add messages to warn that some config to be deprecated soon. (DOC_FOLDER)

[jckr]

the use case I have in mind is vis academy which i think is not the only "classic" ocular website with several documentation trees.
in vis academy, not only md files are in different folder, but they are built into different trees with different urls which don't necessarily start with /docs/.

this is in that spirit that i opened #173.

the issue today is that "docs" is not only assumed to be the location of md files and documentation files, but also of the url of all of the documentation. when there are too many pages / too many levels it makes sense to no longer want to have all documentation be under one single tree, even if they can be visible under the search for instance.