Merge branch 'main' into jaisch01-maintain-performix-install-guide

Author: pareenaverma

.github/skills/code-sample-review/SKILL.md

@@ -46,7 +46,7 @@ Check for:
 ## Workflow
 
 1. Identify the review scope and whether the request is editorial, technical, or mixed.
-2. Inspect surrounding prose before judging a code block; code samples should be evaluated in context.
+2. Inspect surrounding prose before judging a code block; code samples should be evaluated in context. If you've previously read the page, use context and don't re-read it unless there's a change since the last read. 
 3. Depending on the type of review, suggest fixes as follows:
   - For review requests, report issues by file and line when possible, ordered by learner impact.
   - For edit requests, report issues and suggest focused changes that preserve technical intent and existing repository patterns.

.github/skills/draft-learning-path/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: draft-learning-path
+description: "Toggle draft mode on a Learning Path _index.md. Use when: marking a learning path as draft, hiding a learning path from publication, adding draft: true to front matter, unpublishing or disabling a learning path, removing draft, publishing a learning path, taking a learning path out of draft."
+---
+
+# Draft Learning Path
+
+Sets `draft: true` and `cascade: draft: true` in the front matter of a Learning Path `_index.md` file so the page and all its child pages are excluded from the published site.
+
+For new content intake where the goal is to prevent unreviewed content from publishing, use `.github/skills/intake-metadata-update/SKILL.md` instead.
+
+## Draft block to insert
+
+The following YAML must be added to the front matter, after the `title:` field. Leave a blank line between `title:` and the draft block for readability:
+
+```yaml
+title: Your Learning Path Title
+
+draft: true
+cascade:
+    draft: true
+```
+
+## Workflow
+
+1. **Identify the target file**
+   - If the user specifies a path, use that.
+   - Otherwise, use the currently open or most recently edited `_index.md` file in the workspace.
+   - Confirm the file is a Learning Path `_index.md` (contains Hugo front matter between `---` markers).
+
+2. **Read the file**
+   - Read the file to inspect the existing front matter.
+
+3. **Apply the draft block**
+   - If `draft: true` and `cascade:` with `draft: true` already exist, inform the user it is already in draft mode and stop.
+   - If a `draft:` field exists but no `cascade:` block, replace the existing `draft:` line with the full draft block above.
+   - If no `draft:` field exists, insert the draft block after the `title:` field, with a blank line between them.
+
+4. **Confirm**
+   - Report the file path and confirm the draft block has been set.
+   - Remind the user that Hugo will exclude this file and all child pages from the built site until the draft block is removed.
+
+## Undraft workflow
+
+If the user asks to publish, undraft, or remove draft mode:
+
+1. **Identify the target file** (same as above).
+2. **Read the file** to locate the draft block.
+3. **Remove the draft block**
+   - Remove the `draft: true` line.
+   - Remove the `cascade:` block (`cascade:` and its indented `draft: true` child line).
+   - Remove any blank line that was added between `title:` and the draft block, restoring the original spacing.
+   - If no draft block exists, inform the user the file is already published and stop.
+4. **Confirm**
+   - Report the file path and confirm draft mode has been removed.
+   - Remind the user the Learning Path will now appear on the published site.

.github/skills/link-text-review/SKILL.md

@@ -18,7 +18,7 @@ This skill focuses on anchor text and link clarity. For tables, notices, tab pan
 
 ## Workflow
 
-1. Identify the target file, directory, section, or selected text.
+1. Identify the target file, directory, section, or selected text. If you've previously read the page, use context and don't re-read it unless there's a change since the last read. 
 2. Read surrounding context before suggesting any changes.
 3. After understanding the context of the URL, suggest concise and natural rewrites to the anchor text based on `Quality rules`. 
 4. After the user accepts suggestions, make changes, then re-open or search changed lines to verify the Markdown link syntax is valid.

.github/skills/markdown-component-edit/SKILL.md

@@ -18,7 +18,7 @@ This skill is best when the user highlights text, names a section, or asks for a
 
 ## Workflow
 
-1. Use the user's highlighted, selected, or explicitly named text as the edit target. If the target is ambiguous, ask for the exact text, file, or section before editing. 
+1. Use the user's highlighted, selected, or explicitly named text as the edit target. If the target is ambiguous, ask for the exact text, file, or section before editing. If you've previously read the page, use context and don't re-read it unless there's a change since the last read. 
 2. Inspect nearby Markdown so the new component fits the surrounding flow.
 3. Verify internal links before adding or changing them when practical.
 4. Use `component rules` and the `component-patterns` reference and do one of the following:

.github/skills/metadata-description-update/SKILL.md

@@ -31,7 +31,7 @@ This skill is for search and discovery metadata. For draft visibility metadata,
 ## Workflow
 
 1. Identify whether the target is an install guide content page, a Learning Path `_index.md`, or a Learning Path content page.
-2. Read the title, existing description, headings, introduction, task flow, code or command context, and validation or conclusion.
+2. Read the title, existing description, headings, introduction, task flow, code or command context, and validation or conclusion. If you've previously read the page, use context and don't re-read it unless there's a change since the last read. 
 3. Add or revise the `description` field in front matter based on quality rules.
 4. After editing, re-open or search the files to verify each changed target has one `description` field.
 5. Report files changed and note any skipped files.

.github/skills/seo-geo-aeo-review/SKILL.md

@@ -23,8 +23,8 @@ For focused front matter `description` edits only, use `.github/skills/metadata-
 
 ## Workflow
 
-1. Identify the target content type and target developer intent.
-2. Read the title, front matter description, headings, introduction, prerequisites, main task flow, validation, conclusion, and further reading.
+1. Identify the target content type and target developer intent. 
+2. Read the title, front matter description, headings, introduction, prerequisites, main task flow, validation, conclusion, and further reading. If you've previously read a page, use context and don't re-read it unless there's a change since the last read. 
 3. State the page's owned task in one sentence. If the task is unclear or too broad, flag it.
 4. Review SEO signals:
    - The title is task-led and includes the main technology, platform, or tool.

.github/skills/writing-style-review/SKILL.md

@@ -10,7 +10,7 @@ Use this skill for granular prose, voice, readability, terminology, and style re
 ## Workflow
 
 1. Identify the target file, section, or selected text.
-2. Read surrounding context so style edits preserve the author's intent and the technical flow.
+2. Read surrounding context so style edits preserve the author's intent and the technical flow. If you've previously read the page, use context and don't re-read it unless there's a change since the last read. 
 3. Review the target against the guidelines defined in this skill.
 4. Depending on request type, do the following:
   - For review requests, report high-impact style issues by file and line when possible. 

.gitignore

@@ -8,7 +8,6 @@ package-lock.json
 .vscode
 .env
 startup.sh
-data/
 
 # macOS files
 *.DS_Store
@@ -26,4 +25,4 @@ z_local_saved/
 tags
 
 # Generated spell check config
-.spellcheck-non-draft.yml
+.spellcheck-non-draft.yml

assets/contributors.csv

@@ -128,3 +128,4 @@ Sabika Tasneem,Memgraph,,,,
 Anupras Mohapatra,Arm,,,,
 Tomas Agustin Gonzalez Orlando,Arm,tgonzalezorlandoarm,tgorlando,,
 Jai Adam Schrem,Arm,jai-adam-schrem,jai-adam-s-395bb1233,,
+Steve Jordahl,Rafay,,,,