[Feature]: User should be able to specify default list when using TNT Content

[thombruce]

Feature request

E.g. If the user has a /content/blog directory and their site is a blogging site, they may set the default content directory to blog and this should show on the front page.

Presently I believe the front page simply lists neighbouring pages by default (i.e. non-nested ones).

Consider use cases:

• Blog is likely to want blog/ as main content
• News site might want articles/ as main content
• Shop might want products/ as main content
• Docs site might want... exactly the current behaviour

Tempted to create new layer templates that inherit from TNT Content... Also tempted to rename 'TNT Content' to 'Dynamite' so that new inheriting layers can be named like 'Dynamite Blog', 'Dynamite Shop', 'Dynamite Docs', etc. A separation of responsibility - TNT as the main framework, Dynamite as the content site templates.

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[thombruce]

Note that regardless of any new template setting its own default, the main content section should still be configurable.

[thombruce]

Note that if we do want to abandon @thombruce/tnt-content in favour of @thombruce/dynamite, we should mark TNT Content as deprecated following the steps suggested here: https://stackoverflow.com/questions/28371669/renaming-a-published-npm-module