{"id": "writing_plugins:writing-plugins-custom-templates", "page": "writing_plugins", "ref": "writing-plugins-custom-templates", "title": "Custom templates", "content": "If your plugin has a  templates/  directory, Datasette will attempt to load templates from that directory before it uses its own default templates. \n             The priority order for template loading is: \n             \n                 \n                     templates from the  --template-dir  argument, if specified \n                 \n                 \n                     templates from the  templates/  directory in any installed plugins \n                 \n                 \n                     default templates that ship with Datasette \n                 \n             \n             See  Custom pages and templates  for more details on how to write custom templates, including which filenames to use to customize which parts of the Datasette UI. \n             Templates should be bundled for distribution using the same  package_data  mechanism in  setup.py  described for static assets above, for example: \n             package_data = (\n    {\n        \"datasette_plugin_name\": [\n            \"templates/my_template.html\",\n        ],\n    },\n) \n             You can also use wildcards here such as  templates/*.html . See  datasette-edit-schema  for an example of this pattern.", "breadcrumbs": "[\"Writing plugins\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette-edit-schema\", \"label\": \"datasette-edit-schema\"}]"}