Organised eleventy

[jbarnardmoj]

Pull-request templates

Please follow the steps below to tell us about your contribution.

1. Copy the correct template for your contribution

• Are you fixing a bug? Copy the template
• Are you improving performance? Copy the template
• Are you updating documentation? Copy the template
• Are you changing functionality? Copy the template

2. Replace this text with the contents of the template
3. Fill in all sections of the template
4. Click "Create pull request".

[chrispymm]

I think this PR goes a bit further than I anticipated, and IMO ends up with a slightly unreadable .eleventy.js file - it feels like it ends up being hard to scan that file and see what filters / shortcodes are enabled and most importantly the string I need to use to invoke them, which isn't ideal.

I think I was expecting each extracted filter/shortcode to export the filter/shortcode function, and then the eleventy config file would still have the addShortcode definition bit

const tabs = require('shortcodes/tabs.js')

eleventyConfig.addPairedShortcode("tabs", tabs)

This extracts away the implementation, but leaves someone able to read the eleventy config file and see what shortcodes and filters are available to them, and how to invoke them.

This may cause scoping issues for the tabs / tab shortcode though...

I think if we can't do the above I'd still prefer manually requiring each file within .eleventy.js rather than looping through a directory