Skip to content

website: add the Back to StackQL Docs link and the source repo link - #3

Merged
jeffreyaven merged 4 commits into
stackql-providerfrom
feature/azure-provider-updates
Oct 7, 2026
Merged

jeffreyaven merged 4 commits into
stackql-providerfrom
feature/azure-provider-updates

Conversation

@jeffreyaven

@jeffreyaven jeffreyaven commented Oct 6, 2026 •

Copy link
Copy Markdown

Adds the "Back to StackQL Docs" link at the top of the docs sidebar on all four sites (azure, azure_extras, azure_isv, azure_stack), pointing at /stackqldocs (the redirect to https://stackql.io/), matching the query library site and the stackql-provider-TEMPLATE. The arrow and divider are styled by the .sidebar-back-link rules in each site's stylesheet.

Bumps @stackql/provider-utils to 0.7.12, passes --source-project from bin/generate-docs.sh (SOURCE_PROJECT, overridable) and regenerates the markdown docs for all four providers, so each provider summary links to the source repository.

Migrates all four sites from their self-contained Docusaurus configs to the shared stackql/docusaurus-config (createConfig, vendored into .shared-config at build time), so they pick up the current navbar with the nested providers dropdown, the footer and the shared redirect routes: provider.js; the template's docusaurus.config.js (with the monorepo's repo name and an edit link into each site's directory), sidebars.js, package.json (Docusaurus 3.10.2, Node 22) and .gitignore; src/css/custom.css renamed to global.css; the redirect pages under src/pages and HomepageFeatures removed; the template's DocBreadcrumbs, SchemaTable and StackqlDeployDropdown added; favicons and site.webmanifest at the static root; a netlify.toml per site with the build command and Node 22; yarn.lock regenerated. The template's "Last updated on" stamps are left off: Docusaurus derives them from git log over the whole repository, and this fork's history overflows the buffer.

All four sites were rebuilt locally against the current stackql/docusaurus-config main with no broken links (the azure site needs a 16 GB Node heap and about 4 minutes).

Generated with Claude Code

jeffreyaven and others added 3 commits October 6, 2026 15:54
…epo link

Bumps @stackql/provider-utils to 0.7.11, passes --source-project to the
doc generation target and regenerates the markdown docs, so the provider
summary links to the source repository.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Opens the docs sidebar with a link to /stackqldocs, the redirect to the
main stackql.io docs, matching the query library site and the provider
template. Styled by the new .sidebar-back-link rules in the site
stylesheet. No generated docs or dependencies change.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Keeps the doc generation dependency on the current release. 0.7.12 only
changes the generate-docs-v2 index page (Markdown hard breaks in the
Provider Summary); this provider uses the v1 generator, whose output is
unchanged, so the regenerated docs are identical.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@jeffreyaven jeffreyaven self-assigned this Oct 6, 2026
@netlify

netlify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for stackql-azure-isv-provider ready!

Name Link
🔨 Latest commit ef391af
🔍 Latest deploy log https://app.netlify.com/projects/stackql-azure-isv-provider/deploys/6ac596cbfebbff0008f3aa28
😎 Deploy Preview https://deploy-preview-3--stackql-azure-isv-provider.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for stackql-azure-extras-provider ready!

Name Link
🔨 Latest commit ef391af
🔍 Latest deploy log https://app.netlify.com/projects/stackql-azure-extras-provider/deploys/6ac596cb25b74d00080b2b75
😎 Deploy Preview https://deploy-preview-3--stackql-azure-extras-provider.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for stackql-azure-stack-provider ready!

Name Link
🔨 Latest commit ef391af
🔍 Latest deploy log https://app.netlify.com/projects/stackql-azure-stack-provider/deploys/6ac596cbd92b4600089b6451
😎 Deploy Preview https://deploy-preview-3--stackql-azure-stack-provider.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Moves azure, azure_extras, azure_isv and azure_stack from their
self-contained Docusaurus configs to createConfig from the shared
stackql/docusaurus-config, vendored into .shared-config at build time
by the vendor-config script (prebuild and prestart), so they pick up the
current navbar, the nested providers dropdown, the footer and the shared
redirect routes. Per site: provider.js; the template's
docusaurus.config.js with the monorepo's repo name and edit link,
sidebars.js, package.json (Docusaurus 3.10.2, Node 22) and .gitignore;
src/css/custom.css renamed to global.css with the template's rules; the
redirect pages under src/pages and HomepageFeatures removed (the shared
plugin registers those routes); the template's DocBreadcrumbs,
SchemaTable and StackqlDeployDropdown added; favicons and
site.webmanifest at the static root; a netlify.toml with the build
command and Node 22; yarn.lock regenerated.

The template's "Last updated on" stamps are left off: Docusaurus derives
them from git log --name-status over the whole repository, and this
fork of the azure-sdk-for-python monorepo has a history that overflows
the buffer (MaxBufferError).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@jeffreyaven
jeffreyaven merged commit 701431e into stackql-provider Oct 7, 2026
13 of 14 checks passed
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.

1 participant