Skip to content

docs: add structured connector documentation in docs/ - #15

Open
vaishnavi-kedar-cstk wants to merge 2 commits into
mainfrom
docs/connector-wiki
Open

docs: add structured connector documentation in docs/#15
vaishnavi-kedar-cstk wants to merge 2 commits into
mainfrom
docs/connector-wiki

Conversation

@vaishnavi-kedar-cstk

@vaishnavi-kedar-cstk vaishnavi-kedar-cstk commented Sep 9, 2026

Copy link
Copy Markdown

What

Adds a structured, detailed documentation set for the connector under docs/, following the Contentstack product-wiki conventions so the docs team can review it (and, if useful, promote it into the central wiki as a spartacus-connector product directory).

Pages (12)

File Covers
index.md Table of contents + system-context diagram
schema.md Structural rules + diagram convention for this doc set
overview.md What it is, features, limitations, status
concepts.md Hybrid rendering, slots/islands, two-token model, DI ordering, page-type resolution
architecture.md Adapter-override chain, request flow, normalizer pipeline, module composition
installation.md End-to-end install + verification
configuration.md Full ContentstackConfig reference
content-model.md Content types, slot map, custom slots, seed
live-preview.md Live Preview / Visual Builder
access-control.md Presentation-level content gating
api-reference.md Public API surface from public-api.ts
troubleshooting.md Common integration issues + diagnostic decision tree

Diagrams

23 inline Mermaid diagrams across the set (GitHub renders these natively — no image assets): system context, hybrid islands, adapter-override + request-flow sequence, normalizer dispatch, DI last-provider-wins (correct vs silent-failure), two-token security, page-type resolution, content-model ER + uid↔typeCode mapping, media resolution, live-preview sequence, access-control decision tree, module map, and a troubleshooting decision tree.

Conventions & quality gates

  • Per-file YAML frontmatter (title, product, type, tags, last_updated); schema.md + index.md spine.
  • Standard relative Markdown links for internal navigation (renders on GitHub / VS Code). Cross-page anchors validated against the exact GitHub slug algorithm — 0 broken. If promoted into the Obsidian-based product-wiki, links convert to [[wikilinks]] at that point.
  • Content and every diagram identifier verified against the shipped source (src/ adapters, normalizers, client, live-preview, access, slot-maps) — no invented behavior.
  • All Mermaid blocks syntactically validated.

Notes for reviewers

  • Docs-only change; no code touched.
  • Product slug used is spartacus-connector (easy to rename if the docs team prefers another).

🤖 Generated with Claude Code

Add a product-wiki-style documentation set for the SAP Composable
Storefront connector under docs/, following the Contentstack
product-wiki conventions (per-file YAML frontmatter, a schema.md +
index.md spine, standard relative Markdown links for navigation).

Pages: index, schema, overview, concepts, architecture, installation,
configuration, content-model, live-preview, access-control,
api-reference, troubleshooting. Content is grounded in the repo's
existing README/GETTING_STARTED/CONTENT-MODEL/TROUBLESHOOTING and src/.

Intended for docs-team review ahead of possible promotion into the
central product-wiki.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vaishnavi-kedar-cstk
vaishnavi-kedar-cstk requested a review from a team as a code owner September 9, 2026 09:50
@snyk-io

snyk-io Bot commented Sep 9, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

Roughly double the depth of every page and add 23 inline Mermaid
diagrams (system context, hybrid islands, adapter-override + request
flow, normalizer dispatch, DI last-provider-wins, two-token security,
page-type resolution, content-model ER + uid<->typeCode mapping, media
resolution, live-preview sequence, access-control decision tree, module
map, and a troubleshooting decision tree).

Content and every diagram identifier are verified against the shipped
source (adapters, normalizers, client, live-preview, access, slot-maps).
Cross-page anchor links validated against the exact GitHub slug
algorithm; no [[wikilinks]]; frontmatter preserved.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@dange-cstk dange-cstk left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants