Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an idea of how books might work. The hope is that it will provoke discussion and help drive towards what might be useful (if this does turn out to be useful at all.)
They way I have it setup in this example is to use a
books
collection with its own layout that has no exciting structure. The author is free to lay it out as they see fit and either inject recipes using a standard lookinginclude
(not yet written) or just write them out in their own way. The book can be quite free-form in this manner as I think @clarklab was keen on. The clever part comes form the recipe end.In recipes you can mark them as being part of any number of books.
This keeps the association with the recipe and makes life a bit easier. When viewing a recipe you can see which books it is in:
Also, at the bottom of the book you can see an index of the recipes that refer to it, and a list of books by the same author:
Authors are identified in
_data/people.yml
- which no doubt will find uses elsewhere. We could even use them as the 'chef' of a recipe?As I say, although very much a functioning idea, this is still just an idea and open to ravaging change.