cbcfd9599f
Snapshots all four versioned Docusaurus sections at v6.1.0. Built on top of the version-cutting tooling work in chore/docs-cut-6.1.0-versions so the snapshot benefits from: - Auto-gen refresh before snapshotting (database pages from engine spec metadata, API reference from openapi.json, component pages from Storybook stories) — captured at the SHA we cut from rather than whatever happened to be on disk. - Data-import freeze: country list, feature flag table, database diagnostics, and component metadata are copied into snapshot-local `_versioned_data/` dirs so the historical version doesn't silently mutate when the source files change. - Depth-aware import-path rewriter that handles deeply-nested component MDX files referencing `../../../src/` from the snapshot. Versioning behavior: `lastVersion` stays at `current` for every section, so the canonical URLs (`/docs/...`, `/admin-docs/...`, `/developer-docs/...`, `/components/...`) continue to render content from master. The `current` version is consistently labeled "Next" with an `unreleased` banner, and `6.1.0` is a historical pin accessible only via its explicit version segment. Component playground: previously `disabled: true` in versions-config.json, now enabled and versioned. The plugin block in docusaurus.config.ts was already gated only by the `disabled` flag, so no other code changes were needed to bring it back online. The frozen `databases.json` in the snapshot is the canonical 80-database artifact from the latest committed state in master (preserved by the generator's input-hash cache), not a fallback regenerated from a local Flask environment.
5.2 KiB
title, sidebar_position
| title | sidebar_position |
|---|---|
| Overview | 1 |
Developer Docs
Welcome to the Apache Superset Developer Docs - your comprehensive resource for contributing to and extending Apache Superset.
Quick Start
New Contributors
Extension Development
Documentation Sections
Extensions
Learn how to build powerful extensions that enhance Superset's capabilities. This section covers the extension architecture, development patterns, and deployment strategies. You'll find comprehensive guides on creating frontend contributions, managing extension lifecycles, and understanding security implications.
Testing
Comprehensive testing strategies for Superset development. This section covers frontend testing with Jest and React Testing Library, backend testing with pytest, end-to-end testing with Playwright, and CI/CD pipeline best practices.
Contributing to Superset
Everything you need to contribute to the Apache Superset project. This section includes community guidelines, development environment setup, pull request processes, code review workflows, issue reporting guidelines, and Apache release procedures. You'll also find style guidelines for both frontend and backend development.
Development Resources
Prerequisites
- Python: 3.9, 3.10, or 3.11
- Node.js: 18.x or 20.x
- npm: 9.x or 10.x
- Git: Basic understanding
- React/TypeScript: For frontend development
- Flask/SQLAlchemy: For backend development
Key Technologies
- Frontend: React, TypeScript, Ant Design, Redux
- Backend: Flask, SQLAlchemy, Celery, Redis
- Build Tools: Webpack, Babel, npm/yarn
- Testing: Jest, Pytest, Playwright
- CI/CD: GitHub Actions, pre-commit
Community
Get Help
- Slack - Join #development, #troubleshooting, or #beginners
- GitHub Discussions - Ask questions and share ideas
- Mailing Lists - Development discussions
Contribute
- Good First Issues - Start here!
- Help Wanted - Issues needing help
- Roadmap - See what's planned
Additional Resources
External Documentation
- User Documentation - Using Superset
- API Documentation - REST API reference
- Configuration Guide - Setup and configuration
Important Files
- CLAUDE.md - LLM development guide
- UPDATING.md - Breaking changes log
Where to Start?
|
I want to contribute code |
I want to build an extension |
|
I found a bug |
I need help |
Welcome to the Apache Superset community! We're excited to have you contribute.