docs: bifurcate documentation into user, admin, and developer sections

[rusackas]

SUMMARY

Reorganizes the Superset documentation information architecture by splitting the single "Documentation" section into four distinct sections:

• User Docs (/user-docs/) — End-user guides: quickstart, FAQ, creating dashboards, database connections, SQL templating
• Admin Docs (/admin-docs/) — Installation, configuration, security (moved from /docs/configuration/, /docs/installation/, /docs/security/)
• Developer Docs (/developer-docs/) — Contributing, extensions, testing, guidelines, UI components (renamed from /developer_portal/)
• Community — Existing community pages (unchanged)

Key changes:

• Moved installation/configuration/security docs from docs/docs/ to docs/admin_docs/
• Renamed developer_portal/ to developer_docs/ with URL path /developer-docs/
• Renamed user-facing docs URL from /docs/ to /user-docs/
• Added comprehensive URL redirects for all old paths (/docs/* → new locations, /developer_portal/* → /developer-docs/*)
• Added new user-facing SQL templating guide alongside the admin-level config guide
• Updated all internal cross-references and sidebar links
• Updated versioned docs (v6.0.0) links with correct version prefixes
• Restored content lost during migration (Kubernetes debugging section, pkg-resources migration guide)
• Added missing sidebar entries (extension-points/editors, pkg-resources-migration)
• Updated README.md, DOCS_CLAUDE.md, and LLM instruction files to reflect new structure

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A — documentation restructuring, no UI changes to the Superset application itself.

TESTING INSTRUCTIONS

1. Build the docs site locally:

   cd docs
   npm install
   npm run build

2. Verify the four sections appear in the navbar (Users, Admins, Developers, Community)
3. Verify old URLs redirect correctly:
   • /docs/configuration/configuring-superset → /admin-docs/configuration/configuring-superset
   • /docs/installation/kubernetes → /admin-docs/installation/kubernetes
   • /developer_portal/contributing/overview → /developer-docs/contributing/overview
   • /docs/quickstart → /user-docs/intro
4. Verify sidebar navigation works in all sections
5. Spot-check internal links in admin docs, developer docs, and user docs

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

🤖 Generated with Claude Code

[bito-code-review]

Bito Automatic Review Skipped - Large PR

Bito didn't auto-review this change because the pull request exceeded the line limit. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.

[codeant-ai-for-open-source]

Suggestion: The import example uses a default import from the barrel module, but this module can only have a single default export, so importing one specific component as the default (Slider) is misleading and inconsistent with the pattern used for other components, likely causing consumers to import the wrong value; switch to a named import to correctly reference the Slider component. [possible bug]

Severity Level: Major ⚠️

- ⚠️ Slider import snippet misleads developers integrating Superset components.
- ⚠️ Copy-pasted snippet can cause runtime React element errors.
- ⚠️ Inconsistent with other UI docs using named imports.

Suggested change

	import Slider from '@superset/components';
	import { Slider } from '@superset/components';

Steps of Reproduction ✅

1. Open the Slider UI component docs at
`docs/developer_docs/components/ui/slider.mdx:227-246`, which show the import snippet:

   ```tsx

   import Slider from '@superset/components';

2. Note from docs/src/components/StorybookWrapper.jsx:36-47 and
   docs/src/theme/ReactLiveScope/index.tsx:48-58 that require('@superset/components')
   returns an object (SupersetComponents) whose keys are individual components (e.g.
   Button, Slider) and is merged into a registry by spreading the object, indicating
   components are exposed as properties, not as a single default React component.

3. A developer following the Slider docs copies the snippet import Slider from '@superset/components'; into their own Superset-frontend extension or external React
   project, then uses <Slider /> in JSX expecting a React component.

4. At runtime, because @superset/components is an object of components (per the
   require usage) and not a single default Slider export, Slider will actually be that
   object, causing React to throw "Element type is invalid: expected a string (for built-in
   components) or a class/function but got: object" when rendering, until the import is
   corrected to import { Slider } from '@superset/components';.

</details>
<details>
<summary><b>Prompt for AI Agent 🤖 </b></summary>

```mdx
This is a comment left during a code review.

**Path:** docs/developer_docs/components/ui/slider.mdx
**Line:** 245:245
**Comment:**
	*Possible Bug: The import example uses a default import from the barrel module, but this module can only have a single default export, so importing one specific component as the default (`Slider`) is misleading and inconsistent with the pattern used for other components, likely causing consumers to import the wrong value; switch to a named import to correctly reference the `Slider` component.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.

👍 | 👎

[rusackas]

Good catch — fixed in 779d677. This was a bug in the auto-generated docs: @superset/components only exposes named exports, so the default import would resolve to the module object rather than the component. Fixed this for Slider and 4 other components (Tree, ProgressBar, TableCollection, Tabs) that had the same issue.

[codeant-ai-for-open-source]

Suggestion: The import example for the Tree component uses a default import from the '@superset/components' module, but the components index only provides Tree as a named export, so copying this snippet into real code will fail or not import the component correctly. [logic error]

Severity Level: Major ⚠️

- ⚠️ Tree component docs show incorrect import syntax.
- ⚠️ Copy-pasting snippet into plugins causes import/build failures.

Suggested change

	import Tree from '@superset/components';
	import { Tree } from '@superset/components';

Steps of Reproduction ✅

1. Open `docs/developer_docs/components/ui/tree.mdx` and locate the "Import" section at
lines 257–261, which shows:

   ```tsx

   import Tree from '@superset/components';

2. Create a new React/TypeScript component in a Superset frontend or extension package
   that imports using this snippet:

   import Tree from '@superset/components'; and then renders <Tree treeData={[]} />.

3. Build or type-check the frontend using the same component library used by the docs,
   which exposes components via @superset/components. The module is treated as an object of
   named exports, as seen in docs/src/components/StorybookWrapper.jsx:36–47, where
   require('@superset/components') is spread into a registry and its keys are used as
   component names.

4. Observe that the build or type-check fails (e.g., TypeScript "Module
   '@superset/components' has no default export" or runtime Tree being undefined),
   because Tree is exported from @superset/components as a named export (the Storybook
   story
   superset-frontend/packages/superset-ui-core/src/components/Tree/Tree.stories.tsx:21
   imports Tree from a local index and the docs infrastructure only ever treats
   @superset/components as a bag of named components, not a default export).

</details>
<details>
<summary><b>Prompt for AI Agent 🤖 </b></summary>

```mdx
This is a comment left during a code review.

**Path:** docs/developer_docs/components/ui/tree.mdx
**Line:** 260:260
**Comment:**
	*Logic Error: The import example for the Tree component uses a default import from the '@superset/components' module, but the components index only provides Tree as a named export, so copying this snippet into real code will fail or not import the component correctly.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.

👍 | 👎

[rusackas]

Same issue as the Slider comment above — fixed in 779d677 alongside all other components that had default imports.