You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your interest in improving our documentation! This site is built with [VitePress](https://vitepress.dev/) and covers the NetApp Innovations Labs projects.
4
+
5
+
## Project Structure
6
+
7
+
***```docs/```**: The source code for the documentation site.
8
+
***```docs/content/```**: Portfolio of our team's contribution to blogs, videos, etc.
9
+
***```docs/projects/[cloud,containers,mlai]```**: Documentation per domain
10
+
***`docs/.vitepress/`**: Site configuration, theme, and sidebar settings.
11
+
12
+
## Local Development
13
+
14
+
To update and preview documentation changes locally before pushing:
15
+
16
+
1.**Prerequisites**
17
+
*[Node.js](https://nodejs.org/en/download) (version 20 or higher)
18
+
* npm (comes with Node.js)
19
+
* Fork the [NetApp Innovation Labs](https://github.com/NetApp/Innovation-Labs) repository
20
+
21
+
2.**Setup**
22
+
```bash
23
+
# Install dependencies
24
+
npm install
25
+
```
26
+
27
+
3. **Run the Dev Server**
28
+
```bash
29
+
npm run docs:dev
30
+
```
31
+
The site will start at ```http://localhost:5173```. Any changes you make to markdown files will hot-reload automatically.
32
+
33
+
## Writing Guidelines
34
+
35
+
We use native and GitHub Markdown without any HTML or add-ons with VitePress extensions and follow the categories/subcategories of the existing content.
36
+
37
+
### Adding a New Page
38
+
1. Create a ```.md``` file in the appropriate directory (e.g., ```docs/projects/cloud/my-new-project.md```).
39
+
2. Add the file to the **sidebar** (not the **nav**) in```docs/.vitepress/config.mts``` so it appears in the sidebar navigation menu.
40
+
41
+
### images
42
+
Place images in the ```docs/public``` folder and reference with the markdown tag
43
+
``````
44
+
45
+
## Publishing
46
+
Once you are happy with your content, open a Pull Request from your repository towards ours and we will review your contributions!
Copy file name to clipboardExpand all lines: docs/projects/mlai/neo/core/d-configuration.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,8 @@ This guide assumes you have already reviewed the [Prerequisites](../prerequisite
4
4
5
5
When the connector is deployed it will deploy in SETUP mode by default. This allows you to complete the initial configuration of the connector via the API or web console. Once the connector is configured it can be switched to PRODUCTION mode.
<strong>📘 Note:</strong> The following guidance is temporary and will be native in Neo Console in a future release. During this time please follow the steps below to switch between modes and configure your license.
9
-
</blockquote>
7
+
> [!NOTE]
8
+
> The following guidance is temporary and will be native in Neo Console in a future release. During this time please follow the steps below to switch between modes and configure your license.
<strong>❗ Important:</strong> ACL overrides bypass the original file permissions. Consider the following:
216
-
<ol>
217
-
<li><strong>Data Exposure Risk</strong>: Using <code>acl_override_mode: "everyone"</code> makes all files in the share accessible to everyone in your Entra tenant. Only use this for truly public content.</li>
218
-
<li><strong>Audit Trail</strong>: The original file ACLs are still extracted and stored in the database for auditing purposes, even when overrides are applied.</li>
219
-
<li><strong>Principle of Least Privilege</strong>: When using <code>specified</code> mode, grant access only to the users and groups that genuinely need it.</li>
220
-
<li><strong>Regular Review</strong>: Periodically review shares with ACL overrides to ensure the permissions are still appropriate.</li>
221
-
</ol>
222
-
</blockquote>
213
+
> [!WARNING]
214
+
> -**Data Exposure Risk**: Using ```acl_override_mode: "everyone"``` makes all files in the share accessible to everyone in your Entra tenant. Only use this for truly public content.
215
+
> -**Audit Trail**: The original file ACLs are still extracted and stored in the database for auditing purposes, even when overrides are applied.
216
+
> -**Principle of Least Privilege**: When using ```specified``` mode, grant access only to the users and groups that genuinely need it.
217
+
> -**Regular Review**: Periodically review shares with ACL overrides to ensure the permissions are still appropriate.
0 commit comments