[docs] chore(feature flag): introduce feature flag

Author: RomuDeuxfois

README.md

@@ -5,7 +5,8 @@
 
 ## Introduction
 
-This is the main repository of the OpenAEV Documentation space. The online version is available directly on [docs.openaev.io](https://docs.openaev.io).
+This is the main repository of the OpenAEV Documentation space. The online version is available directly
+on [docs.openaev.io](https://docs.openaev.io).
 
 ## Development (local setup)
 ### Prerequisites
@@ -86,3 +87,36 @@ List known versions:
 ```
 $ mike list
 ```
+
+## Feature Flags
+
+The documentation supports **feature flags** to conditionally show or hide content, powered by the [
+`mkdocs-macros-plugin`](https://mkdocs-macros-plugin.readthedocs.io/).
+
+This mechanism allows to prepare documentation for upcoming features without publishing it, similar to feature flags in
+the OpenAEV application codebase.
+
+### How it works
+
+1. Feature flags are declared in `mkdocs.yml` under `extra.feature_flags`.
+2. Content is wrapped in Jinja2 conditions in `.md` or `.html` files.
+3. At build time (`mkdocs build` / `mkdocs serve`), flagged sections are included or excluded.
+
+### 1. Declare a flag
+
+In `mkdocs.yml`:
+
+```yaml
+extra:
+  feature_flags:
+    palo_alto_cortex: true    # visible in the documentation
+    my_new_feature: false     # hidden from the documentation
+```
+
+### 2. Use the flag in Markdown
+
+```markdown
+{%- if config.extra.feature_flags.palo_alto_cortex %}
+This entire section is only rendered when the flag is enabled.
+{%- endif %}
+```

docs/administration/enterprise.md

@@ -54,11 +54,13 @@ according to the [OpenAEV architecture](../deployment/platform/overview.md#archi
 
 The SentinelOne Agent can be leveraged to execute implants as detached processes that will then execute payloads
 according to the [OpenAEV architecture](../deployment/platform/overview.md#architecture)
+{%- if config.extra.feature_flags.palo_alto_cortex %}
 
 ### Palo Alto Cortex Agent
 
 The Palo Alto Cortex Agent can be leveraged to execute implants as detached processes that will then execute payloads
 according to the [OpenAEV architecture](../deployment/platform/overview.md#architecture)
+{%- endif %}
 
 ## Remediations in CVES
 

docs/deployment/ecosystem/executors.md

@@ -14,7 +14,9 @@ architectures. This table below summarizes the information about each agent.
 | **Tanium Agent**                   | Under license | As a system service                               | Executable        | An admin background process            | As a system admin                              | No, always the same agent                        |                              
 | **Crowdstrike Falcon Agent**       | Under license | As a system service                               | Executable        | An admin background process            | As a system admin                              | No, always the same agent                        |                              
 | **SentinelOne Agent**              | Under license | As a system service                               | Executable        | An admin background process            | As a system admin                              | No, always the same agent                        |
+{%- if config.extra.feature_flags.palo_alto_cortex %}
 | **Palo Alto Cortex Agent**         | Under license | As a system service                               | Executable        | An admin background process            | As a system admin                              | No, always the same agent                        |
+{%- endif %}
 | **Caldera Agent**                  | Open source   | As a user session                                 | Script            | An admin background process            | As a user admin                                | Yes, depending on the user                       |                      
 
 ## OpenAEV Agent
@@ -293,6 +295,7 @@ Endpoint on the OpenAEV endpoint page.
     You are now ready to leverage your CrowdStrike platform to run OpenAEV payloads!
 
 ---
+{%- if config.extra.feature_flags.palo_alto_cortex %}
 <a id="paloaltocortex-agent"></a>
 ## Palo Alto Cortex Agent
 
@@ -378,6 +381,7 @@ Endpoint on the OpenAEV endpoint page.
 !!! success "Installation done"
 
     You are now ready to leverage your Palo Alto Cortex platform to run OpenAEV payloads!
+{%- endif %}
 
 ---
 <a id="sentinelone-agent"></a>

docs/usage/assets.md

@@ -69,7 +69,7 @@ To register new endpoints, you will need to install an agent. You can find detai
 | Attribute       | Meaning                                                                             |
 |-----------------|-------------------------------------------------------------------------------------|
 | **Name**        | Local user account on the endpoint that executes the agent process                  | 
-| **Executor**    | Agent type (OpenAEV, Crowdstrike, Tanium, SentinelOne, Palo Alto Cortex or Caldera) | 
+| **Executor**    | Agent type (OpenAEV, Crowdstrike, Tanium, SentinelOne{% if config.extra.feature_flags.palo_alto_cortex %}, Palo Alto Cortex{% endif %} or Caldera) | 
 | **Privilege**   | Local account's privileges on the endpoint (admin, or standard user)                | 
 | **Deployment**  | Installation type (Service or Session)                                              |
 | **Status**      | Active or Inactive (threshold: 1 hour)                                              | 

mkdocs.yml

@@ -34,6 +34,8 @@ extra_css:
 
 # Extra
 extra:
+  feature_flags:
+    palo_alto_cortex: true
   version:
     provider: mike
   analytics:
@@ -60,6 +62,7 @@ plugins:
       alias_type: symlink
       canonical_version: latest
   - search
+  - macros
   - git-committers:
       repository: OpenAEV-Platform/docs
       branch: main