Skip to content

docs: clarify Contentstack stack setup in README - #6

Merged
vaishnavi-kedar-cstk merged 1 commit into
mainfrom
docs/clarify-contentstack-stack-setup
Oct 6, 2026
Merged

vaishnavi-kedar-cstk merged 1 commit into
mainfrom
docs/clarify-contentstack-stack-setup

Conversation

@vaishnavi-kedar-cstk

Copy link
Copy Markdown
Contributor

What

Adds a clarification note to the README about how the Contentstack stack is set up.

Why

Developers setting up the demo assumed they had to stand up a stack from scratch. The README did not state that (a) running against your own stack first requires configuring the content models + entries that correspond to the demo site, and (b) internal Contentstack developers can instead use an already-configured demo stack by asking the repo owner for the details. This note prevents that confusion.

Change

  • Single blockquote added after the intro, above Prerequisites. No other content changed.

🤖 Generated with Claude Code

Explain that running against your own stack requires configuring the
content models and entries that correspond to the demo site, and that
internal Contentstack developers can instead request the details of the
already-configured demo stack from the repo owner.

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 October 6, 2026 06:35
@snyk-io

snyk-io Bot commented Oct 6, 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 Oct 6, 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 1 32 25 ✅ Passed
🟡 Medium Severity 0 25 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: 32
  • Medium without fixes: 25
  • 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

@vaishnavi-kedar-cstk
vaishnavi-kedar-cstk merged commit f2ffb01 into main Oct 6, 2026
7 checks passed
@vaishnavi-kedar-cstk
vaishnavi-kedar-cstk deleted the docs/clarify-contentstack-stack-setup branch October 6, 2026 09:05
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