Merge pull request #252 from HOSTED-POWER/BjarneVO-KBrestructure

Bjarne vo k brestructure

Author: BjarneVO

…gies/CMS & Frameworks/MedusaJS/index.yml …ies/CMS & Frameworks/Medusa.js/index.ymlTechnologies/CMS & Frameworks/MedusaJS/index.yml renamed to Technologies/CMS & Frameworks/Medusa.js/index.yml Technologies/CMS & Frameworks/MedusaJS/index.yml renamed to Technologies/CMS & Frameworks/Medusa.js/index.yml

@@ -1,4 +1,4 @@
-label: MedusaJS
+label: Medusa.js
 order: 80
 icon: apps
 expanded: false

Technologies/CMS & Frameworks/Medusa.js/readme.md

@@ -0,0 +1,6 @@
+**Medusa.js** is an open-source, headless eCommerce platform built in JavaScript and Node.js, designed to give developers and merchants a highly flexible, API-first foundation for building custom online commerce experiences. It features a modular architecture with composable commerce modules for products, carts, orders, inventory, discounts, multi-region/currency support and more, plus a customizable admin dashboard and APIs that let you build your storefront with any frontend framework. Whether you’re launching a simple store, a complex marketplace, or a global B2B/B2C platform, Medusa.js provides the extensibility and developer control to design tailored eCommerce solutions suited to modern headless workflows.
+
+### Overview:
+* [Medusa.js Reference Guide](referenceguide.md)
+### How-To Guides
+* [Medusa.js Setup Example](setupexample.md)

… & Frameworks/MedusaJS/referenceguide.md …& Frameworks/Medusa.js/referenceguide.mdTechnologies/CMS & Frameworks/MedusaJS/referenceguide.md renamed to Technologies/CMS & Frameworks/Medusa.js/referenceguide.md Technologies/CMS & Frameworks/MedusaJS/referenceguide.md renamed to Technologies/CMS & Frameworks/Medusa.js/referenceguide.md

@@ -1,16 +1,16 @@
 ---
 hidden: true
 ---
-# MedusaJS Hosting Reference Guide
-Our TurboStack is equiped to handle your optimized MedusaJS application! 
+# Medusa.js Hosting Reference Guide
+Our TurboStack is equipped to handle your optimized MedusaJS application! 
 
 We maintain the server and infrastructure, but MedusaJS configuration, themes, plugins, and customizations are your responsibility.
 
 This guide will inform you about the filestructure, permissions, caching and more, of your MedusaJS application.
 
 ## File Structure
 
-The following table shows the directory structure of a MedusaJS application:
+The following table shows the directory structure of a Medusa.js application:
 
 | Path                 | Purpose |
 |----------------------|---------|
@@ -42,7 +42,7 @@ chown -R $USER:$USER ~/<Project>/<Shopname>
 You can find our documentation on how to set up Redis [here](../../Caching/redis.md)
 
 ### Varnish
-The MedusaJS dashboard does not need any caching. We do recommend adding varnish to your storefront.
+The Medusa.js dashboard does not need any caching. We do recommend adding varnish to your storefront.
 
 You can enable Varnish in our TurboStack GUI by adding the following line to the YAML configuration, for the `vhost` where your frontend resides.
 

…MS & Frameworks/MedusaJS/setupexample.md …S & Frameworks/Medusa.js/setupexample.mdTechnologies/CMS & Frameworks/MedusaJS/setupexample.md renamed to Technologies/CMS & Frameworks/Medusa.js/setupexample.md Technologies/CMS & Frameworks/MedusaJS/setupexample.md renamed to Technologies/CMS & Frameworks/Medusa.js/setupexample.md

@@ -2,12 +2,12 @@
 hidden: true
 ---
 # Setup example on TurboStack
-In this example, we will set up a MedusaJS instance on TurboStack. This will include the demo frontend and the MedusaJS backend. 
+In this example, we will set up a Medusa.js instance on TurboStack. This will include the demo frontend and the Medusa.js backend. 
 
-If you only want to set up the backend, you can choose this in project creation later. MedusaJS exposes API's for you to _'Plug in'_ your own frontend.
+If you only want to set up the backend, you can choose this in project creation later. MedusaJS exposes APIs for you to _'Plug in'_ your own frontend.
 ## YAML configuration
 MedusaJS requires:
-- NodeJS 20+ (LTS versions only)
+- Node.js 20+ (LTS versions only)
 - PostgreSQL
 
 The dashboard (backend) runs on port 9000/app and the demo frontend runs on port 8000.
@@ -39,7 +39,7 @@ system_users:
 ## Server setup
 
 ### Creating the project
-After the deploy succeeded, we can start setting up the server. We will use generic names, for this example. You can change these to your own.
+After the deployment succeeded, we can start setting up the server. We will use generic names, for this example. You can change these to your own.
 
 Make a new project directory and navigate to it:
 ```bash
@@ -48,11 +48,11 @@ cd project
 ```
 > **Important:** You don't want to place this in the `public_html` directory, as it will expose sensitive files to the public.
 
-To create a MedusaJS project, run the following command:
+To create a Medusa.js project, run the following command:
 ```bash
 npx create-medusa-app@latest <shopname>
 ```
-This will start the interactive install process. Follow the prompts to complete the installation:
+This will start the interactive installation process. Follow the prompts to complete the installation:
 ```
 ? Would you like to install the Next.js Starter Storefront? You can also install it later. Yes
 ? Enter your Postgres username demo_db
@@ -180,8 +180,8 @@ pm2 start "npm start"  --name storefront
 ## Tips
 ### Automating the deployment process
 If you want to automate the deployment process, you can do two things:
-  - Include the database connectionstring in the create-medusa-app command
-  - use the `--with-nextjs-starter` flag to include the storefront, then delete it after the install.
+  - Include the database connection string in the create-medusa-app command
+  - use the `--with-nextjs-starter` flag to include the storefront, then delete it after the installation.
   - Grab the Postgres credentials on the server, instead of the TurboStack GUI.
 
 To get the Postgres credentials, run the following command in the home directory of the user:
@@ -194,5 +194,5 @@ The command should look like this:
 npx create-medusa-app@latest shopname --db-url "postgres://<username>:<password>@localhost:5432/<dbname>" --with-nextjs-starter
 ```
 
-After the install, delete the storefront directory.
+After the installation, delete the storefront directory.
 ---

Technologies/CMS & Frameworks/MedusaJS/readme.md

@@ -1,4 +1,4 @@
-label: NodeJS
+label: Node.js
 order: 70
 icon: apps
 expanded: false

…logies/CMS & Frameworks/NodeJS/index.yml …ogies/CMS & Frameworks/Node.js/index.ymlTechnologies/CMS & Frameworks/NodeJS/index.yml renamed to Technologies/CMS & Frameworks/Node.js/index.yml Technologies/CMS & Frameworks/NodeJS/index.yml renamed to Technologies/CMS & Frameworks/Node.js/index.yml

@@ -1,7 +1,10 @@
+---
+hidden: true
+---
 ## Overview 
 
 In this article we will be going over handy how-to commands in configuring, deploying and troubleshooting your PM2 application.
-PM2 is a process manager for NodeJS applications, it comes with many benefits with the overall benefit being it making sure your application runs continuously and is easily manageable. 
+PM2 is a process manager for Node.js applications, it comes with many benefits with the overall benefit being it making sure your application runs continuously and is easily manageable. 
 
 Benefits include:
 - Keeps the application running due to auto-restarts
@@ -12,16 +15,16 @@ Benefits include:
 
 ## Installation
 
-When defining NodeJS in your deployment in my.turbostack.app pm2 will be installed by default by your node package manager :
+When defining Node.js in your deployment in my.turbostack.app pm2 will be installed by default by your node package manager :
 
 <img width="1000" height="713" alt="image" src="https://github.com/user-attachments/assets/ac652f6a-1a9e-4824-8764-e0904a605b39" />
 
 ## Deploying the application
-1. In case you migrated from another environment and you want to start with a fresh deployment, make sure to clean out the node_modules directory:
+1. In case you migrated from another environment, and you want to start with a fresh deployment, make sure to clean out the node_modules directory:
 
     `rm -rf node_modules`
 
-    It could be that during migration somethig is missing/corrupted/incompatible. Removing the directory ensures a flawless reinstall.
+    It could be that during migration something is missing/corrupted/incompatible. Removing the directory ensures a flawless reinstall.
 
 2. Check the important configuration files are present and changed accordingly if needed ( `next.config.js` and `package.json`)
 
@@ -41,13 +44,13 @@ When defining NodeJS in your deployment in my.turbostack.app pm2 will be install
 
     `pm2 save`
 
-  > This will store the **current** process list so the application can be restarted automatically after a reboot of the server or any other disturbance causing the service to stop. **Always do this whenever the running process list changes** ( e.g when deleting/starting a new application, changing the app name, et citera...) 
+  > This will store the **current** process list so the application can be restarted automatically after a reboot of the server or any other disturbance causing the service to stop. **Always do this whenever the running process list changes** (e.g. when deleting/starting a new application, changing the app name, etcetera...) 
    
 7.**If this is the first time setup** it could be that you need to run:
 
     `pm2 startup`
 
-  This prepares pm2 to launch on system boot, afterwards `pm2 save` will handle all running operations.
+  This prepares pm2 to launch on system boot, afterwards, `pm2 save` will handle all running operations.
 
 ## Monitoring and troubleshooting the application
 
@@ -78,7 +81,7 @@ When defining NodeJS in your deployment in my.turbostack.app pm2 will be install
       * `--err` : show only errors
       * `--out` : show only output
 
--  Restart or reload an applicaiton:
+-  Restart or reload an application:
 
     `pm2 restart <appname>`
 

…hnologies/CMS & Frameworks/NodeJS/pm2.md …nologies/CMS & Frameworks/Node.js/pm2.mdTechnologies/CMS & Frameworks/NodeJS/pm2.md renamed to Technologies/CMS & Frameworks/Node.js/pm2.md Technologies/CMS & Frameworks/NodeJS/pm2.md renamed to Technologies/CMS & Frameworks/Node.js/pm2.md

@@ -0,0 +1,11 @@
+**Node.js** is an open-source, cross-platform Javascript runtime environment.
+Traditionally Javascript is used to make websites interactive within the browser. 
+Node.js is a way to let you use JavaScript outside of a web browser and instead use it on the server itself.
+
+### Overview:
+
+* [Node.js Reference Guide](referenceguide.md)
+
+### How-To Guides
+
+* [PM2 - Process manager for Node.js applications ](pm2.md)

Technologies/CMS & Frameworks/Node.js/readme.md

@@ -1,6 +1,9 @@
+---
+hidden: true
+---
 # Node.js Hosting Reference Guide
 
-We provide optimized server environments for running **Node.js applications**. As the hosting provider, we maintain the server infrastructure, network, and runtime environment. Application code, dependencies, environment variables, and process management within your project areyour responsibility. (but we are always happy to assist when you are encountering issue ofcourse)
+We provide optimized server environments for running **Node.js applications**. As the hosting provider, we maintain the server infrastructure, network, and runtime environment. Application code, dependencies, environment variables, and process management within your project are your responsibility. (but we are always happy to assist when you are encountering issue ofcourse)
 
 This guide outlines the typical file structure and recommended permissions for your application.