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: README.md
+35-16
Original file line number
Diff line number
Diff line change
@@ -70,8 +70,8 @@ Formatting:
70
70
- Use sentence case for all titles and headings.
71
71
- Use H1 headings for the page title. Use H2 and H3 as subheadings. Use H4 headings to introduce example code snippets.
72
72
- Never stack headings with no content between them. Add content or remove a heading, likely the latter so as to avoid adding non-essential text.
73
-
- Use [bulleted lists](https://docs.splunk.com/Documentation/StyleGuide/current/StyleGuide/Bulletlists) for non-linear lists.
74
-
- Use [numbered lists](https://docs.splunk.com/Documentation/StyleGuide/current/StyleGuide/Tasklists) for procedures or ordered tasks.
73
+
- Use <ahref="https://docs.splunk.com/Documentation/StyleGuide/current/StyleGuide/Bulletlists"target="_blank">bulleted lists</a> for non-linear lists.
74
+
- Use <ahref="https://docs.splunk.com/Documentation/StyleGuide/current/StyleGuide/Tasklists"target="_blank">numbered lists</a> for procedures or ordered tasks.
75
75
- Use relative links to link to other files or sections in Soda documentation.
76
76
- Use hard-coded links to link to external sources.
77
77
- Liberally include links to the [Glossary]({% link soda/glossary.md %}), but only link the first instance of a term on a page, not all instances.
@@ -84,6 +84,19 @@ Content:
84
84
- Produce content that focuses on how to achieve a goal or solve a problem and, insofar as it is practical, is inclusive of all products. Avoid creating documentation that focuses on how to use a single product. For example, instead of writing two documents -- one for "Troubleshoot Soda SQL" and one for "Troubleshoot Soda Cloud" -- write one Troubleshoot document that offers guidance for both tools.
85
85
- Remember that Every Page is Page One for your reader. Most people enter your docs by clicking on the result of a Google search, so they could land anywhere and you should assume your new page is the first page that a new reader lands on. Give them the context for what they are reading, lots of "escape hatches" to the glossary or pre-requisite procedures, and instructions on what to read next in a "Go further" section at the bottom of all Concept or Task pages.
86
86
87
+
### Release note documentation
88
+
89
+
Document the details of each Soda SQL and Soda Cloud release using included release note files.
90
+
91
+
1. Create a new branch in this Docs repo to create your product release notes.
92
+
2. To the `_release-notes` folder in this Docs repo, add a new markdown file for your new product release notes. Follow the file naming structure established by existing files.
93
+
3. Copy and paste the contents of the `template-soda-cloud-rn.md` file or the `template-soda-sql-rn.md` file into your new file.
94
+
4. Write your release notes using the style guide for guidance on format, language, etc.
95
+
5. Spell check your content. (Copy paste to a Google Doc or your favorite editor to run a spell check.)
96
+
6. Commit your changes, then create a new pull request when you are ready to publish.
97
+
7. In the new pull request, request a review by @janet-can if you wish, or simply squash and merge to publish.
98
+
99
+
87
100
### Use Jekyll markdown
88
101
89
102
Kramdown is the default markdown renderer that Jekyll uses.
@@ -140,29 +153,35 @@ Show code:
140
153
```
141
154
To keep the numbered list intact, apply endraw to the end of the line of preceding text; do not prepend with a line break.
142
155
156
+
Add Last modified date:
143
157
144
-
### Redirecting site visitors
145
-
146
-
The `jekyll-redirect-from` plugin is installed, allowing authors to redirect users if a page is moved.
147
-
148
-
See documentation: https://github.com/jekyll/jekyll-redirect-from
149
-
150
-
To apply a redirect, navigate to the redirect destination file, then add the following to the file metadata at the top:
New monitor type "Schema Evolution" is now available for Soda Cloud. Read the [Schema evolution monitor docs]({% link soda-cloud/schema-evolution.md %}) to learn more.
- Core: fix time option as it's always set to "now" by default
9
+
- Core: Update dev requirements
10
+
- Core: Update readme with dialect status (#477)
11
+
- Core: Update Tox in dev requirements to prevent version deadlock (#474)
12
+
- BigQuery: fix NoneType issue when credentials are not sufficient for BigQuery (#472)
13
+
- BigQuery: Update bigquery dependency version (#470)
14
+
- MySQL: Fix MySQL dialect issues (#475)
15
+
16
+
Refer to the <ahref="https://github.com/sodadata/soda-sql/blob/main/CHANGELOG.md#210b16---2021-09-07-celeborn"target="_blank">Soda SQL Changelog</a> for details.
Single sign-on support is now available for Soda Cloud with SAML 2.0 Identity Providers (IdP), Okta and Azure AD. Contact <ahref="mailto:[email protected]">Soda Support</a> to set up Soda Cloud as a service provider in your SSO IdP so that users in your organization must log in to Soda Cloud via the IdP. Read the [Single sign-on docs]({% link soda-cloud/sso.md %}) to learn more about activating and using SSO with Soda Cloud.
Copy file name to clipboardExpand all lines: soda/product-overview.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -54,10 +54,11 @@ Get started with the [Quick start tutorial for Soda Cloud]({% link soda-cloud/qu
54
54
|Configure scan YAML to send <br />[failed row samples]({% link soda-sql/send-failed-rows.md %}) to Soda Cloud | Use a missing value metric type to [collect failed row samples]({% link soda-cloud/failed-rows.md %}#use-a-missing-value-metric-type-to-collect-failed-row-samples)|
55
55
|| View [failed rows]({% link soda-cloud/failed-rows.md %}) |
56
56
| Configure scan YAML to send <br />[sample dataset data]({% link soda-sql/samples.md %}) to Soda Cloud |[Enable sample data]({% link soda-cloud/display-samples.md %}) for a dataset |
57
-
|| View sample data for a dataset |
57
+
|| View [sample data]({% link soda-cloud/display-samples.md %}) for a dataset |
58
58
||[Disable sending all sample data]({% link soda-cloud/display-samples.md %}#disable-sample-data) to Soda Cloud |
59
59
|| Use [anomaly detection]({% link soda-cloud/anomaly-detection.md %}) |
60
60
| | [Collaborate]({% link soda-cloud/collaborate.md %}) with your team to monitor your data: invite team members, and integrate with Slack
61
+
|| Set up [Single sign-on for Soda Cloud]({% link soda-cloud/sso.md %}) so that all users in your organization must use your IdP to access Soda Cloud. |
61
62
|| Manage [user access]({% link soda-cloud/roles-and-rights.md %}) to your organization and its datasets. |
0 commit comments