github/datasette
1
0
Fork 0
mirror of https://github.com/simonw/datasette.git synced 2025-12-10 16:51:24 +01:00
Code Issues Projects Releases Packages Wiki Activity

Fixed some rST header warnings

Browse source
This commit is contained in:
Simon Willison 2023-10-12 15:05:02 -07:00
commit 11f7fd38a4
2 changed files with 14 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

20
docs/configuration.rst
View file

@ -118,6 +118,7 @@ Here's a full example of all the valid configuration options that can exist insi
} }
} }
} }
.. [[[end]]] .. [[[end]]]
.. _configuration_reference_settings: .. _configuration_reference_settings:
@ -275,26 +276,19 @@ For database level or table level plugin configuration, nest it under the approp
.. _configuration_reference_permissions: .. _configuration_reference_permissions:
Permissions Configuration Permissions configuration
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~
TODO
.. _configuration_reference_authentication:
Authentication Configuration
~~~~~~~~~~~~~~~~~~~~
TODO TODO
.. _configuration_reference_canned_queries: .. _configuration_reference_canned_queries:
Canned Queries Configuration Canned queries configuration
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TODO TODO
.. _configuration_reference_css_js: .. _configuration_reference_css_js:
Extra CSS and JS Configuration Extra CSS and JS configuration
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TODO TODO

19
docs/metadata.rst
View file

@ -693,14 +693,14 @@ Here's an example of a ``metadata.yml`` file, re-using an example from :ref:`can
.. _metadata_reference: .. _metadata_reference:
Metadata Reference Metadata reference
----------------------- ------------------
A full reference of every supported option in a ``metadata.json`` or ``metadata.yaml`` file. A full reference of every supported option in a ``metadata.json`` or ``metadata.yaml`` file.
Top-level Metadata Top-level metadata
~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~
"Top-level" metadata refers to fields that can be specified at the root level of a metadata file. These attributes are meant to describe the entire Datasette instance. "Top-level" metadata refers to fields that can be specified at the root level of a metadata file. These attributes are meant to describe the entire Datasette instance.
@ -715,11 +715,8 @@ The following are the full list of allowed top-level metadata fields:
- ``source`` - ``source``
- ``source_url`` - ``source_url``
Database-level metadata
~~~~~~~~~~~~~~~~~~~~~~~
Database-level Metadata
~~~~~~~~~~~~~~~~~~
"Database-level" metadata refers to fields that can be specified for each database in a Datasette instance. These attributes should be listed under a database inside the `"databases"` field. "Database-level" metadata refers to fields that can be specified for each database in a Datasette instance. These attributes should be listed under a database inside the `"databases"` field.
@ -732,15 +729,13 @@ The following are the full list of allowed database-level metadata fields:
- ``about`` - ``about``
- ``about_url`` - ``about_url``
Table-level metadata
Table-level Metadata ~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~
"Table-level" metadata refers to fields that can be specified for each table in a Datasette instance. These attributes should be listed under a specific table using the `"tables"` field. "Table-level" metadata refers to fields that can be specified for each table in a Datasette instance. These attributes should be listed under a specific table using the `"tables"` field.
The following are the full list of allowed table-level metadata fields: The following are the full list of allowed table-level metadata fields:
- ``source`` - ``source``
- ``source_url`` - ``source_url``
- ``license`` - ``license``