Hey @garanews!

What are the steps to create a new resource, in terms of mandatory files to be added/modified?

For new resources (topics?), I would suggest introducing them as ideas here in the "Discussions" section of this repo. Me or someone from my team would take a look and decide whether the proposed topic is worth move forward on.

You're always welcome to create PR for a new topic if you wish, but I can guarantee that it will be considered after I've conferred with my team.

About the topics there are grouped by language such as C++, Go, R but there are like a sub topic (likely libraries) such as Python:Numpy , Python:Pandas : what is the distinguish reason to have or not to have a library?

The current version of Docs allows us to structure our content such that:

• A single topic (be it a language or a library, etc.) can have many concepts. (content/topic/concepts/)
• A single concept can have many terms. (content/topic/concepts/concept/terms/)

This structure is sensible, but a bit rigid if you ask me. For the moment, we've used a sort of workaround by employing the colon : to keep, for example, Pythonic topics close to one another.

My team decided to set up NumPy and pandas as their own distinguished topics because they contain many concepts that bear out many terms. A few examples include:

• ndarray and dtype objects (NumPy)
• [pyplot] module (Matplotlib)