Developer Experience Canonical URL: https://babadook.tech/sub-modules/developer-experience Entity: sub-modules Content hash: f9534d5c29c82219324f57d00e15b0df0247175ed3c31e6804fb47678bf53310 CLI, LSP integration, editor extensions, and framework-agnostic SDKs for productive DXP development. Developer-facing tools including CLI, Language Server Protocol integration, editor extensions, and framework-agnostic SDKs that make building on DXP productive and enjoyable. Developer Experience provides the toolchain that makes DXP feel native to any developer workflow. Built by Developers, for Developers subtitle: A platform that respects your workflow — CLI-first, LSP-powered, and framework-agnostic. DXP CLI desc: Project scaffolding, local dev server, deployment, and content management from the terminal. LSP Integration desc: IntelliSense for DQL, content types, component props, and API endpoints in any editor. Editor Extensions desc: First-party extensions for VS Code, JetBrains, and Neovim with inline previews. Framework SDKs desc: TypeScript, JavaScript, Python, Go, and Rust SDKs with full type safety. your-workflow,-your-way Your Workflow, Your Way The DXP CLI handles every lifecycle stage: create a project with scaffolding templates, run a local dev server with hot-reload and content preview, manage content types and entries from the terminal, and deploy to any environment with a single command. The Language Server Protocol integration provides real-time IntelliSense for DQL queries, content type definitions, component props, API endpoints, and configuration files. Errors are caught as you type, not at build time. Hover documentation shows field types, descriptions, and validation rules inline. Framework SDKs provide fully-typed client libraries for TypeScript, JavaScript, Python, Go, and Rust. Every SDK is auto-generated from the DXP API schema, so types are always in sync with the backend. Breaking changes are detected at compile time, not in production. data Viz Developer Experience Specifications - CLI Commands: create, dev, build, deploy, content, schema, migrate - LSP Features: IntelliSense, diagnostics, hover docs, go-to-definition, rename - Editor Support: VS Code, JetBrains (IntelliJ, WebStorm), Neovim, Zed - SDK Languages: TypeScript, JavaScript, Python, Go, Rust - Local Dev: Hot-reload, content preview, API mocking, seed data - Type Generation: Auto-generated from API schema with zero config - Package Format: @dxp/* npm packages + PyPI + Go modules + crates.io faq section Section 1 Which editors are supported by the LSP? The DXP Language Server works with any editor that supports LSP: VS Code, JetBrains IDEs (IntelliJ, WebStorm, PhpStorm), Neovim, Zed, Sublime Text, and Emacs. First-party extensions for VS Code, JetBrains, and Neovim provide the deepest integration. Section 2 Can I use DXP with an existing framework like Next.js or Nuxt? Yes. DXP provides framework adapters for Next.js, Nuxt, Remix, Astro, SvelteKit, and vanilla React/Vue. The adapters handle data fetching, preview mode, and incremental static regeneration with zero configuration. Section 3 How are SDKs kept in sync with the API? SDKs are auto-generated from the DXP API schema. When you add a content type or change a field, regenerating the SDK updates all types automatically. CI/CD pipelines can include type generation as a build step. Section 4 Is there a local development experience? Yes. The DXP CLI starts a local dev server with hot-reload, content preview, API mocking, and seed data loading. You can develop and test offline with full functionality. features cli: true lsp: true sdks: true extensions: true Relationships products - DXP — https://babadook.tech/products/dxp modules - DXP CLI & SDK — https://babadook.tech/modules/dxp-cli-sdk - Editor Extensions — https://babadook.tech/modules/editor-extensions - Framework Compatibility — https://babadook.tech/modules/framework-compatibility - Language Server — https://babadook.tech/modules/language-server deployment types - Air-Gapped - Cloud (SaaS) - Self-Hosted