Bring over the last bits of info from old docs on package management interop (#276)

Author: chenglou

data/sidebar_manual_latest.json

@@ -46,7 +46,8 @@
     "inlining-constants",
     "use-illegal-identifier-names",
     "generate-converters-accessors",
-    "browser-support-polyfills"
+    "browser-support-polyfills",
+    "libraries"
   ],
   "Build System": [
     "build-overview",
@@ -56,8 +57,7 @@
     "build-performance"
   ],
   "Guides": [
-    "converting-from-js",
-    "libraries"
+    "converting-from-js"
   ],
   "Extra": [
     "newcomer-examples",

pages/docs/manual/latest/libraries.mdx

@@ -1,15 +1,25 @@
 ---
-title: "Libraries"
-description: "ReScript libraries"
+title: "Libraries & Publishing"
+description: "Install & publish ReScript packages"
 canonical: "/docs/manual/latest/libraries"
 ---
 
-# Libraries
+# Libraries & Publishing
 
-ReScript libraries are just like JavaScript libraries: hosted on [NPM](http://npmjs.com).
+ReScript libraries are just like JavaScript libraries: published & hosted on [NPM](http://npmjs.com). You can reuse your `npm`, `yarn` and `package.json`-related tools to manage them!
 
-If you can't find what you're looking for: sometimes **you don't need a wrapper** to use a JS library:
+## Tips & Tricks
+
+### Publish
+
+We recommend you to check in your compiled JavaScript output, for its [various benefits](interop-with-js-build-systems.md#popular-js-build-systems). If not, then at least consider publishing the JavaScript output by un-ignoring them in your [npmignore](https://docs.npmjs.com/cli/v7/using-npm/developers#keeping-files-out-of-your-package). This way, your published ReScript package comes with plain JavaScript files that JS users can consume. If your project's good, JS users might not even realize that they've installed a library written in ReScript!
+
+### Find Libraries
+
+Search `rescript`-related packages on NPM, or use our [Package Index](/packages).
+
+If you can't find what you're looking for, remember that **you don't need a wrapper** to use a JS library:
 
 - Most JS data types, such as array and objects, [map over cleanly to ReScript and vice-versa](shared-data-types.md).
 - You also have access to the familiar [JS API](api/js).
-- You can use a JavaScript library without needing to bind to them first. Check the [`external`](external) page.
+- You can use a JavaScript library without needing to install dedicated binding libraries. Check the [`external`](external) page.

pages/docs/manual/latest/shared-data-types.mdx

@@ -21,6 +21,7 @@ Unlike most compiled-to-js languages, in ReScript, **you don't need to write dat
 - Record. Record compiles to JS object. Therefore you can also treat JS objects as records. If they're too dynamic, consider modeling them on the ReScript side as a hashmap/dictionary [`Js.Dict`](api/js/dict) or a ReScript object.
 - Object. ReScript objects are JavaScript objects, vice-versa.
 - Function. They compile to clean JS functions.
+- Module. ReScript files are considered top-level modules, and are compiled to JS files 1 to 1. Nested modules are compiled to JavaScript objects.
 - Unit. The `unit` type, which has a single value `()`, compiles to `undefined` too. Likewise, you can treat an incoming JS `undefined` as `()`.
 
 <!-- TODO: talk about poly variant -->

pages/docs/manual/v8.0.0/shared-data-types.mdx

@@ -21,6 +21,7 @@ Unlike most compiled-to-js languages, in ReScript, **you don't need to write dat
 - Record. Record compiles to JS object. Therefore you can also treat JS objects as records. If they're too dynamic, consider modeling them on the ReScript side as a hashmap/dictionary [`Js.Dict`](api/js/dict) or a ReScript object.
 - Object. ReScript objects are JavaScript objects, vice-versa.
 - Function. They compile to clean JS functions.
+- Module. ReScript files are considered top-level modules, and are compiled to JS files 1 to 1. Nested modules are compiled to JavaScript objects.
 - Unit. The `unit` type, which has a single value `()`, compiles to `undefined` too. Likewise, you can treat an incoming JS `undefined` as `()`.
 
 <!-- TODO: talk about poly variant -->