chore(docs): change stacks-docs-next to stacks-docs (#2250)

* chore(docs): change stacks-docs-next to stacks-docs

* chore(docs): remove legacy docs dependencies

* fix(docs): resolve docs check errors

* fix(docs): remove legacy llms content fetch

* ci: update release branch workflow

* docs(docs): remove legacy docs navigation guidance

* chore(docs): remove obsolete docs ignore rules

* docs(docs): update local dev instructions

* refactor(docs): use turndown for llms output

* fix(docs): clone private docs during build

* chore: prune stale gitignore entries

* fix(docs): include svelte check in lint

* fix(docs): build svelte before docs check

* fix auth base url

* Revert "fix auth base url"

This reverts commit 1c8e191.

* fix auth base url… again

* chore: trigger ci

---------

Co-authored-by: Dan Cormier <dancormierall@gmail.com>

Author: ttaylor-stack

.github/workflows/main.yml

@@ -2,9 +2,9 @@ name: CI
 
 on:
   push:
-    branches: [develop, beta, main]
+    branches: [main, beta]
   pull_request:
-    branches: [develop, beta, main]
+    branches: [main, beta]
 
 jobs:
   build-and-test:
@@ -55,7 +55,7 @@ jobs:
 
   release:
     name: Release (latest or beta)
-    if: github.ref == 'refs/heads/develop' || github.ref == 'refs/heads/beta'
+    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/beta'
     needs: [build-and-test]
     runs-on: ubuntu-latest
     outputs:
@@ -80,7 +80,7 @@ jobs:
           title: "chore(new-release)"
           commit: "chore(new-release)"
           branch: ${{ github.ref == 'refs/heads/beta' && 'beta' || null }}
-          createGithubReleases: ${{ github.ref == 'refs/heads/develop' }}
+          createGithubReleases: ${{ github.ref == 'refs/heads/main' }}
         env:
           GITHUB_TOKEN: ${{ secrets.STACKS_TOOLING_GH_RW_PAT }}
           NPM_TOKEN: ${{ secrets.NPM_API_KEY }}
@@ -96,25 +96,6 @@ jobs:
                 This is necessary because the PR is updated by github-actions[bot].
                 This is a technical user which does not trigger actions workflows on push events.
                 See this GH issue for more details: https://github.com/changesets/action/issues/187
-
-  update-docs:
-    name: Update main site stackoverflow.design
-    if: ${{ needs.release.outputs.published == 'true' && github.ref == 'refs/heads/develop' }}
-    needs: [build-and-test, release]
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v5
-      - name: 🔄 Update stackoverflow.design docs
-        run: |
-            git config --global user.name 'github-actions[bot]'
-            git config --global user.email 'github-actions[bot]@users.noreply.github.com'
-            git fetch origin
-            git checkout production
-            git merge --no-ff --allow-unrelated-histories origin/develop -m "chore: merge develop into production"
-            git push origin production
-        env:
-            GITHUB_TOKEN: ${{ secrets.STACKS_TOOLING_GH_RW_PAT }}
-
 # cancel the jobs if another workflow is kicked off for the same branch
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}

.gitignore

@@ -1,29 +1,6 @@
-# Compiled source #
-###################
-*.com
-*.class
-*.dll
-*.exe
-*.o
-*.so
-
-# Packages #
-############
-# it's better to unpack these files and commit the raw source
-# git has its own built in compression methods
-*.7z
-*.dmg
-*.gz
-*.iso
-*.jar
-*.rar
-*.tar
-
-# Logs and databases #
-######################
+# Logs #
+########
 *.log
-*.sql
-*.sqlite
 
 # OS generated files #
 ######################
@@ -37,53 +14,33 @@ Thumbs.db
 *_rsa
 *_rsa.pub
 
-# Sublime #
-######################
-*.sublime-workspace
-
-# 11ty Site #
-###############
-# This is compiled by Netlify on its servers, so no need to include it.
-_site/
-.asset-cache
-
-# Komodo Edit #
-###############
-*.komodoproject
-
 # NPM #
 ###############
-node_modules
+node_modules/
 
 # Compiled CSS/JS #
 ###############
-dist/
-/packages/stacks-docs/assets/css/
-/packages/stacks-docs/assets/js/stacks.*
-/packages/stacks-docs/assets/js/controllers.js
-/packages/stacks-docs/assets/js/controllers.js.map
-/packages/stacks-docs/assets/js/library.*
+/packages/stacks-classic/dist/
+/packages/stacks-svelte/netlify/dist/
+/packages/stacks-utils/dist/
 /build/
+
+# Build caches #
+################
 .tscache
+*.tsbuildinfo
+.svelte-kit/
+
+# Private docs are cloned during docs builds and must not be tracked.
+/packages/stacks-docs/src/docs/private/
 
 # legacy compiled files -- these are no longer generated, but may still be lingering around
 /packages/stacks-classic/lib/css/*.css
 
-# Environment normalization #
-###############
-/packages/stacks-docs/.bundle
-/packages/stacks-docs/vendor/bundle
-/packages/stacks-docs/_includes/svg-icons
-/packages/stacks-docs/_includes/svg-spots
-
 # Testing Assets #
 ###############
 **/screenshots/**/failed/**
 
-# GitHub Actions #
-###############
-/.github/main.workflow
-
 # Editors #
 ###########
 /.idea
@@ -92,6 +49,4 @@ dist/
 ################
 **/storybook-static
 .eslintcache
-*.tsbuildinfo
-.svelte-kit
-/packages/stacks-svelte/lib/
+/packages/stacks-svelte/lib/

.gitmodules

@@ -98,7 +98,7 @@ Draft PRs are welcome for work in progress, but we focus our review time on PRs
    ```
 6. Push your branch and [open a pull request](https://github.com/StackExchange/Stacks/pulls) with a clear title and description.
 
-All pull requests should target the `main` branch. Pull requests targeting `production` will be rejected.
+All pull requests should target the `main` branch unless the Stacks team specifically asks you to target a release branch.
 
 ## Changesets
 

CONTRIBUTING.md

@@ -178,14 +178,14 @@ We use [changesets](https://github.com/changesets/changesets) to automatize the
 
 - Every time you do work that requires a new release to be published, [add a changesets entry](https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md) by running `npx changeset` and follow the instructions on screen. (changes that do not require a new release - e.g. changing a test file - don't need a changeset).
     - When opening a PR without a corresponding changeset the [changesets-bot](https://github.com/apps/changeset-bot) will remind you to do so. It generally makes sense to have one changeset for PR (if the PR changes do not require a new release to be published the bot message can be safely ignored)
-- The [release github workflow](.github/workflows/main.yml) continuously checks if there are new pending changesets in the `beta` branch; if there are, it creates a GH PR (`chore(release)` [see example](https://github.com/StackExchange/apca-check/pull/2)) and continues updating it as more changesets are pushed/merged to the `beta` branch.
-- When we are ready to cut a release we need to simply merge the `chore(release)` PR and the release github workflow will take care of publishing the changes to NPM and create a GH release for us. The `chore(release)` PR also give us an opportunity to adjust the automatically generated changelog when necessary (the entry in the changelog file is also what will end up in the GH release notes).
+- The [release github workflow](.github/workflows/main.yml) runs on `main` and `beta`. On `beta`, it creates and updates the `chore(release)` PR as pending changesets are merged. On `main`, it publishes the latest release to NPM and creates GitHub releases.
+- When we are ready to cut a beta release we merge the `chore(release)` PR. The release github workflow publishes the changes to NPM and gives us an opportunity to adjust the automatically generated changelog before release notes are created.
 
 _The release github workflow only run if the CI workflow (running linter, formatter and tests) is successful: CI is blocking accidental releases_.
 
 _Despite using changesets to communicate the intent of creating releases in a more explicit way, we still follow [conventional commits standards](https://www.conventionalcommits.org/en/v1.0.0/) for keeping our git history easily parseable by the human eye._
 
-Successful releases trigger automatically a new deployment to stackoverflow.design by merging the `main` branch.
+Docs are deployed directly from the current release flow; we no longer merge into a `production` branch to publish stackoverflow.design. Normal contribution PRs target `main`.
 
 ## License
 Code and documentation copyright 2017-2026 Stack Exchange, Inc and released under the [MIT License](/LICENSE.MD).