docs: add structured connector documentation in docs/ - #15
docs: add structured connector documentation in docs/#15vaishnavi-kedar-cstk wants to merge 2 commits into
Conversation
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>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ 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:
✅ 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>
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ 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:
✅ BUILD PASSED - All security checks passed |
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 aspartacus-connectorproduct directory).Pages (12)
index.mdschema.mdoverview.mdconcepts.mdarchitecture.mdinstallation.mdconfiguration.mdContentstackConfigreferencecontent-model.mdlive-preview.mdaccess-control.mdapi-reference.mdpublic-api.tstroubleshooting.mdDiagrams
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
title,product,type,tags,last_updated);schema.md+index.mdspine.[[wikilinks]]at that point.src/adapters, normalizers, client, live-preview, access, slot-maps) — no invented behavior.Notes for reviewers
spartacus-connector(easy to rename if the docs team prefers another).🤖 Generated with Claude Code