Skip to content

Footer: say SOC 2 Type 2 Compliant - #585

Merged
glasstiger merged 1 commit into
mainfrom
docs/footer-soc2-type-2
Oct 15, 2026
Merged

glasstiger merged 1 commit into
mainfrom
docs/footer-soc2-type-2

Conversation

@sandroqdb

Copy link
Copy Markdown
Contributor

The docs footer still says "SOC 2 Type 1 Compliant". The main site footer and Enterprise page moved to "SOC 2 Type 2 Compliant" in questdb/questdb.io#3021 (14 Sep); this companion change was missed.

  • src/theme/Footer/index.tsx: "SOC 2 Type 1 Compliant" -> "SOC 2 Type 2 Compliant"

One line, nothing else. Verified with a full build: every built page's footer renders "SOC 2 Type 2 Compliant", and "Type 1" no longer appears anywhere in the build output.

🤖 Generated with Claude Code

Match the main site footer (questdb/questdb.io#3021), which moved to
"SOC 2 Type 2 Compliant" on 14 Sep 2026. The docs footer still said Type 1.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🤖 Component Converter Reminder

A component in src/components/ or src/theme/ was modified in this pull request.

We are creating markdown correspondents of every path (e.g. questdb.com/docs/quick-start/ → questdb.com/docs/quick-start.md) for LLM consumption.
If the component usage is shadowing useful content, it may need a converter for markdown output in convert-components.js.

Quick Check

  • ✅ Content component (code, tables, data) → Add converter if not exists
  • ❌ UI/visual component (styling, buttons, decorative) → No converter needed

💡 This is a friendly reminder, not a blocker. Ignore if not applicable.

@github-actions

Copy link
Copy Markdown

🚀 Build success!

Latest successful preview: https://preview-585--questdb-documentation.netlify.app/docs/

Commit SHA: 11ab4ba

📦 Build generates a preview & updates the link on each commit.

@glasstiger
glasstiger merged commit f8c65ce into main Oct 15, 2026
4 checks passed
@glasstiger
glasstiger deleted the docs/footer-soc2-type-2 branch October 15, 2026 13:32
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.

3 participants