docs: move docs to docs package

[talkor]

PR Type

Documentation

---

Description

• Move theming documentation from core package to docs package

• Update migration guide links to reflect new documentation structure

• Relocate vibe2-migration-guide and vibe-3-changelog references

---

Diagram Walkthrough

flowchart LR
  A["packages/core/docs/theming.md"] -- "moved" --> B["packages/docs"]
  C["Migration Guide Links"] -- "updated paths" --> D["packages/docs/src/pages/migration-guide/"]

Loading

File Walkthrough

Relevant files

Documentation

theming.md Remove theming documentation from core package                      packages/core/docs/theming.md File deleted from core package docs directory Content moved to centralized docs package structure Theming documentation no longer in core package +0/-48    migration-guide.mdx Update documentation links to new package structure            packages/docs/src/pages/migration-guide/migration-guide.mdx Updated link to vibe2-migration-guide from old path to new docs package location Updated link to vibe-3-changelog from core package to docs package path Both links now point to packages/docs/src/pages/migration-guide/ directory +2/-2

---

[qodo-merge-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Verify File Existence The updated links point to new locations in the docs package. Ensure that the files vibe2-migration-guide.md and vibe-3-changelog.md actually exist at the new paths (packages/docs/src/pages/migration-guide/) and were moved along with theming.md, as only the deletion of theming.md is visible in this diff. guide](https://github.com/mondaycom/vibe/tree/master/packages/docs/src/pages/migration-guide/vibe2-migration-guide.md) </Tip>

[qodo-merge-for-open-source]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label