You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
-
# Contribute to TigerData documentation
1
+
# Contribute to Tiger Data documentation
2
2
3
-
TigerData documentation is open for contribution from all community members. The current source is in this repository.
3
+
Tiger Data documentation is open for contribution from all community members. The current source is in this repository.
4
4
5
-
This page explains the structure and language guidelines for contributing to TigerData documentation. See the [README][readme] for how to contribute.
5
+
This page explains the structure and language guidelines for contributing to Tiger Data documentation. See the [README][readme] for how to contribute.
6
6
7
7
## Language
8
8
9
-
Write in a clear, concise, and actionable manner. TigerData documentation uses the [Google Developer Documentation Style Guide][google-style] with the following exceptions:
9
+
Write in a clear, concise, and actionable manner. Tiger Data documentation uses the [Google Developer Documentation Style Guide][google-style] with the following exceptions:
10
10
11
11
- Do not capitalize the first word after a colon.
12
12
- Use code font (back ticks) for UI elements instead of semi-bold.
@@ -20,7 +20,7 @@ Each major doc section has a dedicated directory with `.md` files inside, repres
20
20
- A short intro describing the main subject of the page.
21
21
- A visual illustrating the main concept, if relevant.
22
22
- Paragraphs with descriptive headers, organizing the content into logical sections.
23
-
- Procedures to describe the sequence of steps to reach a certain goal. For example, create a Tiger service.
23
+
- Procedures to describe the sequence of steps to reach a certain goal. For example, create a Tiger Cloud service.
24
24
- Other visual aids, if necessary.
25
25
- Links to other relevant resources.
26
26
@@ -54,22 +54,22 @@ The navigation hierarchy of a doc section is governed by `page-index/page-index.
54
54
55
55
```js
56
56
{
57
-
title:"Tiger services",
57
+
title:"Tiger Cloud services",
58
58
href:"services",
59
-
excerpt:"About Tiger services",
59
+
excerpt:"About Tiger Cloud services",
60
60
children: [
61
61
{
62
62
title:"Services overview",
63
63
href:"service-overview",
64
-
excerpt:"Tiger services overview",
64
+
excerpt:"Tiger Cloud services overview",
65
65
},
66
66
{
67
67
title:"Service explorer",
68
68
href:"service-explorer",
69
-
excerpt:"Tiger services explorer",
69
+
excerpt:"Tiger Cloud services explorer",
70
70
},
71
71
{
72
-
title:"Troubleshooting Tiger services",
72
+
title:"Troubleshooting Tiger Cloud services",
73
73
href:"troubleshooting",
74
74
type:"placeholder",
75
75
},
@@ -100,7 +100,7 @@ live in the `_partials` top-level directory. To make a new partial, create a new
100
100
101
101
## Formatting
102
102
103
-
In addition to all the [regular Markdown formatting][markdown-syntax], the following elements are available for TigerData docs:
103
+
In addition to all the [regular Markdown formatting][markdown-syntax], the following elements are available for Tiger Data docs:
104
104
105
105
- Procedure blocks
106
106
- Highlight blocks
@@ -113,7 +113,7 @@ See [Formatting examples][formatting] for how to use them.
113
113
114
114
## Variables
115
115
116
-
TigerData documentation uses variables for its product names, features, and UI elements in Tiger Console with the following syntax: `$VARIABLE_NAME`. Variables do not work inside the following:
116
+
Tiger Data documentation uses variables for its product names, features, and UI elements in Tiger Cloud Console with the following syntax: `$VARIABLE_NAME`. Variables do not work inside the following:
117
117
118
118
- Front matter on each page
119
119
- HTML tables and tabs
@@ -145,8 +145,8 @@ To make a documentation page more visible and clear for Google:
145
145
- Summarize the contents of each paragraph in the first sentence of that paragraph.
146
146
- Include main page keywords into the meta tags, page title, first header, and intro. These are usually the names of features described in the page. For example, for a page dedicated to creating hypertables, you can use the keyword **hypertable** in the following way:
147
147
148
-
- Title: Create a hypertable in Tiger
149
-
- Description: Turn a regular $PG table into a hypertable in a few steps, using Tiger Console.
148
+
- Title: Create a hypertable in Tiger Cloud
149
+
- Description: Turn a regular Postgres table into a hypertable in a few steps, using Tiger Cloud Console.
<h3>Tiger is the modern Postgres data platform for all your applications. It enhances Postgres to handle time series, events, real-time analytics, and vector search—all in a single database alongside transactional workloads.
11
+
<h3>Tiger Cloud is the modern Postgres data platform for all your applications. It enhances Postgres to handle time series, events, real-time analytics, and vector search—all in a single database alongside transactional workloads.
[](https://console.cloud.timescale.com/signup)
16
+
[](https://console.cloud.timescale.com/signup)
17
17
18
18
</div>
19
19
20
-
This repository contains the current source for TigerData documentation available at https://docs.tigerdata.com/.
20
+
This repository contains the current source for Tiger Data documentation available at https://docs.tigerdata.com/.
21
21
22
-
We welcome contributions! You can contribute to TigerData documentation in the following ways:
22
+
We welcome contributions! You can contribute to Tiger Data documentation in the following ways:
23
23
24
24
-[Create an issue][docs-issues] in this repository and describe the proposed change. Our doc team takes care of it.
25
25
- Update the docs yourself and have your change reviewed and published by our doc team.
26
26
27
-
## Contribute to the TigerData docs
27
+
## Contribute to the Tiger Data docs
28
28
29
29
To make the contribution yourself:
30
30
@@ -45,9 +45,9 @@ To make the contribution yourself:
45
45
46
46
See the [Contributing guide](CONTRIBUTING.md) for style and language guidance.
47
47
48
-
## Learn about TigerData
48
+
## Learn about Tiger Data
49
49
50
-
TigerData is Postgres made powerful. To learn more about the company and its products, visit [tigerdata.com](https://www.tigerdata.com).
50
+
Tiger Data is Postgres made powerful. To learn more about the company and its products, visit [tigerdata.com](https://www.tigerdata.com).
You are charged for all active $SERVICE_SHORTs in your account, even if you are not actively using them. To reduce costs, pause or delete your unused $SERVICE_SHORTs.
Copy file name to clipboardExpand all lines: _partials/_cloud-installation.md
+14-10Lines changed: 14 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
3
3
You create a $ACCOUNT_LONG to manage your $SERVICE_SHORTs and data in a centralized and efficient manner in $CONSOLE. From there, you can create and delete $SERVICE_SHORTs, run queries, manage access and billing, integrate other services, contact support, and more.
4
4
5
-
<Tabslabel="Create a Tiger account"persistKey="source-cloud">
5
+
<Tabslabel="Create a Tiger Cloud account"persistKey="source-cloud">
6
6
7
-
<Tabtitle="Tiger"label="tiger-cloud">
7
+
<Tabtitle="Tiger Cloud"label="tiger-cloud">
8
8
9
9
You create a standalone account to manage $CLOUD_LONG as a separate unit in your infrastructure, which includes separate billing and invoicing.
10
10
@@ -16,11 +16,13 @@ To set up $CLOUD_LONG:
16
16
17
17
Open [Sign up for $CLOUD_LONG][timescale-signup] and add your details, then click `Start your free trial`. You receive a confirmation email in your inbox.
18
18
19
-
1.**In the confirmation email, click the link supplied and sign in to [$CONSOLE][tsc-portal]**
19
+
1.**Confirm your email address**
20
20
21
-
1.**Answer the requirements questions**
21
+
In the confirmation email, click the link supplied.
22
22
23
-
Your answers help us optimize $SERVICE_LONGs for your use cases.
23
+
1.**Select the [pricing plan][pricing-plans]**
24
+
25
+
You are now logged into $CONSOLE_LONG. You can change the pricing plan to better accommodate your growing needs on the [`Billing` page][console-billing].
24
26
25
27
</Procedure>
26
28
@@ -35,7 +37,7 @@ case, $CLOUD_LONG is a line item in your AWS invoice.
35
37
36
38
To set up $CLOUD_LONG via AWS:
37
39
38
-
1.**Open [AWS Marketplace][aws-marketplace] and search for `Tiger`**
40
+
1.**Open [AWS Marketplace][aws-marketplace] and search for `Tiger Cloud`**
39
41
40
42
You see two pricing options, [pay-as-you-go][aws-paygo] and [annual commit][aws-annual-commit].
41
43
@@ -51,13 +53,13 @@ To set up $CLOUD_LONG via AWS:
51
53
52
54
Add your details, then click `Start your free trial`. If you want to link an existing $ACCOUNT_LONG to AWS, log in with your existing credentials.
Your $CLOUD_LONG and AWS accounts are now connected.
58
+
You are now logged into $CONSOLE_LONG. You can change the pricing plan later to better accommodate your growing needs on the [`Billing` page][console-billing].
0 commit comments