GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — crate/docs at master · crate/crate

Expand file tree

/

docs

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
/

docs

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
_extra
_extra
 
 
_static
_static
 
 
admin
admin
 
 
appendices
appendices
 
 
concepts
concepts
 
 
config
config
 
 
general
general
 
 
interfaces
interfaces
 
 
sql
sql
 
 
src/doc_tests
src/doc_tests
 
 
README.rst
README.rst
 
 
cli-tools.rst
cli-tools.rst
 
 
conf.py
conf.py
 
 
docutils.conf
docutils.conf
 
 
index.rst
index.rst
 
 
requirements.txt
requirements.txt
 
 

README.rst

Outline

Documentation README

Top-level structure

The documentation is structured as follows:

Section Title Description
Running CrateDB Documentation for the crate command.
Configuration Full documentation for configuration settings, split into sections by topic.
General Use Primary documentation for any feature primarily of interest to a general user, split into sections by topic.
Administration Primary documentation for any feature primarily of interest to a database administrator, split into sections by topic.
SQL Syntax Full documentation for SQL syntax, split into general SQL topics and SQL statements, one document per statement.
Client Interfaces Documentation for client interfaces, split into documents by interface.
Appendices

Supplementary information.

This also includes collection of release notes, one document per release. Each document should contain upgrade information as well as a list of changes.

How to document a feature

A single feature may have three types of documentation:

  • Primary documentation
  • Configuration documentation
  • SQL syntax documentation

Primary documentation is located under one of the following sections:

  • CrateDB SQL
  • Administration
  • Plugins

Primary documentation should cover:

  • What the feature does
  • How the feature can be used

Primary documentation should not include a full configuration settings reference or a full SQL syntax reference. Instead, full references should be added to Configuration or SQL Syntax sections.

When a feature is documented in more than one place, those locations should be interlinked.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.