Reorganize website

Author: jlblancoc

README.md

@@ -24,6 +24,13 @@
   Configurable pipelines for LiDAR Odometry, LIO, and more.
 </p>
 
+<p align="center">
+  <a href="https://docs.mola-slam.org/latest/why-mola.html"><b>Why MOLA</b></a> &nbsp;|&nbsp;
+  <a href="https://docs.mola-slam.org/latest/solutions.html"><b>Solutions</b></a> &nbsp;|&nbsp;
+  <a href="https://docs.mola-slam.org/latest/pricing.html"><b>Plans &amp; Pricing</b></a> &nbsp;|&nbsp;
+  <a href="https://docs.mola-slam.org/latest/"><b>Documentation</b></a>
+</p>
+
 ---
 
 
@@ -52,7 +59,10 @@ Refer to the [official documentation](https://docs.mola-slam.org/latest/) for bu
 
 ## 🗺️ Features
 - 📍 LiDAR Odometry (LO), LiDAR-Inertial Odometry (LIO), geo-referenced maps, sensor fusion
-- 🧩 Plug-and-play modules to build configurable ICP and SLAM pipelines 
+- 🧩 Fully configurable YAML pipelines - no recompilation needed to change sensors, filters, or map layers
+- 🎯 Flexible accuracy: fast real-time navigation or survey-grade (<1 cm) mapping
+- 🌍 Map-less RTK-quality outdoor georeferencing with low-cost GNSS + LiDAR + IMU
+- 🛠️ Rich `.mm` metric map ecosystem: viewer, LAS/PLY/TXT export, filtering, georeferencing tools
 - 🤖 ROS 2 ready (Humble, Jazzy, Kilted, Rolling) but also usable from standalone pure C++
 
 ## 🚀 Demo videos
@@ -136,8 +146,11 @@ MOLA was initially presented in 2019 in ([PDF](http://www.roboticsproceedings.or
 ```
 
 ## License
-MOLA is released under the GNU GPL v3 license, except noted otherwise in each individual module. Other options available upon request.
-Some modules are released under BSD-3. See the [official documentation](https://docs.mola-slam.org/latest/).
+MOLA follows an **Open Core** model. Core modules are released under the GNU GPL v3 license, while foundational libraries (MRPT, mp2p_icp) are BSD-3.
+
+**Commercial use:** Companies needing to deploy MOLA in closed-source products can obtain a commercial license ([MOLA Pro](https://docs.mola-slam.org/latest/pricing.html)).
+
+See the [Plans & Pricing](https://docs.mola-slam.org/latest/pricing.html) page for details on Community vs Pro editions.
 
 Contributions require acceptance of the Contributor License Agreement (CLA).
 

docker/Dockerfile

@@ -47,18 +47,18 @@ is run through a lightweight pre-processor that expands special ``$``\ -prefixed
 expressions.  The three expansion passes are always applied in the following
 fixed order:
 
-1. :ref:`yaml_include` — ``$include{path}``
-2. :ref:`yaml_cmd` — ``$(command)``
-3. :ref:`yaml_vars` — ``${VAR}`` / ``${VAR|default}``
+1. :ref:`yaml_include` - ``$include{path}``
+2. :ref:`yaml_cmd` - ``$(command)``
+3. :ref:`yaml_vars` - ``${VAR}`` / ``${VAR|default}``
 
 This ordering means that:
 
 - ``$include{}`` can pull in files whose paths are themselves built with
   ``$()`` or ``${}`` tokens.
 - ``$()`` command output can reference environment variables already present in
   the environment at parse time.
-- ``${}`` variable expansion sees the fully assembled text — including the
-  content of all included files — and can therefore reference variables that
+- ``${}`` variable expansion sees the fully assembled text - including the
+  content of all included files - and can therefore reference variables that
   are defined in those files.
 
 **Comments are never expanded.**  Any ``$include{}``, ``$()``, or ``${}``
@@ -160,17 +160,17 @@ Variables and environment: ``${VAR}`` / ``${VAR|default}``
 The pattern ``${NAME}`` is replaced by a value looked up in the following
 order (first match wins):
 
-1. **Environment variable** — the current value of ``getenv("NAME")``.
-2. **Built-in token** ``CURRENT_YAML_FILE_PATH`` — expands to the directory
+1. **Environment variable** - the current value of ``getenv("NAME")``.
+2. **Built-in token** ``CURRENT_YAML_FILE_PATH`` - expands to the directory
    of the file currently being parsed (or the value of
    ``YAMLParseOptions::includesBasePath`` when called programmatically).
-3. **Caller-supplied variables** — entries in the
+3. **Caller-supplied variables** - entries in the
    ``YAMLParseOptions::variables`` map, which allows C++ code to inject
    arbitrary name/value pairs at load time.
-4. **Inline default** — if the token has the form ``${NAME|default_value}``,
+4. **Inline default** - if the token has the form ``${NAME|default_value}``,
    the literal text after ``|`` is used as a fallback.  The default may be
    empty (``${NAME|}`` resolves to an empty string).
-5. **Error** — if none of the above matched, a fatal error is raised.
+5. **Error** - if none of the above matched, a fatal error is raised.
 
 .. code-block:: yaml
 
@@ -180,7 +180,7 @@ order (first match wins):
     # Use a default value when the variable is not set:
     log_dir: ${LOG_DIR|/tmp/mola_logs}
 
-    # Empty-string default — never raises an error:
+    # Empty-string default - never raises an error:
     optional_suffix: ${SUFFIX|}
 
     # Refer to the directory of this file (useful for sibling-relative paths):