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
|`data.json`| Generates a [project open data](https://project-open-data.cio.gov/v1.1/schema/)-compliant `data.json` file that can be used to harvest the JKAN site into other data catalogs. |
31
31
|`datasets.json`| Generates a list of datasets used to populate the `datasets-list` component (as seen on the `/datasets/` page). |
32
-
|`_data/schemas`|[Schema definition files](/docs/configuration.md), which list the fields each dataset, category, and organization should have. |
32
+
|`_data/schemas`| Schema definition files which list the fields each dataset, category, and organization should have. |
33
33
|`_data/licenses.yml`| A list of licenses that datasets can be associated with |
34
34
|`_datasets`| A directory of `.md` files containing dataset information in YAML front-matter |
35
35
|`_dataset_categories`| A directory of `.md` files containing dataset categories in YAML front-matter |
@@ -67,6 +67,8 @@ A component is just an [ES6 class](https://developer.mozilla.org/en-US/docs/Web/
67
67
68
68
By convention, elements within a component's HTML markup that need to be referenced by JavaScript are designated using a `data-hook` attribute, an idea [borrowed from ampersand.js](https://ampersandjs.com/learn/data-hook-attribute/) that helps keep styling and JavaScript concerns separate. For example, the `datasets-list` component looks for 3 elements within it: a place to put the count of datasets, a search box, and the place to list the dataset items themselves.
0 commit comments