Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove "next" site #1261

Closed
1 task done
jtcohen6 opened this issue Mar 22, 2022 · 0 comments · Fixed by #1340
Closed
1 task done

Remove "next" site #1261

jtcohen6 opened this issue Mar 22, 2022 · 0 comments · Fixed by #1340
Labels
engineering improvement that requires site engineering help or back up

Comments

@jtcohen6
Copy link
Collaborator

jtcohen6 commented Mar 22, 2022

Contributions

  • I have read the contribution docs, and understand what's expected of me.

What page(s) or areas on docs.getdbt.com are affected?

Now that docs are versioned, we no longer need the twin deployments at docs.getdbt.com and next.docs.getdbt.com... right?

What changes are you suggesting?

We can remove logic put by yours truly in:

  • docusaurus.config.js
  • netlify.toml (PRERELEASE = "true")
  • Netlify to deploy the next branch
  • Algolia, which runs a separate search index for the "next" site... that never worked quite right

Let's also:

  • update the PR template, to mention VersionBlock instead of the next branch
  • set up a CNAME redirect from next.docs.getdbt.com to docs.getdbt.com
  • just have one branch named main :)

Additional information

No response

@jtcohen6 jtcohen6 added the engineering improvement that requires site engineering help or back up label Mar 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering improvement that requires site engineering help or back up
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant