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

Restructure docs: Lead with Postgres #384

Merged
merged 3 commits into from
Oct 15, 2024
Merged

Conversation

tsg
Copy link
Member

@tsg tsg commented Oct 14, 2024

  • Raised up the generic postgres topics, lowered the "data platform"y topics.
  • Heavily edited the "What is Xata?" section to be more Postgres focus.
  • Removed the references to the Xata Go SDK.

No URLs were harmed in the making of this restructure.

- Raised up the generic postgres topics, lowered the "data platform"y topics.
- Heavily edited the "What is Xata?" section to be more Postgres focus.
- Removed the references to the Xata Go SDK.

No URLs were harmed in the making of this restructure.
@xata-bot
Copy link

xata-bot commented Oct 14, 2024

Check out the preview at https://xata-docs-pr-384.vercel.app

Copy link
Contributor

@snide snide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the UI planning to prevent folks from using files, shouldn't the docs list them as deprecated? I'd also remove mention of them from relevant rollup pages. Since search will now be a toggle, should the docs discuss how to turn them on?

The sample app is heavily files dependent. Should it be removed from the docs as well?

010-Getting-started/010-what-is-xata.mdx Outdated Show resolved Hide resolved
010-Getting-started/010-what-is-xata.mdx Outdated Show resolved Hide resolved
@SferaDev
Copy link
Member

I agree with Dave, even if some features are still available in pro plan, since we don't plan to maintain them or add them to the new platform, I'd undocument them or at least mark them as deprecated.

Copy link
Contributor

@snide snide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tsg explained his reasoning on Slack.

@tsg tsg added this pull request to the merge queue Oct 15, 2024
Merged via the queue into main with commit c8cd5b1 Oct 15, 2024
5 checks passed
@tsg tsg deleted the restructure_lead_with_postgres branch October 15, 2024 16:24
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.

4 participants