Extend scripts to a more general packages management topic

docs/.vitepress/config.js

@@ -24,13 +24,16 @@ export default defineConfig({
 
     sidebar: [
       {
-        text: 'Guide',
+        text: 'Common',
+        items: [{ text: 'Whitespace', link: '/whitespace/' }],
+      },
+      {
+        text: 'Front-end',
         items: [
-          { text: 'Whitespace', link: '/whitespace/' },
           { text: 'Browers support', link: '/browsers-support/' },
           { text: 'Accessibility', link: '/accessibility/' },
           { text: 'Assets bundling', link: '/assets-bundling/' },
-          { text: 'Scripts', link: '/scripts/' },
+          { text: 'Packages management', link: '/packages-management/' },
           { text: 'Styleguides', link: '/styleguides/' },
           { text: 'Tools', link: '/tools/' },
         ],

docs/javascript/index.md

@@ -58,7 +58,7 @@ Add some scripts in your package.json to validate/format files:
 // ...
 ```
 
-See [scripts](/scripts/) for conventions.
+See [scripts](/packages-management/#scripts) for conventions.
 
 ### Related
 

docs/scripts/index.md → docs/packages-management/index.md

@@ -1,6 +1,10 @@
-# Running scripts
+# Packages management
 
-We use [npm](https://www.npmjs.com/package/npm) scripts to run all kind of tasks related to npm packages.
+We use [npm](https://www.npmjs.com/package/npm) to install dependencies and tools.
+
+## Scripts
+
+We use npm scripts to run various commands easily. We're trying to standardize script names across projects, with no regard for the different tools used in the background.
 
 1. Favor npm default scripts such as `start` or `test` over custom ones.
 2. Name common scripts based on what they do, not what tools they run: `test:unit` instead of `jest`