Update the ordering of the future talks on the talks page so that
upcoming talks are shown in chronological order (soonest first),
followed by past talks in reverse chronological order (most recent
first).
This still uses the `created` date for ordering, which is updated
automatically on saving the node to match the furthest future talk, but
I may want to move that into a custom node property at some point.
Fixes#140
- Updated npm dependencies
- Replaced `webpack.mix.js` with `webpack.config.js`
- Added `postcss.config.js`
- Removed the `src` directory and moved `css` and `js` to the root level
of the theme
- Renamed `dist` to `build` and updated in libraries file
References #41
Update the test for updating a talk node as it was essentially doing the
same as the test for creating a new talk node.
The test now ensures that the talk is saved before adding an event, and
that the talk created date is different to the original created date as
well as that it matches the latest event date.
To ensure that the event dates for a talk are always in the correct
order, and to make the editing experience easier, this change
automatically re-orders the events on a talk node to be based on the
event date.
Fixes#74
Include the file containing the body field values within the `purge`
settings so that Tailwind uses it and prevents any classes within it
from being removed from the production CSS.
References #55
Add a custom Drush command that exports the body field values for node
and block body fields into a file.
This file can then be included within Tailwind's `purge` settings to
prevent classes used within the body fields from being purged.
References #55
Oliver Davies