scriptype / writ-cms / 14285885590 / 1

39%

master: 39%

push

github

[CM2] Introduce inline collection contentTypes 👇

Collection index can have these properties:
- contentType
- categoryContentType
- entryContentType
- categoryAlias
- categoriesAlias
- entryAlias
- entriesAlias
- defaultCategoryName

'defaultCategoryName' is to allow custom defaultCategory names per collection.
'ContentType' fields are used for template lookup during rendering.
'Alias' fields are to assist contentType-specific templates' readability.

for example, in a custom collection template, instead of:
{{#each categories}}

you can say:
{{#each technologies}}

given you set categoriesAlias: technologies in the collection index.

Similar logic applies to all aliases and their template counterparts.
You can talk domain-driven in your templates now 💫

The idea is to brace myself to standalone contentType definitions the
CMS frontend will eventually require. For now something resembling them
can be inlined to collection frontMatter. Besides, compiler probably won't ever
care about much more than what is implemented here.

Also:
- Fix default category index overriding collection index by giving it an actual
slug, outputPath etc.
- Remove the unneeded Settings dependency from attachment, category, post and tag
- Lookup for a 'default.hbs' during rendering as a last resort, instead of 'index.hbs'
- Get rid of the default 'text' contentType

What's left:
A theme2 I guess...

443 of 698 branches covered (63.47%)

Branch coverage included in aggregate %.

2231 of 2798 relevant lines covered (79.74%)

37.12 hits per line