This repository contains the guide oriented documentation at xata.io/docs. It does not include the REST API documentation which is stored alongside the private code within Xata itself.

Contributing

PRs are welcome in this repository. Any merges will trigger a build that will update the statically generated website. Our docs use MDX syntax, which adds some extra features to typical Markdown.

Linting

There's a hefty dose of linting through eslint, prettier and remark. If you'd like to see lint errors as you work run pnpm install as you work. husky should make checks on your commits. Similarly, there are GitHub actions that will run on PRs to this repo.

Frontmatter

Each MDX document needs to include the following frontmatter at the top of the page. Most fields should be self-explanatory. The doc.schema.yaml file defines its shape.

---
title: Command line interface
navTitle: CLI
keywords: ['terminal', 'term', 'commands', 'cli']
description: Xata provides a CLI for working with databases
slug: dave/cli
published: true
---

Slugs

The slug field should be written without the /docs/ prefix and should not contain a forward slash, both of which will be added programmatically. The slug is independent from the folder structure of the menu and it is advised to never edit a slug location once the document is live. If this is needed, please contact a Xata engineer to set up a permanent redirect.

Keywords

The keywords field accepts an array of strings, and is the highest rated value for search. This should allow authors to "boost" certain words in search over similarly titled documents.

Folder structure and menus

The folder structure you create in this repository will transform into a collapsible menu system within the site. Write the names of folders in the following syntax: 500-typescript-client. The number prefix can be any number between 0 and 999. When making new pages or folders it is advised to give yourself enough room in between numbers to insert new pages. For example, using values of 25 will give you 24 pages in between each page, and leave plenty of room at the end. The numbers are used to provide the order for the folders and pages within the structure.

MDX Syntax

The following are extra components that can be used within the markdown files.

Alerts

Alerts accept a status prop with values of info | warning | danger.

<Alert status="warning">
  This feature is Beta. It is still under active development. While we are avoiding breaking changes, we do not
  guarantee backwards compatibility until the functionality is GA.
</Alert>

This component assumes your alert is simple and is a simple string (which is good practice). However, if you need multiple lines or other markdown (like links or images) you might need to include extra whitespace for proper rendering:

<Alert status="warning">

Aggregations cannot be used with [link](/docs/concepts/data-model#link) columns.

</Alert>

Images

Images using typical markdown syntax will transform into ones that will work with the Next JS / Vercel pipeline. Images can exist anywhere within this repo, but should be relative to the document they are referenced in

![My image](../images/my-image.png)

Video

When including video in your MDX, utilize the following component. platform accepts html | youtube | vimeo for sources. If your video is not 16x9, you can pass additional width and height properties to properly align responsive aspect ratios.

<ArticleVideo platform="html" src="https://xata.io/images/blog/launch/search.mp4" autoplay loop />

Code syntax

Snippets can have the following syntax on the first line to enable various abilities

tsx  title="my/file.tsx" showLineNumbers {3-5,7} /highlightWord/

You can create tabbed code blocks by enclosing multiple fenced snippets within <TabbedCode>. This is hard to show because of Markdown inception within this Readme, but the below example would have two triple tick code blocks within the component.

<TabbedCode tabs={['Some typescript', 'Some JSON']}>{/*  fence based code blocks within */}</TabbedCode>

<TabbedCode> formatting (careful!)

Using the <TabbedCode> component in MDX can cause very bad formatting issues where prettier / eslint completely destroys the formatting of the file.

The correct way to format the <TabbedCode> component is like this:

<TabbedCode tabs={['TypeScript', 'Python']}>
\n empty line !important
```ts // TypeScript code ```
\n empty line !important
```python
# Python code
```
\n emptyline !important
</TabbedCode>

Example without the comments:

<TabbedCode tabs={['TypeScript', 'Python']}>

```ts
// TypeScript code
```

```python
# Python code
```

</TabbedCode>