Archive latest deduplicate version 202602

.claude/CLAUDE.md

@@ -0,0 +1,5 @@
+# Local Claude Instructions
+
+Include:
+
+@CLAUDE.local.md

.claude/skills/spryker-ci/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: spryker-ci
+description: Run continuous integration tools and fix issues.
+---
+
+# SprykerCI Fixing Process
+
+Use this skill to systematically run continuous integration tools and fix errors in the Spryker documentation.
+
+## Process
+
+1. **Run SprykerCI**:
+
+2. **Results for issues**:
+   When there is issue output:
+    - Identify problematic
+    - Why the error exists (explanation of the type issue)
+    - Current code snippet
+    - Proposed fix with explanation
+    - Wait for user approval before applying
+
+3. **Verify**: Run the full SprykerCI execution path again
+
+## Important Notes
+
+- **Always get user approval** before applying each fix
+- Present one error at a time for manageable review
+- Explain WHY the error exists / test fail, not just HOW to fix it
+- User may have domain knowledge that affects the fix (e.g., knowing a value is never null)
+- Use type casts when user confirms value is always set
+- Use null checks when uncertain
+
+## Example Workflow
+
+```
+1. Run SprykerCI
+2. Present Issue #1:
+   - What: [what has failed]
+   - Why: [explanation]
+   - Fix: [proposed solution]
+3. User approves → Apply fix
+4. Run SprykerCI for this module again to verify success
+9. Present Issue #2...
+10. Continue until all errors/tests presented and approved
+11. Run SprykerCI again to verify success
+```
+
+## Fix guidelines
+
+### Sidebar issues
+
+When there is a page missing in the sidebar the issues shows fileName.md to be missing. TO fix this use the same path to be added and replace `md` with `html`.
+
+To get the title read the file that was mentioned rto be missing and get the title from it.
+
+## Commands
+
+Run Vale
+```bash
+vale $(find docs/ _includes/pbc/ -type f -name "*.md" ! -path "*/202311.0/*" ! -path "*/202404.0/*") --minAlertLevel=error
+```
+
+Run Markdown Linter
+```bash
+npx markdownlint-cli2 "docs/**/*.md" "_includes/pbc/**/*.md" "#node_modules"
+```
+
+Run Sidebar checker
+```bash
+./_scripts/sidebar_checker/sidebar_checker.sh
+```
+

.github/instructions/copilot-instructions.md

@@ -0,0 +1,145 @@
+# Spryker Documentation Repository Guidelines
+
+This file contains important instructions for working with the Spryker documentation repository.
+
+## Validation Workflow
+
+### Finding Changed Files
+
+When working on a branch, find all changed markdown files compared to master:
+
+```bash
+git diff master..HEAD --name-only | grep '.md'
+```
+
+### Running Validation Tools
+
+Run both validation tools on changed files:
+
+**Vale (prose linting):**
+```bash
+vale --minAlertLevel=error path/to/file.md 
+```
+
+**Markdownlint (markdown syntax):**
+```bash
+markdownlint-cli2 path/to/file.md
+```
+
+**Installation:** If vale or markdownlint-cli2 are not installed, install them according to the OS requirements.
+
+### Validation Policy
+
+- **ONLY address ERRORS**, not warnings or suggestions
+- Provide specific fixes for each error found
+- Validate all changed files before completing work
+
+## Documentation Standards
+
+Follow documentation Standards to ensure content is high-quality and consistent with Spryker documentation standards.
+
+### Internal Links Format
+
+All relative internal links MUST follow this format:
+
+```markdown
+[link text](/docs/section/file.html)
+```
+
+**Rules:**
+- Path starts with `/`
+- Path ends with `.html` (NOT `.md`)
+- Use the actual file path, replacing `.md` extension with `.html`
+
+**Example:**
+- File location: `docs/dg/dev/integrate-and-configure/integrate-development-tools/integrate-web-profiler.md`
+- Link format: `[Web Profiler Integration](/docs/dg/dev/integrate-and-configure/integrate-development-tools/integrate-web-profiler.html)`
+
+### Purpose and Goals
+
+- Evaluate content intended for documentation on docs.spryker.com
+- Ensure Markdown code for Jekyll meets high-quality standards in tone, writing style, grammar, and web best practices
+- Provide specific, actionable amendments to improve the article
+- **ONLY show amendments - do not show "no change" items**
+
+### Grammar and Sentence Structure
+
+- Identify grammatical errors:
+    - Typos
+    - Incorrect verb tense
+    - Subject-verb agreement issues
+    - Incorrect punctuation
+- Evaluate sentence structure for clarity and conciseness
+- Identify sentences that are too long, complex, or unclear
+- Formulate improved sentence structures for better readability
+- Ensure Markdown is correct and content conforms with web best practices (alt text, no skipped headings)
+
+### Tone of Voice
+
+Analyze the overall tone to align with technical documentation styles (Google Developer Documentation Style Guide, Microsoft Style Guide). The tone should be:
+- Formal yet helpful
+- Encouraging
+- Clear and concise
+- Consistent
+- Warm, relaxed, and ready to lend a hand
+
+**Required tone elements:**
+- Use second person ('you') to address the reader directly
+- Use active voice for clarity
+- Use present tense where appropriate for immediacy
+- Avoid contractions (use 'do not' instead of 'don't')
+- Use appropriate technical terms, avoiding unnecessary jargon
+
+### Writing Style, Markup and Markdown
+
+**Spelling:**
+- Use American spelling consistently
+
+**Markdown Formatting:**
+- Use standard Markdown for headings, lists, links, code blocks, and inline formatting
+- Verify proper use of headings, lists, code blocks, links, bolding, italics, etc.
+- Use Jekyll-compatible syntax for Spryker-specific components:
+    - `{% info_block infoBox "Info" %}...{% endinfo_block %}` instead of `> [!NOTE]`
+- Apply other Spryker Liquid tags as needed:
+    - `{% include %}`
+    - `{% info_block warningBox "Warning" %}`
+- Ensure output renders correctly in Jekyll but remains readable in raw Markdown
+
+### Presenting Suggestions
+
+Present all suggestions in a numbered list. Each item must have:
+
+1. **Original markdown code** - The current text/code
+2. **New markdown code** - The improved version
+3. **Summary of the change** - Brief explanation of what was changed and why
+
+**Example format:**
+```
+1. **Original:** `This is the old text.`
+   **New:** `This is the improved text.`
+   **Summary:** Changed passive voice to active voice for clarity.
+```
+
+## Workflow Automation
+
+When asked to "build" or "validate" documentation:
+1. Find all changed markdown files
+2. Run vale on each file
+3. Run markdownlint-cli2 on each file
+4. Report only errors (not warnings)
+5. Suggest specific fixes for each error
+6. Check internal links format and fix if needed
+7. Validate with Documentation Standards
+
+### Best Practices
+
+- Always validate documentation changes before committing
+- Fix validation errors immediately
+- Maintain consistency with surrounding content
+- Ensure all internal links are valid and properly formatted
+- Follow Documentation Standards for generation and validation of documentation
+
+### Limitations
+
+- Do not suggest removing any part of the document unless it violates a documented rule in the style guides or validation tools
+- If removal seems beneficial but isn't required by the rules, note it as an optional consideration rather than a recommendation

.github/workflows/check_last_modified.yml

@@ -0,0 +1,22 @@
+name: Check last_updated is not older than 30 days
+
+on:
+  pull_request:
+    types:
+      - opened
+      - synchronize
+
+jobs:
+  check-sidebar-links:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+
+      - name: Check last_updated is not older than 30 days for files with 1 changed line
+        env:
+          GITHUB_BASE_SHA: ${{ github.event.pull_request.base.sha }}
+        run: /bin/bash ./_scripts/last_updated_checker.sh 1 30

.vale-ignore

@@ -1,3 +1,2 @@
 lx0amx3m1b
-docs/pbc/all/payment-service-provider/202410.0/base-shop/third-party-integrations/powerpay.md:115.1.2.9/2018
 SprykerEco.Computop

.vale.ini

@@ -7,7 +7,7 @@ Packages = Google, Spryker
 
 [NoQuestionInHeadings]
 # List of file globs to ignore for this rule
-ignored = docs/pbc/all/tax-management/202410.0/base-shop/third-party-integrations/vertex/vertex-faq.md
+ignored =
 
 [*.{md}]
 BasedOnStyles = Google, Spryker, terms