Note: ODDK now has a custom search facet, update_frequency. To display this properly in the UI, a small change was needed in frontend-v2. Instead of hardcoding the custom facet in the master branch, the change is in its own branch, oddk/custom-facet. When there's a better way to handle or override this somewhere else (e.g. in this theme or in ckanext-portalopendatadk), we can switch back to using the master branch of frontend-v2. Until then, you should use the oddk/custom-facet branch of frontend-v2 for development and deployments.

To watch files:

npx gulp

This watches for changes to CSS and icons. On changes to CSS PostCSS and plugins (postcss-import, postcss-preset-env, tailwindcss, cssnano) are run. On icon changes, the SVG icon sprite is remade. These processes can be run without watching via npx gulp css and npx gulp icons.

Note: Unless you are making significant changes to the design, you probably won't need these processes. Most styling is done through Tailwind's utility classes.

The CSS framework Tailwind is used to style this theme. This means that if you want to change the appearance of something, or add new elements, Tailwind utility classes should provide you with what you need. The docs at tailwindcss.com should provide you with most of what you need to know.

Some styles have been extracted out into CSS files (src/css/components). The spirit of Tailwind would be to avoid doing this, but there are two scenarios where it becomes desirable, or necessary.

1. You are repeating a combination of utility classes.
2. You need aspects of CSS that is not catered for by Tailwind.

Scenario 1 should probably be resolved with the use of (Nunjucks) templates where reasonable to do so. This codebase could probably be improved a little in that regard.

In either scenario, the @apply feature is and should be used, whenever dealing with the variable-like utility classes, such as width, padding, colour etc. This ensures that the same variables are being used throughout, and that a change to the Tailwind configuration will effect these custom components.

In addition to the components directory, there is an elements.css file, which adds some styles to base HTML tags, mostly when nested in specific containers. For example, headings and paragraphs within a content wrapper get styling, without the need to add classes to each element.

(This convention of components and elements is not Tailwind related, but part of a general approach to making stuff easy to find.)

All Tailwind classes and custom components are imported into src/app.css. The importing, and other operations (such as Tailwind) are handled by PostCSS plugins, as defined in gulpfile.js.

Tailwind is configured in tailwind.config.js. The configuration for this theme adds an additional spacing variable named gutter, to remove some of the guess work from spacing e.g "Was I using p-4 or p-6 to separate columns?". The default colour and font family have been replaced. Note, unlike the addition of the gutter value, colour and font family were replaced, so the values found in the Tailwind docs will not be applicable.

Icons are used like so: <svg><use xlink:href="#<filename>" /></svg>. Eg. to use the src/icons/search.svg icon, you put the following in the template: <svg><use xlink:href="#search" /></svg>.